@tom Sure, Thanks it worked out.

Can anybody find out the problems? Many thanks.

@Trinadh Can you edit the file /etc/modalai/voxl-px4.conf and set GPS=NONE, RC=EXTERNAL, POWER_MANAGER=NONE, DISTANCE_SENSOR=NONE, and OSD=DISABLE. After updating that file and rebooting does the CPU utilization change at all?

@wilkinsaf I completely agree. We can compare to a normal USB camera as well to see if the issue is with specifically streaming from the HDMI to USB capture card

hi @Siddhanth to ssh onto the voxl you will need the IP address of the voxl. This means you will need to setup wifi on the voxl and then acquire the IP address. Once you have the IP address, you can run the command as in the image you posted above and the default password is oelinux123: ssh root@<IP ADDRESS>

@Moderator Thank you for responding in the repo where can i find the config file like in the source or tools can u pls help thank you the doc say's this Reset VIO resets vio to (0,0,0). Please do not reset in flight, only do this when it is safe and necessary

@Aaron-Porter The tracking sensor does not need to be straight, but the extrinsics need to reflect the accurate position of the sensor relative to the IMU if you monitor the qvio-overlay in voxl-portal, it's usually obvious what is going on. If you need help interpreting, please post a screen video capture of the qvio-overlay here

@Vinny Thank you so much. Kim,

I should have posted this earlier, but I was able to make my IO board work with sbus by building my own version of Px4 based on your guy's master branch. For anyone else coming across this post, @Eric-Katzfey solution should work.

@wilkinsaf Thanks for the follow up!

@tom Thanks a lot for the reply.

@ATMA said in Technical specifications VOXL 2 mini: Following on my request. Are you planning to integrate support of the lte device? Timeline? Hello Team Modalai, any feedback on this topic? As the Starling also integrates the Voxl2 it seems at bit like the Voxl 2 mini is more of a future product that needs much more work to be ready. So regarding weight and size savings it could be a great product... Thank you! Cheers Josua

@brycek did you eventually figure out? I need to create a full image as well

@James-Strawson Quick update. I was able to lower the value to 300 and it seems to work as well.

Hi @AndriiHlyvko The chip is not infinity flexible. Many things are fixed/set in hardware meaning either the silicon device or the PCB. There is no internal cross-bar in the QRB5165 that allows for 100% remapping like on FPGAs. Please see these pages: https://docs.modalai.com/expansion-design-guide/#qups-the-key-io-groups-for-expansion https://docs.modalai.com/voxl2-qups/ Hope that helps explain things a little.

Hi @RykerBarthold That USB-C follows the pinout you can get from the device spec. We list the MPN of the connector here: https://docs.modalai.com/voxl2-mini-connectors/#summary I must caution that you need to plan on failure here. That connector will take a lot of heat to remove and you risk damaging a lot of the surrounding components. We will obviously not be able to offer any RMA or credit for boards that have been through this potential process.

@Abdullah01 There has been some progress but it is taking longer than expected. We are actively working on all of it.