Back to Blog

How to Check an AOV Camera for Recording Gaps Before You Order Fifty

2026-09-088 min readSolaGuard Team
AOVtestingprocurementsolar camera

TL;DR

The app timeline cannot prove 24-hour coverage. Here is a 72-hour on-site acceptance test — card audit, spreadsheet method, staged events and a gap-pattern table — that turns an AOV claim into something you can measure and write into a purchase order.

The answer: audit the card, not the app timeline

To verify that a camera sold as AOV really logs a full 24 hours, run one sample for a calendar day on battery and panel in the position you actually intend to use, then pull the microSD and audit the file list — start time, duration, computed end time, next start time — and confirm every minute from midnight to midnight is accounted for. The app timeline is not evidence: it is a rendered summary that smooths short gaps, hides segment boundaries and often shows cached data. A gap is a numeric difference between where one file ends and the next begins, and you can only see that on the card. Run it for 72 hours including one overcast day, stage a handful of events at known clock times, and you have a test that costs one sample and tells you more than any datasheet.

Do this before you order fifty. Cameras are 5 to 10 minutes to install, so a proper acceptance test costs an afternoon, and the trial MOQ of 10 units exists so that buyers can run exactly this.

Why the app timeline is not evidence

Mobile apps compress a day into a few hundred pixels. A two-minute hole is a fraction of a pixel wide, so it is invisible by construction. Apps also render from an index the camera or the cloud generated, and if the index is written after the fact it can be complete while the underlying files are not. Worse, some apps display a continuous bar wherever recording was scheduled, not wherever footage exists.

Three practical consequences:

  • Scroll and tap testing proves nothing. If you tap into ten random moments and all ten play, you have sampled ten of 1,440 minutes.
  • Cloud playback can be more complete than the card, or less. Establish which one you are actually buying before you compare anything.
  • If the app is your only view into the recording, you have no way to audit a supplier's claim after delivery, either. That is a procurement problem, not just a testing one.

The 72-hour acceptance test

Set it up on the site, not on a desk. Bench conditions remove the two variables that decide the outcome: solar harvest and cellular signal.

  1. Day 0. Format the card in the camera. Set the time zone and confirm the burnt-in timestamp against a phone clock. Set the camera exactly as you intend to deploy it — same resolution, same continuous-recording setting, same detection zones. Write down the settings.
  2. Position. Mount one unit in the worst position you expect to sell into: partial shade on the panel, weak signal, north-facing. Mount a second in a representative good position. One camera tells you whether it works; two tell you where the edge is.
  3. Hands off. Do not open the live view for the whole 72 hours. Live streaming over 4G is the single biggest power draw, and if you spend the budget watching, you have tested a different product from the one that will be deployed.
  4. Stage events at recorded times. Note the clock time of each on paper — see below.
  5. Retrieve and audit. Pull the card, copy everything, and build the spreadsheet described in the next section. Then, separately, look at the app for the same period and note every discrepancy. The discrepancies are as informative as the gaps.

Staging the events that matter

The point of AOV is coverage when nothing triggers a sensor. Stage the events a motion-triggered camera is known to miss, and check they exist on the continuous track even where no event tag fired:

  • A slow walk along the fence line at the far end of the camera's usable range, around 03:00.
  • Someone entering at the extreme edge of frame rather than through the middle.
  • A person standing still for five minutes, then moving — the classic PIR failure.
  • A vehicle arriving and leaving on the same pass, before dawn.
  • One event during the overcast day, late in the test, after the battery has been working.

That last one is the whole test in miniature: it checks whether coverage still exists at the moment the power budget is under stress, which is exactly the moment a site is unattended.

Auditing the card: what a gap actually looks like

Continuous recorders write fixed-length segments. Load the file list into a spreadsheet with four columns — filename, start timestamp, duration, computed end — then add a fifth: next start minus computed end. Sort by that column, largest first. Everything you need is now at the top of the sheet.

