Hansolo

Alright lets start with getting the display online. First of all you need to wire it correctly. In the pictures you posted there isn't any wires on but they Display Uno Vcc 5V GND GND SCL A5 (SCL) SDA A4 (SDA) Since you can compile I assume that you have the OLED library installed? This code should work; /* Tell DCS-BIOS to use a serial connection and use the default Arduino Serial library. This will work on the vast majority of Arduino-compatible boards, but you can get corrupted data if you have too many or too slow outputs (e.g. when you have multiple character displays), because the receive buffer can fill up if the sketch spends too much time updating them. If you can, use the IRQ Serial connection instead. */ #define DCSBIOS_DEFAULT_SERIAL #include "DcsBios.h" #include "Wire.h" #include "OLedI2C.h" OLedI2C LCD; /* paste code snippets from the reference documentation here */ void onCmsp1Change(char* newValue) { LCD.sendString(newValue, 0, 0); } DcsBios::StringBuffer<19> cmsp1Buffer(0x1000, onCmsp1Change); void onCmsp2Change(char* newValue) { LCD.sendString(newValue, 0, 1); } DcsBios::StringBuffer<19> cmsp2Buffer(0x1014, onCmsp2Change); void setup() { DcsBios::setup(); Wire.begin(); LCD.init(); } void loop() { DcsBios::loop(); } I don't really understand this. Are you talking Serial Monitor? As for the RS485 I can't help you at the moment as I am waiting for parts to figure out why I can't get a second Mega running as Master. Cheers Hans

My example? Which one to be precise?

Hi Gary I am not home but will be in 8 hours. I got mine working and can upload my sketch. You should need anything special apart from correct wiring and correct sketch. I'll get back to you later unless someone beats me to it Cheers Hans

Yes if I read the description correctly you get the Mega to show up as two joystick controller each of 128 bottons. This is quite similar to the B256A13 boards I have and as Overpro states then Windows can't show more than 128 buttons. As far as I understand you configure the Mega to be a joystick controller but then cannot function with DCS-BIOS. You have to make the choise whether to go with DCS-BIOS or joystick controller per board. But there is nothing wrong with using both systems in your pit. I am still in the transfer phase from joystick controller to DCS-BIOS so I am running a little of both. There can also be some flexibillity in running some of your things with joystick controllers. When using DCS-BIOS you program the Arduino to become e.g. landing gear panel for the A-10. Which also means that you can't use this for e.g. the F-5 unless you reprogram the Arduino. With a joystick controller you can just map the inputs to a new module. Hope it made a little sense. Cheers Hans

Beautiful craftmansship Sir. Looking awesome. I really enjoy watching these 'pack-away-pit' as there is so much thoughs gone into the design and it will allow for more people to have a pit as opposed to the big ones :thumbup: Nice job Sir. Cheers Hans

Hi WhoMadeWho, Sorry can't really help you with rounding up/down of the number. BUT do you really want to do this?? My reason for asking is that when you fly a DME arc of 8, you would like to know if you are going away from or closer to before the switch to either 9 or 7. Ian, and others I presume, made some altimeters using OLED and there you get the same display as you do on the altimeter which I think may be hacked into showing the HSI range in a similar fasion; Just a kind suggestion Cheers Hans

Looks like you are off to a good start Sir. - I don't think the Leo Bodnar card has any problem reading ON-ON nor ON-ON-ON. The problem may be in the joystick lua you need to change to facilitate this. - It's true that you can only use modules where the software package has been done for DCS-BIOS. Or you can do it yourself. Alternatively you may want to look at Overpro's mod for an Arduino Mega which turns into a joystick controller https://forums.eagle.ru/showthread.php?t=117011 As for DCS-BIOS, Ian has a Youtube page where you can find some initial answers; https://www.youtube.com/channel/UCwECFPfC3QJiNYS5fskF2vg As long as you are using 'just' switches then it very easy to use. When you want to do more advanced stuff it may get more tricky but the options are there to do it or learn how to do it. Cheers Hans

Thanks a lot Snoopy and rest of 476th for making these available for us. Much appreciated gents. Cheers Solo

Whoa Calum that looks awesome man. You have really been busy :thumbup: That AN/ARC-164 and -186 really looks professionally done. Can't wait to see the result of all your hard word. Cheers Hans

Two TACAN's for $25; https://www.ebay.com/itm/122951984195?ul_noapp=true Cheers

Yes it is. After you have made mark point for all your targets (in this axample A, B & C), shift Aux. Avionics Panel PAGE knob into WAYPT. Now call up mark point A by typing A into the scratch pad and press L3 on the CDU to call up mark point A, type in the new name e.g. TGT.A and press R3. Mark point A has now been renamed to TGT.A Now call up mark point B by typing B into the scratch pad and press L3 on the CDU to call up mark point B, type in the new name e.g. TGT.B and press R3. Mark point B has now been renamed to TGT.B Quick poor recording Cheers Solo

Hi Sven, I didn't get my boards to work even though I tried the solution suggested by Ian. But during this I did notice one difference between the Arduino Mega I have running as RS485 Master and the remaining Arduino Mega's I have laying around. My working master is using a ATMEGA16U2 chip for the communication whereas the others are using a CH340 which from what I can read is just a USB to TTL converter. I honestly don't know if this is the issue but I have ordered two Arduino Mega's from Germany with ATMEGA16U2 jo to see if that can be related. Once I get the two new boards I will try and load it as RS485 Master and see if it pops online immediately. Cheers Hans

IIRCC 250k or a 500k ohm potentiometer would be much more sensitive for noise as the current running through is a lot less. 500k ohm: I=0.01 mA 10k ohm: I=0.5 mA This is from Brydlings B256A13 manual (https://forums.eagle.ru/showpost.php?p=1304711&postcount=1) You'll be running an Arduino but I imagine the noise isssue would be the same. Cheers Hans

I got Helios working with 2.5. Didn't do anything but to copy all the files from saved gamed scrips folder of 1.5.8 into 2.5. Cheers Solo

Added illustration to hopefully clear the confusion in the text. Cheers Solo

Wrote one of our VWing's CAS Instructor who is active JTAC. He says you should avoid overflying friendlies at all cost. Final Attack Heading depends on the situation but ideally weapons should be dropped on friendlies 3-9 line. If weapon goes short or long then you don't risk fraggin friendly forces. Cheers Solo

To the best of my knowledge new modules will not be automatically added into DCS-BIOS. Someone has to do the work of including the module. There is a how to start on the DCS-BIOS website; http://dcs-bios.a10c.de/docs/v0.7.0/developerguide.html So IMHO all it takes is for someone wanting the module enough to lift the task of making all the code necessary for Ian to include into the DCS-BIOS. As you can see pdmarch and ArthurDCS have already done a great job in adding other modules with their DCSFlightpanels project; https://github.com/DCSFlightpanels/DCSFlightpanels Cheers Hans

Searching with the TGP is like looking through a soda straw and is time consuming. You have to find the general target area, slew the TGP around target area to find target, set TGP as SPI designator, slew all sensors to SPI, shift to MAV page, lock and fire. If you have already located the app. target location you can fly the A/C unto target using the wagon wheel in the HUD which will speed up the process. Here is an example of 4xRIFLE on a target of opportunity. The targets were spotted on reciprocate heading, the A/C made a left hook and lined up for the kille; 1h25min This is the view from the A-10 perspective; Cheers Hans

Thanks gents for the kind words. Truth is that I just have too much time anymore to be fiddling with cnc trying to aqquire the skills to make good panels so I try and grab as much as I can from Ebay. @Alburg, the IFF most probably isn't an A-10 panel as the lenses on the edge lit lamps are red. Maybe from a helo or an F-4. And yes it takes countless hours looking for stuff on Ebay and in 99% of the time there isn't anything. Managed to get hands on a HARS panel, close but no cigar. It has a 3 position rotary instead of the toggle switch for DG-SLAVE. Not sure which aircraft it's from but it will do nicely. It cleaned out good, even the push to sync works with a pressure plate and re-centering springs. I'll post some pictures of it later ones it's fully wired up. I just need to make a small circuit with a +- voltage and a operational amplifier to get the Arduino output to be converted into +- voltages to drive the instrument. Is it moddeled in DCS? Not sure but i could be fun to get it working :-) Cheers Hans

Hmm well if it's any consolation then I can't setup a Mega as master.I tried to replicate your setup but I get the same result as you. TX is flashing but no reaction on the Slave. I even used a slave which I had been using in a test setup and that won't communicate either. I have also tried with two different Mega's as Master by to no success. I do have my original Mega as Master on my pit setup and that runs just perfectly. Rest assure, I will not be tampering with that. I'll try again another day. Cheers Hans

Really good looking work Sir :thumbup: Looking forward for more pictures on the process. Cheers Hans

Alright. I can't see anything wrong with the connections and you are right. On the Master you need to use RX1/TX1 for the first slave line as RX0/TX0 is used by the usb. I am a little surprised that you got onboard LED pin13 on on the master. Are you sure you didn't by mistake load the Slave sketch unto the master? I canøt see if mine are on as I have a prototype shield ontop of mine. Secondly when you power up SOCAT and connect it to the COM's port that the Mega Master is on, AND start DCS; Does you RX/TX led's on the Mega Master flicker to indicate communication from DCS? Ps. the resistors you have on should be removed. They are already on the MAX485 boards you are using hence the reason Ian stated somewhere we should be using these. That being said it should work with the boards. My very first sketch was with these. Cheers Hans

Hi Sven, Can you upload a picture of the connections you have made on both boards? Cheers Hans

Sorry John lack of inforrmation. The KY-58 encryption has been moddeled by UniversRadio for some time but the IFF is just recently been implemented UR/LotAtc (typo on my part, sorry); https://www.lotatc.com/documentation/transponder.html http://tacnoworld.fr/universradio-transponder/ A few from our ATC squadron has been testing it out with good results. For A/C like the A-10C the code is being taking from the transponder inside the aircraft. Cheers Hans

My bad. Misread the code. but looks like you're missing a pin number for the fuel lever. Try a simple setup in the beginning, e.g. define pin 13 on the Mega Slave as Caution light and check that the onboard LED lights up when you have a master caution Cheers Hans