Table 25: Structure of a write ISDU response – negative response
Name Value Type Description
CIP Data CIP/Error
code
UINT IO-Link Master Error
USINT IO-Link Device Error
USINT IO-Link Device Additional Error
Overview of CIP status code
The following table describes the parameters that come back:
Table 26: CIP status code
CIP status Description
0 (0x00) Success.Service was successfully performed.
5 (0x05)
Path destination unknown.Addressed CIP Class or CIP Instance is not
known.
8 (0x08)
Service not supported.The requested service is not implemented or was not
defined for this Object Class/Instance.
19 (0x13)
Not enough data.The service did not supply enough data to perform the
specified operation.
20 (0x14)
Attribute not supported.The attribute specified in the request is not sup‐
ported.
21 (0x15) Too much data.The service supplied more data than was expected.
30 (0x1E)
An embedded service resulted in an error.The IO-Link specific error codes
within the CIP response
8.1.2 Function blocks
8.1.2.1 MSG box
The IO-Link device parameter object can be accessed via the MSG box. For
this purpose, the service code, class and instance must be entered according to
section 8.1.1.5.1. The instance corresponds to IO-Link port S1...S8. In addition, the
data sources (Source Element, Destination Element) must be specified. The first 2
bytes of the Source Element determine the index and the 3rd byte the subindex. The
following data contains the payload to be transmitted. It is important to note that the
source length corresponds to the byte length of the corresponding IO-Link parameter or
at least 3 bytes for reading (index + subindex).
The path to the SIG350 must be selected in the Communication tab.
8 OPERATION
42
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
To Next Page
Loading...
