0.8 m fast sensor tether
Fast • 400 kHz • 2 devices
- VCC: 3.3 V
- Cable: 0.8 m @ 70 pF/m
- Extra: 30 pF
- Suggested R: 2.7 kΩ
Quickly size the pull-up resistors for your I2C bus, estimate rise time, and check compliance with the I2C specification.
Click “Apply” to load values, or “Copy link”.
Fast • 400 kHz • 2 devices
Standard • 100 kHz • multi-drop
Standard • 100 kHz • short
Range: 0 – VCC/2 (we clamp to this theoretical limit).
Range: 0.5 – 10 mA (typical MCU sink capability).
Range: 0 – 20 m (values outside are clamped).
Range: 10 – 150 pF/m (typical twisted pair: 40–80 pF/m).
Range: 0 – 500 pF (roughly 15–20 pF per device).
Count ~15 pF per device on the bus.
Estimated capacitance: pF
Rpull-up min (IOL = 3 mA):
Rpull-up max (tr = 1000 ns):
Range: 0.5 – 100 kΩ (tool clamps the value).
Rise time:
Pull-up current: mA
Package the calculation for a ticket, a review, or a teammate in seconds.
References: NXP AN10216-1, TI SLVA689.
A step-by-step playbook to estimate bus capacitance, size pull-ups, draft the harness, and validate that SDA/SCL stay within spec.
Staying roughly mid-way between the minimum and maximum resistor values keeps both requirements happy: you respect the sink-current limit while staying well inside the rise-time window. If you need extra robustness, aim for about 20% more current than the minimum and 20% faster rise time than required.
Try reducing cable length, removing unused branches, or lowering the pull-up voltage so the current requirement relaxes. If the bus is still too heavy, consider an I2C buffer/repeater to split the capacitance or migrate the longest segment to a differential standard that tolerates more load.
Only if every device on the bus is 5 V tolerant. Otherwise you should pull the bus up to 3.3 V, add a level shifter, or use a dual-rail buffer. Overstressing the inputs is a common cause of intermittent I2C faults.
Follow the complete checklist to size pull-ups, route the harness, and verify timing.
Generate a shareable harness diagram once your planner values are locked in.
Review spec limits, buffering options, and noise mitigation tips for I2C.