Error sending data to device: Win32Error:GetOverlappedResult Ep 0x0131
Hi,
While pinball fx doesn't show up right on pin2dmd I decided to stick with pinball fx 3.
Sometimes it works 20 minutes, sometimes only 3 But every time minutes I get an error :
Error sending data to device: Win32Error:GetOverlappedResult Ep 0x0131
I've tried every freezy dmdext version there is, all give the same error.
Any help would be appreciated Thanks
Hi, thanks for the report. As always, it's very hard to debug without a log. Would you mind posting one, the next time the problem arrives? Instructions how to produce a log are here.
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd" autoReload="true" throwExceptions="false" internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log" >
<targets>
<!--
add your targets here
See https://github.com/nlog/NLog/wiki/Targets for possible targets.
See https://github.com/nlog/NLog/wiki/Layout-Renderers for the possible layout renderers.
-->
<target name="console" xsi:type="ColoredConsole" useDefaultRowHighlightingRules="false"
layout="${pad:padding=4:inner=[${threadid}]} ${date} ${pad:padding=5:inner=${level:uppercase=true}} | ${message} ${exception:format=ToString}">
<highlight-row condition="level == LogLevel.Trace" foregroundColor="DarkGray" />
<highlight-row condition="level == LogLevel.Debug" foregroundColor="DarkGray" />
<highlight-row condition="level == LogLevel.Info" foregroundColor="Gray" />
<highlight-row condition="level == LogLevel.Warn" foregroundColor="Yellow" />
<highlight-row condition="level == LogLevel.Error" foregroundColor="Red" />
<highlight-row condition="level == LogLevel.Fatal" foregroundColor="Magenta" />
</target>
</targets>
<rules>
<logger name="*" minlevel="Trace" writeTo="console" />
</rules>
C:\Visual Pinball\VPinMAME\DMDext>dmdext mirror --source=pinballfx3 --destination=pin2dmd --no-virtual [1] 2024/10/28 09:43:01.380 INFO | Launching console tool v1.10.2 [1] 2024/10/28 09:43:01.461 INFO | Found PIN2DMD device. [1] 2024/10/28 09:43:01.461 DEBUG | Manufacturer: PIN2DMD [1] 2024/10/28 09:43:01.461 DEBUG | Product: PIN2DMD [1] 2024/10/28 09:43:01.461 DEBUG | Serial: 00000000050C [1] 2024/10/28 09:43:01.461 DEBUG | Language ID: 1033 [1] 2024/10/28 09:43:01.461 INFO | Added PIN2DMD renderer. [1] 2024/10/28 09:43:01.478 WARN | Device PIN2DMDXL is not available. [1] 2024/10/28 09:43:01.478 WARN | Device PIN2DMDHD is not available. [1] 2024/10/28 09:43:01.527 INFO | Setting up Render Graph for 1 destination(s) [1] 2024/10/28 09:43:01.527 INFO | Connecting Pinball FX3 to PIN2DMD (ColoredGray2 => ColoredGray2) [1] 2024/10/28 09:43:01.538 INFO | Waiting for Pinball FX3 process to start... [1] 2024/10/28 09:43:01.552 INFO | Press CTRL+C to close. [3] 2024/10/28 09:43:11.580 INFO | Process found, starting capturing... [3] 2024/10/28 09:43:11.581 INFO | Reading DMD data from Pinball FX3's memory at 25 fps... [3] 2024/10/28 09:43:11.581 INFO | Frames coming in from Pinball FX3. [9] 2024/10/28 10:18:00.840 ERROR | Error sending data to device: Win32Error:GetOverlappedResult Ep 0x01 31: [8] 2024/10/28 10:18:02.893 ERROR | Error sending data to device: Win32Error:GetOverlappedResult Ep 0x01 31: [8] 2024/10/28 10:18:04.906 ERROR | Error sending data to device: Win32Error:GetOverlappedResult Ep 0x01 31:
Thanks. That's weird indeed and has something to do with the communication between dmdext and the PIN2DMD.
I have not much clue how to debug this, unfortunately. Did you try plugging the display into a different USB port?
I've added something that might help to a new branch, could you test it and check if that works better for you?
https://ci.appveyor.com/project/freezy/dmd-extensions/builds/50951616
Hi,
First of all thank you for your work. Unfortunately i really have no clue where to download the test version 2.3.1. Or do i have to copy/paste the code somewhere ?
I did plug the pin2dmd in all different USB ports with no effect. I get the overlap error on different machines too.
On my 12700k/RTX3080, but also on my ancient 2500k/RTX1060.
Op vr 8 nov 2024 om 17:57 schreef freezy @.***>:
Thanks. That's weird indeed and has something to do with the communication between dmdext and the PIN2DMD.
I have not much clue how to debug this, unfortunately. Did you try plugging the display into a different USB port?
I've added something that might help to a new branch, could you test it and check if that works better for you?
https://ci.appveyor.com/project/freezy/dmd-extensions/builds/50951616
— Reply to this email directly, view it on GitHub https://github.com/freezy/dmd-extensions/issues/501#issuecomment-2465279283, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMJQYNCMSUNF6OLTM4KYYRLZ7TURDAVCNFSM6AAAAABQOQUJV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVGI3TSMRYGM . You are receiving this because you authored the thread.Message ID: @.***>
Click on the platform of choice and under "Artifacts" you'll have the binaries to test.
Unfortunatly the problem persists :(
Op za 9 nov 2024 om 21:42 schreef freezy @.***>:
Click on the platform of choice and under "Artifacts" you'll have the binaries to test.
— Reply to this email directly, view it on GitHub https://github.com/freezy/dmd-extensions/issues/501#issuecomment-2466453926, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMJQYNAGAVN2QLARSLQXOFLZ7ZXVDAVCNFSM6AAAAABQOQUJV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGQ2TGOJSGY . You are receiving this because you authored the thread.Message ID: @.***>