3 posts were merged into an existing topic: Relay integration with the navigator board
Hi @matosinho, welcome to the forum
BlueOS and Navigator are separate projects. BlueOS is open source software, and isn’t even confined to being used as part of a vehicle - we have no plans to lock down which flight controller(s) it supports. At the moment it supports at least Pixhawk, Pixhawk 4, and Navigator, with some level of support for other ArduPilot compatible flight controllers. Other controllers and firmware types may get added over time, particularly with community contributions
New features developed by Blue Robotics will generally be flight controller agnostic, and will aim to maintain compatibility with systems BlueOS is already compatible with at the time. That said, new features may get developed and tested with Navigator first, since it’s our in-house flight controller and will be going in our electronics enclosures and vehicles.
I am curious if and how this Raspberry Pi can be retrofitted into an existing ROV2?
A Raspberry Pi 4B by itself is very easy to fit in - it just replaces the existing Raspberry Pi 3B and can have all the connections the same.
If you mean putting in a Navigator as well (in place of the Pixhawk) then I’d direct you to this comment
I suspected it was a swap-out. I am somewhat cautious about swapping out the Pixhawk but if the Navigator is a better option, we’ll consider it along the Pi. Thanks.
Some slight caveats
- the RPi4 requires BlueOS (Companion won’t work), and
- I’m unsure whether it would need some kind of heat sink or fan.
- I imagine that’s not strictly required (since the RPi3 doesn’t use one, and it’d be running the same software), but we do use a heat sink with Navigator so it might be advisable (and definitely wouldn’t hurt)
I upgrades to the Navigator and everything seams to be working except the nmea injector. I also posted on the cerulean forum aswell
Another question I have is ping 1D isn’t streaming its data as a rangefinder like it did for the pick hawk is there a way to get the ping 1D data with the navigator
Are there any plans to add a can bus port (or two ) on the navigator?
How about DroneCAN (UAVCAN v0) support in BlueOS?
Glad it’s mostly working well
Which part of the NMEA injector is not working as expected?
Indeed - I’d recommend you take a look through the feature comparison table on the BlueOS release post, which mentions that for the Ping Sonar devices
Given the board has only recently been put into mass production, I don’t expect there will be major design changes in the near future. If it’s possible to accomplish via a software or firmware change in ArduSub or BlueOS to change / switch the function of an existing port then it may be an option
I don’t believe it’s something we’re working on internally, but BlueOS is designed to be extensible so that may come about via an external / community effort, particularly once we’ve stabilised the BlueOS API and released the extension system in an accessible form
3 posts were merged into an existing topic: Navigator/BlueOS NMEA GPS not working
Noting that there’s now a Navigator Retrofit Guide for people with an existing Pixhawk + Raspberry Pi 3B BlueROV2
Thanks to @DanielG_BR for all the hard work!
2 posts were merged into an existing topic: Benefits upgrading BR2 with Navigator and New Raspberry
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:
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?
A post was split to a new topic: BlueOS NMEA Injector
When will the Navigator be back in stock ?