flx54

UPDATE: BIG SUCCESS !!! I managed to get Display 1 of the UFC to show correctly on the 4 digit 14-segment display using this code. (Nothing special for (FSF)Jan (THX A LOT !!!) but i guess but thought i´d share with you) // include Adafruit LED Backpack library #include <Wire.h> #include <Adafruit_GFX.h> #include "Adafruit_LEDBackpack.h" // include DCS-BIOS Arduino library #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" // display instance Adafruit_AlphaNum4 alpha4 = Adafruit_AlphaNum4(); void onufcOptionDisplay1Change(char* newValue) { alpha4.writeDigitAscii(0, newValue[0]); alpha4.writeDigitAscii(1, newValue[1]); alpha4.writeDigitAscii(2, newValue[2]); alpha4.writeDigitAscii(3, newValue[3]); alpha4.writeDisplay(); } DcsBios::StringBuffer<4> ufcOptionDisplay1Buffer(0x7432, onufcOptionDisplay1Change); void setup() { // initialize display alpha4.begin(0x70); // write something to the display // so you see something before data is received alpha4.writeDigitAscii(0, 'A'); alpha4.writeDigitAscii(1, 'B'); alpha4.writeDigitAscii(2, 'C'); alpha4.writeDigitAscii(3, 'D'); alpha4.writeDisplay(); DcsBios::setup(); } void loop() { DcsBios::loop(); } For Connection i used this reference: https://pinout.xyz/pinout/four_letter_phat Pin A4 is used for DATA Pin A5 is used for CLOCK Now i dont know whether the colon in front of the symbols needs a fifth digit or could be adressed separately?!

OK, i think i messed up. Trying to clean up the libraries even after uninstalling the IDE. Cant include dcs-bios.h as it is already installed somewhere else. I need to check for a clean uninstall before continuing i guess. Whats the best option to include the library for DCS BIOS? Add the zip or place the uncompressed folder into the library folder of the IDE?

Hi Ian, thanks for your input and useful hints. I already found "display1" in the hornet section with which i want to start testing. I guess there is not much more for me to do, than spending more time with it and understanding the logic. I think, that this is going to work well as winter nights are very long... :D

I am at the same stage. Copy and Paste. Not much more for me to do, as i am not experienced in coding or whatsoever. I2C is a must as far as i see, because of the simple connection. Dont want to code every pin/segment of the display myself. The PCB size does not matter in my opinion as you could 1st: modify the 3d STL file to fit your PCB or (easier) wire the LED pins to the PCB (detach PCB from LEDs) and place the PCB somwhere else... BTW: the 0,54" LEDs are too large anyway. Looking for green/yellow 0,39" I mean this sort or similar: https://store.arduino.cc/10-jumper-wires-150mm-male

It´s actually not sooo dificult. Soldering is. I am not too talented in soldering and it therefore took me quite some time with some very cheap equipment. Now i will try to add the appropriate lines from DCS-BIOS in the right place. Will see how long it takes me to get this right...

Cool. Didnt know this thread. Will have a look onto it. Many thanks! Currently investigating how to get these "snippets" from DCS BIOS to work on my project...

Thought i´d share with you. ;)

Wonderful, this is how it should be. Winter is coming, and I will be experimenting at home. Cool! And I will give this one a shot. See how far I get and which 14-segment LEDs I can solder to it. it´s been made for 2 sets of 2 digits, probably its possible to connect more than that?!: https://www.adafruit.com/product/1910 Thank you for your inputs and many thanks to Ian for DCS BIOS! :thumbup:

THX for that. I will try to do that. What fits DCS BIOS better? Common Anode or Cathode? Remembering, that Mobiflight and another civil sim were only compatible with one sort of...;)

Exactly my point. The standard HT16K33 backpack comes also as a kit with too high displays. But can I "simply" attach smaller ones to this board? Pin layout should be the same I guess. best regards

I got my UFC now printed by a friend and investigating hardware (cheaper) options here in Europe. AFAIK a 14-segment LED will do fine. I plan to use 10mm digit height, 4 up to 8 digit tubes. Of course they are from well known Chinese sources. Problem is, that they don't supply the backpack/driver board to interface it i2c wise, which would be way too much wiring/soldering. Any ideas which 14-segment displays I could use with ease? I saw the 4 digit Adafruit solution but the digits seem too large for the UFC... Have a great Weekend! flx54

Wish i could test it by myself, but i still dont get it running. Looks like it is not exporting. Can someone with the Android UFC working please post his/hers export.lua file? Thanks!

