Not always reading NFC tag info

[RoseanneParticipant]

Hi,

We are in final stages of testing and have found that when tags are written with Flomio, the read will always work.

However when tags are written with an Android application, the read does not always work. Attached is a screenshot of a third party Android app which is reading info from our tag:

With the Flomio reader, I am not getting past the check if ndefRecords exist:

            tag.readNdef { (ndefMessage) in
                guard let uid = tag.uid else  { return }
                self.localUid = uid
                print("uid is : \(uid)")
                print("tag.atr is : \(tag.atr)")
                print("tag.atr is : \(tag.type)")
                
                guard let ndefRecords = ndefMessage?.ndefRecords else {
                    print("message nil")
                    return
                } 
             }

Message nil is printed, this is consistently happening with a card right now. Can you advise on what the issue may be?

• This topic was modified 6 years, 3 months ago by  Scott.

[ScottKeymaster]

Hi Roseanne,

Can you send a picture of the memory within the tag, not just the NDEF messages found on Android. This sounds like an issue with our NDEF Parser within iOS.

Kind Regards,
Scott

[RoseanneParticipant]

Hi Scott,

Image attached:

Thanks,
Roseanne

• This reply was modified 6 years, 3 months ago by  Roseanne.

[ScottKeymaster]

If you could print the whole page from Full Scan on NXP TagInfo that would be great.

Scott

[RoseanneParticipant]

Hi Scott,

Anytime I paste in the info and submit, the post isn’t coming up here on the Flomio forum. Do you have an email I can directly send the info to?

Thanks

** TagInfo scan (version 4.23) 2018-08-24 08:27:57 **
Report Type: External

— IC INFO ——————————

# IC manufacturer:
NXP Semiconductors

# IC type:
NTAG213

# NFC Forum NDEF-compliant tag:
Type 2 Tag

— NDEF ——————————

# NFC data set information:
NDEF message containing 2 records
Current message size: 132 bytes
Maximum message size: 132 bytes
NFC data set access: Read-Only

# Record #1: MIME type (RFC 2046) record:
Type Name Format: MIME type (RFC 2046)
Short Record
type: “application/vnd.cga.flex_tag”

Payload length: 64 bytes
Payload data:

[00] 56 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 |VsGJcpZtz3QsjIgI|
[10] 4E 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E |N22Xovr+ftngn+PN|
[20] 4A 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 |JntIwXnTX6uEJUkw|
[30] 59 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B |Yy8ttRa+cjemta2+|

# Record #2: Android Application record:
Type Name Format: NFC Forum external type
Short Record
type: “android.com:pkg”
package name: com.cga.flexsummary
Payload length: 19 bytes
Payload data:

[00] 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D 6D |com.cga.flexsumm|
[10] 61 72 79 |ary |

# NDEF message:
[00] 92 1C 40 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 |..@application/v|
[10] 6E 64 2E 63 67 61 2E 66 6C 65 78 5F 74 61 67 56 |nd.cga.flex_tagV|
[20] 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 4E |sGJcpZtz3QsjIgIN|
[30] 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E 4A |22Xovr+ftngn+PNJ|
[40] 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 59 |ntIwXnTX6uEJUkwY|
[50] 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B 54 |y8ttRa+cjemta2+T|
[60] 0F 13 61 6E 64 72 6F 69 64 2E 63 6F 6D 3A 70 6B |..android.com:pk|
[70] 67 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D |gcom.cga.flexsum|
[80] 6D 61 72 79 |mary |

# NDEF Capability Container (CC):
Mapping version: 1.0
Maximum NDEF data size: 144 bytes
NDEF access: Read-Only
E1 10 12 0F |…. |

# Control TLVs:
Lock Control TLV at address 0x04, offset 0
* Dynamic lock bytes at address 0x28, offset 0
– 12 lock bits
– 8 bytes locked per lock bit
01 03 A0 0C 34 |….4 |

— EXTRA ——————————

# Memory size:
144 bytes user memory
* 36 pages, with 4 bytes per page

# IC detailed information:
Full product name: NT2H1311G0DUx
Capacitance: 50 pF

# Version information:
Vendor ID: NXP
Type: NTAG
Subtype: 50 pF
Major version: 1
Minor version: V0
Storage size: 144 bytes
Protocol: ISO/IEC 14443-3

# Configuration information:
ASCII mirror disabled
NFC counter: disabled
No limit on wrong password attempts
Strong load modulation enabled

# Originality check:
Signature verified with NXP public key

— FULL SCAN ——————————

# Technologies supported:
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible

# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.NfcA, android.nfc.tech.MifareUltralight, android.nfc.tech.Ndef]
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms

# Detailed protocol information:
ID: 04:86:91:BA:AE:4F:81
ATQA: 0x4400
SAK: 0x00

# Memory content:
[00] * 04:86:91 9B (UID0-UID2, BCC0)
[01] * BA:AE:4F:81 (UID3-UID6)
[02] * DA 48 FF FF (BCC1, INT, LOCK0-LOCK1)
[03] * E1:10:12:0F (OTP0-OTP3)
[04] * 01 03 A0 0C |….|
[05] * 34 03 84 92 |4…|
[06] * 1C 40 61 70 |.@ap|
[07] * 70 6C 69 63 |plic|
[08] * 61 74 69 6F |atio|
[09] * 6E 2F 76 6E |n/vn|
[0A] * 64 2E 63 67 |d.cg|
[0B] * 61 2E 66 6C |a.fl|
[0C] * 65 78 5F 74 |ex_t|
[0D] * 61 67 56 73 |agVs|
[0E] * 47 4A 63 70 |GJcp|
[0F] * 5A 74 7A 33 |Ztz3|
[10] x 51 73 6A 49 |QsjI|
[11] x 67 49 4E 32 |gIN2|
[12] x 32 58 6F 76 |2Xov|
[13] x 72 2B 66 74 |r+ft|
[14] x 6E 67 6E 2B |ngn+|
[15] x 50 4E 4A 6E |PNJn|
[16] x 74 49 77 58 |tIwX|
[17] x 6E 54 58 36 |nTX6|
[18] x 75 45 4A 55 |uEJU|
[19] x 6B 77 59 79 |kwYy|
[1A] x 38 74 74 52 |8ttR|
[1B] x 61 2B 63 6A |a+cj|
[1C] x 65 6D 74 61 |emta|
[1D] x 32 2B 54 0F |2+T.|
[1E] x 13 61 6E 64 |.and|
[1F] x 72 6F 69 64 |roid|
[20] x 2E 63 6F 6D |.com|
[21] x 3A 70 6B 67 |:pkg|
[22] x 63 6F 6D 2E |com.|
[23] x 63 67 61 2E |cga.|
[24] x 66 6C 65 78 |flex|
[25] x 73 75 6D 6D |summ|
[26] x 61 72 79 FE |ary.|
[27] x 00 00 00 00 |….|
[28] . FF 0F 00 BD (LOCK2-LOCK4, CHK)
[29] . 04 00 00 FF (CFG, MIRROR, AUTH0)
[2A] . 00 05 — — (ACCESS)
[2B] +P FF FF FF FF (PWD0-PWD3)
[2C] +P 00 00 — — (PACK0-PACK1)

*:locked & blocked, x:locked,
+:blocked, .:un(b)locked, ?:unknown
r:readable (write-protected),
p:password protected, -:write-only
P:password protected write-only

————————————–

• This reply was modified 6 years, 3 months ago by  Roseanne.
• This reply was modified 5 years, 8 months ago by  Richard.

[RoseanneParticipant]

Hi Scott,

Any time I paste in the info, the post does not appear on the forum?

Do you have an email I can send the info onto directly?

Thanks,
Roseanne

[ScottKeymaster]

We try to avoid using emails so that other customers can find these threads useful in the future. If embedding an image is the issue, posting a link to the image would work.

Scott

[RoseanneParticipant]

Hi Scott, it was actually just pasting in the text that lead to this issue of the post not appearing. See links instead:

[ScottKeymaster]

Hi Roseanne,

I’ll try recreate the issue and get back to you.
There is also a share option within NXP TagInfo app which you could
use to share the tag scan to scott@flomio.com.
Please continue to post via the forums for the reason I said above.

Scott

[ScottKeymaster]

Hi Roseanne,

Can you share within NXP TagInfo app to scott@flomio.com, it’ll mean I can use your NFC tag data to debug our parser. As we are getting ready to launch PassNinja we have to focus our attention on that in the short term, if you would like our engineers to focus on your issue with more immediacy you can purchase Flomio Service Hours.

Kind Regards,
Scott

[RoseanneParticipant]

Hi Scott,

The share option is what I tried to do first because I thought it would be easier for you to input into your parser. I have just sent the info to scott@flomio.com. Please let me know here if this is what you need.

We might wait to see if there is a quick fix for this issue, that is easily spotted by your dev team before considering purchasing Flomio Service Hours to fix the issue with the Flomio parser.

