Make sure to clear CBAUD before setting the baud and disable
input modifications.
Fix for #12162
This change removes input options that can modify the input data stream.
INLCR: map new line to carriage return
ICRNL: map carriage return to new line
IUCLC: map upper case to lower case
IGNCR: ignore carriage return
BRKINT: send SIGINT on serial break
This renames some of the TYPE parameter's driver options:
19 :BenewakeTF02 is unchanged
20: BenewakeTFMini becomes BenewakeTFMini/Plus-Serial
25: BenewakeTFMiniPlus becomes BenewakeTFMini/Plus-I2C
27: BenewakeTF03 is unchanged
- checking of space in send_to_active_channels was incorrect - did not
take into account locked status of the channel
- corrected return value on comm_get_txspace - took a uint32_t, cast it
to int16_t, checked it for zero, then cast it to uint16_t on return.
That's just... odd.
... unless we are in SITL
Users moving backwards and forwards between versions can hit this case
too easily.
We probably need a better story around this error loop so it's less
confusing to the user about what's going on.
Adds the dynamic harmonic notch filter and static notch filter to the Solo's default parameters. PID tuning parameters for the green cube Solo adjusted to take advantage of the better control.
Trying to get correct version of pymavlink (i.e. the one with messages
references in our mavlink repository)
As-is, if there is a pymavlink release after the one references in the
ardupilot repo, we don't pick up any new messages in the Python
bindings.
The _TYPE change is to remove the "v2" from the LidarLite description because both v2 and v3 are supported
The _PIN change is to make it more clear that any of the auxiliary pwm pins can be used for PWM input
Michael du Breuil
Andrew Tridgell
Randy Mackay
Daniel Magree
Patrick José Pereira
Peter Barker
Henry Wurzburg
Matt Lawrence
Pierre Kancir