About this replacement
Riser Bond RD6000 Series — 7.2V Ni-MH Replacement Battery (61/160-0038-00)
This is a 7.2V 3900mAh Ni-MH replacement battery for the Riser Bond RD6000, 6000DSL, and 6000TDR multi-function cable test analysers. It replaces OEM part 61/160-0038-00 directly. The pack fits into the same battery bay and uses the same connector as the original unit.
- RD6000, 6000DSL, and 6000TDR compatibility: All three variants run the same 7.2V power rail, use the same mechanical bay dimensions, and share the same BMS handshake protocol — which is why one pack covers the full range without modification.
- Bench tested on actual hardware: We ran this pack through full charge and discharge cycles on the RD6000 platform. The BMS handled probe initialisation current spikes without tripping, and voltage held steady across sustained TDR measurement sessions.
- First-use calibration on RD6000: After installing this pack, run a full calibration cycle through the instrument menu before heading into the field. The RD6000 maps battery state during calibration — skip this and the low-battery indicator fires prematurely on the first measurement session, even with a full pack.
BMS lockout after the RD6000 sat unused in a carry case for months
Ni-MH cells self-discharge over time, and if the pack drops below approximately 5.4V total during extended storage, the BMS enters a protection state and refuses to accept a charge. The charger appears to do nothing — no indicator, no current draw. To recover the pack, apply a slow trickle charge at around 0.1C for 20–30 minutes using a compatible Ni-MH charger that supports recovery mode. Once cell voltage climbs back above the BMS threshold, normal charging resumes.
Voltage dropout causing readings to reset mid-logging session
During a sustained TDR or DSL logging run, the RD6000 draws continuous power across both its processing core and active sensor circuits. A degraded or partially charged Ni-MH cell cannot hold voltage under that combined load, causing a brief dropout that triggers a measurement reset. This looks like a software glitch but is a power supply issue. Charge the pack fully before any long logging session, and check that resting voltage reads at least 8.4V before you start.