SkyJunky

Hey, the next update of my UFC. The first PCB is delivered and looks pretty good. I soldered all the tactile switches and all the SMD parts. The first light test looks good. All switches are already working properly. Next steps coming soon... Cheers

I am currently revising my already completed and fully functional UFC. It is planned to downsize the prototype and make most of the cables disappear. To implement this, I have to modify the OLED displays to reduce the size. I also make printed circuit boards where 80% of the cables disappear. There is still a long way to go but the first big step has been taken. The first two picture shows the "old" prototyp. Cheers

It is an incredible job! Awesome.

Next Panel finished... The knobs are still missing, they still have to be made. Cheers Sky

Also wenn ich das alles so lese, dann schreckt es mich wieder mächtig aber Vaicom Pro zu kaufen. Ich bin auch schon seit ein paar Tagen drauf und dran es mir zu kaufen.

Oh ja, da bin ich auch dafür. Ich würde es auch richtig gut finden, wenn ED die Schnittstelle für die Homepits supporten würde. Es ist toll das Ian mit DCS BIOS so eine gute Grundlage geschaffen hat und das BlackLibrary und andere ihre Zeit opfern, um das weiter zu pflegen, aber es wäre gut wenn da eventuell was von ED kommen würde, um das auch zukunftsträchtig zu halten. Wenn die Community irgend wann das Projekt nicht mehr selbst am Leben hält, wäre es schon irgend wie blöd wenn dann Essig wäre. Ich würde mir wünschen das in naher Zukunft, vor vielen weiteren Modulen, mehr Augenmerk auf Core Feature gelegt werden würde. ATC, dynamische Kampagne, Wetter usw. Die Liste ist da ja doch schon recht lang geworden. Aber ich glaube nicht, das die Spieler in Strömen weglaufen wegen des neuen MS Sim. Ich denke das DCS auf einem guten Weg ist, wenn man die aktuellen Baustellen nicht aus dem Auge verliert.

And the next please.

I have all three, CNC, laser and 3D printer. In my opinion, it depends on the quality that everything should have in the end. Is it a pure VR cockpit or do you need everything illuminated. I use all 3 tools. In my opinion you should have a lot of patience and a lot of your own ideas, this is much more important than these 3 tools.

And the next stepstone to finish my right upper panel. Cheers Sky

Hello, here my final version of the radat altitude gauge. The next step is the hydr. pessure gauge in the upper right panel. Cheers Sky

Hello, here the first test of my Radar Altitude. It is not perfect, but for the first test I think it is good. Sky...

Hey, Ok, as I have already written, you have to tell the servo what to do when. A servo is a motor that uses a potentiometer to determine its position and then move to the desired position. In your sketch you only said which area your servo can drive. But you didn't say when to take which position. DcsBios::ServoOutput voltE (0x752e,2, 544, 2400, [](unsigned int newValue) -> unsigned int { return map(newValue, 0, 43089, 544, 2400); }); You have to map it. In my exemple.: If the DCS value is 0, please go to position 544. If the value is 43089, then go to position 2400. You have to find the right values yourself so that your pointer also shows the correct position. Sky...

Hello, do you need for the servo additional code. You need mapping for the servo. For example the servo has been a range from 544 to 2400. From DCS Bios come a value from 0 to 64.000. You tell the servo, what is the right position, when comes the value 45.000. Sky...

Hey Ian, thanks for your fantastic work. Thanks for your support in solving problems. Too bad we will lose you in the future. I can understand that very well, I feel the same way often enough. Is it possible to give someone rights to help with bugs? I think of BlackLibrary, for example, which has helped me a few times with the F18. I wish you all the best in your new job for the future. Stay healthy and thank you again for everything. Cheers Sky

Nein, letzte Info von ED war 15.04.. Die Info ist aus der vergangen Woche. Ich hab gerade keinen Link zur Hand. Es hieß das sie nicht während des Sale den Release machen wollen und die zusätzliche Zeit nutzen wollen, um noch wichtige Bugfixes vorzunehmen. Gruß Sky

You need both files to use the UFC font. The UFC fonts are in the fonts.c and the fonts are called in the other file. You can also insert the required lines from this files into your files. Sky

Hey everyone, I attach a new version of the UFC font for the Hornet. I fixed a couple of problems. Now everything should work again. If there is still a mistake, please tell me so that I can fix it. You need Hornet2 and Hornet4 for the scratch display and Hornet3 for the option displays. Greetings Sky UFC Font.zip

Hello everyone, i have a problem with the F/A-18C and DCS Bios. I have built an attitude indicator. I have wired everything but the data coming from BIOS is a mystery to me. If I roll to the left, the data output increases from 0 to about 65,000 until I have rolled 180 degrees. The other half of the circle no more data come. So if I roll to the right, the data output stay at 0 and from 181 degrees does the data output jump from 0 to 65,000 and then continue to decrease the further I roll. The pitch is similar. The data increase to 90 degrees and decrease again to 180 degrees. For the rest of the circle, the data output remains zero. So I can not control a servo if the data output simply stops at half. Can someone help me with this? Thx Sky

I‘m using Windows. Encodet is the font by a converter. The font is handmade, converted and then inserted into the U8g2 library. There are 3 different fonts for the UFC. The scratch display already needs 2 different fonts. I make a video showing and explaining everything. But it still takes a little while, I have to finish the project first. It is not yet certain that the construction will stay that way. Sky

Thx guys... My current project and the first test. Sky

Hello, because a few people asked me if I would share my font from the UFC, I have the font here for you to download. You need the U8g2 library for this. If I have a little time left, I'll make a video of how I created the font and how to insert it correctly. Have fun with it... Sky u8g2_fonts.zip

Hey everyone, I built an integrated panel lighting. I made a video about it. It is only in German, but maybe it will still give you ideas and information through the pictures. Have fun... Sky

Moin zusammen, ich habe mal wieder kleinere Probleme mit DCS BIOS. Ich habe im DCS BIOS Hub den Code raus kopiert und in meinen Sketch eingebaut. Ist ja nichts wildes aber ich bekomme eine Fehlermeldung. Der ServoOutput scheint so nicht zu funktionieren. Anbei mal die Meldung: DcsBios::ServoOutput pressureAlt(0x7504,7, 544, 2400); ^ exit status 1 'ServoOutput' in namespace 'DcsBios' does not name a type Gruß Sky [Edit] Hat sich erledigt, habe es zum laufen gebracht.]

Die Kühe fressen das Gras ab. Das Gras muss nicht mehr berechnet werden, also gibt es durch den Kuh DLC 10 FPS mehr. Also schupst nicht so viele Kühe um, das kostet dann FPS. :huh: :pilotfly:

Hey Guys, I ran into a problem with my project with DCS BIOS and Arduino I am currently building the FA-18C UFC and have trouble with the 2 16-segment displays. They both are wired up for multiplexing with the anodes wired up on pin 31-47 and the cathodes on 48 and 49. The encoding for the numbers and letter as well as the wiring have been tested and work just fine. The problem starts when I try to get the displays to display the values, I receive form DCS BIOS. My current suspicion is that the methods that come with DCS BIOS are not called in the correct way or not at all since despite what code I put in them it doesn’t seem to get executed. But since I am new to Arduino and C I can not rule out that I made a mistake in my code. Therefore, I add my sketch below and I would really appreciate if someone with a little more experience could take a look at it and tell me if its my code or if there is a problem with DCS BIOS. As to what my thoughts where regarding the script. I encoded the different segments and binary codes of the numbers and letter the displays have to show. Then initialized the pins and put a routine in the loop that reads out the current digit that should be displayed grabs the binary encoding and sets the right pins active first for the first display than for the second. (currently they would both show the same but it takes only one a additional variable to fix that. In the methods that DCS Bios supplies I tried to get the char that is forwarded form DCS and determine witch one it is than setting a global variable that the loop can use to display the right letter. (I suspect the mistake laying somewhere in how I process the char from DCS but I tried it with if and switch cases and didn’t manage to get either to work so your help would be highly appreciated. #define DCSBIOS_RS485_SLAVE 7 #define TXENABLE_PIN 2 #include <Arduino.h> #include "DcsBios.h" int chnr; const int CH1 = 48; const int CH2 = 49; const int segmente[17] = {31, 32, 33, 34, 35, 36, 37, 38, 39, 41, 42, 43, 44, 45, 46, 47, 0}; const long bitCode[26] = { 19205, //0 18432, //1 25345, //2 26881, //3 26628, //4 10501, //5 11012, //6 18433, //7 27397, //8 26629, //9 19253, //10 18480, //11 25393, //12 26929, //13 26676, //14 10549, //15 11060, //16 18481, //17 27445, //18 26677, //19 50651, //20 10675, //G 51256, //M 435, //C 14739, //S 0,}; void setup() { DcsBios::setup(); pinMode(CH1, OUTPUT); digitalWrite(CH1, HIGH); pinMode(CH2, OUTPUT); digitalWrite(CH2, HIGH); for (int i = 0; i < 16; i++){ pinMode(segmente[i], OUTPUT); digitalWrite(segmente[i], LOW); } } void loop() { DcsBios::loop(); /* for(int i = 0; i < 16; i++) { digitalWrite(segmente[i], HIGH); } */ for (int i = 0; i < 16; i++){ digitalWrite(segmente[i], LOW); } digitalWrite(CH1, LOW); digitalWrite(CH2, HIGH); for (int i = 0;i < 16; i++) { if (bitRead(bitCode[chnr], i) == 1) { digitalWrite(segmente[i], HIGH); } } digitalWrite(CH1, HIGH); digitalWrite(CH2, LOW); for (int i = 0;i < 16; i++) { if (bitRead(bitCode[chnr], i) == 1) { digitalWrite(segmente[i], HIGH); } } } void onufcComm1DisplayChange(char* newValue) { if (newValue[0] == '1') { chnr = 1; } else { if(newValue[0] == '2') { chnr = 2; } else { if(newValue[0] == '3') { chnr = 3; } else { if(newValue[0] == '4') { chnr = 4; } else { if(newValue[0] == '5') { chnr = 5; } else { if(newValue[0] == '6') { chnr = 6; } else { if(newValue[0] == '7') { chnr = 7; } else { if(newValue[0] == '8') { chnr = 8; } else { if(newValue[0] == '9') { chnr = 9; } } } } } } } } } } DcsBios::StringBuffer<2> ufcComm1DisplayBuffer(0x7424, onufcComm1DisplayChange); void onufcComm2DisplayChange(char* newValue) { if (newValue[1] == '1') { chnr = 1; } else { if(newValue[1] == '2') { chnr = 2; } else { if(newValue[1] == '3') { chnr = 3; } else { if(newValue[1] == '4') { chnr = 4; } else { if(newValue[1] == '5') { chnr = 5; } else { if(newValue[1] == '6') { chnr = 6; } else { if(newValue[1] == '7') { chnr = 7; } else { if(newValue[1] == '8') { chnr = 8; } else { if(newValue[1] == '9') { chnr = 9; } } } } } } } } } } DcsBios::StringBuffer<2> ufcComm2DisplayBuffer(0x7426, onufcComm2DisplayChange); Greeting Sky.