1. Mavproxy and Position_Forward do not launch.
This issue is more often than not encountered when you have multiple QGroundControl applications running on different machines under the same network. Ensure that you do not have multiple QGroundControl running at the same time and restart the drone again.
2. Streaming enabled on RCBenchmark Tracking Lab but, the LCD screen indicates Tracking Offline.
Check that the port number is correctly entered. For reference, the port number should be 5401. Also check if the IP address has been correctly entered.
Incase the problem still persists, please close and relaunch RCbenchmark Tracking Lab to start a new session.
3. The Drone suddenly loses tracking.
This is due to the latency in the network. Ensure that the drone and the main computer are connected to a different network or any low latency network.
A way to check if your network has high latency is:
From the main computer, navigate to cmd prompt and type ping _ip_address_of_your_drone.
_Incase the delay is more than 10ms, then it is a network issue.
4. The screen not display anything at all. (Raspbian does not boot)
If your Raspberry Pi does not boot, try to connect the HDMI port to a screen and reboot. If no image is displayed an you have checked all the electrical connections, the files on your SD card are probably corrupted. In this case, you will unfortunately have to reinstall the SD card image. Follow the instructions here.
5. My Otus is not being tracked by the RCTracking Lab.
This case usually arises when the base station loses tracking of the Otus. Do the following to eliminate the issue.
- Ensure that the base station is on and that there is nothing in between the Otus and the base station.
- Ensure that the controller firmware is up-to-date on Stream VR.
- Click Steam VR > Devices > Update Firmware > Select the controller.
- If the problem still persists, please exit and re-launch the RCBenchmark Tracking Lab.
- Connect the Otus tracker dongle into a different USB port on the main computer.
6. The screen displays EKF yaw error.
This error arises when the position co-ordinates from the Otus Tracker are not reset to local axis. This causes the position mismatch with the position co-ordinates from the pixhawk which leads to wrong vision position estimate calculation leading to a EKF Yaw error.
To fix this issue, Please perform the following steps in the described order:
- Reset local axis on the RCbenchmark Tracking Lab.
- On QGroundControl, navigate to parameters then click on Tools on the top right corner and select reboot. Once Pixhawk has been rebooted, the correct co-ordinates are plugged into the vision position estimate fixing the issue.