Plane 4.5.0-beta release


We have just released plane 4.5.0-beta1. This is a major release with a huge number of changes.
The most visible change for plane users in 4.5.x is that we have renamed a significant number of parameters and changed them from centimeters and centidegrees to meters and degrees. Not all centimeter and centidegree parameters have been done, only those that are specific to plane users. For 4.6.x we are aiming to change the common parameters between plane, copter and rover too, eventually ending up with no centi- parameters.
When you upgrade to 4.5.x ArduPilot will automatically convert any existing parameter values you have for the affected parameters to the new name and automatically re-scale where the parameter has changed from a centi- parameter.
This is a very big release and we expect it to be in beta for a couple of months. We would greatly appreciate feedback from testers!

Parameters renamed and rescaled

  • COMPASS_DISBLMSK replaces COMPASS_TYPEMASK
  • STAT_BOOTCNT replaces SYS_NUM_RESETS
  • AIRSPEED_CRUISE replaces TRIM_ARSPD_CM
  • AIRSPEED_MIN replaces ARSPD_FBW_MIN
  • AIRSPEED_MAX replaces ARSPD_FBW_MAX
  • CRUISE_ALT_FLOOR replaces ALT_HOLD_FBWCM
  • LAND_PITCH_DEG replaces LAND_PITCH_CD
  • MIN_GROUNDSPEED replaces MIN_GNDSPD_CM
  • PTCH_LIM_MAX_DEG replaces LIM_PITCH_MAX
  • PTCH_LIM_MIN_DEG replaces LIM_PITCH_MIN
  • PTCH_TRIM_DEG replaces TRIM_PITCH_CD
  • Q_LAND_FINAL_SPD replaces Q_LAND_SPEED
  • Q_PILOT_ACCEL_Z replaces Q_ACCEL_Z
  • Q_PILOT_SPD_UP replaces Q_VELZ_MAX
  • Q_PILOT_SPD_DN replaces Q_VELZ_MAX_DN
  • ROLL_LIMIT_DEG replaces LIM_ROLL_CD
  • RTL_ALTITUDE replaces ALT_HOLD_RTL

New autopilots supported

  • ACNS-F405AIO
  • Airvolute DCS2 onboard FMU
  • Aocoda-RC-H743Dual
  • BrainFPV RADIX 2 HD
  • CAN-Zero
  • CM4Pilot
  • CubeRed
  • Esp32-tomte76, esp32nick, esp32s3devkit
  • FlyingMoonH743
  • Flywoo F405 Pro
  • FlywooF405S-AIO with alternative IMUs
  • Here4 GPS as flight controller
  • Holybro 6X revision 6
  • Holybro6X-45686 with 3x ICM45686 IMUs
  • JAE JFB110
  • KakuteH7 using ICM42688
  • PixFlamingo (uses STM32L4PLUS CPU)
  • PixPilot-C3
  • PixSurveyA1-IND
  • QiotekAdeptF407
  • Sierra TrueNavIC
  • SPRacing H7RF
  • SW-Nav-F405
  • YJUAV_A6
  • YJUAV_A6SE, YJUAV_A6SE_H743 Plane

Autopilot specific changes

  • 1MB boards lose features to save flash (Payload Place, some battery monitors, NMEA Output, bootloaders, Turtle mode)
  • CubeOrangePlus supports IMU high resolution sampling (works with ICM42688, ICM42652, ICM42670, ICM45686 IMUs)
  • F4 processors with only 1 IMU gain Triple Harmonic Notch support
  • F765-SE bdshot support on 1st 4 pin
  • F7 and H7 boards lose DMA on I2C ports (not required, limited DMA better used elsewhere)
  • FlyingMoonH743, FlyingMoonF427 2nd and 3rd IMU order swapped
  • HEEWING-F405 supports CRSF
  • MatekL431-RC bootloader added, DMA used for RC and GPS
  • PH4-mini, PH4-mini-bdshot, Swan-K1 and TBS-Colibri-F7 BRD_SER4_RTSCTS param conflict fixed
  • Pixhawk6C supports BMI088 baro
  • TMotorH743, Heewing-F405 serial parameter definitions fixed

