-
Notifications
You must be signed in to change notification settings - Fork 23
-
Hi Evan,
Wondering about the steps necessary to go from an existing BlueROV2/ Heavy system to your system.
For example, is it as simple as: Take the R-PI in the bluerov as is, install everything necessary per your tutorials, then deploy? Does the flight controller matter? For example, older Bluerov's use the pixhawk instead of bluerobotic's navigator flight controller, does that make a difference?
Right now I have a newer heavy config bluerov, and a modified older bluerov that my lab has been slowly building up (adding structures, writing our own ros2 code). I think now is a good time to try out your system but I am trying to gauge which of our subs it would be faster to get it running on. The modified bluerov is running bare bones ubuntu 22 with our ROS2 code for thruster mapping, thrusters are in same physical config as bluerov2 (6 thruster) and we removed the pixhawk and drive the thrusters with a pwm driver on a custom PCB.
Any recommendations would be appreciated :)
Unrelated, but your new updates to the documentation looks great! Awesome work.
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 3 comments 1 reply
-
Hey Baker,
That's a good question. Here are the specs for the tests that we did with Blue installed on the BlueROV2:
- Vehicle: BlueROV2 Heavy (modified to use the Alpha arm)
- Compute: RPi 4 with the Navigator Pi hat
- OS: arm64 version of Raspbian Bullseye
- Installation: Blue was installed onboard the BlueROV2 RPi 4 using Docker. We also did some successful tests with Blue installed on a topside computer, but decided to run things on the vehicle itself.
Here are the steps that we took to get that configuration working:
- Install a clean version of Raspbian Bullseye 64-bit on the BlueROV2 RPi 4. We used this instead of the off-the-shelf 32-bit RPi image that Blue Robotics provides to avoid any issues with installing the 32-bit version of ROS 2.
- Install the arm64 BlueOS image (instructions are available here)
- Download the Blue
*-robotDocker image onto the BlueROV2 RPi; we did our tests using Iron - Setup a new MAVLink endpoint in BlueOS. Here is a relevant thread to help set that up
- Modify the MAVROS configuration file to use your new MAVLink endpoint (also described here)
If you are planning to make changes on-the-fly while doing testing, you can also clone Blue onto the BlueROV2 RPi and then mount the clone into the Blue Docker image. That is what I did while doing debugging to avoid needing to rebuild the image each time I made changes. The VSCode Remote Development extension works quite nicely for that too.
I have not tested anything with the Pixhawk. However, you should still be able to get Blue to work by running it on a companion computer. I won't make any promises there though. I've used MAVROS successfully on a companion computer with the Pixhawk on UAVs in the past, and the configuration is hypothetically similar.
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
We integrated a Reach Alpha arm onto our BlueROV2 to do some work on manipulation and were running into limitations with the tether's bandwidth when trying to run Blue + the Alpha + whole body control from the topside computer. We also saw quite a bit of latency when trying to run the Alpha from a topside computer. Unless you happen to need high rate control capabilities, are running tetherless, or have a lot of data running on the tether, you probably don't need to run Blue onboard. @rakeshv24 runs all of his work (MPC) from the topside without any issues
Beta Was this translation helpful? Give feedback.
All reactions
-
@amarburg you might find this thread relevant to our offline discussions
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1