Kaiser78

Great. That worked. Thank you.

Where are the practice missions located? I just purchased the campaign, and I cannot find them in the campaign section. They do not come up in the training section, nor do they come in the My missions folder.

I own the hawk and this looks similar. The hawk can cover more ground and get there quicker. Plus the albatross is out and they look to fill the same roll. Love the M2k though. Keep up the good work.

No luck. I tried 250000 and also 125000. Both my export.lua and the one provided. I am going to try using an Uno without it being soldered and see what happens. Maybe there is something with the pro mini that is an issue. I also shared a common ground with all the switches. Just going to hook up one switch and ground and see what happens. DCS BIOS 0.3.0 UPDATE: Hooked up one switch on an Uno and it worked flawlessly. It also went from Com 7 to Com 4. Tried another mini pro no luck. When loading the software on the mini pro's compared to the Uno it was a lot longer. Also with the Uno the TX/RX lights were blinking all the time while the MiniPro. Starting to wonder if its the USB adapter that was stopping the correct communication. Either way, thanks IAN. Looks like I'm off to buy some Uno's.

Help To anyone who can help. Following the hard work put in by others I am converting my pit from strictly Helios to DCS Bios because I am able to make arduino boards at work for projects. I had a pro mini laying around and decided to give this a try. Following the instructions at appears that the switches work when looking at the scrolling cmd file but I get no feedback from DCS. I have modified the cmd file for the com port my arduino is on (com 7) and I placed the DCS BIOS folder into my DCS Scripts folder as seen in the 2nd picture. I have my own Export.lua file and I have tried using just the original one supplied to me by IAN. Neither seem to work. Picture 3 is of my device manager showing there are no issues with COM 7. I also just loaded the blinking light example on the arduino IDE just to make sure everything was OK. Which it was. Then loaded my electrical panel sketch based on the instructions given on the web page. The last image is what I get when I don't have DCS running but go through the 6 switches from the electrical panel. Everytime I toggle a switch I get a result back but nothing that tells me if it is on or off. But it appears that there is a response when I flip the toggle. Here is the sketch: #include <DcsBios.h> #include <Servo.h> /**** Make your changes after this line ****/ DcsBios::Switch2Pos eppEmerFlood("EPP_EMER_FLOOD", 4); DcsBios::Switch3Pos eppInverter("EPP_INVERTER", 3, 12); DcsBios::Switch2Pos eppApuGenPwr("EPP_APU_GEN_PWR", 2); DcsBios::Switch2Pos eppBatteryPwr("EPP_BATTERY_PWR", 5); DcsBios::Switch2Pos eppAcGenPwrL("EPP_AC_GEN_PWR_L", 7); DcsBios::Switch2Pos eppAcGenPwrR("EPP_AC_GEN_PWR_R", 6); /**** In most cases, you do not have to change anything below this line ****/ /* Instantiate a ProtocolParser object to parse the DCS-BIOS export stream */ DcsBios::ProtocolParser parser; void setup() { Serial.begin(500000); } /* Your main loop needs to pass data from the DCS-BIOS export stream to the parser object you instantiated above. It also needs to call DcsBios::PollingInput::pollInputs() to detect changes in the state of connected controls and pass them on to DCS. */ void loop() { // feed incoming data to the parser while (Serial.available()) { parser.processChar(Serial.read()); } // poll inputs DcsBios::PollingInput::pollInputs(); } /* You need to define void sendDcsBiosMessage(const char* msg, const char* arg) so that the string msg, followed by a space, the string arg and a newline gets sent to the DCS-BIOS import stream. In this example we send it to the serial port, so you need to run socat to read the data from the serial port and send it over UDP to DCS-BIOS. If you are using an Ethernet Shield, you would probably want to send a UDP packet from this subroutine. */ void sendDcsBiosMessage(const char* msg, const char* arg) { Serial.write(msg); Serial.write(' '); Serial.write(arg); Serial.write('\n'); } /* This subroutine gets called every time a message is received from the export stream (you need to define it even if it does nothing). Use this to handle outputs which are not covered by the DcsBios Arduino library (e.g. displays). */ void onDcsBiosWrite(unsigned int address, unsigned int value) { } } PS ignore the smiley faces. That resulted from the : P in the code when I copied it.

Looks good. I can't wait for my house to be finished so I can finally make the side panels. As for the arduino, I spend most my time reading and learning here.

Those of you looking to use arduino a in your pits, http://www.sparkfun.com is having a sale this weekend.

Yeah we do all of those things. Maybe it's my wingman goofing up somewhere. It wouldn't be the first time. It was working for the longest time. Maybe he did something different.

No I am not lasing. I find the target in my tgp and tms up short to lock. Then tms up long to make it my spi. Hook my wingman in my tad and send. If I need to lase when would that need to be done? Before I tms up short to lock?

Looks like my dream will be short lived. They said that at 6 foot 3 I was too tall when I talked with them today.

Yeah it's always off. Doesn't matter if he sends me or I send him.

When sending my buddy my spi over the net he accepts the tasking and it's never correct when he looks in his mfcd. I know this was a problem long ago but is anybody still having issues with this?

Thanks Thick8.

Excellent job!

Yes! Thank you, thank you, thank you.