I too have this problem.. have been following this (these) threads.. for a while now..

Let's try looking at it, "forest from the trees"... meaning, it shouldn't matter how inept the user might be, as far as power management goes..

Even if he jumps in, turns just the battery on, and then powers up the avionics and all the lights.. then goes for a walk (obviously draining the battery).. comes back hours later.. ground-power should allow him to fire-up the APU, and start the engines.. right ?

I think it's power hierarchy/logic problem.. like the only way the the engine-start-sequencer can be powered, is by the FSX battery.. and the only way to charge, or keep the FSX battery charged, is via engine driven generators.

The engine-start-sequencer should be able to get power from ground-power, or the APU.. OR the battery itself should be able to maintain a charge (or get re-charged) by either (or both) the ground-power, or the APU .. right ?

I've poked around all the XML gauge folders, and I've seen no reference to, "Aircraft Variables" .. only references to "Local Variables". My guess is, that CS needed to define a lot of stuff independent of FSX, to make its systems "work".. and along the lines, the battery/avionics/starters, ect.. ended up with an illogical set of interactions... leaving "broken" connections.

All of the gauge folders, and XML files, and local-variables are named by proprietory/cryptic conventions.. so I can't debug this. My XML skills are limited to my own, freeware work (found under the name, "Brett Henderson"), but I know enough to know that this can be a simple, "hot fix", long overdue. It severly limits a sim-pilot from using realistic, emmersive pre-flight practices.. a large reason for why we but these beautiful models..