This page shares issues that users have run into and how they were resolved. Hopefully this will help to solves issues for others.
Vehicle flips itself over
Vehicle turns or moves even when not controlled to do so.
Please check RCx_TRIM parameters to make sure that all trims are set to 1500, with the exception of RC3_TRIM, which should be set to 1100.
Motors spin as soon as the vehicle is armed.
Make sure that the vehicle is in Manual mode.
The flight controller attempts to stabilize the vehicle's attitude so that it is perfectly level. If the vehicle's attitude is off from level, even a fraction of a degree, the flight controller will spin the motors in an attempt to correct the error. If the vehicle is sitting on land, the error will not change, and the flight controller will spin the motors faster and faster as it tries harder and harder to correct the error. Testing the vehicle on land should be done in MANUAL mode, which just passes pilot inputs to the motors with no stabilization.
No Telemetry (No Pixhawk Connection)
Make sure the companion computer is powered with a supply that is capable of delivering at least 2A.
Make sure that the QGroundControl is configured to automatically connect to UDP links. Click on the 'Q' icon in the upper left to view the Application Settings. Click on the 'General Settings' tab. In the options for 'Autoconnect to:', make sure the UDP option is checked.
Check Your Network
You should be able to ping the companion computer from the surface computer. On the surface computer's command line enter:
If you do not get a ping response, then something is wrong with the network communication between the surface computer and the companion computer.
Check your network settings. The surface computer should have a static IP address of 192.168.2.1. You may have to adjust your firewall settings to allow QGrouncControl access to the network.
Check the activity lights on the Raspberry Pi ethernet Jack. The lights should be on or blinking.
If the lights are not on, make sure that you are using a network patch cable, not a crossover cable. Look closely at the color of the wires inside connectors on either end of the network cable, the order of the wires should be the same on both ends of the cable.
If your network is configured correctly, but you still have no telemetry, we need to make sure that MAVProxy is running on the companion computer and that the Pixhawk and the Raspberry Pi are communicating. Please note that the Pixhawk must be connected to the companion computer before the companion computer is powered on. The MAVProxy process is started at boot, and if the Pixhawk is not connected at this point the MAVProxy process will exit until the companion computer is rebooted.
Check that mavproxy is running on the pi. Log into the Pi via ssh or PuTTY, and type
screen -r mavproxy
Mavproxy and the Pixhawk are working correctly if the output contains something like this:
APM: ArduSub V3.4 (422c10cf) APM: PX4: 96a4c296 NuttX: 580f5354 APM: Frame: ROV_VECTORED_FRAME APM: PX4v2 0048003B 3135510C 35333436 Received 608 parameters Saved 608 parameters to mav.parm
To return to the command line and keep the mavproxy process running, hit control+a then type 'd' (to detach).
If you do not see the above lines in the output, or if you see something like this:
There is no screen to be resumed matching mavproxy.
then there was an error starting MAVProxy. You can restart the MAVProxy process by typing:
Make sure that the Pixhawk is plugged into the companion computer (Raspberry Pi) with a micro USB cable. Make sure that the USB cable has data lines, some USB cables only provide power and will not allow communication. You can connect the Pixhawk to the surface computer directly with the USB cable to verify that the USB cable works.
If you still do not have telemetry after all of these steps, please reboot the surface computer and the companion computer, and try again. If it is still not working after rebooting, please leave a comment on discuss.bluerobotics.com.
If you do not have telemetry, please troubleshoot that first according to the above instructions.
If you have telemetry, but no video, make sure the video settings are correct in QGroundControl. The video settings are found in the General tab of the Application Settings (Q icon) view. The video source should be set to UDP video, and the port should be 5600. These are the default settings. If you change these settings, you will need to close and re-launch QGroundControl.
If the video settings are correct, and there are no errors displayed in the Console tab of the Application Settings in QGC, the most likely cause of a missing video stream is a faulty physical connection with the camera ribbon cable. Disconnect power to the ROV/Raspberry Pi and reseat the ribbon cable on both ends, ensuring that the contact side of the cable is oriented correctly. The contacts should face towards the board on the camera module, and towards the HDMI connector on the Raspberry Pi.
If you have checked all of the above and still don't have a video stream, you can check the video streaming process for errors. Log into the Raspberry Pi (the default ip address of the Raspberry Pi is 192.168.2.2) via SSH or PuTTY using the username 'pi' and the password 'companion'. After you have logged and enter the following command into the Raspberry Pi command line:
screen -r video
If the camera is working and the video stream is running, the output should end in something like this:
Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock
To return to the command line and keep the streaming process running, hit control+a then type 'd' (to detach).
If the video stream isn't running the output of the
screen command will be:
There is no screen to be resumed matching video.
You can relaunch the video streaming process by entering:
If the output of this command contains something like this:
mmal: Failed to create camera component
Then the camera isn't working. Double check the camera ribbon cable, and try running
If you are using a Windows computer:
- Disable/re-enable the network interface
Poor video streaming performance
The video stream should have about 200ms delay, just barely noticeable. There are many factors that could cause lag, low framerate, and pixelation/tearing in the video.
Here are some tips for troubleshooting poor video performance:
- Bandwidth - Test the bandwidth at 192.168.2.2:2770/network. The maximum theoretical bandwidth on a Raspberry Pi 3 is 100Mbps, if the bandwidth tests achieve greater than 70Mbps, it is a very good connection. Systems with bandwidths below 40Mbps should be diagnosed for issues.
- Try another cable - Not all cables are created equal; some are really junk.
- Update Software - Use the latest software to make sure you are getting the best performance.
- Companion computer power supply - Most companion computers require a power supply capable of providing 5V at 2A. Smaller/weaker power supplies can severely affect performance of the companion computer.
- Tether interface power supply - If you are using a tether interface board, make sure it has a solid power supply. Some laptop USB ports cannot provide enough power for the tether interface board to perform optimally. Try using a portable USB battery charger.
- Tether interface connections - Make sure that all connections are well-seated and tight.
- System resources - Open the system resource monitor and look at how much CPU and RAM your computer is using. Try closing other programs like anti-virus and screen recorders to make more system resources available to programs used to operate the vehicle.
If you are using a Raspberry Pi camera:
- Delete the '--intra 1' setting at 192.168.2.2:2770/camera and restart the camera.
- Update the companion computer software at 192.168.2.2:2770/system.
If you are using a Windows computer:
- Upgrade to Windows 10!
Try these three suggestions by Bo Koppel:
When using original power supply that supply laptop (but not charge at the same time) there is something probably in BIOS that slow down graphic card to save energy. That makes processor do some of the graphics calculations. (And actually consume even more energy!) Solution: Go on battery or use a large powersupply (in our case 120W) How to quick check if this is the problem: pull out powersupply, if this is the case, latency disappear in two seconds.
Nvidia powerful graphic cards use an engine called PhysX for games etc. It seams QGC does not use that. Also QGC works default on motherboard graphic card, not on the more powerful Nvidia extension card. Solution: In Nvidias “control panel” select under “Programs” QGC so Nvidia forces QGC to use Nvidia card. Some graphic cards also needs tweeking in Nvidia 3D setup (same place as above line)
Real crazy in a few computers: Switch system fonts from 125% size to 100% (Right click desktop, “adjust screen” then “monitor” translated from Swedish OS) Check the 100% tickbox instead of 125% Log out and log in again, fixed….
Camera does not tilt
The output servo rail on the Pixhawk requires a separate 5V power supply. The power module and USB power inputs on the Pixhawk will not power the servo rail. Make sure you have a 5V input on the servo rail via an ESC BEC or standalone BEC.
Check that input/output channels are configured for camera tilt.
Check that joystick buttons have been assigned to camera tilt functions.
"No io thread heartbeat" message constantly appears.
This message indicates that the APM io thread has stopped running. The most likely cause is a corrupted filesystem on the micro SD card. Remove the card from the pixhawk, and format it as FAT32. If the error persists, you will need to replace the SD card, or disable dataflash log files by setting the LOG_BACKEND_TYPE parameter to None (0).
Compass heading drifts while the vehicle is stationary
The compass inside of the ROV is very sensitive and will be affected by large iron/steel structures, including rebar in concrete. You will get the best compass calibration outside, away from large structures and concrete. It is possible to calibrate inside, you may need to increase the value of the COMPASS_OFS_MAX parameter before you get a passing calibration. Note that the compass will always be affected by ferrous structures because they distort Earth's magnetic field, however the heading should remain stationary (maybe incorrect) while the vehicle is stationary in any case.
Perform these steps to recalibrate the compass:
- Power on the vehicle and wait 10 minutes to ensure the sensors are warmed up.
- Make sure that the INS_GYR_CAL parameter value is set to 'Never'.
- Perform an accelerometer calibration.
- Perform a compass calibration.
- Reboot the vehicle. The compass should be still.
We're always trying to make our documentation, instructions, software, and user experience better. If you're having an issue with anything, please report it so that we can address it as soon as possible! Here's where to do that depending on what's wrong:
- ArduSub Issues: For anything related to the ArduSub software that runs on the Pixhawk and controls the ROV, reports issues on the ArduSub Github Issues Page. If you're unsure where your issue should be posted, you can report it here.
- QGroundControl Issues: For anything related to the QGroundControl software, joystick setup, video streaming, etc., please report an issue on the QGroundControl Github Issues Page.
- Documentation: For anything related to the documentation and instructions here, please report an issue on the ArduSub Documentation Github Issues Page.
Sponsored by Blue Robotics. Code released under the GPLv3 License. Documentation released under the CC-NC-SA 4.0.
Submit a Documentation GitHub Issue here to report any errors, suggestions, or missing information in this documentation.
Submit an ArduSub GitHub Issue here to report issues with the ArduSub software.