User manual | Festo CTEU-EP, CPX-FB36, CPX-CTEL-LK EtherNet/IP IO-Link Integration Application Note
Add to My manuals30 Pages
The CTEU-EP, CPX-FB36, and CPX-CTEL-LK are Festo products that support the ability to add 3rd party IO-Link devices. These devices can be used to control various types of sensors and actuators, such as RFID readers, light stacks, and other IO-link devices. The application note provides detailed information on how to configure and use these products, including information on how to validate the IO-link devices, how to read diagnostics events, and how to set IO-link parameters.
advertisement
Application Note
EtherNet/IP IO-Link Integration
Controlling IO-Link Devices with Festo EtherNet/IP Products CTEU-EP,
CPX-FB36,
CPX-CTEL-LK
100116
Title ........................................................................................................................ EtherNet/IP IO-Link Integration
Version ............................................................................................................................................................. 1.30
Document no. .............................................................................................................................................. 100116
Original .................................................................................................................................................................en
Author ............................................................................................................................................................. Festo
Last saved ............................................................................................................................................ 21.12.2016
Copyright Notice
This documentation is the intellectual property of Festo AG & Co. KG, which also has the exclusive copyright. Any modification of the content, duplication or reprinting of this documentation as well as distribution to third parties can only be made with the express consent of Festo AG & Co. KG.
Festo AG & Co KG reserves the right to make modifications to this document in whole or in part. All brand and product names are trademarks or registered trademarks of their respective owners.
Legal Notice
Hardware, software, operating systems and drivers may only be used for the applications described and only in conjunction with components recommended by Festo AG & Co. KG.
Festo AG & Co. KG does not accept any liability for damages arising from the use of any incorrect or incomplete information contained in this documentation or any information missing therefrom.
Defects resulting from the improper handling of devices and modules are excluded from the warranty.
The data and information specified in this document should not be used for the implementation of safety functions relating to the protection of personnel and machinery.
No liability is accepted for claims for damages arising from a failure or functional defect. In other respects, the regulations with regard to liability from the terms and conditions of delivery, payment and use of software of
Festo AG & Co. KG, which can be found at www.festo.com and can be supplied on request, shall apply.
All data contained in this document do not represent guaranteed specifications, particularly with regard to functionality, condition or quality, in the legal sense.
The information in this document serves only as basic information for the implementation of a specific, hypothetical application and is in no way intended as a substitute for the operating instructions of the respective manufacturers and the design and testing of the respective application by the user.
The operating instructions for Festo products can be found at www.festo.com.
Users of this document (application note) must verify that all functions described here also work correctly in the application. By reading this document and adhering to the specifications contained therein, users are also solely responsible for their own application.
(Festo AG & CO. KG, D-73726 Esslingen, 2016)
Internet: http://www.festo.com
E-Mail: [email protected]
Table of contents
Components/Software used
1
Type
Components/Software used
Name Version Software/Firmware
Bus node
Bus node
Electrical Interface
Electrical sub-base
Software
Software
Table 1.1: Components/Software used
CTEU-EP
CPX-FB36
CPX-CTEL-2-M12-5POL-LK
R3
R12
R3
CAPC-F1-E-M12 --
STUDIO 5000, Rockwell Automation Rev 28
CPX-FMT V 4.21.203
Seite 4 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Introduction
2 Introduction
The CPX-FB36 and CTEU-EP EtherNet/IP busnodes both support the ability to add 3rd party IO-Link devices.
Therefore, additional products such as RFID readers, Light stacks, and any other IO-link devices can be added to
CPX or CTEU with EtherNet/IP.
These features, for supporting IO-Link, are only roughly documented in the standard manuals. This application note is intended to support these additional features. These specifically include; how to validate the IO-link devices, how to read diagnostics events, and how to set IO-link parameters. Details of the various objects required for these functions are documented below.
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 5 von 30
3
Setup of Process data for IO-Link Devices
3 Setup of Process data for IO-Link Devices
Follow the instructions from the standard manuals for CPX-FB36 or CTEU-EP for the basic setup of the I/O-Devices in your Engineering Software. The following examples are showing the typical integration in the “Studio
5000” Engineering Software provided by Rockwell Automation.
3.1 Typical Configuration of CPX-FB36 with CPX-CTEL-LK
Note
There must be at least one CPX-CTEL-LK module in the CPX terminal
• The I/O-size of the CPX-CTEL-LK module has to be large enough to hold the data of the connected
IO-Link devices. Refer to the CPX-CTEL-LK manual for details on the corresponding settings of the
DIL switches
Seite 6 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
3
3
Setup of Process data for IO-Link Devices
3.2 Typical Configuration of CTEU-EP
Below is an example with a fixed dual port configuration with a separate status for the CTEU-EP bus node. This allows for maximum device type size, and keeps the I/O in equal sizes.
Informationen
The shown configuration also adds an additional Status-Byte for diagnostics without the need to change the default DIL-Switch settings by using
Comm. Format “Data – SINT – With Status”
and assembly instance 103 as
Status Input
.
Note
• The CTEU-EP must be configured with an assembly instance large enough for the IO-link device.
Refer to the CTEU-EP manual. The size of the IO data determined by the assembly instances must also be large enough for the IO-link device.
• The I/O-size of the CPX-CTEL-LK module has to be large enough to hold the data of the connected
IO-Link devices. Refer to the CPX-CTEL-LK manual for details on the corresponding settings of the
DIL switches
Note
In both, the CPX and CTEU, the process data will be automatically transferred to the device. However, due to the little-endian / big-endian difference in EtherNet/IP vs. IO-Link, the byte order will be swapped. This must be handled in the controller logic.
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 7 von 30
Web Server Support for IO-Link Devices
4 Web Server Support for IO-Link Devices
For both the CPX-FB36 and the CTEU-EP, there are IT tools available for reading the diagnostics and status of IOlink devices.
4.1 CPX-FB36 with CPX-CTEL-LK
For the CPX-FB36, a web server and the Festo Maintenance Tool both display the relevant IO-link device information and diagnostics.
Figure 1: CPX I-Port Master for IO-Link devices – Diagnosis via Web Server
Seite 8 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Web Server Support for IO-Link Devices
Figure 2: CPX I-Port Master for IO-Link devices – Diagnosis via FMT
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 9 von 30
Web Server Support for IO-Link Devices
4.2 CTEU-EP
For the CTEU-EP, there is a Web server available to display the relevant IO-Link status and diagnostics:
Figure 3: The CTEU web-server will show the IO-Link devices connected
Seite 10 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Methods for Validating the IO-Link Configuration
5 Methods for Validating the IO-Link Configuration
For a customer to validate a configuration, he must retrieve the vendor and device ID manually via an explicit message. This will assure the correct device is connected to an IO-link port.
5.1 CPX-FB36
For the FB36, the General Object Parameter Object 101d will be used. This currently exists in the CPX system since these values are stored as parameters from the CTEL-LK. An explicit message to Object class 101 with the correct instance and attribute based on the channel & slot number will work.
Figure 4: This ladder example will retrieve the Vendor ID of a device in port 2 of the CTEL-LK plugged into the
5th CPX slot.
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
CIP Generic CIP-specific message
Get Attribute Single Read only access to single CIP attribute -> Service Code “e”
65 h / 101 d
6 d
CIP-Class-ID to access CPX-Parameter-Object
Slot number where CTEL-LK resides + 1
Possible Values: 1-10 d
In the example a value of 6d means CPX module number 5
73 h / 115 d Service-Data: Vendor ID Port 2, Word
Possible Values Service Data
71 h / 113 d
73 h / 115 d b5 h / 181 d b8 h / 184 d
7b h / 123 d
7d h / 125 d
Vendor ID Port 1, Word
Vendor ID Port 2, Word
Device ID Port 1, DWord*
Device ID Port 1 DWord*
Errorcode Port 1, Word
Errorcode Port 2, Word
*Mask MSB when accessing Device ID
Table 5.1: Service code table to Read Device Type and Vendor ID to CPX-FB36
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 11 von 30
Methods for Validating the IO-Link Configuration
5.2 CTEU
First, each of the CTEU ports must be set to allow 3 rd party IO-link devices. Use the CTEU
Port Configuration Object 107d. The details are as follows:
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
CIP Generic CIP-specific message
Set Attribute Single Write access to single CIP attribute -> Service Code “10h”
6B h / 107 d Vendor-specific object for IO-Link Ports
1, 2
5
Port 1 or 2
(Port 2 only available when using CAPC Adapter)
Service-Data: IO-Link support, SINT
Possible Values Comment
0
1
Disable IO-Link Support (Default)
Enable IO-Link Support for 3 rd Party
Table 5.2: CTEU Service code table to Set IO-Link mode
Next, the CTEU Slave Information Object 104d will be used. This object stores device information for each of the
2 CTEU ports. An explicit message to Object class 104d with the correct instance and attribute based on port 1 or
2 will allow the user to retrieve the Vendor or Device ID.
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
CIP Generic
Get Attribute Single Read only access to single CIP attribute -> Service Code “e”
68 h / 104 d
1, 2
6
2
CIP-specific message
CIP-Class-ID for Slave-Information-Object
Port 1 or 2
(Port 2 only available when using CAPC Adapter)
Service-Data: Vendor ID,
Possible Values Service-Data:
6
2
Vendor ID, 2 Bytes (UINT)
Device ID, 3 Bytes (DWord)*
*Mask MSB when accessing Device ID
Table 5.3: Service code table to Read Device Type and Vendor ID from CTEU-EP Slave Information Object
Seite 12 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Diagnostic Reporting:
6 Diagnostic Reporting:
Both the CPX and CTEU can be programmed in advance to detect and report errors related to the IO-link channels and devices. This includes if a device is missing, changed, or faulted.
This is generally a 3 step process:
1. Write the specific information to a “Port Configuration Object” via an explicit message. The data will be the
Vendor ID and the Device ID plugged into each port.
2. Monitor general diagnostics provided by the CPX or CTEU either from the input table or status table.
3. Read specific error information from a CIP object via an explicit message.
The next chapters describe in detail how these 3 steps apply to CPX-FB36 und CTEU-EP.
6.1 CPX-FB36
6.1.1 Step 1: Set VendorID and DeviceID
Use the following table to write the specific device information to the FB36 IO-Link Port Configuration Object
140d.:
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
CIP Generic
Set Attribute Single
8C h / 140 d
0-10
1-2
Source Element Tag of user defined type
(see details below)
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
CIP-Class-ID for vendor specific „IO-Link Port Configuration
Object“ to set IO-Link Device Type.
Slot number where CTEL-LK resides + 1
Possible Values: 1-10 d
Channel of Device (Port of CPX-CTEL-LK where device is connected)
Possible values: 1 – 2
Data Order of user defined data-type:
Master Cycle Time (SINT)
Comm_Error (SINT)
VendorID (INT)
DeviceID (DINT)
0 (Default)
0, 1
Device specific
Device specific
Source Length 8 Bytes
Table 6.1: CPX-FB36 Service code table to Write to IO-Link Port Configuration Object
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 13 von 30
Diagnostic Reporting:
Since this object requires access to a data structure, this example will show how to enter the service data for an
IO-Link device in the Rockwell Logix environment with a CPX-FB36 /CPX-CTEL-LK:
1. Create a user Defined Data Type to include these 4 variables:
Figure 6.1
2. Create Controller Tags to be used as a source and destination for a message instruction to write / read to the module. The variables are of the data type created. Load the source data with the appropriate data for the
IO-Link device.
3. Use a MSG instruction to load the data to the FB36 so the Vendor ID, Device ID, and choice to monitor the
Comm_Error are entered. Instance 6 means CPX module number 5, and attribute 1 is for CPX-CTEL-LK channel
1.
Figure 6.2
Seite 14 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Diagnostic Reporting:
4. The data can be read in a similar manner using a Get Attribute Single service type in a separate MSG instruction. Copy the data to a destination element of the same data type.
6.1.2 Step 2: Monitor Diagnostics
Monitor basic CPX diagnostics, a fault with bits 3 (fault at function module) and 7 (other fault) of the CPX diagnostic byte should occur.
6.1.3 Step 3: Read Specific Error Information
Use the General Module Parameter Object 101d to read the specific error codes form the CPX-FB36 / CPX-CTEL-
LK. This is the same object as used to validate the IO-link device, however, in this case, use an explicit message to read attribute 7B or 7D for specific error codes of port 1 or 2 respectively.
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
Source Element
CIP Generic CIP-specific message
Get Attribute Single Read only access to single CIP attribute -> Service Code “e”
65 h / 101 d CIP-Class-ID to access CPX-Parameter-Object
6 d
73 h / 115 d
Slot number where CTEL-LK resides + 1
Possible Values: 1-10 d
In the example a value of 6d means CPX module number 5
Service-Data: Vendor ID Port 2, Word
Tag
Possible Values
71 h / 113 d
73 h / 115 d b5 h / 181 d b8 h / 184 d
7b h / 123 d
7d h / 125 d
Service Data
Vendor ID Port 1, WORD
Vendor ID Port 2, Word
Device ID Port 1, DWord*
Device ID Port 1 DWord*
Errorcode Port 1, Word
Errorcode Port 2, Word
*Mask MSB when accessing Device ID
Datatype of Tag Source Length Attribute
VendorID
ErrorCode
DeviceID
INT
INT
DINT*
2
2
4
Table 6.2: Service code table to Read Error code from CPX-FB36
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 15 von 30
Diagnostic Reporting:
6.2 CTEU-EP
6.2.1 Step 1: Set VendorID and DeviceID
Use the following table to write the specific device information to the
CTEU Port Configuration Object 107d. The details are as follows:
Parameter Value Description
Message Type
Service Type
Class
Instance
Attribute
Source Element
CIP Generic CIP-specific message
Set Attribute Single Write access to single CIP attribute -> Service Code “10h”
6B h / 107 d Vendor-specific object for IO-Link Ports
1, 2
6 or 7
Port 1 or 2
(Port 2 only available when using CAPC Adapter)
Service-Data:
Tag
6
7
Expected Vendor ID (INT)
Expected Device ID (DINT*)
Attribute
*Mask MSB when accessing Device ID
Datatype of Tag
Expected VendorID INT
Source Length
2
Expected DeviceID DINT* 4
Table 6.3: For CTEU Service code table to Write Device Type and Vendor ID
6.2.2 Step 2: Monitor Diagnostics
Monitor basic CTEU diagnostics for a fault with an I-port channel.
Seite 16 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Diagnostic Reporting:
6.2.3 Step 3: Read Specific Error Information
Use the Status Object 103d to read the specific error codes from the CTEU.
Parameter Value Description
Message Type
Service Type
Class
Instance
CIP Generic CIP-specific message
Set Attribute Single Write access to single CIP attribute -> Service Code “10h”
67h / 103d CIP-Class-ID for vendor specific „Status Object”
1,2 Port 1 or 2
(Port 2 only available when using CAPC Adapter)
Attribute 5
Source Element Tag of type INT
Port status
Attribute
Port Status
Datatype of Tag
INT
Source Length
2
8
9
10
5
6
7
0
1
2
3
4
Table 6.4: Service code table to Read Error from IO-Link device with CTEU-EP
“Port Status” is a bitfield with the following meaning:
Bit Description no device connected device initializing device is operational error in device
Port stopped
Port disabled device reinitialized short circuit on I-Port reserved
Port unused
Port used, but configured as empty
Table 6.5: Description of Port Status
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 17 von 30
Parameterize via Mailbox Function:
7 Parameterize via Mailbox Function:
IO-Link Device parameters are accessed via the ISDU Access Object 768d.
This object exists in both the CPX-FB36 and the CTEU-EP. It is handled exactly the same in either case.
Informationen
“ISDU-Access” (Index Service Data Unit Access) is the mechanism used for accessing data objects in all IO-Link devices.
The parameters are device specific, and can be both read / write. The user shall use a MSG instruction to access these parameters. This is known as the “Mailbox Function”. Since the MSG instruction must use the source element for the index number, one index at a time can be accessed.
The following tables show the general Mailbox Function message instruction requirements:
Parameter Value Description
Message Type CIP Generic
Service Type Custom
Service Code
Class
Instance
32 h / 50 d
300 h / 768 d
1-2
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Read ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Port where device is connected
Attribute 0-9 or
0
Source Element Tag of user defined type
CPX slot number of CPX-CTEL-LK module or
0 in case of CTEU-EP
Data Order of user defined data-type:
Index (INT) 0...65535
Subindex (SINT) 0...255
Source Length 3
Destination Element
Source Length is always “3” for read access.
Tag of SINT[1+n] Response to read access
Status (SINT)
Data 0(SINT)
Status / Errorcode of read request, see table below
Byte 0 read from device
Data 1(SINT)
Data n(SINT)
Byte 1 read from device
Byte n read from device
Table 7.1: Message Instruction for ISDU Access (read)
Parameter Value Description
Message Type
Service Type
Service Code
Class
Instance
Attribute
CIP Generic
Custom
33h / 51 d
300 h / 768 d
1-2
0-9 or
0
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Write ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Port where device is connected
CPX slot number of CPX-CTEL-LK module or
0 in case of CTEU-EP
Seite 18 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Parameterize via Mailbox Function:
Parameter
Source Element Tag of user
Source Length
Destination Element
Value defined type
3 + “Length of
Data” Bytes
SINT
Description
Data Order of user defined data-type:
Index (INT)
Subindex (SINT)
Data 0 (write only)
0...65535
0...255
Data 1(write only)
Data n (write only)
Byte 0 of data to write to ISDU addressed by Index and Subindex
Byte 1 of data to write to ISDU addressed by Index and Subindex
Byte n of data to write to ISDU addressed by Index and Subindex
When writing 4 Bytes of data to an ISDU, then Source Length is 3+4=7
Bytes.
Response to write access
Status (SINT) Status / Errorcode of write request, see table below
Table 7.2: Message Instruction for ISDU Access (write)
Response Status Description
E5 h
E6 h
E7 h
E8 h
E9 h
FF h
0
E1 h
E2 h
E3 h
E4 h
Success
Write data length too long
Port unknown
Device busy
Write failed
Read failed
Read answer too long
State unknown
Port on master not support
Port in invalid state
Timeout
Table 7.3: Status- and errorcodes for read and write ISDU access
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 19 von 30
Parameterize via Mailbox Function:
We will use a commercially available IO-Link RFID tag reader model number BIS-4xx as an example with CTEU-
EP. Below are the device specific parameters that may need to be modified for proper operation.
Figure 7.1
Seite 20 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
Parameterize via Mailbox Function:
7.1.1
–
MSG Instruction for Read Access
To read sub-index 3, the user must create the following:
“Source” Controller Tag of type SINT[3] for
SINT[0]=40h (index)
–
–
SINT[1]=0
–
SINT[2]=3h (sub-index)
“Destination” Controller Tag of type SINT[3] for
SINT[0]=reserve or port error
–
SINT[1]=value returned
–
SINT[2]=reserve for 2 byte sub-index
MSG instruction
The controller tags are created as follows:
RFID_RD_source_CTEU = SINT[3]
RFID_RD_destination_CTEU = SINT[3]
Figure 7.2
This shows the source data index 40h / sub-index 3h, plus the return of 7h in the destination.
The table data to fill the message instruction is as follows:
Parameter Value Description
Message Type
Service Type
Service Code
CIP Generic
Custom
32 h / 50 d
Class
Instance
300 h / 768 d
1
Attribute 0
Source Element Tag of SINT[3]
Source Length
Destination Element
3
Tag of SINT[3]
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Read ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Read from Port 1
Always 0 in case of CTEU-EP
Contents of tag: RFID_RD_source_CTEU
40h
0h
Index (INT)
3h Subindex (SINT)
3 Bytes have to be written from Tag “RFID_RD_source_CTEU”
Contents of tag: RFID_RD_destination_CTEU
0h Data 0 Reserved or error
7h Data 1 Return from BIS M-4xx
Table 7.4
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 21 von 30
Message Instruction to read Parameter data:
Parameterize via Mailbox Function:
Figure 7.3
The communication tab will have the path to the CTEU Ethernet module configured:
Sample logic to execute instruction:
Figure 7.4
Informationen
The message is executed upon a rising edge trigger.
Seite 22 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
7.1.2
–
MSG Instruction for Write Access
To write to sub-index 3, the user must create the following:
“Source” Controller Tag of type SINT[4] for
SINT[0]=40h (index)
–
–
SINT[1]=0
SINT[2]=3h (sub-index)
–
SINT[3]=7h (example value to write to sub-index 3)
“Destination” Controller Tag of type SINT[4] for destination holder
MSG instruction
The controller tags are created as follows:
RFID_WR_source_CTEU = SINT[4]
RFID_WR_destination = SINT[4]
Parameterize via Mailbox Function:
Figure 7.5
The table data to fill the message instruction is as follows:
Parameter Value Description
Message Type
Service Type
Service Code
Class
CIP Generic
Custom
33 h / 51 d
300 h / 768 d
CIP-specific message
Write access to single CIP attribute -> Service Code “10h”
Write ISDU
CIP-Class-ID for vendor specific „ISDU Access Object“
Instance
Attribute
1
0
Read from Port 1
Always 0 in case of CTEU-EP
Source Element Tag of SINT[3] Contents of tag: RFID_RD_source_CTEU
40h Index (INT)
Source Length
Destination Element
4
0h
3h Subindex (SINT)
7h Data 0 Value to write to Index 40h, Subindex
3h (parameter inside RFID reader:
“Action if Tag is present”)
When writing 4 Bytes of data to an ISDU, then Source Length is 3+4=7
Bytes.
Tag of SINT[4] Contents of tag: RFID_RD_destination_CTEU
0h Data 0 Reserved or error
Table 7.5:
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 23 von 30
Message Instruction to write Parameter data:
Parameterize via Mailbox Function:
Figure 7.6
In this case, the source element is the first byte of the array.
Figure 7.7
The communication tab will have the path to the CTEU Ethernet module configured:
Sample logic to execute instruction:
Figure 7.8
Informationen
The message is executed upon a rising edge trigger.
Seite 24 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
AOI Support:
8 AOI Support:
Devices with a large number of parameters, or with multiple Boolean parameter functions in a single byte, can become difficult to manage. Therefore, a device specific AOI can improve the user experience when using the
Mailbox Function.
Attached there is an example AOI which demonstrates the use of the mailbox with a 3 rd
party RFID reader.
There are two separate AOI’s, read parameters and write parameters.
8.1 Read Parameters of RFID Reader
Import the attached AOI into the Rockwell project.
Figure 8.1
Precede the Read MSG instruction with the AOI. In this case, use the same trigger as the MSG instruction. You should notice the tags for Source and Destination are the same tags used in the MSG instruction.
Figure 8.2
A new tag must be created for “Parameter Read Values”. This will be of user defined data-type:
“UDT_FESTO_RFID_BISM_4x_Param_RDWR” which comes from the AOI installation.
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 25 von 30
3
AOI Support:
Note
By reviewing tag names below, please note:
• The tag name RFID_Param_CTEU data-type is user defined from the AOI
• There is one function, to select the index to read. These are values 1 to 7, defined by the AOI, and described in the comment field
• In this example, value 3 ( Act on Tag) is selected
• The AOI automatically loaded the index + sub-index with the proper values to the tag
RFID_RD_source_CTEU
• When the trigger was enabled, the BIS 4xx returned a 7, meaning AUTO 8 bytes
• The value is stored in the tag RFID_RD_destination_CTEU
• It is also copied to the tag RFID_RD_Param_CTEU, so the user only needs to reference this tag name
Figure 8.3
Seite 26 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
3
AOI Support:
8.2 Write Parameters to RFID Reader
Import the attached AOI into the Rockwell project.
Figure 8.4
Precede the Write MSG instruction with the AOI. You should notice the tag for Source is the same tag used in the
MSG instruction.
Figure 8.5
A new tag must be created for “Parameter_Write_Values”. This will be of user defined data-type:
“UDT_FESTO_RFID_BISM_4x_Param_RDWR” which comes from the AOI installation.
Note
By reviewing tag names below, please note:
• The tag name RFID_Param_CTEU data-type is user defined from the AOI
• There is one function, to select the index to write. These are values 1 to 7, defined by the AOI, and described in the comment field
• In this example, value 3 ( Act on Tag) is selected. Also, 7 is entered into instance Act_on_Tag
• The AOI automatically loaded the index, sub-index, and payload data with the proper values to the tag RFID_WR_source_CTEU
• When the trigger was enabled, the BIS 4xx received a 7, meaning AUTO mode
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 27 von 30
Figure 8.6
The value can then be read for verification.
AOI Support:
Seite 28 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
CTEU – EDS AOP to Parameterize Festo I-Port devices
9 CTEU – EDS AOP to Parameterize Festo I-Port devices
Festo IO-link devices have a unique connection scheme to connect with Festo masters. This is called I-Port, which uses IO-Link technology, but enables Festo devices to self configure.
When using CPX, the CTEL 4 port module is used, and commissioning and setting parameters are well documented in user manuals, and with FMT using the L5K Export.
When using CTEU, parameters for I-Port devices can be best configured using EDS AOP. Refer to the following steps for Logix5000:
1. Go to the Festo Support portal to find the EDS file CTEU-EP.eds
2. Use the Tools menu in Studio 5000 to install the EDS file
3. When selecting a new module for Ethernet, type Festo in the search bar for module type. Select CTEU-EP communication adapter
4. Use the change button to configure the IO connection of the CTEU, add the appropriate IP address, etc.
Figure 9.1
5. Go to the configuration tab. Here you will need to follow the manual of the I-port device to be commissioned.
Enter the appropriate data as needed.
Application Note – EtherNet/IP IO-Link Integration – 1.30 Seite 29 von 30
CTEU – EDS AOP to Parameterize Festo I-Port devices
Figure 9.2
Information
You can use the “Group” dropdown-list to filter the displayed parameters.
6. The “Parameters”-tab can be used in online mode to display the currently connected IO-Link-Devices.
You can copy&paste the values from the “Parameters”-tab to the “Expected Vendor ID” and “Expected Device
ID” parameters in the “Configuration”-tab.
This is a easy method to set up the check for a specific IO-Link configuration.
Figure 9.3
7. Select OK. This configuration is now complete.
All configuration parameters will be sent to the CTEU-EP during the forward open message of EtherNet/IP, commissioning the I-Port device connected.
Seite 30 von 30 Application Note – EtherNet/IP IO-Link Integration – 1.30
advertisement
Key Features
- Supports IO-Link devices
- Provides diagnostics for IO-Link devices
- Allows parameterization of IO-Link devices
- Integrates with Festo EtherNet/IP products
- Provides detailed documentation for setup and configuration
- Supports a range of 3rd party IO-Link devices