m0jo

The flare dispenser seem to be missing from some Ka-50 (board #23 and #27). The gunner on the Ka-52 have some weird control

You can already export the elevation data with the ACMI export script. In the file TacviewExportDCS.lua, uncomment the line AcmiData:ExportTerrain(); and launch any mission and wait a few minutes. When the game is finally loaded, you can exit and check the /temp/ directory inside the game main folder. There will be a lot of file named like N45E36.hgt, these file will contain a grid of elevation data in SRTM3 text format. You can reduce the number of point by modifying this python example: Canyon decimation.

Well, Eagle Dynamics have registered the domain f-18c.com a few months ago...

Use a computer power supply if you need a lot of amps on the +5V and +12V rail. For exemple, this power supply can have up to 20A on the +5V rail and 18A on each(2) +12V rail. These switching power supply also only cost about 40$.

Those simulators are tiny compared to the Desdemona:

see also ED's wiki for more information about export.lua

Both coordinate are used in DCS:BS, the lat/long are used in the mission editor and the x/y coordinate are used in game. Both coordinate may not match perfectly inside the game, this might be why you are getting a 1km error.

The new patch also need to add a option to disable the trim on the rudder, this will be useful for people without self-centering pedals and a lot more realistic for this type of input device.

The leo bodnar's card is a normal HID joystick, your old joystick should work. I think the method quoted use Helios and is communicating with DCS by the export.lua script.

You wont be able to dim the LED with a 100k ohm pot. About 1% of the range of the pot will be usable between full intensity and light off.

You can't use a potentiometer to dim LED directly because the luminosity is not linear in relation with the current through the LED. The only way do dim correctly some LED is to use PWM.

Normaly the game is only using float between 0.0 and 1.0. Sioc only support integer, if you want to obtain a usable value for Sioc, multiply the exported value by ~1024 in export.lua.

It seem you have wired each pair of led/resistor in series. You need to put them in parallel

The A-10C is using a similar seat to the F-16, the mesurement are probably somewhere in the ACESII section of viperpits.org

From the datasheet:

SV mapper can be used to send keypress when the key is pressed and/or released. The middle position can be detected in software but I don't think this is possible with SV mapper or Xpadder. Maybe AutoHoyKey could send the corresponding keypress when both outer switch are LOW. One working solution is SIOC with Opencockpit, or PHCC but these are a lot more complicated but they can also control LED, stepper, servo and other usefull thing in a pit.

These are probably Dual Pole, Single Throw (DPST), also marked as ON-OFF These are similar to a Dual Pole Dual throw (DPDT), also know as ON-OFF-ON, the middle position on the switch is not-connected to any outside pin. These are Dual Pole, Dual Throw (DPDT), also know as ON-ON That question is quite unclear, if you have a ON-ON switch, you can wire each side to a different input and these 2 input will be always in opposition, one input will be OFF while the other will be ON but this is quite a wasteful arrangement, this could be done in software to reduce the size of the input board. You can also send 2 different command with a ON-OFF-ON switch, for example, the left connection can be connected to input#1, the middle contact to either Vcc or GND depending of the board and the right connector will be connected to input #2. When the switch is in the middle position, both input will be at the OFF state and when the switch is in either the left or the right position, one of the two input will be at ON while the other will be at OFF. If you are using a Leo Bodar board, you can use this schematic to wire the different buttons in a matrix. You can use some 1N4148 diode to correct possible ghost key. If you don't use them, you will not be able to push more than ~3 button at the same time. If you use a BU0836X, you do not need any diode in the circuit.

The cruise speed of the Ka-50 is around 220 km/h. The autopilot is probably slowing the helicopter to maintain either the nominal cruise power or the maximum continouous power. Check the engine power indicator on the right panel to confirm.

You can use a USB joystick interface like one of Leo Bodnar product if you want to add a few switches and potentiometer. If you want a lot more of switches/potentiometer, you can use OpenCockpits with Oakes export.lua script. Another solution with more capability is the PHCC project but this doesnt have any interface with the DCS series. You can use a 4 position rotary switch with OpenCockpits without synchronisation problem. Digital axes doesnt mean anything, they are either analog input or digital input. Analog axes are normaly used with potentiometer or hall effect sensor. Digital input are used with switches.

Led calculation is quite simple: R_serie = (V_in - V_forward)/I_led P_R = R * (I_led^2) So for a 5 volt supply power supply : R_serie = (5-2.5)/0.025 = 100 ohm or greater P_R = 100 * (0.025^2) = 0.0625 Watt, so a standard 1/4 watt or even a 1/8 resistor will be alright. You can also use the led calculator website if your are unsure of your calculation

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.

The function EKRAN:get_actual_text_frame() should be implemented for every display inside de Ka-50 and the A-10, including for example the PVI-800 7 segments display and the CDU on the A-10. - Correct FFB on the pedal/yaw axis with a FFB wheel or joystick to support force trimming like the cyclic with a MSFFB2. The yaw FFB is somewhat supported on FC2, the pedals are shaking in overspeed situation but with the Ka-50, the FFB wheel is only used/detected as a normal non-FFB axis.

siocconfig.lua : [600] = {SimplePotentiometer, 8, 3},--IT-23 display contrastIn blackshark.ssi: Var 900 Link IOCARD_ENCODER Input 61 Aceleration 2 Type 2 { L0 = v900 // * -1 turning clockwise should be plus v600 = ROTATE 0 256 L0 } Var 600 // False Potentiometer

Use this tutorial to interface those encoder: http://www.lekseecon.nl/howto.html#rotaryencode Change 359 by 256 and replace "var 2" by the value used for SimplePotentiometer.

The SimplePotentiometer code is expecting a value between 0 and 255 to work correctly. This is the default value from a potentiometer connected directly to a OC card. You could maybe use a grey encoder if the SIOC variable is changing between 0 and 255 with the encoder's rotation.