# Ping360 auto\_transmit update

**URL:** <https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187>\
**Category:** Ping Sonar Devices\
**Tags:** ping360\
**Created:** [March 4, 2024, 7:04am UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187 "2024-03-04T07:04:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![lewisjluck](https://avatars.discourse-cdn.com/v4/letter/l/71c47a/32.png) [@lewisjluck](https://discuss.bluerobotics.com/u/lewisjluck)\
**Post date:** [March 4, 2024, 7:04am UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/1 "2024-03-04T07:04:19Z")

</div>

Hi all,

New to the forum and BlueRobotics. We have purchased two Ping360s and are interfacing to them with ping-python. I noticed the auto\_transmit option for data return from the devices is as yet unreleased and appears to have been intended but unimplemented for some time.

I was wondering if there is an update on this feature and if it has been deprioritised for now or if we can expect it to be released any time in the future?

Cheers!

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [March 4, 2024, 11:15pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/2 "2024-03-04T23:15:06Z")

</div>

Hi @lewisjluck, welcome to the forum! 🙂

> [@lewisjluck](#):
>
> I noticed the auto\_transmit option for data return from the devices is as yet unreleased and appears to have been intended but unimplemented for some time.
> 
> I was wondering if there is an update on this feature and if it has been deprioritised for now or if we can expect it to be released any time in the future?

This has indeed been in the works for quite a while. Good news is that active work on it recently resumed 🙂

In terms of what’s left to do:

- There’s an [open Pull Request to Ping Viewer](https://github.com/bluerobotics/ping-viewer/pull/1070) that will allow it to update a Ping360’s firmware
  - Without this firmware updates are only supported for the Ping(/2) Sonar devices

- A Ping360 firmware with `auto_*` support is [in the repository](https://github.com/bluerobotics/ping-firmware/tree/master/ping360) but is currently under evaluation
  - if that evaluation goes well we’ll start recommending it (hopefully some time next month, if all goes to plan), but
  - we have had a couple of previous candidates we’ve needed to pull due to firmware bugs, so we need to do some more testing internally before we’ll be comfortable suggesting others try it

---

<div class="post-metadata">

**Author:** ![lewisjluck](https://avatars.discourse-cdn.com/v4/letter/l/71c47a/32.png) [@lewisjluck](https://discuss.bluerobotics.com/u/lewisjluck)\
**Post date:** [March 10, 2024, 10:40pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/3 "2024-03-10T22:40:17Z")

</div>

Hi Eliot,  
Thanks a lot for your response.  
The team and I will start working on our solution using the manual mode and will await updates on the auto mode!

---

<div class="post-metadata">

**Author:** ![3dMB](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/3dmb/32/13905_2.png) [@3dMB](https://discuss.bluerobotics.com/u/3dMB)\
**Post date:** [June 24, 2024, 5:01pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/4 "2024-06-24T17:01:27Z")

</div>

Hi Eliot, I too am looking for the auto\_transmit option to integrate in Cerulean Sonarview.  
You say " There’s an [open Pull Request to Ping Viewer](https://github.com/bluerobotics/ping-viewer/pull/1070) that will allow it to update a Ping360’s firmware"  
Is there a version of this link that gives a method that can be understood by non-computer programmers, please?

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [June 25, 2024, 12:10am UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/5 "2024-06-25T00:10:32Z")

</div>

> [@3dMB](#):
>
> Is there a version of this link that gives a method that can be understood by non-computer programmers, please?

A Pull Request is a proposed code change (not a validated software state or release). They are sometimes accompanied by an automatic workflow that builds the software and provides the results as temporarily downloadable files, but in this case [those files have expired](https://github.com/jaxxzer/ping-viewer/actions/runs/8175637626).

Ping Viewer context aside, I asked for a status update on the new Ping360 firmware and was told our evaluation unfortunately did not go as hoped. More specifically:

> [@Lead Acoustics Design Engineer](#):
>
> … this is on hold at the moment. [The new] firmware is not ready for release, or even early testing.

---

<div class="post-metadata">

**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\
**Post date:** [August 8, 2024, 11:48pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/6 "2024-08-08T23:48:57Z")

</div>

The latest release of Cerulean SonarView supports the Ping360 in whichever mode it is capable of based on f/w version. Performance (ping rate) is higher with the auto function, but Ping360 with SonarView is a great combination either way.

Here’s the link [Release 1.10.0 · CeruleanSonar/SonarView · GitHub](https://github.com/CeruleanSonar/SonarView/releases/tag/v1.10.0)

---

<div class="post-metadata">

**Author:** ![frmunoz](https://avatars.discourse-cdn.com/v4/letter/f/9e8a1a/32.png) [@frmunoz](https://discuss.bluerobotics.com/u/frmunoz)\
**Post date:** [March 11, 2025, 3:07pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/7 "2025-03-11T15:07:48Z")

</div>

Hi, any update on when this pull request may be ready?

It seems the firmware with `auto_*` support is already confirmed and the website has [documentation on firmware update](https://docs.bluerobotics.com/ping-viewer/firmware-update/) using pingViewer, but i guess is for the version that will come from this pull request, since the current pingViewer version 2.5.1 doesn’t have the feature.

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [March 12, 2025, 12:13am UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/8 "2025-03-12T00:13:06Z")

</div>

Hi @frmunoz, welcome to the forum 🙂

You can track [the Ping Viewer pull request progress](https://github.com/bluerobotics/ping-viewer/pull/1070) if you want to, but as I understand it it’s primarily our evaluation of the new firmware functionality and robustness that’s holding back the release of a Ping Viewer version that’s capable of updating the Ping360 firmware, along with any adjustments that would be necessary to make full use of the improved features (including in complementary software like BlueOS).

> [@frmunoz](#):
>
> the website has [documentation on firmware update](https://docs.bluerobotics.com/ping-viewer/firmware-update/) using pingViewer

That documentation is only for updating the Ping Sonar firmware (so isn’t relevant to the Ping360).

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [April 18, 2025, 12:11pm UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/9 "2025-04-18T12:11:53Z")

</div>

Noting the pull request is now merged!

I’m still documenting the update process, but it’s quite similar to the Ping Sonar - if you don’t want to wait you’re welcome to try updating your Ping360 firmware using the latest Ping Viewer release, and report back if you run into any issues. Note that using the `auto_*` functionality when connected through BlueOS requires the latest stable (BlueOS \>= 1.4).

---

<div class="post-metadata">

**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\
**Post date:** [July 22, 2025, 6:10am UTC](https://discuss.bluerobotics.com/t/ping360-auto-transmit-update/16187/10 "2025-07-22T06:10:09Z")

</div>

Update: [`auto_transmit` is fully released now](https://discuss.bluerobotics.com/t/ping360-firmware-update/21023) 🙂
