No1sonuk

Looks like some of the writing is a part number. What are the lights indicating?

Yes, Electronics engineer. I only had a quick look, as I'm away from home until Wednesday, and the diagram has a weird layout. e.g. it looks like the bulbs are in parallel (as they should be for redundancy), but theyre drawn in an odd way. That may so so the diagram would fit the shape tgey have to work with. There are transistors in there, and it would need a proper look (and probably redraw of the diagram) to figure out what's going on. It's also a bit out of focus. Those transistors mean it may not be as simple as changing the bulbs. They also mean a MOSFET might be advisable rather than required. I just cant tell on my phone. Most of the motor drive MOSFET modules are rigged to ground the "output" when they are turned on. It's "simply" a matter of using the "LED" code lines of DCS-BIOS to turn on the appropriate output that connects to the MOSFET input.

Looks like connecting any of the top three wires to ground will turn on the corresponding light when 28V is applied as shown at the bottom. Any "N-channel" MOSFET meant for motors, etc. would do that, and you'd need an Arduino to drive the appropriate MOSFET As for the connector: Unless you can find one, you'll need to source some pins and 3D print a housing, or disassemble it and rebuild the inside.

If you can supply 24V, that should also work. Do you know how it's wired? If it's individual lamps, some sort of MOSFET driver would work.

Spacedesk presents your other device to Windows as though it's another monitor. Helios can then use it as though it's a monitor connected to the host machine.

This might be at least partly what you're after: https://www.spacedesk.net/

Do you see the rectangular plate at the front of the seat platform? Some of the seats have that plate removed and a shaped cushion like the A-10. No idea why, though. None have a central stick.

Airbus pilot seat material images. I took these photos... Large files - sizes shown Dark blue with rule (2.4Mb): Dark Blue Torn (3.1Mb): Light blue (sides) with rule (1.9Mb): Bonus image - Bare seat (partially disassembled) (8.2Mb!):

I took some photos with steel rule which I'll upload when I get home. In the meantime, this appears to be the exact fabric used for Airbus pilot seats: https://www.iwantfabric.com/paris-blue-stripes-upholstery-seating-wool-fabric.html

Do they show up in the Arduino IDE?

We repair them. No airport wandering required.

If it helps, Les, I can probably get you a close-up photo of the fabric on an Airbus pilot seat tomorrow.

The double ActionButton option just worked for me with the P51 gen switch example.

OK. ActionButton won't work then. UNLESS, you rig a second one to turn off using the other contact on a SPDT switch. So maybe this: DcsBios::ActionButton ltdRSwToggleOn("LTD_R_SW", "1", 5); DcsBios::ActionButton ltdRSwToggleOff("LTD_R_SW", "0", 6); // Second contact on same switch. Note different names before parenthesis DcsBios::LED ltdRSw(0x74c8, 0x4000, 4); That trades code simplicity for using extra IO pins. Otherwise, you'll need to do it with polling the switch and sendDcsBiosMessage or the DCS-BIOS/HID hybrid idea mentioned earlier.

The "toggle" part might be what's causing that. Did you try it with "1"?

I think it's FAR easier than you've made it. I just did a test with these two lines: DcsBios::ActionButton gen("GEN", "1", 8); DcsBios::LED genHold(0x5000, 0x0001, 13); Those two lines could run a mag switch... ActionButton only fires the command once, on the falling edge of the switch input. In my example, the switch turns on the P51 generator switch, and the LED responds to the in-game switch position. I triggered the switch and left it in place. The light came on. I then moved the switch in DCS (with the physical switch still on), and it turned off, and stayed off, and the LED went out. Then moving the physical switch to off did nothing. For the mag switch, the hold solenoid could be driven in place of the LED to hold the switch on. Test sketch for P51: #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" /* paste code snippets from the reference documentation here */ DcsBios::ActionButton gen("GEN", "1", 8); // Sends switch position "1" to the "GEN" switch on the pin 8 falling edge DcsBios::LED genHold(0x5000, 0x0001, 13); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } EDIT: This is flawed and I didn't notice - there's no way to turn off the control with the physical switch...

Not 100% sure what you mean by "ethernet shields and a Arduino Due", but I know a Leonardo can take status data from DCS and send "keypresses" in one device: That sends joystick button presses, but it could easily be changed for keypresses.

Have a look here: That's for an Arduino Pro micro or Leonardo to give 3 different button outputs for a single on-off-on switch.

I recently posted code for a 3 position switch to on-on-on, but I can't find it with the phone app.

Did you read the comments? Those aren't on-off-on switches.

Yes. In my post, I mentioned "WIBBLE" was just to make it unique. The label between the function and parenthesis (bleedAirKnobWIBBLE in this case) can be anything you want. That's to make the control in the arduino code unique. The part inside the parenthesis is the critical part for DCS. "BLEED_AIR_KNOB" is the start of the message sent to DCS, and that's the part that can't be changed.

FYI. I submitted code to the Flightpanels guys that would replace the LED function with one where you can add ",false" on the end to invert it. No idea when it'll make it to the full "build", though.

OK... I'm answering the question asked... Those two lines I sent in my last message should give what I thought was asked for: Left and right rotation by the encoder and press to zero...

In the DCS-BIOS Arduino library examples, there's a "one of everything" sketch. If you want to learn how those commands work, you can look in the Arduino library source code. BE CAREFUL not to accidentally edit them, though, in case you screw something up. On my computer, those files are located here: C:\Users\timja\Documents\Arduino\libraries\dcs-bios-arduino-library-0.3.7\src\internal Looking at the LED code in there, it possibly wouldn't take much effort to add an active low type, or a flag that can be set if required. The 2 position switch has that.

Having looked at the Arduino library code, it looks to me like all the switch types are fancy packaging that leads to sendDcsBiosMessage commands. I think whatever comes after the switch type is an arbitrary name to prevent clashes. So try this: DcsBios::RotaryEncoder bleedAirKnob("BLEED_AIR_KNOB", "DEC", "INC", 19, 20); DcsBios::ActionButton bleedAirKnobWIBBLE("BLEED_AIR_KNOB", "0",21); // or whatever pin the encoder switch is Actionbutton only sends the command on the falling edge of the switch (connecting to gnd), not the rising edge. "WIBBLE" is in there because it's pretty much guaranteed you won't have any other function with that in it.