![]() The sensor status block will be yellow, but the controller will still arm and fly normally. These 5 short beeps may or may not be periodic, depending on vehicle motion and stick inputs.ĥ)External mag senor handling is improved, firmware will still run but throw an error if the sensor is selected but not detected (not installed, not powered, etc.) In the case of the F3Fc integrated and racing, the racing board will need the Tolerate Missing Sensors UAVO set true. The in air calibration should beep 5 short beeps, one after every 100 samples are collected. At the end of the calibrations, 2 long beeps repeating indicates pass, 3 long beeps repeating indicates fail. There’s a lot of changes from the previous release.ġ)All three boards (F3Fc, KakuteF4V3, Matek405) are now navigation capable, supporting external HMC5883 and HMC5983 magnetometersĢ)On ground ServoCal limit checks relaxed slightly, should complete now in those few cases that were previously failingģ)In air ServoCal calculation bounds increase slightly, V4 doesn’t need much trim and was right on the edge of failingĤ)ServoCal beep tones. Both vehicles performed very well, all tunes completed on the first attempt. This was in the confines of my back yard, so nothing radical. Test flew Arco, Leveling, Horizon, LQG Rate, LQG Attitude, and LQG Horizon (new mode in this build). The testing covered basic setup, on ground ServoCal, AutoTune, apply AutoTune gains, in air ServoCal. Tonight, I was able to setup from scratch and test fly my Baby Tri with the F3Fc, and V4 Tri with MatekStd. Okay, I have the new build complete and have started flight testing. Perhaps this is contributing to the overly-active tail?Īny tips would be greatly appreciated, and please see the attached screen-grabs of my TriFlight and PID settings. I have zeroed out the D gain on Yaw as was suggested by David’s video, but the I term seems huge. I then went looking again for parameters that seemed strange, and I did notice that the Yaw PIDs from AutoTune do look a little odd. Strangely, it doesn’t seem like either of these changes made a real significant impact (if any) on the V4’s flight performance. ![]() I was reading David’s tuning tips on the first post of the thread and after reading, I set YawBoost to 0 and DynamicYawMaxThrottle to 0. Its seems like whenever I get in the 80-90% throttle range the tail servo starts wagging rapidly and gets worse the more I raise the throttle. Not even jamming it full-throttle, and then cutting it off, but even just steadily raising the throttle to 100% and then backing off relatively slowly. ![]() I am out and flying, and that’s good, but I’m noticing some very strong yaw oscillations during high-throttle punch outs. I think that the extra beeps will make it a more intuitive user experience. I have another unit coming tomorrow that will accept either 5v or 3.3v power, going to give that one a try and see what I sounds good. All the gps/mag units I tried with the KakuteF4V2 work with other boards, AQ32, F3Fc, Matek405Std, even my Raspberry Pi and Beaglebone Blue boards. The KakuteF4V2 is the first board I’ve used that seems sensitive to the SDA/SCL pull up resitor values on the external mag. Never graduated to return to home, so that’s were I’m going to start poking around again once I get this mag issue sorted out. I had position hold mode working fairly well quite some time ago, but got sidetracked with other things. I’ve not looked into the details of the mag_calibration.py script, I’ve got some of my own tools/routines I use for that. GPS will need at least 7 satellites if I recall correctly before the system will set the home point and allow the attitude filter to run properly and the system to arm.Ī good mag calibration is important for good navigation results. – remind me which FC you are using again….įrom memory, you need to enable the Path Planner and VTOL Path Follower modules, and set the navigation algorithm (on Attitude->Filter Settings pane) to INS.
0 Comments
Leave a Reply. |