-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rover no longer supported? #15711
Comments
Which pixhawk board are you using? |
A Pixhawk 1 board |
You're right it was removed for FMUv2. It is possible you have a Pixhawk 1 that can be upgraded to use FMUv3 - that is the first thing to try: http://docs.px4.io/master/en/config/firmware.html#bootloader @dagar Is it possible to get Rover on FMUv2? If so, how? |
I tried to upgrade the bootloader but I couldn't. I guess the Pixhawk 1 is an early version. |
There's a dedicated |
@dagar So would the short term solution be to modify the source code to remove that line and build px4_fmu-v2_rover yourself? |
@dagar ^^^ |
Is generic rover (50000_generic_ground_vehicle) sufficient? If that's all then yes let's remove the exclude so that px4_fmu-v2_rover can function. I have some ideas for a better overall airframe inclusion (and organization) method, but that will take longer. |
- this allows px4_fmu-v2_rover to function until we have a better mechanism for including or excluding ROMFS dependencies #15711
I tried installing the latest firmware from the "master" branch today via qgroundcontrol onto an old pixhawk 2.4.8 (px4 fmu v2). The firmware should have the fix now, but alas, I still cannot switch to the "generic ground vehicle" frame, with the exact same symptoms as described by the OP. |
- this allows px4_fmu-v2_rover to function until we have a better mechanism for including or excluding ROMFS dependencies #15711
- this allows px4_fmu-v2_rover to function until we have a better mechanism for including or excluding ROMFS dependencies #15711
- this allows px4_fmu-v2_rover to function until we have a better mechanism for including or excluding ROMFS dependencies PX4#15711
Fixed in #15849 |
I've loaded the lastest Firmware version (1.11.0) in a Pixhawk board and, when I tried to choose a "Rover" frame, the option did not show up. So I followed the instructions in https://discuss.px4.io/t/airframes-rover-bug/6267/3 and deleted the PX4AirframeFactMetaData.xml file in C:\Users\User\AppData\Roaming\QGroundControl.org
It now shows the option to select a "Rover" frame, but when I select it and click apply and restart, the board does restart but nothing else happens, the software still shows me the following image, as if I did not choose an airframe:
I tried with other versions of the 1.11.0 firmware too, such as the beta testing and developer build, and had the same result.
I even tried to manually load the px4_fmu-v2_rover.px4 file and had the same result.
When I use an earlier version (i.e. 1.10.0) I don't have this problem:
Also, when I select another airframe such as a generic quadcopter x, it gets selected without any problem:
Any Idea how to fix this? Or should I give up on using the 1.11 version?
The text was updated successfully, but these errors were encountered: