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

SeeedStudio Grove 125khz RFID reader Wiegand protocol #9673

Closed
dbvcode opened this issue Oct 30, 2020 · 6 comments
Closed

SeeedStudio Grove 125khz RFID reader Wiegand protocol #9673

dbvcode opened this issue Oct 30, 2020 · 6 comments
Labels
duplicated Result - Duplicated Issue feature request (devs?) Action - awaiting response from developers stale Action - Issue left behind - Used by the BOT to call for attention

Comments

@dbvcode
Copy link

dbvcode commented Oct 30, 2020

Have you looked for this feature in other issues and in the docs?
Yes, but only a long closed issue.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.

The problem is RDM6300 like readers seem to output fake data on the serial TX. See issue #9522

Describe the solution you'd like
A clear and concise description of what you want to happen.

SeeedStudio Grove 125khz readers also offer Wiegand communication by switching a jumper.
They have a wiki page with details about the readers.
And also in the page you can find Arduino sample code for the wiegand interface.
It's a matter of tasmotizing the code.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

No alternatives

Additional context
Add any other context or screenshots about the feature request here.

SeeedStudio Grove 125khz is superior to the RDM6300 and even if they output the same data on the serial, these readers pick up the cards from greater distance and don't miss tags.

(Please, remember to close the issue when the problem has been addressed)

@arendst
Copy link
Owner

arendst commented Oct 30, 2020

To rule out useless work being done I suggest you start to use the default Wiegand arduino code provided by seeedstudio on their devices and see if no fake data pops up.

I don't expect this will solve the fake issue as the serial fake data was valid data with a valid header and a valid tail. I would expect to see the same using the wiegand interface.

I guess there is a reason why there is different kinds of RFID hardware ;-)

@dbvcode
Copy link
Author

dbvcode commented Oct 30, 2020

I'll close the issue as I need an Arduino for that. When I have one, I'll post my findings..

@dbvcode dbvcode closed this as completed Oct 30, 2020
@ascillato2 ascillato2 added troubleshooting Type - Troubleshooting feature request (devs?) Action - awaiting response from developers and removed troubleshooting Type - Troubleshooting labels Oct 31, 2020
@ascillato2 ascillato2 reopened this Nov 6, 2020
@ascillato2
Copy link
Collaborator

ascillato2 commented Nov 6, 2020

Reopening as requested by other users.

Just for reference:

@ascillato2 ascillato2 added the duplicated Result - Duplicated Issue label Nov 6, 2020
@dbvcode
Copy link
Author

dbvcode commented Nov 6, 2020

I'll close the issue as I need an Arduino for that. When I have one, I'll post my findings..

My Arduino is still on it's way...

@github-actions
Copy link

github-actions bot commented Dec 5, 2020

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Action - Issue left behind - Used by the BOT to call for attention label Dec 5, 2020
@github-actions
Copy link

This issue was automatically closed because of being stale. Feel free to open a new one if you still experience this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicated Result - Duplicated Issue feature request (devs?) Action - awaiting response from developers stale Action - Issue left behind - Used by the BOT to call for attention
Projects
None yet
Development

No branches or pull requests

3 participants