Search the Community
Showing results for tags 'dcs bios'.
-
I am building a motor driven cyclic to provide variable centering torque and trim position, and one of the key goals is to have the stick follow the co-pilot stick when the co-pilot is flying (either when 'autopilot' or in multiplayer) - in the real Huey the two sticks are mechanically linked so the always follow each other, and linking them in the game means that way when you take back control the stick is already in the right place. However I have not been able to find any exportable data for the stick position. (This may be specific to the Huey, I'm not sure, but I imagine the it should probably be common to all aircraft) The list_cockpit_params() lua function returns BASE_SENSOR_STICK_PITCH_POS and BASE_SENSOR_STICK_ROLL_POS, but it is just a reflection of the pilot stick input - when in 'autopilot' it continues emitting the pilot stick input position (ie. my joystick position), not the copilot stick position that is actually controlling the aircraft. When you show the control positions overlay, it is the position of the white copilot diamond I want, not the one that moves with my own stick. This data is obviously there somewhere as it is used to display on the controls overlay and also used to animate the cyclic position when in 'autopilot' mode - the question is, is it accessible from a lua script? Any ideas, anyone?
-
fa18_simpit.ino I noticed theres not a lot of info pertaining to planning the circuits and building the code with "Arduino" and "DCS bios " or maybe its buried in the archives so I'll leave this here. This is my attempt to future proof my starting point on my flight panel build, in an attempt to use as little storage and pins as possible. you'll see I'm using a clunky but simple method to combine DCS bios global variables with ad-mux-library channels and also kept the loop as short as possible to maintain a high refresh rate as the build goes on that will likely change. I have yet to verify this even works as I am waiting for supplies and wanted a starting point with the code to familiarize with and test as i build. any ways let me know what you guys think
-
New to DCS-Bios and Arduino Won't connect to Virtual Cockpit
supa325 posted a topic in Home Cockpits
A few weeks back, I happened to find a home made A-10C Electric Panel wired to a Arduino Nano. I also have an old landing gear handle that I've been wanting to wire up, but has been a bit overwhelming. So I find this panel, wired, and cheap. I buy it thinking the hard part is done, and I can reverse engineer how this person physically hooked it up. I get arduino started, I follow the online instructions and assign a couple of switches and upload it successfully to my nano. But, DCS Bios "Virtual Cockpit" doesn't turn green. I've tried to add DCS bios automatically and also copy-paste to my Export.lua. And the right Com port is connected in Bios Bios is installed in C:, Beta is in C:/Users/.../SavedGames and also E: This is my test code uploaded into Arduino for my F-16 #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" DcsBios::Switch2Pos gearHandle("GEAR_HANDLE", 9); DcsBios::Switch2Pos airRefuelSw("AIR_REFUEL_SW", 8); DcsBios::Switch2Pos storesConfigSw("STORES_CONFIG_SW", 4); void setup() { DcsBios::setup(); } void loop() { DcsBios::loop(); } -
Hello! As the title says I need help with my segment display. Im making uhf radio panel for my f-16c simpit. I bought that nice display https://pl.aliexpress.com/item/4001293690559.html?gatewayAdapt=glo2pol&spm=a2g0o.order_list.0.0.21ef1c24AJGZ6f After many hours trying to make it work with DCS BIOS, it's actually worked... But there are some issues. When I turn on radio, digits turns on too and I can change them correctly, but when Im turning off radio, all digits are changing to 0 and staying in that position til I turn radio on again. I want to have blank display! My code: /* Mega and Uno pinout is the same * GRND = GRND * VCC = 5V * D10 = Digital input pin - this code uses pin 3 * CLK = Digital input pin - this code uses pin 2 */ #define DCSBIOS_DEFAULT_SERIAL #include <Arduino.h> #include <TM1637TinyDisplay6.h> #define CLK 2 //pins definitions for TM1637 and can be changed to other ports #define DIO 3 TM1637TinyDisplay6 display(CLK, DIO); #include "DcsBios.h" uint8_t data[] = { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; // Test Pattern - All uint8_t blank[] = { 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 }; // Test Pattern - Blank uint8_t dots = 0b01010000; // Add dots or colons (depends on display module) // DCS-Bios Code void onUhfFreqDispChange(char* newValue) { //newValue[3] - dot display.setBrightness(1); data[0] = display.encodeDigit(newValue[0]); // digit 1 data[1] = display.encodeDigit(newValue[1]); // digit 2 data[2] = display.encodeDigit(newValue[2]); // digit 3 data[3] = display.encodeDigit(newValue[4]); // digit 4 data[4] = display.encodeDigit(newValue[5]); // digit 5 data[5] = display.encodeDigit(newValue[6]); // digit 6 display.setSegments(data); } DcsBios::StringBuffer<7> uhfFreqDispBuffer(0x4590, onUhfFreqDispChange); // End DCS-Bios Code void setup() { DcsBios::setup(); display.clear(); display.setSegments(blank); } void loop() { DcsBios::loop(); } Library that I'm using: https://github.com/jasonacox/TM1637TinyDisplay I was trying many others but that one seems to work the best for me. I'm using arduino mega Thank you in advance for help and sorry for my English!
- 23 replies
-
- f-16 uhf radio
- tm1637
-
(and 3 more)
Tagged with:
-
After last update I had problems with caution lights in my cockpit. As I checked in Control Reference their codes has changed E.g: DcsBios::LED lightMainGen(0x4476, 0x0020, 12); (Before) DcsBios::LED lightMainGen(0x447a, 0x0002, 12); (Now) This small diffrences made my lights completly usless. After changes in codes they are working. I saw that my segment display is not working with code that was fine before, so I checed strings, and they are diffrents too. E.g: DcsBios::StringBuffer<7> uhfFreqDispBuffer(0x4590, onUhfFreqDispChange); (Before) DcsBios::StringBuffer<7> uhfFreqDispBuffer(0x45a8, onUhfFreqDispChange); (Now) Anyone of you had same problems as me? Is there are any other thigns I should know?