Hi There, Summary We are working with Ping360. After the recent discussion , we started using the C++ library. We are having problems that we don’t understand why. Before I describe the problems any further, I want to make it clear that Ping360 works with the Desktop client. Although I’m not certai…

Update: auto_transmit is available now :slight_smile:

Hi @incebellipipo , auto_transmit is a part of the protocol specification, but isn’t yet available in Ping360 devices. There’s a new firmware that’s been tested somewhat internally, but it’s not yet public, and there isn’t yet a publicly available firmware updater either. There was supposed to be a…

Thank you @EliotBR , that explains why auto_transmit is not working. I updated the first post that I send. I forget to mention that we are getting NACK after requesting device_data from ping360. How should we approach this problem?

[image] incebellipipo: we are getting NACK after requesting device_data from ping360. How should we approach this problem? nack messages have a nack_message field, which should indicate the cause of the nack. What message are you receiving?

That’s the message that we are receiving. [image] incebellipipo: After requesting the device_data (2300) message, the response from Ping360, A NACK message. Message[0-7]: 42 52 02 00 06 00 00 00 Message[8-15]: fc 08 Cheksum: a0 01

Parsing that, I get -------------------------------------------------- ID: 6 - general_request Header: start_1: 66 start_2: 82 payload_length: 2 message_id: 6 src_device_id: 0 dst_device_id: 0 Payload: - requested_id: 2300 Checksum: 416 check: 416 pass: True → That’s not a nack, it’s a general_…

Hmm, very interesting. Very much so much interesting. Because the message I’m sending is the message below: [image] incebellipipo: # Transducer Message[0-7]: 42 52 0e 00 29 0a 00 00 Message[8-15]: 01 01 c8 00 64 00 10 04 Message[16-23]: bc 02 e2 04 01 00 Cheksum: bc 03 I’ll con…

How are you determining what you’ve sent vs what you’ve received? That parses to -------------------------------------------------- ID: 2601 - transducer Header: start_1: 66 start_2: 82 payload_length: 14 message_id: 2601 src_device_id: 0 dst_device_id: 0 Payload: - mode: 1 - gain_setting: 1 …

I have breakpoints in the code. That’s how I see what I’m receiving and what I’m sending. I’m using a branch that is not yet merged to master. Which has an open pull request on it. Add ping360 device generation by patrickelectric · Pull Request #38 · bluerobotics/ping-cpp · GitHub I’m using Ping36…

I need to be sure that I’m getting the concept: If I want to get device_data, I should send transducer right? And then wait for the reply that is device_data? Am I mistaken? [image] EliotBR: I misunderstood, so that is incorrect - my apologies. No worries;

[image] incebellipipo: I’m pretty sure that I’m the one who’s sending the message. Definitely, ping360 is not sending that to me. I misunderstood which message it was - I’ve corrected my comment. It seems like you either aren’t getting a reply from the Ping360, or just aren’t recording it. A…

Ping360 - failed to initialize auto transmit mode

Blue Robotics Products Ping Sonar Devices

Topic		Replies	Views
Ping360 auto_transmit and firmware update Ping Sonar Devices	2	145	July 22, 2025
Ping360 auto_transmit update Ping Sonar Devices ping360	9	549	July 22, 2025
Obtaining raw data from the Ping360 using Ping-cpp Ping Sonar Devices	1	94	March 12, 2025
Getting readable data from ping360 through python Blue Robotics Software	1	1179	November 28, 2022
Ping360 not changing angle (ping-cpp) Ping Sonar Devices	5	1020	January 27, 2022

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Ping360 - failed to initialize auto transmit mode

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Ping360 - failed to initialize auto transmit mode

Related topics