The Nano Goblin with Beta 6 works great after the tune, it flew amazingly well in 30Km/h winds.
I upgraded my S800 wing from 3.9.3 to Beta 6 and reset the tune parameters and it really surprised me how well it flew under the same wind with the defaults.
To the whole Ardupilot community thank you very much !!!
tridge，I found the RST parameter lost in parameter tree ，so i can’t reset flight mode，can you check it? And it can’t be set rally point in latest mission planner，i can’t find out where to set rally point in mission planner。
Completed the autotune on the S800 that used to be notoriously prone to have pitch oscillations after autotune in 3.9.x apparently tune ended and there were no oscillations. There was a wind of about 15/20 Km/h. But I am very happy with the result.
Hi tridge,I found there may be some issue about estimated airspeed in beta5,i did several flight today,and the estimated airspeed became wrong value when it display message of EKF3 ACTIVE。there have almost no wind,but the FC give a wind of 12m/s or 6m/s.you can see the pitcture below,the estimated airspeed is 21km/h,but the plane does not move.
it offten happen when the plane just take off and the plane become unstable ATT.
it happened many times after I update to firmware4.1 beta5,i record the issue this time so i post here,hope you can analysis it .
Please let me know if you can’t download my log
Plus:this plane was flight about 40 flight hours with firmware4.0.5,but i think the estimate airspeed is quite accurately,does is the EKF3 ISSUE?
thanks for the report! It is almost certainly related to the handling of no-compass flight where EKF3 initialises after takeoff.
I haven’t been able to reproduce this in SITL. Would you be able to get a replay log showing this issue?
To get a replay log set the following parameters:
You will end up with a larger log that will allow us to reproduce the problem using the replay tool and hopefully find the cause.
Hi. I am running 4.2.0 Dev version on a Matek F765WING. I have recently upgraded to this version from 4.1.something. I have a breakwire function that changes flight mode using one of the button inputs but it seems to have stopped functioning in the later firmware. I read somewhere that the BRD_PWM_COUNT parameter has been eliminated and the functionality defined through other means in the firmware. I suspect the pullup resistors on these outputs are not being enabled. In my case it is for button2.
The button press is monitored by a LUA script to change the flight mode when the input goes high. This was working on the earlier version of the firmware. I have measured the voltage on the relevant pin and it is zero.
Anyone have anything similar or knowledge of what might be wrong here please?
If you can tell me a better place to post for Plane 4.2.0 Dev please feel free to do so.
As an aside, I had an odd bug on beta5 today; the aircraft entered RTL and then QRTL immediately after auto takeoff. The same mission/parameters were flown several times before the problem flight and once after it, all today. The logged reason is 39, which (from what I can tell from ModeReason.h) is RTL_COMPLETE_SWITCHING_TO_VTOL_LAND_RTL. I’m not sure how to see the current waypoint in the binary logs, but this was a cold boot, so the mission should have proceeded normally.