Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different 11x40 Device? #22

Open
gosniffme opened this issue Oct 31, 2019 · 7 comments
Open

Different 11x40 Device? #22

gosniffme opened this issue Oct 31, 2019 · 7 comments

Comments

@gosniffme
Copy link

I got a generic 11x40 LED badge from China (white)
It identifies itself as 0483:5750 (MM32 custom HID) instead of 0416:5020.
Obviously, led-badge-11x44.py won't run correctly, because the IDs do not match.
Anyone else run into this?

Came with a baidu cloud link to download their software "MiniLED9.92" if it helps
https://pan.baidu.com/s/1bp29yaj
The box claims it's a B1248, but I don't think that's correct, as this is a 11x40 LED badge.

@CozmoCyke
Copy link

Hello @gosniffme ,

Try to change the values in led-badge-11x44.py

Find these lines :
if have_pyhidapi:
devinfo = pyhidapi.hid_enumerate(0x0416, 0x5020)
#dev = pyhidapi.hid_open(0x0416, 0x5020)
else:
dev = usb.core.find(idVendor=0x0416, idProduct=0x5020)

And replace idVendor by 0x0483
idProduct by 0x5750

@tpakula-fender
Copy link

Simply changing the vendor and product IDs won't work - the device will be detected, but the proto_header sent at the beginning of the transmit buffer seems to be different for these two devices.

@ragesaq
Copy link

ragesaq commented Mar 8, 2020

I've tried two different devices off amazon trying to find one of these programmable ones with 0x0416 0x5020 and they were both 0x0483 0x5750 despite different chassis, these seem to be the only ones available right now.
Any chance of getting this software to work with them?

@fluxtransistor
Copy link

fluxtransistor commented Apr 24, 2020

I have an unsupported 0x0483 0x5750 11x40 badge as well. I have tried find+replacing 0x0416 and 0x5020 in the python file with 0x0483 and 0x5750, but instead of displaying a message the badge blinks and then goes back to the message that was programmed before. Could I modify the proto_header?

@cslaviero
Copy link

Same issue here. Maybe this link could help implementing support to this device?

https://cat-in-136.github.io/2020/07/b1248-led-name-badge-protocol-reverse-engineering.html

I’m not an expert in reverse engineering, so I have no ideia what I could do to make it work…

@fluxtransistor
Copy link

Wish I could help somehow, but my 1248 badge died a few months ago when the flimsy microUSB port broke off.

@redongh
Copy link

redongh commented Aug 13, 2021

same here. sadly i found this issue only after spending quite some time to figure out the correct IDs and how/where to change them.

i tried to map some of the data provided in the link provided by @cslaviero to the code of this project and found that either i don't understand how this projects code is working or the protocol of the badge with VID/PID of 0483/5750 is quite different to the one used here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants