Failed to initialize

Dear,

Every time I try to run the sonar I get the error “Failed to initialize Ping!”. I also tried to run in the ping viewer software but it is unable to recognize the device. Although the sonar is not initialized, the pc recognizes it in the ttyUSB0 port.

Do you know how can I fix it? How to restart/reboot the sonar?

def sonar_acquisition(device='/dev/ttyUSB0'):

    #TODO: ADICIONAR TRATATIVA DE ERRO PARA SELECIONAR PORTA

    "Identify and initialize sonar"

    device = f"{device}"  # USB port
    baudrate = 115200

    # Make a new Ping
    myping = Ping1D()

    if device is not None:
        myping.connect_serial(device, baudrate)
    elif device is None:
        myping.connect_serial("/dev/ttyUSB1", baudrate)

    if myping.initialize() is False:
        print("Failed to initialize Ping!")
        exit(1)

    return myping
[...]
self.myping = sonar_acquisition()

first = list(self.myping.get_profile()["profile_data"])

[..]

Regards,
Mariana Flavio.

Hi @mlflavio,

Can you try going through our Ping Viewer troubleshooting steps? If it’s detected by the computer, and the drivers are installed, but Ping Viewer can’t recognise it then it’s perhaps worth attempting a device recovery.

If you’re unable to get the sonar connected to Ping Viewer then you’ll likely need to contact our support email (support@bluerobotics.com), with a link to this thread for some context, and your order number (/rough order date), and try to sort things out from there.

1 Like

Thanks for your reply, Eliot.

Just to confirm, if none of the troubleshooting steps work I still can apply for a warranty. Right?

The troubleshooting steps are there to help find and fix issues where it’s possible to do so, but if a device is actually broken then there’s no guarantee it’s easily fixable.

If you’ve received a broken product, or it has stopped working in an unexpectedly short timeframe without being misused, then that’s the kind of scenario where you should contact support to discuss getting a warranty replacement :slight_smile:

Hi Eliot, I am experiencing similar but not quite the same issue.

Today, I brought my boat out to a wetland to do a survey, and it worked for about 30 minutes. Then I took the boat out and bring it to another section of the wetland to continue my survey. When I turned the boat on at the new location, my boat cannot detect Ping2 sonar device anymore. I checked everything, my BlusOS is the latest stable one (1.3.1 I guess), and my ardupilot is the latest stable one as well. I also double checked that all my extensions are the up to date versions as well.

After tried to reboot a few times, I gave up and went to do other works at the wetland. At the end of the day (about 2 hours later I identified the issue), I turned the boat back on and I was able to detect Ping2 sonar again… This is 2nd time this kind of issue happened to me.

Since I have so much experience with in-water sensors, I clearly do not think this is a software issue at all. It definitely looks like a water ingressing issue. For devices that not always seating in water and only has a tiny leakage (moisture getting in), it can cause this type of issues. After you get the sensor out of water for a while, the device can usually back online.

My project cannot wait, so I just ordered a new one from you website (order number: 180427). But could you please double check with the warrenty team whether I can get another replacing one? I only used the boat twice and this Ping2 sonar never worked for more than 30 minutes. I think having two of them with me all the time is good as well. My project eventually requires me to do the survey in wastewater treatment plant lagoons. In order to access some areas, the permit application usually takes 2 weeks. I really cannot affort the sensor just suddenly stopped working for a few hours.

Btw, there is no point runing any troubleshotting procedures, because when the Ping2 is in my lab, everything works perfectly fine! Thanks in advance!

Hi @Lukio -
We’ve yet to see a leak on a Ping2 sonar when properly used, especially at the extremely shallow depth it is used on a boat! The likelihood that moisture is your issue is very small. Please use the support form to report the problem with your product (including order #) - we will likely request that you open the unit to inspect it and verify communications. I would bet that the root cause of your issue is related to a flaky electrical connection!

Hi Tony,

I got the new Ping2 sonar I ordered from your store and it worked well for me.

I also opened the origianl one I had and it seems like there is no leakage in there, LED was blanking good and I did not find any bad connections in there. I am still curious about why the origianl one won’t last long.

I have another question about the minimum detection range of the Ping2 sonar. I tried in my wetland and it seems like the minimum depth it can detect is about 0.8m. Once it is lower than 0.8, the measurement won’t have any high level of confidence any more. I tried to lock the measurement range to 2m, but this does not help with anything. I am wondering whether there is any settings I can change to improve the detection for low water depth (like 0.3m). I am currently using firmware version 1.1.

Cheers,
Luke

Hi @Lukio -
Are you using the Ping sonar with a BlueBoat? Moving the sonar closer to the surface of the water ay help , or even moving it a bit deeper. Setting the maximum range to 1m may also help you measure the short distance…

Hi Tony, I did some quick test on the Ping2 yesterday. Just want to share the results with you guys to get some insights. I checked your website, the sensor’s minimum detection limit should be around 0.3m, so I set up a bucked with water level around 0.35m. The sensor is placed around 0.3m from the bottom. I used PingViewr to check the results from the sensor and it is recorded in the video below.

As you can see, although the confidence was 100%, the level measurements changed quite a lot between 0.4 and 0.6m. I tried to get the sensor deeper in the water (lower water depth expected like 0.2m), it will keep reading around 0.4 and not going any further.

I have not tried higher water level yet. The reason I am focusing on shallow water depth is mainly for the purpose of my study (a wastewater treatment lagoon with a water level between 0.2-2m).

Therefore, please let me know if you think there is anything I can do to improve the low-level measurements, any settings I might be able to change to improve its performance?

If there is no change, please let me know if you know there is any other sonar devices you know might be works well for this purpose and can be easily integrated to your boat. I like your SonarView and the Map funcitons you guys developed. Definitely do not want to lose those functions.


Hi @Lukio -
Tests in a bucket, or even a tank/pool are not going to work well! The amount of reflections will be considerable, and make it hard for the device to get a lock on a definite response. The firmware is tuned to work in mapping applications, not tank level monitoring!

To improve your shallow water measurements with the BlueBoat, try reducing the survey speed to 0.5m/s (waypoint speed parameter.) Also, use PingViewer to set the lowest gain and manually specify a 1 or 2m maximum range, and minimum ping rate.
What type of bottom is in the body of water you’re trying to map? If it is concrete, this is likely providing a very strong return vs. sediment…