Copter-4.6.0-beta4 has been released for beta testing and should appear in the ground stations (MP, QGC) within a few hours after which time it can be downloaded and installed using the GCS’s beta firmwares links. Alternatively it can be manually downloaded from firmware.ardupilot.org
The changes vs -beta3 are in the Release Notes and copied below:
Board specfic changes
BETAFPV F405 supports DPS310 baro
BETAFPV F405 board variants added
Driver enhancements
CADDX camera gimbal support
UltraMotion CAN servo support
Copter specific fixes and minor enhancements
SysId mode uninitialised variables fixed
ARMING_NEED_LOC blocks arming regardless of mode until position estimate is good
Bug Fixes and minor enhancements
AM32 ESC passthrough fixed
BMP581 baro initialisation fix
DDS/ROS2 driver waits indefinitely until companion computer running ROS2 starts
Lua script potential deadlock fix when initialising mavlink in script
Mcast and HW CAN bridging disabled by default
Plane’s TILT log message only logged on tilt-rotors
ROMFS race condition when opening files that caused apparent script corruption fixed
Serial flow control support on UARTS 6 to 8
Serial passthrough fix to restore parity upon completion
Serial protocol parameter fix to include I-Bus Telemetry
uAvionix ping200X driver fixes
Video stream information lua script param index fixed (avoids param conflict with other scripts)
ViewPro object tracking fixed
This could be the final beta release so all testing and feedback is greatly appreciated!
“Thanks for bringing this up again.” This is a very old bug that I was able to find back in the translation chibos day and again in 8-22-2021. No amount of tuning would fix it. I did mention last month I recognized it and have it in a video the second time it showed. Glad its located.
OK, so that means that we didn’t track the issue very well. I think the best way to get an issue investigated and fixed is:
report the issue in the forums
create an issue in the issues list including logs and any other information or evidence to re-create the issue
bring the issue up especially during beta testing
remind the core devs a few times, bring it up in a weekly dev call
Sorry, I know this can be a lot of work for the reporter, as you know we all do what we can but none of us are perfect and things slip through the cracks sometimes.
Personally I feel that we properly maintain a list of issues especially during beta testing so getting involved in beta testing is actually one of the best ways to get issues resolved
Thanks for the report. It looks like our parameter descriptions haven’t been updated with the changes from -beta4. -beta3 is there in the drop-down but not -beta4 yet. I suspect it will appear given another day but I’ll ask some of the other devs like @peterbarker and @khancyr if they know.
Regarding arming, does this mean i will not be able to arm on the bench without taking the build outside to get sats then arm for a home position? Props off.
Not sure if this is only on my setup, as I am testing it with FC connected only to ESC and gimbal, but seems on startup gimbal is not initialized into selected default mode (neutral in my case). Setting neutral with MP makes it to work in neutral mode
Same situation with default “Retracted” selected as default.
Correction - it actually is initialized to default mode, but after 60 seconds. Is that result of no receiver beeing connected?
So i had a odd flight after swapping a 4s battery with a 6s battery on a older firmware. Some bad oscillations. Had a small crash. I did notice the FC was a tad loose. So i flashed to the current Beta.
I mended the quad superglue, updated to 4.6.0-beta4, had a issue arming with false flags. Yappa gave gave a few arming messages that went away after a compass cal reboot, seems to be flying ok now. Next I will test the s6.
Re the new ARMING_OPTIONS bit, “Require position for arming”, yes, if this bit is checked then the vehicle may not be able to be armed indoors. Of course if the bit is left unchecked (which is the default) there shouldn’t be any change in behaviour from 4.5.
Hi Andy, Not nomaly I had a lot ot S6 and S4 swaps without issue however yes that effects the tune and backing down the PIDs will help, most of the crafts I build are 9" to 10" propellers. Thing is I did adjust the PID’s in order to reduce but i had no resolve on the oscillations. I thinking the issue was my FC was a little loose now ok. tomorrow i will test the S6 again.
If you dont touch it, motor tests all work as per normal - I just tested it.
I set it to 1 and disabled my GPS (since it was working inside just fine) , rebooted and Messages indicated waiting for Home and all the expected things for requiring a location. FENCE settings have nothing to do with the motor tests either, only hardware (un)safety switch.
