Posts made by Eric Katzfey

@jmltt For reference, here is a commit that will allow our fork to build for SITL on Ubuntu 24.04: https://github.com/modalai/px4-firmware/commit/8366d2e56c171230ee31c0856cb243d46f09de31

@schew The ESC states are as follows:
0: idle / not spinning or trying to spin
1: spinning up
2,3: unused
4: very brief transition between spin-up and full back-emf sensing mode (user's commands are not yet executing)
5: back-emf sensing mode (rpm or power control based on user's command)
If there is any issue that causes ESC to think it's stalled or communication timed out, it will go through state 0 and then to 1 if non-zero commands are sent via UART.
The typical start-up sequence is basically 0->1->4->5 and should stay at 5 until you send a zero command or stop sending commands.

@YUUJI-INOUE Can you send a PX4 log? If you can arm in manual mode then the PX4 IMU is working fine. The last voxl-px4 message sequence shows the IMU start correctly. If the parameters file does not yet exist (e.g. no PX4 parameters have been updated yet) then there will be no /data/px4/param/parameters file and you will see the error message: "open '/data/px4/param/parameters' failed". That is fine and to be expected. Once you have updated some parameters (e.g. running voxl-px4-param) then that file will be created and that error message will no longer appear.

@alan123 Are you starting voxl-px4 from the command line (e.g. voxl-px4 -d) or is it starting automatically from a systemd service file on startup. If you have started it from the command line you can enter commands from the px4 shell. So, after the script is done, you can enter gps status to see that the driver is doing. If the driver hasn't been started, try starting it directly from the command line.

@alan123 Well, is PLATFORM = M0052? Seems like you are still executing the qshell one. And the command isn't setup correctly, should be gps start -i spi -d /dev/spidev14.0

@alan123 If you are starting it on apps side the you use gps start -d <device port>. If you start it on DSP side then you use qshell gps start -d <device port>. For /dev/spidev14.0 you have to start on the apps side. Also it defaults to UART so if you want SPI then you will need to add -i spi to your start command.

@Muqing-Cao In the voxl-vision-hub configuration file /etc/modalai/voxl-vision-hub.conf how is the parameter en_vio set?

@voxltester That is not a normal option to choose via voxl-px4.conf. You will need to hand modify the startup script /usr/bin/voxl-px4-start to properly start the driver in i2c mode. Use option -b 4 to select that i2c bus.

@remill libusb doesn't use cmake. It uses autogen.sh, configure, make, etc. These are standard Linux build tools. If you enter a query such as "How do I build libusb on Linux?" into Google and check AI mode it will provide you with all the steps.

@Nitin-Varma-Vegesna If you are just flying in manual or altitude hold modes then those shouldn't be an issue.

@voxltester Only if it is connected to a GCS that sends the Mavlink SYSTEM_TIME message.

@Nitin-Varma-Vegesna I think it's this one: https://store.3dr.com/mini-gps-ublox-max-m10s/

@mkriesel First steps would be to verify that the correct propellers are installed, that all the propellers are spinning in the correct direction and that the motors are mapped correctly.

@Nitin-Varma-Vegesna None

@Nitin-Varma-Vegesna In /etc/modalai/voxl-px4.conf set GPS to NONE. Then set the PX4 parameters SYS_HAS_GPS, and SYS_HAS_MAG to 0. Set EKF2_MAG_TYPE to 5. Set EKF2_GPS_CTRL to 0. Then reboot and see if the preflight error is cleared.

@remill said in Different package version from voxl-cross and Voxl2:

1.0.27

Perhaps you can build the desired version of libusb from source and install it? We have used this approach for a variety of other "third party" libraries. Examples are here: https://gitlab.com/voxl-public/voxl-sdk/third-party?page=1

@박지현 Unfortunately, for Ardupilot, our ESCs are only supported with UART interface when using the VOXL 2 / VOXL 2 mini as the flight controller. When using Flight Core v2 that is not supported.

@Hunter-Scott Can you update to SDK 1.6.0? Then do the ver all and qshell voxl_esc status commands again and attach the output?

@voxltester It uses the NTP to update time and date. So, once you have an internet connection, it will update.