I had a scary moment last night. While connected to the computer to make some small changes I changed the software bank from 0 to bank 1 and the motor started up and the heli spun out on the table. I quickly reached the battery and disconnected it. Luckily nothing and no one was hurt though the blades smacked my laptop screen pretty good. I normally disconnect my motor from esc before connecting to software but I didn't last night thinking I was just going to make a quick change. That will not happen again.
I disconnected my motor and reconnected to software everything worked fine in bank 0 but as soon as I changed the tab to bank1 or bank2 the cyclic locked up and the heli didn't respond to transmitter inputs (except for rudder) until I switched the software back to bank 0. I can change everything in the software but cannot get the heli to respond in bank 1 or 2. Everything seems to work fine with the heli when not connected to the software, but I'm afraid to fly it until I figure out what's going on. There is nothing in the log when I checked and the software isn't freezing up, it's just the heli cyclic that freezes and motor engages.
I checked my transmitter and setup but every thing was right. I had both throttle hold on and I have a second switch set to throttle cut as a second fail safe which was on too. I've gone through everything multiple times and cannot figure out what happened.
The only changes I made in software were to speed up rudder 1 point in bank 1 and 2 and changed governor throttle response in bank 0 from 4 to 6 (they are at 7 in Bank1 & Bank2). The odd thing is that I had been in the software for a couple of minutes and had changed banks multiple times without any issue. It was only after I changed my bank 0 gov settings that the occurred.
Im running Spektrum DX9 with 2 DSMX sats. I've had over 35 flights on this heli since the last spirit update. I've probably had 80+ flight on this heli (Goblin 380) all with Spirit. I've had probably 75+ flight with the same Spirit unit on a Trex 450l before I moved it to the Goblin. This is the only problem that I've had since I've owned this unit.

Sean

It is back to working like it should today. I spent an hour trying to get the motor to start without command again while connected to the computer. However, It worked exactly how it should. I guess I'll have to write it off as a computer glitch that caused it. It is bizarre how it happened a few times in a row last night though.
Thanks,
Sean

Hello,

I recommend to check failsafe. Failsafe can be triggered for a very short time when you are saving the settings.
And also to check if esc is arming properly before each flight/power cycle.

I am on holiday, so it is hard to answer. But I hope it will be ok now.

_________________
Spirit System developer

I've tested the unit in every way I can think off or the past week and I cannot get the problem to reoccur. The fail safe works like it should. That was the first thing I tested. This problem did repeat a couple of times in a row on one night but hasn't happened again since I've restarted my laptop. When it happened the second time that night I checked a few things and the cyclic had locked up and didn't respond to Stick inputs, the motor started fast but didn't spool up all the way, and the rudder did somehow still respond to stick inputs. I really think it was just a computer glitch that caused it. I will of course always either disconnect my esc or remove my blade from now on when connecting to a computer. My wife gets up a leaves the room every time I connect the Goblin. I've tried explaining that I have the motor disconnected and there is no way it can possibly start, but she doesn't care. I can't wait until the Bluetooth for iPhone comes out. I will buy that the day it comes out. I have one for another flybarless unit I use and it makes changing things at the field so much easier.