Getting NExT to read at work

[Pilgrimsmaster]

@Absolutezero91

But I know the badge transmits on LF cause the LF commands are the only ones I’ve used to see my badge in the PM3.

There is a flaw in your logic buddy.
Just because you don’t look for something doesn’t mean it is not there.
Both the reader AND card COULD be both LF and HF, but you need to look to confirm.

it’s like Schrödinger’s Frequency

hf search

also, if you have a bright flashlight behind your card, my guess is you MAY see a circular antenna in the centre and another antenna running the perimeter.

A SIMILAR appearance to this

realistically it will look more like this

In saying that.

@Absolutezero91

I was able to write the ID to my NExT using lf hid clone and copying the ID I scanned from the badge.

@Absolutezero91

I then did another lf search and scanned the NExT, then my work badge again, and all the numbers sent over matched, with the exception of my work badge showing as an em chip and the NExT showing unable to ID the chip.

So you initially read your work card as HID
Then when you checked later it is saying EM

We probably want to also bottom out this anomaly.

Ideally we want you work to be using LF because it is much easier to play nice with.

@Absolutezero91

• New chip with rewritable UID for HF. (Magic chip?)
• Have my employer add the UID on my implant to their system.
• Very slim chance the reader isn’t looking at the UID, and maybe looking for something that can be written to my NExT? Datasheet doesn’t say anything about NTAG so I doubt it. It just calls out the ISO14443A

I would say you are in the ball park here, but there could be a couple of hiccups.

• New chip with rewritable UID for HF. (Magic chip?)
  Well, sorta, kinda, maybee, it depends

• Have my employer add the UID on my implant to their system
  Well, sorta, kinda, maybee, it depends

• Very slim chance the reader isn’t looking at the UID, and maybe looking for something that can be written to my NExT?
  Well, sorta, kinda, maybee, it depends

Let’s see how your further testing goes before diving deeper into those, but you are on the right track.

Do you have any test cards?
T5577 ones? Write to those for your testing, when / if it works, then we will have an answer, basically we are eliminating the implant from the equation ( Freshly installed and reduced read range etc. )

Can you also read your card with TagInfo and see if you get a succesful read.
If so, how may byte UID?

00:00:00:00 = 4
00:00:00:00:00:00:00 = 7