BECKHOFF TF6280 EtherNet/IP Slave Manual
The TF6280 TwinCAT EtherNet/IP Slave enables data exchange with an EtherNet/IP master. Both multicast and broadcast are supported. The function TF6280 TwinCAT EtherNet/IP Slave can behave like eight EtherNet/IP adapters. For sample, it is possible to: connect a master with eight slaves connect up to eight masters with 8 slaves This way more data can be transported or the master can be operated with different cycle times.
advertisement
Manual
EtherNet/IP Slave
TwinCAT 3
Version:
Date:
Order No.:
1.0
2016-12-27
TF6280
Inhaltsverzeichnis
Inhaltsverzeichnis
EtherNet/IP Slave Version: 1.0
3
4
Foreword
1 Foreword
1.1
Notes on the documentation
This description is only intended for the use of trained specialists in control and automation engineering who are familiar with the applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing and commissioning the components.
It is the duty of the technical personnel to use the documentation published at the respective time of each installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff
®
, TwinCAT
®
, EtherCAT
®
, Safety over EtherCAT
®
, TwinSAFE
®
, XFC
®
and XTS
®
are registered trademarks of and licensed by Beckhoff Automation GmbH.
Other designations used in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and patents:
EP1590927, EP1789857, DE102004044764, DE102007017835 with corresponding applications or registrations in various other countries.
The TwinCAT Technology is covered, including but not limited to the following patent applications and patents:
EP0851348, US6167425 with corresponding applications or registrations in various other countries.
EtherCAT
®
is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany
Copyright
© Beckhoff Automation GmbH & Co. KG, Germany.
The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express authorization are prohibited.
Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or design.
Version: 1.0
EtherNet/IP Slave
Foreword
1.2
Safety instructions
Safety regulations
Please note the following safety instructions and explanations!
Product-specific safety instructions can be found on following pages or in the areas mounting, wiring, commissioning etc.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the application. Modifications to hardware or software configurations other than those described in the documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are familiar with the applicable national standards.
Description of symbols
In this documentation the following symbols are used with an accompanying safety instruction or note. The safety instructions must be read carefully and followed without fail!
Serious risk of injury!
Failure to follow the safety instructions associated with this symbol directly endangers the life and health of persons.
DANGER
Risk of injury!
Failure to follow the safety instructions associated with this symbol endangers the life and health of persons.
WARNING
Personal injuries!
Failure to follow the safety instructions associated with this symbol can lead to injuries to persons.
CAUTION
Damage to the environment or devices
Failure to follow the instructions associated with this symbol can lead to damage to the environment or equipment.
Attention
Tip or pointer
This symbol indicates information that contributes to better understanding.
Note
EtherNet/IP Slave Version: 1.0
5
Overview
2 Overview
In combination with a network-capable Beckhoff PC, the function TF6280 TwinCAT EtherNet/IP Slave can be used to create an Ethernet/IP adapter.
Up to eight adapters can be parameterized with a physical interface. A virtual MAC address is formed, through which up to eight EtherNet/IP adapters can be operated on a PC via an Ethernet interface.
Technical data
Requires
Target system
Performance class (pp)
TF6280
TC1200 from build 4020
Windows XP, Windows 7/8, Windows CE
20
–
30
–
40
X
50
X
60
X
70
X
80
X
90
X
Ordering information
TF6280-00pp TC3 EtherNet/IP slave
The function TF6280 TwinCAT EtherNet/IP Slave enables data exchange with an EtherNet/IP master. Both multicast and broadcast are supported. The function TF6280 TwinCAT EtherNet/IP Slave can behave like eight EtherNet/IP adapters.
For sample, it is possible to:
• connect a master with eight slaves
• connect up to eight masters with 8 slaves
This way more data can be transported or the master can be operated with different cycle times.
In an EtherNet/IP network, the TF6280 behaves as a slave device. No further configuration via an EtherNet/
IP master is required. The configurator in TwinCAT 3.1 is used for the configuration, e.g. by specifying the IP settings and the number of data. The only requirement for a connection to be established is that the data itself must be set in the same way in the EtherNet/IP master.
EtherNet/IP
EtherNet/IP (Ethernet Industrial Protocol, EIP) is a real-time Ethernet protocol, which was disclosed and standardized by the ODVA (Open DeviceNet Vendor Association). The protocol is based on TCP, UDP and
IPv4.
Further information can be found at www.odva.org or https://en.wikipedia.org/wiki/Ethernet/IP.
6 Version: 1.0
EtherNet/IP Slave
Prerequisites
3 Prerequisites
Software
TF6280 is included in TwinCAT version 3.1 build 4020.28. No further installation is required.
Older product versions
Older versions are beta versions. Delete any older EtherNet/IP device configurations and create a new configuration.
Note
Hardware
Beckhoff PC
Beckhoff PC systems are usually preconfigured for the operation of EtherNet/IP devices.
Note
3.1
Verifying the hardware
Check whether the network interface is suitable
1. Create an EtherNet/IP slave. Right-click on “Devices” and add a new device (“Add New Item…”).
EtherNet/IP Slave Version: 1.0
7
Prerequisites
2. Select “EtherNet/IP Adapter (Slave)”.
3. Now select the adapter and find the appropriate Ethernet interface (Search…).
8 Version: 1.0
EtherNet/IP Slave
4. Select a “real-time capable” interface under “Compatible devices”.
Prerequisites
ð You can install the real-time driver.
No “real-time capable” network interface available
If the list contains no network interfaces under “Compatible devices”, the TF6280 function cannot be used on the present hardware.
Note
EtherNet/IP Slave Version: 1.0
9
Licensing
4 Licensing
The TwinCAT 3 functions are available both as a full and as a 7-Day trial version. Both license types can be activated via TwinCAT XAE.For more information about TwinCAT 3 licensing, please consult the TwinCAT 3
Help System.The following document describes both licensing scenarios for a TwinCAT 3 function on
TwinCAT 3 and is divided into the following sections:
• Licensing a 7-Day trial version [} 10]
• Licensing a full version [} 11]
Licensing a 7-Day trial version
1. Start TwinCAT XAE
2. Open an existing TwinCAT 3 project or create a new project
3. In “Solution Explorer”, please navigate to the entry “System\License”
4. Open the tab "Manage Licenses" and add a "Runtime License" for your product (in this screenshot
“TE1300: TC3 Scope View Professional”)
10
5. Optional: If you would like to add a license for a remote device, you first need to connect to the remote device via TwinCAT XAE toolbar
Version: 1.0
EtherNet/IP Slave
Licensing
6. Switch to the tab "Order Information" and click the button "Activate 7 Days Trial License..."to activate a test version
7. Please restart TwinCAT 3 afterwards.
Licensing a full version
8. Start TwinCAT XAE
9. Open an existing TwinCAT 3 project or create a new project
10. In "Solution Explorer", please navigate to the entry "SYSTEM\License"
11. Open the tab "Manage Licenses" and add a "Runtime License" for your product (in this screenshot "
TE1300: TC3 Scope View Professional”).
EtherNet/IP Slave Version: 1.0
11
Licensing
12. Optional:If you would like to add a license for a remote device, you first need to connect to the remote device via TwinCAT XAE toolbar
13. Navigate to the "Order Information" tab
The fields "System-ID" and "HW Platform" cannot be changed and just describe the platform for the licensing process in general a TwinCAT 3 license is always bound to these two identifiers: the "System-ID" uniquely identifies your system.
The "HW Platform" is an indicator for the performance of the device.
14. Optionally, you may also enter an own order number and description for your convenience
15. enter the "Beckhoff License ID" and click on "Generate License Request File...". If you are not aware of your "Beckhoff License ID" please contact your local sales representative.
16. After the license request file has been saved, the system asks whether to send this file via E-Mail to the
Beckhoff Activation Server
17. After clicking "Yes", the standard E-Mail client opens and creates a new E-Mail message to
"[email protected]" which contains the "License Request File"
18. Send this Activation Request to Beckhoff
NOTE! The “License Response File“ will be sent to the same E-Mail address used for sending out the ”License Request File”
12 Version: 1.0
EtherNet/IP Slave
Licensing
19. After receiving the activation file, please click on the button "Activate License Response File..."in the
TwinCAT XAE license Interface.
20. Select the received "Licnse response file" and click on "Open"
21. The "License Response File" will be imported and all included licenses will be activated. If there have been any trial licenses, these will be removed accordingly.
EtherNet/IP Slave Version: 1.0
13
Licensing
22. Please restart TwinCAT to activate licenses..
NOTE! The license file will be automatically copied to "..\TwinCAT\3.1\Target\License" on the local device.
14 Version: 1.0
EtherNet/IP Slave
Configuration
5 Configuration
The most important settings in order to establish a connection with an EtherNet/IP master are:
• the IP address,
• the assembly instance numbers and thus the length of the data
• and the correct cycle time.
IP address:
The IP address can be assigned freely, although it should be from the same network class as the master.
Otherwise a gateway must be entered, in order to route the protocol accordingly.
Assembly instance numbers:
The assembly instance numbers are permanently assigned and must be correctly set in the master. This also always includes the number of data or the size of the process image.
Cycle time:
The task cycle time in the TF6280 may not exceed the time on the master side, although it can be a fraction of that time. If, for sample, an EtherNet/IP cycle time of 10 ms is set on the master side, the task cycle time on the slave side can be 10 ms, 5 ms, 2 ms or 1 ms.
Recommended cycle time
EtherNet/IP enables cycle times of 1 ms or higher. The task can always be operated with 1
ms, as long as the system load of your systems [} 6] permits this.
Note
5.1
Creating an EtherNet/IP slave
Once you have added an EtherNet/IP adapter, a slave is automatically added to your configuration.
1. Set the IP address of the slave. (The IP address does not have to be the same as the IP address of the operating system.) Click on the box and switch to the Settings tab. Here you can set the IP address, the network mask and the gateway address.
EtherNet/IP Slave Version: 1.0
15
Configuration
1 a) If the IP address is to be issued by a DHCP server in your network, enter the value 0.0.0.0 in the
“IP address” field.
1 b) If the IP address of the operating system is to be used, enter the value 255.255.255.255 in the
“IP address” field. The subnet mask and the gateway address can be used unchanged. When TwinCAT starts, the EtherNet/IP driver then uses the IP address of the system.
2. Click on the box and select “Append IO Assembly”.
16 Version: 1.0
EtherNet/IP Slave
Configuration
3. To create data under Inputs, right-click on “Add New Item…”
4. Now select the data format and the number of data to be transferred. The number of bytes will be important later. It can be read in the object tree. e.g.: Enter 4 words, i.e. 8 bytes of process data:
In addition there are 4 bytes for the ConnState. The ConnState currently has no function. It can be used for additional information in the future.
EtherNet/IP Slave Version: 1.0
17
Configuration
5. Therefore, 12 bytes of process data must be created. Navigate to the box and select the Settings tab.
ð The length can be found in index field 0x8001:07. The length is displayed from the master perspective. TwinCAT inputs are outputs in the master, hence the reference to output size here.
6. Now do the same with the outputs of the EtherNet/IP slave.
ð Data creation is now complete. Now link the data with the PLC.
5.2
Setting the cycle time
The cycle time of the EtherNet/IP adapter (slave) is specified by the master. The task on the TwinCAT system must operate with at least the same speed.
Recommended cycle time
EtherNet/IP enables cycle times of 1 ms or higher. The task can always be operated with 1
ms, as long as the system load of your systems [} 6] permits this.
Note
To set the task cycle time navigate to the EIP Adapter device, then to the “Sync Task” tab and set the time.
18 Version: 1.0
EtherNet/IP Slave
Configuration
Note
Use a dedicated Sync Task
Use a dedicated Sync Task, since mapping via the PLC can result in the task being stopped, e.g. if a breakpoint is encountered, with the result that the EtherNet/IP connection is interrupted.
Also see about this
5.3
Changing EtherNet/IP settings
entered in the object F8000:2B "Advanced Options" in all EtherNet/IP devices.
If the corresponding bit is set, the IP address from the memory is used. If no value is entered, the bit is ignored, and the parameters of the TwinCAT system are used.
In the following sample bit 8 (0x0100) is set, which means that Store Category 1 is selected, which affects the IP settings (index 0x8000: 21…23).
EtherNet/IP Slave Version: 1.0
19
Configuration
To use Store Category 1 and 2, 0x0300 should be entered in object 8000:2B. Only bits 8 and 9 should be used. All other bits are reserved and must not be used.
ADS function blocks are used for reading or writing the settings from/to the PLC.
20 Version: 1.0
EtherNet/IP Slave
Configuration
5.3.1
Object description
Offset Name
0x00..0x01
0x02..0x03
0x04..0x23
ID
Reserved
Product Name
0x24..0x27
0x28..0x2B
Device Type
Vendor ID
0x2C..0x2F
Product Code
0x30..0x33
Revision
0x34..0x37
Serial Number
0x38..0x7D
Reserved
0x7E..0x83
0x84..0x87
MAC Address
IP Address
0x88..0x8B
Network Mask
0x8C..0x8F
Gateway Address
0x90..0x91
0x92..0x93
DHCP Max Retries
TCP/IP TTL
0x94..0x95
0x96..0x97
TCP/IP UDP Checksum
TCP/IP TCP Timeout
0x98..0x99
Multicast TTL
0x9A..0x9B
Multicast Checksum
0x9C..0x9D
Forward Class3 to PLC
0x9E..0x9F
Flags
0xA0..0xFF
Reserved
Data Type
UINT16
UINT16
BYTE[32],
STRING(31)
UINT32
UINT32
UINT32
UINT32
UINT32
BYTE[70]
BYTE[6]
UINT32
UINT32
UINT32
UINT16
UINT16
UINT16
UINT16
UINT16
UINT16
UINT16
UINT16
Byte[96]
38
39
40
41
34
35
36
37
42
43
-
8
-
32
33
4
5
6
7
1
-
SubIndex Store Category
1 2
3 X
X
X
X
X
Store Category
The “Store Category” determines which settings are overwritten with the values from the non-volatile memory. Bits 9 - 8 have to be set accordingly in the project under “Flags”. In order to modify both, both bits must be set.
(Bit9=Cat2, Bit8=Cat1)
5.3.2
ADS-Write command
AmsNetId
The AMSNetId can be found under the “EtherNet/IP” tab in the “NetID” field. When you select the option “Info
Data Support” it is linked directly.
The advantage of a direct link is that it always retrieves the current AMSNETID, even if controllers are used that use different AMSNETIDs. The AMSNETID of the EtherNet/IP adapter therefore does not have to be read manually.
EtherNet/IP Slave Version: 1.0
21
Configuration
ADS port number
For the function “EtherNet/IP Adapter” set the ADS port number to a fixed value of 0xFFFF.
Slave
IDXGRP: 0x0001F480
IDXOFFS: 0x00000000
Setting for setting (4 bytes + object size (256 bytes))
Byte Offset 0: 0x45
Byte Offset 1: 0x23
Byte Offset 2: ObjIndex LoByte (e.g. 0x8000 for slave 1 and 0x8010 for slave 2)
Byte Offset 3: ObjIndex HiByte
Byte Offset 4-260: Data of the object (see object description below)
Setting for resetting (4 bytes)
Byte Offset 0: 0x00
Byte Offset 1: 0x00
Byte Offset 2: ObjIndex LoByte (e.g. 0x8000 for slave 1 and 0x8010 for slave 2)
Byte Offset 3: ObjIndex HiByte
Note
Accept changes
After setting the properties restart TwinCAT for the TF6280, after which the new settings are applied and valid. The settings remain stored and don't have to be loaded again, unless there are changes.
5.3.3
ADS-Read command
AmsNetId
The AMSNetId can be found under the “EtherNet/IP” tab in the “NetID” field. When you select the option “Info
Data Support” it is linked directly.
22 Version: 1.0
EtherNet/IP Slave
Configuration
The advantage of a direct link is that it always retrieves the current AMSNETID, even if controllers are used that use different AMSNETIDs. The AMSNETID of the EtherNet/IP adapter therefore does not have to be read manually.
ADS port number
For the function “EtherNet/IP Adapter” set the ADS port number to a fixed value of 0xFFFF.
Slave
IDXGRP: 0x1F480
IDXOFFS: 0x8000 for the first slave
IDXOFFS: 0x8010 for the second slave
IDXOFFS: 0x8020 for the third slave
…
IDXOFFS: 0x8070 for the eights slave
LEN: 256
The data are stored in the data array, as described above -> see Object description [} 21].
5.3.4
Sample
A sample program can be downloaded: http://infosys.beckhoff.com/content/1033/
TF6280_Tc3_EthernetIPSlave/Resources/tszip/3105211403.tszip
5.4
Creating the EtherNet/IP slave in other EtherNet/IP masters
All the information you need is provided in the “Settings” dialog:
EtherNet/IP Slave Version: 1.0
23
Configuration
You need
• the IP address of the slave (see Creating an EtherNet/IP slave [} 15])
• the “Assembly Instance” numbers (see Settings tab)
• the number of data (see Settings tab)
• the “Configuration Instance” number 128 length 0
• the “Input Instance” number 129 length 12
• the “Output Instance”-number 130 length 12
The instance numbers are always the same. An export of the EDS file only contains the instance numbers.
The number of data still has to be entered.
The EtherNet/IP device (slave) can be integrated via a “generic node” structure or via the EDS file.
24 Version: 1.0
EtherNet/IP Slave
5.4.1
Sample for Rockwell CPUs
1. Under “Ethernet”, “New Module…”, select “Generic Ethernet Module”.
Configuration
2. Enter the IP address from object 0x8000:21.
3. Enter 129 dec
for Input Instance.
4. Enter 130 dec
for Output Instance and
5. 128 dec
for Config Instance.
EtherNet/IP Slave Version: 1.0
25
Configuration
ð The data length is dependent on the Comm format.
Note the properties of the selected Comm format
In the above sample the Comm format INT was selected, which means the number of data from objects
0x8001:05
and 0x8001:07 have to be divided by 2, since in TwinCAT they are specified in bytes and in the RSLogix in word length (INT).
An odd number of bytes must be rounded up. This also applies even if the Comm format is set to DINT, in which case you must round up to the next whole number.
Note
System limitations
In the case of Multicast, pay attention to the high network loads that this causes, especially in systems with many or short cycle times. A high network load may possibly impair communication.
26 Version: 1.0
EtherNet/IP Slave
Properties
6 Properties
6.1
Virtual slave
Using the TF6280, up to eight slaves can be parameterized with a physical interface. In this case a virtual
MAC address is formed for each virtual slave device, so that up to eight EtherNet/IP slaves can be operated on a PC via an Ethernet interface.
The advantage is that this option enables convenient connection of eight EtherNet/IP controllers and limitations in the bus communication with the slave can be bypassed without using additional hardware.
This feature can be used, for sample, for exchanging large data quantities with an EtherNet/IP master or for connecting with several EtherNet/IP masters in different subnets.
Create an additional box in the TwinCAT system configuration and proceed in the same way as for the configuration of a real slave.
Unique MAC address
If the virtual MAC address is assigned manually, ensure that it is truly unique in your network.
Note
EtherNet/IP Slave Version: 1.0
27
Properties
6.2
TF6280 - Configuration parameters
6.2.1
Index 0x8000 Slave Settings
Index Name
8000:0 Slave Settings
8000:1
8000:3
8000:4
8000:5
8000:6
8000:7
8000:8
8000:20
8000:21
8000:22
Slave Number
Product Name
Device Type
Vendor ID
Product Code
Revision
Serial Number
MAC Address
IP Address
Network Mask
Meaning
Slave Box ID
Name of the device
Device type
Vendor number
Product code
Version
Serial number (see object 0x9000)
MAC address (see object 0x9000)
IP address
• 0.0.0.0: Will be assigned dynamically by the DHCP service
• 255.255.255.255: The operating system address is used
Otherwise: statically assigned IP address
Subnet mask
• 0.0.0.0: Will be assigned dynamically by the DHCP service
8000:23
8000:28
Gateway address
Multicast TTL
8000:29 Multicast UDP checksum
Otherwise: statically assigned subnet mask
Gateway address
• 0.0.0.0: Will be assigned dynamically by the DHCP service
8000:24 DHCP Max Retries
Otherwise: statically assigned gateway address
0: Continuous repetition of the DHCP addressing attempts.
(Currently only this mode is implemented, as of: 10-2016)
8000:25 TCP/IP TTL “Time to live” – value for unicast TCP/UDP communication
8000:26 TCP/IP UDP Checksum Checksum function (Unicast):
8000:27 TCP/IP TCP Timeout
• 0: UDP checksum disabled.
• 1: UDP checksum enabled
Time switch for inactive TCP connection in seconds
• 0: Time switch disabled
“Time to live” value for multicast UDP communication
Checksum function (Multicast):
• 0: UDP checksum disabled
• 1: UDP checksum enabled
8000:2A Forward Class3 to PLC Message forwarding to the PLC
(Currently not implemented, as of: 10-2016)
8000:2B Advanced slave options “Store Category” parameter
• Bit9=Cat2,
• Bit8=Cat1
see Writing the IP address from the PLC [} 19]
28 Version: 1.0
EtherNet/IP Slave
Properties
6.2.2
Index 0x8001 IO Assembly Settings
Index Name
8001:0 IO Assembly Settings
8001:1
8001:1
Assembly Number
Configuration Instance
Meaning
Assembly Id
Configuration instance
8001:3
8001:4
Configuration Size
Input Instance (T->O)
Configuration size (always 0)
Link point for input values
(T->O: Target->Originator)
Size of the input values (in bytes) 8001:5 Input Size (T->O)
8001:6 Output Instance (O->T) Link point for output values
(O->T, Originator->Target)
Size of the output values (in bytes) 8001:7 Output Size (O-T)
8001:8 Heartbeat Instance (Listen Only)* Heartbeat link point (only for monitoring connections)
8001:9 Heartbeat Size (Listen Only)* always 0
8001:A Heartbeat Instance (Input Only)** Heartbeat link point (only for input connections)
8001:B Heartbeat Size (Input Only)** always 0
8001:C Advanced Assembly Options Bit 14: 0x4000 hex
• 0 = default
• 1 = disables the link between “ConnCtrl“ and
”ConnState“ for the EtherNet/IP IO connection
The other bits are always set to 0 (reserved)
* Heartbeat Instance (Listen Only): Enables monitoring of the input data (output data for TF6280) if a connection exists. The "Listen Only" connection is also terminated when the normal connection is terminated.
** Heartbeat Instance (Input Only): Enables reading of the input data (output data for TF6280). This connection is independent of the actual communication.
The heartbeat is necessary for the monitoring of both connection types (Listen Only and Input Only).
6.2.3
Index 0x9000 Slave Info
The current valid settings are displayed here; these can differ from the object 0x8000. The object 0x9000 displays the active parameters.
6.2.4
Index 0x9001 IO Assembly Info
The current valid assembly settings are displayed here; these can differ from the object 0x8001. The object
0x9001
displays the active parameters.
EtherNet/IP Slave Version: 1.0
29
Diagnostic history
7 Diagnostic history
The diagnostics history is a tool for monitoring the status of the EtherNet/IP interface and displaying the diagnostic messages with timestamps in plain text.
In addition, information / errors that occurred in the past are logged, in order to enable precise troubleshooting at a later stage. This also applies for errors that only occurred for such a short time that any corresponding messages were not visible.
The diagnostic history is part of the TwinCAT system, where it can be found under Devices, EtherNet/IP in the “Diag History” tab.
30 Version: 1.0
EtherNet/IP Slave
Diagnostic history
7.1
Error codes TF6280
Error
CN_ORC_ALREADY_USED
CN_ORC_BAD_TRANSPORT 0x103 /
(259)
CN_ORC_OWNER_CONFLICT 0x106 /
(262)
CN_ORC_BAD_CONNECTION 0x107 /
(263)
CN_ORC_BAD_CONN_TYPE 0x108 /
(264)
CN_ORC_BAD_CONN_SIZE
CN_ORC_CONN_UNCONFIGUR
ED
CN_ORC_BAD_RPI
0x109 /
(265)
0x110 /
(272)
0x111 /
(273)
CN_ORC_NO_CM_RESOURCES 0x113 /
(275)
CN_ORC_BAD_VENDOR_PROD
UCT
0x114 /
(276)
CN_ORC_BAD_DEVICE_TYPE 0x115 /
(277)
CN_ORC_BAD_REVISION 0x116 /
(278)
CN_ORC_BAD_CONN_POINT 0x117 /
(279)
CN_ORC_BAD_CONFIGURATIO
N
CN_ORC_CONN_REQ_FAILS
0x118 /
(280)
0x119 /
(281)
CN_ORC_NO_APP_RESOURCE
S
0x11A /
(282)
Code hex /
(decimal)
0x100 /
(256)
Description
Connection already in use
Transport type not supported
More than one guy configuring
Trying to close inactive conn
Unsupported connection type
Mismatch in electronic key
Mismatch in electronic key
Mismatch in electronic key
Non-existent instance number
Remedy/meaning
The connection is already established; use another connection or close this one
The transport type is not supported
A connection already exists; a further connection cannot be established
Faulty connection
Connection size mismatch
Connection unconfigured
The Connection type is not supported, check your settings.
The connection size does not match, check your settings.
Connection was not configured
Unsupportable RPI The task time usually doesn't match; make sure that the EL6652 operates internally with 1 ms and that you can adjust this with the Cycle Time
Multiplier. Otherwise adjust the task time.
Conn Mgr out of connections
No further resources are available
Wrong vendor number
Wrong device type
Wrong revision number
Wrong connection number
Bad config instance number
Faulty configuration
Connection could not be established No controlling connection open
App out of connections
No more free connections available.
If you cannot fix this error yourself, Support will require the following information:
• TwinCAT version and build number and a
• Wireshark recording
Prepare Wireshark recording
The Wireshark recording can be created with a network hub, a network switch with port mirroring, e.g. the
Beckhoff ET2000, or with the “Promiscuous Mode” of the TwinCAT system.
EtherNet/IP Slave Version: 1.0
31
Diagnostic history
32 Version: 1.0
EtherNet/IP Slave
advertisement
Key Features
- Data exchange with EtherNet/IP master
- Supports multicast and broadcast
- Behaves like eight EtherNet/IP adapters
- Allows connection of multiple masters and slaves
- Enables data transport at different cycle times
- Configured via TwinCAT 3.1
