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

Chameleon Lite / DevKit - LF emulation not working #146

Open
panayotoff opened this issue Sep 11, 2023 · 4 comments
Open

Chameleon Lite / DevKit - LF emulation not working #146

panayotoff opened this issue Sep 11, 2023 · 4 comments
Labels
bug Something isn't working specific Affects specific device(s)/user(s), not all devices

Comments

@panayotoff
Copy link

panayotoff commented Sep 11, 2023

Hi all,
I've received my Chamaleon Lite and Devkit from the Indiegogo campaign. I have troubles with emulating the LF on Lite and DevKit. However, with the same FW and same card on same slot Ultra is emulating LF fine.

Describe the bug

I've tried the following:

  • Flash latest FW ( both from the GUI and CLI )
  • Set only LF on slot, setting LF and HF on the same slot
  • Waking up chameleons beforehand
  • Trying different distances.

Readers

  • nothing on Flipper0
  • nothing on my home card-access reader
  • nothing on PM3 when I try general lf search . If however I'm more specific and I try lf em 410x reader -@ on PM3 I would get the proper ID

Chameleon

When presented near LF reader, the slot is in LF mode ( the slot light is blue ) and the side light on LIte and central light on DevKit shines white. If the slots have two cards on them ( LF and HF ), when presented to HF they shine green and when presented to LF they shine blue, but the LF card is not recognised by the reader. Again same card, same slot, same setup, same firmware on Ultra works.

To Reproduce
Steps to reproduce the behavior.

  1. Install latest FW ( and any previous for this matter )
  2. Read LF EM410x card with Ultra ( reader mode is working )
  3. Copy the EM410x card to a slot ( either GUI or CLI )
  4. Go to this slot
  5. present to reader

Expected behavior
Reader is able to read the card ( Tiny and DevKit )

Screenshots

Additional context

@xianglin1998
Copy link
Contributor

  1. Have you attempted to execute the hw factory_reset command after update to the latest firmware.(Updating firmware may damage simulated data)
  2. Is the type of simulation card correctly set in the card slot? using cmd: hw slot type
  3. Did you see the blue light of the chameleon when reading the card? If not, it may be that your card slot selection is incorrect. Please select the correct card slot for your uploaded ID.

@xianglin1998
Copy link
Contributor

From the factory firmware to the latest firmware, the low-frequency simulation has been modified many times. If your chameleon cannot correctly read the card number even when the blue light is on during card reading, please try using the factory firmware test.

@panayotoff
Copy link
Author

panayotoff commented Sep 12, 2023

Thanks, I did a upgrade to latest (4d8fb87) and did a factory reset, which has not fixed the issue. After factory resetting, I can not read with my PM3 or F0 slots 1 or 3 in LF ( HF is readable thought ). The DevKit is able to read LF cards, but not emulate them back.

I've set the slot type to LF ( hw slot type -t 1 -s 1 for first slot, only EM410X there, saved to flash ) and still does not work.

When I read the card I don't see blue light from the non-slot LEDs. The slots itself are blue if I present them to LF reader and green if presented to HF reader ( HF is working in all devices )
On the Tiny, I can see the light next to the USB-C port ( first side LED ). }
On the DevKit, the central LED ( between the version number and chameleon dev edition print ) lights up.
But both light in white, not blue.

@xnfra
Copy link

xnfra commented Sep 16, 2023

I am having a similar problem simply getting the chameleon to read lf t5577 cards. Does low frequency even work? Is my device defective?

@doegox doegox added bug Something isn't working specific Affects specific device(s)/user(s), not all devices labels Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working specific Affects specific device(s)/user(s), not all devices
Projects
None yet
Development

No branches or pull requests

4 participants