Quote from Hangar45 Admin on December 18, 2017, 8:33 am

(Original thread started on 10-23-09 by Mark L.)

I am looking at the Pokeys cards and playing around with the Pokeys demo console. While it supports some analog inputs, it's several short for the Lear45 in regards to the major analog inputs. I know we can control the engines separately, so does this mean I will need a Leo Bodnar card to interface my throttles? It seems pricey to use two Pokey cards, although I would still use the connections, but I also have the IOCards available.

 

Actually, it will take more than one card anyway, either a Pokey or a Leo. The flaps and spoiler are pots requiring analog, so it will require another card anyway. The question I suppose would be, the Leo or Pokeys to handle the TQ? I'm thinking the Leo card for the TQ and the Pokeys for the encoders etc.

 

UPDATE:  (10-17-16)  The Pokeys55t and Pokeys56U has been replaced with the Pokeys57u which is basically the same card but with upgraded features and abilities. Here is a link to the Pokeys57u card:

https://www.poscope.com/product/pokeys57u/

 

(Posted by Vince on 10-24-09)

As I have both the Pokeys and the Leo Bodnar cards, here is a side by side comparison of the two cards in various aspects:

 

1) Analog Input Axis:

BU0836X has 8 analog inputs with 12 bit resolution. Pokeys has 5 analog inputs with 10bit resolution. Both are seen in windows as generic analog axis and can be used in FSUIPC to drive TQs or Yokes.

 

2) Buttons:

BU0836X has 32 inputs, Pokeys has 55 (only 53 really usable though). The 32 Bodnars keys are seen by windows as joystick buttons. You can use direct button assignment through FSUIPC for all of them. the 55 Pokeys buttons are usable instead as keystroke mappings to be used in the key mapping FSUIPC facility. It's a step more to do, but advantage of Pokeys is that you can use both normally open and closed buttons because it allows to invert pin status. Pokeys also supports macro features on every input and trough it you can use latched buttons easily and as of keystroke support it can be used for many other different purposes as well. Last Pokeys support a keyboard matrix too, so you can use 16 of it's inputs to drive a 8x8 key matrix giving you 64 more buttons to use.

 

3) Encoders:

Bu0836X supports up to 16 encoders, but... There's no clear way to use them in FSUIPC. You'll need to use extra software to map button press of CW and CCW rotary encoder to a key and then use it in the keystrokes tab in FSUIPC to map to a function. Pokeys insteadcan use up to 25 encoders and has direct key mapping for each side turn and support of multiple detents/rev encoders.

 

4) Outputs:

BU0836X doesn't support outputs at all. You can't use LEDs, PWM driven encoders, relays etc.. with it. Pokeys can assign output to any of it's 55 I/O, though programming skills are needed to have this feature available to FSUIPC and FSX. Pokeys can anyway drive with outputs any other hardware with a quite complex logic.

 

5) Rotaries:

Both cards can use rotaries and each pin has to be assigned to an input.

 

(Posted by Mark L. on 10-24-09)

I definitely see the advantage of the Pokeys, but still short on analog inputs. Here is a list of all of the analog inputs in the Lear45:

 

Yoke Elevator - 1

Yoke Aileron - 1

Yoke Rudder - 1

TQ - Left Throttle -1

TQ - Right Throttle -1

Flaps -1

Spoiler - 1

Capt L Tow Brake -1

Capt R Tow Brake -1

FO L Tow Brake -1

FO R Tow Brake -1

 

So it looks like we will need another card of some type, another PoKeys or a Bu0836X.

 

(Posted by Vince on 10-25-09)

Consider also that the BU0836X only has 32 inputs, so to drive the whole AAS suite you'd need three of them (2 Pokeys anyway). Maybe the best thing is having a mix of cards to be used for different situations. ATM, my "I/O boards garage" has: 2 Pokeys, 1 BU0836X, 1 Opencockpits Mastercard+USB Expansion. The plan is not complete, but I suppose that I will use the 2 Pokeys cards to manage the AAS suite+CDU (with the matrix facility)+TQ+some general cockpit logic, like panels lighting, general audio management and my special FMS. I'll let the BU0836X run some basic already available FSX offsets that don't have relations with other parts of the cockpit and Opencockpits card for the FGC and lower MIP panels that will include all the logic for the electrical, hydraulic and light system. My Yoke and rudder will use the Saitek board because I'm going to modify their commercial parts so I don't need to rewire to a different board.

 

