Execute IO-Link Commands Through Explicit Messaging
The IO-Link master module allows you to define message instructions to use the IO-Link
Service Parameter object that is defined in the CIP Specification Volume 7C “Integration
of IO-Link Devices into the CIP Architecture” to Get or Set IO-Link parameters in the
IO-Link devices in either IO-Link data format or CIP data format.
The IO-Link master module supports two vendor-specific services in the IO-Link Service
Parameter object. Each of these services (Raw_Get and Raw_Set) can be used for parameter
access with or without subindex.
Service Code | Service Name | Description |
|---|---|---|
0x32 | Raw_Get | This service behaves the same as Raw_Get_Single if the
application path in the request contains a nonzero Attribute ID.
Otherwise it behaves the same as Raw_Get_All. |
0x33 | Raw_Set | This service behaves the same as Raw_Set_Single if the
application path in the request contains a nonzero Attribute ID.
Otherwise it behaves the same as Raw_Set_All. |
During IO-Link device operation, sending an excessive number of explicit messages might
cause a delay for IO-Link parameter Get or Set tasks for configuration or operation of
the IO-Link device. Periodic explicit messaging, for example, connected and cached
message instruction, is not recommended.
For connected messaging:
- Up to two concurrent Class 3 connections are supported for every IO-Link device.
- For extra Class 3 connection limitation that applies on the chassis level, see EtherNet/IP Network Devices User Manual, publication ENET-UM006.
For unconnected messaging:
- Up to two concurrent unconnected messages are supported for every IO-Link device.
- Up to 16 concurrent unconnected messages are supported for the IO-Link master module and all attached IO-Link devices.
To use explicit messaging with IO-Link devices, see Use Explicit Messages to Read and Write IO-Link Device Parameters.
Provide Feedback