Hi guys,

2 questions:

One, began planning/sketching/CADing my hornet semi-scale cockpit and currently looking at electronic/components.
I'm on mouser.com and was wondering something regarding toggle switches.

What type is actually best for 2-pos / 3-pos switches? Is it safe to assume I should go with on-on / on-on-on switches, since I want a different keystroke for each position?
Example: The HUD brightness switch. It's a 2-way toggle to switch between "Day" and "Night", so do I use an on-on switch? Or should it be an on-off switch and the keystroke is determined by the software (on keypress/on release) ?

Same goes for 3-way, Example, HUD Reject switch, I guess I want a 3-way on-on-on right?

I'm planning to use either a BU0836X or an I-PAC4 board... more tempted by the I-PAC since a lot more inputs are possible with their shifted mode.

My other question is regarding LED control. What kind of board/electronic do I need to control LEDs in my cockpit, for example, if I want a working annunciator panel, master caution, FIRE etc...? And I guess I have to do some programming to catch the event somewhere, is that done thru FSUIPC?

For sure the LED part is for a later phase in my design, I'm starting with basic/most often used switches first, and will add more with time.

Thanks for the tips!


Thanks!

Hi,
I can only give you what I've found out from building my own pit.

1. Switch selection will be determined by the input controller you use for them. I used an Opencockpits card which needed momentary action switches, so that's what I've got. If your controller can use straight toggle switches then that would be better and more realistic. The question that I asked myself was "When the program starts up does it know which position the switch is in ?" i.e If you crash and the landing gear lever was in the up position, would the program know the next time, or would it assume it's in the down position. Thats another reason I used momentary action switches.

2. I'd recommend a look at the outputs board from Opencockpits (no, I don't get a commission). I think it has 64 outputs and their stuff was designed to work with FS. They're at http://www.opencockpits.com/

Hope this helps you decide.

Cheers,

Andy

VERY GOOD POINT!

I was actually considering this! Using "real" toggle switches would require to "reset" the pit almost on every flight.... could be a hassle, although the Superbug "remembers" almost all switches after a flight ends/crash, not a problem for the Superbug, but could be a problem for other aircraft/sim.

FWIW, both the bu0836x and the i-pac support non-momentary toggles.

Thanks for the tip on opencockpit, I'll have a look!

Are you shure that the BU0836 can use non-momentary switches? Wont you get a constant signal? What I read about the i-pac, that that one supports only 6 switches or something. Thats to little for my needs..... I'm still looking at a product that's cheap, simple and supports "real" toggle switches(non-momentary). And has a whole bunch of inputs off coarse
Sorry for the hi-jack!

Hey JAK, I use two BU0836X's, to get a toggle to not show up as a constant signal I use a program called SVMapper. It will two a signal to the game just as if it were a momentary switch, and then it will show another momentary signal when you flip the toggle off. So you can have gear up with toggle up and gear down with toggle down. There are several programs like this around. SVMapper only allows the use of two devices but others can use as many as you wish. With my two Bodnar boards I have 80 switches (I use the hat inputs to get four more switches over the 36 normal ones) and 16 axis'.

I was also considering the BU0836X for my pit, but after 3 failed attempts to get an answer if Leo Bodnar would ship it to Brazil. I assumed he could be retired or not producing the boards anymore.

Does anyone know if he's still active?

back to topic...
Well JAK, similar to PropNut my idea was to use the BU0836X for interface and the XPadder for converting the JoyButtons to KeyPresses

té mais
tityus

AHAAAA!!! Thanks for the headup guys!!! For some years now I have a BU0836 laying around somewhere, but always thought switches where a no go with that interface. Have an evil plan in my head, making a basic lockon setup with two side consoles. And alway hated the idea of using buttons.
Tityus; I read so much about Leo Bodnar lack of communication, but the guy delivers!! Maybe Sokol1 has more answers about getting a board to Brasil(I thought he also has a BU0836)

JAK, thanks to remember.

Tityus,

Saudações from Uberaba-MG.

Just put the order in L.Bodnar page, in ~one week the board arrive at you address.
I allready got three BU, and know more people from Brasil that buy from him.

In Brasil you have a local made alternative, for similar cost: www.usbinterface.com.br
Notice that this board is intended for Flight Simulator fans, so he priorise encoder user, show in Windows 16 buttons and 8 encoders (plus HAT and 8 axis)
But have 64 imputs - inputs upper than 32 need keymapper, like freeware SVMapper of Joy to Key, or payware Xpader.

Or, if you are adept of DIY, you can build a Mjoy8 or 16, or Joy.01 controller with ~U$25.

Sokol1

Leo is still very much alive and working. I ordered a board from him last Friday, and it shipped this past Wednesday. Assuming ones country doesn't have a trade embargo against the UK, I'm sure he'll ship to you.

So, to come back to the original topic, I have decided to go ahead and use on/on, on/on/on toggles. I decided I wanted a more realistic experience and am willing to "reset" the cockpit before each if needed, although with the Superbug it's not much of an issue as most of the switches are "remembered" on each successive flights, only a few are reset, such as the seat lock.

As for controllers, since I'm on a delicate financial position lately, I've decided to wait and use the cheap keyboard hack method instead. I tested and evaluated a bunch of macro softwares for this setup, but none do everything I want so I've started writing my own interface software, which will be coded specifically for keyboard-hacks and support all the array of switches I'll need in my pit.

I might distribute it if anyone is interested, when it's good enough.


I'm still looking for how to convert sim events in LED lighting, guessing a need a special controller card for this, if anyone knows anything about that, please let me know.


Cheers!

JAK, Sokol1 and Aggressorblue,

Thanks for the replies. I'll consider this blind deal based on your reports.

Saudações from São Paulo!

Well, Sokol1, in theory I am... I have the needed background in electronics; when life was worry free and 8bis was uh huuu, I designed some circuits with the Z80 and was also proficient in 6502 assembly. But then, workaholic I am, engaged in a hectic life and presently I barely have time to fly.

As one may conclude, I haven't started a simpit project yet, but I fancy one.

té mais
tityus

Do you really need macro software for the 'bug? I thought every click-able action was also mapped to a key?

I'd also suggest searching for lighting programs for the Logitech G940. There are a few user-made programs out there that fill in the gaps that logi couldn't be bothered to, and make the three way lighting functional in FSX. From what I understand, those programs aren't just for show, they actually display color based on feedback from the sim. For example, gear down yields a solid green, when you press that button, it flashes green for the duration of gear travel, and goes solid red for gear stowed and locked. If there is an issue with the gear, say in a situation where it won't raise due to being speed-soaked, the light would flash orange. That said, tracking down the authors of that code might be a good way to see how their getting the feed from FSX.

In addition, simconnect probably has outputs that could be sent to a LED controller.