Posts made by Eric Katzfey

@kestrelsystemsbp Take a look at Python MPA interface: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/tree/dev/python?ref_type=heads

@Sam-Kiley Yeah, try dpkg --force-all -i <package-name>

@Sam-Kiley our fork is based on pre-1.14.0 PX4. But mainline PX4 now runs on VOXL 2 at (almost) feature parity so the voxl-mainline-px4 package bundles up a mainline version (in this case v1.16.0-rc1).

@Sam-Kiley Not sure, we haven't tried that one yet. Since it works with voxl-ardupilot that pretty much confirms that it is wired up properly. You could try with a mainline build such as: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.16.0-1.0.2-202505070835_arm64.deb

@h3robotics I've been using v2.5 on my development machine and it works fine so v2.7 should also be fine. (Dang, I need to update )

@h3robotics I'd just try with v2.7

@shawn_ricardo To figure out which service could be causing the issue just try starting each one and see which one causes the issue.

@h3robotics This is the first request we've had for such a feature. It shouldn't be too hard to add that feature into voxl-mavlink-server. All of the fundamental pieces are there. It is open source and we accept PRs. If you would like to add that feature yourself and submit a PR for it that would be great!

@shawn_ricardo Can you capture the log of startup messages for voxl-px4-hitl so I can look for any error messages, or incorrect settings?

@shawn_ricardo I just tried it and it worked fine. But I had all services disabled except for voxl-wait-for-fs, voxl-mavlink-server, and voxl-cpu-monitor. So maybe try that.

@shawn_ricardo I'll try it on my setup and see what happens.

@shawn_ricardo What command did you use to start HITL? Are you trying hold mode with GPS?

@will-huang-oksi On VOXL 2, if you enter the command px4-listener sensor_gps what do you get? (Try it a few times)

@will-huang-oksi We have setup routines to do all of this on our drones. But if you are making your own drone then you have to know how to set those values up yourself.

@will-huang-oksi You need to set some parameters, calibrate sensors, etc. to properly setup PX4 for flight. If that hasn't been done then QGC will show those tabs in red indicating that you need to address something. If you set SYS_AUTOSTART to 4001 does that make the Airframe tab change from red?

@will-huang-oksi Can you share a px4 flight log? How do you have the parameter SYS_HAS_GPS set?

@will-huang-oksi Don't worry about the missing parameter warning in QGC. VOXL 2 is slightly different in it's operation from standard microcontroller based boards and it doesn't use all of the same parameters which confuses QGC a bit.

@h3robotics What is the setting of the VOXL_ESC_PUB_BST PX4 parameter? If you issue px4-listener battery_status from the command line what do you get?

@Quetzalcoatl We have used mavsdk running on VOXL2 (versus on the PC). Some documentation is here: https://docs.modalai.com/mavsdk/. An example Python script is here: https://github.com/mavlink/MAVSDK-Python/blob/main/examples/takeoff_and_land.py. Hopefully this information can help you resolve your issue.

@Jetson-Nano How are the VOXL_ESC parameters set on your FCv2? There could be a UART baud rate mismatch between what FCv2 is using and what the ESC is using.