New to Arduino and DCS Bios. Looking for Help Please

[Kenpilot]

I don't understand what you mean. Am I supposed to copy and paste that boxed command in to the export lua? Where do I find the export lua in the game files and where in the lua do I paste it?

[Stefan1208]

Hallo zusammen, 

Ich hoffe Ihr könnt mir helfen. 

Da das Arduino Board ziemlich Neuland für mich ist hoffe ich auf eure Hilfe. 

Ich besitze seit kurzem das Arduino Board Mega. 

Da ich momentan in mein Keller ein Huey Homecockpit baue und nach einer Lösung suche wie ich z. B das Nav comm Feq. Auf ein 7 Segment display wiedergebe, habe ich mich für das Board entschieden. 

Nun also folgende Schritte habe ich gemacht. 

- Arduino software Installiert 

- Gidhut die zip Datei download 

DCS-bios-arduino library-0.2.11

DCS-Bios 0.10.0

- Arduino Bibliothek eingebunden

-DCS bios Hub installiert 

- in Gespeicherte Spiele Export. Lua den Code eingefügt und abgespeichert

-Das 7 segment display max 7219 an das Arduino mega angeschlossen 

-Code in der Arduino software eingefügt überprüft und hochgeladen aufs Board.

-vorher natürlich usb Comm zugewiesen und das Board ausgewählt 

- dcs bios gestartet und im Browser geöffnet, usb angewählt

-DCS World gestartet trainings Mission 

.... Das Display ist aber dunkel und zeigt mir nichts an bei der freq. Änderung. 

Was mache ich falsch oder habe ich etwas vergessen? 

Ich habe mal eine Beispieldatei im Arduino ausprobiert was ohne Probleme funktioniert. 

Ich habe mich zum größten Teil an diese Beschreibung gehalten. 

https://www.cruzdesanandres.com/foro/viewtopic.php?f=10&t=3453

Vielleicht mache ich auch einfach einen Denkfehler ich weiß es nicht und hoffe auf eure Hilfe oder einen Tipp wie ich es zum laufen bringe. 

 

Vielen Dank schon einmal 

Code Arduino:

#define DCSBIOS_IRQ_SERIAL

#include <LedControl.h>

#include <DcsBios.h>

 

LedControl lc = LedControl (22,26,24,1);

 

// Huey VHF Nav Freq Funktion

void onVhfnavFreqChange (char * newValue) {

lc.setChar (0,7, '-', false);

lc.setChar (0,6, newValue [0], false);

lc.setChar (0,5, newValue [1], false);

lc.setChar (0,4, newValue [2], false);

lc.setChar (0,3, newValue [3], false);

lc.setChar (0,2, newValue [4], false);

lc.setChar (0,1, newValue [5], false);

lc.setChar (0,0, '-', false);

 

}

DcsBios :: StringBuffer <6> vhfnavFreqBuffer (0x14f0, onVhfnavFreqChange);

 

void setup () {

DcsBios :: setup ();

 

//INITIALIZATION lc.shutdown (0, false); // schalte die Anzeige ein

lc.setIntensity (0,8); // setze die Helligkeit

lc.clearDisplay (0); // Anzeige löschen

 

// Benutzerdefinierter Bootcode vor Verbindung

lc.setChar (0,7, '-', false);

lc.setChar (0,6, '-', false);

lc.setChar (0,5, 'E', false);

lc.setChar (0,4, '5', false);

lc.setChar (0,3, 'A', false);

lc.setChar (0,2, '-', false);

lc.setChar (0,1, '-', false);

 

 

}

 

void loop () {

DcsBios :: loop ();

 

}

 

 

 

Update:

Ich glaube ich kann den Fehler etwas eingrenzen. 

Ich bekomme keine Verbindung zwischen DCS und DCS Bios hub.... 

Habe mal Fotos hochgeladen. 

Anhand einer Beschreibung soll sich ein Skript Ordner in DCS Bios sein.... Ich habe da aber leider keinen Ordner oder habe ich das wohlmöglich falsch verstanden? 

http://www.vielfrass-engineering.de/index.php?option=com_content&view=article&id=192:installation-dcs-bios&Itemid=248

 

