crash test pilot

Do you have a multimeter to check if the labeling for the pins on the tle5010 board is correct? I remember reading somewhere about mislabeled pins on some of these boards. The setup is correct, just tested on mine and it works.

https://github.com/DCSFlightpanels/dcs-bios/blob/master/Scripts/DCS-BIOS/doc/userguide.adoc

I know blacklibrary is fast on updating the flightpanel fork, but not that fast. Give him a week. As far as I know the hub version does not get that much love.

What software do you plan to use? For mmjoy2 a cheap but adequate replacement would be a pro micro clone (around 5 bucks). It has less input ports but for your planned 35 inputs i would use shift registers which you can daisy-chain for up to 132 inputs (8 inputs per sr chip; 8 in a chain, mmjoy supports 2 chains). For the atmega chip based control boards 10k pots are good, just make shure you get linear (b10k) and not logaritmic (a10k) pots. Nice looking prototype btw!

Funny... My Warthog stick was perfectly upright with the standard springs - just a little wobble if i released the stick from full deflection.

Its 3 shift registers cd4021. User rel4y offers ready.made, debolestis offers boards for self soldering or you design your own - can be done on strip board.

WarBRD and Warthog stick worked fine for me with the soft spring, for the 20cm curved extension i had to install the extra heavy springs.

If ypo have a legal win7 key you can still upgrade to win10 for free. Microsoft never made that public but they have not deactivated the free upgrade possibility.

I have MFG Crosswinds with dampener and i am totally satisfied. I read a lot of bad rewiews for the tpr´s, but not a single bad one for crosswinds. Slaws seem to be equally good but much more expensive.

Looking nice! Now all I need is a 3d-printer...

Wonderful! Thanks for a really handy tool! A note: even the small 9g servo draws up to 700 mA, which is far too much for a nano (max 200mA), so an external power source is a must.

mmjoy2 (freeware) and a cheap pro micro clone (around 5 bucks on the bay) will work. within the mmjoy folder is a picture folder, there you find a pin-out for the cougar which is the same on the warthog.

Within mmjoy2 folder you should have a tools folder, there you find usbdeview.exe. Try deleting devices there and rewrite new vid/pid from mmjoy again.

Virpil base owner here, it is very much better than TM base. Yes, they are compatible with Warthog and Cougar sticks.

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.

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.

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

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

@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....

Do you have any possibility to test wether its the base or the stick? If the stick itself works, you could upgrade to a virpil base. A cheap pro micro and mmjoy2 software would be an easy test tool... plus you can use it afterwards for building a button box.

@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!

@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?

Do you have added the export lines to the export.lua?

The line DcsBios::Integerbuffer flapPosBuffer(going-on-and-on); was part of the display void (think of a void as a sub program run within the main program) so you need to delete that too. Edit: minimal code should look like this: #define DCSBIOS_DEFAULT_SERIAL #include "Servo.h" #include "DcsBios.h" DcsBios::ServoOutput flapPos(0x10a0, 9, 2400, 1472); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); }

You forgot the end brackets #include "Servo.h" and you do not need the void onflapposchange part, this is for printing the flap pos on a display (so forget my last edit, was junk, sorry).