ModalAI Forum

@dsupplee yes, the images on VOXL 2 are unsigned. please see the VOXL 2 kernel build guide here: : https://docs.modalai.com/voxl2-kernel-build-guide/

@Moderator Got it. I have mailed already to contact@modalai.com . Please expedite my request and let me know.

@brinkap unfortunately, there is no CAN capability on VOXL 2. You would need to have an adapter PCB that supports CAN connects to one of the available interfaces, and then write a Linux driver that enumerates as can0

@ErezI I think we did it, but i'll try again. Thanks

@camharrisvayu At this point it may be worth submitting an RMA for this flight deck and we can take a look: https://www.modalai.com/pages/rma

@camharrisvayu Ok, we should be able to close this issue -- I flashed 1.0.0 and uploaded params for the sentinel model and that made it so the RC inputs could control the drone -- not sure which parameter made the difference, but I may investigate and report back if I find out.

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

@I_Dwyer @Chad-Sweet Hello all, has this issue been solved in and particular version, we too are facing the same issue, on HS1 the voxl-mavlink server is initiating but we are not able to see any data from this port. We are right now on the 1.5.3 build. Pls provided more info on the same.

@KevinChan 0.9.5 is the newest, 0.9 is second newest, 1.3.1-0.8 (0.8) is super old. We changed our naming scheme some time ago so I can understand the confusion

https://docs.modalai.com/voxl2-io/

Thanks for the feedback! Document updated here: https://docs.modalai.com/calibrate-cameras/#stereo-calibration-video-tutorial

@MartinP This is a bug that we have since fixed but requires flashing that the image you're trying to flash in order to fix... However, a work-around is to do the following when forcing the board into fastboot: disconnect power and USB press and hold fastboot button attach power attach usb wait a few seconds now release fastboot button

Please see the documentation for voxl-camera-server here: https://docs.modalai.com/voxl-camera-server/ There are many examples in our SDK code base of how to consume that data. Here is a good place to look for each of our services: https://gitlab.com/voxl-public/voxl-sdk/services Here is some exact code here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/main.cpp#L474 And another example here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tflite-server/-/blob/master/src/main.cpp#L208

Hi @roy , I don't have quantitive data to give you, except that even in the native setup, we are doing a bunch of "translations". For example, one of the DSPs (sensors DSP, sometimes called Sensors Low Power Island (SLPI), at least on the older platform and carried over by us out of habit)) is talking SPI to an IMU, and then that data get's passed via mUORB to the applications processor and in some scenarios for our vision processing code that runs on the application processor. (We've now actually hooked up an IMU directly to the applications processor for vision processing and PX4 has it's own, but the data path and delays introduced did not cause issues for us) This graphic is from: https://docs.modalai.com/voxl2-px4-developer-guide/ [image: 1654876616605-2e82e9d0-a1bd-49a3-b9ac-1790090ec700-image.png] It shows how we're doing things roughly. So you can imagine this: have an external flight controller connected via UART (as explained above, through an add on board or soon via a camera connetor J8) use our voxl-mavlink-server has a UART implantation that can be used as reference to get MAVLink to/from your Flight Controller INTO VOXL2 Maybe not answering all your questions, but keep the back and forth going and we can widdle away