DCS-BIOS Discussion Thread

[NightShiftNinja]

Thanks techross, I just went through his entire build thread. I may have to talk to him and look in to that.

 

Quick question for you experts, will a mega be able to power a single led off of usb power or do I need an external power supply???

 

Sent from my SM-G930W8 using Tapatalk

[Inverted]

Quick question for you experts, will a mega be able to power a single led off of usb power or do I need an external power supply???

I'm no expert but yes the mega will have no problem powering an LED, as long as it's not a high power one.

The max output it can provide from USB power is 500mA afaik.

[Elnocho3]

Before I commit to designing my UFC-ish panel around DCS-BIOS, can somebody answer if it works regardless of multiplayer server settings? As in, will integrity checks or export lua restrictions from certain servers break it?

[NightShiftNinja]

question for you guys, i just built the master caution test circuit and can get it to work fine in the release build but i can not get it to work in the open beta build. both (and 1 at a time) of the save folders for release and open beta have the dcs bios folder in them. is there something i missed to get it to work in the open beta.

 

Thanks

[Tekkx]

I'm no expert but yes the mega will have no problem powering an LED, as long as it's not a high power one.

The max output it can provide from USB power is 500mA afaik.

 

500 mA is the value of the "main" protecting (self resetting) PTC. It protects your connected PC's USB-port by preventing over current in case of a short circuit (or other incidents).

Each port (no matter if PWM or not) should not loaded with more than 20 mA (40 mA for a short time). This is exactly the value of one "normal" LED with suitable Resistor.

This is valid to all members of the Arduino-Family. But consider not to exceed an overall load of 150 mA.

Thumb rule: If it starts smoking: It has been to much and it's too late.

 

If you're in doubt: You don't have to be expert to read a datasheet. (GiyF! and every PDF-reader has a search tool - often to start by F3)

https://www.sparkfun.com/datasheets/Components/SMD/ATMega328.pdf

Check out paragraph 26.2 DC Characteristics, page 313ff

 

question for you guys, i just built the master caution test circuit and can get it to work fine in the release build but i can not get it to work in the open beta build. both (and 1 at a time) of the save folders for release and open beta have the dcs bios folder in them. is there something i missed to get it to work in the open beta.

Thanks

This should also run with the Open Beta. Checkout if you modified the script files as you did inside the release build.

Last weekend I almost to despair while bringing my DCS (with Helios, external Screens, Headtracker and DCS-BIOS) back to work after half a year to be "grounded". So I know it's easy to overlook a little line of code.

Edited February 6, 2019 by Tekkx

[BlackLibrary]

Hi

we made a Fork from the Original DCS-BIOS repositorie and made some additions to it.

More planes!!

 

At least the A-4 and the MB-339PAN are integraded.

here the link to it: GitHub

 

The Mig-15 needs Testers, because i dont own the module

 

I got the files for the 3 missing planes (to cover all aviable in DCS), but i dont have the modules.

 

To make the Files i need the names in DCS-BIOS for the planes. a Screenshot would be the best.

 

 

To get it,jump in one of the missing planes, open the BIOS refpage, in MetadataStart can the name found. (i add an example )

 

Missing planes are: Yak-52, Christen Eagle, C101 in both variants.

Maybe someone can help.

[BlackLibrary]

new Release:

Planes added:

Yak-52, MiG-19P, Christian Eagle II and Tomcat (WIP)

 

and Basic Data support for some Mods

VSN-Mods, PAK-FA Project, Civil Aircraft Mod, Upuaut’s Bell-47G, Mirage F.1, SU-30 FAMILY PROJECT,MIG-23UB Project

 

v.0.7.25 from GitHub

[Mverick]

Hi

 

I tried to access DCS BIOS link http://dcsbios.a10c.de but does not work!!!

 

Is there a new link or problem with the page?

 

Thanks

[patogn20]

Same problem!

[BlackLibrary]

There is a "copy " of the page, in the doc folder of dcs bios ;)

[patogn20]

There is a "copy " of the page, in the doc folder of dcs bios ;)

 

I'm sorry... where?

[BlackLibrary]

Dcs-bios/Doc there are the guide .html

[Mverick]

Dcs-bios/Doc there are the guide .html

 

I already saw that, but noticed the files are a bit old.

I suppose the version that was online would be more up to date.

 

But out of curiosity, is there any special reason why the page is down?

[BlackLibrary]

i dont know.

last change on page was early 2017. i have keept them up todate., In next version i made a "Start page" where you can find tutorials, gudes and latest versions. Like the web start page

[Roger01]

Hi, I use Helios to get some instruments informations but Helios do a hudge fps drop . Can I use dcs bios to create virtual instrument like an export (like Helios...)? Using c++ builder and import dcs bios output. (I'm noob on programmation) thx!

[Tekkx]

Your Question: No. You can't export instruments. DCS-BIOS ex- and imports just positions of switches, buttons, lamps and pots. Exception: Screen of the CDU (line by line).

 

FPS-drop: From my POV (point of view) it isn't to blame on HELIOS. It's just the higher resolution, resulting from the extra screen where you export HELIOS to.

On my system I watched a slightly drop of FPS with Facetrack. It consumes about 15 % of CPU. I antagonized this with a larger CPU. :)

