Monkstable Posted July 2, 2017 Posted July 2, 2017 (edited) Hola.. I successfully messed around with DCS-BIOS on release, but never had the time back then to do anything serious with it. Now i've got the time and a room full of panel parts, I'm having a hard time getting past initial setup (and feeling like an idiot :music_whistling:). I'm using, * Win10 build 10.0.15063, firewall off * UNO with IDE 1.8.3 and working blink sketch * DCS World 2.1.1.6837 / A-10C 2.1.1 * DCS-BIOS 0.5.5 with library 0.2.11, setup as per the docs * MasterCaution example sketch supplied with DCS-BIOS I see continuous output in the cmd window when I run connect-serial-port.cmd with DCSW running, and the RX light on the UNO suggests it's receiving continuous data. However, I get no activity from the onboard LED/13 when using the MasterCaution example sketch & triggering it in-game. The Control Reference Live Preview does work, using that I can toggle stuff in Chrome and see it reflected in-game (and vice versa). I have switched connect-serial-port.cmd to TCP with no success (same symptoms, UNO appears to be receiving data, but not actioning it). There are no relevant errors in dcs.log (no lua export or path errors), but dcs-bios.log fills with "value -116.000000 is too small for address 1028 mask 63". I've also tried a second UNO on a different COM port with no success. Before I nuke the PC from orbit and start over, does anyone have any suggestions as to what's up? Edited July 2, 2017 by Monkstable
Monkstable Posted July 2, 2017 Author Posted July 2, 2017 Solved - now working with socat launched from an Administrative command prompt (caught a random socat timeout complaining about a permission error).
THeCeltic Posted July 11, 2017 Posted July 11, 2017 How did you do it exactly? I have the same problem. Thx THeCeltic
Recommended Posts