-
Notifications
You must be signed in to change notification settings - Fork 166
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
fix-LF-emulation #221
base: main
Are you sure you want to change the base?
fix-LF-emulation #221
Conversation
You are welcome to add an entry to the CHANGELOG.md as well |
Built artifacts for commit 6145f5cFirmwareClient |
Havent tested it on a real reader yet, but it definitely works with flipper0! So this is a progress, many thanks! |
@alexbilevskiy Thanks a lot, hope it would be useful. Did you have any related problems before? |
LF emulation didn't work at all on my CU |
Has anyone tested and provided more feedback on the test results? |
@Dmytro02 in discord REALLY stressed the point that this needs to be reworked in his opinion, so maybe merging as is isnt the best idea? |
It is not. It is just proof of concept. Maybe, if possible, we can rework this part with @doegox (Philippe Teuwen), as I can see he is the main author of this functionality. And together, I believe, we will properly fix the issue. |
worked on the bootleg ones |
Hello @mitmarcus , |
By bootleg I meant a chamele0n Sadly when I purchased, I got this one instead of the original. However, EM4100X worked countless times without problems on at least 3 separate types of readers ¯\_(ツ)_/¯ |
The original EM4100 tag continuously sends its ID.
The root problem, in my point of view, was that CU started to "feel" the field too far to be able to modulate it deep enough,
and 3 times (LF_125KHZ_BROADCAST_MAX) of repeating takes only about 100ms, CU is still not close enough to the reader.
That is why the emulation worked only if the CU moved past the reader quickly (fly by).