-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
125kHz Card Not Reading - Images and Raw Files Attached #3646
Comments
Yep this one is RFID, payload ASK coded, should be totally doable. |
The reading using flipper-raw-rfid from .ask looks similar to #3336 Also long pulses are around 330 mu sec given by Flipper Lab's pulse plotter. Close enough to RF/40 clock which would give 320 mu sec. I'm not sure if inverting is intentional or if it is my mistake in analyzing the signal. If it is intended to be like the second sequence, then my PR #3697 should enable support for this card as well. @davewilliamstx : do you mind taking a photo of the reader? It might help confirming the brand and protocol of this card. |
Sure thing, it’s pretty beat up - hope it helps.
…On Sat, Jun 8, 2024 at 11:18 PM Zinong Li ***@***.***> wrote:
The reading from .ask looks similar to #3336
<#3336>
100000000011010010111111111111111111111011110011011100111011000011011010010111111111111111111111
Reverting it and adding spacers gives Securakey 26-bit format
preamble ??bitlen reserved EPf fffffffc cccccccc cccccccOP CS1 CS2
0111111111 0 01011010 0 00000000 0 00000000 0 01000011 0 01000110 0
01001111 0 01001011 0 10000000 0 00000000 0 0000
f deontes facility code and c denotes card id. In this case card id is
1010001100100111 which is equal to 41767 in decimal. The same card number
as printed on OP's card.
Also long pulses are around 330 mu sec given by Flipper Lab's pulse
plotter. Close enough to Securaket's RF/40 clock which would give 320 mu
sec.
I'm not sure if reverting is intentional or is it my mistake in analyzing
the signal. If it is intended to be like the second sequence, then my PR
#3697 <#3697>
should enable support for this card as well.
@davewilliamstx <https://github.com/davewilliamstx> : do you mind taking
a photo of the reader? It might help confirming the brand and protocol of
this card.
—
Reply to this email directly, view it on GitHub
<#3646 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3Q4DJAS4F5MEXWTOAZSATZGPJRZAVCNFSM6AAAAABHTIC2LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWGMYDSMZWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks! I'm not sure if the image got through from email replies to the comment section. Would you mind upload it on github directly? |
Ok I'm pretty sure that's a securakey radio key reader. Should be supported once my pull request above passes through, fingers crossed. In the meantime, if you toggle on Debug Mode, you should be able to read raw and emulate raw. I've heard of successes with securakey raw emulations. Maybe it works in your case too. |
Description of the feature you're suggesting.
Have tried two different versions of this card, not reading on Flipper. I'm not sure on source of the cards, our HOA uses them.
Unknown RFID Card.zip
Anything else?
No response
The text was updated successfully, but these errors were encountered: