G00dnight

Very nice this is a great idea something like a normal controller but with more buttons and a better layout, You had better patent it quick..

Sorry WarHog I did misread your post.

I think you should do it the way Ian wants not the way you think, it is his program and he is trying to give us a service. Easy way is to close this thread and then we have to start new ones. But he don't want to do that because of all the information in here.

Hi Baker I would like to say thanks for the update for 1.5 and 2.0, It all works fine here with both versions + Helios + DCS-Bios. I do have an interesting feature concerning Track IR, If I turn my head to a certain point the Exports minimise or move up off the lower screen I can just see a lower edge, then come back as soon as I move my head, It isn't a big deal and I haven't got a clue if it is repeatable on other setups. I will try different check boxes when I get time.

@ Terrorvogel, That is the main advantage of this. you can export the viewports to a screen that is NOT part of the DCS resolution so DCS can be running on a 1650 x 1080 top monitor and the MFD's, RWR Etc can be on any screen at there own resolution completely separate. It is drag and drop for placing and click and drag for resizing. At the moment there are some problems with the amount of changes DCS is going through breaking it on nearly every update so don't expect to get anything working well till we get DCS2 combined. Hope this helps with you question.

@ Onedef1, I still get the impression that you are confused. Umfcd does not need a toggle as it is not installed into DCS or your computer. It is a completely separate application that is NOT installed into DCS you can just have the folder sitting in any drive or even on your desktop, You either run it prior to starting DCS or you don't in which case nothing in DCS or your computer is changed so no need for a on/off toggle. hope this helps.

I have around 4 pots connected,,just never used them so don't know if they work, from what Ian said they don't LOL. I am in the middle of a pit rebuild as her in doors got the hump with a cockpit in the living room. Gets in the way.

Good vid only that weapon will sound completely different in an aircraft wing as its breach will be enclosed and that is where a lot of the sound comes from.

It has 14 digital + 6 analog pins so 20 in total, Are you planning on a 10 switch plus 10 push button box if so it will just do it. DCS-Bios is a good choice if you are capable of click and paste plus a few changes to DCS itself, then there is connecting all the switches I would suggest solder to the switches and pin connectors on the arduino. Have fun I have and I now have switches, lcd screens and leds on 7 panels.

If your a Pikey from Reading you have more to worry about than an Activation or two...:smilewink::music_whistling::pilotfly:

I have not had any problems with a Mega cpu not being fast enough I had one all pins connected plus 2 x 16/2 lcd screens worked like a dream in dcs as a full radio stack incorporating multi pos switches, toggles,push buttons,encoders,plain leds and the 2 16x2 character lcd screens. however it may struggle with a tft. I will be testing for my cdu at some point.

I think this is dcs does it work without UMFCD, if not do a repair, I use Skatezilla's update utility it is great.

I personally have used megas for everything they are not very expensive and you can always link small panels together using one mega for 2 or 3 panels. I use the prototyping board that has holes with rings round rather than stripboard and dupont pin connectors that are the same as the pins on arduinos, Do get the proper crimping tool for the dupont connectors though. Others use smaller arduinos one for each panel and plan to have them on a master and slaves system. I am not doing a full cockpit and most of my panels are hybrids of 2 or 3 panels.

They are normally left on for the ground crew checks etc then the ground crew will switch everything off. this is standard for a lot of aircraft as some ground checks require certain things to be on some of which would involve going through a lot of other things if the switches are not left on.

Just in case anyone out there has found their exports have stopped working in 1.5.5, If you use Capt Zeens export. Quote from another post. "if you are using one of my export.lua, look for this line: os.setlocale("ISO-8559-1", "numeric") and comment it like this: -- os.setlocale("ISO-8559-1", "numeric") That fix the problem."

You are correct Helios and DCS-Bios no longer works in 155, I have checked and nothing has changed in scripts so it must be in the game itself.

Thanks my tacan and ils rotary encoders now work perfectly.

@ GSS Rain. thanks spot on I thought it was summat simple. now on to the other 6 panels.