AHRS/EKF enhancements and fixes

  • AHRS_OPTIONS supports disabling fallback to DCM
  • BARO_ALT_OFFSET slews more slowly (was 20sec, now 1min)
  • EKF2 removed (can be re-enabled with Custom build server)
  • External AHRS support for multiple GPSs
  • InertialLabs INS-U external AHRS support
  • Lord external AHRS renamed to MicroStrain5
  • MAV_CMD_EXTERNAL_POSITION_ESTIMATE supports setting approximate position during dead-reckoning
  • Microstrain7 (aka 3DM-QG7) external AHRS support

Driver enhancements

  • 3DR Solo supports up to 6S batteries
  • Airspeed health checks vs GPS use 3D velocity
  • BDshot on the first four channels of boards with F103-based IOMCUs (e.g. Pixhawk 6X)
  • Dshot on all IOMCU channels on all boards with an IOMCU (e.g. all CubePilot autopilots)
  • Dshot commands (e.g. motor reversal abd beeps) and EDT supported on IOMCU
  • DroneCAN battery monitors calculate consumed energy if battery doesn’t provide directly
  • DroneCAN RC and Ghost RC protocol support
  • EFI MAVLink driver
  • Extended DShot Telemetry support (requires BLHeli32 ver 32.10 or BlueJay, set SERVO_DSHOT_ESC=3 or 4)
  • GPS L5 band health override to enable L5 signal use (see GPS_DRV_OPTIONS)
  • GPS-for-yaw works at lower update rate (3hz minimum)
  • GSOF GPS supports GPS_COM_PORT parameter
  • Hirth ICEngine support
  • ICE option to enable/disable starting while disarmed
  • ICE support for starter via relay
  • IMUDATA serial protocol outputs raw IMU data on serial port (only available using custom build server)
  • Innomaker LD06 360deg lidar support
  • Intelligent Energy fuel cells new protocol support
  • IRC Tramp supports 1G3 bands A and B
  • IRC Ghost support
  • JAE JRE-30 radar
  • KDECAN driver rewrite (params moved to KDE_, works on all vehicles)
  • MCP9601 temperature sensor support
  • NanoRadar NRA24 rangefinder support
  • NeoPixelsRGB support
  • NoopLoop TOFSense, TOFSenseF-I2c rangefinder support
  • OSD shows flashing horizon when inverted
  • OSD2 support (e.g. second OSD)
  • QMC5883P compass support
  • Relay refactored to support RELAYx_FUNCTION, RELAY_STATUS message support added
  • Reventech fuel level support (extends existing analog driver, see BATT_FL_xx parameters)
  • RPLidarS1 360 deg lidar support and improved reliability for all RPLidars
  • SBF GPS supports yaw from dual antennas
  • Temperature sensor using analog voltages supported
  • Trimble PX-1 support added as a GPS
  • Winch driver enhancements including stuck protection, option for spin-free on startup

Control and navigation changes and enhancements

  • Auto missions can always be cleared while disarmed (would fail if mission still running)
  • DO_ENGINE_CONTROL allows starting engine even when disarmed
  • DO_SET_MISSION_CURRENT command can reset mission (see Reset Mission field)
  • DO_SET_SERVO, DO_REPEAT_SERVO work with servo outputs set to RCInxScaled
  • Fractional Loiter Turn Support in missions
  • HarmonicNotch supports up to 16 harmonics
  • JUMP command sends improved text msg to pilot (says where will jump to)
  • MAV_CMD_AIRFRAME_CONFIGURATION can control landing gear on all vehicles
  • MOT_OPTIONS allows voltage compensation to use raw battery voltages (instead of current corrected voltage)
  • PID controllers get DFF/D_FF (derivative feed-forward), NTF (target notch filter index) and NEF (error notch filter index)
  • PID controllers get PDMX param to limit P+D output (useful for large vehicles and/or slow actuators)
  • PID notch filter configured via new filter library using FILT parameters
  • VTOLs send ATTITUDE_TARGET messages to GCS

Plane specific enhancements

  • AUTOTUNE_OPTIONS allows disabling filter updates
  • Harmonic Notch frequencies can be logged at full rate
  • L1 controller checks heading and ground track agree to improve strong headwind edge case
  • Land airspeed default is halfway between min and cruise
  • LoiterAltQLand mode re-uses Loiter point if available
  • AUTO mode landing abort aux switch renamed
  • Q_M_SPOOL_TIM_DN allows slower spool down of motors
  • Quadplane use of forward throttle in VTOL modes improved
  • Tailsitters use motor I term for pitch control if no pitch surfaces are setup
  • Takeoff mode holds down elevator on taildraggers
  • Transition time may be no less than 2 seconds (see TRANSITION_MS)
  • VTOL angle controller gets feed-forward scaling (see Q_OPTIONS)

