Dear All, Sometimes we lose control of the ROV and the following error messages appear: ‘Warning: MYGCS: 255, heartbeat lost - Critical: Lost Manual Control’. Please find attached an image of the error messages. Does anyone have any idea of the cause? [Warning message]

Hi! First thing I would check is network bandwith from ROV to surface computer. [image] Lost Heartbeat on System Blue Robotics Software Hi @Stevenlb , On top of @Boko and @Charles ’ suggestions, some of our troubleshooting steps may be helpful. If this is still an ongoing …

Hi @Boko , we contacted the support and they suggested us the following setting that seems to work: “changing the parameter FS_PILOT_TIMEOUT to 5 in QGC” (see attached screenshot) [image]

I want to ask you, when I want to change it, it tells me that the maximum limit is 3, and I cannot put the number 5, and the error message still appears on the program. I cannot control the vehicle. Have you found a solution?

Hi @rabah - It seems like you’re not connected to the vehicle correctly, have you followed the network setup instructions ? Can you ping 192.168.2.2 successfully? If you can ping and not connect, I would recommend opening that IP address in your browser, and making sure BlueOS and the Ardupilot fi…

Hi, I’ve just upgraded a BlueROV R3 by replacing the RPi 3 and Pixhawk to a navigator and a Raspberry Pi4. As a result I’m getting the MYGCS: 255, heartbeat lost error average every 7 mins. I’ve just made the change to MAVP2P as suggested above but still getting the heartbeat lost every now and a…

Hi! While this is not the “right” fix for the issue, I’ve just opened a PR in Ardupilot to add a parameter for setting the timeout, and doubled the default value. It will eventually show like this in the (new) failsafes configuration page in BlueOS: [image]

Meanwhile, you could just disable the GCS failsafe at FS_GCS_ENABLE. The Rov should still disarm if you lose control if you keep the pilot input failsafe enabled.

I was struggling with this and a newly built ROV today as well - After trying MavP2P with no luck, I updated to 1.3 beta 7, and switched back to Mavlink Router. This combined with setting FS_GCS_ENABLE as Willian suggests, and extended inthe pilot input failsafe to 10 seconds (from 3) seems to have…

I’m unsure whether it’s related, but there are some optimisations in the latest ArduSub beta that reduce its CPU load, which should allow it to process and send messages with lower latency, and may help to reduce or avoid issues like this one. That said, the control station heartbeat and input from…

Warning: MYGCS: 255, heartbeat lost - Critical: Lost Manual Control

Blue Robotics Software QGroundControl

rabah (islaROV) February 8, 2024, 5:38pm 5

In addition to the warning message, I cannot connect to the program and it tells me that it cannot access the vehicle

Topic		Replies	Views
Lost Heartbeat on System Blue Robotics Software	12	5073	November 7, 2022
Lost Connection Issues Blue Robotics Software	6	2151	March 27, 2019
Mycgs 255 forced reset / lost manual control / heartbeat lost QGroundControl ardusub , pymavlink	1	272	March 3, 2024
Lost control during dive BlueROV2 ardusub	25	250	May 23, 2025
Sending and recieving heartbeats to BlueROV from surface computer using pymavlink Blue Robotics Software pymavlink	9	5232	May 18, 2024

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Warning: MYGCS: 255, heartbeat lost - Critical: Lost Manual Control

Community

BR Website

Software Docs

Autopilot Docs

BR and Beyond

Software

Warning: MYGCS: 255, heartbeat lost - Critical: Lost Manual Control

Related topics