Ping1D not always detected in Pingviewer

[eri3t (Eric Ruiz)]

Hi! thanks for all the input! Sorry I couldn’t answer sooner, I didn’t have access to the ROV for a few days. Already upgraded to BlueOS 1.4 stable .

@tony-white

If you’re using a USB adapter, have you added this device to the serial ports available to the Autopilot under Autopilot Firmware / Serial menu? Whatever serial port you assign it to will also need to be configured under Autopilot Parameters - Serial Function should be Rangefinder, and Baud should be 115200.

I believe the device is connected to serial port 0, although I’m not sure how to configure the serial function for ‘rangefinder’ (see photo below). I’m using a Pixhawk1, and a friend mentioned that this board doesn’t provide direct access to the serial ports for configuration. I assume the port is correctly assigned, since I’ve been able to connect briefly to ping1d.

@tony-white

The Surftrack status shows that messages are not coming through fro your Ping sonar. You may want to include the maximum range from 7m to 50m, the first yellow row “Fix It” will change this parameter. The rest of the red issues should go away once your receiving data from the Ping Sonar.

As @BillyBudd suggested, I had an older version of Ping1D firmware and already updated to v3.29. I also fixed the messages from surftrak fixit, and I was able to connect to ping1d!! Nevertheless, now I’m in the same situation as before, and I don’t have input from the sonnar… The following message is appearing now: RNGFND1_TYPE is 10 (MAVLink), but there are no down-facing DISTANCE_SENSOR messages. Just after dissconecting and reconnecting the battery from the ROV, ping1d is not being detected. There are entries under /dev/ttyUSB0, and the connection is active, so Ping1D should be working properly, right?

@tony-white

From your issues with Cockpit, it sounds like you’re having network connectivity problems. In general, the BlueOS page has to load completely before the Cockpit and other extension icons will appear. You may prefer using Cockpit as a standalone application on your computer, like QGC - you can download it for your OS here.

I’m using BlueOS 1.4.0 and Cockpit 1.15.1. I tried the standalone app, but the video still had lag/occasional freezing. In this post I read about Technical Bulletin 12. Apparently I had the same issue, and the resistors seem to be in good condition (see photos below). I already clipped the camera mount, and video feed seems to be working better (no more lagging/freezing).

@tony-white

Completing a network speed test and sharing the results would be helpful.

I’ve done a bunch of tests, with very different results. My main computer is a Panasonic toughbook fz g2, and these are the results:

I also tried in my personal laptop (Lenovo Ideapad 3 15ACH6), with very inconsistent performance:

@tony-white

You may want to open the sonar and confirm that the internal LED is behaving as expected…

Regarding the LED, it’s behaving as usual (steady green light).