SATO CL4NX Programming Reference Manual page 396

Parameters related to NFC(NDEF) support (omissible)
nfc: NFC(NDEF) support
Detailed parameters of NFC(NDEF) support (omissible)
ndf: Specifying NFC(NDEF) format
spl: Specify format of detailed record
ptl: Protocol
ecd: Character code
lgc:
Language code
idt:
Icon data type
ndd: Write user data
ver: Version
hma: MAC Address for handover
Use for handling record with NDEF (NFC Data Exchange Format) stipulated
by NFC Forum.
※Set to respond as NFC Type3 Tag.
Specify 1 to enable NFC support or 0 to disable NFC support.
Valid range: 0 ~ 1
Specify this parameter when you set data in NDEF(NFC Data Exchange
Format) format stipulated by NFC forum.
Valid range：1～6
1: user data is regarded as URI format.
2: user data is regarded as TEXT format.
3: user data is regarded as smart poster format.
4: user data is regarded as handover (Bluetooth) format.
5: user data is regarded as handover (Wi-Fi) format.
6: user data is regarded as handover (mixture of Bluetooth/Wi-Fi) format.
Furthermore, specify the user data format in the case of ndf:3.
Valid range：1～4
1: treats user data as URI record
2: treats user data as title(TEXT) record
3: treats user data as action record
4: treats user data as icon Record
*For smart poster, make sure to specify the URI record. As other records are
treated as options, specify if necessary.
For ndf:1 or ndf:3 (spl:1), specify the protocol (scheme) corresponding
number to 1~3 digit decimal.
The valid range is 1~255 (refer to the table of "Setting value of protocol (ptl:)"
in 16.10(14443 TypeA<RK>)).
※Considering the extensibility of the function, only the valid range is checked
instead of its content.
For ndf:2 or ndf:3 (spl:2), specify the character code.
Valid range 0～1
0:UTF-8
1:UTF-16
For ndf:2 or ndf:3 (spl:2), specify the name that complies with RFC5646 to
2~63 digit.
Usable characters are 0~9, A~Z, a~z and - (hyphen).
E.g.: French(fr), Japanese (ja), English (en), American English (en-US)
For ndf:3 (spl:4), specify the icon data type to MIME type that complies with
RFC2046. 1 ~ 64 digits.
E.g.: PNG image⇒[image/png]
Specify user data. Command error will occur if this is not specified. The size
information for the data area is required before the data. For example, if the
data size was 64, it should be specified as ndd:64,abcde...
ndf: spl: Setting value
1 - Specify the resource with UTF-8 character code.
3 1
2 - Specify any string. Specify with consideration of
character code and language code.
3 2
3 3 Specify the following value:
Valid range：0～2
0:Do the action
(Send SMS to start browser)
1:Save for later (Save process)
2:Open for editing (SMS, UR edit)
3 4 Specify the icon data (binary data) to hexadecimal
which digit is 2's multiples.
For ndf:4～6, specify the handover version number to decimal.
Specify major and minor numbers delimited by a period character. For
example, specify as ver:2.1 if the major number is 2 and minor number is
1.
Note: It is possible to specify 2 versions when ndf:6. One will be reflected to
Bluetooth record, and the other will be reflected to Wi-Fi record. The version
will not be reflected to Wi-Fi record if you have specified only one.
For ndf:4～6, specify the MAC address to a fixed 12-digit hexadecimal.
Note: It is possible to specify 2 MAC addresses when ndf:6. One will be
reflected to Bluetooth record, and the other will be reflected to Wi-Fi record.
The version will not be reflected to Wi-Fi record if you have specified only
one.
388