Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware

Black Square

What about this?

(A:CIRCUIT ON:@GeneralAvionics_EICASCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_PilotCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_CopilotCircuit, bool)
or or d
(&gt;K:AVIONICS_MASTER_SET)
(&gt;A:CIRCUIT SWITCH ON:@AvionicsMasterCircuit, bool)

There's also this post, which attempts to accomplish the same thing.

DrZGard

@Black-Square said in Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware:

What about this?

(A:CIRCUIT ON:@GeneralAvionics_EICASCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_PilotCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_CopilotCircuit, bool)
or or d
(&gt;K:AVIONICS_MASTER_SET)
(&gt;A:CIRCUIT SWITCH ON:@AvionicsMasterCircuit, bool)

There's also this post, which attempts to accomplish the same thing.

Still not getting power to external radio stack. A curious problem. I'll review the wording for the King Air.

DrZGard

I am curious is this wording is what is needed to trip FSUIPC into sensing the native Avionics Master has been turned on? (A:AVIONICS MASTER SWITCH, bool)

Black Square

I was just testing this one my end too, and I saw the correct behavior with A:CIRCUIT AVIONICS ON, bool)

Your variable also appears in the SDK, but you might need to add an index to access it: A:AVIONICS MASTER SWITCH:1, bool)

DrZGard

@Black-Square said in Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware:

I was just testing this one my end too, and I saw the correct behavior with A:CIRCUIT AVIONICS ON, bool)

Your variable also appears in the SDK, but you might need to add an index to access it: A:AVIONICS MASTER SWITCH:1, bool)

Edit to this?

(A:CIRCUIT ON:@GeneralAvionics_EICASCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_PilotCircuit, bool)
(A:CIRCUIT ON:@GeneralAvionics_CopilotCircuit, bool)
or or d
(>K:AVIONICS_MASTER_SET)
(>A:AVIONICS MASTER SWITCH:1, bool)

DrZGard

Tried both... didn't work yet. Maybe didn't put them in right place.

DrZGard

Maybe if there is a way that when the pilots and/or copilots switch is on the signal is sent in MSFS to trip the native avionics master coding.

Randolf

@DrZGard did you check out the new 1.1 version? Changelog suggests this may have been addressed.

DrZGard

@Randolf said in Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware:

@DrZGard did you check out the new 1.1 version? Changelog suggests this may have been addressed.

Just saw that this morning. Hopefully get a chance to try it at lunch.

DrZGard

I wish I could report that version 1.1 fixed the radio stack but it is still dead. Fortunately the yoke, pedals, quadrant and switches associated with the console do work and I am able to fly the Starship. The radio stack and RIC (remote instrument console) which has the heading, baro, and obs knobs are all unusable.
Here is a shot of using it with the BlackSquare King Air which I have custom programmed most of the functions to work with.
alt text

Randolf

Do you know which variables your setup is looking for to enable the radios? Because it seems to me that the problem might be elsewhere.

DrZGard

@Randolf said in Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware:

Do you know which variables your setup is looking for to enable the radios? Because it seems to me that the problem might be elsewhere.

That programming is deep in FSUIPC and Pete Dowson's PFC module which I don't have access to. I am able to assign the hardware switch for the avionics master (as well as basically any other switch/knob) with FSUIPC to any other designated function... or multiple of functions. For example the Pitot heat switch when flying the King Air also turns on both pitots, fuel vent heat, and stall sensor heat.

Within the PFC module it is looking for the native avionics switch to be turned on which then enables the radio stack and PIC to function within the sim.

Edit: I can either use the avionics master on the hardware itself which will turn on the avionics master in almost all aircraft and/or I can mouseclick the avionics switch on the virtual panel of almost any aircraft and the radio stack and PIC are enabled.

DrZGard

I've used this hardware since early 2000's when I purchased it after reviewing it for AVSIM at the Seattle AVSIM conference. It has worked with FS2004, FSX, and MSFS2020. It was designed for use with the FAA certified version of xPlane which I have v8 and v9 and have used for instrument recurrency. This is the first time and only aircraft that the radio stack doesn't turn on for.

Black Square

Now that's a nice setup! I've always been fond of those big metal units when I've handled them at flight schools, even if they are a little archaic these days. The all metal construction would be hard to beat with anything else on the market. I'm sorry this is still causing you problems, but I would really have to know what variable it's looking for in order to fix something less obvious with Starship. I'll look for differences with the King Air, though..."

Oh, you know what? I have an idea...

Just as a test, open the systems.cfg file, and locate this line:

circuit.203 = Type:CIRCUIT_LIGHT_LOGO       #Connections:bus.35       #Power:0.3, 0.4, 20        #Name:GpuStrobe

Directly after it, add this:

circuit.204 = Type:CIRCUIT_GENERAL_PANEL       #Connections:bus.14       #Power:0.1, 0.2, 15        #Name:General Panel

I have a hunch that will solve it.

DrZGard

@Black-Square said in Starship avionics electrical coding doesn't trigger MSFS avionics master switch on PFC hardware:

Now that's a nice setup! I've always been fond of those big metal units when I've handled them at flight schools, even if they are a little archaic these days. The all metal construction would be hard to beat with anything else on the market. I'm sorry this is still causing you problems, but I would really have to know what variable it's looking for in order to fix something less obvious with Starship. I'll look for differences with the King Air, though..."

Oh, you know what? I have an idea...

Just as a test, open the systems.cfg file, and locate this line:
circuit.203 = Type:CIRCUIT_LIGHT_LOGO       #Connections:bus.35       #Power:0.3, 0.4, 20        #Name:GpuStrobe
Directly after it, add this:
circuit.204 = Type:CIRCUIT_GENERAL_PANEL       #Connections:bus.14       #Power:0.1, 0.2, 15        #Name:General Panel
I have a hunch that will solve it.

IT WORKED!!!!!!!!!! I am so excited right now. Discovering what native bindings are working... and a lot of them do! Now I can get to work programming the buttons that don't work correctly and get a really immersive simulation going.

I still have those Starship Diaries flightplans to assemble. You know I know the Beechcraft rep that flew the Starships a little over 3,000 hours all over the world for airshows and private demonstrations. He has given me some very good insights on flight operations and sweet spots for the aircraft. I can't wait to show him this gem you have created in MSFS. He says that the Starship years are his best memories of his professional life flying and selling for Beechcraft.

Black Square

Wonderful! It was teamwork, because posting the King Air made me thing of just the right thing. I will add this to the release build for you. Let me know what kind of fantastic stories you might get from this very lucky individual. Have fun, and let me know if there is anything else I can do for you!