Posts made by Moderator

@Viktor-Gal have you read through the troubleshooting VIO documentation? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

@LucaVertiq Hi, sorry you're running into issues. You should probably try the unbricking process https://docs.modalai.com/voxl2-unbricking/

@Wesley-Gunawan did voxl-inspect-cam show anything while voxl-camera-server was running? it looks like you restarted voxl-camera-server while voxl-inspect-cam was running.

I think the proper steps are:

1. update config (done)
2. reboot VOXL 2
3. run voxl-inspect-cam -a

there is still a lot of churn on the APIs, etc. which makes it difficult to document and support comprehensively

@Wesley-Gunawan Can you please set and run inspect-cam again?

"en_preview": true,

"en_snapshot": false,

@Wesley-Gunawan that looks like it's running properly. Can you open another terminal and run voxl-inspect-cam -a ?

@Wesley-Gunawan It looks like you are using a C08 config. https://docs.modalai.com/voxl2-camera-configs/#c8---hires-only

Have you tried voxl-configure-cameras 8 ?

voxl-camera-server documentation for troubleshooting recommends running voxl-camera-server -d0. Can you try that and paste the output?

@Bilal-Hussain Hi Bilal, USB is a wired protocol, typically limited to a few meters. The range you would achieve would be dictated by the radio, and not the USB interface

@Aapo_Rei Hi Aapo, all of the source code is open so folks can extend to suit their needs. We're happy to take merge requests. You could start by looking here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2/-/blob/master/colcon_ws/src/voxl_mpa_to_ros2/src/interface_manager.cpp?ref_type=heads

@david-moro Yes, absolutely. if you are OK posting it here we can take a look or if you'd like to email the schematic to contact --at-- modalai.com we could take a look that way as well

@Wesley-Gunawan can you please share a picture of your setup? It needs to match a camera config found here: https://docs.modalai.com/voxl2-camera-configs/

Often when a camera can't be found:

1. it's installed backwards
2. the cable isn't fully connected or the connector is damaged
3. the wrong camera config has been configured during setup

@John-Nomikos there's really nothing we can do to affect the SD Card write speed. It's directly connected to the Qualcomm chip

@swickliff it is most likely a damaged connector or similar somewhere. If there is an issue with camera connectivity it can prevent the board from booting. The connectors on the flex cables are very fragile and are only designed for about 10 insertions, after that they can become unreliable. They aren't meant for moving around a bunch.

Also, if you try to daisy chain cables together there can be signal integrity issues as there is a maximum length of MIPI around 25cm

In general, everything is tested prior to shipping. You could have a bad cable in there somewhere

Can you please share a picture of your setup?

@Usama-Hamayun you can order the drone without battery.

The Starling 2 and Starling 2 Max both use the same battery packs. They can be either Sony VTC6 or Amprius 18650 cells

@Rowan-Dempster I think it is safest to just not use data that reads 0,0,0 as the sensor cannot measure that close anyways

@Kiazoa-Joao Hi Kiazoa, drones can be very dangerous, especially if you don't understand how they work. These drones are designed for software development and are not consumer products. Configuration, and potentially coding, are required for them to operate to their potential.

You are likely referring to flying with VIO https://docs.modalai.com/flying-with-vio/

Please make sure the VIO system is working well before trying flight. Then please be careful and follow the safety guidelines: https://modalai.com/safety

@ayrric yes, you can find it here: https://www.modalai.com/products/m0155

@nuallaino you can see how that error is generated here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/main.cpp?ref_type=heads#L683