Offline storage needs a defined limit and recovery process; event sizes, full-buffer behavior and original timestamps all matter.
That depends on the device's configured behavior: it may stop collecting, overwrite older records or raise an alert. The supplier needs to state which applies, with capacity expressed using the actual records and images the installation will retain.
A loosely described number of plate logs is not enough. Record size, retained images and reserved free space determine how much interruption the buffer can accommodate.
Local recording separated the moment an observation was captured from the moment it reached a central record. Connected edge deployments use that separation as an offline buffer followed by synchronisation.
Once delivery is deferred, acknowledgements matter. The device needs to distinguish an observation still awaiting upload from one received successfully, while keeping its original identity and capture time.
Buffering is useful where communications may be interrupted. Another permitted fallback can lead to a different storage arrangement. The decision should follow the expected outage volume and what the operator can do when collection is interrupted.
Unlimited local history is not an appropriate default. Retention and access controls still apply to buffered records, so capacity planning needs to respect how long those records may be held.
For illustration, 1,000 events per hour at 250 kB each produce about 2 GB over eight hours in decimal units. That excludes indexes, telemetry, repeated images and reserved space. Retaining video with each event could change the requirement substantially, so the assumed event content must be explicit.
Test full-buffer behavior, restart and upload recovery together. Original event identifiers help reconcile retries, and original capture times preserve when the observation happened. An upload timestamp should not silently become the visit time; removing a pending copy also needs a successful-delivery acknowledgement.
SolarLink describes local operation with permitted records synchronised when connectivity returns. Its public description does not provide a universal offline capacity for every installation.
The offered device's capacity and full-buffer behavior need separate confirmation. Those details connect the general synchronisation approach to the site's actual outage and retention requirements.
Aero Ranger: SolarLink local operation and managed synchronisation
Sources were reviewed on the publication date. Check the linked material for current details.
