Laden...

Allen-Bradley ControlLogix Ethernet

Weitere Details in den Kaufinformationen einsehen
Download Free Demo

Produktübersicht

Der Allen-Bradley ControlLogix Ethernet-Gerätetreiber kann gemeinsam mit KEPServerEX verwendet werden, um den Datenaustausch zwischen OPC/DDE-Clients und Allen-Bradley ControlLogix-Controllern via Ethernet zu ermöglichen.

Der ControlLogix Ethernet-Gerätetreiber unterstützt die Kommunikation mit 1761-NET-ENI, der Micrologix-Reihe, dem festen E/A-Prozessor SLC 500, der modularen E/A-Reihe SLC 500 und der PLC 5-Reihe. Darüber hinaus ermöglicht der Treiber Konnektivität mit der ControlLogix 5500-Reihe, der CompactLogix 5300-Reihe und der FlexLogix 5400-Reihe mit Unterstützung für 1761-NET-ENI-Reihe B. Weitere Informationen finden Sie im Handbuch für den Allen-Bradley ControlLogix Ethernet-Gerätetreiber.

Für diesen Treiber ist keine Lizenz für Rockwell Automation RSLinx erforderlich.

Ressourcen

Leistung

  • Unterstützung für größere Pakete für ControlLogix Controller Version 20 und höher (konfigurierbar bis auf 4000 Byte) für verbesserte Performance
  • Serial Gateway-Unterstützung mit nicht verbundenem Messaging, das Zugriff auf ControlLogix-, CompactLogix-, FlexLogix- und SoftLogix-Geräte über den seriellen ControlLogix-Anschluss ermöglicht
  • EtherNet/IP-Gateway-Unterstützung mit Zugriff auf EtherNet/IP-fähige MicroLogix-, SLC- und PLC 5-Geräte über das ControlLogix Ethernet-Kommunikationsmodul
  • ControlLogix – Performance-Verbesserungen
  • Unterstützung des ControlLogix Gateway-Zugriffs über Data Highway Plus- und ControlNet-Netzwerke
  • Unterstützung für Geräte-Routing, das den Zugriff auf ControlLogix-, PLC 5- und SLC 500-SPSen über jede beliebige verbundene Netzwerktopologie ermöglicht
  • Automatische Tag-Datenbankgenerierung über Online-"Connect to Device" oder L5K- und L5X-Dateien
  • Unterstützung für Allen-Bradley Logix-Tag-Datenbankgenerierung
  • Unterstützung des Zugriffs auf alle vordefinierten Strukturdatentypen (wie CAM, AXIS usw.)
  • Verbundenes Messaging für Lese-/Schreib-Transaktionen
  • Hinweis: Der Treiber ist Bestandteil unserer Allen-Bradley Suite. Wenn Sie den Allen-Bradley ControlLogix Ethernet-, den Allen-Bradley DF1-, den Allen-Bradley DH+-, den Allen-Bradley Unsolicited- oder den Allen-Bradley PLC5/SLC505 Ethernet-Treiber erwerben, berechtigt Sie dies zur Verwendung aller Treiber.

Protokolle

  • EtherNet/IP

Unterstützte Geräte

  • CompactLogix 5320
  • CompactLogix 5323
  • CompactLogix 5330
  • CompactLogix 5331
  • CompactLogix 5332
  • CompactLogix 5335
  • CompactLogix 5345
  • CompactLogix 5370
  • CompactLogix 5380
  • ControlLogix 5550
  • ControlLogix 5553
  • ControlLogix 5555
  • ControlLogix 5561
  • ControlLogix 5562
  • ControlLogix 5563
  • ControlLogix 5572
  • ControlLogix 5573
  • ControlLogix 5574
  • ControlLogix 5575
  • ControlLogix 5580
  • FlexLogix 5433
  • FlexLogix 5434
  • MicroLogix 1000
  • MicroLogix 1100
  • MicroLogix 1200
  • MicroLogix 1400
  • MicroLogix 1500
  • PLC 5 Control Net
  • PLC 5/10
  • PLC 5/15
  • PLC 5/20
  • PLC 5/20C
  • PLC 5/25
  • PLC 5/30
  • PLC 5/40
  • PLC 5/40C
  • PLC 5/60
  • PLC 5/80
  • PLC 5/80C
  • SLC 5/01
  • SLC 5/02
  • SLC 5/03
  • SLC 5/04
  • SLC 5/05
  • SLC 500 Fixed I/O Processor
  • SoftLogix 5810
  • SoftLogix 5830
  • SoftLogix 5860

