Topics created by brahim

All output pipes that begin with "hires" should have the same timestamp for each frame as they all come from the same image frame. the small and large pipes are simply different resolutions being encoded for different use cases from the same source camera frame

@brahim , i dont think you can easily use SPI on VOXL2 for Neopixel. However, our ESCs support neopixel output. Pleasee see https://docs.modalai.com/modal-esc-datasheet/#neopixel-led-support and similar docs for the mini and fpv ESCs.

You can use the python script to test the LED strip and if you want to go further we can help you with PX4 integration.

Alex

Hey there, voxl-logger for openvins is only avaiable using a combination of raw flags, e.g. -c tracking_front -i imu_apps -r ov -r ov_extended -r ov_overlay Yes the -o option for odometry is not completed yet for openvins. That hsould get you the log data for openvins

As for simulating camera stream failure, it's very likely any attempt to cover a camera will increase the exposure of that stream, and in some cases you will still see random features: for example, covering with a finger will still pick up features from your finger print. We're still actively improving voxl-feature-tracker and should have a new version available soon.

Hey Eric, so I ruled out the dsp as the problem since I am getting the same behavior on an nxp nuttx-flashed board. It appears the external device is the issue as it is not responding to i2c commands. From what I can tell qurt uses the same I2C 'transfer' command at least with the same parameters. It can find the device on the bus when I give the command "qshell xm125_evk start -X -b 4" but probing it appears to be impossible right now.

@brahim , Tom is on vacation for the holidays, so please be patient with us during this break.
Most of our team is taking some much needed time off to spend with family.

In the meantime, I'd go through the usual trial and error of different hardware, cables, and USB ports to see if things improve for you. Also check all connectors and cables are secure and pin-1 aligned.

Thanks!

The drone has had it's crashes yes. Visibly carbon fiber is okay but there's flex especially on the arm connected to motor 4. Used CA glue to hopefully stiffen the carbon fiber for now