Some of the defaults diles we ship are setting RC, which they shouldn’t
Could change things such that arming check instead waits for all channels to be within deadband of trim values except throttle
Even throttle on unsprung transmitters
NE: Add a warning that the input is beyond range. Being within range just gives you reduced input.
RC calibration is used on Copter to determine whether we output to the motors
Removing the check might let servos move after frame is selected
Split rc3-min and rc3-max entirely from servo3-min and servo3-max on Copter
Mot-pwm-min and mot-pwm-max
Can’t just change the defaults
Repacking parameters?
Doing stuff atomically makes this difficult
RL: Michael, what exactly is the root problem here? I missed it.
[9:34 AM] Muted.
[9:35 AM] (Channel) MdB: Rob: My transmitter by default has min 1100 max 1900 which meant the check failed even though I did calibration
[9:35 AM] Unmuted.
[9:35 AM] Muted.
[9:35 AM] (Channel) JW: if your rc calibration lands on the default values, they aren’t committed to non volatile memory and then are not flagged as saved, and you fail the ‘rc calibrated’ check
[9:35 AM] (Channel) LV: @Robert, the problem is that we got a plane guy going for a racing quad
[9:35 AM] (Channel) MdB: Changing TX is ofc easy, but its not an obvious reason why it failed, and when I looked it up on the internet I just found piles of confused users
[9:35 AM] (Channel) MdB: So I decided it was a real problem and brought it up
[9:35 AM] (Channel) JW: The bit about using RC3 seems like the confusing bit to me
We should be enforcing ESC calibration rather than this stuff!
Change things:
Arming check will be on mot-pwm-min and mot-pwm-max
Put Michael’s new flag on mot-pwm-min and mot-pwm-max
Most escs have 1000-2000
So we should use those as defaults
This way we’re checking the ESC range
We’ll have the correct arming failure!
So:
Mot-pwm-min-max will be copied from rc3minmax
If they’re in storage
One-off-check at startup rather than in polling
Remove checks for rc calibration
Don’t apply this PR at this time
Remove storage check retain the range check!
MdB: Jacob: Forget my force save patch, automatically set the MOT_PWM min/max to the RC3 values if RC3 had been set before, then remove the configuration bit of the rc_checks.
(Basically force all vehicles to have configured MOT_PWM_MIN/MOT_PWM_MAX period and not use the RC3 range)
New process required for calibrating escs to set mot-pwm-min and mot-pwm-max
DJI ESCs have fixed range
Calibration will need to write values
Quadplane has two lots of min/max
This is not absolutely urgent
But we’ll want to chase this as running out of parameter space will be dire
[10:30 AM] (Channel) Michael_duBreuil: Other people attending with booths: Rob and myself
Youtube partner’s video playlist would be a really good idea!
Jeff’s working on allowing us to use the AUVSI logo
Early-registration for next year will be done
Need to worry about interdrone next
Tables and chairs this time…
Jeff is short on time but can show up
There’s a Skype chat for this
UTC0034 - GSoC
Interviews are underway
Meet again after this meeting to do selections
We have n slots - do we have sufficient mentors?
Please contact Jaime
Will also bug people directly for specific projects anyway
Looking forward to good ROS integration improvements
Do we build and ArduPilot ROS bridge or continue using MAVROS?
UTC0044 - Randy and Copter
Copter 3.5.6 beta coming for safety switch changes
Maybe tomorrow
Probably a regular week of testing
3.6 beta testing after that
Request for other bits and pieces to go in
Including tradheli and attitude controller filtering
Will start 3.6 testing without those
Wants set-time PR for 3.6
UTC0046 - Randy and Rover
3.3 beta coming soon
Again, set-time PR
UTC0047 - set-time PR
FF’s already had a look at it
Move to under BRD_
Putting PPS-pin into the RTC parameter space
(Channel) JacobWalser: I think a gcs application (ex residing on a companion computer) should have some reasonable level of certainty of the right time before sending the message
[10:56 AM] (Channel) Michael_duBreuil: But its unreliable
[10:56 AM] (Channel) Michael_duBreuil: (It’s only better over long periods)
Knock-off-board’s crystals can be very ,very bad
100-200ppm is reliably a crap crystal number
Not being temperature-compensated can also cause drift
Good crystals?
Cost-gradient…
10 or 20 ppm
UTC0100- tridge and Plane
Tridge is writing the release announcement for next 3.8 release
Tridge would like to do 3.9 off master soon
Dual release, px4 or ChibiOS
UTC0100 - EKF3 as a default setting?
Already the default for tailsitters
Ditching an EKF on the px4-v2 for space reasons?
UTC0103 - Lidar as primary height source problem
Only while landing (Plane)
We don’t support any other use
Range issue on most lidars traditionally
70m to 100m very few lidars are reliable at that range