@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.
@clange Yes, definitely. All the support to build a Debian package for installation is in https://github.com/ArduPilot/ardupilot/tree/master/libraries/AP_HAL_QURT/packaging
@Hunter-Scott When you swapped in the power module board did you update the px4 configuration file in /etc/modalai/voxl-px4.conf? In that file, how is POWER_MODULE set? For the power module it should be POWER_MANAGER=VOXLPM. For standard Starling 2 Max configuration it should be NONE. Can you stop voxl-px4 running as a service systemctl stop voxl-px4, wait a few seconds, then run voxl-px4 from the command line in non-daemon mode with voxl-px4 -d and let the startup script run through. At the command prompt type ver all and qshell voxl_esc status and then include all of the output here? In the log that you sent that did have battery_status, where did that come from? A different drone?
@aspen The landing detector in PX4 isn't perfect (obviously) so in this case it didn't detect the landing. I would map one of the switches to toggle between arm and disarm so that when the drone lands you can disarm via switch. Did you try the v1.16 package?
@aspen Can you provide the log file? There is a version of px4 v1.16 available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.4-202509030932_arm64.deb
@Hunter-Scott If you delete all logs then fly you don't see any log files afterwards?
@Muqing-Cao Just the standard Mavlink ODOMETRY message is what we have used. Not exactly sure how that translates into ROS land. But it isn't anything ModalAI specific.
@Muqing-Cao Yes, definitely. The applications are auto started using systemd services and can be stopped / disabled using standard commands as desired.
@Hunter-Scott The log you provided contained battery_status
@taiwohazeez Are the propellers spinning in the right direction? If they are attached in the correct place, the motors are spinning in the correct direction, and they are spinning faster than another flying drone then physics says it will fly also.
@Hunter-Scott Can you supply a px4 log file?
@taiwohazeez Could the propellers have been removed and replaced such that they are no longer in the proper position? If they are reversed they will be trying to push the drone down instead of up.
@Jetson-Nano Okay, well we don't support that right now. If you want to make your own build then you can probably just replace all of the files in the src/drivers/actuators/voxl_esc with the files from the voxl-fpv-dev branch.
@Jetson-Nano It's hard to follow what you are asking. Are you trying to add turtle mode to another ESC driver? Are you trying to get turtle mode working with a joystick and VOXL ESC?