Not sure if this helps your concerns, but I’m not sure it’s fiddly.
I do expect it to be fiddly, and it sure looks dodgy and fiddly AF. Yet I haven’t messed with it enough to neither confirm nor deny it.
Then… I would guess what you need is a chip such as the DF2 or similar, with a big antenna.
In which case I expect the MN is not going to perform as you want.
Well, I equipped myself with the flexNExT as a pure productivity tool: the attractiveness was that (1) it read easily and from a very long distance and (2) it was compatible with as many cellphones as possible (unlike a Mifare Classic). It died, and now I need a replacement that fits that bill.
As far as reading distance, I don’t know that yet, because neither you nor Ottomagne have the large antenna version. That’s why I said I’ll be following the progress of whoever gets the first big flexMN with great interest.
As for reliability, I am hoping you two got an unconfigured version and you didn’t set it up quite right. That’s why I asked Amal to configure mine right before shipping, so it’s as good as it needs to be - because unlike me, Amal knows what he’s doing.
So there is hope. But I can’t help thinking early reports on this chip don’t look like a good start.
Which version are you referring to when you say large antenna version? Because Eyeux got his in the new flex format, but I got mine in the disc format ala the flexNExT. Unless there’s another even larger antenna design that I missed, I’m pretty sure I have the large version.
I was kinda hoping we could just refer to it as the “new flex” format, and in a few months we would just start calling it the flex. It appears this is what we’re going to be using moving forward because of its versatility and durability, and it’s not a wedge.
Just busted it out to test. I was able to get pretty good reads. I used my digital calipers to get an idea of how far I was reading from (I’d start high and lower the calipers with the chip on-top until the LED turned green), and I tried from a variety of angles (which accounts for some disparity in the reading range).
Successful Read Distances
25.59mm
19.25mm
13.73mm
22.67mm
21.18mm
29.00mm
29.09mm
31.20mm
23.90mm
28.04mm
Also, for your own knowledge @anon3825968 , I was able to write directly to the chip from the proxmark. I wrote a small NDEF record to redirect to http://example.com/ onto the chip, then read it with my phone. It redirected fairly quickly. I’m gonna write up a bigger thread synthesizing this info with some more tests I’m gonna try to run this weekend, but I thought you’d like to know that, once you actually get it written to the chip, it works as you’d expect it
Okay over an inch then. That looks good - especially with an ACR122U. The Feitian I used with my FlexNExT would read from even farther away.
At the risk of being annoying, can you try filling the chip to the brim with the biggest NDEF possible and reading that, see how long it takes? If you don’t wanna, no problem. I don’t want to waste your time.
I’ll give that a shot this weekend! I’m actually working my second gig right now, so I don’t have too much time to play around with my tags, but I should have free time this weekend to.
I think that will end up causing some confusion, such as when Rosco thought Otto’s flex was the strip formal, when it’s the large disc one.
This comes because xSeries always come in a single form factor, but flex…
wedge
strip
T5577 disk
NExT/MN disk
DoNExT
even if wedge get’s decommissioned, there’s still a fairly large amount of formats out there which fit the “flex” tag…
This data is actually really useful for this Thread!
Those are almost consistent with my “old” flex DF2 reading range on ACR122U. 15mm is a distance from which almost any angle reads, but I do achieve 30mm+ successful reads with it.
Since I would expect the larger antenna to perform better than the old one, then the MagicNtag chip definitely eats out range more than I assumed during my initial write up.
Uhuu!! looking forward!
That is an interesting test.
Although not indicative of this chip’s particular results, when I ran tests on my DF I got the following conclusion (I didn’t put much effort into testing though):
Using TagInfo, there was no full scan time difference between differing NDEF lengths. (using other methods yes, but not on TagInfo’s full scan)
And on that note, my DF gets a full scan in roughly less than half a second, while my MN takes a good 3 seconds.
I actually agree with this, specifically since the flexMN is being offered in both disc form and wedge form (which, as Satur9 mentioned, is not longer wedge shaped). I’d be inclined to think that a new nomenclature should be added for the larger disc implants (assuming they become long-term stays in inventory):
flexMN -> the new standard flex form factor
discMN -> the disc form factor
maybe Amal doesn’t need to adopt this officially on the storefront (since the flexMN is the only disc based form factor currently available and in the foreseeable future), but we, as a community, could colloquially start referring to them that way to differentiate (kinda how @anon3825968 did with his doNeXt). tbh, I’ll probably start doing that on my own, and if others want to hop on, the more the merrier
I’m thinking that’s probably going to be the case when I get around to testing that out. The NDEF record that I currently have on the chip is only 17 bytes long, and the TLV block ends it after that - at which point, the phone would redirect to that url. I have to imagine that if the TLV block terminated later, the phone wouldn’t read as quickly. Unless the hard part for the chip isn’t data transfer speeds but something about the initial read being slow due to emulation wankery - that’d be nice (since it’d mean that the entire memory buffer would be able to be read fast), but by the looks of it, the chip is just slow to read.
Despite me agreeing with you… Imagine the confusion for those who join the forum having only the knowledge obtained by storefront and not knowing about this “internal agreement” of ours…
I personally don’t have a problem with overexplaining things here, so I mostly use “new flex Wedge/strip”.
This comes from my efforts to intentionally simplify whatever I write in open forums, to the point where I would rather be misinterpreted by an over-zealous connoisseur (which already happened a few times here), than to be too cryptic to the eyes of new members.
That’s where I believe TagInfo’s Full scan does attempt to keep on reading. Hence the same read speed on my DF regardless of NDEF written size.
(or the DF2 is too fast…)
No I had my eye on the magic ntag for some time and I can get ntag216 in mob packages… but with the total failure of the flexNExT, and the inclusion of the T5577 in the flexMN replacement, it made the most sense to make the flexMN contain two very versatile chips in the same package… maybe a flexNExT is possible in the future using a wire coil antenna and mob packaged ntag216, but honestly it’s not looking likely. The magic ntag chip has been vetted by iceman as “finicky yes, but very stable”, with the only problem being noted is that people forget their password and sorta lock themselves out of it.
I might just be running around too much on hardstyle festivals, but I think I might run into problems when saying I’ve got some Emma in my hands… aaaat least in Germany, dunno how international that is