Edited May 12, 2021 by Stefan1208

[crash test pilot]

@Kenpilot: You find the export.lua in user/"insert your username here"/saved games/DCS/scripts/. Check if the line is already there, else paste it at the top. Next is to check if your dcs-bios connects to dcs: Does the button "virtual cockpit" on the dashboard page of dcs-bios hub go green after you start dcs? If not, do you have the "vitual cockpit autostart" option on the dcs connection page of dcs-bios hub checked? Third: do you use an external power sorce for the uno? Even the smallest servo (9g) can draw up to 700 mA - USB only delivers 500 mA and the uno needs some of that, too. Use a 7 to 12 v/1 to 2 A external power supply plugged to your uno.

 

@Stefan1208: Dein screenshot zeigt den richtigen Ordner. Du hast die Dateiendungen ausgeblendet. "Export" ist die Datei export.lua, diese mit einem Editor (auf keinen Fall Word!!! Empfehlung: notepad++, notepad geht auch) öffnen und nachschauen, ob die entsprechende Zeile für den Export von Daten vorhanden ist.  Ansonsten wie bei kenpilot: Ist auf der DCS-Connection Seit im dcs-bios hub der haken bei "Virtual Cockpit Autostart" gesetzt?

[Kenpilot]

2 minutes ago, crash test pilot said:

@Kenpilot: You find the export.lua in user/"insert your username here"/saved games/DCS/scripts/. Check if the line is already there, else paste it at the top. Next is to check if your dcs-bios connects to dcs: Does the button "virtual cockpit" on the dashboard page of dcs-bios hub go green after you start dcs? If not, do you have the "vitual cockpit autostart" option on the dcs connection page of dcs-bios hub checked? Third: do you use an external power sorce for the uno? Even the smallest servo (9g) can draw up to 700 mA - USB only delivers 500 mA and the uno needs some of that, too. Use a 7 to 12 v/1 to 2 A external power supply plugged to your uno.

 

@Stefan1208: Dein screenshot zeigt den richtigen Ordner. Du hast die Dateiendungen ausgeblendet. "Export" ist die Datei export.lua, diese mit einem Editor (auf keinen Fall Word!!! Empfehlung: notepad++, notepad geht auch) öffnen und nachschauen, ob die entsprechende Zeile für den Export von Daten vorhanden ist.  Ansonsten wie bei kenpilot: Ist auf der DCS-Connection Seit im dcs-bios hub der haken bei "Virtual Cockpit Autostart" gesetzt?

Awesome, thanks Crash Test Pilot, I'll look in to all of your suggestions!

[Stefan1208]

Hello
Thanks for your answer
In the export. Lua I inserted the code dofile (lfs.writedir () .. [[Scripts \ DCS-BIOS \ BIOS.lua]]) and saved it using an editor.
In the dcs bios hub I clicked on virtual cockpit but it still shows me that there is no connection to dcs. Would you maybe have some screenshots of yourself like you did that?
I would be very grateful

null

 

null

 

[crash test pilot]

@stefan1208: Sorry, I use the Flightpanels fork of DCS-BIOS, so I cannot show you a succesful connection of the hub version. But as far as I remember from using it, your screenshot looks good (Virtuelles Cockpit ist grün = OK!). Have you tried something simple like a switch or a LED to see if it works in your cockpit? The Max7219 modules can be a real pain in the **s sometimes... But dont give up!

[No1sonuk]

I seem to remember, you have to put the servo.h include BEFORE the DCSBIOS.h include.

 

I think some of the libraries only work properly if they go in before DCSBios.

[Kenpilot]

I

8 hours ago, crash test pilot said:

@Kenpilot: You find the export.lua in user/"insert your username here"/saved games/DCS/scripts/. Check if the line is already there, else paste it at the top. Next is to check if your dcs-bios connects to dcs: Does the button "virtual cockpit" on the dashboard page of dcs-bios hub go green after you start dcs? If not, do you have the "vitual cockpit autostart" option on the dcs connection page of dcs-bios hub checked? Third: do you use an external power sorce for the uno? Even the smallest servo (9g) can draw up to 700 mA - USB only delivers 500 mA and the uno needs some of that, too. Use a 7 to 12 v/1 to 2 A external power supply plugged to your uno.

 

