SICK SIG200 - Page 68

Command HTTP
method
Request JSON
body
Response JSON
body
Function
api/crown/ac/GetRest‐
DataIn
POST
(read)
"data": {"Offset":
0}
{
"header": {
"status": 0,
"message": "Ok"
},
"data": {"Value":
1024}
Returns a data
value that was
set as Logic Edi‐
tor input (“Offset”
selects data
value)
api/crown/ac/GetRest‐
DataOut
POST
(read)
"data": {"Offset":
0}
{
"header": {
"status": 0,
"message": "Ok"
},
"data": {"Value":
1024}
Returns a data
value that is a
Logic Editor out‐
put (“Offset”
selects data
value)
7.4.7 IO-link Device Communication
Access to connected IO-Link devices is also possible via REST API.
The namespace for accessing IO-Link devices on REST is “iolink/sickv1/”.
NOTE
The namespace does not include the default name “api”.
The access will be different depending on whether an IODD has been assigned to a
port or not. The following table shows the use cases:
Table 16: Use Cases
IODD assigned Correct IO-Link Device connected REST access
No Any Raw access
Yes As per IODD Access by name or Raw access
Yes Other than per IODD None
“Raw access” indicates that any data access to the connected IO-Link Device needs
implicit knowledge of the data:
•
Process data is returned as a byte array without details on the data structure
•
ISDU access is done by providing the index number and data is available as byte
array
NOTE
The available process data, index numbers, and data format is usually supplied by the
IO-Link Device manufacturer in the datasheet of the device.
Table 17: API version
Command HTTP
method
Request JSON body Response JSON
body
Function
iolink/sickv1/
apiversion
GET - 1 (no JSON nota‐
tion)
Returns version
of IO-Link API
The following table shows the access functions on REST in “Raw access”:
7
SIG200 CONFIGURATION
68
O P E R A T I N G I N S T R U C T I O N | Sensor Integration Gateway - SIG200 8017853/2019-06-06 | SICK
Subject to change without notice