Posts made by Eric Katzfey

@qubotics-admin First you need to determine the version of PX4 running. With ssh or adb you can run the following at the command line: px4-ver all. You will see PX4 version and Vendor version. So, for example, for px4 version 1.14.0 and vendor version 8.134.3 then you would checkout the tag v1.14.0-8.134.3-dev from the repo to see that commit.

@qubotics-admin It's in the voxl-fpv-dev branch of our px4 fork. See https://github.com/modalai/px4-firmware/blob/7e1625f20fac5f44a0034bebdb1e3d4027124684/src/modules/mavlink/mavlink_receiver.cpp#L108

@qubotics-admin The joystick button to use for turtle mode is set via the VOXL_ESC_T_ON parameter.

@cbay voxl-fpv-px4 is based on voxl-px4 but has some custom tuning code / parameters for our fpv drones that isn't in voxl-px4. So, it's kind of a superset. But there isn't anything related to low level i2c drivers so I have no idea how that could be causing this issue.

@bendraper Actually, if you try to build the dev branch in voxl-cross:V4.4 it works but you first need to initialize the submodule with git submodule update --init. Can you try this with the dev branch and see if it works for you?

@bendraper Yes, we can recreate the failure. We need to release voxl-cross 4.8. We're working on it.

@Karteek-Gandiboyina Also, for reference: https://forum.modalai.com/topic/4403/starling-2-max-with-ublox-f9p-ultralight/7?_=1772217162290

@Karteek-Gandiboyina Unfortunately, we don't have any experience with that unit. It looks like it is hooked up correctly since you get a response from it. What baud rate did you change it to? You can try running the latest version of px4 but we have spent very little time testing it so use with extreme caution: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.17.0-1.0.2-202602240859_arm64.deb. Perhaps load that, remove the propellers, and just verify that it can properly see the GPS? And what if you just remove the baud rate option on the start command, does that change anything?

@Sarika-Sharma We have a variety of parameters sets available in the voxl-px4-params repo https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/ However, they are mostly for either indoor or outdoor use. Older versions of PX4, like what our fork is based off of, had a hard time with external vision based navigation coexisting with GPS based navigation. Newer versions of PX4, supposedly, are much better at this but we have not spent the time to prepare a parameter set for that yet. You are free to experiment with our mainline PX4 build here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-mainline-px4_1.17.0-1.0.2-202602240859_arm64.deb. However, if you decide to use the mainline build, be aware that it is considered "experimental" at this point and has very little testing on voxl2 so use extreme caution.

@joshuagaus Sorry, but SBUS is not supported. That option will be hidden in future SDK releases to prevent confusion.

@Myles-Levine You should see an actuators tab. Do you have our standard VOXL SDK loaded on the drone?

@jameskuesel Thanks! Merged

@jameskuesel Feel free to make the change and submit a PR

@Eric-Katzfey And this is also handy: https://www.sparkfun.com/breadboard-to-jst-ghr-04v-cable-4-pin-x-1-25mm-pitch.html

@Gad-Levin We generally use HITL. There is some documentation here: https://docs.modalai.com/voxl2-PX4-hitl/. This is the repo with the most up to date HITL driver for VOXL: https://github.com/modalai/px4-firmware/tree/voxl-fpv-dev. There is some more info in the HITL driver README: https://github.com/modalai/px4-firmware/blob/voxl-fpv-dev/boards/modalai/voxl2-slpi/src/drivers/dsp_hitl/README.md. I'm sure there's some outdated / incomplete information in those documents but it should give you a pretty good starting spot. This is the cable I use: https://www.sparkfun.com/usb-to-ttl-serial-cable.html

@Myles-Levine Have you tried with the QGroundControl motor (actuator) spin tab?

@jon For MONOTONIC the apps side uses the slpi version so that they are in sync. Your application should use apps MONOTONIC. PX4 will convert it using timesync.

@Nitin-Varma-Vegesna Well, that's why I asked you to do the full SDK installation. If you install the SDK and set it up as we do from the factory then it should be working like when you first got it. If it doesn't then that potentially points to some damage caused by the crash and not some configuration change you have made since then.

@Nitin-Varma-Vegesna You can set parameters via voxl-configure-px4-params.

@kgn-mdlai Unfortunately, the April Tag code is quite outdated and hasn't been tested on any of our latest hardware. As it is now it is provided as reference code and if you are able to get things working correctly on your own we are happy to accept PRs to the repo. We do plan an update of this in a future revision of the SDK but there is no scheduled date that we can provide right now.