Verfügbare Sprachen

  • Deutsch
  • Englisch
  • Japanisch
  • Simplified Chinese

Anwendungsunterstützung

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Version 1.02
  • SuiteLink and FastDDE for Wonderware

Versionshinweise

6.5.829.0

19.06.2018

  • Added support for firmware V31, including new Energy tags.
  • Added the channel and device information to "Project online edit detected" event log messages.

6.4.321.0

13.12.2017

  • Behebung eines Problems beim Laden alter Standardwerte mit oberem Grenzwert der Array-Anzahl
  • Behebung eines Problems mit der automatischen Tag-Generierung aus Projekten, deren Struktur das Wort "hidden" enthält.

6.3.305.0

11.06.2018

  • Fixed issue where the value of Array Count Upper Limit could be loaded in below the minimum from v5 projects.
  • Fixed an issue where Automatic Tag Generation on a project with a hidden structure yielded an unknown error.

6.2.506.0

11.06.2018

  • Fixed an issue where the value of Array Count Upper Limit could be loaded in below the minimum from v5 projects.

6.2.460.0

06.07.2017

  • Neu: Unterstützung der chinesischen Sprache.

6.1.655.0

11.06.2018

  • Fixed an issue when loading v5 projects where Array Count Upper Limit could be loaded below its minimum value.

6.1.601.0

04.04.2017

  • Die Firmware-Versionen 29 und 30 werden jetzt unterstützt.
  • Behebung eines Problems, bei dem Lesevorgänge bei einem Array mit dynamischer Adresse fehlschlagen, wenn kein Datentyp angegeben wird.
  • Erweiterter Treiber für die neuen CIP-Datentypen in Firmware 28.012.
  • Behebung eines Problems, bei dem beim Hinzufügen eines dynamischen booleschen Tags mit einem nicht unterstützten Datentyp scheinbar ein gültiges Tag hinzugefügt wurde.

6.0.2206.0

11.06.2018

  • Fixed issue where the value of Array Count Upper Limit could be loaded in below the minimum from V5 projects.

6.0.2107.0

15.11.2016

  • Neu: Support auf Deutsch.
  • Neu: Support auf Japanisch.
  • Stations-/Knoten-ID für EIP Gateway-Modelle (PLC-5, MicroLogix, SLC Fixed und SLC Modular) wird nun validiert und auf Angabe von ENBT-Kanal und Remote-IP überprüft.

5.21.235.0

11.06.2018

  • Fixed an issue where data types could be misinterpreted.

5.21.114.0

20.03.2017

  • Lösung eines Problems, bei dem Lesevorgänge bei einem Array mit dynamischer Adresse fehlschlagen, wenn kein Datentyp angegeben wird.
  • Aktualisierung des Treibers, damit UDTs korrekt gemäß Firmware 28.012 verarbeitet werden.

5.21.112.0

16.08.2016

  • Fixed an issue where tags stayed in “Bad” quality following a project download or toggle of device data collection.

5.20.396.0

03.05.2016

  • Added support for V28 firmware.
  • Added support for L8 Series controllers.

5.19.467.0

20.10.2015

  • Added support for V26 and V27 firmware.
  • Resolved an issue where a dynamic array tag could be orphaned due to an abrupt disconnection of the client. On reconnect, the array tag was unable to be re-added by the client.
  • Resolved issue that prevented reading arrays with more than 65535 elements when using the Logical Blocking protocol mode.

5.18.662.0

