Good morning.
We are having communication problems (COMM LOST) with the USV.
My USV has a suitcase on it with a PC. There is a Wi-Fi router that provides internet to the PC via cable, and to the Raspberry Pi via Wi-Fi. Since when Comm Lost happens in QGroundControl we remain connected to the PC via remote desktop, I would like to know if it is possible through the LOGs to find out whether we really lost communication because the Raspberry Pi restarted (which already happened to us with a defective ESC that was replaced) or if it is really because the Wi-Fi is being lost. If it can be seen in the LOGs, which parameters should be looked at?
Thank you.
Hi @Pulsar79 -
I think we need a bit more information to provide useful feedback. Is your USV custom, or what model is it?
If I understand correctly, you’re using a Raspberry Pi with Navigator to host your autopilot? It reaches your control computer by connecting to a WiFi router on the vessel- does your control computer connect to the same WiFi network as the Pi then?
How have you configure a BlueOS Mavlink Endpoint to point at your control computer? Is connecting the pi to the WiFi router on the vessel via ethernet cable not an option?
The .BIN logs on the vehicle capture autopilot telemetry, things like GPS location and orientation, and messages that would be sent to a GCS - regardless of connection status. The BlueOS logs (assuming you’re using BlueOS) may capture some elements of networking? What type of WiFi hardware are you using? Mikrotik?
My USV is like the one you sell (BlueBoat), but a suitcase has been added on top that carries a PC and has communication with a multibeam probe (I explain this in previous messages). The Raspberry with the Navigator uses BlueOS and gets internet through the wifi provided by this router:
M7000 | Router Móvil MiFi 4G LTE N300 | TP-Link España
The PC gets internet directly via cable from the router.
When we are doing the bathymetry, I have two monitors: one with QGroundControl to see the USV and give it the commands, and another monitor with remote desktop to the PC that is in the USV case. I am on land connected to another Wi-Fi that I have on land. Well, during the mission, it happens that QGroundControl several times shows “COMM LOST” but the PC in the case remains connected, so I understand that either the Wi-Fi connection between the Navigator board and the router (which is just above, less than 40 cm) is lost, or BlueOS may be restarting for whatever reason and everything is starting up again.
That is why I wanted to know if there is any message in the LOG that I can see: - ardupilot restarted, Wi-Fi connected again, etc.
Thank you for your reply.
@tony-white any help? Can you think of any message I could look at to check if the system restarts or if the Wi-Fi recovers? Thanks