Old xsiid from recent purchase?

Support
1

So I got my Xsiid installed a week and a half ago. My plans were to put my business card on it like i currently have on my nfc side of my NExT. But I can’t read it with anything but a flipper. I haven’t tried pulling out the pm3 yet. I’ve tried the NXP tag writer app. No read/write. Similar results with the nfc cool app. And nxp tag info. But all appear to link well and give good bright light. Flipper sees it proper as I2c chip but I can’t rewrite it from there. Is it possible this was an older batch that wasn’t Natively seen as ndef. Any suggestions? Right now it’s just a field detector light with UID

Edit: SOLVED case just thick enough to prevent data exchange but thin enough to allow what appeared to be full power.

1 Like
2

TLDR
You cant write NDEF to it!? but everything else works!

To me this sounds like everything is working as it should, as it lights up and the flipper “sees” it.

I think we need to look at your process.

lets start with:

My initial thought is a phone issue…

What type of phone do you have, and do you know where the antenna trace is?

Have you tried removing the phone cover?

Also, so that we dont get caught out later,
What size is the NDEF you are trying to write?

1 Like
4

I was trying to write the same url as I have in my Ntag216 on my NExT. It’s just a url to the Linq business card page. It’s only 37 bytes but I can’t get anything on my phone to interact I with this. I have an iPhone 15. The top left corner opposite the camera section seems to be the strongest. It’s where I present my NExT to grab the url for my business card currently. Playing with it a little more so the flipper sees a NTAG I2C plus 2K. My phone running any scanning app won’t see anything (maybe because there’s not a NDEF message yet?) but I can’t seem to get my phone to write anything. I’ve tried url. Contact card. WiFi. Nothing. And when I try to write the same info from my next and copy it over with the flipper. I get “this is the wrong card: card of the same type should be presented”

IM A DUMBASS. It was the case. It was good enough to make a nice bright light but it kept polling and didn’t ever go solid. I took the case off to try and it locked to it and made it act just as the flipper makes it respond. It polled till it locked then stayed solid while reading data. But I got it. It wrote and now it reads. Thanks for your help.

1 Like
5

Are you presenting the phone flat against your tag or perpendicular, like this;

6

I was presenting parallel. With my phone case presenting perpendicular gave me a led that wasn’t as bright if I got one at all. But with the case off I can present either way. But the case was my issue. I was eventually able to write my data to it. I have a thicker otterbox and it blocks all the MagSafe stuff too.

7

Not at all, its often times just a little gotchas.

Easy to overlook.

Generally implants are not to blame, they just do their thing.
Its normally the meat sacks the implants are in, where the issue lies.

So fault finding is easier when working backward

2 Likes
8

Now I just need to drop a repeater sticker on my phone and see if that helps. Wont help other people’s phone and the contact exchange. But I mainly got it for the blinkie

1 Like
9

Let’s not ignore that. There could be some swelling still and it’s very likely that your reads will improve over time.

3 Likes
10

true. I was just going off my previous experience with my NExT. My nfc side was pretty easy to catch after the first few days on both my phone and flipper. But even after a little over a month the RFID side is still very tricky to catch even with the flipper. but at least presenting to the known readers sweet-spot is easy to hit reliably. But it was hard to find my work’s Honeywell keypad reader as it wont set off either the diagnostic card or either of the field detectors.