No1sonuk

https://lilliputdirect.com/lilliput-um80 Looks like purely USB input to me. Though it's specifically THAT model.

If you look in the controls page of DCS, you can see if there are, for example, "volume up" and "volume down" binds. If there are, you can use a rotary encoder on a Leo Bodnar board, or an Arduino that can simulate joystick buttons (e.g. Leonardo and Pro Micro). I'm not sure if the Mega can do that. Other than that. you'll need 10k linear potentiometers feeding an A-D converter in the Arduino, or again, an analogue channel on a Leo Bodnar board. DCS-BIOS will also allow some of that - I HIGHLY recommend the "Flight Panels Fork" over the "Hub" version. Hub hasn't been updated for a while, but Flightpanels is up to date and actively maintained. WRT the Mega - do you need all that I/O? More inputs means more code complexity and greater chance of messing it up. I'd use multiple Nanos and Unos to split up the panels and code to limit any failures that occur. It makes the USB or RS485 connection more complex, but I think that's worth the hassle-saving.

I'd be tempted to build the 210, but make it work like the 164.

Photo link is broken.

Have a word with MFG. They have these as spares, and might have an optional shorter travel. https://mfg-sim.com/en/rudder-spare-parts/18-brake-limiter-set-left-right-graphite.html

You could possibly make a new piece to replace the part that holds the spring end and restricts the pedal movement, then recalibrate in the MFG app.

If you're using an Arduino as a HID, you can program a centre-off switch to send a "virtual" button press when the two inputs are off. And if you're using DCS-BIOS, you can use the "sendDcsBiosMessage" function in a similar way.

OK. Two things. 1) Hub may not have what you're after as it's not currently updated, and hasn't been for a while. The "Flight Panels Fork" may have it. What label comes up when you put the cursor over the switch? Having had a look at the Flight Panels control reference, it might be this: DcsBios::Switch2Pos radGridSelSw("RAD_GRID_SEL_SW", PIN); That's shown as the "Radar Grid Selector Switch", and switches the display between PPI and B-scope modes. I can't check the Hub reference as I don't have the Mirage, but that might help you find it. 2) You could use an Arduino Pro micro or Leonardo with the "joystick" library to create a button box that your PC sees like any other joystick. There are also Leo Bodnar boards and "Zero delay USB interfaces" that could also work like that for you.

I use 10K linear potentiometers

Which DCS BIOS fork are you looking in?

I'm not aware of a 13-way rotary switch.

I tried a normal webcam with filters changed. It didn't work nearly as well as the Delanclip and PS3 Eye camera setup I have now. If you go the webcam route, you have to open it up to remove the IR filter, then fit a visible light filter (e.g. a piece of floppy disk, as mentioned above).

Thanks for that - I've had a few issues myself, and I'll try that setting. Though I should add, it's in the PointTracker input settings on mine, not the Accella filter settings.

I got this (UK source), and it works really well in DCS and Elite: Dangerous using the Opentrack software - https://delanengineering.com/shop/#!/DELANCLiP™®-Gamer-Complete-Kit-Wired/p/43397050/category=68198003 They have different options too. e.g. Wireless head clip: https://delanengineering.com/shop/#!/DELANCLiP™®-Fusion-Complete-Kit-Wireless/p/241172148/category=68238008

They actually come without the spring fitted. Have a look here:

If you use a pot (or multi-position switch), when you start a new session, the control won't be synced until you move it. Then it'll jump to the new position. If you have the option for a rotary encoder, moving it will start from the existing point. The downside is, as you said, resolution steps. There ARE rotary pots that can be depressed, though the only ones I've found so far are push-push (push on, push off) or push-pull (push on, pull off). There must me momentary push versions, but I've not found them yet. Alternatively, you could make your own by using a pot that can be allowed to slide, but not rotate and place it over a tactile switch or other button.

A 3-position switch can be handled in a couple of ways. 1) Use any Arduino with the corresponding DCS-BIOS code line with a SPDT, centre-off switch. e.g. DcsBios::Switch3Pos irSarNeu("IR_SAR_NEU", PIN_A, PIN_B); 2) If there are 3 individual binds in the DCS controls bindings, you can do a more complicated setup using an Arduino Leonardo or Pro micro. In this case, you can read the switch using the 2 inputs, then send "joystick button" presses to the computer depending on the 3 switch positions. NOTE 1: For this to work, the Arduino has to have the 32u4 processor. An Uno or Nano won't work properly, if at all. NOTE 2: A Bodnar board could do this if the switch has only two positions. There's no "centre off" option. Why you would chose one method over the other depends on how the control behaves in-game and how you want to use it or implement it in your physical cockpit. e.g. the Mosquito bomb doors, flaps, and landing gear levers auto reset at the end of their function's travel. The DCS-BIOS lines won't allow a physical switch to be reset, so it holds the lever in-game too. AND, the #2 method can be re-bound to other modules or games.

The Bodnar boards are a good option for input only. They present themselves to the PC as a game controller, so they'll work with any game you can change the controller binds with, AND you can "cross-bind" them within DCS for different modules. If you choose the DCS-BIOS route, which can give you gauge outputs, etc. I highly recommend the "Flight Panels Fork". It may seem to be older than the easier-to-connect "Hub" version, but Hub hasn't been properly updated for years. The Flight Panels fork doesn't have the fancy console for connecting your Arduinos, but it is actively bug-fixed and updated - it already has the early access AH-64 included. https://github.com/DCSFlightpanels IIRC, the Flight Panels fork was developed to make use of the Saitek units, but the basic DCS-BIOS and Arduino library work on their own. THE biggest thing to remember, though, is that you don't have to use just one scheme. Use what's needed for the job. e.g. The Arduino Leonardo can be run as a game controller type input device AND run DCS-BIOS for light, etc. output at the same time - I've tested it.

On the plus side, you'll be concerned the printer's not working because it'll be so quiet.

That's huge! Are you going to fit a second z axis drive to support the weight at the other end of the X axis arm?

Is the address right? The one in my control reference says : DcsBios::LED landingGearHandleLt(0x747e, 0x0800, PIN); Miught be a different version of DCS-BIOS, though, but worth a check.

Is this it?

I usually use an immediate action cold start mission for switch testing, or a takeoff or free flight mission for displays. I run DCS on a SSD, so it starts quite quickly. You could try that, or just create your own empty mission on a simple map to help it load quickly.

Thanks. I wrote the code so it can easily be adapted for DCS-BIOS integration - I just haven't gotten around to it yet. One option I'm also considering is a larger, non-square TFT that will fit in the case. Either landscape with switches for the buttons, or portrait with a touch screen for the buttons. OR, as I'm not planning on building a full size cockpit, I might just leave it small.

WOW! 21 months! Here's the latest. I went with a round TFT. This one is what I could get when I decided to revisit this project, so it's only 1.28". That's too small, even for just the segment ring, but it's a start. The ring segments are made of 2 filled triangles, with the coordinates calculated from the seconds angle on-the-fly. The digit segments are rounded rectangles. The "ETC" is a text string. On a Nano, all this adds up to 56% of program storage space and 28% of dynamic memory for global variables. It's free-running there, using a delay between ticks for testing. Buttons and DCS-BIOS integration next. I have an idea for a real time clock as well. One that would switch over to DCS-BIOS when it receives data. As for the size: I'm revisiting some of the earlier suggestions.