23.06.2015

  • Added support for reporting socket errors in the Event Log when connecting, sending, and receiving data.
  • Fixed an issue where the first read from a device that had been in an error state returned bad quality. The read now returns good quality if the device is available
  • Fixed an issue where the thread count increased when changing the device ID via a System Tag.

5.17.495.0

24.02.2015

  • Added support for V23 and V24 firmware.
  • Updated the driver to work with future-generation devices and firmware. Before this fix, the driver experienced a communications failure with these devices.
  • Increased the maximum channel limit from 256 to 1024.
  • Fixed an issue where automatic tag generation from an L5K file failed if the L5K contained an AOI parameter that aliased another parameter. AOI alias parameters are not supported in automatic tag generation and should not be automatically generated.
  • For Logix FRN V24, updated Predefined Data Types for offline automatic tag generation and added new members to AXIS_CIP_DRIVE, AXIS_CONSUMED, AXIS_GENERIC, AXIS_GENERIC_DRIVE, AXIS_SERVO, AXIS_SERVO_DRIVE, AXIS_VIRTUAL, and MOTION_GROUP per Logix FRN V24 changes.

5.16.722.0

21.10.2014

  • Fixed an issue where device reads may be starved for a device under a channel if another device under the same channel is not in an error state. This would prevented the device in an error state from coming out of the error state.
  • Fixed an issue where a buffer overflow could occur with writes containing 500 or more characters.

5.15.585.0

22.07.2014

  • Enhanced the driver to allow default data types to be replaced by the data type returned from the controller. This does not require clients to specify the data type upfront.
  • Fixed an issue where Boolean array writes were not supported in Logical Mode.

5.14.491.0

18.02.2014

  • Fixed an issue where channels would suddenly stop communicating. This was a rare occurrence that had to do with improper event handling.
  • Fixed an issue where reading arrays of 64 bit data types (LINTs) that spanned multiple transactions would fail.
  • Fixed an issue where switching from Symbolic Mode to any Logical Protocol Mode without reinitializing the server would not honor the Logical Mode and would stay in Symbolic Mode.
  • Expanded and made configurable the CIP Connection size for Logix models. The supported range is now 500 to 4000 where it had previously been hard set to 500.
  • Note: CPU and EtherNet/IP modules must support Large Forward Open for connection sizes greater than 500 bytes.

5.13.191.0

15.10.2013

  • Fixed an issue introduced in server version 5.11 where in certain conditions, reads and writes would be performed in the reverse order in which they were submitted to the driver from a client application.
  • Corrected the message size estimation for Symbolic Writes, which was making it possible to underestimate and overflow a request packet.

5.12.140.0

18.06.2013

  • Fixed a defect in which the "Synchronize with Controller after" settings were not being respected with regard to Online and Offline edits.
  • Changed a behavior where the driver will now retry tags instead of failing them upon detecting an Online or Offline edit (except for Downloads). It's likely that the next attempt will succeed. Also, Offline edits will take priority over Online edits if both occur before being detected by the driver.
  • Fixed an issue where the Protocol Mode drop-down selection arrow would not redraw correctly if the selection invoked a vertical scroll bar in the grid.

5.11.262.0

03.05.2013

  • Fixed an issue where synchronization failed on controllers with Firmware revision 15 or older that contained CAM_PROFILE Tags. This caused the driver to revert to and stay in Symbolic Mode.

5.11.250.0

