Topics created by jconk

I was able to use the v1.13.2-0.1.1 file with mission planner, it connected but said update was not required. I will keep an eye out for the v1.13.2-0.1.2 drop. Looking into my compass setup, its a new release from MRO, could be an issue there

Nice work locating that setting, agreed it's not obvious to locate all of this info... Although this is VOXL2 documentation, the graphic here might be helpful to see the plumbing:

https://docs.modalai.com/voxl2-external-flight-controller/#component-overview

@Adrian-Hidalgo said in rx-tx from v2 to voxl:

px4_uart_bus": 12, for J11 connection

worked transmitting data now

Originally the FW update via QGC worked, and ideally that would be the way it works, but at some point the update stopped working (note that our bootloader didn't change).

The px_uploader tool to me uses the same protocol as QGC, and as this works, I have a hunch the issue will be QGC side, but the jury is still out while we track it down.

I decided to proceed to ship Flight Core v2 as I found the work around acceptable and had the work around publicly documented. I agree that our product line is still a bit bent towards power users at this point, so the use of git and such is a big ask for most people.

If you have the chance, with respect to this topic in particular on this thread, please let me know where you got stuck with this particular process with our documentation and then I can use that feedback to improve things.

https://docs.modalai.com/flight-core-v2-firmware/#how-to-upgrade-using-px_uploader-tool

@jconk If you're struggling with an issue you are more than welcome to create a post here with a description of the problem, things you've tried, things that aren't working, etc. and we will gladly help you resolve your issue.

It seems as though this is your first post on this forum meaning you haven't reached out previously.

We want people to succeed using our platforms and our team monitors this forum every day providing solutions.