Jasper2610

NICE, that looks like it's deficiently worth considering, cheers mate. I'm not launching into this super fast so ATM I'm just trying to gather as much information as I can and find a solution that I can handle technically and not to costly. Would love to see your setup you have going atm....

Concept OUTLINE TouchPal - Touchscreen Cockpit by Dastardly, and Gadrock ------------------------------------------------------------------------------------------------------------------------------------------- 46" LCD 22" Touch Screen X65-F Rudder Pedals

Soz bro, I hope what i said didn't sound arrogant. I'll probably need about a dozen MUX's and chain them through out the pit. As I'm planning on using 46" monitors I'm going to use the gauges displayed on them, and fix switch panels around the seat and over the monitor switch display, will also disable head bob. Also I plan on using hte PFGA for other home projects so I don't mind the extra cost for it

This is the board i plan on using: AES-S6MB-LX9-G It has 12 IO pins to control the CLK, MUX select, Logic High out, Data In, and any other stuff like you 7 seg display and LEDs. The MUX chips to get all switch states and a PCB's will be daisey chained to the FPGA IO ports. CD74HC4067 Schematic coming soon

IT's CALLED MULTIPLEXING - each data input uses the same circuit line and active for (1/n) of the CLK frquency for "n" inputs. have another look. I don't need more of them, just a few MUX chips. The FPGA is like a master to interface with the PC, and there will only be ONE data line in as all the switches will be multiplexed with select lines controlled by the FPGA. As for your input/output shift registers can be integrated onto the FPGA with some VHDL code. So controlling a seven segment display with this FPGA is an option too, just add a MUX line out the the display for serial data and enable the output after all bits are loaded onto the 7 seg display bit register. hope you understand, i really should be be doing my uni work and not playing with these toys. I plan on putting a PDF together to show the schematics. Q: Do you know how many unique switch states there are in the DCS KA-50 cockpit? i read it some where but can;t find it agian.

I don't know to much about HELIOS or outputting data from DCS KA-50 but it dose interest me. Ideally I would like a small command prompt window, either as an alt tab solution or use a second monitor input and just change back and forth from DVI to VGA input, to push all switch states out to the micro controller (FPGA) and run a diagnostics to make sure the SimPit switches are identical to KA-50 at mission load. The hardware is the easy part for me, I'm an electronic and computer systems Engineer, and we used VHDL on Xilinx chips more many projects, shift registers, MUX's, ALU's, and CPU's. I also know a bit of C# and C++ but it's not my specialty. So if you have trouble with Integrated Circuit design I'm willing to help. I plan on using a series MUX's from all SimPit switch states on one PCB and serial port with the data line, MUX select, and logic high, and clcok from the FPGA. The FPGA will be an integrated deMUX and higher level of keyboard drivers. MUX states will be buffered and only data sent to windows when any bit of the latched buffer changes. The latched bit will be transcribed to ASCI and sent to windows looking like various keyboard key presses (not a constant key press). But I would love to hear about you helios data output from KA-50 so that i can run a diagnostic switch state check at mission load. What I'm planning is a program to run in the background to DCS. It will run once, only at the start of a new mission loading. Each of the physical switch positions will have a unique bit code. And when the microchip gets the aircraft switch positions from DCS, not sure how yet, the buffer (register) on the microchip for switch positions will compare the data to that of the data pushed from DCS to check what state each switch is in. Now when DCS's pushed data dose NOT match the physical SimPit switch configuration. Say you complete a mission and shutdown the aircraft completely so it is dark, but the next mission you load the communications is on and engines in idle. You alt tab to the background program and it pauses, and names the switch that is not in the correct state, even a image of the cockpit with the unsynchronised switch in a highlighted displayed so that you can change it. The switches are NOT automatic. The background program just helps you synchronise the physical SimPit to what the DCS has loaded for the mission. Once everything is sunchronised, the background program either closes or stays open for the next mission load, after outputting that the system is synchronised.

This is the board i plan on using: AES-S6MB-LX9-G It has 12 IO pins to control the CLK, MUX select, Logic High out, Data In, and any other stuff like you 7 seg display and LEDs. The MUX chips to get all switch states and a PCB's will be daisey chained to the FPGA IO ports. CD74HC4067

Let me explain this a little better, I think you misunderstood me. What I'm planning is a program to run in the background to DCS. It will run once, only at the start of a new mission loading. Each of the physical switch positions will have a unique bit code. And when the microchip gets the aircraft switch positions from DCS, not sure how yet, the buffer (register) on the microchip for switch positions will compare the data to that of the data pushed from DCS to check what state each switch is in. I think you understand the correctly. Now when DCS's push data dose NOT match the physical SimPit switch configuration. Say you complete a mission and shutdown the aircraft completely so it is dark, but the next mission you load the communications is on and engines in idle. You alt tab to the background program and it pauses, and names the switch that is not in the correct state, even a image of the cockpit with the unsynchronised switch in a highlighted displayed so that you can change it. The switches are NOT automatic. The background program just helps you synchronise the physical SimPit to what the DCS has loaded for the mission. Once everything is sunchronised, the background program either closes or stays open for the next mission load, after outputting that the system is synchronised. I never considered making them automatic, I don't even know if a switch like that is possible. But I do like where you took my idea. I imagine if they exist they would be expensive and large, as they would need some kind of mechanical mechanism. But I will do some research as cost analysis. The way i originally planned would also help you member where whats switches are, because I'm nowhere near starting a dark chopper in 30 seconds.

