I am working on developing a custom Mini ROV and would like to use the Nvidia Jetson Nano as my companion computer and the BlueRobotics Navigator as my autopilot board. I have been unsuccessful in installing the BlueOS-Docker on the Jetson Nano. Can I kindly have some assistance?
We don’t have a Jetson to test with, but we can help troubleshooting. What errors have you ran into?
Thanks William. I would appreciate your help.
This is the error that shows up in the terminal when we run the BlueOS-Docker installation script from github.
the issue seems to be on this line. What is the default username for the distro you are using? try using that instead.
Thanks William. I was able to fork and modify the script, however when i rerun it, i run into another error.
I think our images are armv7, which should work under a v8 host just fine…
can you try this patch?
Hello William, I was able to add your patch and run the installation script. However, BlueOS does not seem to run over the network. Any ideas why?
Here is a shot of the final messages from the terminal after the installation completed.
The following message about the hardware not being identified, is not a hard error, only a message to help us identify if there is the hardware support for the
NVIDIA Jetson Nano Developer Kit in our installation script.
Everything else should proceed as expected.
Which system are you running on your desktop computer ?
If you are running though linux, make sure that avahi is running and you can access BlueOS though the mdns address.
Try to access the board via the IP address directly on your browser, if that does not work, connect via SSH and run
docker container ls and return the output here.
Hi @BennyAmk, welcome to the forum
As an additional note on this, our Navigator is not an independent flight controller - it requires a Raspberry Pi 4 as a host computer. You could conceivably have both a Raspberry Pi 4 + Navigator and a Jetson Nano in your vehicle, but if you’re wanting a single onboard computer then you’ll either need to use a Raspberry Pi 4 instead of the Jetson Nano, or use a different flight controller board instead of the Navigator.
What do you mean by “BlueOS does not seem to run over the network”? How is your computer connected to the Jetson Nano (e.g. ethernet / local wifi network / …?), and how are you trying to interact with it (e.g. SSH, browser, etc)?
We just started deploying arm-v8 docker images, you may what to recall the install script to install the new version.
Hi @EliotBR ,
I would also be interested in the Jetson Nano/Navigator combination. It seems the navigator fits on the 40 pins of the Jetson Nano as it does on the Pi4. Could you explain why a Pi4 is needed ? Is it because of ArduPilot firmware compilation issues ? Or is it because BlueRobotics doesn’t want to support this ?
The Navigator was designed quite specifically around the hardware of the Raspberry Pi 4, to the extent that it’s not even supported on the Raspberry Pi 3. While in theory it could be electrically connected to another board with the appropriate hardware capabilities that’s not a use-case it’s been developed for or tested with, and trying to do so would likely require adjustments to the Navigator support code in both BlueOS and ArduPilot’s HAL (hardware abstraction layer), as well as a new heat sink (since the one it comes with is custom designed to interface to the Raspberry Pi 4’s ICs).
In previous internal discussions I’ve been told that
which is presumably related to how configuration is currently done.
There are many things we want to do, but don’t have sufficient resources to focus on.
I’m sure Blue Robotics would be happy if our Navigator flight controller could be used with more onboard computer options, because that’s a valuable feature to have. That said, it’s not an existing feature, and given our other priorities it’s not something we can currently allocate development resources to attempting by ourselves, and may not be practical to do even if it turns out to be technically possible. For what it’s worth, if it was already implemented and being used then I imagine we would try to provide support to maintain the functionality.