The systems are overhauled by the Black Square Developer only. Credits to that only belongs to him. It is his addon product and he did a magnificent job. I only made some drafts for flight model changes. Kind regards, JayDee
5 Likes
The right engine is started first because it is closer to the battery, which is located in the right wing root. Therefore there is less of a voltage drop when starting the right engine compared to the left. This allows for a slightly higher Ng% on start, producing a slightly cooler peak ITT, which is better for the engine.
After the right engine is started, the right generator is switched on, which assists starting the left engine.
Interesting fact (for those that care), on older model King Airs, there are current limiters that connect the generators to the main busses. The initial draw when engaging the starter is significantly more than the tripping point of these limiters, so when starting the left engine, the right generator is initially switched off after recharging the battery from the first start. Only after passing 10% Ng is it switched back on to assist the second start, as the current draw drops quickly and is now below the tripping point of the current limiters. At first this quick swichology mid-start is a bit of a nightmare and is hard to get right, but the muscle memory quickly builds up and it becomes second nature.
9 Likes
Thanks so much for this explanation.
Had my first failure. Right engine fail. I feathered it and it went in to a non recoverable spin from FL20. weather radar showed both engines at 100% and no failures.
Is there a file to look at to see what really went wrong?
I had 110 hours in it.
1 Like
Just curious, were you climbing out when it occurred? Also did “you” feather it or did you have autofeather engaged?
Had been level for 2 hours at FL20. Autofeather was disengaged.
Safe to assume you had enough fuel?
1 Like
OK, good to know…
wow, 2 hours at 2000ft, hope it was flat terrain 
Could have had a spike in your controller condition lever. Happens from time to time.
PS, if you get into a spin like that, shut down the other engine and feather both props to prevent any asymmetry thrust and drag.
Sorry 20,000 feet
Left engine was failed and tried to feather it and restart that’s when it went into the “death spiral”
Feathered right prop
shutdown right engine
applied approach flaps to slow down
almost regained control when it crashed
Has anyone had any luck getting keybinds for the AP disconnect and Pitch Sync switches? They’d be handy to not have to click around for. Also be interested in mapping the vertical speed rocker to something more handy.
Yes, Assigned both pitch sync and AP to buttons on my controller. Just standard bindings through MSFS controls options screen.
“TOGGLE AUTOPILOT MASTER”
“FLIGHT DIRECTOR PITCH SYNC”
Rocker switch is: each press is 100fpm (no rocker animation but it does work)
“INCREASE AUTOPILOT REFERENCE VS”
“DECREASE AUTOPILOT REFERENCE VS”
I have a Honeycomb Bravo and am unable to feather one prop without the other side feathering as well.
Could you share your bindings… or at least tell me what is wrong with mine?
Mine are as follows:
I can only do Feathering with 3rd party software. FSUIPC in my case.
1 Like
One thing I found odd when using the SPAD data monitor to build a profile was that the TWOTTER spoiler axis variable was showing when reverse thrust was engaged [for readers who are not familiar, this is the variable developed by Aerosoft in their Twin Otter to simulate the enhanced drag effect of prop beta range].
I didn’t have the time to investigate properly, but needless to say was baffled/intrigued that the SPAD was registering this variable in the Blacksquare King Air. Perhaps this is something to do with the super stopping power? (And apologies if this has been resolved in some more recent post)
It’s the Hold Propeller Reverse Thrust. Same with me. Feathering used to work but it got broken I think at SU9. I’ve been hoping they would fix it.
While I have neither aircraft note that these programs can themselves set local variables. For example I use “(L:AAO_Comm_1_Tag,·Number)” to switch from 10000s to 1000s to 100s etc. when setting Com 1 frequency sequentially with a keypad. This tag appears in the dev mode after using the scripts, exactly like an aircraft specific LVAR would. So if you are using some custom command scripts that were made with Twotter in mind, it might be porting some Twotter code over. Search through the interior.xml should show if this plane is actually using same LVAR as the Twotter.
Loving the Black Square treatment on this bird! One minor complaint; the clickspot to reset each of the generators is too small. I wind up hitting the gang flap all too often, shutting the generators and battery off. Otherwise, really love flying this machine. 
3 Likes
I’m not actually seeing these things work:
-
TOGGLE AUTOPILOT MASTER - turns the autopilot off but subsequent presses don’t turn the FD off
-
FLIGHT DIRECTOR PITCH SYNC - with WTT enabled, does nothing. Without WTT, it reverts the FD to pitch mode and and won’t re-capture a new airspeed in IAS mode.
-
AUTOPILOT REFERENCE VS - only appears to work in VS mode, and has no affect in pitch, IAS or Climb/Descent modes