Command
HTTP
method
JSON request
part
JSON response
part
Function
iolink/sickv1 / readPort
(ISDU data)
POST
{
"header": {
"portNumber": 0
},
"data": {
"index":24
}
}
{
"header": {
"status": 0,
"message": "Ok"
},
"data": {
"24": [
42,
42,
42,
42,
42,
42
]
}
}
Returns the
raw parame‐
ter data of a
connected
IO-Link
device.
portNumber:
0 = Port 1, 1
= Port 2, 2 =
Port 3, 3 =
Port 4
index: ISDU
number
data: Byte
array of the
parameter
data
iolink/sickv1 / writePort
(ISDU data)
POST
{
"header": {
"portNumber": 0
},
"data": {
"24": [
49,
50,
51,
52
]
}
}
{
"header": {
"status": 0,
"message": "Ok"
}
}
Sets the raw
parameter
data of a
connected
IO-Link
device.
portNumber:
0 = Port 1, 1
= Port 2, 2 =
Port 3, 3 =
Port 4
data: Empty
member for
ISDU num‐
ber, followed
by the byte
array of the
parameter
data
NOTE
“Raw data access" is also available when an IODD is assigned.
"Access by name" means that data access to the connected IO-Link device is extended
by metadata:
•
Process data is returned segmented and displayed according to the definition in
the IODD file.
•
ISDU access is performed by variable ID and the data is represented according to
the definition in the IODD file.
Below is an example from the SIG100 IODD:
<Datatype
</Variable>
SIG200 CONFIGURATION
7
8017853.1D0S/2021-11-04 | SICK
O P E R A T I N G I N S T R U C T I O N | Sensor Integration Gateway - SIG200
99
Subject to change without notice
