Hi guys,
Has anyone encounted Ping360 Scanning Stopped after about 10 seconds each run, about 1 and 3/4 circles?
Ping360 with default USB configuration, no alternations, windows OS.
Testing Ping 360 Sonar direct to PC USB port via USB connection: running all good in PingViewer. So hardware is good.
Ping360 into Rpi 3B (Ardusub-Raspbian) via USB port, then Rpi direct to PC ETH port via an ethernet cable (no tether whatsoever): PingViewer detects and connects to Ping360, everything seems great until it stops after about 10 seconds (1 and 3/4 circles). This happens each time with a new manual connection.
IP setting: UDP connection, 192.168.2.2, port 9092
I read some topics in this block. Not sure if I need to change the Ping360 IP to a static IP such as 192.168.2.4, would that help ? OR shall I run some scrip in Rpi3B?
Or shall I alter the Ping360 from USB to Ethernet configuration (I do not want to open the sonar if necessary)
Great thanks if anyone can help or solved the same issue before.
Sorry for the issue. Can you share what version of BlueOS you’re running?
How are you powering the ping 360 when testing with your computer vs connected to the ROV?
In BlueOS under ping sonar devices is the ping 360 listed?
Have you updated the firmware of the ping 360?
The “fake”ping device is strange, but likely not having causing any issues . With the ping 360 connected via USB, the IP address is that of the Pi, which forwards the connection- changing the IP would cause things not to work at all!
Feel free to give the beta ping viewer next extension a try! Switching to Ethernet connection on the device would require an Ethernet switch in your vehicle…
I’m running the old ardusub-raspbian on my Rpi instead of BlueOS.
I was using a 4S Li-ion battery (15.9V) to power Ping360.
This Ping360 unit was just purchased in March, Do I have to update its firmware in this case? If so I will update it.
So with the images I attached, did I set the IP and port number correct for the Ping360 (192.168.2.2:9092)?
I am not able to change it to Ethernet connection now, because I did not purchase an Ethernet switch…
Blue Robotics moved on from Companion OS quite some time ago, so I’m afraid we can’t really provide support for such legacy code!
Please update your system and try again- the firmware your device came with is likely having issues with the legacy architecture! It’s quite easy to do - see the guide here.
So Ardusub-companion does not fully support Ping360 Sonar now?
If I switch to BlueOS, can I still use QGC as my surface ground control or do I have to stick on Cockpit?
We’ve not tested newer Ping360 firmware with CompanionOS, so we just don’t know if there would be an issue there! The service running in the system does not indicate it is working…
BlueOS supports QGC, of course! We’ve yet to update our BlueROV2 guides to use Cockpit, so it is still the officially supported GCS.
Long time ago I had similar issue;
That time Rapberry used wifi and Ethernet same time, but there was no Wifi net.
By disabling wifi in the Raspberry OS I made it work.
I disabled wifi on Rpi using #sudo ifconfig wlan0 down# and confirmed with ifconfig that wifi is not listed.
But Ping360 still stops like last Friday, about 10 seconds of scanning.
How did you diable wifi back then? Anything else you recommend I should do in my case?
BlueOS flashed onto my Rpi3B and Ping360 is scanning continuously now!
New Issue: I am using Raspberry Camera V2 NoIR and found the video stream has a noticeable reddish tint, while with the old companion OS, the video color on QGC is just right from the same camera.
@AliceShanghai You’ve chosen a camera with a lens that does not have an IR-blocking filter. Whatever IR light is in the scene is leaking into the R,G, and B pixels of the camera. You won’t get proper colors when the camera is out of the water.
When the camera is in the water, there won’t be any IR light, so the colors should be OK.
Thanks Walt. I will try the underwater video later.
But I am just wondering, if there is an auto-adjusting mode or auto-balance setting that i can use so the video stream looks proper both in water and in air?
Because when I use this Rpi V2 NoIR camera with the old companion (same hardware, just a different SD card in Rpi3B), the video looks quite balanced with RGB, a little bit reddish but not as obvious as the screen shot i attached above.
As @wholm points out, that red color is due to the lack of IR filter. While you can adjust color settings on the video streams page for that video device, it does not happen automatically and may need more adjustment once in the water?
I’d guess that you’re now receiving the video at higher resolution and frame rate than you may have been with Companion OS? That could make differences more noticeable? It’s also very strange if there is a difference to the colors between Cockpit and QGC, currently. Maybe Companion OS had some video color adjustments in effect that I’m not aware of, it has been many many years since I used it.
Now that you’re on BlueOS and Cockpit, checkout the PingViewer Next extension - once installed, you can add a ping360 widget to Cockpit and not need to have PingViewer open at the same time!
That legacy camera config timeous is nothing to worry about! I believe it is trying to find a CSI camera (connected via ribbon cable) and failing?
BlueOS flashed onto my Rpi3B and Ping360 is scanning continuously now!
