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

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

Using the roskinetic Mavros example as a basis, I'm trying to program autonomous missions for the drone to fly in VIO. However, I can't get a lot of the mavlink commands that depend on local_position_ned to run (i.e. https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED). What mavlink messages/commands do you recommend for flying a drone in VIO?

@Prasad-Antervedi Try following these: https://docs.modalai.com/calibrate-cameras/

Hello again,

I'm trying to follow the instructions here: https://docs.modalai.com/mavros/. Everything worked fine until i got to run_mavros_test.sh, which is supposed to have the drone takeoff and make a figure 8 in offboard mode. When I try running this script, it reads "mission sent" and "requesting home position" indefinitely. I have the drone in VIO mode with all the px4 parameters uploaded (the one in the params file that is recommended) and the tracking camera enabled. I also have voxl-qvio-server enabled and running.

I also attempted running this outside with a gps (with appropriate px4 parameters changed with the params file provided) and I was able to get "mission sent" but no arm, and no "requesting home position."

How can I get the drone to execute its mission?

VIO screenshot (GPS disabled):

@Alex-Gardner Worked, thanks!

Not modalai, but something that helped me debug this very same issue was installing voxl-portal, and using that to view the qvio stream, which will overlay the points onto the tracking camera screen. If it creates points at your drone's motors and feet, then I presume it would be a problem

I recently purchased a TOF camera and was following the guide in here: https://gitlab.com/voxl-public/old-projects/voxl-hal3-tof-cam-ros. I was able to get a ROS connection and access the camera, but I couldn't get frames to appear. How can I get the frames and data to stream?

System: Ubuntu 18.04
ROS version: melodic

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

I recently bought a TOF sensor, and I wanted to test it with ROS using the guide in the documentation. However, I got stuck when I got to this step because the VOXL doesn't have "voxl_hal3_tof_cam_ros/launch/tof.launch" in its share folder. I am on the latest system software. Is there another download I need to run or install?

@Eric-Katzfey Voxl-streamer has been working fine so far with our current software, and I can test against QGC 3.5.6, so the main issue to worry about is the power issue you described. Could the custom UVC driver code be made available? The Boson IR camera is currently a critical component of our project