User's Manual

© 2020 EnOcean | www.enocean.com PTM 210 / PTM 215 / PTM 215U / PTM 215J User Manual August 2020 | Page 27/45
USER MANUAL
PTM 210 / PTM 215 / PTM 215U / PTM 215J
DC Step code and later
5.3.1 Device Identification NDEF
The NDEF area contains a device identification string using the NDEF (NFC Data Exchange
Format) standard that is readable by most NFC-capable reader devices (including
smartphones).
The NDEF content can be read also by conventional NTAG commands, but this is then exe-
cuted in “binary” mode. The conversion to a string is achieved by applying UTF-8 decoding.
The contents of the NDEF container are defined by the EnOcean Alliance Labelling specifica-
tion. For more details please see [3].
An example device identification string from the NDEF area of a PTM 215 module could be:
6PENO+30S000012345678+1P000B00000053+30PS3001-A215+2PDC22+2Z01234567891234
+3C31+16S01000000
This NDEF string encodes the parameters shown in Table 5 below.
Identifier
Length of data (excl. identifier)
Value
6P
3 characters
Standard: “ENO”
30S
12 characters
EURID (6 byte, variable)
1P
12 characters
EnOcean Alliance Product ID
PTM 215: „000B00000053“
PTM 215U: „000B00000055“
PTM 215J: „000B00000057“
30P
10 characters
Ordering Code
PTM 215: “S3001-A215”
PTM 215U: “S3051-A215”
PTM 215J: “S3061-A215”
2P
4 characters
Step Code and Revision (“DC22”)
2Z
14 characters
NFC UID (14 byte, globally unique)
3C
2 characters
Header Start Address (“31” = 0x31)
16S
8 characters
SW Version
Example: 01000000 = 01.00.00.00
Table 5 – NDEF Parameters
5.3.2 User Information NDEF
The NDEF area allows the user to store a string of up to 64 characters starting at page 0x20
and ending at page 0x2F. The string is formatted in the UTF-8 encoding.
5.3.3 NFC Header
The NFC HEADER area contains information about the NFC memory structure and can there-
fore be used to distinguish between different NFC memory layouts. The start of the memory
is defined by the Header Start Address from the device identification NDEF, see 5.3.1 for
details.