There’s my log. It is latest master because I’d no chance to switch from fport back.
There’s FBWA, MANUAL, ATUN, AUTO, GUID flight modes and autonomous landing at the end.
Any recommendations would be appreciated 
It hit the limits of SERVO_AUTO_TRIM. The auto trim won’t go beyond 20% of the throw, which means 1600 max for your servo range. You will need to physically adjust the servos to re-center the elevons.
Looks like it is doing well! Nothing obvious wrong from a quick look at the log
1 Like
Please let me know when it would be possible to test fport rc firmware.
There’s two issues I’d faced
- Rssi reading looks incorrect on osd
- I’d not all fields at yaapu scrip at my Taranis. I have gps, batt voltage, current, mah. But total distance looks blank. I’ll do photo at next flying session
very good point! 
thanks for pointing it out, will re-check all of that… Cheers!
I’ve just released plane 4.0.3 stable. This is a minor release with a few bug fixes and enhancements. The changes since 4.0.2 are:
- fixed 3 missing semaphore waits
- fixed checking for bouncebuffer allocation on microSD card IO
- fixed incorrect param count
- prevent failsafe action from overriding a VTOL land
- fixed compass calibration failures with auto-rotation detection
- fixed errors on STM32H7 I2C (affects CubeOrange and Durandal)
- fixed a race condition in FrSky passthrough telemetry
- fixed DSM/Spektrum parsing for 22ms protocols
- added fixed yaw compass calibration method
- re-generated magnetic field tables
- ensure SERIAL0_PROTOCOL is mavlink on boot
The most important fix is for FrSky pass-through telemetry. Pass through telemetry support had a race condition which could lead to the flight controller generating a fault and rebooting. All uses of FrSky telemetry should update immediately.
Happy flying!
2 Likes
The new “prevent failsafe action from overriding a VTOL land” comes default with this last release or it needs to be activated from a parameter? Thanks.
it is the default behaviour
1 Like
I’d just tryed all flight modes: fbwb, loiter, cruise, guided, auto and tkoff (dev firmware)
Everything works nice and smooth.
Until my wing was crashed
There’s a sequence of crash…
Had a tip stall in fbwa mode because a slow turn.
Fortunately it was recovered in rtl mode.
Just after recovery I’d switched to auto mode and had a stall again because auto mode made a tight turn but at that moment the speed was pretty low just after recovery. Nothing serious but shit happens
Was STALL_PREVENTION turned on?
There’s no airspeed sensor on the wing
I have a Pixracer R15 from mRobotics
In order to flash arduplane 4.0.3 do I need to do something special or is it Ok if I I do it from mission planner ?
Alcala
Ps : i posted same request in another post but I believe it is more appropriate to do it here
You can flash directly from MissionPlanner
I finally had the chance to test-fly 4.0.3 stable yesterday, and I had a very successful flight. Upon analysis of the logs, I’m not sure I undertand what is driving a roll demand oscillation in the middle of an automatic mission. See the screenshot (red line indication) and attached log below.
https://1drv.ms/u/s!AunBK4rE1ZDCgedfzY8urJ0vpdPvXA?e=v0yTeF
it is navigation indecision. The plane was flying south and the next waypoint was to north. It flipped between turning right and left a couple of times. We do have code to prevent this type of indecision but it isn’t perfect, and sometimes we get temporary indecision depending on the yaw rate of the aircraft at the time.
Just tryed fully autonomous flight (no rc control) and it was fully successful!
Much better when I’d try to do a smooth manual landing last time.
1 Like
I’ve just released plane 4.0.4beta1. This release includes a significant number of changes from 4.0.3. Key changes are:
- re-sync the 4.0 release with Copter-4.0, bringing them in line so as to maximise cross-vehicle testing
- fixed a timing issue in IOMCU that could lead to loss of RC input frames and increased latency of output to ESCs on the IOMCU
- fixed a bug in restoring gains in QAUTOTUNE that could cause the aircraft to be unstable on leaving QAUTOTUNE mode
The Copter-4.0 re-sync brings in quite a few structural changes. The main user visible changes are:
- UAVCAN DNA server no longer needs a microSD card to operate
- added logging of UAVCAN servos and ESC feedback messages
- reduced QTUN logging rate to 25Hz
- reduced memory usage in EKF with multiple lanes
- Minor OSD improvements
- added a lot more scripting bindings
- fixed UAVCAN GPS status when not connected
- added EK3_MAG_EF_LIM limit for earth frame mag errors
- added MAVLink FTP support
- added support for WS2812 LEDs
Due to the significant number of changes with the re-sync I would particularly appreciate as much flight testing as we can get on this release.
Happy flying!
2 Likes
I am trying to have camera triggering happen on the ground before flying, and now I’m having no luck. It was working a few days ago, and I don’t recall having issues with previous firmwares but now something is different. I believe the logs indicate that the trigger message is not getting through as I can’t find any TRIG events. RC6_Option = 9, and that has worked in the past. Trigger camera now from mission planner is also not working. Log at the following link. https://1drv.ms/u/s!AunBK4rE1ZDCged5m_r3Z2tkNfI0GQ?e=JlXe8S
just a reminder that I’d love to see logs from the 4.0.4beta release. I can’t do the release till I have sufficient logs to be confident everything is OK
Do you need logs from any particular flight controller?