I got to spend an hour with Ralph Robinson of R&R Electronics (at his home) and got my EPIC working with EPIC Center.Now, why can't I set a button switch in action. Do I need to write an EPL program and download it into the EPIC? That's what I think, so I'm preparing to do so.I'm reading the documentation, but if anyone wants to show me a short piece of code that will let me see a switch operate, I'd appreciate it.I don't plan to use any middleware. I just plan to have EPIC send keyboard presses to sim software based on switch positions.Thanks.

I used a gear example project from the R&R webpage and was able to check my switches using EPIC info.Next step, try to send a key press based on a switch movement.

Gee Wizz....... An hour with Ralph!!! How did you do that? If I had an hour with him my sim would be finished!!!! and you don't know how to get a key perss... I just don't get it. and WHY would want to use key press anyway?.....

An hour with Ralph: well I live an hour away and I had an old EPIC with a hardware problem which he helped me fix.As you might be able to tell, I've only had power to my EPIC for 4 days, I think I'm making good progress. I've spent the last year and a half designing and building my F-16 cockpit, integrating a helmet mounted display, and wiring up my first set of panels.As far as key presses: for Falcon4, all I need to do is send key presses based on switch positions. If you got some other ideas, I'm all ears.

Jam, (from James?)first, do read the documentation. It contains a section on how to wire up a button and how to program it. If you don't get it the first time, read it again, it will eventually become clear.Next, look at sample code written by others. I gladly offer mine, but it does not contain keypresses. Then again, once you have your device descriptor written and all your modules defined corretly, sending a keystroke is super easy:The procedure would look like this (as an example for press of the trigger on your joystick):void Joystick.Trigger.On (void) { keyhit (A) }This will produce the letter "a" each time you press the trigger. If you want the "a" to be sent when you release the trigger, the first line should read:void Joystick.Trigger.Off (void) ...Remember, "oystick"and "Trigger"on that joystick have to be defined in your device descriptor. You need to know to which module, scan row and bit that trigger is connected. That shows up in the analog section of EpiCenter. Once thed analog window is open, just press the trigger and check in which box the tick appears.Hans

Thanks Hans:I'm reading every piece of documentation I can find but there's no one place where it's all laid out logically. As I understand how this works, I plan to put together an easy to read document and submit it to R&R to provide to others.I have my switches wired (I actually have 20 panels and 120 switches ready to be installed in my cockpit) and I have their module, row, bit assignments written down (got that form EPIC Info).What I need to know is how and where to write the device decriptors. I thought I had it right, but I keep getting errors on my definebutton statements (see my compile error post on this board). If you don't mind passing me your code with the device descriptors, I would appreciate it. Your code might help me figure out how to complete my Project.Thanks.

Maybe I found my error.In the definebutton statement in previous versions of EPIC, they used a 1 to 3 digit number to denote the button position (0, 29, 174, etc.). In the EPIC USB documentation, it states we should use the format M_,R_,B_ (M1,R3,B4 for example).My question is am I to use the actual "M", "R", and "B" along with the numbers?If not, that would explain why I got errors. I'm at work so I can't test this theory right now.

Jam:again - I would skip the "definebutton" alltogether. Use the names from your device descriptor, as explained in my message above. Even the MRB form looks outdated to me. Device Despriptor - thats the way to go.Give me your email so I can send you my stuff as a reference.Hans

I got the definebutton suggestion from another simmer who thought it would work. It would have, except my EPIC USB keyboard driver didn't install correctly. After having Ralph look over my project (he said it worked on his machine) I reinstalled the EPIC Windows USB driver and everything worked.Thanks for all the help and suggestions.