Newbie: Trying to understand if NExT is compatible with work entry system

Thanks @Pilgrimsmaster

Really its down to what you want to do, most projects people undertake only juse the UID of the chip (thats the 4 bit number). The NExT is definatly versatile but its also a case of personal preference.

The HF side of the NExT is a NTAG216 iirc which would not be able to function the same as a mifar 1k however if you have the option to enrol an implant the first thing i would try would be to pick up a ntag216 card/tag and try getting that enrolled. Most systems only like one card type but others don’t care as long as it has a valid UID.

If that works fine then great go for a NExT if you want. If not the only thing you loose is the LF side which if you don’t mind another needle can be picked up for i $40 iirc (xEM)

2 Likes

I think an M1 and xEM combo chip would be pretty sweet and get you the best of both frequencies. Unfortunately it doesn’t exist yet. There is, however, a survey started by @Pilgrimsmaster where you can vote if you’d like to give a suggestion for future products.

2 Likes

images (63)

A 2in1 xM1 / xEM would be

tenor (22)

3 Likes

I still recon we need a dual flex, flexEM + apex or flexEM + flexM1

Yeah, and specifically the flexEMgen2 the problem is the LF antenna, OR just have a giant implant.
I have poised this before, with a potential antenna layout, the problem is, just because you can draw it, doesn’t mean it will be as small as you want it to be…stoopid physics. :abacus:
I would LOVE a wedge shaped FlexEM

But you could get one of each and put them next to each other.
Ideally, one ontop of the other…but not sure how this would read :man_shrugging: or if chaffing would become an issue :interrobang:

Ohhhh, I am about to drop an Amal teaser comment
I have been having a little tinker on my bench with something related to this, but only as and when I have time, I will let you know how it goes, but won’t be anytime soon.
( FYI even if it works, It won’t be as cool as any of Amals actual products )

Teaser
:microphone:
:arrow_heading_down:

1 Like

@Pilgrimsmaster
image

I thought a flexEMgen1a is probably better? Your likely to have a PM3 for the t5577 anyway so they seem to fit together.

I don’t know about “better”, but yes another option.
I did have the exact same thought, but why not make it easy if you can?
For this thing that doesn’t exist…yet :wink:

Some updates!

  • Bought an NExT
  • Bought a Proxmark Easy from Piswords (it’ll take forever to arrive in the mail)
  • The person who manages the access control system at work is happy to add my NExT into the system

When I got a peek at the enrollment software, it looks like there were various protocols that the system can accept, I saw HID on the list. So even though the badges they are administering are MIFARE EV1 cards, I am assuming I don’t need to clone one of those, and could use a different protocol instead.

My question is: Assuming the reader really can accept a wider range of protocols… do you think there’s a certain protocol I should learn toward using with my NExT?

I definitely haven’t seen every access control system frontend on the market, but in this case I would wager that the company who installed it uses 1 software to control all the different types of reader hardware they sell, but only activate 1 type of protocol in the software per customer depending on what readers they install in the building.

Most readers that I’ve seen can only support 1 protocol. So for example even though ISO 14443a and ISO 15693 are very similar protocols operating on the same frequency (13.56MHz) very few door swipe readers can be configured to read both. They purposely limit them, even though they often charge more than $100 for a reader and it hypothetically could read anything if the firmware was better. It’s quite a racket.

MIFARE Classics are also a completely different memory structure than the HF chip in the NExT. You’d need like an xM1 for that. You should hope the system runs on HID, because then at least there’s a chance you can clone it onto the LF side

1 Like

Ha crap. I’ll do some testing. Thank you!

I did some research. Below is a screenshot from the user manual. Looks like it’s possible to switch different protocols on/off. Verbiage in manual didn’t seem to indicate that they’re disabled unless you pay for the feature… appears to be something you can easily toggle.

When I was able to look at our setup, there was just 1 switch flipped on, I assume it was 14443 Secure MiFare.

Hoping that if we flip more on, I can get NExT to work.

Also-- when I hold the Diagnostic Card up to the reader, LF and HF blink.

1 Like

Yes buddy, I think you may be onto a winner

The 14443 UID ( CSN ) SHOULD do that for you

NExT - HF uses 14443A and if it is just looking for the UID ( CSN - Card Serial Number ) This should do it

Go Toggle that button
Good luck, keep us updated

2 Likes

After attempting to make the changes in the access system today, I have mixed news…

Bad news - you cannot have “14443 UID (CSN)” and “14443 Secure MiFare Plus” enabled at the same time. You must choose one or the other, and obviously we need to keep the latter enabled because it’s what everyone else is using.

Good news - that seems to be the only restriction, all the other options can be turned on in conjunction with “14443 Secure MiFare Plus”.

So that being said… what protocol do you think I should try next? The only one that rings a bell to me is “Schlage HID”… but I’m not sure! :slight_smile:

Either HID or AWID are nicely supported on the T5577, pick your poison. I’d probably go HID because it seems to be more widely compatible for if you want to use the same implant for multiple things.

2 Likes

Perfect-- thank you. Attempt #2 will be the HID.

1 Like

After several more failed attempts, we have SUCCESS! I got it to work by using my Proxmark Easy to program the T5577 side of my NExT as HID. Being friends with the person who handles the access system was invaluable.

It felt pretty surreal to use my hand to unlock the doors at work this morning :slight_smile:

THANK YOU ALL for your help & expertise! I hope to pay it forward.

Tips for anyone else trying to work with the “Allegion Engage” access control system in the future:

  • Scanning the ID (at the door or the computer reader) is the ONLY way to enroll any type of card. You cannot go into the web portal and type in a UID (that type of manual entry is not supported).
  • There’s a screenshot of all the supported protocols in a post above. If you have the Allegion system, all of those protocols are available to you. It’s not feature-locked. You just flip the switch to enable. However, there are some protocols you cannot have on at the same time, so you’ll need to play around.
  • You can easily enroll MiFare cards via the USB attachment on the admin’s computer. But if you want to enroll most other types of cards (such as HID) you must enroll at the actual door reader using the mobile phone app.
3 Likes

Great suff, awesome not have to worry about loosing your access card

Do you have images or better yet links to the actual readers you use?, so I can add it to the Compatibility Matrix unless it is already on the sheet

Yessir!

-Card reader on the building is MT15, it does LF and HF, lots of options to turn certain protocols on/off
-The Enrollment reader that plugs into computer (to add/remove cards from user profiles) is MT20W, it can only do MiFare cards

2 Likes

Excellent info, thanks
Added to the Compatibility Matrix

1 Like