I got no idea what you mean by that, LOL I don't know to much about HELIOS or outputting data from DCS KA-50 but it dose interest me. Ideally I would like a small command prompt window, either as an alt tab solution or use a second monitor input and just change back and forth from DVI to VGA input, to push all switch states out to the micro controller (FPGA) and run a diagnostics to make sure the SimPit switches are identical to KA-50 at mission load. The hardware is the easy part for me, I'm an electronic and computer systems Engineer, and we used VHDL on Xilinx chips more many projects, shift registers, MUX's, ALU's, and CPU's. I also know a bit of C# and C++ but it's not my specialty. So if you have trouble with Integrated Circuit design I'm willing to help. I plan on using a series MUX's from all SimPit switch states on one PCB and serial port with the data line, MUX select, and logic high, and clcok from the FPGA. The FPGA will be an integrated deMUX and higher level of keyboard drivers. MUX states will be buffered and only data sent to windows when any bit of the latched buffer changes. The latched bit will be transcribed to ASCI and sent to windows looking like various keyboard key presses (not a constant key press). But I would love to hear about you helios data output from KA-50 so that i can run a diagnostic switch state check at mission load.

If this don't work can i get you to psudo code (comment) on why you have the resolution values you do and the x,y positions from your monitorsetup lua file.

ok. I'll look at the specs for both again, but I was given the non combat ones for Christmas, everything else is a wish list. I don't think I'll be firing up A10 any time soon but definitely would get F18 if they do it.

AMD Radeon EYEFINITY with 3 27" monitors is emersive and awesome. This photo dosen't give proper justice, i had to tweak a few FOV and zoom settings to make it better. I have 2 x HD6800 cards in crossfire, 2 x monitors in DVI and the third from a display port. You can get adapters that turn one display port into 1,2 or 3 x DVI outputs. http://www.accellcables.com/products/DisplayPort/DisplayPort.htm But in all honesty, why not go 3 x 46" flat-panels? 8P, thats my next upgrade

using an inexpensive microcontroller to interface hardware with DCS http://forums.eagle.ru/showthread.php?t=72338

I'm currently doing something very similar with an Xilinx FPGA. http://forums.eagle.ru/showthread.php?t=73075 In regards to limitations of IO ports, have you considered multiplexing all SimPit switches into the chip. Sure this would require several MUX chips and output selection signal and logic high to each switch, but integrating the deMUX is surely easier then using multiple uC's

@ StageFright >> What is the resolution of EACH of your monitors and their physical position, center, left.....?

I also would love to see ACTIVATE and DEACTIVATE key stroke options

I have read various threads and compiled links into this post for questions regarding a SimPit for the KA-50. The main queries I have are to do with the switch panel interface options available. I applied for Australian Army Aviation Corps to be a Tiger Attack Chopper pilot but was unsuccessful due to medical issues, so I am trying to get as close to the real thing as possible and would greatly value suggestions and ideas from all you SimPit builders out there. ----------------------------------------------------------------------------------------------------------------------- Greetings all, I am only a few months old to this whole simulator business but have already decided that the keyboard controls for switches is not enough. I, like many of you, want the emersion of the simulation. By this I mean building a SimPit. However I have a few question and option to outline for your valued feedback, and hopefully DCS read this which may help if the future Pits of other builders. HOTAS I have opted to go with Saitek for HOTAS, their new X-65F Combat Control System, <1>, and Rudder Peddles, <2>. If you have a more preferred choice, please post it with at least a short reason why you believe it to be better. VISUALS (Multi-Monitor Display) I have plans for 4 x wide screen flat panel TV screens, preferably 16:9 with measurements of approximately 1 meter wide and 0.56 meters high, which is an ~46” LCD. I have chosen this size as from Triggerhappy´s cockpit-drawings, <3>, the front instrument panel is just shy of a meter wide. Now I would arrange the screens using RADEON EYEFINITY to form an expanded desktop giving an aspect ratio of 16:9 left, 16:18 centre, and 16:9 on the right, with the possibility of upgrading to 48:18 aspect ratio. If you’re unsure of how to configure such a system please read the threads on multi-monitor support. SimPit Input Control Option 1: Keyboard Hacking, <4> (Schwinn, 2009). I think this is a great option, as I have done it before with WINAMP and a jukebox addon. And I like that the switches will always have the KA-50 default positions when I load the game each time, no having to worry about flicking all the switches back to their non active state. eg: if you crash and your gear is up, quit, come back later, load, and find your gear switch is set to up but the gear is actually down. However I am interested if DCS have replied to <5> (ruprecht, 2009), as to discrete key mappings for every switch and know position. So that the switch is not such a TOGGLE but rather up is activate and down deactivate. Option 2: ELITE USB. I am unsure about this option, it seems like an expensive macro device that keyboard hacking could easily do. Comments would be great. Option 3: Xilinx FPGA This is the option I think I will go with but it is rather technical and requires knowledge of VHDL programming language. A Xilinx FPGA (Field Programmable Gate Array) , <6>, basically a programmable micro controller. Multiplex all SimPit switches to a logic data line, and implement keyboard drivers to output macro key combinations to Windows and KA-50. With code there is potential to buffer the switch signal and only output a keyboard command, for a short pulse, when the switch changes, so no problem with keyboard hacking holding keys down constantly. However I have been told about switches that will send a short signal only when changed so the key is not being held down. I’m yet to look into this and the cost of switches Vs cost of the Xilinx FPGA and basic switches. Again thoughts are greatly appreciated. References <1> Saitek - X-65F Combat Control System http://www.saitek.com/uk/prod/x65f.html <2> Saitek - Rudder Peddles http://www.saitek.com/uk/prod/pedals.html <3> Triggerhappy´s cockpit-drawings http://home.arcor.de/simpit/F16fighter/Downloads_Download-Site_for_Co/Black_Shark/Cockpit-Drawings_Triggerhappy_/cockpit-drawings_triggerhappy_.html <4> Schwinn, 2009, ED Forums » English » Sim Topics » Home Cockpits » Keyboard hacking http://forums.eagle.ru/showthread.php?t=43244 <5> ruprecht, 2009, ED Forums » English » Sim Topics » Home Cockpits » DCS (KA50/A10C) cockpit builder's wishlist http://forums.eagle.ru/showthread.php?t=44405 <6> Xilinx – FPGA http://www.xilinx.com/products/silicon-devices/fpga/index.htm

FA-18 E Super Hornet

Dose your desktop mesh smoothly with both monitors, or is there clipping of the bottom monitor on the sides? Yes? then change... Shkval = { x =227; y =1280; -- may need to be -ve width = 683; height = 384; } ABRIS = { x =960; y = 1080; -- may need to be -ve width = 683; height = 768; }

These numbers are taken from what you say above. If you need explanation as to why they are so just ask. ---------------------------------------------------------------------------------------------------------- Viewports = { Center = { x = 0; y = 0; width = 1920; --center (main) width height = 1080; -- center (main) hight viewDx = 0; viewDy = 0; aspect = 1.777777778; } } Shkval = { x =0; y =1280; -- may need to be -ve width = 683; height = 384; } ABRIS = { x =683; y = 1080; -- may need to be -ve width = 683; height = 768; }

@ StageFright >> I posted this before if found how to utilize eyefinity properly, so if you have support fo eyefinity read the following. If your able to utilize eyefinity and have it setup so that your desktop is spanned across all you monitors, the tool bar is across all of the your monitors, you don't need to do most of what i have outlined above. With eyefinity setup properly the game will detect the maximum desktop resolution. The only thing necessary to change IF YOUR USING 1 CAMERA is the FOV (option 2 - part 2), I found the poor integration of the side cameras to the center camera annoying, so i prefer 1 camera option. Setup eyefinity to be one desktop across multiple monitors. Put all the settings back to default Use the game option settings to change the resolution and aspect ratio. Pick camera option Try to zoom in game again. -------------------------------------------------------------------------------------- USING NON IDENTICAL MONITORS EDIT: <root>\Config\MonitorSetup\*.Lua If your monitors have different resolutions, you will need to change the camera option file to specify the width of each as it will not simple be 1/3 of your desktop. 2CAMERA.Lua ------------------------ Viewports = { Left = { x = 0; -- horizontal starting point for resolution output of left monitor y = 0; width = screen.width / 3; --width resolution of left monitor height = screen.height; viewDx = -1; viewDy = 0; aspect = screen.aspect / 3; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; --resolution width of center monitor height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 3; }, Right = { x = screen.width * 2 / 3; --Horizontal starting position of right monitors resolution display = horizontal resolution of left and center monitor y = 0; width = screen.width / 3; height = screen.height; viewDx = 1; viewDy = 0; aspect = screen.aspect / 3; } }

Eurocopter Tiger Tiger ARH (Armed Reconnaissance Helicopter) is the version ordered by the Australian Army

Hi, I want to display the Shkval & ABRIS on septate monitors but want it to be as realistic as possible. So I was wondering what the screen dimension of both are. I noted that in one of the training tutorials it says that the ABRIS is 16cm wide. Could someone with the knowledge please let me know what the actual dimension are. Cheers.

Hi, I think your using the 3camera view... Check out this thread. http://forums.eagle.ru/showthread.php?p=1099525#post1099525 And look for option 2 1camera with changed field of view, it look much neater. Let me know if you have any problems.

Catalyst Control Center Presets I'm not to sue about anti aliasing, but in CCC create different profiles under the "presets" tab. Make the required settings for each preset then save them and edit the next "preset"