@Stefan1208: Dein screenshot zeigt den richtigen Ordner. Du hast die Dateiendungen ausgeblendet. "Export" ist die Datei export.lua, diese mit einem Editor (auf keinen Fall Word!!! Empfehlung: notepad++, notepad geht auch) öffnen und nachschauen, ob die entsprechende Zeile für den Export von Daten vorhanden ist.  Ansonsten wie bei kenpilot: Ist auf der DCS-Connection Seit im dcs-bios hub der haken bei "Virtual Cockpit Autostart" gesetzt?

I verified the line is in the export.lua. I started DCS and went in to DCS BIOS and verified the Virtual Cockpit is highlighted (and autostart is selected. I not only have the UNO connected via USB, but I also added a 9V 1.5a power supply to it as well. The flap position indicator is still not working. I verified what No1sonuk mentioned as well, that the servo.h is before the dscbios line in the sketch. Any other ideas as to why this is not working??? This is getting beyond frustrating at this point.  Just to be sure the sketch is correct, this is what I have uploaded:

 

/*
  Tell DCS-BIOS to use a serial connection and use interrupt-driven
  communication. The main program will be interrupted to prioritize
  processing incoming data.

  This should work on any Arduino that has an ATMega328 controller
  (Uno, Pro Mini, many others).
*/
#define DCSBIOS_IRQ_SERIAL

#include "Servo.h"
#include "DcsBios.h"

DcsBios::ServoOutput flapPos(0x10a0,9, 2400, 1472);

void setup() {
  DcsBios::setup();
}

void loop() {
  DcsBios::loop();
}

[Kenpilot]

I got it working. I tested another servo and it was working so I just tried to rotate the gearing on the servo in the flap position indicator and it started working. Guessing it was stuck or something. Now I just need to change the numbers in the command line so the Flap position arrow matches the flap settings. Thanks for all of the help guys!! I'm sure I'll be needing some more help when I try to write the sketches for the gear handle and gear lights, etc, but I'm going to play around with them first to see if I can figure it out now without bothering you guys. Thanks again!!

 

[Kenpilot]

Ok spoke to soon. I'm having a hard time dialing in the position numbers to put in the sketch line:

 

DcsBios::ServoOutput flapPos(0x10a0,10, 1330, 1790);

 

With 1300 and 1790, The Flap setting is showing 0 when flaps are selected 0, whether I'm raising or lowering them, it always shows 0, so that's good. But when I select flaps down to 10 degrees, it shows 9 degrees, and then flaps down to 20, it shows 30 degrees. And then when I raise them back up to 20 degrees, it shows 12 degrees and then back up to 0 shows 0. I've played around with a bunch of different numbers but I can't figure out how to match the numbers to the flap setting selected. Any help would be greatly appreciated! 

[Stefan1208]

I was now able to narrow down the troubleshooting.

When I start DCS Bios Hub and DCS World and sit in the Huey, I open the connect-serial-port.cmd
With the port specification in my case 6 this error message comes ..... Anyone an idea?
DCS Bios Hub and Arduino as well as Device Manager show the Comm Port 6

null

 

[crash test pilot]

@stefan1208: You are mixing  the hub version and the non-hub version. "connect-serial-port.cmd" is part of the non-hub version and the com-port gets blocked by the hub. You have to decide which version you want to use.

 

@kenpilot: Wow, thats new. At least you have 3 distinguishable pointer settings....

Edited May 13, 2021 by crash test pilot

[Kenpilot]

17 minutes ago, crash test pilot said:

@stefan1208: You are mixing  the hub version and the non-hub version. "connect-serial-port.cmd" is part of the non-hub version and the com-port gets blocked by the hub. You have to decide which version you want to use.

 

@kenpilot: Wow, thats new. At least you have 3 distinguishable pointer settings....

 

So does that mean you're not sure how to fix it so that the indicator matches the indicator and flap settings in DCS? lol 

[Stefan1208]

@crash test pilot

sry i tried all possibilities ...
I am now a step further

I've just programmed a button to test whether I really have a connection to DCS World.
With "connect-serial-port.cmd" and Dcs Bios Hub the button works in the game.
But it still doesn't work with the 7 segment display where my Latain is slowly coming to an end.
the display works wonderfully when I put a test code on the board.

Either it is really as tricky as you said or something is wrong with the code.
I've tried it for the umpteenth time with other plugs, other digital plug connections, but it doesn't work.
But I thank you in any case for the help I have received from you so far.

.... achso and sry for my english

[Stefan1208]

@all
I just got it right by a really stupid accident
In another forum she mentioned that these displays are very vulnerable if you put them in the wrong way.
since my display didn't show anything but was dark, I added an example code to test whether the display works.
it ran flawlessly and I noticed something in the code that was missing and out of sheer desperation I simply copied it in and lo and behold it works ...

lc.shutdown (0, false);

This code was missing.

void setup () {
DcsBios :: setup ();

// put your setup code here, to run once:
// MAX7219 INITIALIZATION
lc.shutdown (0, false); // turn on the display
lc.setIntensity (0.8); // set the brightness
lc.clearDisplay (0); // clear the display

// custom boot code before connection
lc.setChar (0,7, '-', false);
lc.setChar (0,6, '-', false);
lc.setChar (0.5, 'E', false);
lc.setChar (0.4, '5', false);
lc.setChar (0,3, 'A', false);
lc.setChar (0,2, '-', false);
lc.setChar (0,1, '-', false);


}

void loop () {
// put your main code here, to run repeatedly:
DcsBios :: loop ();
}

thank you anyway for your help

null

 

 

 

 

 

[Stefan1208]

but now I have another question ...

I got the first 7 segment display working.
now I'm standing on the hose and want to connect a 2 and 3 display to other pins

so the next code should then LedControl lc = LedControl (9,7,8,1); move on.
how do I continue the code for a function UH-1H VHF Comm ???

this is the code for Huey VHF Nav Freq

#define DCSBIOS_IRQ_SERIAL
#include <LedControl.h>
#include <DcsBios.h>
 
LedControl lc = LedControl (12,11,10,1);

 
// Huey VHF Nav Freq function
void onVhfnavFreqChange (char * newValue) {
lc.setChar (0,7, '-', false);
lc.setChar (0.6, newValue [0], false);
lc.setChar (0.5, newValue [1], false);
lc.setChar (0,4, newValue [2], false);
lc.setChar (0,3, newValue [3], false);
lc.setChar (0,2, newValue [4], false);
lc.setChar (0,1, newValue [5], false);
lc.setChar (0,0, '-', false);
 
}
DcsBios :: StringBuffer <6> vhfnavFreqBuffer (0x14f0, onVhfnavFreqChange);
 
void setup () {
DcsBios :: setup ();
 
// INITIALIZATION lc.shutdown (0, false); // turn on the display
lc.shutdown (0, false);
lc.setIntensity (0.8); // set the brightness
lc.clearDisplay (0); // delete ad
 
// User-defined boot code before connection
lc.setChar (0,7, '-', false);
lc.setChar (0,6, '-', false);
lc.setChar (0.5, 'E', false);
lc.setChar (0,4, '5', false);
lc.setChar (0,3, 'A', false);
lc.setChar (0,2, '-', false);
lc.setChar (0,1, '-', false);
 
}


void loop () {
DcsBios :: loop ();
 
}

[crash test pilot]

Hi Stefan! You can daisy-chain the max7219 modules. connect the first module to the arduino, the second module to the first and so on. If you have a closer look at the modules, it has input connectors om one side and output connectors on the other side. Connect D-out on the first module to D-in on the second module. load and clock likewise, better not use vcc and ground that way but connect the to the arrduino direct because else the first display stays bright, the second module will be darker, the third willl rarely light up and the fourth may even not start up. You can chain up to eight modules. In the line LedControl lc = LedControl(11, 9, 10, 2);  you have three numbers for the pins, the fourth number is for the amount of max7219 modules.

Here is an example scetch for testing three modules:

 

//We always have to include the library
#include "LedControl.h"

/*
  Now we need a LedControl to work with.
 ***** These pin numbers will probably not work with your hardware *****
  pin 11 is connected to the DataIn
  pin 9 is connected to the CLK
  pin 10 is connected to LOAD
  We have two MAX72XX.
*/
LedControl lc = LedControl(11, 9, 10, 2);

/* we always wait a bit between updates of the display */
unsigned long delaytime = 250;

void setup() {
  /*
    The MAX72XX is in power-saving mode on startup,
    we have to do a wakeup call
  */
  lc.shutdown(0, false);
  lc.shutdown(1, false);
 
  /* Set the brightness to a medium values */
  lc.setIntensity(0, 8);
  lc.setIntensity(1, 8);

  /* and clear the display */
  lc.clearDisplay(0);
  lc.clearDisplay(1);

}

/*
  This method will display the characters for the
  word "Arduino" one after the other on digit 0.
*/
void writeArduinoOn7Segment() {
  lc.setChar(0, 0, 'a', false);
  delay(delaytime);
  lc.setRow(0, 0, 0x05);
  delay(delaytime);
  lc.setChar(0, 0, 'd', false);
  delay(delaytime);
  lc.setRow(0, 0, 0x1c);
  delay(delaytime);
  lc.setRow(0, 0, B00010000);
  delay(delaytime);
  lc.setRow(0, 0, 0x15);
  delay(delaytime);
  lc.setRow(0, 0, 0x1D);
  delay(delaytime);
  lc.clearDisplay(0);
  delay(delaytime);

    lc.setChar(1, 0, 'a', false);
  delay(delaytime);
  lc.setRow(1, 0, 0x05);
  delay(delaytime);
  lc.setChar(1, 0, 'd', false);
  delay(delaytime);
  lc.setRow(1, 0, 0x1c);
  delay(delaytime);
  lc.setRow(1, 0, B00010000);
  delay(delaytime);
  lc.setRow(1, 0, 0x15);
  delay(delaytime);
  lc.setRow(1, 0, 0x1D);
  delay(delaytime);
  lc.clearDisplay(1);
  delay(delaytime);
}

/*
  This method will scroll all the hexa-decimal
  numbers and letters on the display. You will need at least
  four 7-Segment digits. otherwise it won't really look that good.
*/
void scrollDigits() {
  for (int i = 0; i < 13; i++) {
    lc.setDigit(0, 7, i, false);
    lc.setDigit(0, 6, i + 1, false);
    lc.setDigit(0, 5, i + 2, false);
    lc.setDigit(0, 4, i + 3, false);
    lc.setDigit(0, 3, i + 4, false);
    lc.setDigit(0, 2, i + 6, false);
    lc.setDigit(0, 1, i + 7, false);
    lc.setDigit(0, 0, 1, true);
    lc.setDigit(1, 7, i, false);
    lc.setDigit(1, 6, i + 1, false);
    lc.setDigit(1, 5, i + 2, false);
    lc.setDigit(1, 4, i + 3, false);
    lc.setDigit(1, 3, i + 4, false);
    lc.setDigit(1, 2, i + 5, false);
    lc.setDigit(1, 1, i + 6, false);
    lc.setDigit(1, 0, 2, true);
   
    delay(delaytime);
  }
  lc.clearDisplay(0);
  lc.clearDisplay(1);
  delay(delaytime);
}

void loop() {
  writeArduinoOn7Segment();
  scrollDigits();
}

LCDemodaisytest-2.ino

Edited May 14, 2021 by crash test pilot

[Stefan1208]

@crash test pilot

You are really great.....
I don't even know how to thank you for the help.
I think without your tips I would not be so far today and I think I would sit on it for days and weeks.

Thank you very much

.... I had my run and by now I have finished all of my 4 displays.

Tomorrow I can relax and do the wiring again and then install the displays in my center console.

Thank you again

null

 

[crash test pilot]

Have fun! Two years ago I was where you are now, and without this forum I would have no hmecockpit at all...

[No1sonuk]

On 5/13/2021 at 4:19 AM, Kenpilot said:

Ok spoke to soon. I'm having a hard time dialing in the position numbers to put in the sketch line:

 

DcsBios::ServoOutput flapPos(0x10a0,10, 1330, 1790);

 

With 1300 and 1790, The Flap setting is showing 0 when flaps are selected 0, whether I'm raising or lowering them, it always shows 0, so that's good. But when I select flaps down to 10 degrees, it shows 9 degrees, and then flaps down to 20, it shows 30 degrees. And then when I raise them back up to 20 degrees, it shows 12 degrees and then back up to 0 shows 0. I've played around with a bunch of different numbers but I can't figure out how to match the numbers to the flap setting selected. Any help would be greatly appreciated! 

I'd set up a standalone unit to test this.  Just put only the servo drive part in and don't connect anything else.

If you have too much hanging off the arduino's power supply, it could cause problems.
If it works fine in that configuration, try using an external 5V supply with the other setup.

[Kenpilot]

I need some help with the Landing Gear Safe indicator lights. Each of my LED indicator lights have 3 pin wire connectors. The GND is connected to a GND, The red wire is connected to 5v on the uno and the yellow(signal) wire is connected to pins 5,6,7 for Left, Nose and Right and the lights are continuously on. My sketch command lines are copied directly from the DCS Bios control reference. How come they are continuously ON and not what seems like getting communication from the sketch and turning on and off depending on what the actual lights are doing in DCS???

 

/*
  Tell DCS-BIOS to use a serial connection and use interrupt-driven
  communication. The main program will be interrupted to prioritize
  processing incoming data.

  This should work on any Arduino that has an ATMega328 controller
  (Uno, Pro Mini, many others).
*/
#define DCSBIOS_IRQ_SERIAL

#include "Servo.h"
#include "DcsBios.h"

DcsBios::ServoOutput flapPos(0x10a0,10, 1330, 1790);
DcsBios::LED handleGearWarning(0x1026, 0x4000, 9);

DcsBios::LED gearLSafe(0x1026, 0x1000, 6);
DcsBios::LED gearNSafe(0x1026, 0x0800, 7);
DcsBios::LED gearRSafe(0x1026, 0x2000, 8);

void setup() {
  DcsBios::setup();
}

void loop() {
  DcsBios::loop();

4 hours ago, No1sonuk said:

I'd set up a standalone unit to test this.  Just put only the servo drive part in and don't connect anything else.

If you have too much hanging off the arduino's power supply, it could cause problems.
If it works fine in that configuration, try using an external 5V supply with the other setup.

I've tried this before with only the servo connected to the uno and it still did the same thing. 

[crash test pilot]

What kind of LEDs are these? I suspect it may be a high-power led module that needs a pwm signal for brightness adjustment. You should use a two pin LED, one contact to ground and one to the signal pin on your arduino. Do not forget the resistor or your LED burns very bright once and not at all after that.

[Kenpilot]

6 minutes ago, crash test pilot said:

What kind of LEDs are these? I suspect it may be a high-power led module that needs a pwm signal for brightness adjustment. You should use a two pin LED, one contact to ground and one to the signal pin on your arduino. Do not forget the resistor or your LED burns very bright once and not at all after that.

They are indicator lights, korry style replicas, that I purchased from pcflights.com. The leds are built in to the indicator. 

 

https://pcflights.com/index.php?route=product/product&product_id=245&search=Boeing+indicator

 

Is there any way to make the 3 pin indicator work or do I need to remove the led that's in the indicator and put in 2 wire ones? 

Edited May 16, 2021 by Kenpilot

[crash test pilot]

Ok, these have two common ground pins. Use one of these for ground contact, and the +5v pin for the signal. Do not attach to +5v on your arduino. They have build-in resistors so you do not need extra resistor.

[Kenpilot]

1 minute ago, crash test pilot said:

Ok, these have two common ground pins. Use one of these for ground contact, and the +5v pin for the signal. Do not attach to +5v on your arduino. They have build-in resistors so you do not need extra resistor.

Ahhh ok. I'll try that. Thanks Crash Test Pilot!