Compare event images, short clips and continuous video by output value, power, bandwidth, storage, review workload and the CamThink hardware role each mode requires.
Event-triggered images, event clips and continuous video are not three quality levels of the same system. They create different evidence, cost profiles and hardware requirements. A still image can prove that a condition existed at a time. A short clip can add movement context. Continuous video preserves the sequence before, during and after an event.
That distinction matters in more than wildlife monitoring. A remote meter project may only need a scheduled image. A waste bin or field asset project may need an event image plus a structured result. A restricted zone may need an AI event with a short evidence clip. A factory gate, parking entrance, wildfire lookout or VMS upgrade may need continuous video with edge-side event extraction.
This guide focuses on the capture-mode decision and the CamThink hardware route behind it. For detailed trigger wiring, use the low-power camera trigger guide. For solar sizing and off-grid networking, use the solar-powered remote monitoring guide.
Event-triggered image capture works well when the useful result is a compact visual record. The camera can sleep between captures, wake from a PIR, radar, GPIO input, schedule or remote command, then store or transmit a JPEG and return to low-power operation. The trigger starts capture; it should not be treated as proof that the correct object or condition was present unless the downstream logic confirms it.
The weakness is context. A trigger may fire late. One image may not show direction, duration, sequence or cause. A burst can improve the chance of a useful frame, but it increases active time, storage and network transfer.
NE101 is CamThink’s low-power capture role for scheduled or event-based imaging, local Micro TF storage and modular communication paths. NE301 adds 0.6 TOPS of on-device AI compute when the node should filter obvious non-target events or publish a structured result before upload.
A short event clip keeps the event boundary but adds a few seconds of motion. It is useful when a still image is too thin, yet continuous recording is too expensive. Typical examples include a person crossing a restricted line, a vehicle entering a yard, a short animal interaction, a machine action, a loading event or a safety incident that needs visual confirmation.
The tradeoff is active time. The camera, illumination and radio may stay awake longer. Files are larger, weak networks take more time to upload and review changes from scanning images to watching clips.
Use event clips when the project can define the action and its likely duration. If the action often starts before the trigger or continues after the clip ends, the system is cutting away the evidence the operator or model needs.
Continuous video is the right source when sequence, dwell time, handoff or later investigation matters. It can show arrival, approach, duration, direction, repeated interaction and departure without relying on a trigger to define the beginning of the event.
Fixed observation points are the natural fit: parking entrances, factory gates, warehouse zones, equipment rooms, security perimeters, wildfire lookout points, waterholes, crossings or any location where the same scene deserves repeated analysis. Continuous video also lets a team change the event definition later, provided the media has been retained.
The cost is operational. Continuous cameras need stable power, sustained storage, network planning and a way to extract the useful events. In research settings, a US Forest Service study of continuous nest-cavity video illustrates the review burden: automated motion detection can help tag events, but human review may still be required for final interpretation.
NE503 fits the fixed video role. It combines 4K video input, 20 TOPS INT8 Hailo compute, containerized applications, RTSP and structured event paths in an IP67 camera powered by PoE 802.3at or DC 12 V. It can run detection close to the image source and send selected events, clips or data upstream.
| Decision | Event images | Event clips | Continuous video |
|---|---|---|---|
| Best evidence | Presence, condition, timestamp | Short action, direction, visual confirmation | Dwell, sequence, handoff, repeated interaction |
| Power pattern | Sleeps between events | Sleeps, then remains active for the clip | Sustained camera and processing load |
| Storage and network | Lowest per event | Moderate per event | Highest unless processed locally |
| Trigger dependence | High | High at clip start | Low for capture, AI can define events later |
| Review workload | Fast image triage | Clip review | Requires event extraction or large review effort |
| Typical CamThink role | NE101 or NE301 | NE301 for event workflows; NE503 for fixed points | NE503 or NG4500, depending on camera topology |
The table is a routing tool, not a ranking. Continuous video is not a better version of event capture. It solves a different evidence problem and brings a different infrastructure requirement.
Choose NE101 when the point is distributed, capture is infrequent and the node should spend most of its time asleep. It fits scheduled images, event-triggered stills, remote inspection, field image collection and server-side AI workflows.
Choose NE301 when an event-based site benefits from local lightweight inference. It can reduce blank media, publish structured detections over MQTT and support pilots where Wi-Fi, LTE Cat.1 or PoE variants match different site constraints. The model and threshold still need validation on the project dataset.
Choose NE503 when the camera point has stable power and the output depends on continuous video, higher-resolution evidence, local applications, RTSP or structured event delivery. It is a fixed-site edge AI camera, not a deep-sleep battery node.
Choose NG4500 when several camera feeds or uploaded image sets need shared local processing. It fits existing IPC upgrades, multi-camera AI, heavier models, local storage and integration workflows. NG4500 is an edge AI box for a cabinet, station, vehicle or equipment room, not an outdoor camera by itself.
A real project may combine roles. NE101 can collect scheduled images from remote assets, NE301 can filter low-power event points, NE503 can watch fixed high-value zones, and NG4500 can process several camera feeds at the site. That product mix is often more realistic than forcing every point into one camera model.
When the output and site constraints are clear, ask CamThink to compare a low-power image node, an event AI camera, a fixed AI camera and a local processing gateway.
This order keeps the operating result ahead of the product. It also prevents common mismatches: streaming 24/7 video when a timestamped image is enough, or trying to prove dwell time from isolated trigger images.
| Scenario | Usually start with | Typical CamThink route |
|---|---|---|
| Remote meter, gauge or equipment inspection | Scheduled image or event image | NE101 for image capture; NE301 when local AI/OCR filtering is required |
| Remote intrusion, gate or field asset alert | Event image, event clip or structured AI event | NE301 for low-power AI event reporting; NE503 when the site is fixed and powered |
| Factory gate, parking entrance or warehouse zone | Continuous or frequent video with event extraction | NE503 for camera-side AI; NG4500 when multiple streams are processed together |
| Existing CCTV or VMS upgrade | Continuous RTSP streams into local inference | NG4500 for multi-camera edge AI, with NE503 for new high-value camera points |
| Wildlife, agriculture or environmental field point | Event image, scheduled image or short clip | NE101 for low-power capture; NE301 for lightweight filtering; link to the wildlife system guide for full remote design |
| Wildfire lookout or fixed risk zone | Scheduled image, event evidence or continuous video depending on power | NE301 for low-power remote pilots; NE503 or NG4500 for fixed powered observation |
An event-capture pilot should measure how many usable records arrive per service interval, how many files are blank, how long the node stays active and whether the backend receives a clean event contract. A continuous-video pilot should measure whether the event extractor preserves the beginning and end of useful events, how much footage is stored and how much review time remains.
Do not combine every requirement in the first test. A small pilot that answers one capture decision creates a better basis for camera count, power design, data plan, storage budget, model placement and integration scope.
Use event images when the business value is a compact visual record. Add short clips when a bounded action needs motion context. Use continuous video when sequence, dwell, later investigation or operator review is the actual result.
CamThink supports the transitions between those modes. NE101 collects low-power images, NE301 adds event-side AI filtering, NE503 handles fixed video and local camera applications, and NG4500 provides shared on-prem processing. The products are not substitutes on a single performance ladder. Each one belongs at a different point in the edge AI camera architecture.
