set_wp_destination clear yaw target
limit velocity and acceleration based on track slope
add is_active() and remove unused reached_spline_destination
init accepts desired speed
set_kinematic_limits uses current speed limits instead of defaults
add time compression to prevent target moving too fast for air
implement alternative spline
remove vel-target-length
set_wp_destination always calculates this leg
set_kinematic_limits moved to scurve
fix origin speed after spline segment
spline terrain following fix
handle s-curves with mismatching alt types
fix set_spline_destination_next
add update_track_with_speed_accel_limits
Change to next waypoint at corner apex
use scurve advance along track
remove unused definitions and out-of-date todo
set_spline_destination_next sets fast_waypoint
scurve origin speed set from spline target velocity
fixup takeoff delay
SCurve const more local variables
rename update to get_jerk_vel_pos_at_time
removed unused update
debug output in SITL
fixes to ensure finished at end of path
fixes including validity check
includes corrections from peer review
this is intended to catch problems where we have unexpectedly received
invalid arguments. For example an out-of-bounds target speed that
should have been caught somewhere else.
running out of bits so we use a single bit to capture invalid inputs to or output from a calculation
indent is not available on our documentation server:
[build_parameters.py]
Traceback (most recent call last):
File "./param_parse.py", line 422, in <module>
do_emit(XmlEmit())
File "./param_parse.py", line 415, in do_emit
emit.close()
File "/home/wiki/build_wiki/ardupilot/Tools/autotest/param_metadata/xmlemit.py
", line 24, in close
etree.indent(self.paramfile)
AttributeError: module 'lxml.etree' has no attribute 'indent'
If the RTC time we reset parameters (STAT_RESET) is zero then we reset all parameters.
In SITL we only set that time if we see a GPS due to the AP_RTC RTC_TYPES parameter default bitmask value of 1
So if you reboot SITL fast enough while STAT_RESET is zero you can see that STAT_BOOTCNT does not increase. Easily reproducible in SITL; start with -w and type reboot in several times before SITL sees the GPS come up and you can see STAT_BOOTCNT doesn't increase.
Fix is to ensure STAT_RESET is non-zero before rebooting.
this fixes an issue with bad read of WHOAMI on a mRoPixracerPro. We
don't know how the sensor gets in a state where WHOAMI can't be read,
but toggling CS does fix it