Thanks,
Roseanne

[RoseanneParticipant]

Hi Scott,

Any update on whether you were able to recreate the issue?

Regards,
Roseanne

[ScottKeymaster]

Hi Roseanne,

No sorry, I have not been able to dedicate time to this issue as of yet.

Scott

[RoseanneParticipant]

Hi Scott,

I know you said on the 28th that the short term focus was on Pass Ninja.
This is a bit vague, would you be able to provide a ballpark estimate on when you might be able to dedicate time to the issue?

Thanks,
Roseanne

[ScottKeymaster]

Hi Roseanne,

I’m sorry I can’t shed more light on it. I appreciate your patience in the meantime. I’ll hopefully be able to get to it soon.

Scott

[RoseanneParticipant]

Hi Scott, I noticed there was a new release of the flomio SDK a week ago, marked improvements in iOS reading. I’m not sure if this release was supposed to be addressing the bug outlined here, since you didn’t post about it here but I’ve tried the new SDK and am having the same issue. I currently have 4 different tag types – all of which can be read on Android and with Core NFC but Flomio can only read 2 of them.

[RichardKeymaster]

@Roseanne, we are not supporting Type 1 and 3 tag types in the Flomio SDK. Is this something you’re interested in? For what use case??

thanks,
Richard

[ScottKeymaster]

Hi Roseanne,
You can send me the tag info for the two tags via NXP TagInfo on android. I only received one in the past.

Scott

[RoseanneParticipant]

Hi Scott,

I sent on one particular example a month ago, when requested. This was a test case I had to hand when posting here.

Of the 4 tags, I am using this morning, all are NFC Forum Type 2.
3 of them are NTAG213 and one is of type NTAG203.

Two of the 213’s work while the third doesn’t.
The 203 doesn’t.

I will send on another two reports for the tags I happened to have to hand this morning, when testing the latest SDK. The data written to these tags is of the same format as the example previously sent.

Thanks,
Roseanne

• This reply was modified 6 years, 2 months ago by  Roseanne.

[RoseanneParticipant]

Any update?

[RoseanneParticipant]

Hi, it’s been over two months since we first highlighted this issue and over a month since we’ve received a response. Can we expect to hear back soon about this?

[ScottKeymaster]

Hi Roseanne,

Sorry for all this delay! I am the main developer on the iOS SDK and I have been completely unable to dedicate time to this for several reasons for the last few months. I will have time soon, but for the immediate future we won’t be able to address this issue.

My apologies,
Scott

[KamranParticipant]

Hi,

We are also facing the same issue. Data written on NFC tag using other applications are not being read by FloJack BZR.

[RoseanneParticipant]

Hi Scott, can you confirm a date which you will spend time to resolve the issue?

Again, we’ve been waiting since August 23rd, I don’t see this as an acceptable wait time for customers, especially those who purchased the Pro SDK

[ScottKeymaster]

Hi Roseanne,
I will fix this soon, I will try have this fixed for you over the holidays. Again, I understand your frustration and agree, its not an acceptable wait time for customers regardless of the product you purchased.

Kamran,
The FloJack BZR is not ideal for reading NDEF data as the audiojack throughput is quite slow. You should try use the FloBLE Plus, I suspect you are not experiencing the same issue as Roseanne. If you like to discuss this further, I suggest creating a new thread.

Scott

[RichardKeymaster]

Hi Roseanne, I wanted offer you some alternate ways of solving your problem. First and foremost you need to be aware that supporting NTAG203 tags is not our priority since only a small number of customers use it. We are constantly trying to upgrade our SDK to support more tag types but this is a background task and will continue to be until we see a business need. The Pro aspect of the SDK you purchased is for offline mode, reader connection management, and other features unrelated to individual tag types. In fact both Basic and Pro SDKs support the same tag types.

In order to read NTAG203 all you need is to implement it’s data protocol. Our SDK offers an interface for you to program your own APDUs. All you need to do is register a FmSessionManagerDelegate for when tags are scanned, then parse the FmTag atr member variable to get filter for NTAG203 targets. Finally, you can sendApdu via the FmSessionManager to implement the NTAG203 data protocol.

For mission critical customers we offer Flomio Service packages for sale to implement niche features they may need. We estimate it will take roughly 8 packages to get this done for you.

best,
Richard

[RoseanneParticipant]

Hi Richard,

For now we would just be happy if we could have one of our type 2 tags working consistently, and not reporting back zero records when some do exist. If that’s type 213, that’s fine.

