Resource Description
/master/{masterNumber} /ports List of all available ports at a specific master
including port number, status information and
deviceAlias
/master/{masterNumber} /ports/{portNum‐
ber}
Addressing of a specific port connection at a
specific master
/devices Addressing of all connected devices at all mas‐
ters
/devices/{deviceAlias} Addressing a specific device via the device
name
/gateway
Additional resources are defined for the individual HTTP methods:
Table 29: Gateway Resource overview(/iolink/v1/gateway)
Resource HTTP
Method
Description
/identification GET Read out of identification data (e.g. MAC address or
serial number of the device)
/capabilities GET Information on device functions
/configuration GET Read out of device or Ethernet configuration (e.g.
DHCP or IP address)
/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 30: 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:
8
OPERATION
46
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 8027834./2022-06-10 | SICK
Subject to change without notice