ROS2 / DDS support
We now support ROS2 via the DDS protocol directly without going via a MAVLink ROS layer. This is especially useful in combination with the networking support for DDS over UDP.

Camera and gimbal enhancements

  • Calculates location where camera gimbal is pointing (see CAMERA_FOV_STATUS)
  • CAMx_MNT_INST allows specifying which mount camera is in
  • Camera lens (e.g. live video stream) selectable using RC aux function
  • Interval timer (for taking pictures at timed intervals)
  • Image tracking support (ViewPro only)
  • MAVLink Gimbal Protocol v2 support for better GCS integration
  • MNTx_SYSID_DFLT allows easier pointing gimbal at another vehicle
  • MOUNT_CONTROL, MOUNT_CONFIGURE messages deprecated
  • RangeFinder support (only logged, only supported on Siyi, Viewpro)
  • Pilot’s RC input re-takes manual control of gimbal (e.g. switches to RC_TARGETING mode)
  • Siyi driver gets Zoom control, sends autopilot attitude and time (reduces leans)
  • Video recording may start when armed (see CAMx_OPTIONS)
  • ViewPro driver (replaces equivalent Lua driver)
  • Xacti camera gimbal support
  • Zoom percentage support (for both missions and GCS commands)

Logging and reporting changes

  • Battery logging (e.g. BAT) includes health, temperature, state-of-health percentage
  • CAM and MNT messages contain camera gimbal’s desired and actual angles
  • CTUN includes airspeed estimate type (e.g. sensor, EKF3 estimate)
  • INS_RAW_LOG_OPT allows raw, pre-filter and post-filter sensor data logging (alternative to “batch logging”, good for filtering analysis)
  • PID logging gets reset and I-term-set flags
  • Rangefinder logging (e.g. RFND) includes signal quality
  • RC aux functions sorted alphabetically for GCS
  • RC logging (RCI, RCI2) include valid input and failsafe flags
  • RTK GPS logging includes number of fragments used or discarded
  • TEC2 provides extended TECS controller logging
  • TSIT provides tail sitter speed scaling values

Scripting enhancements

  • Autopilot reboot support
  • Baro, Compass, IMU, IOMCU health check support
  • Battery cell voltage bindings
  • Battery driver support
  • BattEsimate.lua applet estimates SoC from voltage
  • Camera and Mount bindings improved
  • CAN input packet filtering reduces work required by Lua CAN drivers
  • DJI RS2/RS3 gimbal driver supports latest DJI firmware version (see mount-djirs2-driver.lua)
  • EFI drivers for DLA serial, InnoFlight Inject EFI driver
  • EFI bindings improved
  • Fence support
  • Generator drivers for Halo6000, Zhuhai SVFFI
  • GCS failsafe support
  • Hobbywing_DataLink driver (see Hobbywing_DataLink.lua)
  • is_landing, is_taking_off bindings
  • led_on_a_switch.lua sets LED brightness from RC switch
  • MAVLink sending and receiving support
  • Mission jump_to_landing_sequence binding
  • mount-poi.lua upgraded to applet, sends better feedback, can lock onto Location
  • Networking/Ethernet support
  • Plane dual-aircraft synchronised aerobatics
  • Proximity driver support
  • Rangefinder drivers can support signal quality
  • revert_param.lua applet for quickly reverting params during tuning
  • RockBlock.lua applet supports setting mode, fix for battery voltage reporting
  • Serial/UART reading performance improvement using readstring binding
  • sport_aerobatics.lua rudder control fixed
  • Thread priority can be set using SCR_THD_PRIORITY (useful for Lua drivers)
  • Wind alignment and head_wind speed bindings

Safety related enhancements and fixes

  • Advanced GCS failsafe action to switch to Auto mode
  • Advanced GCS failsafe timeout configurable (see AFS_GCS_TIMEOUT)
  • Arm in AUTO/TAKEOFF modes only after stick returns to center
  • Arm/Disarmed GPIO may be disabled using BRD_OPTIONS
  • Arming allowed with Fence enabled but without a compass (previously failed)
  • Arming check of compass vs world magnetic model to detect metal in ground (see ARMING_MAGTHRESH)
  • Arming check of GPIO pin interrupt storm
  • Arming check of Lua script CRC
  • Arming check of mission loaded from SD card
  • Arming check of Relay pin conflicts
  • Arming check to allow Tricopter-Plane with no yaw servo
  • Arming check of emergency stop skipped if emergency stop aux function configured
  • Arming failures reported more quickly when changing from success to failed
  • ARMING_OPTIONS allows supressing “Armed”, “Disarmed” text messages
  • BRD_SAFETY_MASK extended to apply to CAN ESCs and servos
  • Buzzer noise for gyro calibration and arming checks passed
  • FENCE_OPTIONS supports union OR intersection of all polygon fences
  • FLTMODE_GCSBLOCK blocks GCS from changing vehicle to specified modes
  • Long failsafe action to switch to Auto mode (see FS_LONG_ACTN)
  • Main loop lockup recovery by forcing mutex release (only helps if caused by software bug)
  • Parachute releases causes disarm and ICE shutoff
  • Rally points supports altitude frame (AMSL, Relative or Terrain)
  • RC failsafe does not trigger until RC has been received at least once
  • SERVO_RC_FS_MSK allows outputs using RC passthrough to move to SERVOx_TRIM on RC failsafe
  • Takeoff mode gets failsafe protections

System Enhancements

  • CAN port can support a second CAN protocol on the same bus (2nd protocol must be 11 bit, see CAN_Dn_PROTOCOL2)
  • CAN-FD support (allows faster data transfer rates)
  • Crash dump info logged if main thread locksup (helps with root cause analysis)
  • Ethernet/Networking support for UDP and TCP server and client (see NET_ENABLED) and PPP (see SERIALx_PROTOCOL)
  • Firmware flashing from SD card
  • Linux board SBUS input decoding made consistent with ChibiOS
  • Linux boards support DroneCAN
  • Parameter defaults stored in @ROMFS/defaults.parm
  • SD Card formatting supported on all boards
  • Second USB endpoint defaults to MAVLink (instead of SLCAN) except on CubePilot boards
  • Serial over DroneCAN (see CAN_D1_UC_SER_EN) useful for configuring F9P DroneCAN GPSs using uCenter

Custom Build server include/exclude features extended to include

  • APJ Tools
  • Bootloader flashing
  • Button
  • Compass calibration
  • DroneCAN GPS
  • ExternalAHRS (e.g. MicroStrain, Vectornav)
  • Generator
  • Highmark Servo
  • Hobbywing ESCs
  • Kill IMU
  • Payload Place
  • Plane BlackBox arming allows Plane to be used as logger (see ARMING_BBOX_SPD)
  • Plane’s TX Tuning
  • Precision landing
  • Proximity sensor
  • RC Protocol
  • Relay
  • SBUS Output
  • ToneAlarm
  • Winch

Developer specific items

  • ChibiOS upgrade to 21.11
  • UAVCAN replaced with DroneCAN
  • AUTOPILOT_VERSION_REQUEST message deprecated (use REQUEST_MESSAGE instead)
  • PREFLIGHT_SET_SENSOR_OFFSETS support deprecated (was unused by all known ground stations)
  • MISSION_SET_CURRENT message deprecated (use DO_SET_MISSION_CURRENT command instead)
  • MISSION_CURRENT message sends num commands and stopped/paused/running/complete state
  • Python version requirement increased to 3.6.9
  • mavlink_parse.py shows all suported mavlink messages
  • COMMAND_INT messages can be used for nearly all commands (previously COMMAND_LONG)

Bug fixes

  • 3DR Solo gimbal mavlink routing fixed
  • Airbrakes auxiliary function fixed
  • Airspeed health always checked before use (may not have been checked when using “affinity”)
  • always ignore invalid pilot input throttle
  • Bootloop fixed if INS_GYRO_FILTER set too high
  • Button Internal Error caused by floating pin or slow device power-up fixed
  • CAN Compass order maintained even if compass powered up after autopilot
  • Compass device IDs only saved when calibrated to ensure external compasses appear as primary on new boards
  • Cruise mode locks in heading only once moving forwards (improves VTOL transition reliability in high winds)
  • Currawong ECU EFI does not send exhaust gas temperature
  • DO_REPOSITION interprets NaN as zero
  • DCM fallback in order to get better GPS is disabled if GPS is not used
  • DJI RS2/RS3 gimbal reported angle fix
  • DO_SET_ROI, ROI_LOCATION, ROI_NONE bug fix that could lead to gimbal pointing at old target
  • Fix throttle going bellow min in fbwa RC failsafe
  • Generator parameter init fix (defaults might not always have been loaded correctly)
  • GPS_TC_BLEND parameter removed (it was unused)
  • Ground speed undershoot correction during loss of GPS fixed
  • Guided mode heading control anti windup fix
  • Harmonic Notch gets protection against extremely low notch filter frequencies
  • Home altitude change while navigating handled correctly (previously led to sudden demanded height change)
  • IE 650/800 Generators report fuel remaining
  • INS calibration prevents unlikely case of two calibrations running at same time
  • LPS2XH Baro supported over I2C fixed
  • MatekH743 storage eeprom size fixed
  • MAVLink routing fix to avoid processing packet meant for another vehicle
  • Mount properly enforces user defined angle limits
  • MPU6500 IMU filter corrected to 4k
  • nav_roll (aka target roll) calculation improved
  • NMEA output time and altitude fixed
  • OSD gets labels for all supported serial protocols
  • OSD RF panel format fixed
  • Reset mission if in landing sequence while also disarmed and on the ground (avoids pre-arm check)
  • RTL_AUTOLAND with rally points fix (could skip climb to rally point’s altitude)
  • RobotisServo initialisation fix
  • RPM accuracy and time wrap handling improved
  • Sagetech ADSB MXS altitude fix (needs amsl, was sending alt-above-terrain)
  • SageTechMXS ADSB climb rate direction fixed
  • SBUS out exactly matches SBUS in decoding
  • Serial port RTS pins default to pulldown (SiK radios could getting stuck in bootloader mode)
  • SERIALx_ parameters removed for ports that can’t actually be used
  • Servo gimbal attitude reporting fix
  • Servo output fix when using scaled RC passthrough (e.g. SERVOx_FUNCTION = RCinXScaled)
  • Siyi continuous zoom stutter fixed
  • Siyi gimbal upside-down mode fixed (avoid bobbing if upside-down)
  • TECS’s max deceleration scales properly with vehicle velocity
  • ST24 RC protocol fixed
  • STM32L496 CAN2 init fix (AP_Periph only?)
  • VFR_HUD climb rate reports best estimate during high vibration events (previously it would stop updating)
  • Visual Odometry healthy check fix in case of out-of-memory
  • VTX_MAX_POWER restored (allows setting radio’s power)
17 Likes

Excellent work Devs,
Thankyou.

1 Like

Alot of great features thanks for all the hard work :pray:
In 4.5 there will be option to use the forward motors on the vtol to move in quad modes right?
Qstabilize and qhover

yes, that is in 4.5.0. See the parameter Q_FWD_THR_USE.

3 Likes

I understood that adding PPP was a waf parameter. This seems to imply that it is now ‘standard’, is that right?
If it’s still a waf parameter is there/should there be a build server option for it?

hi Tim,
it is on the custom build server:
image

1 Like

Good to hear. I asked because it’s not listed in the release notes under “Build Server”.

Great improvements! Thank you for your effort!
Great that we can use fence w/o compass in the future!

4.5 Beta doesn’t seem to be an option

After installing 4.5.0 beta 1 I’m now getting “3D Accel Calibration Needed”.

I calibrated this AP yesterday, this pre-arm was not happening before I installed this.

This is on a Qio-Tek Zealot H743 that had previously been running 4.5.0 dev from master. Is this expected? I build this locally from the 4.5 branch with --enable-ppp.

Of course after doing a complete 3D Accelerometer calibration, the error went away, but this could be a problem with a larger vehicle. (If it’s not just me).

Just flew this 4.5 Beta1 on a VTOL Babyshark. No issues at all, the back transition using q_fwd_thr works very well, nice work team.

1 Like

I just flew 4.5.0 beta on my VT Bird Quadplane. Everything seemed fine but I noticed an “anomaly” on QRTL. The plane tried to land about 55m west of home, which would have brought it down in some bushes by the field.
It’s not a GPS issue, because when I took over, it was showing that it was landing 55m from “Home”, and when I brought it down on the landing mat that I had taken off from, it reported that it had landed 1.0m from Home in the OSD. I think this means the GPS is actually pretty accurate…
See this video from my goggles which shows this. https://youtu.be/iA5_LvsTFUk
Here is the log: Dropbox - log_79_2024-2-7-14-05-00.bin - Simplify your life