Hi Scott,
We look forward to testing your update with the bug fix after the holidays.

Regards,
Roseanne

[RoseanneParticipant]

Hi Scott,

When should we expect the update?

Thanks,
Roseanne

[ScottKeymaster]

Hi Roseanne,

This issue is low priority because there is not enough customer demand for it to be resolved. You should not expect it to be resolved in the near future due to the resource constraints of our small team. We are focusing on Pass Ninja and a cross platform Javascript SDK so that we can support a greater number of customers. I apologise for any inconvenience that this will cause.

Scott

[RoseanneParticipant]

Hi Scott,

Here is what I got from pressing the share button:

** TagInfo scan (version 4.23) 2018-08-24 08:27:57 **
Report Type: External

-- IC INFO ------------------------------

# IC manufacturer:
NXP Semiconductors

# IC type:
NTAG213

# NFC Forum NDEF-compliant tag:
Type 2 Tag

-- NDEF ------------------------------

# NFC data set information:
NDEF message containing 2 records
Current message size: 132 bytes
Maximum message size: 132 bytes
NFC data set access: Read-Only

# Record #1: MIME type (RFC 2046) record:
Type Name Format: MIME type (RFC 2046)
Short Record
type: "application/vnd.cga.flex_tag"

Payload length: 64 bytes
Payload data:

[00] 56 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 |VsGJcpZtz3QsjIgI|
[10] 4E 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E |N22Xovr+ftngn+PN|
[20] 4A 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 |JntIwXnTX6uEJUkw|
[30] 59 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B |Yy8ttRa+cjemta2+|

# Record #2: Android Application record:
Type Name Format: NFC Forum external type
Short Record
type: "android.com:pkg"
package name: com.cga.flexsummary
Payload length: 19 bytes
Payload data:

[00] 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D 6D |com.cga.flexsumm|
[10] 61 72 79 |ary |

# NDEF message:
[00] 92 1C 40 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 |..@application/v|
[10] 6E 64 2E 63 67 61 2E 66 6C 65 78 5F 74 61 67 56 |nd.cga.flex_tagV|
[20] 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 4E |sGJcpZtz3QsjIgIN|
[30] 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E 4A |22Xovr+ftngn+PNJ|
[40] 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 59 |ntIwXnTX6uEJUkwY|
[50] 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B 54 |y8ttRa+cjemta2+T|
[60] 0F 13 61 6E 64 72 6F 69 64 2E 63 6F 6D 3A 70 6B |..android.com:pk|
[70] 67 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D |gcom.cga.flexsum|
[80] 6D 61 72 79 |mary |

# NDEF Capability Container (CC):
Mapping version: 1.0
Maximum NDEF data size: 144 bytes
NDEF access: Read-Only
E1 10 12 0F |.... |

# Control TLVs:
Lock Control TLV at address 0x04, offset 0
* Dynamic lock bytes at address 0x28, offset 0
- 12 lock bits
- 8 bytes locked per lock bit
01 03 A0 0C 34 |....4 |

-- EXTRA ------------------------------

# Memory size:
144 bytes user memory
* 36 pages, with 4 bytes per page

# IC detailed information:
Full product name: NT2H1311G0DUx
Capacitance: 50 pF

# Version information:
Vendor ID: NXP
Type: NTAG
Subtype: 50 pF
Major version: 1
Minor version: V0
Storage size: 144 bytes
Protocol: ISO/IEC 14443-3

# Configuration information:
ASCII mirror disabled
NFC counter: disabled
No limit on wrong password attempts
Strong load modulation enabled

# Originality check:
Signature verified with NXP public key

-- FULL SCAN ------------------------------

# Technologies supported:
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible

# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.NfcA, android.nfc.tech.MifareUltralight, android.nfc.tech.Ndef]
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms

# Detailed protocol information:
ID: 04:86:91:BA:AE:4F:81
ATQA: 0x4400
SAK: 0x00

