LCD, Potentiometer, LED, Rotary Encoder all working with DCS-BIOS

 Learned a lot today trying to get a pot going: 

  • DO NOT have Serial.begin() in the hardware code as that seems to disrupt the DCS BIOS comms
  • DO NOT have a delay in the loop func - DCS BIOS can't do its thing
  • When you run multiple-com-ports.cmd watch for errors - if you have the IDE connected to the device the script will fail to connect since it is tied up - it will errors with a message about the device (but the com number will be 1 lowered that what you put in the script itself, must be zero-indexed)
  • Wire switches from GROUND to a digital pin, not from +5v
  • YOU CAN stop the bios cmd, deploy new code via IDE, and then restart BIOS while the game is running, so that is helpful
  • The BORT tool is called ...setup.exe - that is the binary itself, not a setup program
  • BORT does not appear to update all its values shown on-demand, seems to not be 2-way comms with BIOS - though SOME vals do work 2-way
  • The rotary encoder I was using would occasionally skip input or put out a double input.  It is just a lower quality unit.

==<11><7>===============================================
/*

  The circuit:
 * LCD RS pin to digital pin 7
 * LCD Enable pin to digital pin 8
 * LCD D4 pin to digital pin 9
 * LCD D5 pin to digital pin 10
 * LCD D6 pin to digital pin 11
 * LCD D7 pin to digital pin 12
 * LCD R/W pin to ground
 * LCD VSS pin to ground
 * LCD VCC pin to 5V
 * 10K resistor:
 * ends to +5V and ground
 * wiper to LCD VO pin (pin 3)

 OTHER STUFF TOO

*/


#define DCSBIOS_DEFAULT_SERIAL

#include "DcsBios.h"
#include <LiquidCrystal.h>

#define POT_PIN A0
#define MASTER_LED 6

DcsBios::Potentiometer uhfVol("UHF_VOL", POT_PIN);
DcsBios::Switch2Pos ahcpTgp("AHCP_TGP", 5);
DcsBios::Switch2Pos lampTestBtn("LAMP_TEST_BTN", 4); // rote enc switch
DcsBios::LED masterCaution(0x1012, 0x0800, MASTER_LED);
DcsBios::RotaryEncoderT<POLL_EVERY_TIME, 2> arc21010mhzSel("ARC210_10MHZ_SEL", "DEC", "INC", 2, 3); // setting steps to 2 (in brackets) instead of default 4 - 
          //get proper encoders to avoid this and other skip issues

// initialize the library with the numbers of the interface pins
LiquidCrystal lcd(7, 8, 9, 10, 11, 12);

//-------

void onArc210ComsecModeChange(char* newValue) {
  lcd.setCursor(0,0);
  lcd.print("                "); // 16 blanks to clear row
  lcd.setCursor(0,0);
  lcd.print(newValue);
}

DcsBios::StringBuffer<11> arc210ComsecModeBuffer(0x12ee, onArc210ComsecModeChange);

//------

void onArc210FrequencyChange(char* newValue) {
  lcd.setCursor(0,1); // col, row - zero index
  lcd.print("                "); // 16 blanks to clear row
  lcd.setCursor(0,1); // col, row - zero index
  lcd.print(newValue);
}

DcsBios::StringBuffer<7> arc210FrequencyBuffer(0x1382, onArc210FrequencyChange);

//------

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

    lcd.begin(16, 2);
  // Print a message to the LCD.
  lcd.print("Hello, World!");
}

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

Comments

Post a Comment

Popular posts from this blog

Updating data on the Garmin Perspective system

Image
After changing from the Avidyne system to the Cirrus Perspective (G1000) system, I had to relearn an important part of owning an airplane: how to update all the data the systems use. There's even more data in the Perspective, including AOPA directory data and more charts. In this walkthrough, I make use of the Jeppesen app for Apple OS X: JDM .  It has worked well for me, though I did need to call Jeppesen when I first set this up to get my subscriptions fixed up.  They gave great customer support when I did. The process starts (optionally) by hooking up a ground power unit (GPU).  In the case of the Cirrus, you can certainly do this without it, but I tend to hook it up just to be sure.  The systems draw about 8-10amps while updating, but you won't generally have the power on for long.  One tip I've read: power up the GPU before plugging it into the plane, at least for the one I bought.  That saves the plane from seeing any power spikes that might have occurred when t
Read more

G1000 transistion training - emergencies - final flight

Image
For the final flight in my G1000 transition course we focused on failure scenarios. Not the "engine goes POOF" kind but the avionics kind. Normal situation This picture shows what the 2 Garmin screens show in a normal (non failure) situation. You can see we have 2 screens - the left PFD focusing on flight performance (airspeed, heading, attitude, altitude) and the right screen (MFD) focusing on engine data, mapping, checklists, and everything else. Failed PFD screen In this scenario the screen that is right in front of you (the PFD) has failed. This basically means the screen has gone dark. We simulate that by dimming the screen down to 0% brightness. After darkening the PFD we shot a GPS approach into Rock Hill. When this failure has occured you shift the G1000 into Reversionary mode. That means the info that is normally split across 2 screens is now merged into 1. It actually duplicates the same data on both screens, but since the PFD screen is no longer functioning
Read more

A-10C Standby Compass - Sun Shade

Image
 One of the final items to add to this instrument build (besides the text covers for the lower LEDs) was the sun shade for the AR LED box.  I made this out of thin aluminum sheets , cutting it from a template using some metal sheers .    My template was created by tracing some of the actual artwork from the DCS sim, and then scaling it to the proper size. It turned out ok, not perfect but pretty good.  Primed and painted it and then installed it using 2 of the 4 holes that were already on the LED box 3D print.  I used some heat inserts in those holes to give the screws something to bite, but the holes are really too big for my inserts so had to use some glue to help out.  
Read more