(Posted by Eric Tomlin on 12-03-09)

Vince, now that I have both a Pokeys board on hand as well as a temporary FGC from Scott along with DU bezels, I'd like to know what I need to get the Pokeys board up and running the 5 rotary encoders on the FGC. If I remember they are gray encoders. What do I need to get them talking to the Pokeys board for FS autopilot CRS, HDG, ALT, and VS?

 

(Posted by Vince on 12-03-09)

Okay, here's the walk through:

1) You'll need to buy 5x 2bit grey encoders with same steps/rev or double steps/rev (better the first type).

 

2) Then you have to connect the center pin to ground and the two side pins to two different inputs of the pokeys board.

 

3) In the pokeys' configuration software you'll assign the left and right turn of the selected encoder to two different key combinations (like CTRL+ALT+1 and CTRL+ALT+2). In case you used the twice steps / rev encoders enable the 4X feature. Save the config.

 

4) Finally in the FSUIPC keystroke facility assign the two key combinations to the needed functions.

You're done!

 

To be sure that the keystrokes are working start by using basic keystrokes, like A and B to the turns. Then open the notepad and try rotating the encoder. It should write the chars you assigned. If so, you can now move to more complex key combinations.

 

Some of those encoders needed for the FGC also have a PB in my opinion. FYI I'll plan the FGC PCB with those encoders.  You can find them HERE

 

(Posted by Eric Tomlin on 12-03-09)

Thanks Vince, that sounds easy enough. I have Scott's original FGC with the gray encoders with push buttons already installed- I just needed to know what to do regarding the board and software for the Pokeys. The only one that doesn't require the push function is the ALT rotary. All others require it.

 

I don't quite understand though: "In case you used the twice steps / rev encoders enable the 4X feature"

You mean this depending on what type of encoder, right?

 

(Posted by Vince on 12-03-09)

