We can't send data to Navigator

Blue Robotics Software ArduSub
1

Hi, We are suddenly facing an issue that started yesterday.

I abosoving issue was, We cannot send data to the navigator board and are also having trouble manual mode arming it. “The vehicle is not responding to the commands”, and we have lost manual control. I have attached a screenshot for your reference.

image
image1365×767 91.2 KB

image
image1365×767 120 KB

we tried to calibrate at that time we faced an issue myGCS: 255 heart beat the lost issue.

image
image1365×767 91.5 KB

We were able to upload firmware and change it.

setup is Blueos 1.3.1 Ardusub 4.5.0

Thank you

2

Hi @Sakthivelj -
It seems the ArduSub process is having issues. Some things to check:

  1. Network setup correctly - can you ping vehicle at 192.168.2.2 / reach BlueoOS web interface?
  2. Has current/voltage sensor been configured? It doesn’t seem likely the system would function with 0.44 V supplied as shown in your screenshot!
  3. Have you loaded default parameters? The artificial horizon showing the vehicle rolled over may indicate the autopilot_orientation parameter is incorrectly set.
  4. Have you installed Navigator WebAssistant BlueOS extension or any other software that may interfere with ArduSub? Is this a new vehicle or was it previously working?

Sharing BlueOS system logs downloaded from the gear icon in the lower left would let us troubleshoot with you.

3

Hi @tony-white, thank you for quick turnaround,

Yes, I am able to accessing web page blueOS is loading. I am able change change firmware too using web interface…

Voltage/current sensor not integrated.

For testing I took it outside so it’s showing 90 degree like this this not a issue.

This not new vechile, I have working with this continuosly over week, yesterday suddenly it’s coming.

Just now I have tested with another raspberry Pi and navigation the issue is same.

I hope this issue not related to firmware, Raspberry and navigator. After restart loading on QGC I noticed it’s showing all the parameters are not loading some think like that. I try to reproduce but not comming remaining the issue same.

Sure I will share the logs.

Thanks

4

Hi @tony-white,

I have attached the log and a screenshot for your reference. This issue is not loading the full parameters. Please check it and share your comments.
system_logs.zip (2.9 MB)
logs (1).zip (13.8 MB)

Screenshot 2025-01-08 211243
Screenshot 2025-01-08 2112431365×767 119 KB

Screenshot 2025-01-08 212840
Screenshot 2025-01-08 2128401365×767 102 KB

No extensions are running in BlueOS; only the Major_tom extension, which comes with BlueOS, is active. I disabled it, but the issue remains the same.

Thanks

5

Hi @tony-white, I just tried using the Pixhawk 2.4.8 and encountered the same issue you mentioned.

Could you please suggest some steps or solutions to resolve this problem?

Thank you

6

Hi @tony-white,

I wanted to provide an update on my issue. I was able to resolve it by using Mission Planner, where everything worked perfectly. After that, I switched back to QGroundControl (QGC), and it started functioning as expected.

I’m still facing a “Lost manual control” issue, but I can now arm it in manual mode,

Here’s what I’ve observed:

  • The parameter file wasn’t fully loading in QGC (the green loading bar at the top wasn’t complete).
  • When using Mission Planner, everything worked fine, and I could arm it in manual mode without any issues.
  • Afterward, work in QGC.

Do you have any insights into what might be causing this behavior? I’d greatly appreciate your advice or suggestions.

Thank you.

7

Hi @Sakthivelj -
It sounds like you’re even having general connectivity issues, or there is an issue with the Mavlink Router being used in BlueOS. Can you verify that Mavlink Router is selected in Pirate Mode under Mavlink Endpoints?

Updating to beta 1.4 version 8 will give you the option to select Mavlink Server - please do so and see if that improves things?

Also, confirm that the link light is on and steady, and share results from a network speed test.

8

Hi @tony-white, I have tried it with beta 1.4 version 8 the previous issue was back.

“Error: No acknowledgment received for command ‘MAV_CMD_COMPONENT_ARM_DISARM’ before timeout (5s).”

I have noticed that the compass is unstable,

and

I went back to Blueos old version 1.1.1 and loaded firmware 4.1.1 and faced “Error msg: Vehicle 1 did not respond to request to parameters” error

I suspect this might be an issue with the Raspberry Pi since I experienced the same problem when connecting the Pixhawk. please check the image below.

Screenshot 2025-01-10 235947
Screenshot 2025-01-10 2359471365×766 125 KB

Could you please suggest a way to resolve this issue?

Thanks

9

Hi @Sakthivelj
Ah hah!

since I experienced the same problem when connecting the Pixhawk.

This would suggest your pixhawk is nonfunctional, not the Raspberry Pi! After all, if you can reach BlueOS your Raspberry Pi is just fine, but if you plug the Pixhawk directly into your computer and QGC cannot talk to it, it is dead :cry:

It can be difficult to source the old pixhawk units, so if you’re not able to upgrade to a Navigator contact support and we may be able to connect you with limited reserve stock.

1 Like
10

Hi @tony-white,

The issue fixed itself on its own. After uninstalling and completely deleting the QGC folder from both the program files and app data, I reinstalled QGC, and it began functioning normally.

Since the issue couldn’t be replicated, I’m not entirely certain that this is a resolved error.

I truly appreciate your valuable support on this issue. Your assistance makes a significant difference.

Thanks

1 Like