One more "Which implant should I get and other dumb questions"

This. enginerd is right. The implant circuits:

  1. have very poor coupling with everything in the environment because of the shapes and sizes of the coils
  2. only interact with the magnetic component of the “near-field” (not electrical fields)
  3. are very precisely tuned

A difference of 100kHz from the target frequency can reduce the amount of power the LC tank circuit in the implants recieve from the field by half or more. Maybe if you placed a T5577 chip right up against a wire carrying more than 30A at 100-150kHz you might be able to fry it. You can certainly fry the LF xLEDs with less. You would have to work very hard at frying a HF implant though. Even the HF xLED. Even an NFCKill has to be right next to it.

1 Like

Thats great news, this mean we are pretty much safe from any interferences damaging the implants.

Dam … I didnt even knew those things existed …

On the injection/location side of things.
Is it OK to have 2 implant (xEM & xM1) on the same P0 location?
(wish there were a NExT version with the xM1 instead of the xNT …)
Can you inject the 2 implant back to back in the same injection or you have to place it next to it/at a later date?

Yes, and yes. You can get them both in the same location and at the same time.

1 Like

How do you maintain the 5mm spacing?

Have your installer place them 5mm apart :slight_smile:

Read from here down

and search the forum for “Corral”

Me too, and a few others

Maybe one day :arrow_heading_down:

Thanks for the link, really interesting read (still going through it).

1 Like

I think I’m gonna go with the NExT in L0 and the xM1 in R0 for now, it leaves me the option of adding an xEM in R0 if I have the need down the road.

Now the hardest part: get my wife on board :sweat_smile:

1 Like




Ok, after over 15h laying on the airgap capacitor i have no changes in the cloned cards data (T5577 and MK1) but the MK1 read went from 8 seconds to over 200 … not sure what that is about …
Next test will be on the end of the coil.

One more thought on implant selection:
Is there any advantages to the xEM over the NExT for the LF chip/antenna?
Also, is there anything the Ntag216 does that a DesfireEV2 cannot do?

If the answer are Yes and No respectively, im thinking it might be smarter to get xEM and xM1 on one side, freeing the other side for xDF2 (or an apex when it comes out)

Also thinking about the inner wrist for a small flex down the line … would a metal watch band bother anything there (having the implant bellow the band)?

Also, just confirming the NExT and xM1 cannot be side by side in the same P0 right?

Just weighing all my options/possibility before doing the big jump,

The usual recommendation is that there should be 5mm between implants.

Ideally you don’t have two HF or LF that close together to make it easier to select which one you really want to read.

this is where annoying standards come in :wink: the KBR1 will read any ISO14443A transponder UID, but not any HF (13.56MHz) tag… for example, the Spark 1 or xSLX are 13.56MHz HF but ISO15693 standard, which the KBR1 will not read.

1 Like

Ok, thanks for the details.

So the xDF2 is ISO14443A with “8kB multi-application memory space”, so can i emulate/clone any ISO14443A card to it?
ie: can i use the xDF2 instead of the xNT and the xSIID?

Also, does the xEM has a better read range than the NExT?

sorry no… the memory is “user memory”… but the UID (serial number) of the chip is read-only and not changeable.

no they are approximately the same performance.

1 Like

just to be clear … none of those products are able to have their UIDs changed… they are all read-only.

The only 13.56MHz ISO14443A chips that can change IDs are;


1 Like

Thank you so much for this, this makes so much more sense!
So except those 3 (“Magic” 1K), all other HF chip will have to be enrolled in the access system?

Yes. That is exactly what that means.

awesome, thanks

Now im wondering wither i should go for NExT on one side and xM1 on the other
Or xEM and xM1 on one side and xDF2 (or wait for the apex) on the other …

Unless you have a reason for a desfire chip I would wait for Apex. It is Flex only at the moment.