Posts made by Eric Katzfey

@Alex-Kushleyev If I log the vehicle_imu topic within PX4 at full rate I see exactly the same distribution of timestamps.

@KLindgren Why do you think there are dropped messages? That is just the rate that the data is being produced within PX4. The Mavlink HIGHRES_IMU message is constructed based on the internal vehicle_imu topic which publishes at that rate. It is slower than the rate that IMU samples are being generated by the IMU driver.

@Steven-Girouard Are you using PX4? ArduPilot? You could run that directly on the VOXL 2 mini depending on what your IO needs are.

@Sam-Kiley No need for any voxl-io configuration. voxl-io-server is for use with PX4, not ArduPilot. The ArduPilot firmware will detect if there is a VOXL ESC connected or a VOXL 2 IO board connected. If it detects the IO board then you will have up to 8 channels of PWM available.

@ravi The documentation has been updated. If you are running a recent release from us then you will be using the ICP-20100 barometer. The BMP388 will not be started.

@ravi The ICP barometer should be working. The issues on the VOXL2 mini are related to temperature since it is on the same board as the Qualcomm device that creates a lot of heat on it's own so not applicable to flight core. Why do you say that it is not working? Is the sensor_baro topic being published? What software version do you have loaded on the flight core?

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.

@roy-crosthwaite Can you swap GPS units with the working one and verify that it fixes the issue?

@psafi I just built voxl-px4 with the lis3mdl driver and when I run it the command fails because it fails the probe (I don't have that magnetometer) but otherwise runs normally.

@psafi And how did you load your updated build to the VOXL 2?

@psafi If you disable the px4 service (systemctl stop voxl-px4) and then start it from the command line (voxl-px4 -d) what output do you get? And if you disconnect the magnetometer from the system how does that change things? Remove the start command from voxl-px4-start and enter it after px4 starts from the command prompt to see what happens.

You can obtain Hexagon SDK 4.1.0.4 for the flight controller build environment described in this document: https://gitlab.com/voxl-public/rb5-flight/rb5-flight-px4-build-docker at the ModalAI developers web site under EULA protected downloads in addition to getting it directly from Qualcomm. https://developer.modalai.com/asset/view/184

@psafi Those should only be there on the Nuttx platform.

@psafi Looks like it will compile if you comment out the #include <debug.h> lines in both lis3mdl_i2c.cpp and lis3mdl_spi.cpp

@Jetson-Nano Here is some (admittedly sparse) documentation: https://docs.modalai.com/voxl-streamer/#running-multiple-instances

@psafi In this case we don't use voxl-mavlink-server directly because we are essentially setting up a "mavlink device" straight into px4.

@psafi Some of it is just standard PX4 stuff so you can take a look at their documentation. For voxl-mavlink-server this may help: https://docs.modalai.com/mavlink/

@psafi Yes, unfortunately it is a real pain to get the SDK from Qualcomm and you need that version.

@Jetson-Nano I'm sure it is related to your parameter settings. Take a look at our parameter settings for FPV drones and compare against what you are using: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/dev/params/v1.14/platforms/D0008_v5.params?ref_type=heads

@ashwin I'm not really understanding the issue. Mavlink has no limitation to send packets to a localhost address. On VOXL 2 we configure voxl-px4 to send to localhost but that is because voxl-mavlink-server is the application that actually sends the data to the GCS. At the GCS you will see each connection with a unique IP address.