Today I finally pinpointed the issue I have been having with the standalone Cockpit program. Cockpit seems to work fine up until the DVL is activated, then cockpit effectively stops working. I recorded the screen with my phone (quality is a bit crap) but does document the issue. https://youtu.be/H…

@rafael.lehmkuhl my bad - try this: system_logs.zip (8.9 MB)

Thanks @3dMB ! I can see an automatic restart on the autopilot manager happening at 14:30 UTC. Do you remember if the time matches your tests? It indicated something went wrong with the autopilot process and it tried to recover.

@rafael.lehmkuhl - no, according to the screen record, the issue happened at 10:13 BST (09:13 GMT/UTC)

@3dMB I couldn’t find any clear problem in the logs. I will ask for help from @tony-white and @williangalvani on that since they have DVLs and know better about their behavior. In the meantime, I’m adding some new debug tools in Cockpit so you can know what Cockpit is sending/receiving, and also wh…

@rafael.lehmkuhl Just a thought, how does the Pi/Navigator update time for the log? Does it set it automatically down the tether from the topside computer or does it need an internet connection? If the latter, the restart you spoke of at 14:30 could be the same event. If the former, then the time di…

Yes, there are inconsistencies regarding time sync in the way BlueOS logs the different services. I had a discussion with the team and they are working on improving that so we can make the debugs easier. Todat it only updates the clock when connected to the internet, and different services are using…

Thanks @rafael.lehmkuhl - I’ll give it a go and report back, it won’t be for a couple of weeks though.

Hi @rafael.lehmkuhl , the same happened again today with BlueOS v1.5.0beta6. I did 2 dives, both dives started with Cockpit running, then error saying “[SOMETHING I DIDNT CATCH] 255 heartbeat lost”, ROV disarmed and wouldn’t re-arm, cockpit manually quit & QGC opened, ROV carried on happily. Logs att…

Hey @3dMB ! Just to be sure, this was also with the DVL enabled, right? I received another report yesterday from a user that is having problems of heartbeat lost as well, also with a positioning system enabled. And does restarting Cockpit make it work again, or it won’t regain control? I’m trying …

Hi @rafael.lehmkuhl , Correct, the Cerulean Tracker 650 DVL was active and the dive started with geolocation being inputted into Cerulean Tracker program. I have not tried restarting cockpit in recent months, my priority is to regain control of the ROV and QGC achieves that without fail.

Cockpit stops working when DVL is active

Blue Robotics Software Cockpit

rafael.lehmkuhl (Rafael Araujo Lehmkuhl) August 5, 2026, 10:02pm 48

Linking Tony’s message here as there’s a good chance the root cause for this has been found and a build with the fix made available:

Topic		Replies	Views
MYGCS Heartbeat lost - Fiber Optic Cable Blue Robotics Vehicles cockpit	33	353	August 5, 2026
WaterLinked DVL A50 integration not working Sonar and Acoustics water-linked , dvl	42	7129	November 10, 2025
Cockpit 1.0.0 release! Cockpit news	53	4862	November 12, 2024
Water Linked DVL A50 Support Sonar and Acoustics water-linked , dvl , positioning	57	9643	August 15, 2022
Ongoing DVL-A50 issues Third Party Products	43	4668	August 24, 2023

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Cockpit stops working when DVL is active

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Cockpit stops working when DVL is active

Related topics