V01.00 | 2019/12
113
10.4.2 Diagnostic telegram
Channel Byte no. Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
V1 V1 overcurrent diagnostics
0 - - - - ERR ch3 ERR ch2 ERR ch1 ERR ch0
1 - - - - - - - -
IO-Link Device diagnostic messages Master diagnostics
IO-Link port 1 0 EVT1 EVT2 PD_INV HW_ERR DS_ERR CFG_ERR PPE -
1 GEN_ERR OLV V_HIGH V_LOW ULVE LLVU OTEMP PRM_ERR
IO-Link port 2 2…3 Assignment similar to IO-Link port 1
IO-Link port 3 4…5
IO-Link port 4 6…7
NOTE
The process data invalid diagnostic (PDINV) can be sent from both devices, IO-Link
master or IO-Link device.
Meaning of Diagnostic Bits
Bit Meaning
IOL as digital input or digital output
ERR Chx Error at channel
IO-Link master diagnostics
CFGER Wrong or missing device
The connected device does not match the channel configuration or there is no
device connected to the channel. This diagnostic message depends on the paramet-
erization of the channel.
DSER Data storage error
Possible causes:
n Data storage mismatch:
IO-Link device in accordance with IO-Link V1.0 connected.
The data storage buffer contains data of another device.
n Overflow of the data storage buffer
n The connected device may be locked for parameter changes or for data storage.
PPE Port parameterization
The port parameters are inconsistent. The device parameterization via GSD is active,
but not working.
Possible causes:
n The IO-Link-master did not receive GSDML-parameters for a connected device.
The connected device was not parameterized by a PROFINET PLC via GSDML.
n The port is in operation mode "IO-Link without validation" or "DI". These modes
do not allow parameterization via GSDL file.
n Data storage mode is active. The parameter is not set to "deactivated, clear". A
device parameterization via GSDML is not possible with activated data storage.
n Vendor or Device ID are "0". The connected device can not be identified and is
thus not parameterizable.
To Next Page
Loading...
