Rump0l3

Amen to that. After attempting to build one of these PCBs using a MAX7219 I gave up, because at best each LED is only going to be illuminated 16.7% of the time (i.e. 1/6th, assuming that you configure the board to use six of the available eight digits and configure the scan limit accordingly when you initialise the chip) and it was just too dim. I ended up redesigning the board to use three TCL59282 chips (see photo). Using a separate power supply to drive the LEDs, each "light" on the panel consists of three surface-mount LEDs connected in series. This gives more even illumination, and also means that if anything it's too bright, but it's much easier to make it dimmer in software than to deal with hardware which isn't bright enough. I also had to write my own Arduino code to drive the panel, but it wasn't as hard as I was expecting (having a DSO which can decode SPI helped). Also, don't worry too much about having already ordered five of these PCBs. It's a learning curve and mistakes are inevitable. Sometimes they'll be salvageable by cutting traces on the PCB and/or running bodge wires, sometimes they won't be. It took me three revisions of the PCB for my caution light panel before I was happy with the result. If you decide you want to go down the TCL59282 route, PM me and I can give you some pointers?

When you're buying components from random online suppliers, with listing descriptions that aren't in fluent English if they're in English at all, and it can take a month or more for what you've ordered to arrive (and you might discover what you've ordered doesn't work, you've wasted your money and you're back to square one), there's a lot to be said for using components which are known to work. Especially given the protracted delays experienced by other posters in this thread, I'd have zero compunctions about using the same screens/boards which CubeSim is using and doing the rest myself.

If I've understood your question correctly, I think the tryToSendDcsBiosMessage function is what you're looking for, e.g. to depress the UHF radio test button: DcsBios::tryToSendDcsBiosMessage("UHF_TEST", "1");

That looks awesome - what is the redraw rate of the screen like?

I've been building some custom PCBs for my A-10 cockpit, and because the minimum quantity that I can order of each is 5, I have plenty of spares and I've been toying with the idea of selling some as a side hustle to help others who are building a cockpit. If there's enough interest I might even sell more of them. Are there any fellow A-10 cockpit builders in Australia who'd be up for beta testing some of these PCBs? Because they're prototypes I'd be selling them for a nominal amount over the BOM cost. So far I've got the Caution Light Panel (well-polished, has already gone through multiple revisions, solder an Arduino Nano on the back for a USB interface or connect a separate Arduino via SPI, powered by external 12-36V source (via on-board buck converter), driven by 3x TCL59282 chips with three LEDs per "light" so 100% duty cycle and providing very bright, even illumination), some Arduino shields which do high-side PWM dimming of a 24V power supply for panel backlighting and cockpit illumination, and I'm almost finished with the ARC-164 UHF radio (just waiting for latest PCBs to arrive from China). If you're interested, please drop me a line? Australians only at this stage, overseas shipping is too dodgy at the moment because the 'rona.

Bugger. I did try searching, but I think I was using "caution" as one of the keywords, which isn't mentioned in the other post

The Signal Lts BRT/DIM switch on the Lighting Control Panel doesn't appear to be working. Changing its position doesn't cause a noticeable change in the intensity of the lights on the Caution Light Panel (the manual on page 161 says it should), and according to DCS-BIOS its value is stuck on 65535. Tested on OpenBeta version 2.5.6.61527. Happens in any mission, any map. Hopefully that means you don't need a track file...

Serial #: 04586 (bought it circa 2010) Location: Melbourne, Australia