# Cockpit and Blue OS error with navigator board **URL:** \ **Category:** General Discussion\ **Tags:** thruster, blueos, navigator\ **Created:** [November 11, 2025, 3:55pm UTC](https://discuss.bluerobotics.com/t/cockpit-and-blue-os-error-with-navigator-board/21993 "2025-11-11T15:55:59Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kingcoolance](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kingcoolance](https://discuss.bluerobotics.com/u/kingcoolance)\ **Post date:** [November 11, 2025, 3:55pm UTC](https://discuss.bluerobotics.com/t/cockpit-and-blue-os-error-with-navigator-board/21993/1 "2025-11-11T15:55:59Z")
Hey guys, We recently bought the prebuilt enclosure to incoporate into our ROV, and we have been simply surface testing it with our controller and 6 thrusters, just via an ethernet cable. Our setup so far is basically just connecting computer ethernet to the rasp port (removing the fathom ethernet connection for now) and connecting 14 V power to the whole system. This powers the whole system correctly and the navigator turns on no issues. Last week, we tested it for the first time with 6 thrusters connected to the escs, by installing cockpit and connecting a controller to it. In this test, it worked to control the thrusters, and we could see camera footage very clearly and all the system stats looked right. However, when we tested it this week, the blue os connection still shows the system stats and the camera video, but we are unable to arm the thrusters and it brings up an error about being unable to send mav updates. The setup is all the same, with using cockpit and same controller, but it does not work to arm it. We also tested PWM outputs directly from blueos, but it still did not control the thrusters. We tried rebooting the software, turning on and off, and simple trouble shooting methods, but none of them worked. Do you guys have any possible solutions or ideas? ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [November 11, 2025, 5:49pm UTC](https://discuss.bluerobotics.com/t/cockpit-and-blue-os-error-with-navigator-board/21993/2 "2025-11-11T17:49:03Z")
Hi @kingcoolance - I received your direct message, but am answering here for others to benefit. From the error you receive, it is likely the system is refusing to arm due to a failsafe check failing. You could disable these failsafe checks, or take steps to resolve the issue. Checkout the [ARMING\_CHECK](https://ardupilot.org/sub/docs/parameters-Sub-stable-V4.1.2.html#arming-check-arm-checks-to-perform-bitmask) parameter! ---
**Author:** ![kingcoolance](https://avatars.discourse-cdn.com/v4/letter/k/958977/32.png) [@kingcoolance](https://discuss.bluerobotics.com/u/kingcoolance)\ **Post date:** [November 17, 2025, 5:17pm UTC](https://discuss.bluerobotics.com/t/cockpit-and-blue-os-error-with-navigator-board/21993/3 "2025-11-17T17:17:36Z")
What part of blue os can i check these ardupilot failsafe parameters? ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [November 17, 2025, 6:19pm UTC](https://discuss.bluerobotics.com/t/cockpit-and-blue-os-error-with-navigator-board/21993/4 "2025-11-17T18:19:32Z")
The [autopilot parameters](https://blueos.cloud/docs/stable/usage/advanced/#autopilot-parameters) page is where the arming checks are currently configured: ![Screenshot 2025-11-18 at 2.11.57 am](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/3X/0/b/0b14f211f8cf717b139dc49f287d5c92e7be75bd.png) There’s a nicer visual overview of _failsafe_ behaviours [in the Vehicle Setup / Configure / Failsafes page](https://blueos.cloud/docs/stable/usage/advanced/#failsafes), but note that arming checks occur _before_ arming, whereas failsafes occur during operation (and may forcibly shift the autopilot to a different state, like a particular flight mode, or disarmed, depending on user configuration). > [@kingcoolance](#): > > it brings up an error about being unable to send mav updates. Curious, I don’t believe I’ve come across that before. > [@kingcoolance](#): > > We also tested PWM outputs directly from blueos, but it still did not control the thrusters. This still requires arming, so if arming is failing then it’s expected not to work.