05.03.2013

  • Added Device-level error message for Identity request failures.
  • Added project change detection support for online and offline project edits. Device setting, "Synchronize with Controller after", is available on the Logix Options property page.
  • Following a project download or edit is a period in which Logical reads/writes resort to Symbolic mode, after which the driver synchronizes with the controller so Logical reads/writes can resume. This time period has been lowered from 60 seconds to 30 seconds to improve recovery time.
    1. In the event of an "Invalid or corrupt project" error during synchronization, we now wait 30 seconds until retrying again. Before we retried immediately which caused unnecessary upload attempts and event log errors.
    2. Added support for failing a synchronization in progress as soon as a project download is detected. Synchronization will be retried after 30 seconds.
  • Fixed issue that was causing an unnecessary event log message to be posted if a project change occurs during a CIP reconnect (Idle Watchdog expires).
  • Improved logic that determines how many reads or writes can fit in a single packet, yielding a slight increase in performance.
  • Message size estimation for Symbol Instance reads was incorrect for array element blocks whose starting offset exceeded 255 (likely), making it possible to underestimate and overflow a request packet.
  • Message size estimation and generation for Symbol Instance writes was incorrect for paths exceeding 255 in size (unlikely).
  • Update for Logix FRN V21. Updated Predefined Data Types for offline ATG per Logix FRN V21:
    1. Added new pre-defined types, DATALOG_INSTRUCTION and HMIBC.
    2. Added several new members to ALARM_ANALOG, ALARM_DIGITAL, and AXIS_CIP_DRIVE per V21 changes.

5.10.205

13.11.2012

  • Added support for a new service introduced in Logix FRN V21 for reading Native Tags, called Symbol Instance Addressing. Physical addressing has been deprecated for V21 but is still supported in the driver for Logix FRN V20 and below. Replaced Physical Non-Blocking and Physical Blocking with Logical Non-Blocking and Logical Blocking to encapsulate these two services.
  • Improved the demotion of tags while in an error state by increasing the number of tags failed per transaction. The driver still attempts at least one read tag per transaction to recover from the error state. This does not apply when Auto Demotion is enabled.
  • Fixed an issue where project correlation state information was not being properly reset when switching from one device connection to another which could result in that device using Symbolic mode indefinitely.
  • Resolved a buffer overrun issue where the Device ID could become corrupt if the length of the portion preceding the comma exceeded 16 characters.
  • Added an address validation check to ensure a tag's Symbolic address fits within a single CIP packet. If it exceeds a single packet, the tag will fail with "Address out of range".
  • Floats and Doubles written to BOOL, SINT, INT, DINT, and LINT Tags are now clamped in order to prevent roll-over. For example, the Float 4294967395.0 is larger than a DWord (4294967295) and would roll-over to 0. With this fix, 4294967395.0 will be clamped to 4294967295.
  • Fixed an issue that occurred when writing to BOOL and SINT Tags for Serial Gateway models.

5.9.170

26.06.2012

  • Fixed an issue where the Device ID could become corrupt if any three octets of the IP contained exactly three digits and the remaining octet was set to 44.
  • Updated the "Supported Devices" list in the help file to display support for RS Logix V20.
  • Added the '#' symbol to the ControlLogix Predefined Tag addressing syntax as an alternative to the '@' symbol. Previous usage of the '@' symbol conflicted with the dynamic tag addressing syntax used by the server.
  • Added the new device-level internal tag "_FailedConnection" that indicates the driver failed on its attempt to connect to the device.

5.8.109.0

21.02.2012

  • Fixed the incorrect font that was applied to the Channel Wizard dialog "Suggestions" on Chinese language operating systems.
  • Added support for the following pre-defined tags: @REVISION, @STATUS, @MODE, @VENDORID, @PRODUCTCODE, @PLCTYPE, and @PROCESSORNAME.
  • Fixed an issue where the driver could report incorrect data to client applications if the value read was greater than 262,136 bytes (such as in an array of 65535 DINTs). This only occurred on devices configured for Physical Blocking Mode.
  • Updates for RSLogix version 20. The following was included for offline automatic tag generation:
    • Added the new pre-defined types DCAF_INPUT and DCA_INPUT.
    • Added several new members to the following (per V20 changes): AXIS_CIP_DRIVE, AXIS_CONSUMED, AXIS_GENERIC, AXIS_GENERIC_DRIVE, AXIS_SERVO, AXIS_SERVO_DRIVE, AXIS_VIRTUAL, COORDINATE_SYSTEM, MOTION_INSTRUCTION, and MOTION_GROUP.
  • Performance statistics are now properly disabled when non-ControlLogix models are selected.

