whartsell

In FSX speak the -10c isnt any harder to learn than PMDG's NGX or the 777. The hard part is the employment of the AC the manuals do a great job of what you should do but not why. Also much more stressful when people are shooting at you

That is correct any target but currently only counts gun hits (of a specific type). I was going to post the script and sample mission this evening when i got home from work but saw your questions so I thought i would chime in

Dont want to step on this thread too much but I was inspired by Cougars script to make one that is a lot more flexible. I can share it with both of you if you would like. You can create any number of zones,targets, and units to be tracked. Most of the work is done in the ME (no messy triggers and such will need to be defined) then you just update 3 or 4 tables in the script and you are good to go. Currently it only supports aircraft gun types (no helis but that could be easilly changed). The script is also less than 300 lines of code vs 3000. If y'all(couldnt resist, I live in Texas) are interested I can attach the example mission and script

For the most part you shouldn't have any problems except the usb spec calls for up to 500 ma per port so for 7 ports you could theoretically use up to 3.5 amps. That's assuming every device pulled max power at the same time (very unlikely)

First off I just want to say that Im not the creator of EOS I'm an early adopter that has been working with Gadroc (the creator of EOS and Helios) and Flim (VrSimpits) on prototyping and integration of their designs. With regards to EOS vs the Brydling boards there are some very big differences. EOS is designed to work with Helios (this means anything you can do in helios like lua scripting is supported) wheras Brydlings boards are directX input devices only. They do not support outputs,lcds,servos,etc EOS is an open source software/hardware solution for integrating various inputs/outputs to Helios and anything Helios can talk to. EOS is based on the Arduino IDE and their reference hardware. EOS as it sits right now is a set of Arduino libraries that handle all the dirty work of implementing communication protocols, inputs and outputs programming so all you need to do is add the library to your arduino sketch and implement the features you want. EOS will also have reference boards for all the panels in the A-10c. The example you see in the pics in earlier posts is the first board design. Its a Generic Panel board that has the most common features for most of the panels. Some panels like the CDU and some radios and such have special requirements and will have their own reference boards designed. You can also create your own boards or even run it on a normal arduino. Before i got in touch with Gadroc I tested everything on a breadboard with about $10 in parts. I then used the el cheapo radio shack solderable bread boards to make my first EOS boards. (this is actually more expensive than buying the PCBs that will be available in the future, and quicker to build too) EOS also has stepper motors,servos and LCDs on the horizon as well. Being an open source project all designs will be made available to the public for little or no cost. you will be free to use it on any compatible hardware you want. Some components will be available for purchase as well (for examples PCB and any other hard to procure or fabricate pieces). EOS allows boards to be connected to single bus through a bus controller (Arduino leonardo board with a shield for the RS485) to your pc. This means that you will not have a ton of connections to your PC. In my pit Im running 3 EOS busses so I only have 3 USB connections to the pc. This will allot me to run about 36 boards if need be. Sorry if this post is a bit of a ramble but my free time has been limited due to a new baby in the house. When i have time to sit down and get my thoughts together ill write a proper writeup on EOS. I have written a simple introduction to EOS and the link is in my sig

I'm sorry I missed your earlier posts. When I get in front of my PC I'll give a more thorough response to your questions.

Been busy with the little guy for a while so not much news. I have built out the EOS boards and they work very well. Only need to verify the new expansion ports on them work properly and then they should be good to go. Tentatively in the near future I may put in a batch order for pcbs if anybody is interested. I will of course provide a full write up with source code and BOM on how to use them components for the board are about $25 dollars including shipping from digikey. This is enough parts to build a single board. It would be cheaper if you order parts for more boards. The PCBs pricing will also be affected by batch sizes. Currently they are about $15 each min 5 but drop significantly (<$7) as the batch size goes up If you know how to make your own PCBs I can speak with Gadroc about when the files can be released and such In case its not clear anywhere else. The "standard" EOS panel board has 16 digital inputs,16 digital outputs, one dimmer output for panel back-lighting and 4 analog inputs. There is also an "expansion" port that allows some extras on an daughter board...4 pins intended for high power switching (think solenoid switches), and i2c bus (think more inputs/outputs as needed or LCD etc) aprox 12 EOS Panel boards are intended to communicate to Helios via RS485 and an Arduino Leonardo (about $20). You could also go straight to the computer via serial (and a level converter) but you loose the ability to chain the devices together if you need more than 12 boards you just add another Leonardo. (i currently have 3 leonardo hosted EOS busses on my test rig) Things like Servos,steppers support are planned on in the near future ( HELIOS doenst fully implement them for EOS yet)

if/when the time comes for electrics i can help as well. 7 years in the AF as and avionics tech,2 years volunteer restoring WW2 aircraft electrical sys as well also been working with Gadroc and others on EOS for HELIOS

Its easy to predict the flight dynamics of a 152 at 150 kts. It would have to be flying straight down ;) thats also past vne

It is my understanding that once completed EOS will be released as open source so you wont need to pay for the designs

EOS Boards Got some prototype EOS panel boards in. Almost finished with the first one ... then testing and refining the firmware These boards will be pretty inexpensive once available. were talking only a little more than an Arduino. So start practicing your Arduino/Electronics skills now cause they are for Enthusiasts and not a POTS solution

Thanks. I got a backlog of things to post so there will be more soon.

Current State of the Seat Since my old pit is still usable i decided to take my time a bit and start on the Seat first. Im using the VrSimPits AcesII seat and will be enabling the ejection and safety handles. Currently its ready for sanding and painting

Episode II a new beginning :) Its been along time since i have posted in here and alot of things have changed. With all that i have learned along the way i have decided to start a new version of my cockpit. Initially i built my pit using dimebugs plans and really wanted to tackle the issue of integration of the electronics so this pit was more of a platform for me to hack on and learn what works and what doesnt. Here is how it currently looks In the beginning I was using pokeys for all my electronics. It worked great but there was alot of programming involved to get everything working. While working on my software I had been closely following Gadrocs EOS hardware architecture for HELIOS. Now that it has matured I am going to be using that moving forward. Along the Way I also came into contact with Flim of VRSimPits. I was very happy with his stick extension and have made a curved shaft mod available for it. Over the past few months I have become involved in working out the electrics for the VRSimPits designs. My new pit will be based on designs from Flim and electrics powered by Gadroc's HELIOS and EOS. What the new pit will look like some day.... Right now its just a mishmash of components:

I would be interested in one of each

Ill take two

As far as acrylic overlays go a simple and effective way is to just print up the panel on extra thick matte paper and glue them on. Spray paint the edges of the acrylic first and it looks good

Me. I'll give you a list tomorrow

Me. I'll give you a list tomorrow. Almost a full set

I'm interested in the decals as well

I'm interested in handles :)

I don't steppers are fully implemented yet as well as servos. As far as fatherhood goes you are in for a fun ride :)

It's my understanding that EOSServo integration into Helios is incomplete at this time. Next time I talk to Gadroc ill ping him about it.

My free time has been spotty the last few weeks. I am a new dad and it's a bit exhausting. I'll try to make some time in the next few days to give a complete walk through. I currently fly with eos/Helios controlling my electrical,sas,and AAP. So I'll document how it all works.

I would love to get more of your cast knobs when they are available