-
SYSTEM SEARCH
System Scanners Online:
Username: Guest
>> System Scan?
>> The Universe >
Incoming Message:
Due to system limitations searching with words of 3 or less characters will not return results. For instance; Doctor Who. This will not return results as the system is trying to search for both Doctor AND Who in which Who will not be found as it's a 3 character word. To find Doctor Who; you'd search for either Doctor or "Doctor Who".
Search Tips:
For specific searches; enclose your search with quotes. Example: "Doctor Who" or "Addams Family".
Search the Community
Showing results for tags 'pinmos'.
Found 1 result
-
Hey guys, having an issue where I can't get DOF and MX LEDS working properly, the problem has slightly different behavior depending on the table so I'll try to keep it brief: I have DOF setup and working in VPX 32-bit, confirmed this by launching a B2S table, right click the backglass and making sure DOF plugin is active with no errors on America's Most Haunted BIGUS MOD 2.0. WEMOS seems to work fine before a table is launched, blue blinking light and the RGB test button works fine. On launching Leprechaun King WEMOS seems to lock up and become unresponsive, blue blinking light on it turns off and only one LED on one of my Leg Protector LED arrays turns on and stays on. On launching AMH all LEDs flash and then I get similar leg LED behavior to Leprechaun King but the WEMOS status light stays on solid blue, no blinking. I have attached log files for each of these cases. The LK one has some exceptions regarding failure to put the COM port into command mode, the AMH log doesn't show any errors. Things I have tried: Full reinstall of DOF 32-bit, reflashed WEMOS, uninstalled and reinstalled drivers for the WEMOS and the CH341 driver(per Arnoz instructions on the product page, I saw that another user posted quite recently with a similar or possibly the same issue), checked the registry to make sure the 64-bit .dll wasn't still registered(I tried to do the 64-bit upgrade before confirming DOF was working previously so uninstalled and started again). Any help would be appreciated as I've spent a couple evenings trying to resolve this with no luck. Thinking it's possibly a config issue but I'm out of ideas atm. lepKingDirectOutput.logAMHDirectOutput.log
