Ping 360, problem with decode sensor log

Blue Robotics Products Ping Sonar Devices
1

Hi,

I have a ping 360 sonar which I have been testing lately and run into some problems while trying to decode the log files. First, I did not update the firmware (original firmware from around 2020) and had some connection issues with pingviewer. After I updated to the latest firmware these connection issues were solved and the scanning speed improved. Anyhow, when I try to replay the log files with pingviewer the replay is lagging a lot. If I replay the data logged before firmware update the replay plays smoothly (apart from the times there was connection issues during the logging).

I have used the python code in

“ping-viewer/examples/decode_sensor_binary_log.py at master · bluerobotics/ping-viewer · GitHub”

to dig into the log files and it works with the data logged with the old firmware, but the data logged with the latest firmware does not open. I get error:

“AttributeError: ‘PingMessage’ object has no attribute ‘mode’”

Has some else had any problems decoding ping360 log files after the firmware update?

For information, I am running the ping 360 sonar with a win 11 laptop directly.

2

Hi @Ilkka,

To clarify:

  1. You are running Ping Viewer 2.6.0, on a Windows 11 laptop

  2. Your Ping360 firmware has been recently updated to v3.3.8

  3. In Ping Viewer, you are trying to replay log files, which works well with files created before the firmware update, but is jerky/laggy with new files?

    • I’m not sure we’ve tested the replay functionality with the new firmware. The faster scanning speed is from a new protocol message with lower communication overheads, but it’s possible the replay functionality is having some issues with it. I’ve raised this internally to see if someone knows more.

  4. In Python, you are trying to decode log files, which works well with files created before the firmware update, but is failing with new files?

    • That decoding script hasn’t been tested with files from the new firmware, so while I’d expect it to work it’s possible there are some problems. I’m away from my testing setup at the moment, so I won’t be able to replicate your issue until at least next week, but if you’re able to post a short log file from the new firmware then I can potentially try to look into it sooner.
    • It could also be helpful if you can post the full error traceback, rather than just the summary message, along with the command you’re using to run the file, and/or any modifications / custom code you’re using to try to process the log file.