Copter-4.6.0-beta2 has been released and should be available for download using MP and QGC within a few hours using the “Beta firmwares” link. Alternatively it can be downloaded directly from firmware.ardupilot.org
The changes vs -beta1 are in the ReleaseNotes and copied below
- Board specfic changes
- FoxeerF405v2 supports BMP280 baro
- KakuteH7, H7-Mini, H7-Wing, F4 support SPA06 baro
- MUPilot support
- SkySakura H743 support
- TBS Lucid H7 support
- VUAV-V7pro README documentation fixed
- X-MAV AP-H743v2 CAN pin definition fixed
- Copter specific enhancements and bug fixes
- AutoTune fix for calc of maximum angular acceleration
- Advanced Failsafe customer build server option
- Plane related enhancements and bug fixes
- QuadPlane fix for QLand getting stuck in pilot repositioning
- QuikTune C++ conversion (allow running quiktun on F4 and f7 boards)
- Takeoff direction fixed when no yaw source
- TECS correctly handles home altitude changes
- Bug Fixes and minor enhancements
- AIRSPEED_AUTOCAL mavlink message only sent when required and fixed for 2nd sensor
- CAN frame logging added to ease support
- CRSF reconnection after failsafe fixed
- EKF3 position and velocity resets default to user defined source
- Ethernet IP address default 192.168.144.x
- Fence autoenable fix when both RCn_OPTION=11/Fence and FENCE_AUTOENABLE = 3 (AutoEnableOnlyWhenArmed)
- Fence pre-arm check that vehicle is within polygon fence
- Fence handling of more than 256 items fixed
- FFT protection against divide-by-zero in Jain estimator
- Frsky telemetry apparent wind speed fixed
- Inertial sensors stop sensor converging if motors arm
- Inertial sensors check for changes to notch filters fixed
- Real Time Clock allowed to shift forward when disarmed
- ROS2/DDS get/set parameter service added
- Scripting gets memory handling improvements
- Scripting promote video-stream-information to applet
- Topotek gimbal driver uses GIA message to retrieve current angle
- Tramp VTX OSD power indicator fixed
As you can see from the list we’ve fixed quite a few issues but a few more still remain so there will certainly be a -beta3.
We very much appreciate any help we can get with beta testing because this is an important stage that helps us ensure a good smooth official release so thanks!
