Horizon BP1530 Survey Meter Replacement Battery 7.2V 3000mAh

Horizon HDSM / HDTM Series — 7.2V Ni-MH Replacement Battery (BP1530)

This is a 7.2V 3000mAh Ni-MH replacement for the Horizon BP1530 battery pack. It fits the HDSM, HDSM USB, HDTM, and USB Plus Satellite meter, along with four additional models in the same instrument family. Voltage and cell count match the original pack exactly.

• HDSM and HDTM platform fit: These meters share the same battery bay geometry, voltage rail, and connector pinout across the series. The BMS in each instrument reads cell voltage directly — no proprietary handshake is required, so the pack registers correctly on first boot.
• Bench tested on actual hardware: We cycled this pack through probe initialisation sequences and sustained sensor logging loads. The BMS held without tripping during the current spike at probe power-up, and cell voltage stayed stable under continuous measurement draw.
• Calibration cycle before first field use: After installing this pack, run a full calibration cycle through the instrument menu before taking it into the field. The HDSM and HDTM map battery state during calibration — skipping this step causes premature low-battery warnings during your first measurement session, even with a fully charged pack.

BMS lockout after the HDSM sat unused in a carry case for months

Ni-MH cells self-discharge over time, and a pack stored at low state of charge for several months can drop below the BMS recovery threshold. When that happens, the instrument either shows no battery indicator or refuses to power on entirely — not because the pack is dead, but because the BMS has entered a protective sleep state. Place the pack in a standalone Ni-MH charger first rather than charging through the instrument. Once voltage climbs back above approximately 6.0V, the BMS resets and the instrument will recognise the pack normally.

Readings resetting or logging gaps during a sustained measurement session

This happens when cell voltage sags under sustained sensor load — the instrument interprets the drop as a low-battery event and resets the active measurement rather than logging a gap. It is not a firmware issue. The root cause is typically a pack that has been shallow-cycled repeatedly without a full charge, compressing the usable voltage window. Charge the pack fully before any extended logging session and confirm the instrument reports a complete charge state before you start — do not start from a partial charge.