OK all shipped ok.

Above looks good with flat on table test results...

Here's factory test data which shows OK:

0a21b33e-3335-48ba-b756-2a84a9b9f6f9-image.png

2024-05-03T22:01:18.648Z -- {"desc": "IMU1 - APPS PROC - OK", "GYRO_X": 1.001, "GYRO_Y": 0.998, "GYRO_Z": 0.994, "ACCL_X": 0.99, "ACCL_Y": 0.987, "ACCL_Z": 0.957, "FAILURES": []} 2024-05-03T22:01:19.361Z -- {"desc": "IMU0 - SLPI ACCEL - OK", "ACCL_X": 0.11492, "ACCL_Y": 0.20016, "ACCL_Z": 9.89428, "FAILURES": ""} 2024-05-03T22:01:19.960Z -- {"desc": "IMU0 - SLPI GYRO - OK", "GYRO_X": 0.02435, "GYRO_Y": 0.03108, "GYRO_Z": 0.00174, "FAILURES": ""}

If it passes flat on table I think things are OK and it's a result of expecting certain tests to run in this flat orientation during factory test.

@modaltb I see.

Just one last thing, do you think a gimbal of ~900g would be ok to be attached to the Sentinel without any issues? As the quoted max. payload for the Sentinel is 1kg?

Hi @Jeremy-Frederick
This appears to be a fusing open of some (one or more) power signals on the flex, indicating that excessive current was demanded of the flex. A short at the image sensor module of a power rail could cause this, so a loose connector may have certainly been your culprit, and a voltage likely contacted a GND signal or component.

@jonathankampia We only add drivers to the build that we have used and tested with. The ll40ls driver is not one of them so you would have to add that to the build yourself.

@robertociuch , I tested the dual stereo configuration with M0036 14.5cm extensions on each stereo. Stereo pairs plugged into J6 and J8, just like Camera Configuration 11 shows (link), I unplugged all other cameras. Seems to be working fine. I am attaching the voxl-camera-server.conf file with just stereo set up. Also, i am using SDK 1.3.2, however it should be working with older SDKs. If you find that installing the longer flex is an issue, it is possible that the flex itself is problematic. You can test the stereo pairs individually to find if there is a particular cable that is bad.

Also, please double check that the following sensormodules (camera drivers) are present in the correct location:

voxl2:/$ ls /usr/lib/camera/*combo* /usr/lib/camera/com.qti.sensormodule.ov7251_combo_0.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_4.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_1.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_5.bin { "version": 0.1, "fsync_en": false, "fsync_gpio": 109, "cameras": [{ "type": "ov7251", "name": "stereo_front", "enabled": true, "camera_id": 0, "camera_id_second": 1, "independent_exposure": false, "fps": 30, "en_rotate": true, "en_rotate_second": true, "en_preview": true, "preview_width": 640, "preview_height": 480, "en_raw_preview": true, "ae_mode": "lme_msv", "ae_desired_msv": 60, "exposure_min_us": 20, "exposure_max_us": 33000, "gain_min": 54, "gain_max": 8000, "exposure_soft_min_us": 5000, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 }, { "type": "ov7251", "name": "stereo_rear", "enabled": true, "camera_id": 3, "camera_id_second": 2, "independent_exposure": false, "fps": 30, "en_rotate": false, "en_rotate_second": false, "en_preview": true, "preview_width": 640, "preview_height": 480, "en_raw_preview": true, "ae_mode": "lme_msv", "ae_desired_msv": 60, "exposure_min_us": 20, "exposure_max_us": 33000, "gain_min": 54, "gain_max": 8000, "exposure_soft_min_us": 5000, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 }] }

@Alex-Kushleyev Hi Alex, When I hold the drone in hand and move around the room, I see that VIO is at 100%. It only fails when I shake the drone or start flying it. I'm not sure what's going wrong.

@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.

@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!!