Hi, I’m having a problem. I have an image from my BlueRow2, but it says Disconnected in QGroundControl. The voltage regulator isn’t delivering the 5V to the Raspberry Pi 3 or the Phixhawk (which is connected to an “SB” input between the “RC” and “PWM 8” inputs), so I simulated a 5V voltage input to the Raspberry Pi 3, thus obtaining an image. Do you think the 5V not reaching the “SB” input of the Phixhawk is having an effect, and that’s why I’m getting that disconnected message in QGroundControl? I have an image or video, but I have no control over the thrusters and lights.
You definitely need a proper 5V supply connected to the Pi and Pixhawk for things to work! It sounds like you have an older ROV - is the Pixhawk blinking a blue light after startup?
Until QGC connects, you won’t be able to control any thrusters or outputs. If the Pixhawk is running properly, and the Pi running Companion or BlueOS is properly forwarding its telemetry, then everything should work, assuming you’ve configured your control computer’s static IP address correctly. Going through the setup guide for your generation of hardware may help you sort things out!
Yes, my device is from 2015-2016. As I mentioned, the Phixhawk emits a yellow light and appears disconnected, then sometimes turns blue, but the disconnected message on the QGC continues. I can’t activate any thrusters, lights, or see the battery charge; I can only see video. That’s why I’m wondering if replacing the voltage regulator will improve the connection, and the “Connected” message will appear on the QGC, allowing me to operate the device.
Thank you.
I applied 5V 5A of voltage to the Raspberry Pi 3 from the micro USB input, then connected the USB cable to one port on the Raspberry Pi 3 and the other micro USB cable to the Pixhawk. The Pixhawk now emits a blue light, but remains disconnected from the device. It appears disconnected in the QGC, and I have no control over the propellers and lights; I only have live video. What could it be? An image is attached.
Do you get a connection in QGC if you connect a micro-usb cable directly from the Pixhawk to your control computer? If so, you may want to flash the latest stable version of ArduSub.
Is a 4S battery connected to the system? The lights and thrusters rely on this power supply voltage directly, and with only the pi/pixhawk powered they aren’t going to do anything…
It’s also likely a good idea to upgrade from Companion, but this will require recalibrating and setting up your ROV - likely worth doing anyways if it hasn’t been used in quite some time….
Hello, the battery is connected to the system.
How do I update from Companion? I uninstalled QGC and installed the latest version from the official website.
You can find instructions to upgrade from Companion in the link provided in my previous post!
You should not have updated QGround Control - Blue Robotics recommends version 4.2.8, as linked on our Technical Reference. The newer version may work, but we’ve not tested with it at all, having developed Cockpit as a (free and open source) alternative.
I haven’t turned on the ROV for about a month.
I have the BlueRov2 connected to the umbilical cord that runs to the Surface Fathomx, and then this is connected to the laptop with a USB Type B and Type A cable, respectively, at each end. The 7-26V voltage regulator with a 5V, 6A output is failing. I’ve tested both outputs and it’s not producing any voltage. So, what I’ve done to power the Raspberry Pi 3 and the Pixhawk is: I connected a micro USB cable to the micro USB input of the Raspberry Pi 3, which is connected to a cell phone charger. From one of the USB ports on the Raspberry Pi 3, I connected a cable with a USB-A connector at one end, and the other micro USB end to the micro USB input of the Pixhawk. I also connected the battery with a 14V charge.
With all this connected, the Pixhawk flashes an amber light (when everything was fine, it emitted a blue light), in the QGC program only the live video appears and it appears “Disconnected” so I cannot operate the ROV.
As mentioned, please try connecting your Pixhawk directly to your computer running QGround Control, to see if the hardware is good - it should connect automatically.
The 5V power supply you’re powering the Pi and Pixhawk may not be providing sufficient current - is it rated for at least 3A?
Do you have both a power and link light on your Fathom-X when connected via USB? Have you configured your static IP address, and can you ping 192.168.2.2 a few minutes after powering up the Raspberry Pi?
I connected the ROV to the laptop by doing this in QGC:
If it doesn’t connect automatically, manually:
Settings, then Comm Links.
Click Add.
Name: Pixhawk USB.
Type: Serial.
Port: Select COM5.
Baud rate: 115200 (use this, the standard for ArduSub via USB).
OK, then Connect.
It worked for me. But is this feasible or acceptable? Could it cause inconvenience or problems when operating at sea in the long or short term?
Hi @Rov1 -
I assume once connected, the pixhawk seemed to respond normally? Were you able to flash it with the latest version of ArduSub? Once done, you’ll need to connect it to the Raspberry Pi in the ROV, which forwards the messages to your connected control computer via the network connection. If your Pi is having issues, reflashing your SD card with BlueOS is the best path forward to getting connected and ready to dive!
