Jasper2610 Posted May 3, 2011 Posted May 3, 2011 (edited) Concept OUTLINE TouchPal - Touchscreen Cockpit by Dastardly, and Gadrock ------------------------------------------------------------------------------------------------------------------------------------------- 46" LCD 22" Touch Screen X65-F Rudder Pedals Edited July 31, 2011 by Jasper2610 gone generic TehgRa (n-TehgRa-tea)
m0jo Posted May 3, 2011 Posted May 3, 2011 ------------------------------------------------------------------------------------------------------------------------------------------- IO Hardware SPARTAN-6 LX9 MICROBOARD AES-S6MB-LX9-G See ATTACHMENT: AES-S6MB-LX9-G Product Breif.pdf multiple x 16 Channel Mux-Demux CD74HC4067 See ATTACHED: CD74HC4067 Datasheet.pdf ------------------------------------------------------------------------------------------------------------------------------------------- OUTLINE 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, as an alt tab solution, 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. 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. 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. I plan on using a series MUX's from all SimPit switch states on dasie chained PCB's and a common data line, MUX select, and logic high, and clcok from the FPGA. The FPGA will be an integrated deMUX and higher level of code, maybe to talk to Helios. 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 data DCS knows and sent to windows looking like various keyboard key presses (not a constant key press). You should check the PHCC project, instead of using a expensive 90$ FPGA, this I/O solution is using a relatively cheap 10$ PIC18F. Also, most of the hardware design is already done and the whole thing is opensource. Only the clientside software need to be written and this will be simple because the motherboard is using a serial connection to send and receive data from the PC. I will probably write a software to interface the export.lua and the PHCC card this summer. I will use PHCC in my pit in replacement of OpenCockpit's card because the firmware inside those OC card is not opensource and this is causing a bit of problem with custom card.
Succellus Posted May 3, 2011 Posted May 3, 2011 Your realy in love with the Blackshark aren t you ? Dont you think mayyybe you could do a little more generic pit, or do you plan to always stay K50 only ? Just asking. HaF 922, Asus rampage extreme 3 gene, I7 950 with Noctua D14, MSI gtx 460 hawk, G skill 1600 8gb, 1.5 giga samsung HD. Track IR 5, Hall sensed Cougar, Hall sensed TM RCS TM Warthog(2283), TM MFD, Saitek pro combat rudder, Cougar MFD.
Jasper2610 Posted May 4, 2011 Author Posted May 4, 2011 (edited) yeah, I do love choppers. I would be in the Australian army aviation corps hopefully flying hte tiger, shown in my signature. But I'm not medically fit. So I'm an electronic engineer doing a second degree. My SimPit plans are to have a realistic pit for the KA-50 but also to make it so that i can have multiple profiles programed onto the FPGA. So that hopefully when DCS make FA-18 super Hornet I'll make another pit dash and slide out the KA-50 and slide in the FA-18, and use the same micro controller and have a switch to change firmware for the relevant sim. Edited May 4, 2011 by Jasper2610 TehgRa (n-TehgRa-tea)
Jasper2610 Posted May 4, 2011 Author Posted May 4, 2011 Q: How to edit config code for KA-50? Can anyone help me find where to edit the "center view position" and "starting zoom" code is located in DCS KA-50? Once I know the file I should be right with making my desired adjustments, I just don't know where to look. TehgRa (n-TehgRa-tea)
Jasper2610 Posted June 7, 2011 Author Posted June 7, 2011 (edited) Switch Schematic Switch Schematic. (See attachment for clearer detail) I still have the LED and 7-seg-display Schematics to come...... Schematic Prints.pdf Edited July 31, 2011 by Jasper2610 TehgRa (n-TehgRa-tea)
PanelBuilder Posted June 7, 2011 Posted June 7, 2011 Concept 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, lua export 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. the unsynchronised switch displayed so that you can change it. This is an interesting approach to the problem. What I, and I think others, have been doing is basically the opposite: automatically send all physical switch positions to the sim at mission start, and solve the problem that way. Your way will work too, though. Might even be more fun. Cheers, Colin
PanelBuilder Posted June 7, 2011 Posted June 7, 2011 Concept I plan on using a series MUX's from all SimPit switch states on dasie chained PCB's and a common data line, MUX select, and logic high, and clcok from the FPGA. The FPGA will be an integrated deMUX and higher level of code, maybe to talk to Helios. MUX states will be buffered and only data sent to windows when any bit of the latched buffer changes. Good plan. The latched bit will be transcribed to data DCS knows and sent to windows looking like various keyboard key presses (not a constant key press). Not a good plan. DCS only allows you to do so much with keystrokes and button presses. OK for momentary pushbuttons but that's about it. You need to import the switch states with lua. Cheers, Colin
Jasper2610 Posted July 31, 2011 Author Posted July 31, 2011 Generic Pit I have decided to go with a generic pit design using a touch screen Touch Screen: How to do TehgRa (n-TehgRa-tea)
Jasper2610 Posted July 31, 2011 Author Posted July 31, 2011 Prototype Progression TehgRa (n-TehgRa-tea)
Succellus Posted August 1, 2011 Posted August 1, 2011 If you TV solution as you pretend be SURE that the choosen TV has a response i would be radical and says no more than 3ms. But it cannot surpasses 5ms refresh rate at all cost or you ll have ghosts especially with any quick change in the screen. HaF 922, Asus rampage extreme 3 gene, I7 950 with Noctua D14, MSI gtx 460 hawk, G skill 1600 8gb, 1.5 giga samsung HD. Track IR 5, Hall sensed Cougar, Hall sensed TM RCS TM Warthog(2283), TM MFD, Saitek pro combat rudder, Cougar MFD.
Recommended Posts