Vinc_Vega

Thumps up! That should be a real hardware job. Good luck, please keep us informed. Regards, Vinc

Best experience I did with 10k linear potentiometers in DCS-Bios. Regards, Vinc

Thanks for reactivating that helpful topic. Regards, Vinc

Breakers are at least manually functional by push-pull with the mouse and the Circuit Breaker Panel is available within DCS-BIOS Control reference. That is reasonable enough to use switches to simulate the CBs. I think that tripping could be evaluated by the failure conditions in the mission editor but never checked that out. Nevertheless, if so, tripping could be done by magnetically activated switches. But I don't think it is worth to do so. The LED solution seems to be a good idea Regards, Vinc

If you want to make mock up breakers, here you can download some drawings. https://amironic.co.il/products/circuit-breakers/aircraft-circuit-breakers/3sb-simulator-series/ Else google for military standard MS26574 or MS25244. Regards, Vinc

You are right, I didn't see the resistor for the Max7219 was questioned. I'm with you by choosing the 10k. Regards, Vinc

If you power a LED by 5Volts, resistors between 220 and 330 Ohm are sufficient (not k-Ohms). Regards, Vinc

Another possibility is to unlock the lever in case of a mechanical failure. Regards, Vinc

You are right, suffix letter "K" stands for "locked in center and (one) extreme position". See page 10 of the datasheet https://docs.rs-online.com/c7a1/0900766b816f1916.pdf Regards, Vinc

Hi Les, physically you only need 3 pins per wheel as the signal has only 3 bit (0 to 7 dec). The second wheel for Mode 1 only needs 2 pins (2 bit, 0 to 3 dec). As that makes 17 pins in total plus the pins for all the 3 position switches, a Nano is not suitable. For my wooden mockup of the IFF panel I use a Mega 2650 Pro, and I think that's the best way to go. Here are code snippets for the IFF panel thumb wheels // BCD decoded IFF Mode Thumb Wheels // Mode-1 Wheel 1 const byte iffMode1Wheel1Pins[3] = {A14, 32, 34}; // three bit (0 - 7) DcsBios::SwitchMultiPosBCD iffMode1Wheel1("IFF_MODE1_WHEEL1", iffMode1Wheel1Pins, 3); // Mode-1 Wheel 2 const byte iffMode1Wheel2Pins[2] = {A15, 33}; // only two bit (0 - 3) DcsBios::SwitchMultiPosBCD iffMode1Wheel2("IFF_MODE1_WHEEL2", iffMode1Wheel2Pins, 2); // Mode-3A Wheel 1 const byte iffMode3aWheel1Pins[3] = {36, 38, 40}; DcsBios::SwitchMultiPosBCD iffMode3aWheel1("IFF_MODE3A_WHEEL1", iffMode3aWheel1Pins, 3); // Mode-3A Wheel 2 const byte iffMode3aWheel2Pins[3] = {37, 39, 41}; DcsBios::SwitchMultiPosBCD iffMode3aWheel2("IFF_MODE3A_WHEEL2", iffMode3aWheel2Pins, 3); // Mode-3A Wheel 3 const byte iffMode3aWheel3Pins[3] = {42, 44, 46}; DcsBios::SwitchMultiPosBCD iffMode3aWheel3("IFF_MODE3A_WHEEL3", iffMode3aWheel3Pins, 3); // Mode-3A Wheel 4 const byte iffMode3aWheel4Pins[3] = {43, 45, 47}; DcsBios::SwitchMultiPosBCD iffMode3aWheel4("IFF_MODE3A_WHEEL4", iffMode3aWheel4Pins, 3); Regards, Vinc

I use those switches from RS-Online by "TE Connectivity" and "RS Pro". Here are some measurements: https://docs.rs-online.com/2161/0900766b81587616.pdf Regards, Vinc

I think that he means, removing the seven segment LEDs from the PCB (desolder) and replacing them with the same size other color segments. Not changing the LEDs itselfs. Regards, Vinc

