# Ping1D Firmware

**URL:** <https://discuss.bluerobotics.com/t/ping1d-firmware/21511>\
**Category:** Ping Sonar Devices\
**Created:** [September 3, 2025, 5:30am UTC](https://discuss.bluerobotics.com/t/ping1d-firmware/21511 "2025-09-03T05:30:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![psupine](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/psupine/32/16137_2.png) [@psupine](https://discuss.bluerobotics.com/u/psupine)\
**Post date:** [September 3, 2025, 10:07pm UTC](https://discuss.bluerobotics.com/t/ping1d-firmware/21511/3 "2025-09-03T22:07:59Z")

</div>

Hi @Eliot

> [@Firmware Updates to Ping Sonar](https://discuss.bluerobotics.com/t/firmware-updates-to-ping-sonar/14671/2):
>
> [3.29] fixes an initialisation bug that was causing excess current draw

Ah. Definitely worth trying 3.29 then. I have now managed to avoid the rebooting problem, but the current slamming is still ugly.

–

I knew the more recent version of Ping Sonar changed the transducer to one with a narrower cone, and the FW rev numbering of “Ping2” (from the GIT pages) would seem to indicate a complete firmware rewrite. Are there are no other h/w changes that should matter to me?

The reason I’m asking these particular questions is that yesterday I was writing the discovery code where I read the protocol, device id, device version and firmware versions. But I don’t have any idea of the range of devices and versions that I could expect to support. So far it doesn’t matter because I have (N=1) devices and supporting them all is rather trivial.

Is the most recent protocol still 1.0.0 ? As far as writing the driver, can I just ignore the device and firmware version ? Can I assume that protocol changes will retain backward compatibility?

---

_[View the full topic](https://discuss.bluerobotics.com/t/ping1d-firmware/21511)._