SICK SIG200 - Page 64

Access is different depending on whether an IODD has been assigned to a port. The
table below lists the use cases:
Table 21: Application scenarios
IODD assigned Correct IO-Link device connected REST access
No Any Raw data access
Yes According to IODD Access by name or raw data access
Yes Other than according to IODD None
"Raw data access" means that implicit knowledge of the data is required for any access
to the connected IO-Link device:
•
Process data is returned as a byte array without details of the data structure.
•
ISDU access is done by providing the index number and the data is available as a
byte array.
NOTE
The available process data, index numbers and data format are usually specified by the
manufacturer of the IO-Link device in the device data sheet.
Table 22: API version
Command HTTP
method
JSON request part JSON response
part
Function
iolink/sickv1/
apiversion
GET - 1 (no JSON nota‐
tion)
Returns the ver‐
sion of the IO-
Link API.
The table below lists the access functions in REST for "raw data access":
Table 23: Functions in REST for “raw data access”
Command HTTP
method
JSON request
part
JSON response
part
Function
iolink/sickv1/apiversion GET - 1 (no JSON nota‐
tion)
Returns the
version of
the IO-Link
API.
7 SIG200 CONFIGURATION
64
O P E R A T I N G I N S T R U C T I O N | Sensor Integration Gateway - SIG200 8024482.1FJ7 /2022-05-31 | SICK
Subject to change without notice