I noticed a bug in blue OS where it replicates the ping 360 in the menus
see the attached photo
Hi @CUIS, thanks for sharing this - this isn’t a problem we’ve come across before 
A few questions:
- Do you have any additional context you can provide?
- is your Ping360 connected via USB or ethernet?
- which BlueOS version are you using?
- can you provide system logs?
- Are you able to consistently reproduce this issue?
- if so, can you provide the steps to do so?
- Would you be willing to submit that information as a bug report in our GitHub Issues?
- Do you have any additional context you can provide?
- is your Ping360 connected via USB or ethernet?Its connected using ethernet
- which BlueOS version are you using?using blue OS 1.1
- can you provide system logs?ill I’ll get it to you in a bit
- Are you able to consistently reproduce this issue?yes it’s persistent ever since the vehicle setup menu was modernized even with a clean install of blueOS
- if so, can you provide the steps to do so?turn on the rov open vehicle setup and wait about an hour then open vehicle setup again
- Would you be willing to submit that information as a bug report in our GitHub Issues? I can try
system_logs.zip (4.3 MB)
the Issue still persists even with a clean install
the Ping360 is connected via ethernet
and happens all the time even with the latest BlueOS version 1.2.4
I have attached the system Log
Thanks for sending these through
I just took a look and it seems the Cerulean DVL is getting detected as a Ping360 somehow:
2024-04-21 01:41:40.596 | INFO | ping360_ethernet_prober:find_ping360_ethernet:65 - Data received: SONAR DVL+0+1+1+0+0
Cerulean Sonar
MAC Address:-00-80-E1-3E-24-25
IP Address:-192.168.2.3
Port:-50000
We’ll need to investigate a bit more to determine whether that’s an issue with how the DVL is presenting itself, or if the BlueOS ping service is unreasonably broad in how it’s categorising Ping360 devices.
I’m not sure how difficult this will be to track down, but I’ve raised an issue about it to help track the progress of resolving it.
@CUIS I’ve made a potential fix, but haven’t been able to test it because the issue isn’t happening on my system. Given the issue seems to be quite repeatable for you, could you try testing my image with the proposed fix?
You should be able to install it from the BlueOS Version page, by
- changing the remote repository to
esalexander/blueos-core, and - installing the
fix-ethernet-ping-registrationimage
@CUIS @EliotBR I think we have the same occurring on a Clients ROV, also with a cerulean dvl installed. I should be able to test this fix early next week. Have you confirmed this as a working fix?
That would be helpful - thanks
Nope - I’m still waiting on someone to test.
Hi Eliot,
I did install this and it did appear to fix the duplication. It didn’t solve our main issue which remained even with the ROV separated from the ping360 - that’s in another thread.
1 Like
Hi Eliot,
this appears to have fixed the issue, will this updated be pushed to the latest version of blue OS?
1 Like
The pull request has been merged, and is already included in BlueOS-1.3.0-beta.4, so will be in a stable release once 1.3.0 has stabilised
I don’t expect it will get back-ported to a 1.2 patch release, because the fix is predominantly for an interface issue.
If I’m remembering correctly @mattcmgb’s actual issue ended up being related to a dodgy cable or connector to the ethernet switch that was causing the device to repeatedly reconnect and be registered as a new device (which the infinite sensors in the interface was just a symptom of), so it may be worth checking your hardware to see whether your connections are all stable, to avoid related issues in future.
I’ve raised an issue with some ideas that might help notify of such underlying issues in future, but I’m not sure if/when that will get implemented.