Using a global .dir-locals.el file is a better alternative than
reincluding the same emacs header in every file of the project.

thanks to Tim Gold for reporting this

text revisions

The PSTR is already define as a NOP for all supported platforms. It's
only needed for AVR so here we remove all the uses throughout the
codebase.

This was automated with a simple python script so it also converts
places which spans to multiple lines, removing the matching parentheses.

AVR-specific places were not changed.

this fixes a bug where a mode switch change during an AUTO mission
which does not change the flight mode would cause cross tracking to be
reset, so the plane will not correctly follow the desired track

Many thanks to Michael Du Breuil for the log that showed this bug

setup the MODESWITCH channel as our OVERRIDE_CHAN, allowing for
instant manual passthru in px4io when OVERRIDE_CHAN goes above 1750

This makes for faster switching, and avoids bugs where a still enabled
FMU channel disables override

When arming we need to ensure that we don't enable any channels
otherwise PX4IO will think that FMU is active and will stop running
the internal RC mixer

using OVERRIDE_CHAN would cause a baro reset as it would mean we are
temporarily disarmed, and the "reset baro and GPS when disarmed" check
would reset the baro

Now we only do the mixer update if disarmed

this provides a convenient "real manual" flight mode

this allows both for testing PX4IO override on the ground, and for
forced manual override while flying, including re-arming after in-air
reboot

allows for mission control over inverted flight

this is just like FBWA, but with automatic roll/pitch tuning

having a command ID in them doesn't really make sense

Pair-Programmed-With: Randy Mackay <rmackay9@yahoo.com>

Pair-Programmed-With: Randy Mackay <rmackay9@yahoo.com>

the FrSky X8R receiver will briefly give a PWM of 874 on channel 5
when connection is lost to the transmitter. We need to ensure this
doesn't cause a mode switch

the mode would not revert if the switch was in position 0

use ch3_counter not just the final flag

this makes the logic a bit easier to follow

this prevents the receiver causing a temporary mode change

this does a full mission reset (equivalent to rebooting)

this prevents us resetting key integrators on waypoint change, while
still preventing old integrators being used when a PID starts to be
used again