Transcription
Allen-Bradley ControlLogixEthernet Driver 2016 Kepware, Inc.
Allen-Bradley ControlLogix Ethernet Driver2Table of ContentsTable of Contents2Allen-Bradley ControlLogix Ethernet Driver7Overview8Device Setup9Communications Routing10Connection Path Specification11Routing Examples12Logix Device IDs14CompactLogix 5300 Ethernet Device ID15Logix Communications Parameters17Logix Options18Logix Database Settings20Logix Database Options21Logix Database Filtering221761-NET-ENI Setup22Data Highway Plus Gateway Setup23ControlNet Gateway Setup24EtherNet/IP Gateway Setup25Serial Gateway Setup25MicroLogix 1100 Setup26ENI DF1/DH /ControlNet Gateway Communications ParametersSLC 500 Slot Configuration2728SLC 500 Modular I/O Selection GuidePerformance Optimizations2931Optimizing Communications31Optimizing the Application33Performance Statistics and Tuning34Performance Tuning Example35Data Types Description48Address Descriptions49Logix Addressing49MicroLogix Addressing50SLC 500 Fixed I/O Addressing52SLC 500 Modular I/O Addressing52PLC-5 Series Addressing53Logix Tag-Based Addressing54Address Formats55Tag Scope56Internal Tags57Predefined Term Tags57Addressing Atomic Data Types57Addressing Structure Data Types58Addressing STRING Data Type58Ordering of Logix Array Data59Logix Advanced Addressing60Advanced Addressing: BOOL60Advanced Addressing: SINT62www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver3Advanced Addressing: INT63Advanced Addressing: DINT65Advanced Addressing: LINT67Advanced Addressing: REAL68File Listing70Output Files71Input Files73Status Files76Binary Files77Timer Files77Counter Files78Control Files78Integer Files79Float Files79ASCII Files80String Files81BCD Files81Long Files81MicroLogix PID Files82PID Files83MicroLogix Message Files84Message Files85Block Transfer Files85Function File Listing86High-Speed Counter File (HSC)86Real-Time Clock File (RTC)87Channel 0 Communication Status File (CS0)88Channel 1 Communication Status File (CS1)88I/O Module Status File (IOS)89Automatic Tag Database Generation90Tag Hierarchy90Controller-to-Server Name Conversions92Preparing for Automatic Tag Database Generation92Error Codes94Encapsulation Error Codes94CIP Error Codes940x0001 Extended Error Codes950x001F Extended Error Codes950x00FF Extended Error Codes95Error Descriptions97Address Validation Errors97Address address is out of range for the specified device or register.97Array size is out of range for address address .97Array support is not available for the specified address: address .97Data type type is not valid for device address address .98Device address address contains a syntax error.98Device address address is not supported by model model name .98Device address address is read only.98Memory could not be allocated for tag with address address on device device name .99Missing address99Communication Errors99www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver4Socket error code occurred on device name . Operation operation name failed because reason .99Unable to bind to adapter: adapter . Connect failed.100Winsock initialization failed (OS error n).100Winsock V1.1 or higher must be installed to use the Allen-Bradley ControlLogix Ethernet Driver.100Device-Specific Error Messages100Allen-Bradley ControlLogix Ethernet Device : CIP connection size requested is not supported bythis device. Automatically falling back to 500 bytes.101Device device name is not responding.101Encapsulation error occurred during a request to device device name . [Encap. error code ].101error occurred during a request to device device name . [CIP error code , Ext.error code ].102Frame received from device device name contains errors.102Unable to retrieve the identity for device device . [CIP error error , Ext. error error ]. Alltags will use Symbolic Protocol Mode.102Unable to retrieve the identity for device device . [Encap. error error ]. All tags will useSymbolic Protocol Mode.102Unable to retrieve the identity for device device . Frame received contains errors. All tags will useSymbolic Protocol Mode.103ControlLogix-Specific Error MessagesRead Errors (Non-Blocking)103103Read request for tag tag address on device device name failed due to a framing error. Tagdeactivated.104Unable to read tag address on device device name . Tag deactivated.104Unable to read tag tag address on device device name . [CIP error code , Ext.error code ].104Unable to read tag tag address on device device name . Controller tag data type type unknown. Tag deactivated.104Unable to read tag tag address on device device name . Data type type is illegal for thistag. Tag deactivated.105Unable to read tag tag address on device device name . Data type type not supported. Tagdeactivated.105Unable to read tag tag address on device device name . Tag does not support multi-elementarrays. Tag deactivated.Read Errors (Blocking)105105Read request for count element(s) starting at tag address on device device name faileddue to a framing error. Block deactivated.106Unable to read count element(s) starting at tag address on device device name . Blockdeactivated.106Unable to read count element(s) starting at tag address on device device name . [CIPerror code , Ext. error code ].106Unable to read count element(s) starting at address on device device . Controller tag datatype type unknown. Block deactivated.107Unable to read count element(s) starting at address on device device . Data type type is illegal for this block.107Unable to read count element(s) starting at address on device device . Data type type not supported.107Unable to read count element(s) starting at tag address on device device name . Blockdoes not support multi-element arrays. Block deactivated.Write Errors107108Unable to write to tag address on device device name .108Unable to write to tag tag address on device device name . [CIP error code , Ext.Status code ].108Unable to write to tag tag address on device device name . Controller tag data type type unknown.109Unable to write to tag tag address on device device name . Data type type is illegal for this 109www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver5tag.Unable to write to tag tag address on device device name . Data type type not supported. 109Unable to write to tag tag address on device device name . Tag does not support multielement arrays.109Write request for tag tag address on device device name failed due to a framing error.110Project Synchronization Errors110Encapsulation error occurred while uploading project information. [Encap. error code ].110Error occurred while uploading project information. [CIP error code , Ext. error code ].110Framing error occurred while uploading project information.111Invalid or corrupt controller project detected while synchronizing. Synchronization will be retriedshortly.111Low memory resources.111Project download detected while synchronizing. Synchronization will be retried shortly.112Unable to read element element(s) starting at address on device device name . Native tagsize mismatch.112Unable to read tag tag name on device device name . Native tag size mismatch.112Unable to write to tag tag name on device device name . Native tag size mismatch.112ENI/DH /ControlNet Gateway Specific Error Messages112Device device name is not responding. Local node responded with error [DF1 STS value ].113Unable to read block size element(s) starting at address on device device name . [DF1STS value , EXT STS value ]. Tag(s) deactivated.113Unable to read block size element(s) starting at address on device device name . Framereceived contains errors.113Unable to write to address address on device device name . [DF1 STS value , EXTSTS value ].114Unable to write to address address on device device name . Frame received contains errors.114Unable to write to address address on device device name . Local node responded with error[DF1 STS value ].114Unable to write to function file address on device device name . Local node responded witherror [DF1 STS value ].115Automatic Tag Database Generation Errors115Database error: Array tags orig. tag name dimensions exceed 31 characters. Tags renamed to new tag name dimensions .115Database error: Data type type for tag tag name not found in tag import file. Tag not added.116Database error: Data type for Ref. Tag tag name unknown. Setting Alias tag tag name datatype to Default ( type ).116Database error: Error occurred processing Alias tag tag name . Tag not added.116Database error: Member data type type for UDT UDT name not found in tag import file. Settingto Default type type .116Database error: Program group orig. program name exceeds 31 characters. Program grouprenamed to new program name .117Database error: Tag orig. tag name exceeds 31 characters. Tag renamed to new tag name .117Database error: Unable to resolve CIP data type hex value for tag tag name . Setting to defaulttype logix data type .117Invalid or corrupt controller project detected while synchronizing. Try again later.117Project download detected while synchronizing. Try again later.118Unable to generate a tag database for device device name . Reason: Import file not found.118Unable to generate a tag database for device device name . Reason: L5K file is invalid or corrupt.118Unable to generate a tag database for device device name . Reason: Low memory resources.118Reference Material119Choosing a Protocol Mode120Detecting a Change in the Controller Project121SoftLogix 5800 Connection Notes123Glossary124www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver6Index126www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver7Allen-Bradley ControlLogix Ethernet DriverHelp version 1.117CONTENTSOverviewWhat is the Allen-Bradley ControlLogix Ethernet Driver?Device SetupHow do I configure a device for use with this driver?Communications RoutingHow do I communicate with a remote ControlLogix 5000 processor or 1756-DHRIO/1756-CNB Interface Module?Performance OptimizationsHow do I get the best performance from the Allen-Bradley ControlLogix Ethernet Driver?Data Types DescriptionWhat data types does this driver support?Address DescriptionsHow do I address a tag on a Allen-Bradley ControlLogix Ethernet device?Automatic Tag Database GenerationHow can I easily configure tags for the Allen-Bradley ControlLogix Ethernet Driver?Error DescriptionsWhat error messages does the driver produce?Error CodesWhat are the Allen-Bradley ControlLogix Ethernet error codes?Reference MaterialWhere can I find additional information relating to the Allen-Bradley ControlLogix Ethernet Driver?www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver8OverviewThe Allen-Bradley ControlLogix Ethernet Driver provides an easy and reliable way to connect Allen-BradleyControlLogix Ethernet controllers to OPC client applications, including HMI, SCADA, Historian, MES, ERP, andcountless custom applications.Supported Allen-Bradley ControllersControlLogix 5500 SeriesCommunications with ControlLogix can be accomplished through an EtherNet/IP communication module forEthernet communications or through a 1761-NET-ENI module for Ethernet-to-serial communications using thecontroller's serial port.CompactLogix 5300 SeriesEthernet communications with CompactLogix requires a processor with a built-in EtherNet/IP port such as the1769-L35E. Communications with CompactLogix otherwise requires a 1761-NET-ENI module for Ethernet-toserial communications using the controller's serial port.FlexLogix 5400 SeriesCommunications with FlexLogix can be accomplished through a 1788-ENBT daughter card for Ethernetcommunications or through a 1761-NET-ENI module for Ethernet-to-serial communications using the controller'sserial port.SoftLogix 5800The driver supports the Allen-Bradley SoftLogix 5800 Series Controller and requires an Ethernet card in theSoftLogix PC.Data Highway Plus GatewayThe driver supports the PLC-5 Series and SLC 500 Series with a Data Highway Plus interface. This isaccomplished through a DH gateway and requires one of the aforementioned PLCs, an EtherNet/IPcommunication module, and a 1756-DHRIO-interface module (both residing in the ControlLogix rack).ControlNet GatewayThe driver supports the PLC-5C Series. This is accomplished through a ControlNet gateway and requires theaforementioned PLC, an EtherNet/IP communication module, and a 1756-CNB/CNBR interface module (bothresiding in the ControlLogix rack).1761-NET-ENIThe driver supports communications with the 1761-NET-ENI device. The ENI device adds extra flexibility indevice networking and communications by providing an Ethernet-to-serial interface for both Full Duplex DF1controllers and Logix controllers. In conjunction with the ENI device, this driver supports the following:lControlLogix 5500 Series*lCompactLogix 5300 Series*lFlexLogix 5400 Series*lMicroLogix SerieslSLC 500 Fixed I/O ProcessorlSLC 500 Modular I/O SerieslPLC-5 Series*These models require 1761-NET-ENI Series B or higher.MicroLogix 1100The driver supports communications with the MicroLogix 1100 (CH1 Ethernet) using EtherNet/IP.ControlLogix is a registered trademarks of Allen-Bradley Company, LLC.CompactLogix is a trademarks of Rockwell Automation, Inc.All trademarks are the property of their respective owners.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver9Device SetupSupported DevicesDeviceCommunicationsControlLogix 5550 / 5553 / 5555 / 5561 / 5562 /5563 / 5564 / 5565 / 5571 / 5572 / 5573 / 5574 /5575 / 5585 processorsVia 1756-ENBT / ENET / EN2F / EN2T / EN2TR /EN3TR / EWEB / EN2TXT Ethernet moduleVia Serial GatewayVia 1761-NET-ENI Series B or higher using Channel0 (serial)CompactLogix 5320 / 5323 / 5330 / 5331 / 5332 /5335 / 5343 / 5345 / 5370Built-in Ethernet/IP port on processors with E suffix*Via Serial GatewayVia 1761-NET-ENI Series B or higher using Channel0 (serial)FlexLogix 5433 / 5434 processorsVia 1788-ENBT Ethernet daughter cardVia Serial GatewayVia 1761-NET-ENI Series B or higher using Channel0 (serial)SoftLogix 5810 / 5830 / 5860 processorsVia SoftLogix Ethernet / IP Messaging moduleVia Serial GatewayMicroLogix 1000 / 1200 / 1500Via 1761-NET-ENIVia EtherNet/IP GatewayMicroLogix 1100 / 1400Via MicroLogix 1100 / 1400 Channel 1 (Ethernet)Via 1761-NET-ENIVia EtherNet/IP GatewaySLC 500 Fixed I/O ProcessorVia 1761-NET-ENIVia EtherNet/IP GatewaySLC 500 Modular I/O Processors (SLC 5/01, SLC 5/02, Via DH Gateway**SLC 5/03, SLC 5/04, SLC 5/05)Via 1761-NET-ENIVia EtherNet/IP GatewayPLC-5 series (excluding the PLC5/250 series)Via DH GatewayVia 1761-NET-ENIVia EtherNet/IP GatewayPLC-5/20C, PLC-5/40C, PLC-5/80CVia ControlNet GatewayVia 1761-NET-ENIVia EtherNet/IP Gateway*For example, 1769-L35E.**This driver supports any SLC 500 series PLC that supports DH or that can be interfaced to a DH network(such as the KF2 interface module).Firmware VersionsDeviceVersionControlLogix 5550 (1756-L1)11.35 - 13.34ControlLogix 5553 (1756-L53)11.28ControlLogix 5555 (1756-L55)11.32 - 16.04www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver10DeviceVersionControlLogix 5561 (1756-L61)12.31 - 20.11ControlLogix 5562 (1756-L62)12.31 - 20.11ControlLogix 5563 (1756-L63)11.26 - 20.11ControlLogix 5564 (1756-L64)16.03 - 20.11ControlLogix 5565 (1756-L65)16.03 - 20.11ControlLogix 5571 (1756-L71)20.11 - 28.011ControlLogix 5572 (1756-L72)19.11 - 28.011ControlLogix 5573 (1756-L73)18.12 - 28.011ControlLogix 5574 (1756-L74)19.11 - 28.011ControlLogix 5575 (1756-L75)18.12 - 28.011ControlLogix 5583 (1756-L83)28.011ControlLogix 5585 (1756-L85)28.011CompactLogix 5370 (1769-L1)20.11 - 28.011CompactLogix 5370 (1769-L2)20.11 - 28.011CompactLogix 5370 (1769-L3)20.11 - 28.011CompactLogix 5320 (1769-L20)11.27 - 13.18CompactLogix 5323 (1769-L23)17.05 - 20.11CompactLogix 5330 (1769-L30)11.27 - 13.18CompactLogix 5331 (1769-L31)16.22 - 20.11CompactLogix 5332 (1769-L32)16.22 - 20.11CompactLogix 5335 (1769-L35)16.22 - 20.11CompactLogix 5343 (1768-L43)15.07 - 20.11CompactLogix 5345 (1768-L45)16.24 - 20.11ControlLogix 5380 (5069-L3)28.011FlexLogix 5433 (1794-L33)11.25 - 13.33FlexLogix 5434 (1794-L34)11.25 - 16.02SoftLogix 5800 (1789-L60)16.00 - 20.01ControlLogix, CompactLogix, and FlexLogix SerialCommunications1761-NET-ENI Series B or higher or SerialGatewayMicroLogix 1100 (1763-L16AWA/BWA/BBB)1.1Communication ProtocolThe Communications Protocol is EtherNet/IP (CIP over Ethernet) using TCP/IP.Logix and Gateway ModelsLogix and Gateway models support the following:lConnected MessaginglSymbolic ReadslSymbolic WriteslSymbol Instance Reads (V21 or higher)lPhysical (DMA) Reads (V20 or lower)lSymbol Instance WritesENI ModelsENI models support unconnected messaging.Communications RoutingRouting provides a way to communicate with a remote device over various networks. It can be thought of as abridge between the local device and a remote device even if they are on two different field bus networks. Accessto a remote (destination) backplane allows for direct communication with the supported modules located on thisbackplane. Supported modules include the following:lControlLogix 5500 processor for ControlLogix applications.lSoftLogix 5800 processor for SoftLogix applications.l1756-DHRIO interface module for DH Gateway applications.l1756-CNB or 1756-CNBR interface module for ControlNet Gateway applications.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver11A routing path is a series of backplane hops, whose last hop points to the destination backplane. Each hoprequires a Logix backplane (not a Logix processor). An individual hop can utilize one of the following networks asits medium:lControlNetlDH lTCP/IP (Ethernet/IP)Important: Routing is not supported for ENI and MicroLogix 1100 models.Connection Path SpecificationThe routing path is specified in the device ID. As with non-routing applications, communication originates fromthe Allen-Bradley ControlLogix Ethernet Driver on the PC and is directed at the local Ethernet module. Once at thislocal Ethernet module, the device ID specifies a way out of the module and onto the backplane, just like with nonrouting applications. The routing path directs the message to the desired Logix backplane. The device ID alsodetermines what device is communicated with (such as the ControlLogix processor, SoftLogix processor, DH node, or ControlNet node).The routing path specification begins and ends with the left and right bracket respectively ([ ]). The path itself isa series of port/link address pairs, identical to the communication path syntax in RSLogix 5000 MessageConfiguration dialog.DesignatorTypeDescriptionFormatsRangePort IDSpecifies a way out of the interface module in question.*Decimal065535Decimal0-255Link Address If the corresponding port is the backplane, the link address is the slotnumber of the interface module that goes out.If the corresponding port is an interface module port, the link addressspecifies a destination node as follows.- DH /ControlNet: node ID- EtherNet/IP communication module: IP address- SoftLogix EtherNet/IP module: IP address*For more information, refer to "Port Reference" below.Single HopIP Address, Port ID0, [Link Address0, Port ID1, Link Address1, Port ID2], Link Address2.Multi-Hop (N Hops)IP Address, Port ID0, [Link Address0, Port ID1, Link Address1, Port ID2, Link Address2, . Port ID(N 1), LinkAddress(N 1), Port ID(N 2)], Link Address(N 2).Notes:1. The last port ID in the path (Port ID2 and Port ID(N 2) for single-hop and multi-hop respectively) mustbe 1 (port for backplane).2. Port ID0 must be 1 (port for backplane). Link Address2 and Link Address (N 2) are the slot numbers ofthe remote Logix processor/1756-DHRIO module/1756-CNB module.Port ReferenceInterface ModulePort 1Port 2Port 3EtherNet/IP Communication ModuleBackplaneEthernet NetworkN/ASoftLogix EtherNet/IP Messaging ModuleVirtual Backplane Ethernet NetworkN/A1756-DHRIOBackplaneDH Network on Ch. ADH Network on Ch. B1756-CNBBackplaneControlNet NetworkN/AApplication Noteswww. kepware.com
Allen-Bradley ControlLogix Ethernet Driver121. Messages cannot be routed in or out of the same interface module channel more than once within thepath. Doing so results in CIP error 0x01 Ext. error 0x100B.2. For multiple channel interface modules, messages cannot be routed into and then immediately out of thatsame module (using different channels), regardless of whether the message is directed to the backplanefirst or avoids the backplane all together. As previously mentioned, the latter is not supported since eachhop requires a ControlLogix backplane. An example would be to route a DH message from one DH link(such as Channel A of 1756-DHRIO) to another DH link (such as Channel B of same 1756-DHRIO)through one 1756-DHRIO-interface module. This is commonly referred to as Remote DH messaging andis not supported.Routing ExamplesThe routing examples below include the entire device ID minus the IP of the local 1756-ENBT. The perspective ofthe device ID/routing path is from the local 1756-ENBT Module. Hop descriptions are in the following form:Link Address (N), Port ID(N 1), Link Address(N 1), Port ID(N 2)Note: For more information, refer to Connection Path Specification. For further details on building aconnection/routing path, refer to Allen-Bradley Publication 1756-6.5.14, pp. 4-5 through 4-8.In the illustration below, all DH /ControlNet node IDs are specified in Decimal format. The node ID specified inthe PLC and displayed in RSWho is in Octal format. Descriptions of the colors are as follows:lGreen EthernetlBlue DH lOrange ControlNetNote: For more information, refer to Data Highway Plus Gateway Setup and ControlNet Gateway Setup.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver13Example 1Logix5550 to PLC-5 via DH Gateway.Destination NodeModelRoutingDevice ID less IPPLC-5/20 (D)DH GatewayNo1,1.B.9Example 2Logix5550 to PLC-5C via CN Gateway.Destination NodeModelRoutingDevice ID less IPPLC-5/40C (B)CN GatewayNo1,2.A.1Example 3Logix5550 to Logix5550 via routing over DH .www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver14Destination NodeModelRoutingDevice ID less IPLogix5550 (C)ControlLogix 5550Yes1,[1,2,8,1],0Routing Path Breakdown for Example 3.HopSegmentDescription11,2,8,1Slot 1 (DHRIO) - Port 2 (DH Ch A) - DH Node 8 - Logix C backplaneExample 4Logix5550 to PLC-5C via CN Gateway, routing over DH .Destination NodeModelRoutingDevice ID less IPPLC-5/80C (E)CN GatewayYes1,[1,2,8,1],2.A.3Routing Path Breakdown for Example 4.HopSegmentDescription11,2,8,1Slot 1 (DHRIO) - Port 2 (DH Ch A) - DH Node 8 - Logix C backplaneExample 5Logix5550 to Logix5550 via routing over DH , ControlNetDestination NodeModelRoutingDevice ID less IPLogix5550 (F)ControlLogix 5550Yes1,[1,2,8,1,2,2,15,1],0Routing Path Breakdown for Example 5.HopSegmentDescription11,2,8,1Slot 1 (DHRIO) - Port 2 (DH Ch A) - DH Node 8 - Logix C backplane22,2,15,1Slot 2 (CNB) - Port 2 (CN Ch A) - CN Node 15 - Logix F backplaneExample 6Logix5550 to SLC 5/04 via routing over DH , ControlNet.Destination NodeModelRoutingDevice ID less IPSLC 5/04 (G)DH GatewayYes1,[1,2,8,1,2,2,15,1],1.A.2Routing Path Breakdown for Example 6.HopSegmentDescription11,2,8,1Slot 1 (DHRIO) - Port 2 (DH Ch A) - DH Node 8 - Logix C backplane22,2,15,1Slot 2 (CNB) - Port 2 (CN Ch A) - CN Node 15 - Logix F backplaneExample 7Logix5550 to Logix5550 via routing over DH , ControlNet, Ethernet.Destination Node ModelRoutingDevice ID less IPLogix5550 ControlLogix 5550Routing Path Breakdown for Example 7.HopSegmentDescription11,2,8,1Slot 1 (DHRIO) - Port 2 (DH Ch A) - DH Node 8 - Logix Cbackplane22,2,15,1Slot 2 (CNB) - Port 2 (CN Ch A) - CN Node 15 - Logix F backplane33,2,192.192.180.101,1Slot 3 (ENBT) - Port 2 - Remote1756-ENBT IP - Logix H backplaneLogix Device IDsFor information on ENI device ID setup, refer to 1761-NET-ENI Setup.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver15ControlLogix 5500 EthernetThe device ID specifies the device IP address, as well as the slot number in which the controller CPU resides.Device IDs are specified as the following: IP or hostname ,1,[ optional routing path ], CPU Slot DesignatorDesignatorType*DescriptionFormats RangeIP/Host Name N/AIP Address or host name.Decimal0-2551Port IDPort to backplane.Decimal1OptionalRouting PathMultiple Link,port pairsSpecifies a way out of the EtherNet/IP interface moduleand must equal 1 (port to the backplane).Decimal*CPU SlotLink AddressSlot number of the ControlLogix processor.Decimal0-255*For more information, refer to Connection Path Specification.Example123.123.123.123,1,0This equates to an Ethernet/IP of 123.123.123.123. The port ID is 1 and the CPU resides in slot 0.CompactLogix 5300 Ethernet Device IDThe device ID specifies the device IP address, as well as the slot number in which the controller CPU resides.Device IDs are specified as the following: IP or hostname ,1,[ optional routing path ], CPU Slot /Host NameN/ACompactLogix Ethernet IP Address or host name.Decimal0-2551Port IDPort to backplane.Decimal1OptionalRouting PathMultiple Link,port pairsSpecifies a way out of the Ethernet port and mustequal 1 (port to the backplane).Decimal*CPU SlotLink AddressSlot number of the CompactLogix processor.Decimal0-255*For more information, refer to Connection Path Specification.Example123.123.123.123,1,0This equates to CompactLogix IP of 123.123.123.123. The port ID is 1 and the CPU resides in slot 0.FlexLogix 5400 Ethernet Device IDThe device ID specifies the device IP address, as well as the slot number in which the controller CPU resides.Device IDs are specified as the following: IP or hostname ,1,[ optional routing path ], CPU Slot DesignatorDesignatorType*DescriptionFormats RangeIP/Host Name N/A1788-ENBT IP Address or host name.Decimal0-2551Port IDPort to backplane.Decimal1OptionalRouting PathMultiple Link,port pairsSpecifies a way out of the 1788-ENBT interface moduleand must equal 1 (port to the backplane).Decimal*CPU SlotLink AddressSlot number of the FlexLogix processor.Decimal0-255*For more information, refer to Connection Path Specification.Example123.123.123.123,1,0This equates to 1788-ENBT IP of 123.123.123.123. The port ID is 1 and the CPU resides in slot 0.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver16SoftLogix 5800 Device IDThe device ID specifies the SoftLogix PC IP address, as well as the virtual slot number in which the controller CPUresides. Device IDs are specified as the following: IP or hostname ,1,[ optional routing path ], CPU Slot DesignatorType*DescriptionFormats RangeIP/HostNameN/ASoftLogix PC NIC IP Address or host name.Decimal0-2551Port IDPort to backplane.Decimal1OptionalRouting PathMultiple Link,port pairsSpecifies a way out of the EtherNet/IP Messaging moduleand must equal 1 (port to the virtual backplane).Decimal*CPU SlotLink AddressSlot number of the SoftLogix processor in the virtualbackplane.Decimal0-255Designator*For more information, refer to Connection Path Specification.Example123.123.123.123,1,1This equates to SoftLogix PC IP Address of 123.123.123.123. The port ID is 1 and the CPU resides in slot 1.Note: For information on supplementing a device ID with a routing path to a remote backplane, refer toCommunications Routing.See Also: SoftLogix 5800 Connection Noteswww. kepware.com
Allen-Bradley ControlLogix Ethernet Driver17Logix Communications ParametersDescriptions of the parameters are as follows:llllTCP/IP Port: This parameter specifies the TCP/IP port number that the device is configured to use. Thedefault setting is 44818.Connection Size: This parameter specifies the number of bytes available on the CIP connection for datarequests and responses. The valid range is 500 to 4000 bytes. The default setting is 500 bytes.Note: Only the ControlLogix 5500 and CompactLogix 5300 device models support this feature. To supportconnection sizes greater than 500 bytes, the device must support Firmware version 20 or later controllersand Ethernet bridge EN3x, EN2x, or EN5.x. Older Ethernet modules like ENBT and ENET do not supportthis feature. Devices that do not meet the necessary requirements automatically fall back to the defaultsetting of 500 bytes, although the requested size is re-attempted after communications failure.Important: The Connection Size value may also be requested through the System tag "CIPConnectionSizeRequested." For more information, refer to Internal Tags.Inactivity Watchdog: This parameter specifies the amount of time a connection can remain idle(without read/write transactions) before being closed by the controller. In general, the larger thewatchdog value, the more time it takes for connection resources to be released by the controller and viceversa. The default setting is 32 seconds.Note: If the Event Log error "CIP connection timed-out while uploading project information" occursfrequently, increase the Inactivity Watchdog value. Otherwise, an Inactivity Watchdog value of 32seconds is preferred.Array Block Size: This parameter specifies the maximum number of array elements to read in a singletransaction. The value is adjustable and ranges from 30 to 3840 elements. The default setting is 120elements.Note: For Boolean arrays, a single element is considered a 32-element bit array. Thus, setting the blocksize to 30 elements translates to 960 bit elements, whereas 3840 elements translate to 122880 bitelements.www. kepware.com
Allen-Bradley ControlLogix Ethernet Driver18Logix OptionsDescriptions of the parameters are as follows:lllllProtocol Mode: This parameter specifies how Logix tag data is read from the controller. This optionshould only be changed by advanced users who are loo
Allen-BradleyControlLogixEthernetDriver Socketerror code occurredon devicename .Operation operationname failedbecause reason . 99 Unabletobindtoadapter: adapter .
![INDEX [gfgenealogy ]](/img/44/index-to-wills-cascade-county.jpg)
