Hi All,Well it's time for me to jump into the whole EPIC thing, and despite a programming background and a lot of research, it still seems a daunting task. Having read through some recent posts, it is clear that a respectable number of people are having some trouble getting started, some even resorting to selling their EPIC hardware...a real shame IMHO. As I sit here with my USB hardware hooked up, I am contemplating the best way to begin. While some have suggested reading through others' EPL code (which I have started doing), this approach can lead to even more confusion due to the length and variations in the code.It occurs to me that a better way to start is with a simple task and one that almost every cockpit builder has to face...say, the landing gear. Learning to set up the landing gear will teach me how to handle a simple ON/OFF switch that affects an FS2002 variable, as well as how to control LED lights.If anyone wants to continue this post by providing guidance on this topic, I am certain it would go a long way to helping us newbies get started. I will certainly follow up once I successfully complete this initial task, and perhaps continue with the addition of other operations (rotaries, etc).Cary

Hi Cary. I think the most important place to begin is deciding which way you will end up talking to the flight sim no matter which ver. there are several ways to do it and that will decide how you write the EPL code.I have changed my end results several times and found I need to start over each time. I am refering to wether you will use epicmain, epicinfo, FS COMM and such to send and recive epic to FS. after many months, hell after a year or so I have decided to use FS Comm. it makes programing so much better . With FS Comm you talk to FSUIPC direct. And when you get Project Menginta, as you will, it takes off a few layers of software.anyway good luck.www.flightsimulator.atlink to FS Comm.

TVRON,Thanks for the heads-up (exactly what I was hoping for with this thread). I had been assuming EPICInfo, but will check into FS Comm...Cary

Cary,also check www.Epicmapper.com I am using Epicmapper as middleware and I am happy with it. Only the documantation sucks, and when you ask for support you can consider yourself happy if the answer (which comes very fast, sometimes within 10 min.) consists of more than 1 line... But once you get the hang of it the program does it's job very well, stable and fast. About your question - IMHO:1. Step Write your device descriptors. Without it, you have nothing to reference to in your code. If you are interested, i can upload my devices.hpl to guide you. It contains a fair amount of comments (my comments are a bit like a diary, I make them after something bad has happened to me, or if I found a solution to a problem or if some bizarre EPIC concept has suddenly become clear to me...)2. Program your first switchFirst, with to send a simple keysend to your PC (Nobody should underestimate the amount of satisfaction you get from the first successful test, like pressing the trigger on your joystick and seeing the letter "a" appear in an open notepad window!!!)Second, try to program that switch to toggle an offset via EpicInfo, FS Commander or EpicMapper.I'd be happy to go along with such an tutorial-like thread, uploding the corresponding parts of my epl as necessary (thus avoiding the sheer quantity of a full-blown epl file).Regards,Hans

Hello and welcome,First off, If you think there is a problem with your EPic USB, contact RR Electronics and get the latest EPROM version. This fixed my problems and made things quite easy after that.What will you be using your Epic for? I fly (and drive) multiple sims, using my original TM F22 and TQS, both use the Epic mods available, along with other switches of my 'cockpit'. I currently have no output modules running so I have no need for second party software like those mentioned in other replies to your post. It is quite easy to program the Epic for my needs. EpicInfo provides all the info I need.A gear switch is a great way to start and it is the first thing I made. There is nothing like feeling the switch click in place while gear goes 'clunk' :)I tend to think in concepts, so what is needed is to; 1. Wire up a switch or pot- Print the Epic Manual and diagrams you need. Pots need a +5V, Ground and Analog return. Switches need a module row and switch return lead(s). Find the leads you need for this in the Epic wiring diagrams. Note direction of Diodes you wire in for the switches.2. Open EpiCenter, start a new project. Follow directions of the excellent tutorials that are around. Compile, LoadEpic and Unplug (if you are making any changes to a device file).3. Start up EpiCenter, go TOOLS / EpicInfo and under 'button's, you can choose the Module row you wired to and it should make a checkmark appear in the switch return number you wired to.sorry! I have to go to work now. .I will check in later to update more...Cary - smilinicon

