ModalAI Forum

@restore After reading older posts, changing the Voxl start script to add the ist8308 magnetometer to the build instead of the ist8310 solved the issue. I can now see the compass through PX4-listener

@Eric-Katzfey Thanks Eric. I will try this out and let you know soon.

@Jeremy-Frederick I'm guessing that the black 4 wire cable between the VOXL 2 and the APM may have some issues making an occasional problem for the i2c bus. Do you have another one of those cables to swap with?

@Vinny yes thanks so much! I'll look into it.

@Moderator Thank you. This clarifies everything.

@Eric-Katzfey This sounds like perfect plan. I would implement this and get back for any queries. Thank you Eric!

@riteshsharma , based on changelog (https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/CHANGELOG) you can use voxl-camera-server package version 1.8.10 -- dowload it from here http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/. Upgrading your SDK would also work as Tom suggested.

@Jonathan-Davis said in Unable to run my own offboard node in starling 2: offboard_mode Check: https://docs.modalai.com/mavros/#configure-voxl-vision-hub-localhost offboard_mode - set to “off”. When offboard_mode is on, this enables voxl-vision-hub to command the drone to move, which we don’t want (we only want MAVROS to be sending movement commands)

@John-Nomikos Hi, Can you please explain how you solved this? I am facing same problem where my camera is connected via USB to ethenret convertor with Microhard add-on board and my host machine is unable to ping my camera but can ping voxl2.

Hi @Jonathan-Davis, Our Starling v2 VOXL 2 board requires this flat build image (M0054-2 Starling QDL Image 1.7.4) which is available in our protected downloads as well as in the unbricking documentation here where you can proceed with the same step-by-step instructions. When finished, the qdl command should complete and the terminal should output "partition 1 is now bootable" indicating a successful QDL flash. Hope this helps!

Hi Rowan, There is no one answer, it is entirely dependent on your circumstances. auto will be more conservative than perf. perf is intended to go as fast (and hot) as possible

@Aaky , we are working on resolving the GPS detection issue related to uart baud rate changes - if forcing the baud rate works reliably then just stick with that !

@Paola-Lim , have you tried voxl-inspect-cam -a (to see all camera stats) or alternatively voxl-inspect-cam cam0 which would be just for your specific camera name.

@rdjarvis , The board is in eDL mode (emergency download). Can you please check that SW2 is off and if the issue is persists, provide serial number of voxl2 board, we will check test records.

Noting here that flashing the wrong kernel will brick the device (ie flashing the QRB on the QSM) make sure to select the correct option when upgrading the board.

@muhammadbilal1 The batteries for Starling are standard Lithium Ion batteries (not Lithium Polymer). The recommended charging rate for Li-Ion batteries is 1C, so if the capacity is 3000mAh, the maximum charging rate is 3A. Charging at slower rates will extend the battery life (as is true for all batteries). The maximum voltage is 4.2V. Please use a charger setting that specifically supports Li-Ion batteries. Most LiPo chargers also support Li-Ion batteries. I will check how to proceed regarding the missing adapter.

@Aaky Well, unfortunately it isn't obvious what is going wrong. You will have to start by disabling everything and when px4 comes up reliably start enabling things to find out the culprit.

@Paola-Lim You will need to follow directions from this page : https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release Tom suggested getting the SDK 1.1.3, so per instructions you should go to https://developer.modalai.com, log in, then click on Protected Downloads -> VOXL2 Platform Releases and download VOXL2 SDK 1.1.3 and follow the rest of instructions from "flashing voxl sdk" page Alex