# Memory content:
[00] * 04:86:91 9B (UID0-UID2, BCC0)
[01] * BA:AE:4F:81 (UID3-UID6)
[02] * DA 48 FF FF (BCC1, INT, LOCK0-LOCK1)
[03] * E1:10:12:0F (OTP0-OTP3)
[04] * 01 03 A0 0C |....|
[05] * 34 03 84 92 |4...|
[06] * 1C 40 61 70 |.@ap|
[07] * 70 6C 69 63 |plic|
[08] * 61 74 69 6F |atio|
[09] * 6E 2F 76 6E |n/vn|
[0A] * 64 2E 63 67 |d.cg|
[0B] * 61 2E 66 6C |a.fl|
[0C] * 65 78 5F 74 |ex_t|
[0D] * 61 67 56 73 |agVs|
[0E] * 47 4A 63 70 |GJcp|
[0F] * 5A 74 7A 33 |Ztz3|
[10] x 51 73 6A 49 |QsjI|
[11] x 67 49 4E 32 |gIN2|
[12] x 32 58 6F 76 |2Xov|
[13] x 72 2B 66 74 |r+ft|
[14] x 6E 67 6E 2B |ngn+|
[15] x 50 4E 4A 6E |PNJn|
[16] x 74 49 77 58 |tIwX|
[17] x 6E 54 58 36 |nTX6|
[18] x 75 45 4A 55 |uEJU|
[19] x 6B 77 59 79 |kwYy|
[1A] x 38 74 74 52 |8ttR|
[1B] x 61 2B 63 6A |a+cj|
[1C] x 65 6D 74 61 |emta|
[1D] x 32 2B 54 0F |2+T.|
[1E] x 13 61 6E 64 |.and|
[1F] x 72 6F 69 64 |roid|
[20] x 2E 63 6F 6D |.com|
[21] x 3A 70 6B 67 |:pkg|
[22] x 63 6F 6D 2E |com.|
[23] x 63 67 61 2E |cga.|
[24] x 66 6C 65 78 |flex|
[25] x 73 75 6D 6D |summ|
[26] x 61 72 79 FE |ary.|
[27] x 00 00 00 00 |....|
[28] . FF 0F 00 BD (LOCK2-LOCK4, CHK)
[29] . 04 00 00 FF (CFG, MIRROR, AUTH0)
[2A] . 00 05 -- -- (ACCESS)
[2B] +P FF FF FF FF (PWD0-PWD3)
[2C] +P 00 00 -- -- (PACK0-PACK1)

*:locked & blocked, x:locked,
+:blocked, .:un(b)locked, ?:unknown
r:readable (write-protected),
p:password protected, -:write-only
P:password protected write-only

--------------------------------------

Also here are images of each tab:

[RoseanneParticipant]

Hi Scott this is what I got from pressing the share button:

** TagInfo scan (version 4.23) 2018-08-24 08:27:57 **
Report Type: External

-- IC INFO ------------------------------

# IC manufacturer:
NXP Semiconductors

# IC type:
NTAG213

# NFC Forum NDEF-compliant tag:
Type 2 Tag

-- NDEF ------------------------------

# NFC data set information:
NDEF message containing 2 records
Current message size: 132 bytes
Maximum message size: 132 bytes
NFC data set access: Read-Only

# Record #1: MIME type (RFC 2046) record:
Type Name Format: MIME type (RFC 2046)
Short Record
type: "application/vnd.cga.flex_tag"

Payload length: 64 bytes
Payload data:

[00] 56 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 |VsGJcpZtz3QsjIgI|
[10] 4E 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E |N22Xovr+ftngn+PN|
[20] 4A 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 |JntIwXnTX6uEJUkw|
[30] 59 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B |Yy8ttRa+cjemta2+|

# Record #2: Android Application record:
Type Name Format: NFC Forum external type
Short Record
type: "android.com:pkg"
package name: com.cga.flexsummary
Payload length: 19 bytes
Payload data:

[00] 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D 6D |com.cga.flexsumm|
[10] 61 72 79 |ary |

# NDEF message:
[00] 92 1C 40 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 |..@application/v|
[10] 6E 64 2E 63 67 61 2E 66 6C 65 78 5F 74 61 67 56 |nd.cga.flex_tagV|
[20] 73 47 4A 63 70 5A 74 7A 33 51 73 6A 49 67 49 4E |sGJcpZtz3QsjIgIN|
[30] 32 32 58 6F 76 72 2B 66 74 6E 67 6E 2B 50 4E 4A |22Xovr+ftngn+PNJ|
[40] 6E 74 49 77 58 6E 54 58 36 75 45 4A 55 6B 77 59 |ntIwXnTX6uEJUkwY|
[50] 79 38 74 74 52 61 2B 63 6A 65 6D 74 61 32 2B 54 |y8ttRa+cjemta2+T|
[60] 0F 13 61 6E 64 72 6F 69 64 2E 63 6F 6D 3A 70 6B |..android.com:pk|
[70] 67 63 6F 6D 2E 63 67 61 2E 66 6C 65 78 73 75 6D |gcom.cga.flexsum|
[80] 6D 61 72 79 |mary |

