@Alex-Kushleyev So I have a BMI088 plugged in there, so I was adding IMU4 to not lose support for MPU as well. However, I did as you suggest as a sanity check, and yes I can see it trying to clock. I must have a problem somewhere else, thank you this was very helpful.

voxl-mapper is an example of taking TOF point cloud data and exercising path planning

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.

Oh wow, I totally overlooked the fact that the mavlink server seems to have been disabled during upgrade. Anyway thanks for the more up to date repo link, that might be very useful

@janis_blank No, the needed SPI driver for the Lepton that goes in that socket has not yet been created.

Hi Joe! We're most of the way through a big update that'll make all of our packages able to run on multiple architectures, this release will be paired with a system image update. If you'd like to manually build the latest from our gitlab in the meantime, simply add the line arch arm64 7 to /etc/opkg/arch.conf and then run opkg update on voxl.

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)

@Adrian-Hidalgo @Eric-Katzfey Thanks for the reply, much appreciated. I'll give that a go.

@Zeev-Mindali apq8096

Hi! The hardware on voxl only supports a stereo pair out of the J3 connector. However, you could absolutely plug in fisheye cameras instead of the pinhole ones if you're just trying to get a better field of view. Additionally, the system is setup to be able to support that same ov7251 camera in both the J2 and J4 ports, so you could in theory have 4 fisheye cameras concurrently. NOTE: voxl-camera-server (opensource) is not set up to to handle multiple cameras of the same type since we don't actively support any camera configurations like that. It's very doable though, you'd have to check the camera IDs for the configuration that you create and mod camera server if you're trying to use our standard software stack (so you can out of the box support 3 fisheye cameras, and it would only take some userspace coding to support 4)

If you're not heart-set on monitoring these externally, we already have a voxl-cpu-monitor process that will monitor the temperature, utilization, and frequency of the cores. You can see an in-terminal display of these values with voxl-inspect-cpu, and the source is a good way to see how to monitor this data within a c program. As for the cutoffs, the system tries to maintain under 100C (so you should never see anything above this reported in software), if it does start to get above this, the PMIC will start removing power and shutting off cores. It's generally pretty hard to actually trigger the PMIC even under heavy loads as long as there's any sort of heat distribution around the voxl. The only time's we've done this in the lab in the last 2 years is with a seeker sitting on a desk, even the propwash in flight is enough to cool it.

@Avihay-Gil There is a fairly in depth tutorial on how to use the hardware in the loop simulation software on YouTube here: https://www.youtube.com/watch?v=-uoIxAkiYtk

Hi @Jimk_Aero , Sorry to hear about the problems. Not being able to power off USB does make this hard and is a carry over from the VOXL Flight.... Even without ESC calibration, you can manually attempt to spin a motor, if using PWM, via this: https://dev.px4.io/master/en/middleware/modules_command.html#pwm Do you have an oscilliscope? You could probe the PWM channel output pretty easy (pins 2-5 for a quad) and see if you see any signal coming out of the board. If there's no signal, when you expect it, on a single channel, try to look at those ESD diodes right next to the connector and check for any fried parts. PX4 FW version you are running? There are two programs to handle some edge cases, px4-esc-cal-tool-v1-11.py and px4-esc-cal-tool.py

The VOXL is an open, Linux-based platform. You can change almost anything in software you would like. The source at https://code.modalai.com is provided for reference, and our customers often modify to their use case.

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

@modaltb Thank you for your answer, it is true that the problem is caused by the lack of magnetic compass.