Spirit System

Hi,

two weeks ago, i had a strange Situation. I initialized my Diabolo BE and checked the swashplate as always. Everything seemed to be fine. I moved the helicopter to the starting place and started the engine. Without any steering Input, the helicopter moved up during the spoolup. The Pitch on my TX was around 0 degrees, so he should not do this. Intuitively i tried flying him, but the helicopter toppled backwarts over nick. I switched the Motor off, and pressed him via "Full Nick" to Front to the bottom. Half a second later and the heli would have killed me.

Before i plugged of the battery, i checked all servos. The Nick-Servo was powerless. After a new Initialization, the electronic worked fine (as always). I have made a 2h stress test with that servo. Everything fine. Thanks Gerd, a Diabolo is a very stable machine, so there was less damage as i thought.

After 10-15 successfull flights, yesterday evening, it happend again. Initialization was fine, ich checked all servos. Everything ok. I put the machine to the starting place and once again, the nick servo was not moving (but had Power!!). Power off, Power on -> Works....

The servo is an Futaba BLS175SV.
The Log within the unit does not Show any error.

What the hell is going on in my Devil?

best regards,
Chris

My Heli:
Minicopter Diabolo Black Edition
- Kontronik Cool Kosmik 200A
- XNOVA 50XX Tareq Edition
- Spirit PRO Black Edition
- Futaba BLS175SV (Swashplate)
- Futaba BLS276SV (Tail)
- Linus CAPS 25F
- Jeti REX3 (DS14)
- JLOG 2.6GW
- Powerbox GPS2
- SLS Magnum APL V2 4400mah 45C/90C
- DH711 & DH107 Blades

Hi,

great you are OK.
I think that the best is to replicate the problem, then disconnect the servo and then to connect it again (while unit is still powered).
If it will work again, then the problem is in the servo.
I guess that it will be possible to replicate it on the bench without main blades.

It looks like the servo is turned into a disabled mode for some reason.
Elevator servos are often overheating as the first from the cyclic so you can check if the temperature is OK.
Can you tell me what value do you have on the Elevator filter?
Also make sure that the servo cable is not cutted in any way (even partialy). It can be barely visible.

What frequency you have configured for the servos? It should not exceed 200Hz.

Are you sure that your cyclic limits can't exceed servo limits? If the servo receive (for whatever reason) signal that exceed the limit (or is too low) it will be disabled until reconnected again.

Hi ZeXx,

thanks! i am currently in the Office, so i cannot check the Settings right now, but i am pretty sure, that i have set up 333MHz for the swashplate servos and 1 for the elevator filter.
Overheating is not an issue, since it happend on the first flight yesterday.

Is there a Problem with 333MHz on Futaba servos?

best regards,
Chris

Yes, I recommend 200Hz. Servos are rated for 200Hz so I do not recommend to exceed it.

Am I right that when the problem occured, the elevator servo was as when unpowered (without any force)?

The first time for sure (without power), but i am not 100% sure about yesterday.

My Problem is, that the servo worked as i switched the machine on. And it did not work, after i moved the helicopter to the starting Point.
I don't know how big is the risk, that the servo disables while flying...

Good.

When servo will stop holding completely (even if it is powered) then the problem is very likely not caused by the unit.
This is because when servo receive once valid signal, then it will hold all the time, even if it will not receive signal anymore.
The only exception is, when the servo receive signal close to 0 us. But again, if unit will send the correct signal, it should catch again and operate properly.

So if the problem is in the unit, it will send invalid signal all the time from the point it occured - this can be verified just by replicating the issue and then reconnecting the servo (while unit is still under power).
If servo will move again, then it is definitively some issue related to the servo. If it will move only after unit is restarted, then it is some issue related with the unit.

Ok, thank you. I'll try to find a way to reproduce the issue.

best regards,
chris