# NDEF Capability Container (CC):
Mapping version: 1.0
Maximum NDEF data size: 144 bytes
NDEF access: Read-Only
E1 10 12 0F |.... |

# Control TLVs:
Lock Control TLV at address 0x04, offset 0
* Dynamic lock bytes at address 0x28, offset 0
- 12 lock bits
- 8 bytes locked per lock bit
01 03 A0 0C 34 |....4 |

-- EXTRA ------------------------------

# Memory size:
144 bytes user memory
* 36 pages, with 4 bytes per page

# IC detailed information:
Full product name: NT2H1311G0DUx
Capacitance: 50 pF

# Version information:
Vendor ID: NXP
Type: NTAG
Subtype: 50 pF
Major version: 1
Minor version: V0
Storage size: 144 bytes
Protocol: ISO/IEC 14443-3

# Configuration information:
ASCII mirror disabled
NFC counter: disabled
No limit on wrong password attempts
Strong load modulation enabled

# Originality check:
Signature verified with NXP public key

-- FULL SCAN ------------------------------

# Technologies supported:
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible

# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.NfcA, android.nfc.tech.MifareUltralight, android.nfc.tech.Ndef]
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms

# Detailed protocol information:
ID: 04:86:91:BA:AE:4F:81
ATQA: 0x4400
SAK: 0x00

# Memory content:
[00] * 04:86:91 9B (UID0-UID2, BCC0)
[01] * BA:AE:4F:81 (UID3-UID6)
[02] * DA 48 FF FF (BCC1, INT, LOCK0-LOCK1)
[03] * E1:10:12:0F (OTP0-OTP3)
[04] * 01 03 A0 0C |....|
[05] * 34 03 84 92 |4...|
[06] * 1C 40 61 70 |.@ap|
[07] * 70 6C 69 63 |plic|
[08] * 61 74 69 6F |atio|
[09] * 6E 2F 76 6E |n/vn|
[0A] * 64 2E 63 67 |d.cg|
[0B] * 61 2E 66 6C |a.fl|
[0C] * 65 78 5F 74 |ex_t|
[0D] * 61 67 56 73 |agVs|
[0E] * 47 4A 63 70 |GJcp|
[0F] * 5A 74 7A 33 |Ztz3|
[10] x 51 73 6A 49 |QsjI|
[11] x 67 49 4E 32 |gIN2|
[12] x 32 58 6F 76 |2Xov|
[13] x 72 2B 66 74 |r+ft|
[14] x 6E 67 6E 2B |ngn+|
[15] x 50 4E 4A 6E |PNJn|
[16] x 74 49 77 58 |tIwX|
[17] x 6E 54 58 36 |nTX6|
[18] x 75 45 4A 55 |uEJU|
[19] x 6B 77 59 79 |kwYy|
[1A] x 38 74 74 52 |8ttR|
[1B] x 61 2B 63 6A |a+cj|
[1C] x 65 6D 74 61 |emta|
[1D] x 32 2B 54 0F |2+T.|
[1E] x 13 61 6E 64 |.and|
[1F] x 72 6F 69 64 |roid|
[20] x 2E 63 6F 6D |.com|
[21] x 3A 70 6B 67 |:pkg|
[22] x 63 6F 6D 2E |com.|
[23] x 63 67 61 2E |cga.|
[24] x 66 6C 65 78 |flex|
[25] x 73 75 6D 6D |summ|
[26] x 61 72 79 FE |ary.|
[27] x 00 00 00 00 |....|
[28] . FF 0F 00 BD (LOCK2-LOCK4, CHK)
[29] . 04 00 00 FF (CFG, MIRROR, AUTH0)
[2A] . 00 05 -- -- (ACCESS)
[2B] +P FF FF FF FF (PWD0-PWD3)
[2C] +P 00 00 -- -- (PACK0-PACK1)

*:locked & blocked, x:locked,
+:blocked, .:un(b)locked, ?:unknown
r:readable (write-protected),
p:password protected, -:write-only
P:password protected write-only

--------------------------------------

[RoseanneParticipant]

@Richard the 4 tags I’m currently testing with, are all of NFC Forum Type 2 Tag. We use 203 and 213.

A full NFCTagInfoXP report was shared a month ago which shows details of an example tag which the Flomio Pro SDK was failing to read.

[RichardKeymaster]

Hi Roseanne, were you able to solve your issue?

[Author]

Posts