@Aaron-Porter Most likely jump is due to NTP aligning the clock. The other device that is time stamping using real time clock really should move to monotonic.

@Alex-Kushleyev , Thank you for the clarification! We will change the service and see if it meets our needs. Regards, Jacob

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.

@Federico-Wyrwal , please check the instructions for setting up EIS, specifically https://docs.modalai.com/camera-video/electronic-image-stabilization/#minimal-software-setup The latest drivers can be downloaded from here Please let me know if you have any other questions. Alex

@Alex-Kushleyev Thanks

@detlefurig Yes that is something we're actively working on, probably a few months out at this point

Hi @TomP Looking pretty grim... That specific signal is all buried at least 3-7 layers deep directly from that pad and it hits other BGA devices right in the pad.... no exposed traces, no exposed pins at all... You'll have to find a different UART port or some other plan B.... sorry.

@J-B-Song Hello J.B Song, Did you connect HDMI via USB-C on VOXL2? Did you use this image [image: 1756439982349-7d1ec055-c0a2-497c-8c85-be95d56a1125-image.png] Hope your reply soon, thanks so much.

@Eric-Katzfey I did the systemctl stop and started service again. I guess rebooting the board earlier did not have the same effect. The compass calibration in Q is working now (no more "no mag found" error) which I guess it means the mag is working now and our gps is working too. here is the output of voxl-p4 -d by the way: INFO [qshell] Send cmd: 'lis3mdl start -R 10 -X -b 1' INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic INFO [muorb] [qshell] qshell gotten: lis3mdl start -R 10 -X -b 1 INFO [muorb] [qshell] arg0 = 'lis3mdl' INFO [muorb] [qshell] arg1 = 'start' INFO [muorb] [qshell] arg2 = '-R' INFO [muorb] [qshell] arg3 = '10' INFO [muorb] [qshell] arg4 = '-X' INFO [muorb] [qshell] arg5 = '-b' INFO [muorb] [qshell] arg6 = '1' INFO [muorb] [drivers__device] *** I2C Device ID 0x51e09 335369 INFO [muorb] [drivers__device] Set up I2C bus mutex for bus 1 INFO [muorb] lis3mdl #0 on I2C bus 1 INFO [muorb] (external) INFO [muorb] address 0x1E INFO [muorb] rotation 10 INFO [muorb] INFO [muorb] [qshell] Ok executing command: lis3mdl start -R 10 -X -b 1

@Eric-Katzfey thank you for reverting back, it was very helpful, i was able to get multiple streams.

@psafi In this case we don't use voxl-mavlink-server directly because we are essentially setting up a "mavlink device" straight into px4.

@andrevs01 But, the configuration of what Mavlink broadcasts can be different than what it actually broadcasts. It will only broadcast something that it is configured to broadcast if it is receiving data from the required topic(s) internally.

@Thomas-Müller you can read up on our "VOA" implementations here: https://docs.modalai.com/voa/

@Thomas-Müller interesting. i'm just experience the very same thing. have you by chance figured out what was the issue?

@drones-mexico In order to have the C28 camera config function properly you'll need to flash a different kernel on your voxl2, is that something you tried?

@cguzikowski Yes, very odd. Hopefully it just works now