iKON2/Brain2 brings nitro heli's throttle servo to idle after a couple min of activating governor
I am trying to understand a problem I am having w/my Kraken 700 Nitro/Brain2 (and iKON2) governor behavior. I have 2 units (1 x iKON2 BTHD/ 1 x Brain2 BTHD - Both @ Version 3.3.039) that I have been using to debug this problem and both exhibit the same behavior described as follows:
Setup 1 (No governor) - idle, spool up, hover/normal-mode/idle-1 mode/idle-2 mode are all okay.
Setup 2 (Governor active) - upon switching to "Setup 2" (and idle-1) in mid-flight, the heli goes into governor mode and then within 2-3 seconds shuts the throttle servo down to idle position. Motor is still running after this is done - "Emergency" landing has already taken place by this point. Observations: Throttle servo is locked into idle position and has power - attempt to move the throttle servo's arm by hand does not allow movement - servo still energized and doesn't allow movement. Attempts to change from "Setup 2" to "Setup 1" does not change servo behavior nor is there any response from the throttle servo from the Transmitter's throttle (left) stick. Once engine is killed (via fuel cutoff) while leaving the TX/Rx energized and running, servo starts working again.
NOTE: After observing this behavior on the Brain2 BTHD, I switched it out to the iKON2 BTHD and both show the same behavior.
Setup 3 (Governor active) - not tested.
Setup (Relevant devices listed only):
- Kraken 700 Nitro w/OS 91SZ Engine
- Throttle servo: KST micro (KSTX12-508)
- Spektrum DX8 w/2 satellites bound @ 11ms on DSMX
- RPM Sensor: Spektrum SPM9560 Mounted with care and attn to RPM sensor on iKON Configuration Interface app showing green when sensor is triggered.
- iKON Configuration Interface App notes: Pulses for rotation 1, Main ratio: 8.23, Tail ratio: 5.070, Speed 1: 1650, Speed 2: 1750, Speed 3: 1850, remaining values in Gov are default.
- Backup Capacitor Power Supply: XGuard AAVXG0114
- Throttle Curves:
- Normal: 0-50-100
- Idle-1: 65% all the way across
- Idle-2: 85% all the way across
- ATVs (Travel) - Throttle: Input values adjusted to 0% - 100% and checked on Governor Setup page of iKON Configuration Interface App
As always, to "try" to understand what is happening in your model, we need:
- The Flight Control Unit configuration file.
- The FCU Events file (not a screenshot but the csv file!)
- The flight logs in which the problem occurred (not a screenshot but the csv file!).
thanks for the advisory. I'm glad to see you ask for those things (as we do in I.T. as well). Pls excuse the delay (company merger in prog). I had problems with the above mentioned iKON2 HDBT unit (user error) and had to switch back to the Brain2 HDBT unit and schedule some time to rerun flight tests. I finally did yesterday and so here are the 3 files you requested. I am not sure if the unit recorded the flight properly and if this truly was yesterday's flight log (the more recent ones were just a bunch of flight lines as if it recorded bench time or something). I've been having inconsistency issues with flight logging lately but hopefully the configs & events are comprehensive and in tact. But please let me know if I need to rerun if the flight log is not what was expected (I wish it was somehow dated or timestamped).
Also, I changed out my RPM sensor from the Spektrum SPM9560 bottom-engine mount to an "Align" type w/magnet on fan as I know these are more consistent.
I look forward to your analysis.
The Events do not show a valid flight number.
After several "Voltage <= 4V3" events we see several model start-ups with flight log number 28 which are cancelled and deleted because the configuration software has been connected to the control unit (so, it is a setup session and not a flight).
We do not know which flight log number was sent because the file was renamed and the flight number was deleted.
However, it does not appear to be a log of an actual flight.
If the firmware of the control unit has been updated, we suggest to reinitialize / reformat the flight log memory using the "Erase all Logs" button in the Flight Logs screen.
Also, since the problem you asked for a solution to is related to the throttle, it would be useful if you reprogrammed the throttle parameters that are set by default after a factory reset and that you deleted all. You can run the software in demo mode and see which parameters are set by default with new FCUs or after a factory reset: