-
Posts
1775 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by Hansolo
-
Super Sloth Six, Hah I almost could decipher it myself. Sinced it worked I hadn't touched it for over almost year. Please find new pinout updated with Arduino pins. Be aware that the key press is running over RS485. You can of cause convert the sketch into a USB version. Let me know if your son runs into troubles and I'll try my best to assist. Have a great weekend. Cheers Solo C-130 CDU pinout v. 2.pdf
-
Roger. Let me find my notes when I get back home and post them here. Cheers Solo
-
Hello, Have your son looked here; https://forums.eagle.ru/showpost.php?p=3236594&postcount=159 If that doesn't help give me a shout then I can look at it during the weekend. I am currently away. Cheers Solo
-
Hmm odd. Here is the link address; Cheers Solo
-
Probably they downgraded the limitation as the A/C got older. Cheers Solo
-
Hey turbodiesel, When it comes to switches (inputs to DCS from Arduino) you can test it whithout running DCS. Just start SOCAT, flip the switch and you will get the info: With regard to LED's then these are output from DCS to the Arduino. Thus is DCS isn't running you'll get no action. Cheers Solo
-
Ah in that way. Well you will enjoy the Saved Games location when you update DCS as modifications in the main install location will be overriden during update. Glad you got it to work. Cheers Solo
-
Interesting. Where did you put it? Glad you got it working Cheers Solo
-
Very nice CDU build you have gotten there sir. I seem to recall from the C-130 CDU I have got that they have placed a small piece of foam ring around each button, which then seals to prevent bleed light. Looking forward to seeing more progress on your pit sir. Cheers Solo
-
That sound like there is no communication with DCS. Once DCS is running (unpaused) the SOCAT should be filled with garble which is all the information from DCS through SOCAT. By garble means that you can't read it but the Arduino can. Check that your Export.lua has the following line; dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) If it does not then there is your problem. Export.lua is found in ..\Saved Games\DCS.openbeta\Scripts Secondly if you have both stable and Beta version on your PC make sure that you start the one which has above line in the Export.lua. Alternative make sure both Export.lua has the line :) Cheers Solo
-
Outstanding work sir. Very nice clean build. I can only pray that mine gets as clean but don't think it will. It must be absolutely awesome to set in it what that view. Well done sir. Cheers Hans
-
Many thanks for sharing romeokilo. Much appreciated sir. Happy New Year. Cheers Hans
-
Blue73, that is a very sweet solution sir. Thanks a lot for sharing. Happy New Year sir. Cheers Solo
-
What happens if you change to; DcsBios::LED masterCaution(0x1012, 0x0800, 13); This will use the onboard LED. Have you verified that the LED is connected correctly and not reversed? The error when running SOCAT is normal. Got this from another DCS-BIOS user on 476th Discord I haven't tried it myself yet though. Cheers Solo
-
It's being moved due to wind. It's not possible to center it in the A-10 Cheers Solo
-
You have to modify the file. The file is already used by DCS-BIOS so you just have to enable the filtrering. Alright it looks like I only changed one value in my setup, from 128 to 500; template <unsigned int pollInterval = 5, unsigned int hysteresis = 500, unsigned int ewma_divisor = 5> Cheers Solo
-
Hi snipes, The Potentiometer.h files is located where your libraries for Arduino IDE is located, e.i. ...\Arduino\libraries\dcs-bios-arduino-library-0.2.11\src\internal With regard the different examples this is how I see it; IRQSerial - Use this as default for USB connected panels DefaultSerial - Use this if IRQSerial doesn't work for you RS485Master - shall only be used when you want to assign a master controller for the RS485 protocol. This panel has to be a Mega 2560 which will be connected to DCS via SOCAT over USB. From this panel the communications to all other panels will be via RS485. This panel can ONLY be loaded with the RS485Master sketch as it is default. Thus you cannot connect a switch or led or anything to the panel RS485Slave - shall be used for the individual panels on the RS485 communication. These panels can be UNO/NANO/MEGA and possible also other Arduino or Arduino like boards. Cheers Solo
-
Hi, I can't explain why it worked in the first trial and not when you swapped +5V and GND. Are you absolutely sure that you didn't by mistake +5 or GND with the signal? The reason it is un-smooth might be that your potentiometer is not making slight litters. The easiest way of checking this is to run SOCAT without DCS and notice if you communications all the time from the potentiometer position. If you do then that is probably the reason because the communication gets flooded with information. I noticed similar here; https://forums.eagle.ru/showpost.php?p=3020643&postcount=127 IIRCC then Ian made the changes to the potentiometer.h file where you can adjust the filtering settings for potentiometer. I think I am still running my modified version and it works flawlessly for me. I haven't tried the encoders at all but there was a post from Ian regarding this. The encoder gives a certain number of pulses per revolution and you should be able to set the same in DCD-BIOS as per this; https://forums.eagle.ru/showpost.php?p=3156074&postcount=7 Hope this helps a bit. Cheers Solo
-
Outstanding work on that jettison button sir :thumbup: Cheers Solo
-
I got these MAX487 chips last time; https://www.mouser.dk/ProductDetail/700-MAX487CPA They are more expensive than off Ebay but I got a batch of bad chips which turned really hot. Decided that the fault tracing time vs 2 Euro was in favour of the 2 Euro's. To the best of my knowledge a Mega 2560 which is the newer model. They do run different communications chips for the USB connections ATmega vs CH340 but either works. I had at one point suspected that there was an issue with the CH340 but couldn't replicate issues; https://forums.eagle.ru/showpost.php?p=3397367&postcount=41 Cheers Hans
-
Correct. Ian staten that some time ago to another member. Cheers Solo
-
Never tired on 104th server but ours also run with integrity check and I have no problems connecting to 132nd server. Cheers Solo
-
Hi molevitch, First of all I can only recommend the RS485 for DCS-BIOS. I have been very happy with it. Secondly to answer you questions; 1. The Mega only gets the default DCS-BIOS Master sketch loaded. It cannot run anything else but being a Master. 2. The Slaves will have their individual code AND individual Slave number. What you want for hardware on your Slave units depends a bit on your preferences. You can run a Nano for just one panel or perhaps two panels. You can also run a Mega as a Slave and run as many panels as have IO (Input/Outputs) for. I run my system with just one Arduino per panel and for more advanced panels I just use a Mega to get enough inputs. Each of the slave units will IIRCC receive all commands from the Master. I.e. the radio will also receive all the date for flight telemetry but doesn't use it for anything. However each Slave unit will only return commands which it has been programmed for which is just the way you have already seen with the panels you have running on DCS-BIOS. The only difference is that instead of opening 3 times SOCAT for the 3 USB connected panel, you only open 1 SOCAT for the Master. 3. You can power the Master externally but it doesn't really matter since it need the USB to communicate with the PC and are therefore powered by USB. You can see a little more schematics over how I have done it here; https://forums.eagle.ru/showpost.php?p=3247704&postcount=171 But actually CraigS' video shows it really nicely and with more explanation. Well done @CraigS :thumbup:. Very informative YT Sir. Oh forgot to write. I added a link all my current Slave sketches running DCS-BIOS over RS485 Cheers Solo
-
Actually there is. It looks like you don't have to open the switch cover before activating the switch. I just did a quick test in the A-10C for Arm Ground Safety switch. It appears that if you 'just' flip the override switch then the cover automatically opens. When you flip the override switch back into safe then cover does stay up but if you can live with that then you don't have to make the feed back on the cover. Cheers Hans
-
Update to IFF panel functionallity Firstly I updated the A10C.lua with code from quick, so that GSS Rain/Joe Sim reported item no1 (Audio/Out/Light 3-position switch) is working; https://forums.eagle.ru/showpost.php?p=3583300&postcount=2 The missing feature of IFF Reply and Test lamp , item 2 & 3; https://forums.eagle.ru/showthread.php?t=189774 was fixed by adding following lines the end of DCS-BIOS's A10C.lua; defineIndicatorLight("IFF_REPLY_LAMP", 798, "IFF", "IFF REPLY LAMP Indicator") defineIndicatorLight("IFF_TEST_LAMP", 799, "IFF", "IFF TEST LAMP Indicator") Just before; BIOS.protocol.endModule() NOTE!! It is important to add the change to the end just before "BIOS.protocol.endModule()" as otherwise a lot of addresses within the DCS-BIOS control references will be changed and you need to update all your boards!!!! The changes are done in the JSON file when loading a mission. Adding these two lines will give correct function of IFF Reply and Test lamps when the Arduino code updated with following lines; //REPLY DcsBios::LED iffReplyLamp(0x11BC, 0x800, 13); //TEST DcsBios::LED iffTestLamp(0x11BC, 0x1000, 12); In this small video you may notice that pressing test of Reply and Test on panel does not affect DCS. This is because the lamp tests are hardwired and I did not find it useful to make a relay function in order to give it back to DCS. Link to updated A10C.lua; https://drive.google.com/open?id=10u98XT8yZqQdy6kBQ-R0ygNc9-4aM-qN Link to full Arduino code; https://drive.google.com/open?id=1BFYPCbJKKGopBkiOIJ5HfqgNFmTNIGLI The IFF update is slave no 20 Cheers Hans