5.7.84.0

24.10.2011

  • Fixed a threading issue that could cause a channel to stop communicating on systems with multiple CPUs.

5.6.122.0

25.07.2011

  • Fixed an anomaly in which the device properties Tag Import File and Display Descriptions could be enabled for models that do not support Automatic Tag Generation (such as in MicroLogix).
  • Added a check for a delete pending on each tag before the tag is issued for device communication.
  • Added Serial Gateway support with unconnected messaging, which provides access to ControlLogix, CompactLogix, FlexLogix, and SoftLogix devices via the ControlLogix serial port.
  • Added support for EtherNet/IP Gateway, which provides access to EtherNet/IP-enabled MicroLogix, SLC, and PLC-5 devices via the ControlLogix Ethernet Communications module.
  • Fixed a write issue with LBCD arrays where the driver was writing to every fourth Dword instead of every fourth byte.
  • Fixed discrepancies between L5K and L5X import. Added handling to respect ExternalAccess for AOI Parameters and Data Type members.
  • Resolved an issue where the driver was not correctly handling the connection routing path to a remote device which could cause the driver to fail Automatic Tag Generation and report an invalid device ID.
  • Limited Serial Gateway node id to DF1 limit of 254.

5.5.98.0

02.03.2011

  • A problem has been corrected which could cause data requests to MicroLogix models to fail with CIP Error 0x08.

5.5.94.0

18.02.2011

  • Added support for RSLogix version v19.
  • Added a new check box setting in the Logix Options page of the driver called "Automatically Read String Length". When unchecked, string reads will be optimized by having the driver bypass the LEN member read and terminate the DATA string at either the first null character encountered or the maximum string length of DATA (whichever occurs first).
  • Beginning with L7x controllers, an optimization in controller memory restricts that memory cannot be accessed on a non-DWord boundary or a controller fault will occur. Because the driver was not aware of this restriction, it was possible it could fault the controller while performing Physical reads or writes. To address this issue, the driver now identifies the controller and makes the proper Physical memory access.
  • Fixed an issue where tags stopped updating under certain PC environments running a multi-core CPU.

5.3.118.0

09.06.2010

  • Added support for RSLogix version 18.

5.2.133.0

18.02.2010

  • Modified the driver to support locale-specific multi-byte strings.
  • Resolved an issue with Auto Tag Generation that occurred if a project correlation error was detected.
  • Increased the maximum number of Programs supported from 512 to 1024.
  • Fixed application exception that can occur when multiple Logix Array elements are added and removed at random, followed up by a project upload (due to inactivity, change in project, etc).

5.1.71.0

21.10.2009

  • Fixed issue where L5K files with lines longer than 32768 characters would not import correctly.
  • Fixed various anomalies where tags could not be auto generated via L5K.
  • Added support for automatic tag database generation using .L5X files.
  • Fixed Predefined Data Type tag names created during an L5K/L5X import to match the new names used in online tag generation with V17.
  • Added support for asynchronous hostname resolution.
  • Added support for predefined types as part of support for firmware revision 17: AUX_VALVE_CONTROL, CAMSHAFT_MONITOR, CB_CONTINUOUS_MODE, CB_CRANKSHAFT_POS_MONITOR, CB_INCH_MODE, CB_SINGLE_STROKE_MODE, CC, CONFIGURABLE_ROUT, DCI_MONITOR, DCI_START, DCI_STOP, DCI_STOP_TEST, DCI_STOP_TEST_LOCK, DCI_STOP_TEST_MUTE, EIGHT_POS_MODE_SELECTOR, IMC, MAIN_VALVE_CONTROL, MANUAL_VALVE_CONTROL, MMC, MUTING_FOUR_SENSOR_BIDIR, MUTING_TWO_SENSOR_ASYM, MUTING_TWO_SENSOR_SYM, SAFETY_MAT, THRS_ENHANCED. Also added support for new "Guard" members for AXIS_SERVO_DRIVE.

5.0.1176.0

