65
Access data of the UHF ID tag
The following services allow the access to the UHF ID tags.
Read EPC data of UHF ID tags
Service available
: DTE805, DTE9x5
This service is supported in the channel mode "RWH"
Method: POST
URL:
Request body data:
{"
code
": "request", "
cid
": 3001, "
adr
": "data/port[1]/rfid//id_tag_list/epcs/getdata","
reply
":"
reply text
"}
Request
element
Value
Remark
code
"request"
-
cid
<CorrID>
Correlation identifier.
Can be set from 0…32767
e.g. 3001
adr
"data/port[
N
]/rfid/id_tag_list/epcs/getdata"
"
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"
Response data:
{"
cid
":3001,"
data
":{"value":"[\"e008010c38325124\",\"e008010c38325125\"]"},"
adr
":"reply text","
code
":200}
Response
element
Value
Remark
cid
<CorrID>
Correlation identifier.
Same as send in request. e.g. 3001
data
{"value":"[<string1>,<string2>,….,<stringN>]"}
The string elements are coded as 2 characters
in ASCII hex data.
e.g.
\"
e008010c38325124
\
",
\
"e008010c38325125
\
"
adr
"reply text"
Optional:
Text sent in element "reply" of the service
request.
e.g. "reply text"
code
200
Response code of the IoT core
See chapter ->
e.g. 200
Note: <string> elements are separated by \" delimiters to show the elements are different string objects.
