Flight Core does not have an internal magnetometer (compass) so there's no need!

@ James-Strawson Im sorry but is note the case…. While just activation voxl vision px4 service from fredh resceived voxl cam, voxl output local frame pos and velocitys via mavlink. so how to activate local to body frame velocity transformation? Maybe with px4 this work but with ardupilot i check on mavlink analys and i make simple translations and i can ensure you that voxl send out local frame pos and vels. Maybe you can tell me ou to force voxl to output local frame pos but body frame vels to ardupilot ? Thank you so much.

@Uros . .

@Caleb-Rievley Generally, that won't work.

@ryan-langlois1 Seems as though you've answeredthe question yourself but by default /etc/network/interfaces doesn't exist. It is created in certain configurations i.e. using Microhard with voxl-modem

@Caleb-Rievley Our recommendation is to use voxl-uvc-server and voxl-streamer for UVC cameras. Documentation is at: https://docs.modalai.com/voxl-streamer/#streaming-uvc-cameras-from-voxl-uvc-server, https://docs.modalai.com/voxl-streamer, and https://docs.modalai.com/voxl-uvc-server

@Chad-Sweet That worked! After I did the reinstall, it would not connect. I closed and reopened QGC, switched the usb cable, and then went into the auto-connect section of the general settings and disabled the NMEA GPS device drop-down. Thank you Chad!

Ok great! Thanks for the info!

Oh no, sorry to hear that. Let's see what we can do to resolve that. So as not to be redundant and streamline the process, what have you attempted already to unbrick the VOXL's? Could you also provide further information on the board as well as what you were attempting to do before the VOXL's bricked? eg. software version, setup, camera config, computer setup, usb cables, power management, etc. The more information you can provide, the better we can help you.

IMU's can be found here. Through QGC, the offsets can be adjusted: here You'll have to configure the extrinsic files as well to match the rotation of the board /etc/modalai/extrinsics.conf Hope that helps!

@serge said in autostart voxl-streamer: @Alex-Gardner said in autostart voxl-streamer: systemctl enable voxl-stream thank you

I figured it out! I was following the gitlab page to install the cross docker, which is incorrect when using the prebuilt image from the modalai website. (https://gitlab.com/voxl-public/support/voxl-docker) following this documentation actually works: https://docs.modalai.com/voxl-cross/ Eli

@Alex-Gardner Thank you, is looking good and promising for this use case. I'll give it a try.

Hi Sergio. I'm handle a number of rover configurations here for the team. Reading thru the posts, let's take a step back to confirm your setup. a. you are using the cube to output IMU data into voxl-cam. b. you are using voxl-cam to output odom data [back] to the cube for (e.g. external vision localization) c. the camera has been moved from the stock position of -45deg from horizon w.r.t. voxl-cam body to 0deg from horizon w.r.t. voxl cam body. d. the cube is mounted w/IMU in standard orientation (0 deg to horizon/forward, aka imu RPY is 0,0,0) e. you are not using a modalai flight core (option for voxl-cam purchase) First of make sure your PX4 SENS_BOARD_ROT (or AHRS_ORIENTATION if Ardupilot) is set for a cube setup (I recall should be "No rotation" as well as from your photo). Please reply if that is all correct. If so, then we can move to the next step where I can show you how confirm vio's pose estimation (after that then we'll look at position accuracy).

okay,Thank you

I think we found the issue. this version of the holybro compass has the magometer mounted upside down and turned 90 right. we were able to orient the sensor in QGCS. thanks for the help

Looks like this was being caused by something on our end. Sorry about that! -Drew

@amitga It wouldn't hurt to upgrade your VOXL to the latest platform release (system image + voxl-suite): https://developer.modalai.com/asset/view/91 System Image: 3.6.0 Suite: 0.5.0 I believe voxl-wifi has recieved some robustness updates since the release you're on.