Hi All,Thanks for the well-thought out responses. I have taken your advice and started to research the required software that will be necessary.As suggested, I began by updating the EPIC software and EPROM by downloading the soft/firmware from FlightLink. I updated the EPROM from within EpiCenter, and everything seems OK. At a minimum, you must have installed EpiCenter to program the EPIC device and EpicInfo to communicate with FS2002 (FSUIPC). I believe this is all that is required to begin.Beyond this, there is the optional EpicMapper which I understand to be "middleware" between Epicenter and the EPIC device to facilitate EPL programming. In addition, FS Communicator is available, the details of which I don't fully understand, but resides between the EPIC device and FS2002 (FSUIPC).Perhaps someone can enlighten us on these "optional" programs and the benefits of each. I would personally choose not to deal with additional layers of software unless absolutely necessary.Thank you to everyone for your continued input.Cary

Cary,I have only worked with EpicMapper, so I can only comment on this program. What EM actually does is to handle offsets in FS and in Project Magenta programs. Offsets are needed for different reasons:1. to controll FS or PM like you would controll it with keyboard commands. The difference with EpicMapper is that it also works over a network (but FSUIPC does that too)2. to receive data from FS (either frequencies, or the state of LED's)3. to send data to FS (frequencies, values, state of LED's)Example Gear switch: Imagine that you took off, raised the gear with your gear switch and then aborted the flight. You will find yourself back on the runway with the gear down, but your gear switch is in the up position. If you programed your epl to produce the keypress "g" each time this switch goes on or off, you have a problem: Lowering it (to syncronize it with the actual situation) would raise your gear and you do a very stupid crash on the runway.To avoid this, you can use the apropiate offset (0x....) for gear position. Instead of sending the letter "g" you just write the apropiate values to this offset raise or lower the gear, thus avoiding the problem mentioned above.In general: You do need this additional software layer, if not, the only way to communicate between EPIC and FS would be with keypresses. And that severely limits the possiblilities of EPIC.If you are interested in my (commented) EpicMapper config.ini file, let me know.Hans

if my gearswitch is out of sync, I hit the G key once to fix it. I have another method I use also. I just use an if statment to simulate a switch detent that must be pressed first before the gear toggles. Some aircraft gear switches are like this. If I am out of sync, I work the switch without the detent.

Hello Hans,I was wondering if you would send me you EPL file with all of your comments, I'm sure it would be extremely useful.My e-mail address is [email protected] in advanceJulian.

Hi Julian:Done.Hans

Hans,Many thanks - What a gentleman !Julian.

Hans,Sorry for the absence, but work comes first! I think I will break down and incorporate EpicMapper into the mix, as from what I can tell, it should facilitate some of the programming.This weekend I'd like to get to work on wiring up the landing gear switch. I'd like to take you up on your generous offer to send me your device descriptors file (devices.hpl) and epicmapper config.ini file. Any additional suggestions on the landing gear task would also be appreciated...Will report back as soon as I achieve some level of success, no matter how [email protected]

Cary:check your mail.Hans

Hi All,Well, thanks to Hans and Blue Side Up (Ray), I have achieved some success with EPIC! This weekend I wired up an actual B737 landing gear lever and actually got the system to recognize the position of the handle (gear up or gear down). As Hans said earlier, don't underestimate the level of satisfaction from wiring up ypur first switch...pure bliss (my wife still thinks I'm nuts)!!! Thanks guys and I will post the details of my success later to help others and stay true to the purpose of this thread.A couple of questions:1. I want to be sure I am soldering the connections correctly and would appreciate any advice from the experts on the *best* method to physically solder the connections to the boards.2. What's the difference between a "procedure" and a ":xxxxxxx" block of instructions?Thanks Cary

Cary:1.I use distribution boards for all the wiring. At an electronics parts supplier (CONRAD Electronic) I found blank circuit boards that have groups of three holes connected, which I found ideal. I routed the scanrow / leads ribbon cables from the EPIC extension board into connectors on this distribution board. Same for the analogue ribbon cable and 32P-output ribbons. On the same board I installed DB25 connectors (female). All wires from the EPIC ribbon cables are "distributed" to the appropiate DB25 connectors. Each of my panels (or in some cases: groups of panels) have all their contacts (LED's, buttons, analogues) soldered to a DB25 male connector, which plugs into the distribution board. This system makes it easy to change panels and to assemble or disassemble my whole setup. The distribution boards are an enormous amount of work, and soldering has to be done with a lot of care (and testing), but I am satisfied with the result.2.In the later versions of USB EPL a procedure block looks like this:void (void) {...} orvoid (void) {...}In the old days a procedure block looed like this:: {...}If you use EpiCenter V.50 or up you should - for compatability with future versions - use the new form. Anyway, building procedures directly linked to button on or off transitions makes the "definebutton" statements obsolete and thus the code easier to read.All the best,Hans