FSUIPC Generator, Lights, and Buttons

[coolmanak]

Hello guys.

I'm working to get my overhead panel (hardware) configured with the Wilco A320 overhead panel (software) via FSUIPC.

So far I've encountered 3 problems, and was hoping you could help:

#1. Lights. The mouse macro will not recognize light switches being moved unless they are a 3 possition one and can therefor move forward and back. FSUIPC also does not have Beacon, Wing, Nav, and Taxi lights in it's "default" configuration options. Any way to get those lights controlled?

#2. Buttons. All of the buttons caught using the mouse macro will only last for a milisecond. After that, they "revert". I.E. the APU master will open the valve for a milisecond before it closes it again. Any way to get it to be "locked" more?

#3. Generator. FSUIPC will NOT recognize certain clicks on the Wilco overhead. All of them except two also have FSUIPC "default" commands that work. Those two are Generator 1 and Generator 2. Amazingly important buttons which I can NOT control via FSUIPC. Any work arround this too?

Thanks for the help. I really hope to get things set up nicely, and these are the 3 obstacles in my way.

[Pete Dowson]

FSUIPC also does not have Beacon, Wing, Nav, and Taxi lights in it's "default" configuration options. Any way to get those lights controlled?

There are 10 individual light switches, for all lights supported by FS, in offset 0D0C. You'd need to use the Offset Word controls (Setbits, Clearbits or Togglebits) to operate the switches that way. Offsets are documented in the FSUIPC SDK.

#2. Buttons. All of the buttons caught using the mouse macro will only last for a milisecond. After that, they "revert". I.E. the APU master will open the valve for a milisecond before it closes it again. Any way to get it to be "locked" more?

No idea. That sounds like a mechanism peculiar to the panel. How do you do it with the mouse, hold the mouse button down? If so have you tried using the assorted numbers on the end of the macro which qualify the mouse action -- maybe you need a "button down" when you press your real button and "button up" when you release it. The numbers that can be used are listed in the FSUIPC dox.

#3. Generator. FSUIPC will NOT recognize certain clicks on the Wilco overhead. All of them except two also have FSUIPC "default" commands that work. Those two are Generator 1 and Generator 2. Amazingly important buttons which I can NOT control via FSUIPC. Any work arround this too?

Don't the FSUIPC-accessible FS generators work for that panel? Have you tried using the Event logging in FSUIPC to see if those clicks merely generate FS controls? The FS names include "toggle alternatorN" for each engine 1-4. Otherwise check the FSUIPC offsets and use the offset controls.

Regards

Pete

[coolmanak]

Well, I've gotten the pushbuttons working, so that's a problem down.

Where could I find the lights in FSUIPC? I was about confused about this.

Also, I can not find a "stock" FSUIPC generator control (these are ELECTRIC generators by the way, not engine). I've looked through it many times, and it just did not appear to work.

[Pete Dowson]

Where could I find the lights in FSUIPC? I was about confused about this.

As I said, offset x0D0C in a 16-bit WORD with 10 or its bits acting as one light switch each. The offset documentation is in the FSUIPC SDK, as I thought I mentioned? What part are you confused about?

This particular offset has been discussed in this Forum before too. Search for "lights", or probably better "0D0C".

Also, I can not find a "stock" FSUIPC generator control (these are ELECTRIC generators by the way, not engine).

Did you use the logging as I suggested? Are you sure these are FS simulated and not merely local to the panel you are using?

Regards

Pete

[coolmanak]

All the problems are now fixed.

To get the switches working, I just had to re-do them for each of the individual aircraft making them aircraft specific rather than having all the key presses as one common deal. (IE naming all of the APU Start clicks "APU STRT" does not work, it must be done for the individual Wilco aircraft).

And the default FS "master generator", which I never even considered using (because most default FS controls do not work with the Wilco bus), turned out to do the trick.

I have just one question remaining for you: Is it possible to have JUST wing anti-ice? I've gotten individual Engine 1 and Engine 2 anti-ice buttons working for the Wilco A320, but the can not find an individual Wing Anti Ice (the default FS command does not work in this case).

Thanks very much for all your help! Yesterday at this time I had three buttons on my overhead panel working, now I have about 3 buttons left!

[Pete Dowson]

All the problems are now fixed.

Great!

I have just one question remaining for you: Is it possible to have JUST wing anti-ice? I've gotten individual Engine 1 and Engine 2 anti-ice buttons working for the Wilco A320, but the can not find an individual Wing Anti Ice (the default FS command does not work in this case).

What is the "default one which doesn't work"? The only one I know for wing de-ice is "TOGGLE_STRUCTURAL_DEICE". Doesn't that work? What does the log show when the switch is operated?

Regards

Pete