
Resource
HTTP
Method
Description
/configuration
POST
Writing of device or Ethernet configuration
/masters
In principle, more than one IO-Link Master can be addressed via a gateway. The differ‐
ent masters are numbered consecutively in the request, starting with 1 for the first
master.
NOTE
The {masterNumber} variable is always 1, because the SIG350 gateway has only one
master.
Further resources are also available here:
Table 13: Overview of the master resource
(/iolink/v1/masters/1)
Resource
HTTP
Method
Description
/capabilities
GET
Read out of functions of the specific IO-Link Master
(e.g. the number of ports or the maximum voltage
supply)
/identification
GET
Read out of identification data of the specific IO-
Link Master (e.g. vendor ID, serial number or firm‐
ware version)
/identification
POST
Writing of identification data of the specific master
(e.g. LocationTag, functionTag)
/masters/{masterNumber}/ports
With the following resources, additional information of the individual ports at a specific
master can be called up:
Table 14: Overview of the port resource
(/iolink/v1/masters/1/ports)
Resource
HTTP
Method
Description
/capabilities
GET
Read out of functions of the specific port (e.g. port
type or max. voltage supply)
/status
GET
Read out of current status of a specific port (e.g.
deactivated or the IO-Link version of the connected
IO-Link device)
/configuration
GET
Read out of configuration of a specific port (e.g.
cycle time or deviceAlias of the connected IO-Link
device)
/configuration
POST
Writing of configuration on a specific port (e.g. devi‐
ceAlias)
/datastorage
GET
Read out of Data Storage object
/datastorage
POST
Writing of Data Storage object
/devices
The connected devices are addressed via the deviceAlias. If no deviceAlias is defined,
then the default value (e.g. master1port6) is used.
Example:
An IO-Link device with deviceAlias “sensor34” is connected to port 6. The addressing is
performed with the request
GET/iolink/v1/devices/sensor34/identification
OPERATION
8
8027836./2022-06-10 | SICK
O P E R A T I N G I N S T R U C T I O N S | Sensor Integration Gateway - SIG350
41
Subject to change without notice