xDF2 is not responding to any reader

Hi, i bought the xDF2 on the last cyber monday sales and got it implanted right after it artived. Until now i didn’t get a single reading out of it no matter what reader i used and no matter in which orientation.
Initially i thought it was because of the swelling so i waited but i still wasn’t able to get a reading from it after the swelling went away. I work in the development department at a company that produces electronic locks so i have multiple different devices (mostly different electronic locks) around me that i can use to test and read tags but i still wasn’t able to get a single read with them or the different testing phones that i have access to.
I also tried to measure a resonant frequency using the miniVNA in reflection mode but there was no reflection. I have other rfid chips in my hands and so far i could see the resonant frequency of all of them using this device but on my xDF2. There just was nothing just like with a open line between the chip and the coil.
I ordered a Acr122u now and it will arrive in a few days. If it still doesn’t work with that reader i am out of ideas… i bought quite a few different chip implants over the years to test them with the electronic locks that the company i work for develops and they all worked so far but sadly the one i was most excited about didn’t.
Does anyone have an idea what i could do? Thank you very much in advance!

1 Like

Silly question, but did you try to take a reading before implanting it? And immediately after?

Me, I never implant anything that doesn’t read out of my body unless I absolutely have to. And then as soon as it’s in, i read it again. If it won’t reply at all, I have the piercer check if the chip is still in the needle. If it’s not, I have em remove it immediately.

All that double and triple checking spared me a few failed implant jobs.

I didn’t test it before because taking it out of the needle means bringing contamination in and so far all of the chips worked so there was no need to it. Dangerous things tests all chips before disinfecting them after all. I might test them though in the future.

That don’t mean nothing. I recently got a DOA implant from DT that had been tested before shipping. Shit happens.

And like I said, if it doesn’t ring inside the needle, you can always test it right after it’s implanted. It’s easier to take something out 30 seconds after it’s gone in.

Also, with the right reader and some persistence, sometimes NFC tags read inside the needle. You only need one test read.

Speaking of which, care to divulge the name of your company? I’m always on the lookout for implant-compatible smartlocks…

As mentioned we do test each device before inserting into the needle, however the EO gas sterilization procedure does introduce some thermal cycling that could turn a marginal antenna connection into a broken one. If it truly is DOA we will ship another to you immediately.

1 Like

Amal / DT will sort you out implant wise.

There are currently many people now and will be in the future, people wanting implant compatible door locks.

Do you have any that you work with that you could recommend?
Also, I am curious if you have read and if you had any thoughts and opinions on this, and would this be something your company may be interested in? or again, if you already have an off the shelf product that we don’t know about that ticks all the boxes…

1 Like

Thank you for all the replies! To amal I’ll wait til the acr122u arrives for a last final try and the conclusion to my xDF2 but so far it didn’t react to anything. To the question of Rosco: the company i work for is Dom Security. To the question of Pilgrimsmaster: the devices i could definitely confirm to work with the tags (and has good reading performance) is the Els Pro (125kHz) that will work quite well with the tags but i couldn’t test all yet and the Eniq Pro (13,56MHz)
it has a bit less range but it reads the xNT and the xM1+ quite good. I need to do some deeper testing with it to get valid conclusions but so far it looks quite good. I want to eventually be able to test the full setup of chips that dangerous things has to offer. Our locks are compatible with most chip types like (13,56MHz) the Ntag 213 to 216, mifare classic, desfire ev1 and ev2, mifare ultralight and ultralight c and probably a few more that i can’t remember right now, the icode dna tags or vivo key tags are sadly not compatible. On 125khz all the chips should be compatible as far as i know. But anyways… i’ll wait til the ac122u arrives til i can definitely say that my xDF2 is not working.

1 Like

@Spyfoxls, mate that is some really great info thank you.
I will update the spreadsheet accordingly and link to your post

I hope all works out with your xDF2

Nice products, thanks for the info! Sadly, you guys don’t offer Scandinavian versions of your nice door handles. My quest to find one that’s implant-compatible seems to be going nowhere :slight_smile:

