Problem getting DOF and MX LEDS to work, Arnoz WEMOS + PINMOS

[Ph03nix89]

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

Edited November 17, 2024 by Ph03nix89

[Ph03nix89]

UPDATE:

 

TWO PROBLEMS RESOLVED, ONE NEW PROBLEM EMERGES

 

Tried again today and after a test of each table with the same results as above(resetting the WEMOS after each test) I ran the LK table again for gits and shiggles and it just suddenly started working. I haven't changed or done anything so I'm at a complete loss as to why it's no longer throwing exceptions.

 

I also figured out the one LED staying on was due to it being on the D4 output of the WEMOS with the Activity LED turned on in Tiny Tools when I flashed it. Reflashed with the checkbox off this time and that one LED stays off now like it's supposed to.

 

New problem is that when launching AMH it doesn't seem to be able to find a table config as no RomName is supplied, whereas LK seems to be able to figure it out:

 

AMH

2024.11.16 14:32:56.129    Warning: No table config file found. Will try to load config from LedControl file(s).
2024.11.16 14:32:56.129    Warning: Cant load config from directoutput.ini or ledcontrol.ini file(s) since no RomName was supplied. No ledcontrol config will be loaded.
2024.11.16 14:32:56.129    Table config loading finished: romname=, tablename=America's Most Haunted (Spooky Pinball 2014)_Bigus(MOD)2.0

 

LK

2024.11.16 14:00:05.724    Warning: No table config file found. Will try to load config from LedControl file(s).
2024.11.16 14:00:05.724    Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName leprechaun
2024.11.16 14:00:05.725    Loading LedControl file F:\DIRECTOUTPUT\directoutputconfig30.ini
2024.11.16 14:00:05.741    Min DOF Version is 0.8 for file directoutputconfig30.ini
2024.11.16 14:00:05.741    Resolving Tables Variables (F:\DIRECTOUTPUT\directoutputconfig30.ini)
2024.11.16 14:00:05.743    Resolving Global Variables (F:\DIRECTOUTPUT\directoutputconfig30.ini)
2024.11.16 14:00:07.280    1 directoutputconfig.ini or ledcontrol.ini files loaded.
2024.11.16 14:00:07.281    Config for RomName leprechaun exists in LedControl data. Updating cabinet and config.
2024.11.16 14:00:07.299    Table config loading finished: romname=leprechaun, tablename=Leprechaun King (Orbital 2020)

 

Thing is the entry for AMH exists in my directoutputconfig30.ini and I can only find one reference to the RomName in the table script(see below images) so I dunno how to fix this one. Any help would be much appreciated!

 

 

[Ph03nix89]

Ok so figured it out some more of the issue, turned out to be a mistake on my part when configuring DOF that I haven't seen mentioned anywhere else until I went back to the beginning and followed the mjr guide rather than video walkthroughs.

 

I hadn't told DOF that there was a Pinscape device in the MyAccount settings of the config tool. Lesson here is to just follow the mjr bible when setting up these things in future.

 

The WEMOS seems to lock up the first time running a table after being powered on but hitting the reset button on it and launching the table again solves the issue for the rest of the session. I'll do more testing to see why this is but I'm not too pushed on solving that issue right now.

 

I have everything else working now it's just AMH still not finding config files:

 

2024.11.17 18:33:41.775    Loading table config
2024.11.17 18:33:41.776    Warning: No table config file found. Will try to load config from LedControl file(s).
2024.11.17 18:33:41.776    Warning: Cant load config from directoutput.ini or ledcontrol.ini file(s) since no RomName was supplied. No ledcontrol config will be loaded.
2024.11.17 18:33:41.776    Table config loading finished: romname=, tablename=America's Most Haunted (Spooky Pinball 2014)_Bigus(MOD)2.0

Edited November 17, 2024 by Ph03nix89

[Ph03nix89]

I figured out the AMH issue, there's two lines of code that need to be commented out in the table script of the 2.0 version to get DOF working properly.

 

MX LEDs work fine in the 1.1 version of the table and the only code differences I could find(other than the listed upgrades between versions) were the 1.1 version has lines 24 and 25 commented out and the 2.0 version does not.

 

Not sure why this was done(possibly for testing, who knows) but reverting these two lines to the 1.1 version's code fixed MX LED functionality in the 2.0 table.

 

Haven't looked into the WEMOS locking up yet, will get around to it eventually...