@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

@Leon-Vaidman , we do not currently support any 8K cameras and none planned at the moment.

Alex

@Prabhav-Gupta The RB5 does not have a second IMU like the VOXL 2 does. So voxl-imu-server is only applicable for VOXL 2, not RB5.

@reber34 , perhaps this approach can work for you:

record a video encoded at high bit rate (using voxl-camera-server and voxl-record-video . Please note that the output of voxl-record-video will not be in a standard container (such as mp4, etc), but you can fix it with ffpeg : ffmpeg -r 30 -i voxl-record-video.h264 -codec copy videofile.mp4 re-encode the video offline with desired codecs / bit rates / resolutions install gst-rtsp-launch which uses gstreamer to set up an RTSP stream https://github.com/sfalexrog/gst-rtsp-launch/ you will first need to figure out what gstreamer pipeline to use on voxl2 that will load your video and parse the h264/h265 frames (can use null sink for testing) and then use that pipeline with gst-rtsp-launch which will take the encoded frames and serve them over rtsp stream. gstreamer may be more flexible for tuning the encoding parameters of h264/h265 (compared to voxl-camera-server) and you can also use it in real time later (using voxl-streamer, which uses gstreamer under the hood)

Another alternative is to use voxl-record-raw-image to save raw YUVs coming from voxl-camera-server and then use voxl-replay and voxl-streamer - the latter will accept YUVs from the MPA pipe and encode them using the bit rate that you want. Note that depending on the image resolution, YUV images will take a lot more space than encoded video, but maybe that is also OK since VOXL2 has lots of storage.

Alex

@mario Hi Mario, both Yolov8 and Pytorch are on our roadmap to support. We do not have a good timeline yet though.

@groupo Yes, that's the intention.

@Alex-Kushleyev @Vinny Thank you for your response. I'll test it.

@Namho Hello. Have you found a solution to this issue?

Hi @voxltester
Are you able to post a high res photo of the USB breakout board, both top and bottom?
Could save you the time and hassle of an RMA with a good high quality photo I can inspect.

The board was tested and passed before shipping, but these boards do have some small parts on that that are susceptible to damage if the board is dropped or if a tool or other item hits into it.

Thanks!

@Eric-Katzfey The EKF2_EV_CTRL param is set to 15 bits (all enabled). We don't have any cameras on the drone at the moment, though. Could that be introducing issues in the EKF2 and causing it to reset? I'll try disabling all vision stuff and see if it works different.

@Alex-Kushleyev I had a similar issue and this helped a lot. thanks.

@tom it looks like the groups are the same between machines (and yours except I'm not in docker), and the versions of adb, fastboot, and all android packages are the same. I was looking online and some people say it may be related to or solved by udev (https://askubuntu.com/questions/705537/no-permissions-fastboot-fastboot-and-adb-not-working) but I'm not sure I have more more time to troubleshoot this, and I didn't touch anything with udev on the working machine. Hopefully I'll be able to circle back to this eventually, but thank's for your help with everything!

@Alex-Kushleyev Thanks for your insightful reply!!

Good morning @Chad-Sweet, @modaltb, and team,

Following up on my post from yesterday, I created a back-up folder of dnn (located in /usr/bin/dnn), went into the new folder, renamed ssdlite_mobilenet_v2_coco.tflite to ssdlite_mobilenet_v2_coco.bak.tflite, renamed custom_net_01.tflite to ssdlite_mobilenet_v2_coco.tflite, and restarted voxl-tflite-server. When I opened the web-portal I was able to not only view the camera feed, tflite was also showing a camera feed (something which hadn't happened before), but it wasn't drawing new bounding boxes.

Thankfully, it feels like I'm getting really close to cracking the code on this, but I am still just missing the last step of getting voxl-tflite-server to actually draw bounding boxes using my custom model. I look forward to hearing from you all!

Best wishes,

@groupo This code https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/mavlink_io.c?ref_type=heads#L156 sets up a pipe client to listen for Mavlink messages in the voxl-vision-hub application

@jonathankampia Yes, both qmc5883l and ist8310 are supported now.

@Stefan-Amundarain ,

It is always good to double check the firmware version of our ESCs and IO board (whichever you are using) so that you have control over the version that you are using and do not upgrade unless that is your intention or use outdated firmware. Typically when we release the new SDK we recommend updating ESC and IO board firmware because some features will require the update.

However, if you just receive a new board, you probably want to upgrade it to the firmware version that you have already been using or version required by the sdk.

Our voxl-esc tools (used for firmware update, checking) are used for IO board and ESC and make it easy to check and update firmware in an automated way to ensure you are running the firmware that you intended.

If you need more help with this, please let me know.

Alex