@Aniruddha
Even after matching the versions, I am not able to recreate your error
I will try relfashing my voxl2, to start from a clean slate similar to your setup right now.
Since you reflashed the voxl2, is there something you changed on the voxl2 for your goals? I assume that after a reflash, I should have the same setup as you

I tested the fix and snapshots work now, thank you very much!

Hi @Myles-Levine ,

I just want to double check something to make sure there is no confusion.

The lepton sensor is an IR (thermal) camera. it does not measure range. The lepton sensor plugs into the large square socket that is mounted to the M0157 / M0187 board (they are very similar). The infrared TOF sensor is a smaller (rectangular) sensor, which is marked as U1 on M0187 : https://docs.modalai.com/M0187/ .

Have you checked whether the Lepton sensor is working using voxl-portal, which would allow you to look at the IR image coming from the sensor?

Alex

@yaoyuh , it looks like the order has been taken care of. please let us know if you have any more questions.

Alex

@Jesus-Cardenas Flat builds should be available now!!

@DronAlan https://www.modalai.com/pages/rma

@Gerhold-Ten-Voorde , our lens holders are custom and we do not have any information we could share about those, but you may be able to find similar lens holders from other sources.

IMX412 : https://www.m12lenses.com/M12-Lens-Holders-s/61.htm

For IMX664, you may want to check Runcam fpv cameras, which appear to have similar lens holder / housing, however i don't know if those would have extra threads you need.

Also, please note that if you are going to try the spacer approach, make sure that there is absolutely no gap between the spacer, lens holder, otherwise light can enter the camera from the side and affect the image quality. Also make sure that even when using the default lens holder with IMX664, the mounting holes in the aluminum housing are covered, so that light cannot get inside.

Alex

@Vinny @Alex-Kushleyev @Eric-Katzfey

Hello ModalAI Team,

I am writing to request information regarding the Mean Time To Failure (MTTF) for several hardware components that we have procured from your team for our ongoing development program.

The components include:
VOXL2
ESC
Flight Controller (V2)
Front-End Board (Camera Interface)
Camera Modules

We would appreciate it if you could share any available MTTF data, reliability reports, or qualification/test standards associated with these products.

If detailed MTTF values are not readily available, any indicative data such as MTBF estimates, environmental test results, or reliability benchmarks would also be helpful.

Please let us know if any additional information is required from our side to process this request.

Thank you for your continued support.

@Alex-Kushleyev this is super helpful. Thank you.

@Alex-Kushleyev Thank you so much for your response. It helped a lot.

@Igor , we just uploaded the emulator docker image, please see details in this post : https://forum.modalai.com/topic/5179/qrb5165-emulator-image-1-6

@ZuraNeb Perfect! Thank you!

@Alex-Kushleyev Awesome Thank you!

Additionally, where can I buy the propeller replacements? It's not here https://www.modalai.com/search?page=1&q=propeller

@Alex-Kushleyev said in C29 Configuration:

https://docs.modalai.com/voxl2-coax-camera-bundles/#kit-pictures-and-descriptions

The flex cable is pretty short, where does the tof sensor get mounted exactly after it is plugged in? I assume it is meant to be downward facing.

As an update, I was able to get the latency down to about 50-60ms by making the following changes to /etc/modalai/voxl-camera-server.conf. Are there any other optimizations I can make?

{
"type": "imx412",
"name": "hires_down",
"enabled": true,
"camera_id": 2,
"fps": 10,
"en_preview": true,
"preview_width": 4056,
"preview_height": 3040,
"en_raw_preview": false,
"en_small_video": false,
"small_video_width": 1024,
"small_video_height": 768,
"small_venc_mode": "h264",
"small_venc_br_ctrl": "cqp",
"small_venc_Qfixed": 30,
"small_venc_Qmin": 15,
"small_venc_Qmax": 40,
"small_venc_nPframes": 9,
"small_venc_mbps": 2,
"small_venc_osd": false,
"en_large_video": false,
"large_video_width": 4056,
"large_video_height": 3040,
"large_venc_mode": "h264",
"large_venc_br_ctrl": "cqp",
"large_venc_Qfixed": 40,
"large_venc_Qmin": 15,
"large_venc_Qmax": 50,
"large_venc_nPframes": 29,
"large_venc_mbps": 40,
"large_venc_osd": false,
"en_snapshot": false,
"en_snapshot_width": 4056,
"en_snapshot_height": 3040,
"exif_focal_length": 3.0999999046325684,
"exif_focal_length_in_35mm_format": 17,
"exif_fnumber": 1.2400000095367432,
"snapshot_jpeg_quality": 75,
"ae_mode": "lme_msv",
"gain_min": 54,
"gain_max": 8000,
"ae_desired_msv": 60,
"exposure_min_us": 20,
"exposure_max_us": 33000,
"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
}

@extmoddain ,

Can you please send a picture of the damaged ESCs? Which component blew up? Also what do the labels on the ESD bags from those ESCs say?

The 6s version of M0129 (mini ESC) should have a small label on the white 4-pin connector that says either -63 or -65 (meaning 6S and either 3.8V or 5.0V output for VOXL2 mini or VOXL2). We can also check using the serial number (label should be present on the ESC)

https://docs.modalai.com/voxl-mini-esc-datasheet/#specifications
aa7bc73c-90f7-41ae-9f28-cacb800c72eb-image.png

Alex

@ChrisB here is a system architecture to follow: https://docs.modalai.com/voxl2-d0014/

We do not support an RB5, that is a Qualcomm product

Hi @the_engineer ,

Please see the responses to your questions below:

Is the drone suitable for such an application, or is there a drone better suited for this kind of application?

Starling 2 Max can be equipped with two global shutter tracking cameras, two high resolution (IMX412) cameras and a TOF sensor, providing the most sensing that our platforms offer.

Is such indoor autonomous operation is feasible with the Starling 2 Max?

dual-camera VIO can be used for indoor navigation (using our integration with Open Vins software) please note that we cannot guarantee performance in your environment and you would like to achieve reliable operation, you would need to become very familiar with the software components and test and address the issues that may come up in your environment depending on how narrow the aisles are, you may consider Starling 2 (not Starling 2 Max)

To what extent can this drone be programmed and extended for research or development purposes?

majority of ModalAI software that runs on VOXL2 is open source : https://gitlab.com/voxl-public/voxl-sdk/

Is the drone programmable with Python or a similar programming language?

Voxl2 runs Ubuntu 18.04 OS and you can use any standard programming languages. Most of voxl2 apis for data access (camera, imu, etc) are in C/C++ which can be extended to python via bindings. ROS is also supported.

What charge time can be expected?

Typical recommended charge rate for Li-Ion batteries is 1C, so about one hour, maybe a bit more. You are free to explore other battery vendors if you need faster charge times.

Is a docking station/ induction charging retrofit possible?

we do not support this feature, but it should be possible with additional design. You would probably need to have your own power management board that allows seamlessly disconnecting the old battery (to be charged) and applying a DC power supply.

Is the drone capable of navigating in subpar lighting conditions?

you would need to test in your specific environment and address any issues that come up. Lighting is not the only factor, but also amount of useful features, etc

What is the expected maximum flight time at maximum takeoff weight?

see this thread : https://forum.modalai.com/topic/3732/starling-2-max-payload-capacity-and-flight-time-impact additional recommended payload up to 500g

What are the operational temperature limits of the drone?

Starling 2 Max can operate in reasonable temperatures. However, you would need to monitor your CPU usage - if it hits 95C, automatic throttling will occur and the system may not be able to keep up with all the tasks. ESC is rated to run at least 100C (MCU temperature), so that should not be an issue for this particular drone, which is not significantly loaded in terms of motor power).

Does visual obstacle avoidance also work during remote controlled manual flight?

please take a look at voxl-vision-hub, but remember that this will be a starting point and you will need to develop your own application based on your requirements and testing : https://docs.modalai.com/voxl-vision-hub/

What is the expected delivery time for the system to Germany?

Expected to ship within 60 business days from San Diego, CA, as stated on our web site https://www.modalai.com/products/starling-2-max

@shiva-rv Try heating up the IMU by stressing the CPU then shooting it with air to create a large thermal gradient between the silicon of the VOXL2 and the IMU die itself, I predict you'll see the Z bias jump like crazy, but X and Y not so much.

You might also observe that the temperature gradient determines the bias, not the absolute temperature, hence using a temperature model for compensation is useless, and not applied by modal: https://gitlab.com/voxl-public/voxl-sdk/services/qrb5165-imu-server/-/blob/master/server/src/imu_interface.cpp?ref_type=heads#L168

If you're curious about the physics of why MEMs IMUs like ICM42688 act this way I'm sure your favorite AI chatbot could give you a nice explanation about the materials sciences at play here.

Practically, thermally isolate the IMU component as much as possible.