No1sonuk

I initially thought it was like the P-51 ASI that has a non-linear gauge face, but looking at it, and the gauge script, it IS linear: -- Tachometer TachometerGauge = CreateGauge() TachometerGauge.arg_number = 37 TachometerGauge.input = {0.0, 5000.0} TachometerGauge.output = {0.0, 0.5} TachometerGauge.controller = controllers.TachometerGauge This is how the gauge model reacts to the input number. On the Spitfire gauge above, there is only a start and stop, meaning the whole travel is linear. It SHOULD be 0-65535 is the full travel of the gauge. One thing I did see, though - Remove this, and all the other serial lines: Serial.begin(115200); // Starter seriel monitor It can disrupt the USB communications with DCS. If you want to output data while running a game for testing, use an I2C-connected character LCD or other display that doesn't use the USB connection.

Your code is doing exactly what you told it to because you are using the code lines for the BUTTON position, not the light. DcsBios::LED pltGroundOverrideBtn(0x86f4,0x4000, 3); gives you the position of the button, so the light will go on and off when the button is pressed and released. What you need is the ground override INDICATOR: Pilot Ground Override Indicator (green)AH-64D/PLT_GROUND_OVERRIDE_L DcsBios::LED pltGroundOverrideL(AH_64D_PLT_GROUND_OVERRIDE_L_AM, PIN); It's in the "PLT INTERNAL LIGHTS" group. The Master Arm lights are there too...

Someone else tried this about 18 months ago. I don't know why he abandoned it. I had a WiFi-connected ESP32/TFT running a CWP program, so it's VERY useful if it works well.

Shift registers, in this context, are a means of converting parallel data into serial. They take the parallel data in and "shift" it out one bit at a time, or take 1 bit in at a time and shift it to parallel. They usually have a way of linking between devices so you can make a chain for more parallel connections than one device can provide. The PISO variety take Parallel In and give Serial Out. You can use this to expand the number of inputs an Arduino can take OR you can use it to convey a large number of inputs through only a few wires - IIRC, this is how TM grips transfer their 20+ button data to the base using a 6 pin mini DIN connector.

The DCSBIOSBridge mentioned CAN do the job, but many people experience lag when using it. There's currently no dev for it, so it should really only be used for testing if all else fails. Rapti's response is the way to go for normal running.

You can see the hidden digits at the edges of the slot in that image. They'd use all 8s - custom 7s would cost too much.

From the addresses.h file: #define AH_64D_SEAT_POSITION 0x8750, 0x0100, 8 So if you weren't giving it all 3 of those numbers, it won't work.

Did you know this was a thing? I'm also going to look into creating a 2-seat version of the switch function.

Are you using blocking diodes in the matrix?

It's possible that's a legal liability thing.

The old version still works (I use it), but there won't be new modules added. DCS UFC X is a newer pay per module version.

Start a separate thread in this forum and we'll see what we can do.

What's your hardware setup?

It could be electrical noise. Try this: The resistors shown dotted aren't necessary - DCS-BIOS turns on those in the Arduino.

One problem you'll have is that the full rotation of the A-10 HSI is 0-65535, but the common data magnetic is 0-359. It looks like the code you have is designed to work with 0-65535 input. Try changing the value shown below. If that fails, try writing a stepper routine that takes a position number, and send it from a normal DCS-BIOS code block.