@tom Thanks. I will get one of that.
About using another state estimation source, can you suggest me how to do that? Say we can get lidar-based position estimate in ROS message, can we disable the onboard VIO and feed our position estimate to the onboard flight controller through MAVROS or something else? Please advise.

@Vinny Glad I could help, and thank you for confirming so quickly on your side.

@jonathankampia ,

Have you checked that your Boson actually works (using a USB interface with either Flir GUI or a UVC interface)?

Also, is your Boson configured to send MIPI data in 8-bit raw format?

The camera server cannot change the FPS of Boson (or any of its streaming parameters). In fact there is no communication at all happening from VOXL2 to Boson (besides just probing / detection) - all the settings have to be configured by the user prior connecting to VOXL2 (including resolution, fps, etc).

https://docs.modalai.com/M0153/#boson-software-setup

Please double check these points..

Alex

@mkriesel I recommend connecting the drone to QGroundControl and using the spin tool through there to determine correct orientation. voxl-esc spin doesn't take into account anything px4 is doing to determine motor direction so won't be entirely accurate in term of what direction the motor will spin via the flight controller.

@Wei-Cui-0 @Alex-Kushleyev I would also like to see the intrinsics calibration yaml for the M0161 if available. Couldn't find it on the VOXL2. Thanks!

@Jetson-Nano If all that seems to be working then press the turtle button and arm (with drone right side up, not upside down) and verify that with turtle mode enabled the propellers are spinning in the opposite direction and the drone won't lift off. Of course, you must be extremely careful when running this test!!! Make sure that the drone is in a location where it cannot cause damage or injure someone if it goes out of control. It would be best to completely remove the propellers and just verify that the motors are spinning in the opposite direction of normal flight.

@Thomas-Müller you can read up on our "VOA" implementations here: https://docs.modalai.com/voa/

@Thomas-Müller interesting. i'm just experience the very same thing. have you by chance figured out what was the issue?

@ashwin Can you differentiate each drone based on the drone's IP address? Those will be unique.

@hula Would very much appreciate that, however, I don't see a way to send a DM to another use. Feel free to DM me if I'm missing something or point me in the right direction here on this topic!

Very much appreciate any help!

@Alex-Kushleyev I'm not sure if it came with this error, but I haven't observed this before and I don't recall any event that could have triggered this failure. The UAV has not yet flown, so it has not had any crashes or known failures. What other details would help identify the root cause?

Thanks,
George

@wilt From the production team, these should work for you: https://www.mcmaster.com/99461A923/

@Alex-May , our lenses do not have any IP rating for waterproofing, so we cannot provide any guarantee regarding the performance when exposed to water.

Alex

Solved using SDK 1.4

@Vinny

Thank you so much for your feedback — it’s very valuable to us. I will definitely review and address the suggestions you have mentioned.

Thank you for your continued support.

@Alex-Kushleyev Thanks for clarifying this!