You know what? For some reason I managed to miss your spreadsheet until now. it’s really nice!
May I suggest a few additions / modifications?

  • Becode AIR+ cam lock: works with NFC UIDs
  • Rollock Smart Lock W111/W112 smartlocks: works with NFC UIDs - tried it myself, the manufacturer is next door to me
  • Idesco Door Handle 7N & rebrands: works with NFC UIDs but does NOT work with implants (doesn’t wake up)
  • ACM08Y, ACM26C readers, and any of the kajillion variants of that reader design available from China: read EM4xxx’s. Long range. Wiegand or RS232 interface
  • Identiv uTrust 3700 F USB PC/SC NFC reader. Slightly worse performances than the ACR122U, but otherwise works well with HF implants
  • Elatec TWN4 MultiTech 2 & variants (the manufacturer offers a million variants, but they only have one board design) dual-frequency USB reader (PC/SC, CDC serial or keyboard wedge - configurable): works well with LF implants, terrible performances with HF implants but nominally works if you’re patient. Supports almost all protocols in both frequencie (firmware configurable up the wazoo)
  • The Halo Reader reads EM4xxx chips, provided they don’t contain a zero digit (firmware bug)
  • I have a feeling you can put Yes in all the boxes under the Proxmark entries :slight_smile:
1 Like

It was originally done by Joel Wedberg in Swedish :sweden:
We have just added an English tab, trying to add as much as possible to it.

Amal hasn’t officially " Put it out there", he used it in a post, so I have just started dropping it in occasionally also.

It is still a work in progress

Absolutely, any omissions or errors, I am happy to rectify and would appreciate the feedback.

I will add those ones in. ( Also thanks for the links, makes life easier )
I will link the comments back to this thread

Haha, yep

Ok the Acr122u reader arrived today and i tried for about an hour to get a reading out of the xDF2 chip but i didn’t manage to. The other chip implants that i have work flawlessly but my xDF2 is dead sadly…

aw man… ok… well, hit the floating orange help button on the website and submit a ticket that way… we’ll get a replacement sent out to you asap. Sorry about this!


What happened between the original spark and the spark2 that made it no longer compatible with with Quicklocks and Gunboxes? Or have they simply not been tested/confirmed?

The primary difference between the Spark 1 and Spark 2 is the ISO communication protocol they use.

The Spark 1 was set up to use the less common ISO 15693 protocol. This communication type uses less power so that it can read from a greater range, and also allows it to be used with specific locks that are configured to read that type of tag. The downside was that it could basically not be read by iPhones and while most Android phones supported it, it could be buggy.

The Spark 2 uses the much more common ISO 14443A protocol. All phones can read it now, but it not longer works with those locks. The xSLX was released to fill that gap. It doesn’t have the crypto authentication functions of the Spark, but it’s ISO 15693.


I submitted a ticket through the Digiwell website now since thats the reseller i bought it off. It is probably easier with the order number this way. Thanks alot for the Help!

Hi, i wanted to give another update on the xDF2. I recieved a new one shortly after sending the ticket. Yesterday i could finally go to my piercer to have it placed and now everything works flawlessly. The implant is very responsive and is easily read by phones and the locks that the company i work for produces. Only slightly less range than the xM1. Thanks alot for all the support!


Working for a company that makes NFC locks… Dude, it can’t get any better than that.
Also, they should pay you more for guinea-pigging them :slight_smile:


They didn’t ask me to do it. I was just curious and bought one implant after another to test it out. I bought everything from my own money xD I’m in a good position though to get news and early samples to test of new transponders like the Mifare Desfire Ev2 XL with 32kb of memory. It has enough storage to fit Super Mario Bros on it. There is also the Mifare Desfire Ev3 comming with more reading range and some new features

Hey, he’s even working for the company from which I’d like to buy my next lock… :thinking:

@Spyfoxls - I recently had some e-mail contact with DOM, and they told me that the DOM eniq pro no longer works with the standard NTAG216 chip but requires “more security” now, have you tested that one already? And for my alternative choice, the DOM ELS pro, does it work with the t5577-LF-chip? They told me it “should” work, which is not really assuring, considering the price of the lock… :wink: