@Moderator oh I see, so to reduce overheating would it be recommended to use the default settings instead of limiting my process to cpu 4 to 7?

@tom i figured it out thank you

@Moderator This is appreciated, I had however already seen these docs. My issue is that though you have a 15cm extension that does not account for the orientation of the Voxl2 in relation to the sensor and location to mount them. due to this the 15cm connector is not long enough. Is there any advice on how we can extend these sensors beyond these lengths? Is there some shielding or other potential signal boosting we can do? Our goal is to eventually be able to position the sensors further away from the voxl2 as we want to use the hardware on much larger platforms where the rear sensors will need to be further than our current test development. TIA for any insight.

So something that I was seeing while testing this was having a bit of instability with Open VINS flying and altitude flying (Not Using VFC). I was seeing that voxl-open-vins-server stated that the IMU temperature was too high and kept resetting. After letting the VOXL2 cool down for a day I was able to have the Drone Fly in VFC mode but not sure how it flew compared to Position mode using VIO.

@Andrew-Martin You can check your camera calibration files with voxl-check-calibration If you see any missing I can likely locate them and send them over to you

@Jetson-Nano VOXL 2 does not have PWM out. You would need our IO expander board M0065 to bridge between UART and PWM. https://www.modalai.com/products/voxl2-io?variant=40610514206771

@Alex-Kushleyev Thank you for reverting back.

@zauberflote1 @Cliff-Wong @James-Strawson guys, can you help me with the error mentioned. now i have an another error where, if I arm the drone, the vio is drifting, and i can see the values increasing without any movement. what would cause this kind of errors, earlier the drone was flying fine, then it started drifting, even when just armed.

@Muqing-Cao You can get the VIO data from the ROS1 and ROS2 Topic /ov_overlay , /ov, or /qvio depending on which VIO you are using. Both have the same type interfaces available so either should work. Yes, you will be able to get run the commands on a host computer and as long as they are on the same ROS_DOMAIN_ID, for ROS2 this should be automatic.

@Eric-Katzfey Thanks for that. I had to start the qvio server and mavlink servers. Also, had to connect the flight controller to qgroundcontrol using the makeshift cable. The RC connection also works fine. Wondering what are the functionalities since the product is reaching its EOL and no new upgrades would be coming in terms of autonomous applications and PX4 integration. Thanks.

@Alex-Kushleyev I set the "ae_mode" to "off" and it works! thank you

@Alex-Kushleyev Thank you so much for the detailed explanation! I will keep you posted with the update shortly.

@Eric-Katzfey Very sorry for the late response and thank you for pointing out the mavlink-router approach, https://github.com/mavlink-router/mavlink-router. I will try it and keep you posted here. Thank you for answering my quesiton.

@george-kollamkulam Here's voxl-logger https://docs.modalai.com/voxl-logger/ which you can use to record data. if you need to access the data real-time, that's a good source code starting point for how to capture the data into your application

@nicksheldon Hadron 640R support is in beta. You can request a custom invoice for the adapter at https://modalai.com/contact We have no experience with Herelink. The modems we have support for MVX, Doodle Labs, Cellular and Wifi You cannot use HD Zero to send video from VOXL 2 The software is all open, so if you need to send custom gimbal commands you may need to update the software VIO cameras need to be fixed mounted with the VOXL 2 and cannot be on a gimbal