Governor motor shutdown?
Posted: Sat 24. Jun 2017 15:55:46
First of all I am using the Spirit (v 2.4.1) governor on my Trex 450 in combination with a Hobbywing 60 A V4 ESC i fixed wing mode without a problem. Governor works nice, auto bailout also, no issues with spoolup.
I have setup the governor on my Trex 550 DFC with a Spirit Pro (v 2.4.1). It is a 12s conversion running a Align 130 A ESC (so a Hobbywing really), running a KDE 550XF 565 kv motor. I also used a Scorpion backup guard with this setup. Tested it extensively on the bench and all looked okay. Got an ocasionall RMP signal is noisy message in the log though. Two first flights went very good, governor was easily tunned in real time (excellent Spirit feature btw).
For the next two flights I changed the following: moved the DFC arms on the swashplate to the inner hole in order to be in the optimal mechanical range of resolution (at least 90 on the 6 degree setting) and instead of the Scoprion backup guard I used a Optipower backup guard. Don´t know if you are familiar with these two but they do work slightly different. The Scorpion backup guard puts out around 5.5 V continuesly. The Optipower one once powered up senses the voltage and puts out I believe around 0.5 V less. In my case I am running standard servos so I am running 6V on the Align ESC BEC.
First flight: Up into hover, IDLE UP 1, IDLE UP 2 and after a few seconds the motor shutoff. I was just around 3 m above ground so landed safely. Hooked up the WiFi module and logged showed first a "RPM signal noisy" and right after "RPM signal lost". Had to power down and power up again to be able to be able to start the motor again. Should have stopped here.
Second flight: Raised RPM sensor filter to 8. Took off, some pitch pump about a minute in flight all looked okay. Did some flips, stationary rolls all looked good so I started flying. After about 1 minute motor cut out again, this time it was not the optimum auto but got the heli down with minimal damage. Same messages in the log.
After bench testing two more times for a total of approximatelly 7 minutes of running without blades I was able to reproduce the behaviour only once.
I am a little bit scared of using the Spirit governor now untill I know exactly what is causing this. ESC does not go into any error modes.
My question is firstly: If RPM governor signal is lost will the Spirit automatically shut the motor off and require a reboot in order to continue?
Second can it be the Optipower backup guard causing the issue? Moving the DFC arms on the swashplate inwards would in principle put some more strain on the servos but that could hardly be causing my governor issues. Hope you can help Tomas.
Skickat från min F5321 via Tapatalk
I have setup the governor on my Trex 550 DFC with a Spirit Pro (v 2.4.1). It is a 12s conversion running a Align 130 A ESC (so a Hobbywing really), running a KDE 550XF 565 kv motor. I also used a Scorpion backup guard with this setup. Tested it extensively on the bench and all looked okay. Got an ocasionall RMP signal is noisy message in the log though. Two first flights went very good, governor was easily tunned in real time (excellent Spirit feature btw).
For the next two flights I changed the following: moved the DFC arms on the swashplate to the inner hole in order to be in the optimal mechanical range of resolution (at least 90 on the 6 degree setting) and instead of the Scoprion backup guard I used a Optipower backup guard. Don´t know if you are familiar with these two but they do work slightly different. The Scorpion backup guard puts out around 5.5 V continuesly. The Optipower one once powered up senses the voltage and puts out I believe around 0.5 V less. In my case I am running standard servos so I am running 6V on the Align ESC BEC.
First flight: Up into hover, IDLE UP 1, IDLE UP 2 and after a few seconds the motor shutoff. I was just around 3 m above ground so landed safely. Hooked up the WiFi module and logged showed first a "RPM signal noisy" and right after "RPM signal lost". Had to power down and power up again to be able to be able to start the motor again. Should have stopped here.
Second flight: Raised RPM sensor filter to 8. Took off, some pitch pump about a minute in flight all looked okay. Did some flips, stationary rolls all looked good so I started flying. After about 1 minute motor cut out again, this time it was not the optimum auto but got the heli down with minimal damage. Same messages in the log.
After bench testing two more times for a total of approximatelly 7 minutes of running without blades I was able to reproduce the behaviour only once.
I am a little bit scared of using the Spirit governor now untill I know exactly what is causing this. ESC does not go into any error modes.
My question is firstly: If RPM governor signal is lost will the Spirit automatically shut the motor off and require a reboot in order to continue?
Second can it be the Optipower backup guard causing the issue? Moving the DFC arms on the swashplate inwards would in principle put some more strain on the servos but that could hardly be causing my governor issues. Hope you can help Tomas.
Skickat från min F5321 via Tapatalk