I don’t know if this was a problem before 4.5.0, so I can’t be sure it’s new.

Oh! So there is no problem. I had created a fence/mission previously for a fixed wing and included a Rally Point - for the plane to loiter around if it breached the fence.

But of course a Rally Point also applies if you “QRTL” - overriding the start/home location so of course the quadplane tried to land at the Rally Point.

So - works as expected.

2 Likes

When preparing a maiden flight (MFD Crosswind, Matek H743 Wing V3, Arduplane 4.5.0-beta1) I noticed a problem with FLIGHT_OPTIONS bit 1 (“Use centreed throttle in Cruise or FBWB to indicate trim airspeed”) and bit 10 (“Adjust mid-throttle to be TRIM_THROTTLE in non-auto throttle modes except MANUAL”):
Firstly, you can arm correctly with FLIGHT_OPTIONS = 0 and control the motors in MANUAL and FBWA with the throttle lever.

If you set bit 1 (FLIGHT_OPTIONS = 2), the aircraft can be armed in MANUAL and the motors run, but if you switch to CRUISE mode, the motors stop immediately, regardless of the throttle position. When you return to MANUAL mode, the engines run normally again.

With FLIGHT_OPTIONS = 1024 (bit 10) the aircraft cannot be armed in manual mode “Throttle Stick not near Centerstick”.

Link to the “Benchflight”-log: https://magentacloud.de/s/xq8FDXDd7cf4J2n

Rolf

that is expected in CRUISE when doing a bench test as CRUISE is an auto-throttle mode which uses throttle suppression as a safety feature (ie. if it thinks you are sitting on the ground then it won’t run the motors). Manual mode doesn’t do this check.
Can you re-test using SITL while flying or sim-on-hardware? The behaviour should be the same as 4.4.x.

Do you mean this prearm?

PreArm: Throttle trim not near center stick(1045)

that is a check that if you have set bit 10 (which indicates a center-sprung throttle) that you have also remembered to set RC3_TRIM to the right value. When bit 10 is not set the RC3_TRIM is not used, so doesn’t matter (I’m assuming RCMAP_THROTTLE=3). When bit 10 is set then it is easy to forget to set RC3_TRIM to the right value, so this prearm is to catch that mistake.

Note that these options haven’t had a lot of testing so I wouldn’t be surprised if you did find a bug, but from the above I think you are seeing expected behaviour.

thanks alot for this huuuge update!

hanged them from centimeters and centidegrees to meters and degrees.

thanks for this, it always gave headaches on double checking that all parameters are correct and we actually lost one drone because the user forgot to use centi units.

2 Likes

The fact that engines do not start when the aircraft is stationary while in cruise mode makes sense. Sorry, I didn’t even think about it testing on the workbench. Thanks for the clarification.

FLIGHT_OPTIONS bit 10:
I am confused about not being able to arm if FLIGHT_OPTIONS bit 10 is set and RC3_TRIM (assuming RCMAP_THROTTLE=3) is not centred because with every installation of Arduplane, RC3_TRIM is set to RC3_MIN by the mission planner during radio calibration.

Are you sure? So you can disregard this instruction from MissionPlanner during radio calibration:

Rolf

It looks like the MissionPlanner RC calibration is not setup properly for sprung throttle.
Given sprung throttles are quite common now I think we need a new wording there
I’ve opened a PR for the possible message change:


I’ve just released plane 4.5.0-beta2. Changes from beta1 are:

New Autopilots supported

  • YJUAV_A6Ultra
  • AnyLeaf H7

System level changes

  • fixed float rounding issue in HAL_Linux millis and micros functions
  • fixed loading of defaults.parm parameters for dynamic parameter subtrees
  • fixed discrimination between GHST and CRSF protocols
  • fixed bug in DroneCAN packet parsing for corrupt packets that could cause a crash
  • fixed handling of network sockets in scripting when used after close
  • fixed bit timing of CANFD buses

Plane specific changes

  • fixed handling of force arming when safety is enabled for VTOL motor state

Camera and gimbal enhancements

  • wait for non-zero camera version in SIYI driver

Miscellaneous

  • do relay parameter conversion for parachute parameters if ever has been used
  • broaden acceptance criteria for GPS yaw measurement for moving baseline yaw
1 Like

Today I flew Beta2 on a BabyShark VTOL. No problems encountered.

2 Likes