JCook

Beautiful simpit there Boltz. Very nice work!

Thanks for the update.

Thanks Anton. For daisy chaining is there a "clean" way to tie all these wires together - like some type of block? Without knowing better what I would do is strip off a 1/2 inch on each wire, wind them together, solder the bundle and them wrap it in electrical tape. But that's kind of ugly and since this is new to me I thought maybe there is a preferred method. Got any pictures of what it should look like? Also - use solid wire or stranded?

Thanks guys for the good information. Is there a standard gauge wire we should use for the DCS BIOS - Arduino builds? Looking for a gauge recommendation that can be used with all connections, toggle switches, rotaries, LEDs, servos, etc. Another Question - What is the best way to wire up the ground (GND) connections for a panel? For example the A10's Electric panel has six toggle switches so there will be six GNDs that come from the switches. These need to be "tied" together - what is the best way of doing this so they can all go to the same GND connection on the Arduino. Even though there are several GND sockets on the Arduino I am assuming one GND can be used for all. Thanks

I'm planning on a stick extension for a full cockpit so a longer extension will be my choice. I was watching the install video from Sahaj (http://warthog-extensions-by-sahaj.com/my-product/) and noticed he set the offset angle of his joystick by rotating it slightly to the left before tightening the locking ring. This makes sense because between the base connection and the joystick connection there is now the extension tube and a flexible cable. This cable between the two connections would allow enough flexibility for the joystick to be rotated for the offset. A simple solution. Am I correct in my understanding of this? Can an owner of the Sahaj extension verify my assumption on this? Thanks.

The Arduino digital and analog sockets are setup for easy configuration changes - pushing in or pulling out a wire. Since we're using the Arduino in a more permanent way (panel connectivity) is there a better or preferred way to connect the wires to the sockets and hold them in place?

Is the serial port identified in the Arduino IDE used for any Arduino I connect? In other words if I have multiple Arduinos of various models they are all programmed (uploading sketch) one at a time from the IDE. So does the serial port remain the same?

Thanks for the update. RS-485 it is then. I'll plan around your progress. Much thanks for your ground breaking work. I connected my Arduino UNO up to DCS BIOS the other day and had the Master Caution example working within minutes and I also managed to connect up the battery switch. If I can do this then anyone can. I am looking forward to learning more about electronics as I connect up my cockpit with DCS BIOS. - this is really cool stuff.

Thanks Boltz. As I understand it, right now the way to connect an Arduino (and its panel) to DCS-BIOS is via a USB connection. This could require a good number of USB connections - in addition to the regular USB ports required for the HOTAS, pedals, MFDs, etc. For the other options being explored Ethernet, I2C and RS-485. What is going to be the best solution - or what do I need to consider to determine the best solution. Thanks

Ok - if I understand you then ON-ON and ON-OFF are functionally the same to DCS-BIOS and Arduino as long as they are wired the same. And my question really is about using ON-ON functionally as ON-OFF. The ON-OFF switch has one pole and ground, and each are wired. The ON-ON has two poles and ground and you only wire one of the poles and ground, when used in ON-OFF functionality. Do I have that right?

Does it make a difference to DCS BIOS / Arduino if an ON-OFF switch is used as opposed to an ON-ON switch configuration?

You're off to an impressive start. Can you tell us the model # of the CDU switches you are using and where you ordered them from? Thanks

Thanks. I'll give that a try.

I currently have the original pre-DCS World version of the A10C. What is the best way for me to upgrade to the DCS World version of the A10C? Also, when I build a new PC for running DCS World - how do I transfer the DCS modules (A10C) to the new PC? Thanks

Okay. Thanks DM. I'll keep watching. Using a non-DZUS solution can work as well.

Great to hear the sides have the strength to enter and exit the simpit like in the real aircraft. DM - can you expand upon what you wrote about the side consoles and attaching panels. I had been leaning toward using DZUS rails. Is that not an option? Thanks for this great work.

Looks good. Can't wait to see it completed. Looking forward to seeing the plans. Do you have an estimate on the hours it took to get to 90%. I don't see any ribs - wondering how strong are the sides. Strong enough to enter egress over the top? Excellent work guys - much thanks.

Ky - thanks for the close up pictures of the those footer support frames. I have been trying to design these things in CAD but didn't have enough detail until I saw your pictures. That is a tricky area of the ACES II - lots of stuff going on it that corner and its usually covered by the plates - so a big thank you for the detail. If you have any other pictures of the detail connections of these footer pieces please post. Is that bottom front corner joined together with a spot weld?

Check the first post in this thread. I've added a pdf and drawing showing the CDU and UFC dimensions Shep used to make the circuit boards. We still need some more buyers before the order can be placed.

Thanks for posting those pictures. With the cover plates removed it is easier to see the construction of the seat's angled parts.

Y2kiah - do you have an overhead canopy frame for your design? also is your rails.7z available in a WinZip file format?

MacFevre - I'll check with Shep and see if there are some dimensions for the boards available.

Not from Shep - he's just building the interfaces. There are many examples of the CDU and UFC in the DCS builder forum - so you can find all the dimensions and techniques to build the 'button boxes'. There may be a few people here that would build and sell them. I'll be building my own.

Yes - probably Gadroc's Helios software has all of the functionality defined. One of the images in the first post shows the A10 configuration page in Shep's software. I'll try to get some additional pictures - of course you can also just download his software: http://psfalcon.blogspot.com.es/

A10 pit builders I'm starting a purchase list for some A10 interface boards from PSCockpits. You can read about JShepard's interface system here: http://psfalcon.blogspot.com.es/ and see additional interfaces and prices in his ViperPits postings here: http://www.viperpits.org/smf/index.php?topic=9235.0 He designed a CDU and UFC interface specifically for our A10 builds and has additional boards to interface LEDs, aircores, 7 segment displays and more. It looks like he has a system to meet many of a cockpit vuilders needs. These are fully assembled and tested boards. A "Main Board" (60€) is also needed to drive the CDU and UFC boards. Shep needs 10 orders per board to make his A10 production run. I believe we will also need the main interface board (60€) to interface with the CDU and UFC. I will check with him on that. Who is with me? CDU interface 90€ 1. JCook 2. grayson 3. jimbo 4. 5. 6. 7. 8. 9. 10. UFC interface 60€ 1. JCook 2. grayson 3. jimbo 4. 5. 6. 7. 8. 9. 10. QuickGuideV1.pdf