Hi I have just started to upgrade to latest build and I am having a problem with my lcd displays. I have a radio stack using a 16x2 for UHF and Clock and a 16x2 for the 2 VHF radios. All the buttons,encoders work fine even the 2 for Uhf Load and cover that come up in red on upload. the lcds light up and have a cursor flashing, they didn't used to do that, I use I2C boards connected to SDA/SCL on mega. my code follows. Thanks. #define DCSBIOS_IRQ_SERIAL #define BACKLIGHT_PIN 3 #include <LiquidCrystal_I2C.h> #include <Wire.h> #include <Servo.h> #include <DcsBios.h> LiquidCrystal_I2C lcd1(0x21, 3, POSITIVE); LiquidCrystal_I2C lcd2(0x27, 3, POSITIVE); /**** Make your changes after this line ****/ const byte uhf100mhzSelPins[3] = {10, 11, 12}; DcsBios::SwitchMultiPos uhf100mhzSel("UHF_100MHZ_SEL", uhf100mhzSelPins, 3); DcsBios::RotaryEncoder uhf10mhzSel("UHF_10MHZ_SEL", "DEC", "INC", 52, 53); DcsBios::RotaryEncoder uhf1mhzSel("UHF_1MHZ_SEL", "DEC", "INC", 50, 51); DcsBios::RotaryEncoder uhfPoint1mhzSel("UHF_POINT1MHZ_SEL", "DEC", "INC", 49, 48); DcsBios::RotaryEncoder uhfPoint25Sel("UHF_POINT25_SEL", "DEC", "INC", 47, 46); DcsBios::ActionButton uhfCoverToggle("UHF_COVER", "TOGGLE", 8); DcsBios::ActionButton uhfLoadToggle("UHF_LOAD", "TOGGLE", 9); const byte uhfFunctionPins[4] = {28, 26, 24, 22}; DcsBios::SwitchMultiPos uhfFunction("UHF_FUNCTION", uhfFunctionPins, 4); const byte uhfModePins[3] = {6, 5, 4}; DcsBios::SwitchMultiPos uhfMode("UHF_MODE", uhfModePins, 3); DcsBios::RotaryEncoder vhfamFreq1("VHFAM_FREQ1", "DEC", "INC", 45, 44); DcsBios::RotaryEncoder vhfamFreq2("VHFAM_FREQ2", "DEC", "INC", 43, 42); DcsBios::RotaryEncoder vhfamFreq3("VHFAM_FREQ3", "DEC", "INC", 41, 40); DcsBios::RotaryEncoder vhfamFreq4("VHFAM_FREQ4", "DEC", "INC", 39, 38); const byte vhfamFreqemerPins[4] = {A8, A9, A10, A11}; DcsBios::SwitchMultiPos vhfamFreqemer("VHFAM_FREQEMER", vhfamFreqemerPins, 4); const byte vhfamModePins[3] = {A0, A1, A2}; DcsBios::SwitchMultiPos vhfamMode("VHFAM_MODE", vhfamModePins, 3); DcsBios::RotaryEncoder vhffmFreq1("VHFFM_FREQ1", "DEC", "INC", 37, 36); DcsBios::RotaryEncoder vhffmFreq2("VHFFM_FREQ2", "DEC", "INC", 35, 34); DcsBios::RotaryEncoder vhffmFreq3("VHFFM_FREQ3", "DEC", "INC", 33, 32); DcsBios::RotaryEncoder vhffmFreq4("VHFFM_FREQ4", "DEC", "INC", 31, 30); const byte vhffmFreqemerPins[4] = {A12, A13, A14, A15}; DcsBios::SwitchMultiPos vhffmFreqemer("VHFFM_FREQEMER", vhffmFreqemerPins, 4); const byte vhffmModePins[3] = {A3, A4, A5}; DcsBios::SwitchMultiPos vhffmMode("VHFFM_MODE", vhffmModePins, 3); void onUhfFrequencyChange(char* newValue) { lcd1.setCursor(0, 0); lcd1.print(newValue); } DcsBios::StringBuffer<7> uhfFrequencyBuffer(0x1180, onUhfFrequencyChange); void onClockHhChange(char* newValue) { lcd1.setCursor(0, 1); lcd1.print(newValue); } DcsBios::StringBuffer<2> clockHhBuffer(0x10fe, onClockHhChange); void onClockMmChange(char* newValue) { lcd1.setCursor(3, 1); lcd1.print(newValue); } DcsBios::StringBuffer<2> clockMmBuffer(0x1100, onClockMmChange); void onClockSsChange(char* newValue) { lcd1.setCursor(6, 1); lcd1.print(newValue); } DcsBios::StringBuffer<2> clockSsBuffer(0x1102, onClockSsChange); void onClockEtcChange(char* newValue) { lcd1.setCursor(9, 1); lcd1.print(newValue); } DcsBios::StringBuffer<3> clockEtcBuffer(0x1104, onClockEtcChange); void onVhfcommFreqChange(char* newValue) { lcd2.setCursor(1, 0); lcd2.print(newValue); } DcsBios::StringBuffer<7> vhfcommFreqBuffer(0x14d4, onVhfcommFreqChange); void onVhfamFreq1Change(char* newValue) { lcd2.setCursor(1, 0); lcd2.print(newValue); } DcsBios::StringBuffer<2> vhfamFreq1StrBuffer(0x1190, onVhfamFreq1Change); void onVhfamFreq4Change(char* newValue) { lcd2.setCursor(8, 0); lcd2.print(newValue); } DcsBios::StringBuffer<2> vhfamFreq4StrBuffer(0x1192, onVhfamFreq4Change); void onVhffmFreq1Change(char* newValue) { lcd2.setCursor(1, 1); lcd2.print(newValue); } DcsBios::StringBuffer<2> vhffmFreq1StrBuffer(0x119a, onVhffmFreq1Change); void onVhffmFreq4Change(char* newValue) { lcd2.setCursor(8, 1); lcd2.print(newValue); } DcsBios::StringBuffer<2> vhffmFreq4StrBuffer(0x119e, onVhffmFreq4Change); void onDcsBiosWrite(unsigned int address, unsigned int value) { if (address == 0x118e) { unsigned int vhfamFreq2Value = (value & 0x00f0) >> 4; lcd2.setCursor(4, 0); lcd2.print(vhfamFreq2Value); } if (address == 0x118e) { unsigned int vhfamFreq3Value = (value & 0x0f00) >> 8; lcd2.setCursor(6, 0); lcd2.print(vhfamFreq3Value); } if (address == 0x119c) { unsigned int vhffmFreq2Value = (value & 0x000f) >> 0; lcd2.setCursor(4, 1); lcd2.print(vhffmFreq2Value); } if (address == 0x119c) { unsigned int vhffmFreq3Value = (value & 0x00f0) >> 4; lcd2.setCursor(6, 1); lcd2.print(vhffmFreq3Value); } } void setup() { DcsBios::setup(); lcd1.begin(16, 2); lcd2.begin(16, 2); } void loop() { DcsBios::loop(); }

Thanks for that , these are the leo bodnar type double encoder.

Hi. I have what I hope is an easy Question. I have panels with encoders on and have noticed that the ordinary small encoders work fine but I have a couple of larger dual encoders that when I turn them they move a place in dcs every 2 clicks. how can i adjust the ILS script on A10 to change this to 1 click per place in DCS. thanks.

I just tried DCS-Bios and same thing boxes show but no pictures, I do however get the text in very small letters showing in the right box also a very faint red dot of a target marker also in the right box.

Hi Baker just testing latest build, If I start UM then DCS sometimes I get DCS stopped working. If I start Helios and UM then DCS I get DCS work, Helios Work, UM working but with no pictures from DCS the frames with resize boxes show in place but no pictures in them. I also use DCS bios but have not tried it yet.

I think you need to contact ArturDCS he was doing this with DCS-Bios and saitek panels.

I think I remember hearing about something like this it had to do with the way W10 sees windows, do you run DCS full screen,if so try full screen windowed to test. sorry I cant be more help as I can't remember if there is a W10 setting to change.