senseless Posted February 8, 2017 Share Posted February 8, 2017 every now and then I receive a pop-up when starting a visual pinball game that the firmware is not supported and the pin2dmd does not respond anymore. Only option is a reboot or a device reboot via the pin2dmd tool. Does anyone has an idea why this happens? It is a bit annoying. I'm running firmware 2.36 and the pin2dmd key is on the sd card and also in then pin2dmd tool directory. Thanks for the help :). Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted February 8, 2017 Content Provider Share Posted February 8, 2017 Sound like you have a communication problem on USB and the driver is not getting a response from the device in time. Maybe a other device is blocking the bus. Link to comment Share on other sites More sharing options...
Content Provider UncleSash Posted February 10, 2017 Content Provider Share Posted February 10, 2017 I had the same message today. I tried something to test dumo files and just started a test table in the vpinmame setup. The name was: Taxi (P-5). I just updated the "dmddevice.dll" in the VPinMame folder and now is it running, The dll file is dated with: 12-23-2016 05:47 may be that helps. Edit: I have updated to VPinMamr beta 2.9, runs like a charm (also updated the dll files) Link to comment Share on other sites More sharing options...
senseless Posted February 11, 2017 Author Share Posted February 11, 2017 Thanks, I will try the new 2.9b and see if it disappears :). I don't think it's instability of the USB otherwise it would also happen randomly during gameplay which does not happen. Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted February 11, 2017 Content Provider Share Posted February 11, 2017 3 hours ago, senseless said: Thanks, I will try the new 2.9b and see if it disappears :). I don't think it's instability of the USB otherwise it would also happen randomly during gameplay which does not happen. Not true ! There is no data traffic from pin2dmd to the pc during gameplay and the firmware version is only checked during startup. Link to comment Share on other sites More sharing options...
senseless Posted February 13, 2017 Author Share Posted February 13, 2017 your were right lucky1, it was instability of the usb device. Issue is solved by giving the pin2dmd device dedicated usb connections in stead via an usb hub, Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted February 13, 2017 Content Provider Share Posted February 13, 2017 Thanks for verifying, I will increase the timeout a little bit in the next version just to play it safe. Link to comment Share on other sites More sharing options...
Vanlon Posted January 13, 2018 Share Posted January 13, 2018 I get this error everytime my PC comes out of sleep mode. If I do a reboot it's fine. If I exit out of the game switch USB ports and fire the table back up it's fine. One the latest 10.4 AIO installer. Link to comment Share on other sites More sharing options...
Vanlon Posted February 15, 2018 Share Posted February 15, 2018 Still can't make sense of this. Updated WINUSB, reflashed the PIN2DMD, made sure the dmddevice.dll was out of the latest master file, cord is plugged directly into the motherboard. Every time the PC wakes up I get this error, in VPX, PinballX, DMDExt. Not sure which way to turn next. Link to comment Share on other sites More sharing options...
Rappelbox Posted February 15, 2018 Share Posted February 15, 2018 Do you have usb power turned on when pc is in sleep mode? Link to comment Share on other sites More sharing options...
Vanlon Posted February 16, 2018 Share Posted February 16, 2018 I've tried it both ways, no luck. Running Colorprism 2.54, libusb-win32 1.2.6.0. What program is calling the error. Maybe I can narrow it down that way. Link to comment Share on other sites More sharing options...
Content Provider lucky1 Posted February 16, 2018 Content Provider Share Posted February 16, 2018 This error message is generated by dmddevice.dll which does not get a response from pin2dmd. Link to comment Share on other sites More sharing options...
Vanlon Posted February 17, 2018 Share Posted February 17, 2018 Not sure if it's a BIOS thing, seems weird that restarting the device would make it visible. Can't see any change in the device state before or after restarting it. Anyway, wasted enough time on it so I created a work around. I used AHK to run Windows Devcon.exe to restart the USB device. Made it PBX's startup program. Here's the AHK script in case anyone runs into a similar hair pulling situation: devconexe_Path=c:\Scripts if not A_IsAdmin { Run *RunAs %devconexe_Path%\devcon.exe restart *YOUR PIN2DMD USB HARDWARE ID, CAN BE PARTIAL* ExitApp } The *RunAs command in the script runs Devcon.exe as admisistrator. Also get Devcon.exe here otherwise you will download 1GB to get a 80kb file. Suppose you could get taskmanager to run it on wakeup too instead of PBX. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.