RK3588 EDGE VIDEO EVENT ENGINE
Engineering Prototype / Road-video Test RecordsFrom vehicle detection to traffic event decisions.
An emergency parking bay requires continuous entry, dwell and departure decisions for the same vehicle. A bounding box is not a complete traffic event: association, state and evidence determine whether the result is useful.
A vehicle enters the configured zone. Create event context.
state: entry · evidence: snapshotHow business state is formed
Video → vehicle detection/association → ROI and time rules → ENTRY / OVERSTAY / LEAVE → evidence → external adapter. These names describe business semantics; actual codes are mapped to the interface contract. Occlusion, temporary missed detections and real departures must be distinguished.
Why temporal plate voting matters
Reviewed records include a HyperLPR3 RKNN image path and a GPU/RK road-video parity audit. Individual frames differed; temporal voting produced the same stable result on that sample. This is sample-specific evidence, not general recognition accuracy or coverage of every plate class and night scene.
Evidence and open acceptance items
Records cover panorama/close-up evidence, vehicle lifecycle and fast/e2e checks on a specified clean RK3588 device. Earlier mock dashboards remain mock features. External side effects are disabled by default; leaving prediction, complex occlusion, lighting, camera compatibility and sustained operation remain qualification work. Alert-time targets are not measured results.
Demo and project evaluation
Public pages use an original state-workflow illustration, without customer footage, plates, names or site identifiers. With Hank, first agree authorized footage, target events, zones and failure cases, then confirm the demo version and pilot scope.
DEFINE ONE TESTABLE WORKFLOW
Bring your application to Hank.
Agree inputs, events and acceptance before discussing integration.