I/O messaging
HarshIO module supports up to a maximum of 8 I/O connections. Fewer connections allow faster data I/O update rates (RPI value).
I/O Connections:
- HarshIO module supports 2 transport Class 1 I/O connections (Cyclic and Change-Of-State triggers):
o 1x Exclusive Owner
▪ Unicast or Multicast (TO) connection
▪ Unicast (OT) connection
o 7x Listen Only or Input Only (8 Input Only connection if no Exclusive Owner connection)
▪ Multicast or Unicast (TO) connection
Note!
Listen Only connection allows a second Ethernet/IP scanner connected to the network to listen the Input process data. For example, this feature is useful to share easily Inputs with a HMI/Scada application.
HarshIO 600 eIP • 35 • IP67 IO-Link Modules for EtherNet/IP
EtherNet/IP Assembly instances
The I/O process data are available through the EtherNet/IP assembly instances. Below the list according to the connection type.
If your EtherNet/IP scanner configuration tool does not support the management of EDS files, you may have to configure manually the assembly numbers to access the process data.
– Example of HarshIO assembly setting in Rockwell Automation RSLogix 5000 software –
HarshIO 600 eIP • 36 • IP67 IO-Link Modules for EtherNet/IP
Input process data mapping
Assembly #110 - Digital data + with no IO-Link data
Process Input Data (8 bytes)
SIx: SI - Standard Input data (x = Channel number) – Pin4 DIx: DI - Digital Input data (x = Channel number) – Pin2 PSx: Port Status (x = Port number) - state of the pin1 (L+) 1: short circuit detected
0: No default
UVx: Under Voltage (x = UL or UB) 1: Under voltage detected
0: No default
OVx: Over Voltage (x = UL or UB) 1: Over voltage detected
0: No default
OLx: Over Load (x = UL or UB) 1: Over load detected
0: No default
CSx: Channel Status (x = Channel number) – State of the Digital Output (DO – pin 2) or Standard Output (SO – pin 4)
1: short circuit detected 0: No default
IOLMx: IO-Link Communication Mode (x = Channel number) 0: IO-Link communication not activated
1: IO-Link communication activated
HarshIO 600 eIP • 37 • IP67 IO-Link Modules for EtherNet/IP
Assembly #111 - Digital data + with 4 bytes data per IO-Link device
Input Process Data (8 bytes)
Offset (in byte) per IO-Link channel
IO-Link Process Data (4 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
For Input Process Data information, refer to input assembly #110
IO-Link Input Process Data: Area where the IO-Link process data are mapped.
IOLS - IO-Link Communication Status with device
• 0 – Device is connected and no errors detected
• 1 – Device is not connected
• Other – Please contact tech support IOLD - IO-Link Data Valid
• 1 – Data is valid
• 0 – Data is invalid
IOL_LE_SC – IO-Link Last Event: Sequential Count
This parameter is the number of the latest IO-Link events. When a new event occurs, this counter is incremented by 1.
IOL_LE_EQ - IO-Link Last Event: Evt Qualifier
This parameter provides the instance, the source, the type and the mode of the event.
Refer to chapter IO-Link Events & errors codes IOL_LE_EC - IO-Link Last Event: Evt Code
This parameter provides the event code.Please refer to the specific IO-Link device data sheet for the definition of the event codes.
Refer to chapter IO-Link Events & errors codes
HarshIO 600 eIP • 38 • IP67 IO-Link Modules for EtherNet/IP
Assembly #112 - Digital data + with 8 bytes data per IO-Link device
Input Process Data (8 bytes)
Offset (in byte) per IO-Link channel IO-Link Process Data (8 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
For Input & IO-Link Process Data information, refer to input assembly #110 & assembly #111
Assembly #113 - Digital data + with 32 bytes data per IO-Link device
Input Process Data (32 bytes)
Offset (in byte) per IO-Link channel IO-Link Process Data (32 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
For Input & IO-Link Process Data information, refer to input assembly #110 & assembly #111
Warning!
If the IO-Link Input Process Data size configured (ex: 4 bytes) is lower than the IO-Link Input Process Data size of the connected IO-Link device (ex: 32 bytes), the EtherNet/IP connection will be established and the first 4 input bytes of data will be consumed.
HarshIO 600 eIP • 39 • IP67 IO-Link Modules for EtherNet/IP
Output process data mapping
Assembly #121 - Digital data + with 4 bytes data per IO-Link device
Output Process Data (4 bytes)
Offset (in byte) per IO-Link channel IO-Link Process Data (4 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
4 8 12 16 20 24 28 32 IO-Link Output Process Data (4bytes)
SOx: SO - Standard Output data (x = Channel number) – Pin4 DOx: DO - Digital Output data (x = Channel number) – Pin2
CSICx: Command to Switch an IO-Link port configured in IO-Link mode to SI mode (x = Channel number – Pin4). Refer to chapter SI with IO-Link.
• 0 – SI mode
• 1 – IO-Link mode
EFA: Electrical Fault Acknowledgement. This toggle bit is used to manually acknowledge the electrical fault.
Refer to configuration assembly #100 for Electrical Fault Acknowledgement Mode.
IO-Link Input Process Data: Area where the IO-Link process data are mapped.
Assembly #122 - Digital data + with 8 bytes data per IO-Link device
Output Process Data (4 bytes)
Offset (in byte) per IO-Link channel IO-Link Process Data (8 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
4 12 20 28 36 44 52 60 IO-Link Output Process Data (8 bytes)
For Output and IO-Link Process Data information, refer to output assembly #121 and assembly #122
Assembly #123 - Digital data + with 32 bytes data per IO-Link device
Output Process Data (4 bytes)
Offset (in byte) per IO-Link channel IO-Link Process Data (32 bytes)
C0 C2 C4 C6 C8 C10 C12 C14
4 36 68 100 132 164 196 228 IO-Link Output Process Data (32 bytes)
HarshIO 600 eIP • 40 • IP67 IO-Link Modules for EtherNet/IP For Output and IO-Link Process Data information, refer to output assembly #121 and assembly #122
Warning!
If the Link Output Process Data size configured (ex: 4 bytes) is lower than the IO-Link Output Process Data size of the connected IO-IO-Link device (ex: 32 bytes), the EtherNet/IP connection will be established and the first 4 output bytes of data will be produced.
Configuration data mapping
Assembly #100 - Configuration data
Process Input Data (4 bytes)
EFAM: Electrical Fault Acknowledgement Mode.
When an electrical fault occurs, the module provides a diagnosis about the event into the input assembly (byte offset 02/03/04/05) and applies a protection strategy on pin2, pin4 and pin1. (Refer to the chapter Protection Strategies on electrical fault).
0 = Automatic Acknowledgement and Notification only (NO)
If the electrical fault disappears, the module will automatically acknowledge the error and will remove the protection strategy and output values are restored.
1 = Manual Acknowledgement and Notification & Protection (NP)
If electrical fault disappears, the module will not automatically acknowledge the error. As soon as the user manually acknowledges the error (toggle bit “EFA”), the protection strategy is removed. Once done, it goes in normal mode and output values are restored.
Warning!
Some electrical faults cannot be manually acknowledged even if EFAM is set to 1.
Please refer to chapter Protection Strategies on electrical fault.
HarshIO 600 eIP • 41 • IP67 IO-Link Modules for EtherNet/IP GIF: Global Input filter
This parameter applies debounce filtering to all digital inputs (DI – Pin2) and prevents the processing of fast input state changes, like those caused by contact bouncing. Signal changes are ignored according to the filter time applied and is only registered when the changed polarity has remained fully stable over a given window time (every new change resets the filter timer).
0: 0ms 1: 1ms 2: 3ms 3: 5ms IO Mode
This parameter allows configuring the pin2 (channels number C1, C3, C5, C7, C9, C11, C13, C15) and the pin4 (channels number C0, C2, C4, C6, C8, C10, C12, C14)
For Pin2: For Pin4:
0 = Digital Input (DI) 0 = Standard Input (SI) 1 = Digital Output (DO) 1 = Standard Output (SO)
2 = Extended Power Supply 2 = Standard Input with IO-Link (Refer to chapter SI with IO-Link) 3 = IO-Link
Note!
“Power Supply” on Pin2 is a 24 voltage applied continuously after the EtherNet/IP connection. It allows to power up the Molex IO-Link hub 8D0P-808 and TEDIO-8B4P-808.
DO / SO Fail-Safe Mode
This parameter is used for setting the fail-safe value behavior of Digital Output (DO) configured on Pin#2 and of Standard Digital Output (SO) configured on Pin4.
Fail-safe value will be applied in the below conditions:
- When the Scanner is switched from RUN to PROG (IDLE mode)
- In the event of loss of bus communication (Cable disconnected, connectionTime-out, inhibit mode…) 0 = Reset to 0
1 = Hold Output State. When the communication failure occurs, the output remains in the last state sent by the PLC
Note!
If Pin#2 is defined as Extended Power Supply, the fail-safe mode will be ignored (Fail-safe value not applied).
Note!
If the IO-Link port is in operate mode while the fail-safe mode is triggered, the IO-Link device will apply its own fail-safe mode. Invalid data status will be indicated into the Input assembly.
DI / SI Invert
This parameter changes the polarity of the digital inputs. Therefore, the Input Process Data will also report this inversion.
It could be used to treat normally close sensors in positive logic.
0 = Normal 1 = Inverted
HarshIO 600 eIP • 42 • IP67 IO-Link Modules for EtherNet/IP ID Validation and Data Storage Modes
Please refer to the chapters ID Validation and Data Storage.
IO-Link provides three levels for the validation of the identity of an IO-Link Device per IO-Link port before establishing the IO-Link connection.
o None: no ID checking
o Compatible: Vendor ID / Device ID checking
o Identical: Vendor ID / Device ID / Serial number checking
The Data Storage mode is used to define the parametrization strategy in case of replacement.
o Restore: The parameter data are sent from the IO-Link Master to the device o Backup + Restore: The parameter data can be updated in both directions Possible values are:
0: None 1: Compatible
2: Compatible with Backup & Restore (Data Storage enabled) 3: Compatible with Restore (Data Storage enabled)
4: Identical
5: Identical with Backup & Restore (Data Storage enabled) 6: Identical with Restore (Data Storage enabled)
VendorID / Device ID
This is the Vendor ID / Device ID of the connected IO-Link device.
Refer to the chapter ID Validation Direct Param Page2 Enable (DPP2)
This parameter is a parametrization method for IO‐Link device with specifications V1.0. It enables the data transfer of the Direct Parameter Page 2 to the IO‐Link device.
If validation mode is enabled, DDP2 will be transferred to the IO‐Link device only if the validation is successful.
Possible values are:
0: Not enabled 1: Enabled Direct Param Page2
The DPP2 describes the area between the IO-Link objects 10hex … 1Fhex. This is a manufacturer specific range of IO-Link device parameter data. Please refer to the manufacturer user’s manual.
DPP2 Data is an area of 16 Bytes that will be sent in case of DDP2 Enable set from the IO-Link Master to the IO-Link device at each connection.
Note!
For ease of programming in Studio 5000, Molex provides an AOI (Add-On-Instruction) to use pre-named tags instead of using Generic tags. Please refer to chapter Rockwell Studio 5000.
HarshIO 600 eIP • 43 • IP67 IO-Link Modules for EtherNet/IP