[Roger01]

Dcs bios : I would like to use the data of dcs bios to create instruments on a 2nd screen.

 

Helios. It's Helios, coz i use it on the same screen of my mfd export and I export only 2/3 lights from Helios.

[Yngwie84]

Hi.

I have a suggestion for new dcs-bios-arduino-library function.

My DCS Bios Project thread.

I'm an electrician but not a good c++ programmer.

I just created a new post about my "budget box" i'm experimenting with now.

https://forums.eagle.ru/showthread.php?t=236617

 

My problem:

I've been coding and trying to make it so a button changes a value by adding 1 and use that button as an multi pos switch but I've been failing and just found out why.

The testcode I was trying to run should as it is below not send anything to DCSBIOS, but it sends jibberish.

 

// Counts number of button presses
#define DCSBIOS_IRQ_SERIAL
#include "DcsBios.h"

byte switchPin = 2;                    // switch is connected to pin 2
byte buttonPresses = 0;                // how many times the button has been pressed 
byte lastPressCount = 0;               // to keep track of last press count
bool lastRead = LOW;
#define pos1 0
#define pos2 1
#define pos3 2

const byte domeLightSwPins[3] = {pos1, pos2, pos3};
DcsBios::SwitchMultiPos domeLightSw("DOME_LIGHT_SW", domeLightSwPins, 3);
void setup() {
 DcsBios::setup();
 pinMode(switchPin, INPUT_PULLUP);          // Set the switch pin as input
//  digitalWrite(switchPin, HIGH);      // set pullup resistor
}

void loop(){
 DcsBios::loop();
 if ((digitalRead(switchPin) == LOW) && (lastRead == HIGH) && (lastRead == LOW))  // check if button was pressed
 {
   buttonPresses++;                  // increment buttonPresses count
   delay(1000);                       // debounce switch
 }
 if (buttonPresses == 3) buttonPresses = 0;         // rollover every fourth press
 if (lastPressCount != buttonPresses)              // only do output if the count has changed
 {
   lastPressCount = buttonPresses;    // track last press count
 }
 lastRead = digitalRead(switchPin);
}

 

Solution.

In the Arduino library add the support to use a toggle action switch.

As it is now it has to be to a pin and you can't use a variable.

 

What I want it for.

I'm building a button box that needs to be generic.

Bottom row are all rotary encoders with push buttons.

I want the bottom left one to always in every aircraft "turn on" radio1, My thinking behind radio, say in the Huey, the radio you use the most on a mp server, like UHF 264 to talk to MP GCI and radio 2 30.00 VHFFM to talk to other Helipilots.

In the Huey the power switch is a 4-way switch, in another plane it's something else.

[BlackLibrary]

New Version Online:

 

https://github.com/DCSFlightpanels/dcs-bios/releases/tag/0.7.25b

 

F-14 is almost complete.

 

 

Testers needed for: F-14B, MB-339PAN, MiG-15Bis, MiG-19P, Christen Eagle II, Yak-52, socat Versions

 

need fedback if the Planes,Programs worked as intended

Edited March 23, 2019 by BlackLibrary

[PEEP]

Hi

we made a Fork from the Original DCS-BIOS repositorie and made some additions to it.

More planes!!

 

At least the A-4 and the MB-339PAN are integraded.

here the link to it: GitHub

 

The Mig-15 needs Testers, because i dont own the module

 

I got the files for the 3 missing planes (to cover all aviable in DCS), but i dont have the modules.

 

To make the Files i need the names in DCS-BIOS for the planes. a Screenshot would be the best.

 

 

To get it,jump in one of the missing planes, open the BIOS refpage, in MetadataStart can the name found. (i add an example )

 

Missing planes are: Yak-52, Christen Eagle, C101 in both variants.

Maybe someone can help.

Hi BlackLibrary

See attached if you still need them

[BlackLibrary]

@PEEP Thanks that helps.

 

After the Tomcat and a short break, i will start with it

[patogn20]

Hi! Is there any way to export the Huey Clock to a digital format? To use an LCD

[JG14_Smil]

Hello,

 

I am working on a module for the L-39C. Kagga's L-39ZA .lua starts with this line:

 

"BIOS.protocol.beginModule("L-39ZA", 0x3200)"

 

 

How do I find, or could someone tell me, the address in red for the 39C?

 

Thank you in advance.

[JG14_Smil]

Replace 0x1234 with a base address for your module. A base address is the address in the DCS-BIOS export address space where the data from your export module starts. Choose it in a way so the address space occupied by your module does not overlap with any other export module that is active at the same time. Ideally, choose it so you do not have an overlap with any other export module. As a rule of thumb, take the highest base address of an existing export module (except MetadataEnd) and add 1024 (0x400). 1 KiB of address space should be more than enough for most aircraft.

 

Largest address I find is the P-51D with 0x5000, so I will try 0x5400.

[JG14_Smil]

Found DCS-BIOS/Lib/addresses.txt and all addy's are listed. 0x5400 is the Spitfire address. tried going higher but not getting any in/out when in the "C". Works fine in the "ZA".