Well It looks like that worked.I was still getting the drop to 3 satellites but your message about the ekf issue made me think about it so I ran with the plane to simulate takeoff and get the yaw alignment set seems to have fixed it.
Thanks
Well It looks like that worked.I was still getting the drop to 3 satellites but your message about the ekf issue made me think about it so I ran with the plane to simulate takeoff and get the yaw alignment set seems to have fixed it.
Thanks
Heureka @tridge It works with a better parameter setting!
I systematically tried out settings for BLELI:
SERVO_BLH_AUTO set 1 causes the unwanted behavior at motor output 7 (used for yaw servo in case of non-vectored tri’s). Instead of SERVO_BLH_AUTO (set it to 0) use SERVO_BLH_MASK with the bitmask of actually to BLHELI-ESCs connected outputs. On the bench, yaw servo works.
Rolf
Happy flying!
@yak-54 I just wanted to let you know I haven’t forgotten about your issue. I am going to try and replicate here if I can find my minimosd. I didn’t want to hold up the 4.0.2 release though, so I’m afraid it will probably have the same issue for you
don’t worry about it its new build the other plane that i fly has only one screen
thank you so…much I plan to test with the FX-61 ; flying wing …
I just have updated my quadplane to 4.0.2. I have recalibrated the HERE2 compass but the COMPASS_SCALE remains at zero >>> It should change automatically to 1.17
I have changed it manually to 1.17.
I think it is the right thing but it is not what was expected
what calibration method did you use? Do you have the tlog of the calibration process?
yes, it should work out the calibration. It is unlikely to come out at exactly 1.17, but should be close
I have used onboard calibration with 1.3.68 MP version. I’ll post the tlog. I will try again with latest version of MP, Could it be the problem?
I have updated MP to the latest version 1.3.70
I have recalibrated HERE2 primary compass only
I have used live calibration
I have used onboar calibration
But COMPASS_SCALE still maintains the value zero.
If I change it manually to 1.17 >> Do we get the same result?
The most likely cause is that you are calibrating without GPS lock. If you don’t have GPS lock then the calibrator doesn’t know what the correct magnetic field strength should be, so it leaves COMPASS_SCALE=0.
It will help, but it would be better to get the right scale by calibrating with GPS lock.
Perhaps you are calibrating indoors? If so then that is a bad idea.
I have understood. Indeed I was trying to calibrate without GPS lock. >> Tomorrow I will calibrate it with GPS Fix.
Thanks Tridge
The Matek F765 web site shows it supports CTs7/Rts7: Uart7_CTS/RTS for ArduPilot Telem1 on Serial1. Is this implemented with the new 4.02? I’m unable to see any options to enable it.
Thanks,
it isn’t, and it should be, sorry. It is fixed in master, and I’ve put a fix in for 4.0.3. Thanks for letting me know!
Thanks Tridge, truly appreciate all the work you do with this.
How is work going no more than one compass on UAVCAN like 2 x Here2 gps units ?
Today I have calibrated with GPS Fix. Now Compass scale has collected a nonzero value
COMPASS_SCALE = 1,236598
ok, that should work, but it is a bit higher than expected
What is a new feature in the settings SERVO13_FUNCTION 120 for MATEK F765_WING
According to latest master, it’s neopixel LED function. https://github.com/ArduPilot/ardupilot/blob/master/libraries/SRV_Channel/SRV_Channel.h