Vinc_Vega

Yes, you have to declare the pins as output in the setup routine and than just set it High or Low as usual. Regards, Vinc

Thanks for sharing with us Regards, Vinc

You are right! Regards, Vinc

Same here. Flightpanel's version of DcsBios is not sending data for the A-10C II. Socat is running normal, data are shown. In contradiction to that, for the F-16 and Bf-109 all seem okay and data can be received by an Arduino. No idea so far. Regards, Vinc

Same here! And I'd love to see the progress on a 23 simpit. Regards, Vinc

Looks really great! Just PM me if you want to know more details in my sketches Regards, Vinc

Hi Les, first impression from here https://store.arduino.cc/products/arduino-nano-every They say: pin compatible and code will still work. I try to get one or two for experiments. Regards, Vinc

Hi Les, the name of your font is "SEG14" so the line must read as follows u8g2.setFont(SEG14); But even if there are no compiling errors, the font is not displayed. EDIT: Have a look at Olli Kraus's webite (the author of U8g2) how to convert fonts. https://github.com/olikraus/u8g2/issues/1140 He even has an example there of the 14 segment font at the end of the page. Unfortunately the height is 18pt (20 pixels). Regards, Vinc

Using the Search function and scrolling a bit down would have taken you to some of the already existing answers/tutorials https://github.com/DCSFlightpanels/dcs-bios-arduino-library/wiki/Getting-Started There you will find how Socat is used and where it is installed. Regards, Vinc

Hi Les, you are using only half of the display buffer. Regards, Vinc

I already had the idea to mis-use some kind of motor driven linear potentiometer and capacitive input for AT but did not realized it yet. https://www.adafruit.com/product/5466 Regards, Vinc

only seven segment fonts found https://github.com/olikraus/u8g2/wiki/fntgrpu8g#7segments_26x42 Regards, Vinc

You can try to disable the 16bit feature within the u9g2.h file. I did so but had no sucess with the Nano. Regards, Vinc

Hi Les, what processor board are you using? I had similar issues when connecting to an Arduino Nano with the constructor: U8G2_SH1122_256X64_F_4W_HW_SPI That chip does not have enough memory for a 256x64 pixel display. Changin it into a reduced version, like U8G2_SH1122_256X64_2_4W_HW_SPI only brings half of the display to life. Solution is to use an ESP32 board with similar connections like below /* ----- Harware SPI (SCL=18, SDA=23, SS=5) ----- OLED => ESP32 GND -> GND VCC -> 3V3 SCL -> 18 (CLK / SCL / SCLK) SDA -> 23 (MOSI / DIN / SDA) RST -> 22 (RST / RES/ Reset) DC -> 21 (DC) CS -> 5 (CS / SS) */ U8G2_SH1122_256X64_F_4W_HW_SPI u8g2(U8G2_R0, /* cs=*/ 5, /* dc=*/ 21, /* reset=*/ 22); // Enable U8G2_16BIT in u8g2.h with following libraries #include "analogWrite.h" // PWM functionality to be used with the ESP32 chip https://www.arduino.cc/reference/en/libraries/esp32-analogwrite/ #include "DcsBios.h" #include <SPI.h> #include <U8g2lib.h> Regards, Vinc

Solved, Under ->Preferences, Espressif Systems's esp32 Version 1.0.6 in the ->Additional Board Manager has to be used by introducing the following URL: https://dl.espressif.com/dl/package_esp32_index.json Regards, Vinc

Do you mean somethin like that? // first charracter line on CSMP display void onCmsp1Change(char* newValue) { lcd.setCursor(0,0); lcd.print(newValue); } DcsBios::StringBuffer<19> cmsp1Buffer(0x1000, onCmsp1Change); // second charracter line on CSMP display void onCmsp2Change(char* newValue) { lcd.setCursor(0,1); lcd.print(newValue); } DcsBios::StringBuffer<19> cmsp2Buffer(0x1014, onCmsp2Change); Regards, Vinc

Hi Johnny, "Servos.h" compiling error! As I wrote in the sketchbook repository, you have to include the AnalogWrite library for the ESP32 if you want to use it with DcsBios. https://www.arduino.cc/reference/en/libraries/esp32-analogwrite/ #define DCSBIOS_DEFAULT_SERIAL #include "analogWrite.h" //to be used with the ESP32 chip https://www.arduino.cc/reference/en/libraries/esp32-analogwrite/ #include "DcsBios.h" Regards, Vinc

Hi JohnnyChicaco I don't have the display but would start by connecting it to the ESP32's hardware SPI bus. You may read out the SPI in use at the serial monitor by the loading the below code (taken from ->here<-) For me the sketch returns as follows for an 30 and 38 pin ESP32 devboard MOSI: 23 MISO: 19 SCK: 18 SS: 5 No further data for your display available, I therefore used a pic found on ebay to decifer the pins D0 and D1. If that doesn't work you may flip the connections. D0 (CLK / SCLK / SCK) D1 (DIN / MOSI) CS (SS) The pins for RES (RST) and D/C (DC) have to be defined by yourself. Connect GND and VCC as usual. Regards, Vinc

As far as I know, you may use normal code like DcsBios::LED masterCaution(0x1012, 0x0800, A0); Regards, Vinc

Yes, calling them A0 to A15 should do it. Regards, Vinc

Yes, you can use the analoge pins as digital outputs. You cannot use these pins with PWM signals to dim LEDs. As the outputs should have 5V, ensure to use proper resistors before powering LEDs. Regards, Vinc

Good to hear that! Wish you all the best

@byteman59 and ofcourse that one

Thanks! I did a complete de-installation of DCS and DcsBios. Re-installed the openBeta in a combination with minimal installation of the Flightpanel's Fork (only the dcs-bios-master folder) it is working again. Works like a charme, including the live data in Chrome and the pointer calibration tool. Great work guys Now I have to see if something from the latest Arduino library broke my scripting. Regards, Vinc

No Lot2Learn, for the PWM functionality of the ESP32 you may have a look at my sketches. I've been using it to simulate instrument backlighting. Regards, Vinc