The kernel build is posted at https://gitlab.com/voxl-public/system-image-build/voxl-build

We do not have a thermal option available today, though the Flir Boson and Lepton have been integrated by customers in the past using USB Stereo cameras need to be co-planar and mounted rigidly. Then they need to be calibrated. Otherwise you should be able to mount wherever convenient

Hey sorry for the late reply but I got it to work after some trial and error, not really sure why it wouldn't work in the first place but maybe I just got the timing way off. Thanks anyway

Hi @shlee853 , Although there's a MIPI/CSI2 standard, pinouts can vary and the connectors on the VOXL are semi-specific, so it's not likely to find something off the shelf that can plug in. If you want to share specs here, perhaps we can point to something. Thanks!

Ah, when I run the PWM program there is no chatter on the PWM signals, so I'm going to review that code again and compare it to mine.

I know this is kinda an old post but I have created a driver for px4 that can use both flavors of the MS5837 the bar2 and bar30. I will create a pull request with px4 so it will be available.

@Chad-Sweet Thanks for your reply. This is the exact answer I was looking for. The flight core is perfect but here at our company we need to use different Pixhawk board for some specific application.

This is a known bug that was fixed in voxl-vision-px4 v0.8.8 which is currently on the development repo, scheduled to be merged into the stable repo in a week or so. The bug is not caused by PX4, it was due the the handling of the specific mavlink packet containing console data. It should behave normally when not using the PX4 console.

@PawelJ There isn't an exact way to do that, if you want you could edit your initial question and add a [SOLVED] section at the top and describe the solution.

Well, we aren't routing the 5V on that little M0022 board to prevent it being used to drive servos (for this concern). But 5V does come down to the connector, so it could be soldered to, and you could create solder bridges on the bottom of the board. Not ideal, but 5V is there, just not routed....

Hi Nikhil, Sorry for our delayed response on this. I just recently joined our forum to help out with more HW centric question. As Chad mentioned, this does require HW mods if you do not want the SW driver timestamp method (which would be our recommendation/preference). The Lepton signal VSYNC (on GPIO3 most likely is what you are referring to) is running at the VIO voltage of 2.8V to 3.1V per Lepton specs. Our camera sensors are MIPI based, and as such all of those I/Os are at 1.8V, so a level translator would be required which makes connecting these a bit tricky, especially if you need bi-directional support with another sync controller/snoop device. This would need to be something done on a custom interface between the Lepton and the stereo sensors. We do not have such module but would be happy to give further guidance if you need it. Thanks! Vinny

Hey @Andrew-Keefe , This isn't something I've tried. Curious as to what the setup looks like if you're up to share more details. Thanks, Travis

Hi Nikhil, check out this document here and see if it helps.

Your understanding is correct, ModalAI's supported configurations are a result of Qualcomm limitations

@Chad-Sweet Thanks for the reply. I've send an email through the Contact Us link with a request. Please let me know.

Hi @Andrew-Keefe, I'm not positive on this one. I have an example of using UART for an ESC here, and I remember having to be careful what task was opening the UART port: https://github.com/modalai/px4-firmware/blob/modalai-1.11/src/drivers/uart_esc/modalai_esc/modalai_esc.cpp#L736 Here's opening of the port (note: this is beta level code) https://github.com/modalai/px4-firmware/blob/modalai-1.11/src/drivers/uart_esc/modalai_esc/modalai_esc_serial.cpp#L48

Thank you @modaltb. I was able to control the LED with my code (yellow = waiting for serial, blue = data valid, red = data not valid).

Hello, When you ran the wizard, what did you enter for the camera configuration question, it should have been option 3 (hires+stereo+tracking) for a flight deck. Do you mind running voxl-vision-px4 manually in odometry debug mode to see if VIO is working and share the output? You can use this command: voxl-vision-px4 --debug_odometry Thanks!