Pattern in the delta column Most likely cause What to do about it
Uniform sub-second gaps between every file Normal segment boundary Measure it and record the figure; sub-second is expected, whole seconds are not
The same gap every night at the same clock time Scheduled reboot, firmware housekeeping or a recording schedule Ask for the maintenance window in writing and whether it is configurable
Ragged gaps that begin after a certain hour and worsen across the days Battery step-down as the deficit accumulates Cross-check against the charge history for the same hours
One long gap, normal footage before and after Card write error or a card that dropped out Reformat in camera, retest; if it recurs, the card or the slot is the problem
Gaps that coincide with someone opening the live view The camera cannot record and stream at once A serious defect for an AOV claim — confirm with the factory before ordering
Overlapping or duplicated timestamps Clock resync after signal loss Not a true gap, but it damages the evidential value of the footage

Two arithmetic checks finish the audit. First, the durations for a single calendar day should sum to something extremely close to 1,440 minutes; state the tolerance you will accept and hold the supplier to it. Second, check that the file count matches the segment length — if segments are ten minutes, a full day is 144 files, and a short count is a gap even before you look at timestamps.

Ask for the state log

A camera that records its own power-state and reboot events lets you explain every gap you find instead of guessing. Ask whether the log exists and whether you can export it. A supplier who can hand you the log alongside the footage is a supplier whose AOV claim you can verify; one who cannot is asking you to take it on trust across fifty units.

Turn the test into acceptance criteria

The reason to run this before a volume order is that it converts a marketing term into contract language. Write into the PO, in your own numbers:

Criterion How it is measured Why it matters
Daily coverage Sum of segment durations per calendar day, from the card This is the AOV claim itself
Maximum single gap Largest value in the delta column One long hole is worse than many short ones
Coverage on the worst day Same measurement, on the lowest-harvest day of the test Tells you what you are actually selling in the wet season
Staged-event capture Each staged event present in continuous footage Catches cameras that only really record on trigger
Behaviour under live view Delta column for the period during which the feed was open Exposes stream-versus-record contention

Ask for the same test to be repeatable on production units, not just on the sample you were sent. Then run it again on two units from the first bulk shipment.

Sourcing the trial

Our catalogue runs to 150 SKUs, with wholesale prices quoted per order, all available for OEM and private label, with 1080p to 2K standard across the range and 4K only as a custom or OEM build. Outdoor models are IP66. Manufacturing is by Shenzhen Leksell, TÜV Rheinland certified and established in 2012, with CE, FCC and RoHS. Storage is microSD up to 128 GB as standard, larger only on custom orders.

Samples ship in 7 to 10 days by air and bulk orders in 25 to 40 days by sea; Vietnam orders go out in 7 to 10 business days from our Ho Chi Minh City office. Trial MOQ is 10 units, OEM and ODM start at 100, and dealer margin is 20% from around 10 units and 30% from around 50. Order the trial in a spread of models rather than ten of one — you learn more from testing three candidates in the same yard.

Browse the range on the product catalogue, read the technical background in the AOV solar camera guide, or see volume terms on the wholesale page.

To arrange test samples, WhatsApp +86 188 1869 9870 or email info@solaguard.net. Tell us the sites you are testing against and we will suggest which SKUs to put side by side.

Interested in SolaGuard cameras?

150+ SKUs, dealer orders from 10 units · OEM from 100, 24-month warranty.

Get Quote

B2B terms

  • Dealer margin 20% from ~10 units · 30% from ~50 units
  • OEM / private label / custom spec: MOQ 100 units
  • 24-month warranty · Samples in 7–10 days by air

Browse the matching models

Solar 4G cameras →

Topic overview: AOV Solar Camera: Complete Buyer's Guide — Always-On Video Technology Explained [2026] →

Interested in SolaGuard Cameras?

Contact us for B2B pricing and product samples.

WhatsAppGet quote