Free · No login required
DMX frame timing
Estimate serial DMX frame time and the corresponding maximum refresh rate.
Data slots (1–512): 1–512; BREAK duration (µs): 92–100000; Mark after BREAK (µs): 12–100000
Inputs stay on this page and clear on refresh.
DMX frame timing
Data slots (1–512): 512 BREAK duration (µs): 176 Mark after BREAK (µs): 12
- Frame interval (ms)
- 22.760000
- Maximum refresh rate (Hz)
- 43.936731
At a nominal 250 kbit/s, a slot has 1 start bit, 8 data bits and 2 stop bits: 11 × 4 µs = 44 µs. Raw interval = BREAK + mark after BREAK + 44 × (data slots + 1); the extra slot is the start code, not another control channel. Frame interval = max(raw interval, 1204 µs), adding idle time when necessary to respect the transmitter minimum break-to-break interval in ANSI E1.11-2024. Refresh rate = 1,000,000 / frame interval in µs. Enter 1–512 whole data slots, BREAK 92–100,000 µs and mark after BREAK 12–100,000 µs; timing values may be fractional. This idealized NULL-start-code stream assumes no extra inter-slot or inter-packet gaps. It excludes RDM traffic, network transport, console processing and fixture response time. Short packets may not suit every receiver. This is a timing estimate, not a compatibility or compliance test; verify supported console speeds and fixtures. Six decimals are displayed without intermediate rounding.
Methodology
How it works
At a nominal 250 kbit/s, a slot has 1 start bit, 8 data bits and 2 stop bits: 11 × 4 µs = 44 µs. Raw interval = BREAK + mark after BREAK + 44 × (data slots + 1); the extra slot is the start code, not another control channel. Frame interval = max(raw interval, 1204 µs), adding idle time when necessary to respect the transmitter minimum break-to-break interval in ANSI E1.11-2024. Refresh rate = 1,000,000 / frame interval in µs. Enter 1–512 whole data slots, BREAK 92–100,000 µs and mark after BREAK 12–100,000 µs; timing values may be fractional. This idealized NULL-start-code stream assumes no extra inter-slot or inter-packet gaps. It excludes RDM traffic, network transport, console processing and fixture response time. Short packets may not suit every receiver. This is a timing estimate, not a compatibility or compliance test; verify supported console speeds and fixtures. Six decimals are displayed without intermediate rounding.
Method and assumptions documented by Techrider.live
2026-10-29
Frequently asked questions
Can reducing slots always make fixtures update faster?
No. The model adds idle time below 1204 µs, and actual controllers, receivers and fixture processing can impose slower rates. Keep all required control slots and check manufacturer support.