Encoders are defined for their number of steps per revolution and number of pulses for revolution. The steps are the small clicks you can hear or feel when you rotate the encoder. The pulses are the real signals sent from the encoder in a full turn. So, if you have a 24 steps / 24 pulses encoder , it means that for each click there is a pulse sent to the board. if you have a 24 steps / 12 pulses then for each two clicks one pulse is sent. This last type of encoder has the problem to be slower in sending signals and some "clicks" are just vacant (don't send anything). The 4X function in the pokeys configuration allow an half pulses then steps encoder to act just like a normal 1:1 step/pulse encoder, by simulating the missing pulses.

 

(Posted by Scott Wegner on 12-08-09)

Those encoders work perfect with Open Cockpits inputs cards and I must say, they actually respond better than ALPs on OC cards and I dare say even as good as GoFlight. That said, when I did them on the Open Cockpits cards I simply connected each side to an input and controlled via the SIOC code. I wonder if you can just treat as normal inputs?

 

(Posted by Vince on 12-08-09)

"2Bit Gray type" in my knowledge is the specification of how the encoder sends pulses. In 2Bit Gray Type encoders the sequence sent is 00-10-11-10-11 meaning that just one bit is changed each time a pulse is sent turning the shaft. As far as I know all those encoders work the very same way (even if they have different pulses/rev) and I found out that all the types I had at home (7 different parts) worked the right way with pokeys. I'm not sure but maybe this encoder you have isn't a 2Bit one? this might be the problem but I haven't here different encoder types to test.

 

For general interest here is a list of the encoders that I used successfully with Pokeys55T and eventual issues discovered:

 

Alps EC11EBB24C03: (Dual Encoder) This is a 15 pulses/30 detents. This means that a contact (pulse) is achieved each two steps. This is why you get a step movement on the gauges each two steps rotation in the encoder. You need one and an half full knob rotation to have a full decimal radio rotation. (Since Poscope firmware revision 2.0.7 those are working faster thanks to the 4X function in the Pokeys55T software)

 

Chip Chinese encoders with PB. Those are 30 pulses/30 detents and have a push button too. Act the right way with fast response and a full decimal RMU round in less then 1 full turn. They are cheap though also in build quality.

 

Bourns ECW11-B24-BC0024 and ECW11-B24-BC006: The first is a 24 pulses/24 detents. It acts with a single pulse each step giving smooth resolution. More expensive, about 3$ each. The second is a 6 pulses/rev. Very very slow and buggy, is instead a very first choice for opencockpit cards.

 

Bourns PEC11-4220F-N0012: This is 12 pulses/24 detents. Same behavior as the Alps. Even slower because it has less detents in a full 360 revolution. Price about 1.00$ each from mouser. (Since firmware 2.0.7 it works smoother but look under for a better choice at the same price).

 

Bourns PEC11-4220F-N0024 and 652-PEC11-4225F-S0024: Those are the very same encoder as before but with 24 pulses/rev. The first code is without switch, the second with. This part is available in various shaft size and type. They are working quite well with Pokeys and are really cheap. My very first choice.

 

(Posted by Mark L. on 12-08-09)

Just to reinforce what Vince said, I have the CTS 2bit encoder pn 288V232R161B2 connected to my Pokeys board configured with 4x sampling and it works fine. Make sure to pick which pin is channel A and the other channel B. When wiring, the center pin goes to ground.

 

The following is output from turning the switch Right:abababababababababab

And Left: abababababababab

 

(Posted by Eric Tomlin on 12-09-09)

Okay, testing has been completed on my FGC via Pokeys for the control of CRS, HDG, VSPD, and ALT. The test was a full success! The Pokeys card is simply awesome considering how many rotary encoders can be used on this card for such a great low price. However, we now have 1 more task that I am not quite sure how we can accomplish an important task- toggling between controlling Vertical Speed and Forward Speed via the SPD rotary. We need to have that one rotary encoder toggle between these two functions and I'm not sure how we could get this to work via Pokeys software (yet). It is important to note that between tonight and a few days from now I plan to test the JET45 AAS rotary functions with the Pokeys software as well as Jason's pokeys/Jet45 bridge application. This software will allow the pokeys board to control RMUs, DUs, and the dimming rotaries on the EFIS panels. I'm hoping that we can get the function of toggling what the SPD rotary controls with the bridge application eventually but it will likely only happen after the CDU is completed and a FGC software is created.

 

Thanks to Vince and Jason for helping me get the Pokeys board up and running!

 

(Posted by Eric Tomlin on 01-24-10)

Vince, Mark, Jason and any other Pokeys owners, I finally got my rotary encoders ready to interface and so I plugged in the Pokeys card and although the red LED is coming on, I'm not seeing it as available to connect with the software, nor is it allowing me to upgrade the firmware although the software tells me I need to.

 

Any suggestions? Ive been very careful handling the board to avoid static shock, etc..

 

(Posted by Mark L. on 01-24-10)

Make sure you are not using pin 4. Using pin 4 would cause what you are describing. In the manual it states pin 4 connected to a low prevents the processor from booting. Do not use this pin. Also limited functionality on a few other pins. Read section 12 of the manual for details. It's a PDF so I could not copy and paste it here.

 

Another thought, just in case. There is a procedure to reset the card in the user manual, you may need to do this. I got mine screwed up somehow and had to do this procedure, then all was well.

 

Additionally, did the card installed drivers when you plugged it in? It should have installed quite a lot of interfacing drivers and you should have found in gaming peripherals a Pokeys Joystick interface as well.

 

(Posted by Eric Tomlin on 01-25-10)

I am not connected to the very first one because it appears empty. I have wired into pins 1-10 and then 1 wire into the ground. The physical first slot shows 3.3v so I went to the first pin labeled as '1'. I have 5 encoders which will require 10 inputs. Is is going to mess things up to skip an input?

 

So I removed wires from pins 1-5 and the little green led came on and it 'worked' so I'm wondering now if the issue was in fact pin 4? Seeing as I need 10 inputs for the 5 encoders, I'm guessing I will put encoder:

 

encoder 1 on pins 1/2,

encoder 2 on pins 3/5,

encoder 3 on pins 6/7,

encoder 4 on pins 8/9 and

encoder 5 on pins 10/11

 

What I listed above sound like the way to wire it then?

 

(Posted by Vince on 01-25-10)

You can connect an encoder in any two input pins of the Pokeys, even not consecutive. With 52 full working inputs out of 55 you can still connect 26 of them. Having them consecutive isn't but a way to keep them in order but you are not obliged to follow the strict order.