63
Read User memory of HF ID tags
Service available
: DTE105, DTE605
This service is supported in the channel mode "RWH"
Method: POST
URL:
Request body data:
{ "
code
":"request","
cid
": 1002,"
adr
": "data/port[1]/rfid/id_tag/user_data/getblobdata","
reply
": "
reply text
",
"
data
": { "pos": 0, "length": 16 } }
Request
element
Value
Remark
code
"request"
-
cid
<CorrID>
Correlation identifier.
Can be set from 0…32767, e.g. 1002
adr
"data/port[
N
]/rfid/id_tag/user_data/getblobdata"
For DTE10x :
N
= 1…4
For DTE60x, DTE80x, DTE9Xx:
N
= 1, e.g. 1
reply
"<string>"
Optional:
Text to be send back in the response.
If not needed, this element can be removed
from the request, e.g. "reply text"
data
"pos": <offset>
"length": <data_length>
Offset position in buffer [bytes] : 0…65535
e.g. 0
Length of data to be read [bytes] : 1…65534
e.g. 16
Note: getblobdata = "
Get
B
inary
L
arge
OB
ject
Data
"
Response data:
{"cid":
1002
,"data":{"data":"UGxhbnQtQTFfMDEyMzQ1Ng=="},"code":200}
Respons
e
element
Value
Remark
cid
<CorrID>
Correlation identifier.
Same as send in request. e.g. 1002
data
"data":"<string64>"
(1)
or
"error": "6469616700"
The ‘data’ string element is
Base64
encoded.
e.g. "UGxhbnQtQTFfMDEyMzQ1Ng=="
or
Message "Err"
adr
<string>
Optional.
Text sent in element "reply" of the service request
e.g. "
reply text"
code
<status code>
Response code of the IoT core
See chapter ->
(1)
Data on the ID tag:
Base64: UGxhbnQtQTFfMDEyMzQ1Ng==
ASCII:
Plant-A1_0123456
HEX: 506C616E742D41315F30313233343536