ToolsConductScience tool
Monitoring & TelemetryFree in-browser calculator

Experiment Sync & Timing Calculator.

Plan multi-device experiment rigs with TTL sync analysis, data rate budgets, and timing alignment recommendations.

PrivateData stays in your browser
LiveNo sign-up required
Open methodFormula shown on this page
CitableMethods and citation included

Calculator

Results update in place

Try it out

Load example Experiment Sync & Timing Calculator data to see the full workflow

Add Device to Rig

When to use

  • Plan a multi-device recording rig before purchasing hardware
  • Calculate total data throughput to size your storage system
  • Identify timing alignment risks between electrophysiology, video, and behavioral devices
  • Determine which device should serve as the master clock
  • Generate a sync plan document for your lab notebook or methods section

Do not use for

  • For real-time sync monitoring during active recordings — use your acquisition software
  • As a substitute for empirical latency measurement with an oscilloscope
  • For network-synchronized distributed experiments (NTP/PTP timing)

Always designate a single master clock

Running multiple devices on internal clocks guarantees drift. Choose the device with the lowest TTL latency as your master and wire all others to its sync output. NI DAQ devices are popular choices due to sub-microsecond TTL latency.

Account for display latency in stimulus timing

Monitors and projectors add 8–16 ms of pipeline delay between the software trigger and photon emission. Use a photodiode on the display corner to measure actual stimulus onset and record it on your sync line.

Budget 2× your calculated storage

Raw data rates do not account for file headers, metadata, incomplete writes, or backup copies. For long recordings (>1 hour), budget at least twice the calculated storage and verify sustained write speed with a benchmark before the experiment.

Test sync before every experiment session

TTL cables, BNC connectors, and USB hubs can fail intermittently. Send a test pulse train and verify all devices register the correct count before starting data collection.

1

Method

Data rate computed as sample rate ×\times channels ×\times bytes per sample for each device. Sync error computed as max TTL latency minus min TTL latency across the rig. Warnings triggered by sync error exceeding 1 ms for ephys rigs or exceeding frame duration for video devices. Device specs sourced from manufacturer datasheets for Neuropixels (IMEC), Open Ephys, National Instruments, Tucker-Davis Technologies, Basler, and FLIR.

2

Published

Published 2026-04-08. Calculations support planning and documentation; verify procurement decisions against manufacturer specifications or institutional SOPs.

3

How to cite

How to Cite

ConductScience Experiment Sync & Timing Calculator. ConductScience, Inc. 2026. Available at: https://conductscience.com/tools/experiment-sync-calculator

Siegle JH et al. Open Ephys: an open-source, plugin-based platform for multichannel electrophysiology. J Neural Eng. 2017;14(4):045003.

Jun JJ et al. Fully integrated silicon probes for high-density recording of neural activity. Nature. 2017;551(7679):232–236.

Multi-Device Synchronization Fundamentals

Modern neuroscience experiments typically combine multiple data streams — electrophysiology, video, photometry, behavioral sensors, and stimulus delivery — that must be aligned in time.

TTL Synchronization uses digital pulses (0–5V) to mark common time points across devices. A master clock sends periodic pulses that each device timestamps in its own data stream. Post-hoc alignment matches these timestamps across files.
Clock Sources determine timing accuracy. A master clock generates the sync signal. External-clocked devices lock to the master. Internal-clocked devices run independently and are most prone to drift.
Data Budgeting ensures your storage and bandwidth can handle the combined throughput. Electrophysiology probes like Neuropixels generate 20+ MB/s alone — a full rig can easily exceed 100 MB/s, requiring NVMe or RAID storage.

Common Pitfalls in Experiment Synchronization

Several issues can compromise data alignment in multi-device experiments:

• Unsynced internal clocks: Two devices with independent 10 MHz oscillators will drift apart at 10–100 ppm, accumulating milliseconds of error per hour • Display latency: Monitors add 8–16 ms of frame delay. Stimulus onset times must account for this pipeline delay, not just the software trigger timestamp • USB polling jitter: USB devices have variable polling intervals (125 µs for USB2, 1 ms for USB1.1) that add timing uncertainty beyond the device’s inherent latency • Buffer overflow drops: When data rate exceeds storage write speed, samples are silently dropped, creating undetectable timing gaps • Ground loops: Sharing TTL lines between devices on different power circuits can introduce noise that corrupts sync pulses • Aliased video sync: If sync error exceeds the camera frame period, events appear in the wrong video frame, corrupting behavioral annotations

Frequently asked

What is TTL sync and why does latency matter?
TTL (transistor-transistor logic) sync uses digital pulses to align data streams from multiple devices. Each device has an inherent latency between receiving a TTL pulse and timestamping its data. The difference between the fastest and slowest device latencies determines the maximum timing error in your synchronized recording. For electrophysiology, sub-millisecond alignment is critical for spike-timing analyses.
How is the maximum sync error calculated?
Maximum sync error equals the highest TTL latency minus the lowest TTL latency across all devices in your rig. For example, if a Neuropixels probe has 10 µs latency and a stimulus display has 8,000 µs latency, the maximum sync error is 7,990 µs. This represents the worst-case timing misalignment between any two data streams.
What is a master clock and how should I choose one?
A master clock is the device that generates the synchronization signal for all other devices. The ideal master clock has the lowest TTL latency, highest temporal precision, and a dedicated sync output. NI DAQ devices and dedicated sync boxes are common choices. All other devices should be configured to accept external sync from the master rather than using their internal oscillators.
How are data rates and storage estimates calculated?
Data rate for each device equals sample rate (Hz) ×\times number of channels ×\times bytes per sample. For example, Neuropixels at 30 kHz ×\times 384 channels ×\times 2 bytes = 23.04 MB/s. Storage per hour multiplies the total data rate by 3,600 seconds. These are raw data estimates — compression and file format overhead may vary.
When should I worry about clock drift?
Clock drift occurs when devices with independent internal oscillators gradually desynchronize over time. Typical crystal oscillators drift 10–100 ppm, meaning 36–360 ms of drift per hour. If multiple devices use internal clocks without periodic resynchronization, timestamps will diverge. Always use a shared TTL sync line for recordings longer than a few minutes.
What data protocols are supported?
The calculator supports USB3, USB2, USB, SPI, I2C, analog, and HDMI protocols. Protocol choice affects maximum sustainable data rate and latency. USB3 supports up to 5 Gbps, USB2 up to 480 Mbps, SPI varies by implementation but offers very low latency, and HDMI introduces frame-level latency from display processing.
325
Free tools
1,200+
Institutions
100%
Client-side
0
Uploads required