Gremlin77

thank you all, this gives me a lot motivation to go on!

Time to fly Now here come the promised Pics of my baby. All working now, having all instruments, cdu with displaying real cdu data and the switches on the finished panels connected and running. Both mfds displaying right pictures. For external view three monitors. Caution panel is working, all the little gizmos blinking and numbers showing frequencies... love it! Added some green lighting to get a better atmosphere and, cause having no backlight have to use it this way! It feels very good to sit in and blast some tanks. But, as you all as builders know, still a long way to finish this up.

i know this controller. what i dont like with it is that you have maltrix soldering thousands of diodes. for operations using joystick buttons instead of my opencockpit cards i use the arcaze interface of simplesolutions. the advantage is, that it supports keyboard matrix, buttons axis and rotary encoders. it has 40 in-outputs and its cheaper as well. have a look at it, you will love it.

looks promising, hope if you make it for multiple sims you wont get problems with the interfacing. with my a-10 pit i had to do so many "spezial solutions" that it wont run on any other sim than dcs. if you want to stay open for multiple sim, my advice is to put all your buttons and swiches as joystick buttons or keystrokes. this is what all sims support. with my opencockpit cards you can do more special things like displaying digits and so on, but you have to write specialized programs for it. so go on, now you have a new follower....

if you have oc cards and only want to use 7seg look at my post about radios. you can send directly your frequencies, tacan, ils etc. to sioc variables. now, running my little prog i use a table in visual studio to store all the a-10 values and then from there i send them to sioc. it's just the more convinient way. if i can help, let me know

own interfacing software So, back again. Sorry for the long absent time. I decided to write a piece of software which helps me to avoid all the A-10 restarts when you change the export.lua. (And the weird error search.....) So I took Visual Studio Express 2010 (free for private use) and wrote a little prog that hooks in the SIOC-, A-10- and Helios-network streams. Now I have the possibility to create my commands send to A-10 in a convinient way programming it in Visual Studio. (I love it when a Program says you why it doesn't work......and not like the f..... lua) It took me nearly a week to get it working but now, what should I say, I am so happy with it. Also did the whole connections between SIOC and most of my already finished panels. Here's a pic of my Prog running. (sorry for all the german words in it..) Pics of the running panels will follow

hi, have you ever thought about how the extract your mfds to the network pc. first of all, i also had sioc and helios running on a network pc. but then got problems sending the extracted mfd pics over the net. so now my helios displays are running on the a-10 machine and i only use sioc over tcp. i would prefer helios on the network machine, hope you will find a solution for bringing the mfds alive. some kind of program that copies a part of the mainscreen over the net. i didn't find one. hope you do...

amazing! very clean work.

looks nice. looking forward to see pics of the "professional" version

sorry, my fault. you are right. just getdevice(0) for mainpanel. then get_argument_value for 209 to 214 look in clickabledata.lua under --IFF. then you get the right values. mainpanel = getdevice(0) firstwheel = mainpanel:get_argument_value(209) ...

an outstanding pit! great job!

that thing looks awesome! got some dimensions for us?

you just have to use the getdevice funftion to create a device, in your case the iff. with get_argument_value you can get the position of the switches - from these values you can calculate the code ( just add the positions)

You can use any freeware CAD program you want, doesn't matter because you just have to do simple constructions like rectangles, lines, circles etc. . I have an 60W cutting and engraving laser from www.exklusiv-laser.de . They import the lasers from china, so it would be cheaper to order directly from china. I prefered the way over this company to be sure to have guaranty, spare parts and some safety. This company added some fundamental safety controls to the machine. I have already written in this thread before that I could do some front plates if anybody wants some. But nobody was interested so I didn't follow this idea any more. I think packing and transport will be quite expensive and time robbing so I don't know. :smilewink: Just kiddin' Don't think I have the time to build panels for money. And it's my freetime I prefer investing in this pit. If you want one, I can do one for you for free (hope transport is not so expensive)

how I build my panels - The TISL Okay, have a bit freetime so I decided to show up how I build my panels. In the past, I have build some kind of A320 cockpit, this was the time I tried out several building methods. Now, with the A-10 I use my "recently best results" that work fine for me. Here we go. First of all I use a CAD programm to develope the Panel Backplate and the Front. The different colors are for the different worksteps like cutting or engraving. After lesering the two parts (using a two colored plastic for the front (specially for engraving with lasers) and a 5mm transparent acrylic for the back) I glue them together and start installing the switches and encoders. I simply use hot glue (dont know if this is the right english word) to stick them in. Also insert the opencockpit adapters for the 7-segment LEDs. for the A-10 push buttons I found the RAFI 15x15 mm buttons. I buy them without lighting and use two 3 mm leds wich I glue in. (much cheaper than Korry.....) the frontplates of the switches are also lasered out and glued on the push button. Thats all - so building a panel will only cost you some Euros and about 2 to 3 hours of fun (without cabeling) In the past I used an cnc drilling machine to build the panels. That works too, but isn't that comfortable as a laser is. So, now have to do some cabeling....Pictures follow Guys, go on building, it's worth it!

Hi all, has anyone an idea how to realize some kind of startup procedure that puts all ingame switches to the position of the real switches? I have assigned several switches to Arcaze card and use them in helios like joystick buttons. When I start A-10, the in-game positions dont match the real switch positions. I always have to switch the switches to get the matching or I have to adjust the real switches in a kind of checklist before I start A-10 to get them match. So, is there a possibilty in helios to force A-10 to set the ingame-switches in the right position? In my SIOC connected switches it's no problem, because I program the settings of the ingame switches to match the real ones by programming an startup-procedure. Hope, someone can help.

VHF AM Radio So, after hard work and help from Gadrok(thanx again) for the Preset Numbers my VHF AM radio is full operable. I used Opencockpit cards for the 7-segments exporting the values over UDP and for the Dials I used Gray encoders connected to Arcaze board. Works fine for me, but have to redesign a bit, cause the Presets have two digits.......going to change......F....

why i didn't have the same idea, so its right......my english is so bad, damn it

super, works fine. dont know why i had the same idea, cause i export the actuall frequency by getting the dial value..... sometimes i think i am getting old......

okay thank you, i will give it a try. hope it works. will send some pictures on my threat.

hi gadroc, thanx for information. but i just want to extract the channel number. i can change the channel number with my hardware. but i have to get the actual preset channel number for exporting via sioc to the 7segment display. any idea?

Hi, wondering if anybody has an idea on how to export the PRESET Channel of UHF and VHF Radios with the export.lua. Managed to set up the hole radio panel with working switches and rotary encoders, changing and displaying Frequency on 7-segment-LEDs But have no idea about the preset.... Hope someone can help

sorry not bitch but with... in the last sentence. Dr. Freud says hello..... :-)

Hi, I used to have the opencockpit cards. Used them for interfacing with MFS X and this worked quite well because of FSUIPC. But with A-10 I am interfacing now the are a bit "complicated". So, now I just use opencockpit cards for outputs and 7-segment, for input I use the Arcaze card from simplesolutions which behave like normal joystick buttons. So I can simply config the hole stuff in A-10. So more flexibility with oc cards, but much more simple bitch some kind of joystick-adapter. Your decission....

nice build! keep on going!