New Product: The Navigator Flight Controller and BlueOS!

Anyone know if it’s worth upgrading to the Navigator controller?

It’s not an essential upgrade if you’re already happy with your existing flight controller, but it may still be of interest - there’s an overview of both in the Technical Reference if you want to compare. Functionally speaking the Navigator

  • is a bit more tailored to ArduSub use-cases
    • e.g. there are leak probe connectors built in
  • has a couple of extra PWM outputs
  • has more usable connectors
  • has more potential for expandability
    • we’re planning to make libraries available for accessing the sensors and connectors, so that they’re accessible from user code outside the autopilot firmware, but that hasn’t been done yet
  • does not yet support relay outputs
    • I believe there’s currently a working branch that’s being tested - it should hopefully be merged in to the main ArduSub reasonably soon
  • is more robust when updating firmware (because it’s just files on the Raspberry Pi)
  • has easier to access log files

If you do decide to upgrade,

1 Like

4 posts were split to a new topic: Navigator/BlueOS NMEA GPS not working

I did read the chart but with Blue OS and the Pixhawk the ping 1d works and I can get the data from:
http://192.168.2.2:6040/mavlink/vehicles/1/components/1/messages/RANGEFINDER/message/distance

but when i switched from the pixhawk to the navigator I could not find the rangefinder in the mavlink

That seems doubtful, since rangefinder messages are not implemented yet in BlueOS’s Ping service. Maybe you’re mixing up Pixhawk+Companion with Pixhawk+BlueOS, or perhaps you’ve got a DVL that’s set up to send rangefinder messages?