search

Nelfe80 / RetroBat-Marquee-Manager

Dynamic Marquee Display Tool for RetroBat Arcade Systems: A Python-based solution for automatically updating secondary screen marquees in response to game and system selections.
9 stars 3 forks source link

ZeDMDHD isn't supported? #6

Closed riyadchowdhury closed 3 weeks ago

riyadchowdhury commented 3 weeks ago

Hi, I just built a ZeDMD-HD using 2 128x64 panels, so my device is 256x64.

I am able to run zedmd_test.exe from https://github.com/PPUC/libzedmd/releases/tag/v0.7.4 so I think my device is working correctly. It finds the device on COM3

When running start.bat my DMD screen just flashes white, when running dmd.exe it seems like it doesn't like the response it gets. Here is the output from dmd.exe

C:\RetroBat\plugins\MarqueeManager>dmd\dmd.exe
Loaded DLL: dmd\zedmd.dll
Functions exported by the DLL:
ZeDMD_ClearScreen
ZeDMD_Close
ZeDMD_DisableDebug
ZeDMD_DisablePreDownscaling
ZeDMD_DisablePreUpscaling
ZeDMD_DisableUpscaling
ZeDMD_EnableDebug
ZeDMD_EnablePreDownscaling
ZeDMD_EnablePreUpscaling
ZeDMD_EnableUpscaling
ZeDMD_EnforceStreaming
ZeDMD_GetDefaultPalette
ZeDMD_GetInstance
ZeDMD_IgnoreDevice
ZeDMD_LedTest
ZeDMD_Open
ZeDMD_OpenWiFi
ZeDMD_RenderColoredGray6
ZeDMD_RenderGray2
ZeDMD_RenderGray4
ZeDMD_RenderRgb24
ZeDMD_RenderRgb24EncodedAs565
ZeDMD_SaveSettings
ZeDMD_SetBrightness
ZeDMD_SetDefaultPalette
ZeDMD_SetDevice
ZeDMD_SetFrameSize
ZeDMD_SetPalette
ZeDMD_SetRGBOrder
ZeDMD_SetWiFiPassword
ZeDMD_SetWiFiPort
ZeDMD_SetWiFiSSID
Failed to enable debug mode.
Starting server...
Testing COM3 at 9600 baud...
Connected to COM3 at 9600 baud.
Response: b'\xef\xca'
Handshake failed. Response: b'\xef\xca'
Testing COM3 at 921600 baud...
Connected to COM3 at 921600 baud.
Response: b'\x00\x80\x00\x00\x00\x80\x00\x00\x80\x00\x00\x80\x00\x80\x80\x00\x00\x80\x00\x80'
Handshake failed. Response: b'\x00\x80\x00\x00\x00\x80\x00\x00\x80\x00\x00\x80\x00\x80\x80\x00\x00\x80\x00\x80'
Testing COM3 at 460800 baud...
Connected to COM3 at 460800 baud.
Response: b'\x80\x80\x80\x80x\x80\x00\x80\x80\x80\x80\x00\x80x\x80x\x80\x00\x80x'
Handshake failed. Response: b'\x80\x80\x80\x80x\x80\x00\x80\x80\x80\x80\x00\x80x\x80x\x80\x00\x80x'
Testing COM3 at 230400 baud...
Connected to COM3 at 230400 baud.
Response: b'f\x06~\x1e\x06\x18\x86f~\xe0\x9e\x00\x18x\x86\x18\x18x\x00\x98'
Handshake failed. Response: b'f\x06~\x1e\x06\x18\x86f~\xe0\x9e\x00\x18x\x86\x18\x18x\x00\x98'
Testing COM3 at 115200 baud...
Connected to COM3 at 115200 baud.
Response: b'ets Jul 29 2019 12:2'
Handshake failed. Response: b'ets Jul 29 2019 12:2'
Testing COM3 at 57600 baud...
Connected to COM3 at 57600 baud.
Response: b'H\xc8\x881)ka)i\xa9\x0c\xf7\xa5\x08\xc0\x00\x8cl0\xe2'
Handshake failed. Response: b'H\xc8\x881)ka)i\xa9\x0c\xf7\xa5\x08\xc0\x00\x8cl0\xe2'
Testing COM3 at 38400 baud...
Connected to COM3 at 38400 baud.
Response: b'<adfw\x9eEsM\x12W\x96Fbpb\x1f`df'
Handshake failed. Response: b'<adfw\x9eEsM\x12W\x96Fbpb\x1f`df'
Testing COM3 at 19200 baud...
Connected to COM3 at 19200 baud.
Response: b'J\x18X\x08\xf2\xf1'
Handshake failed. Response: b'J\x18X\x08\xf2\xf1'

I am wondering if dmd.exe isn't configured to get a 256x64 resolution response.

riyadchowdhury commented 3 weeks ago

I got it working by using a different esp32 board.