From the readme and what I followed: Ok, this is important to know, Helios do not export the viewports, is DCS who do that. Some DCS modules are ready to export some of his viewport, but not all of them. That's the reason we need to change some .luas to make that module ready to export the viewports. In the F18 case, and at this date ( 07/30/2018 ), only the 2 DDIs are ready to export. The AMPCD, IFEI, RWR and UFC are not, so we need to overwrite those .luas with other ones ready to export viewport. Usually, in my profile packages you got everything you need to do that operation in a folder called monitor configuration. So... - Check if you installed the files in the correct place. I recomend to you use JSGME or OVGME to do the job, because in every DCS update those files are rewriten again - Then edit the MonitorSetup file to adjust the viewports to your monitor configuration. (2_monitors-FA18C.lua ) - In DCS options, put your max resolution ( this is the total of your monitor resolutions in horizontal and vertical, for example two monitors 1920x1080 placed in horizontal layout, the total resolution is 3840x1080 ) - In DCS options, uncheck full screen option - In DCS options, select the monitorsetup file to use (the one your just edited) So in the Zeen FA18 package update 2 there is a folder called MonitorConfiguration->Mods->aircraft->FA-18C-Cockpit->Scripts and there you find the IFEI,TEWS and UFC files. ;)

Same here. Need to check the lua file again but IFEI disappeared as well... :/ OK, guess i found the solution: From the Hornet package, you need to substitute the scripts again. These are: IFEI_init.lua, RWR_ALR67_init.lua and UFC_init.lua. (Obviously overwritten by the update...) Tried it with IFEI right now and works as it should.

Hi, as i am also interested in building an UFC on my own i am wondering, what is the correct choice for segmnt LEDs? Are these 14(16)segemnt LEDs used in the real Hornet or is it more like a matrix LED style (like we see in the Sim) Anyone knows? THX?

Got it. Thanks!

Good Luck with your new PC and many thanks for your outstanding piece of software! :thumbup:

Hi Solo, as i also did start using the arduino, i just wanted to adress your post. I dont see the picture. I only see a black square in your post. Whats wrong in here? (Using chrome)

Well, i had time to start my helios setup as described in the 50+ pages guide. Unfortunately Win10 does not match well (touch)monitor setup instructions as before. So that was a bit challenging. Also i wanted to ask, is there a difference regarding Helios in (in all tutorials mentioned outdated) DCS 10C and DCS open beta? For simplicity, i changed resolution of the 2k monitor to 1920x1080.(to match the touchscreen) I am stuck at around page 40 So i decided to replicate everything with the A10C instead of trying to work on the F18C. Unfortunately the "Loz SM v2.1.rar" profile file is not available anymore. So, because of my lacking knowledge, i am again stuck. :helpsmilie: Isnt there a fully functional A10C profile around for 2 monitors? (adapted to the actual DCS Version ;) ) Would really appreciate just in order to eliminate one or other error produced by myself... Thank you! EDIT: Just worked with this tutorial and started to understand a lot concerning the monitor setup. Worth having a look for guys like me! https://www.digitalcombatsimulator.com/en/files/214771/ Now i even got it working with the F/A-18C . At this time modifying viewports but looking very very good!

Alright. A very good post to my problem. Thanks for the info. Will have a closer look on the FCS. I am used to trim for speed and not for acceleration forces. ;)

I am having a hard time to get the plane stabilized as well. I know, that in real aircraft, plenty of things happen "aerodynamicallywise" when you extend flaps. Its a combination of lift and drag which changes. The Power curve (Lift/drag or Thrust required/drag) changes. Every aircraft is different and usually built in a stable way. At least civil aircraft are. Military jets, so i do believe, can be a lot different. Just tried some level flight and config changes. Not too easy to handle at all. I have the feeling, that the hornet is a bit unstable even at level flight. To check that i made very very small inputs on the roll axis and noticed, that it will not come back to wings level by its own. Cant say if that is a true hornet behaviuor, but from my understanding, a stable aircraft should return to wings level. More or less. But never increase bank angle once the stick is untouched. Interesting to know, what a real hornet pilot would comment on this...

THX Snacko, will go through it!

+1 here I am Using an 2k as main Monitor and just got a 22" Ilyama touch monitor especially for Helios. I got the profile for F18 but i only see the Main Panel on the 22" without any "interaction" and the main DCS view on my large 32" 2k monitor. (Instruction where to put the profile files was googled, as i didnt find it in Capt. Zeens instructions ) I went through the installation guide, substituted the export.lua file into the right place but no success. Anyone here with a "Helios Guide for Dummies"? I believe, it is an outstanding piece of software if i get it to work right and will donate as soon as i get it working as i expect it to do... :thumbup: Many thanks!

OK, it looks like my Scripts folder has an issue with read/write permissions. Cant remove the write protection. Need to google how to do it properly in Win10

The only checkbox i see is the one beneath "installed games" and there i marked "DCS.openbeta" does it immediately run well for you? Did you make any changes to your ports etc?