22.07.2009

  • Fixed performance issue for DH+ Gateway, ControlNet Gateway, ENI and Micrologix models where writes and priority reads could be starved in a low bandwidth/slow response time scenario.
  • Fixed issue where the driver generated names for imported array tags with 'CONDENSED' tag hierarchy incorrectly. The generated names were instead in the EXPANDED format.
  • Fixed issue where the driver could occasionally read/write empty data for string tags. This only happened for projects with multiple channels.

Details zu unterstützten Geräten

  • ControlLogix 5550, 5553, 5555, 5561, 5562, 5563, 5572, 5573, 5574 und 5575 über das 1756 ENET/ENBT-Modul, Serial Gateway oder die 1761 NET-ENI-Reihe B über Kanal 0 und 5580 via 1756-L83 und 1756-L85 (28.011)
  • CompactLogix 5320, 5323, 5330, 5331, 5332, 5335, 5345 und 5370 über den integrierten EtherNet/IP-Anschluss auf Prozessoren mit E-Suffix, Serial Gateway oder 1761-NET-ENI-Reihe B über Kanal 0 und 5380 via 5069-L320ER (28.011) oder 5069-L340ERM
  • SoftLogix 5810-, 5830- und 5860-Prozessoren über das SoftLogix EtherNet/IP Messaging-Modul oder Serial Gateway
  • FlexLogix 5433- und 5434-Prozessoren über 1788-ENBT Ethernet Daughtercard, Serial Gateway oder die 1761-NET-ENI-Reihe B über Kanal 0
  • PLC 5 Control Net über DH+ Gateway, 1761-NET-ENI, oder EtherNet/IP-Gateway
  • PLC 5/10, 5/15, 5/20, 5/20C, 5/25, 5/30, 5/40, 5/40C, 5/60, 5/80 und 5/80C über ControlNet-Gateway, 1761-NET-ENI oder EtherNet/IP-Gateway
  • Fester E/A-Prozessor SLC 500 über 1761-NET-ENI oder EtherNet/IP-Gateway
  • Modularer E/A-Prozessor SLC 5/01, 5/02, 5/03, 5/04 und 5/05 über DH+ Gateway, 1761-NET-ENI oder EtherNet/IP-Gateway
  • MicroLogix 1000, 1100, 1200, 1400 und 1500 über 1761-NET-ENI, MicroLogix 11/1400 Kanal 1 (Ethernet) oder EtherNet/IP-Gateway

Was ist ein Treiber?

KEPServerEX ist nicht nur ein OPC-Server, sondern eine Konnektivitätsplattform für industrielle Automation und das IoT. Laden Sie KEPServerEX einfach herunter, und wählen Sie aus der Kepware Bibliothek mit über 150 Geräte- und Clienttreibern sowie erweiterten Plugins die passenden Treiber und Plugins für die Kommunikationsanforderungen Ihres industriellen Steuerungssystems aus.

Ein Treiber ist eine Softwarekomponente, mit der KEPServerEX die Konnektivitätsanforderungen eines bestimmten Geräts, Systems oder einer anderen Datenquelle erfüllen kann. Der Treiber übernimmt für KEPServerEX die gesamte proprietäre Kommunikation mit der Datenquelle, während die Clientschnittstellen die unterstützten OPC-Verbindungen sowie Verbindungen gemäß proprietären und offenen Standards mit Anwendungen zur Überwachung oder Steuerung der Geräte verwalten.

Treiber können einzeln oder als Teil von Suiten lizenziert werden. Je nach Entwicklung der Verbindungsanforderungen können zusätzliche Suiten lizenziert werden.

Informationen zum Kauf

Allen-Bradley ControlLogix Ethernet

Dieses Produkt kann im Rahmen der folgenden Suiten erworben werden:

Webinar zum Thema Allen-Bradley-Konnektivität

Erfahren Sie, wie Sie Kepware Allen-Bradley-Treiber für die KEPServerEX Konnektivitätsplattform verwenden, um ganz einfach ein leistungsstarkes Automationssystem zu erstellen.

Jetzt anmelden