[davidreed0]

I'm trying to do a path planner for a fixed wing aircraft. I set flight mode 3 to be PathPlanner and I get the config error. The error just tells me to reduce the flight modes to narrow down which mode has the problem. I am not sure what else needs set up in order for it to not have an error. My board is Revo. It has an onboard mag sensor with errors less than 5%.

Sent from my Nexus 5X using Tapatalk

[f5soh]

Hi,

I assume you talk about a Revolution board, not a CC3D ?
Any GPS assisted mode need a compatible fusion algorithm, usually INS13.

If you cannot resolve your config error, post the config file: File > Export UAV data

[davidreed0]

OK, I'll try that. Sorry about the name. The Chinese site I bought it from threw all those keywords in so it's confusing. It is a Revo board though. Built-in mag and oplink. I'll try your suggestions after my flight I'm on right now.

[davidreed0]

Your suggestion worked. I think I had that set up right on 15.09 but didn't know it and didn't know it was related to the error I was getting. I would suggest another note in the error that says something about GPS modes needing an attitude estimation method set up in the attitude menu. It was not intuitive because I think of attitude as the orientation of the aircraft to the Earth's horizon. Every time I see something about attitude, I think of accelerometers, not GPS.

Thanks for your help though. I'll give it a try next time the boss let's me go fly

[f5soh]

I think the first message in SystemHealth, related to the config alarm is pretty clear ?



Second with [ ? ]

[davidreed0]

If I went to that screen, I suppose. When on the "flight mode switches" screen, the error just says to reduce number of flight modes to find the problem. I never left that screen because I was trying to solve it there.

[davidreed0]

If I went to that screen, I suppose. When on the "flight mode switches" screen, the error just says to reduce number of flight modes to find the problem. I never left that screen because I was trying to solve it there.

I suppose the fix could be as simple as the error telling you to check the system health widget.

[f5soh]

The config error button in flightmode tab was added to show instantly if something was wrong in config or user configure all and finally cannot arm.

SystemHealth still the reference for all alarms / config errors.

[davidreed0]

OK, didn't know that. It is very useful to know right there but then even more so, I also expect to find out the actual error there too. I'm a developer too but from a user perspective, it is more intuitive that way. My thought process was, "Wow, this error is so bad, the software doesn't even know what's wrong" which is why I asked on the forum.

[davidreed0]

Please don't take it as criticism. This software is really awesome but I just wanted to give user feedback. Hopefully people that have the same issue as me will find this post instead of asking it again.

I had looked all through the manual to see if I could find the answer and the verbiage is more tailored to multirotors so my first thought was that GPS type functions weren't available for fixed wings. Things like position hold, altitude hold, auto takeoff, and auto land are obviously more difficult to do with a fixed wing so that was also giving weight to my fears of no GPS functions.

[f5soh]

No need to quote a post just above

If i remember right Fixed wing was the first vehicle supporting autonomous features.
If you search for fixed wing and OpenPilot you will find some videos from 2011
In theory the fixedWing is more easy to implement because still flying forward so the mag is less important.

If you take a look at UAVOBrowser you can find:
- VTOLPathFollowerSettings,
- FixedWingPathFollowerSettings,
- GroundPathFollowerSettings