Found a solution. I had a microhard radio running on the m500. You need to disable the microhard (eth0) with ifconfig eth0 down

@tom That was the problem! Thank you

Solution: sometimes when just binding the RC controller, the inputs aren't shown. Make sure to restart drone after rebinding. Additionally, I've found different controllers have different lever/switch inputs, so its good to use QGC to look for the responsive switches and assign the ones you want accordingly

Found the repository that stores the code here https://gitlab.com/voxl-public/old-projects/voxl-hal3-tof-cam-ros. If this link could be placed in the documentation for future viewers, that would be great

@Chad-Sweet Even with a similar board size (5x6, 55 mm), we have been struggling to account for reprojection error on both VOXL1 and VOXL2. Strangely enough, VOXL1 has been more consistent in terms of less reprojection error. Before running voxl-calibrate-camera, we used voxl-configure-extrinsics to ensure the correct extrinsic was matched to the proper drone. Is there something about how we are tuning the stereo cameras on both the VOXL1 and VOXL2 such that we create additional reprojection error? The videos of us calibrating the cameras on both VOXL boards are in the link below:

https://drive.google.com/drive/folders/1PMSIrXsTeNLAE_pXwqK6am9GpwllQx9S?usp=sharing

Hello,

When running voxl-calibrate-camera on a VOXL2 Sentinel drone, we have struggled to consistently recalibrate the cameras and usually are stuck for long periods of time trying to calibrate one or two "red box" steps of the process. We've achieved successful calibration attempts before, but we cannot do this consistently. Do you have a recommended calibration board size/setting, or a recommended backing for the calibration board? We currently have tried using an opencv 9x6 chessboard with square length of 0.02143 and 0.073 meters

The commands we are running, for each respective board size, are:
voxl-calibrate-camera stereo_front -l 9x6 -s 0.02143
voxl-calibrate-camera stereo_front -l 9x6 -s 0.073

@Vinny Will look into it, thanks!

Hello,

We recently purchased a Sentinel drone with a microhard modem (set to use 30 dbm, max 1 watt) and wanted to explore the possibility of extending the tracking camera's MIPI cable length. We initially attached a 14.5 cm MIPI extension cable to the tracking camera. and were able to fly for ~10 minutes without GPS in position mode with QVIO. However, ever since then, the drone reboots itself intermittently. On occasion it is stuck in a cycle of rebooting every ~20 seconds.

Reflashing the drone to the latest version, using a smaller MIPI extension cable (6 cm instead of 14.5), and completely removing the extension cable have been unsuccessful from stopping the drone from rebooting itself. Removing the extension cable seemed to remove the problem for a day, but the drone returned to its state of rebooting itself. Something we noticed is that removing the microhard modem seemed to help the drone stay in a stable state, but this was not consistent.

Is there anything else we can try to prevent this problem from happening?

Hello,

When we try to run "voxl-calibrate-camera stereo_front -s 9x6 -l 0.073" or "voxl-calibrate-camera stereo_front -s 9x6 -l 0.02413," and after we perform and complete the necessary calibration using voxl-portal, the process ends up giving an error along the lines of "Error is bigger than reprojection error." The max reprojection error allowed is 0.5, but our errors range from 1 to 5. We performed this same process on our VOXL2-based Sentinel with no issues, it is only the rb5s that give us this issue.

Please advise us on how we can calibrate our stereo cameras on these rb5s with the VOXL SDK.

Hello,

Currently, when we try and fly the Sentinel VOXL2-based drone in VIO mode without GPS manually with RC transmitter, the voxl-qvio-server goes into a FAIL state in 1-2 minutes after flying. By running voxl-inspect-qvio, we determined that the error messages returned when the voxl-qvio-server crashes are IMU_BW and IMU_BW_BAD_CAM_CAL. We are using the default tracking camera calibration that came with the Sentinel.

In flight, there is an average of 20ish features at all times during the flight. However, the average q-value (quality) is between 0-20% (fails at -1).

@Adrian-Hidalgo That was it, thanks!

Hello,

We recently flashed our 5G LTE rb5 drones with system image RB5 Platform 1.3.1-0.8 (https://developer.modalai.com/asset/3) but have been experiencing issues when trying to connect to QGC.

First (after putting the drone into softap mode), we ran voxl-configure-vision-px4 and enabled everything but offboard mode. We use the ip of the laptop connected to the drone's network as our input for QGC ip address

Second, when we run voxl-inspect-services, we see voxl-vision-px4 is enabled but not running. If we try "systemctl start voxl-vision-px4," it immediately crashes. Attached is the output of "systemctl status voxl-vision-px4."

Third, we tried running voxl-configure-mavlink-server and enabled permissions, then tried running voxl-configure-vision-px4, but this had the same result.

We couldn't find any specific documentation on how to connect a rb5 VOXL SDK drone to qgc, so any help you could give would be welcome.

@wilkinsaf Way we handled it was creating our own services/scripts for streaming to QGC automatically with mavlink-camera-manager. Hope it helps