have very poor coupling with everything in the environment because of the shapes and sizes of the coils
only interact with the magnetic component of the “near-field” (not electrical fields)
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.
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?
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,
this is where annoying standards come in 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.