No1sonuk

Which version of DCS-BIOS do you use?

As we're sharing "Crap-O-CAD", this is an idea I had a while ago for a mechanical solution. I'd personally use an Arduino and code it, but that's not desirable for some.

That second video brought to mind a design consideration I came across yesterday while planning my own such device to add to my WH Throttle: You should decide where to put your buttons/switches carefully. There's a lot of space under the red buttons in that video that someone might be tempted to use for more buttons. That's OK, BUT those buttons can't be accessed if the throttle levers are forward... So only put switches there that will be used with the throttles back.

Try: DcsBios::LED lightEcm(0x4520, 0x0400, PIN);

If you go the arduino as HID route, i.e. making it appear as a joystick, you need to use one with a 32u4 processor. The Pro Micro and Leonardo are such units. The Leonardo is the same form factor as an Uno, but has the different processor. If you go that route, it's possible to get around some issues that simple "zero delay" boards, like the Bodnar boards, have with some controls in DCS not "turning off" when the button does. With the arduino, you can easily create sequences of button presses with numbers beyond the pins you have. This is particularly useful if you have a centre-off switch. DCS-BIOS can be better for some controls, but it is module-specific. A HID setup can be remapped for different aircraft (or a different sim) more easily.

The Arduino pro micro can behave like a keyboard or joystick, then you could use something like Joy2key to interpret those button presses and run files.

Seen this a few times, but I can't find a specific how-to with code.

I wanted to review my carrier landings. This was originally a bolter...

Use a "virtual button" for the centre position. Read the two inputs in one code block and set the 3 output "buttons" appropriately: Input_A = off, Input_B = off (Centre) gives button 12 = off, button 13 = on, button 14 = off Input_A = on, Input_B = off (Up) gives button 12 = on, button 13 = off, button 14 = off Input_A = off, Input_B = on (Down) gives button 12 = off, button 13 = off, button 14 = on I showed a way to do this here:

How did you do it? I've seen it mentioned a few times, but no actual code given.

Thanks. Link added to my post.

That unit is for 19 inch rack systems. Maybe that's another search term you can use.

Download and install this arduino library in the IDE, then try again: https://github.com/DCSFlightpanels/dcs-bios-arduino-library/releases/tag/0.3.7

Maybe try changing the plugs. I'd likely go for something like this https://www.kenable.co.uk/en/networking/power-distribution-units/rack-mount-pdus/7760-kenable-power-distribution-unit-12-way-c13-iec-19-horizontal-pdu-to-c14-plug-007760-5055383477609.html?gclid=Cj0KCQjwtvqVBhCVARIsAFUxcRsfcw4fcPSOxXbgbaGOT9WOGbQGLBQP-W4ZpOepUrsmR-7if22KCJEaApAGEALw_wcB

The problem is how DCS responds to the "button" inputs. e.g. The A-10C responds to the flap switch on the Warthog throttle in such a way that if one of the two "button" inputs is on, the flaps go all the way up or down, and if both are off, the flaps go to a mid position. But the FC3 F-15 doesn't respond to the centre position. Likewise, when you turn on and off the A-10C APU switch, it turns on and off the APU. I have that switched mapped to the battery switch for the F15. If I turn the switch on, the battery comes on, but turning off does nothing. I turn it on again and the battery goes off. This is why how the aircraft module responds to HID buttons is important for the decision on which type of controller you use.

Not having the F16, I don't know if the 3-way switches will work right as a "joystick". I do know that a lot of those inputs in DCS behave as toggles, so it might not be easy. If you use a Pro Micro or Leonardo in "joystick mode", there IS a way to give them unique identities. I'll track it down later.

I can't see the F-16 controls in DCS as I don't have that module. What I _CAN_ do is give you arduino code for DCS-BIOS: /* Tell DCS-BIOS to use a serial connection and use interrupt-driven communication. The main program will be interrupted to prioritize processing incoming data. This should work on any Arduino that has an ATMega328 controller (Uno, Pro Mini, many others). */ #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" // Change these to the appropriate pin numbers: // LASER ARM Switch, ARM/OFF #define LaserArmPin 2 // MASTER ARM Switch, MASTER ARM/OFF/SIMULATE #define MasterArmPinA 3 #define MasterArmPinB 4 // Autopilot PITCH Switch, ATT HOLD/ A/P OFF/ ALT HOLD #define ApPitchPinA 5 #define ApPitchPinB 6 // Autopilot ROLL Switch, STRG SEL/ATT HOLD/HDG SEL #define ApRollPinA 7 #define ApRollPinB 8 // -------------------- /* paste code snippets from the reference documentation here */ DcsBios::Switch2Pos laserArmSw("LASER_ARM_SW", LaserArmPin); DcsBios::Switch3Pos masterArmSw("MASTER_ARM_SW", MasterArmPinA, MasterArmPinB); DcsBios::Switch3Pos apPitchSw("AP_PITCH_SW", ApPitchPinA, ApPitchPinB); DcsBios::Switch3Pos apRollSw("AP_ROLL_SW", ApRollPinA, ApRollPinB); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } That should work in most Arduinos with DCS-BIOS running in DCS.

The Leonardo doesn't NEED DCS-BIOS if you only want it to behave like a joystick. You can just use the Joystick library. I only mentioned DCS-BIOS because you can use it if you want the controls DCS-BIOS offers, and/or the info DCS-BIOS exports.

Your first problem is trying Hub. That isn't currently actively maintained. Try the FlightPanels fork: https://github.com/DCSFlightpanels

I'd have thought the easier way would be to use the Arduino Joystick library and code it. Then you can use DCS-BIOS as well to get feedback such as lights, etc.

He said it was a Leonardo, which does have the 32u4 processor with USB.

I'm having the same issues as others reported: 1- With the throttle at 100% (Warthog left lever forward), the message is still saying set throttle at 100%. 2- Seriously excess roll at low collective levels and various other times. 3- Can't make it slow and sink without collective down, pulling back and gaining a bit of altitude before it sinks rapidly.

The whole point of microcontrollers is distributed processing. You're SUPPOSED to put more of them in, closer to their I/O location. Not only does it reduce the I/O pin count, it also reduces the complexity of the code in each device.

It depends on the coil current and how many you're going to have running at once. Arduino regulators don't have massive amounts of current capacity. Plus remember that inductive loads like relays need "flyback diodes" to prevent damaging the driver electronics with a back-EMF pulse when they turn off.

I tried ths a while ago when you asked, but your email host rejected 3 attempts, and you didn't respond when I tried to tell you.