@Uros . .

I think we found the issue. this version of the holybro compass has the magometer mounted upside down and turned 90 right. we were able to orient the sensor in QGCS. thanks for the help

@mbahrami Modal AI ESC&2203.5 -- I don't see any reason why this wouldn't work. Battery voltage selection depends on how fast you need to spin the given prop of choice to generate sufficient lift/performance you need in your platform. If you spin the motor at one speed with 3S and that generates the performance you need then go with that. If you move to 4S and in doing so get the performance you want in terms of speed, endurance etc then go with 4S. Really depends on what your goals are. You can pick up a variety of battery pack configurations from any drone/FPV store and try those out -- just make sure you match your connector or get an adapter. Here are some posts on USB Cameras. I have tried this with some -- it works. https://docs.modalai.com/uvc-streaming/ https://docs.modalai.com/voxl-streamer/ For something like the Zed2 you probably need some custom drivers on the VOXL to work properly. Re: other color cameras -- defer to the ModalAI team on those. Hope this helps, Steve

Please follow the documentation here and provide an update. Specifically the troubleshooting tips might help your arming issue.

last question : I could not see the point cloud with stereo , but since I need it to indoor solution, I will use tof anyway. I using the drone without any GPS module (don't need it) but I could not to change from manual to mission nor off board. when I change the gps to rc transmitter (first option) I was able to get move to mission but only left stick worked (up down rotate) the second stick won't work (forward and rotation) is there a way to move to mission without gps module?

too much setting with ads shell. I started to wrote entire web application, so I can change the values like every normal device have (such as routers) too many parameters to work with in add shell.

sweet, i connecting to modalai voxl flight deck, i receiving it today, just wanted to be sure that i connecting the correct battery. already add support for java, rest (with java spring), python and js/node.js. changed also the web server to react with easy access. i will share with you my code (basicly a docker on same network)

There is MAVROS and MAVSDK which might help with what you are looking for https://docs.modalai.com/mavros https://docs.modalai.com/mavsdk

Hi Paolo, we do not have the GPIO interface implemented in python. We do have the i2c interface implemented in python and you could use that as a basis for accessing the GPIO interface. Source code here: https://gitlab.com/voxl-public/core-libs/libvoxl_io/-/tree/master/lib/python

Not sure if USB is exposed into your VM, or if that is possible? Can you type $ lsusb And share if anything shows up?

@Chad-Sweet I could`nt access odometry data via telemtry.

We have never tried that radio, but you are likely correct. The list of receivers tried is on our documentation here

Thanks Alex. Mainly wanted to check if this was a known issue with hardware or the AE algorithm. It is strangely repeatable on this flight deck. Works indoors in pretty extreme high contrast, fails outside in hazy/overcast conditions. Another flight deck was working well in the same/similar conditions. We've ordered some more hardware and will follow up after doing more testing with AE settings.

@Chad-Sweet I have tried with flysky receiver also but it's not working. Please suggest the receiver which is compatiable with flight deck.

There should be no expectation that VIO will work at night, it is a computer vision system that relies on visual features. Please see details here on troubleshooting VIO: https://docs.modalai.com/flying-with-vio/#troubleshooting-vio

The Flight Core portion on the Flight Deck is very similar to a standard Pixhawk with very close to stock PX4. There are 8PWM, so if you assign all of them to motors in an Octo configuration, it should work as any other PX4 flight controller would work.

ADB was not connected. After connecting the fastboot board, it turned out to turn on the device in fastboot mode. After connecting in the fastboot mode manually, using the fastboot command, the disk partitions were flashed, as is done in the install.sh script. Problem solved

Here is our rma page to follow: https://www.modalai.com/pages/rma?_pos=2&_sid=4b1e0e876&_ss=r