Hi Les, a while ago there was a post here, introducing BCD switches as a class in the dcs-bios library to replicate the thumb wheels of the IFF panel. Look here for FSFIan's reply: https://forums.eagle.ru/topic/160387-dcs-bios-v055-iff-panel-thumb-wheel-help Regards, Vinc

Ahhh, as I don't have the F-16 module I didn't know that the flow values are of the "analogue" type that has to be converted (mapped). Fortunately now everything seems to work Regards, Vinc

Caused by your "screen()" function, your display only prints the 100th digits, if any. Try this within the curved brackets: lcd.setCursor(0,0); lcd.print("Fuel: "); lcd.setCursor(6,0); lcd.print(Fueltotalizer10k); lcd.setCursor(7,0); lcd.print(Fueltotalizer1k); lcd.setCursor(8,0); lcd.print(Fueltotalizer100); lcd.setCursor(9,0); lcd.print("00"); lcd.display(); // maybe the display has to be refreshed, otherwise delete that statement Regards, Vinc

Your display is of the I2C type. That means, the four wires are C (clock or SCL), D (data or SDA), VCC (supply voltage) and GND (ground). SDA and SCL are to be connected to the Arduino's I2C bus. For the Uno and Nano these are pins A4 and A5. I'm afraid you have to read more about the used libraries, as most people here seem to use another chip (Max7219) and therefore different libraries. Regards, Vinc

It looks like all displays are of the I2C type. Unfortunately they all have the same address. So either you use a multiplexer between the arduino and the displays or you manage to change the address for each display. Regards, Vinc

Are you able to send a simple text message to your display or is the question strictly DCS related? Would you please post the code that you have so far? Regards, Vinc

I don't have that module and can't read the files on my mobile (now), but it looks like you are exporting to the wrong monitor. Regards, Vinc

Here is another working sketch for the Warthog: The Airspeed Indication. Instead of using the stepper and drum solution I want to use an OLED for the Airspeed Dial. I took parts of Middlefart’s code for the altimeter and developed horizontal flipping bitmaps. Beware of, that the OLED has to be connected by the SPI interface for speed reasons. Using an I2C OLED makes the display blurry during rapid changes. Unfortunately that display is very dark. I don't know if it's driver related or I blow up a display's capacitor. Have a look at the clip, that's an 0.96 OLED, 128x32 pixel, SSD1306 SPI display Regards, Vinc AirSpeed_indicator_40x32_SPI_a.ino and the bitmaps bitmaps_40.h

This more complex digital clock I want to share has been coded on a 3.5 inch TFT and was intended to run at the 1.28 inch color display, that fortunately has been in the mail today. I've found out, that the driver and the Arduino_GFX_library are not working at an UNO but at the NANO. Therefore the code for that display (GC9A01 chip) is included just quick & dirty, TEST-mode can be activated to see the pointer running. Resolution should be 240x240 pixel at the minimum, colors can be adjusted if necessary. The gauge outline is hidden if "hide_border" is set to TRUE. Digits and fonts are taken from this website: http://oleddisplay.squix.ch/#/home As I'm not a programmer, it's far away from beeing perfect and the sketch still needs to be rewritten and improved for more performance and details. But in principle it's already working! See below clips for your consideration. The sketch from the clip at the bottom is also "still work in progress" and will be finally postet if "ready". Regards, Vinc 1.28_LCD_NANO_clock02b.ino DSEG7_Classic_Mini_Bold_36.h Monospaced_plain_28.h Digital Clock Test Mode Work in progress ...

I'm sharing the shetches for the digital clock under the other topic. Feel free to use them and/or post improvements. Thanks in advance. Regards, Vinc Simple digital clock version: A more complex version can be found here:

Here is a working sketch for a simple digital clock in the Warthog's cockpit. Written for a 1.3 inch I2C OLED, resolution is 128x64 pixels and using Adafruit's GFX library. See below for a short clip. Regards, Vinc

These are CAD images. The real picture looks like a Thrustmaster piece but at a verry high price So it's better to keep your fingers away from that dealer. Regards, Vinc

If touches can be programmed as a kind of dedicated arduino inputs, I could imagine that commands may be send to DCS-Bios. But I haven't done so yet. Regards, Vinc