Application · Synchronized high-speed video & sensor data acquisition
At 140 m/s, a 10 ms timing error is 1.4 metres.
When a high-speed camera and a separate measurement system each keep their own clock, the two datasets drift apart. This is how HSCAM keeps them aligned.
Trade-show demonstration Real demonstration
Multi-camera synchronization, shown live
This setup shows synchronization of multiple cameras, analog inputs, and automated trigger options — demonstrated at the Messe Vision trade fair and reviewed live in HSCAM's own recording software.
HSCAM STREAMER 1M13 and 1C13, in MultiCAM mode synced by exposure, triggered on an ADC threshold value with a 1 second pre-trigger buffer. A Python plugin for HSCam Viewer drove acquisition, with a live measurement-evaluation script generating marker/trigger events whenever the ADC value crossed a definable threshold, and automated replay to a separate display.
Dual-camera playback with synchronized ADC data
- Cameras
- 1C13 + 1M13
- Recorded at
- 1,280 × 864 px @ 1,000 fps
- Compression
- ~4.15 / ~4.19
- On-screen date
- 08.11.2018
Real screen recording from Messe Vision 2018. The figures are those shown by HSCam Viewer.
Single-camera view with 4-channel ADC graph
- Camera
- HSCAM 1M13
- Channels shown
- ADC 1–4
- View
- Single camera + waveform
- Source
- Messe Vision 2018
Real screen recording from the same demo, showing the measurement-channel side on its own.
Why this is hard
Two systems, two clocks, one process
A separate camera and measurement system, synced only loosely (e.g. by a shared trigger signal or a control-system cycle), accumulate a timing error that is hard to remove afterwards, because the data was already recorded out of alignment.
Worked example: steel wire at 140 m/s
~10 ms offset → up to 1.4 m
Assume a measurement that is 10 ms away from its video frame (140 m/s × 10 ms = 1.4 m). It refers to a wire position up to 1.4 m from the one in the picture, so video and measurement no longer correlate. About 10 ms is typical when systems sync through control-system cycles.
HSCAM's approach
Measurement data captured on the camera's own clock
HSCAM STREAMER cameras acquire analogue and digital measurement channels internally, on the same clock as the image sensor — rather than relying on an external system to align two independent clocks after the fact.
Built-in channels
4× 16-bit ADC (±10V) · 2× GPIO
Extended channels
Up to 20 ADC via HS-DAQ
Multi-camera sync
MultiCAM mode, synced by exposure
Demonstrated at Messe Vision, in the measurement setup shown below.
Measured performance
Timing and position: two separate results
How tightly frames and samples line up in time is one question; how accurately the resulting positions line up is another.
Timing
100 MHz camera clock
Video frames and measurement samples are acquired on the camera’s internal 100 MHz clock, so each measurement can be tied to the frame it belongs to.
Position
Sub-millimeter
In the steel-mill installation, video and measurement line up in position to sub-millimeter accuracy.
Four numbers that are easy to confuse
- Frame rate and ROI
- Images per second for a given image area. A smaller region of interest gives a higher rate.
- 1,318 fps at 1,280 × 864 px · 168,000 fps at 1,280 × 4 px
- Exposure time
- How long each frame collects light. It sets the motion blur and is chosen separately from the frame rate.
- Minimum 1 µs · 100 ns – 3 µs with strobe lighting in the steel-mill installation
- Synchronization
- Time offset between a measurement sample and its video frame, and how much that offset varies (jitter). Synchronization is based on the camera’s internal 100 MHz clock.
- Example: 140 m/s × 10 ms offset = 1.4 m
- Latency
- Time from an event to a decision or reaction. It depends on where the processing happens.
- < 100 ms in the PC-based tiers · < 1 µs in the FPGA tier
Evidence
Demonstrated Results
Trade-show demonstration Demonstrated Results — trade-show capability demo
Punching-Ball measurement fusion
HSCAM STREAMER 1M13 and 1C13 in MultiCAM mode, synchronized by exposure, triggered on an ADC threshold value, tracking a punching ball. Live HSCam Viewer software shown on-screen.
- Pre-trigger buffer
- 1 second
- Recorded at
- 1,280 × 864 px @ 1,000 fps, both cameras
Documented deployment Photo: demonstration on a high-speed shear Demonstrated Results — real industrial deployment
Steel & rolling mill process monitoring
HSCAM STREAMER 1M13 deployed for around-the-clock monitoring of a high-speed steel shear-trimming process, with synchronized measurement data acquisition. Recording is started by a photocell and runs while goods are present.
- Timing
- Video frames and measurement samples acquired on the camera’s internal 100 MHz clock
- Position
- Sub-millimeter alignment of video and measurement
- Data rate, one camera
- ~1.44 GB/s uncompressed → ~300 MB/s after in-camera compression (~5:1)
Relevant hardware
Cameras used in this application
Integration
Configure triggers in Python, go to FPGA for microsecond timing
Trigger logic, pre-trigger buffering and per-channel measurement acquisition are configured through HSCAM's Python scripting plugin. For sub-microsecond response there is an FPGA tier, integrated by HSCAM.
| Tier | Latency · platform |
|---|---|
| Python-Framework camera SDK | < 100 ms latency · PC/Laptop · customer with provided examples |
| Camera SDK integration | < 100 ms latency · PC/Laptop · customer with additional HSCAM support |
| FPGA integration | < 1 µs latency · on-camera · HSCAM only for now |
| DAQ extension | < 1 µs latency · DAQ module · HSCAM only for now |
Related
The camera behind it
Recognize this problem in your own process?
I have a similar problemThe demonstrations here show what is possible with synchronized recording. Whether it suits your process is checked case by case, in your own setup, before a limited test is agreed. See how a pilot project works.
Talk to an engineer about your synchronization requirement
Tell us which signals have to line up with the video, how closely, and what triggers the recording.
Helpful, but not required
- What your process does and what goes wrong, or what you cannot see today
- Speed or cycle time, if you know it
- Measurement or trigger signals that exist on the machine
- Environment: temperature, lighting, mounting space
contact@hscam.com · hscam.com