In a multi-camera project, synchronization must identify the event involved: trigger arrival, exposure start, image arrival in the application or display refresh. These events occur at different stages. A procurement requirement that only says synchronized display defines neither an exposure-timing test nor which images belong to the same acquisition group.
Specify acquisition and business conditions separately
| Acceptance item | Conditions to define | Suggested evidence |
|---|---|---|
| Exposure timing | Corresponding event, allowed time difference and measurement method | Trigger records, exposure events or validated timing records |
| Frame association | Camera identity, workpiece identifier and grouping rules | Original frames, association identifiers and missing-frame records |
| Processing and transfer | Workload, buffering and timeout rules | Arrival times, queue status and dropped-frame records |
| Business decisions | Samples, decision rules and output states | Labels, results and fault-handling records |
Technology names do not replace acceptance data
Hardware triggering controls a selected acquisition event. A timestamp records the time of a specified event. PTP synchronizes clocks between devices that support it. These mechanisms can be combined, but a feature name does not establish an achieved exposure-time difference. Check manufacturer features against the specific model, firmware and configuration; do not assume identical capabilities across camera brands.
Check fault conditions within the same acquisition group
Define handling for unaccepted triggers, missing frames, unsynchronized clocks, reconnection and processing timeouts. When a current image from one camera is missing, report an incomplete group or pending review under the project rules. No frame from a previous group may be used to mark the current group valid. Timing limits and business-result metrics require the target operating conditions; this article provides no unmeasured universal values.
Associate verification records with actual versions
Record cameras, lenses, exposure settings, trigger wiring, clock configuration, network topology and software versions. Then verify acquisition timing and business-sample results separately. This article describes procurement and acceptance methods, not a deployed or site-accepted multi-camera system.
Mechanism references: Basler triggered acquisition, PTP documentation. Related services: Vision hardware and embedded technology, project consultation.