|
So far, I have found two bugs that need to be mentioned.
Up to now, while trying to fine tune my heli, I have saved the settings to the unit several dozen times. Five to ten of those times I got a very strange bug. At the moment I hit save, the servos, and especially the rudder one, started moving forth and back very fast, like if you had used ultra high gain and the tail runs like mad chasing itself and over-correcting in a really fast frequency. The effect is very intense and I think it could easily burn a servo if you leave it like that for several seconds. Only way to stop it, is to disconnect the unit from power. Nothing else works. What is even more dangerous is the fact that one of those times I had a crash due to that bug. For a strange reason, one of the times I hit save and while I didn't experience the bug at the moment, a couple seconds later that I started spooling up the heli, suddenly the bug took effect and this resulted to a chicken dance on the ground. This only happened once so I can't be 100% sure that happened due to the bug, but I'm pretty much sure it did though. I think that at least before correcting the bug there should be an addition in the manual with big red capital letters saying that EVERYTIME YOU SAVE SETTINGS YOU HAVE TO RE-INITIALIZE THE UNIT BEFORE FLYING. Yet I find it really strange that no one has mentioned this before. I have only used windows xp sp3 and cable to connect to the unit so far.
The next one, I'm not very sure it's a spirit bug. I t could also be an OpenTX one. I use Taranis running OpenTX version 2.0.12. and I connect to the unit using s.bus. OpenTx supports 3 types of failsafe: Hold, Stop pulses, Custom positions.
(c/p from the manual)
Failsafe mode: Allows choosing between simply holding the last received
positions, turning off pulses (like old PPM MHz receivers), or moving the servos to custom
predefined positions. For custom positions a SET field will call the failsafe settings page, where
the position can be defined separately for each channel. Select the desired channel, press
ENTER to get in edit mode, move the control to the desired position, and press ENTER to save. In
D8 mode this field is hidden, failsafe needs to be set on the receiver as described in the receiver's
manual.
I have chosen "custom" mode because I want to turn motor of, get the cyclic back to level, and move the pitch to zero degrees. When I checked it I noticed that it doesn't work as it should. It just cuts off the motor but it holds the last position for swashplate and pitch instead of moving back to zero. I know that it should work because it was working fine with my last fbl unit, the microbeast beastX.
There is something more I'd like to add that it may helps. I noticed that in order to calibrate Pitch in the diagnostics tab I had to add a subtrim of 6.0 from the Tx. Upon re-initialization it didn't seem to work as it should though, I mean I didn't have zero pitch at middle stick. Then a friend of mine had an idea. He told me that maybe upon connecting the battery (that rx and spirit power up simultaneously) the Tx tries to communicate the custom values(0.0 for pitch channel) for the failsafe to the Rx and at the same time the Spirit calibrates the channels and so it takes 0.0 as the center position while the correct value was 6.0. Indeed after changing the custom preset failsafe value for pitch from 0.0 to 6.0, I had zero pitch at the center of my throttle stick, nonetheless failsafe still is not working as it should. Any ideas?
|
