AB1756冗余机架配置
1756-PA75R∕A电源模块使用说明书
140CPS52400C
140CPS52400
140CPS51100C
140CPS51100
1746-A10
1746-A13
1746-A2
1746-A4
1746-A7
1746-BAS
1746-BAS-T
1746-BLM
1746-BTM
1746-C16
1746-C7
1746-C9
1747-ACN15
1747-ACNR15
1747-AENTR
1747-AIC
1747-ASB
1747-BA
1747-BAJMPR
1747-BSN
1747-C10
1747-C11
1747-C13
1747-C20
1747-CP3
1747-DCM
1747-DEMO-7
1747-DPS1
1747-DPS2
1747-DU501
1747-FC
1747-INTWINBAS
1747-KE
1747-KFC15
1747-KY1
1747-L511
1747-L514
1747-L524
1747-L531
1747-L532
1747-L533
1747-L541
1747-L542
1747-L543
1747-L551
1747-L552
1756pa75ra电源模块使用说明书controllogix电源供应模块与1756机架一起使用用于提供直流12v33v5v24v电源给机架背板
1756-PA75R∕A电源模块使用说明书
1756-PA75R∕A电源模块使用说明书
ABB PLC冗余配置及其OPC操作指导
AC500文档编号：ＡＤ２１０００３AC500 HA声明(1) 在实际的系统构建时，请先确认系统组成设备、装置，如使用过程中对额定值、性能留有余量，以及万一发生故障时将危险降到最低的安全电路等。
(2) 为了安全使用系统，请获取组成系统的各个设备、装置的指南及安装说明书，在确认好包括“安全注意事项”、“安全要点”等内容后再使用。
(3) 本文件所属的产品/系统只允许由具备相关工作经验要求的合格人员进行操作，确认适合系统的规格、法规及规定。
(4) 未经ABB公司许可，严禁擅自对本资料的一部分或全部内容进行篡改及散发。
(5) 本资料的记录内容为测试指导，在应用过程，请根据现场实际情况适当调整，或者咨询ABB技术支持人员。
(6) 我们已对文档中所述内容与硬件和软件的一致性作过检查。
然而不排除存在偏差的可能性，因此我们不保证文档中所述内容与硬件和软件完全一致。
文档中的数据都按规定经过检测，必要的修正值包含在下一版本中。
(7) 本资料的记录内容若有改版，恕不另行通知。
1 (3)1.1 (3)1.2 (3)2 (4)2.1 (4)2.2CS31 (5)2.2.1AC500 CPU COM1 (5)2.2.2CI590-CS31-HA (5)2.3 (6)3HA (7)3.1 (7)3.2 (7)3.2.1 CS31 (7)3.2.2 CS31 CI590-CS31-HA (8)3.2.3 CI590-CS31-HA I/O I/O (10)3.3 (11)3.3.1 AC500 HA (11)3.3.2 CPU STOP (13)3.3.3 AC500 HA (15)4 (20)4.1 IP (20)4.2 (20)5 (24)5.1CI590-CS31-HA (24)5.2 HA (26)5.3HA (26)5.3.1 (26)5.3.2 (27)5.4 HA (29)6 (31)6.1 (31)6.1.1 (31)6.1.2 (31)6.1.3 (31)6.1.4 (32)6.2 (32)6.2.1HA (32)6.2.2 (36)7OPC (38)7.1 (38)7.1.1 (38)7.1.2 OPC Server (38)7.1.3 (41)7.2OPC (43)7.2.1 CoDeSys OPC (43)7.2.2 OPC Configurator OPC Server (44)7.3OPC (48)1AC500 HA1.11 CoDeSys2 Control Builder plus1.2PM583-ETH 2 V2.1.3CM577-ETH 2CI590-CS31-HA 1DC522 131PC 1 PS501 CBP CoDeSys ——CoDeSys OPC-Server AE V3.3 SP2 ——OPCserverOPC SOClient.exe —— OPC22.1AC500 CPU PM583-ETH CPUCPU CPU CPU CPU CI590-CS31-HA DC522 CS31 CPU CM577-ETH PC OPC2.2 CS312.2.1 AC500 CPU COM12 CPU CS312.2.2 CI590-CS31-HA3 CI590-CS31-HA4 CI590-CS31-HA2.3CI590-CS31-HA 0~61 70~131 +704 CI590-CS31-HA3HA3.11) ABB Configrator ’FileNew Project ’ AC500PLC CPU – ‘AC500 PM583-ETH V2.03.23.2.1 CS31‘COM1’ ‘Plug Device’ , ‘COM1-CS31-Bus ’ ‘Plug Device’ .‘COM1 – CS31-Bus’ ‘COM1 – CS31-Bus Configuration’ ‘Run on config fault’ ‘Yes’3.2.2 CS31 CI590-CS31-HA‘COM1 – CS31-Bus’ ‘Add Device’ ‘CI590-CS31 16DC’ ‘CI590 16DC + 2 FC’‘CI590-CS31-Bus’ CI590-CS31 Configuration ( 0-61). (70 + Control Builder Plus )I/O Mapping3.2.3 CI590-CS31-HA I/O I/O‘CI590 CS31’ -> Add device I/OI/O I/O Mapping1) 2 3 CS31 CI590-CS31-HA2) AC500 HA CPU‘PM5x1-ETH-Onboard –Ethernet ’ ‘Add Device ’ UDP data exchange ‘Add Device ’.3.33.3.1 AC500 HACoDeSysCoDeSys , ‘Resources ’ ‘Library Manager ’; ‘Additional Library’AC500 High availability HA_CS31_AC500_V20.lib ‘open’AC500 High availability HA_CS31_AC500_V20.lib ,3.3.2 CPU STOPCPU STOP‘POUs’ ‘POUs “Add Object’program “CALLBACK_STOP’CPU STOP “CALLBACK_STOP‘CALLBACK_STOP’ ‘HA_CS31_CALLBACK_STOP’ Standard Programs HA_CS31_AC500_V20.libCPU STOP “CALLBACK_STOP’‘Task configuration ‘stop’ POU ‘CALLBACK_STOP’3.3.3 AC500 HAAC500 HA HA_PRGAC500 POU (PRG) ‘POUs ’ ‘POUs ’ ‘Add Object HA POU HA_PRG ProgramAC500 HAHA_PRGHA_PRG ‘Resource ‘Task configuration , ‘Task configuration ’ ‘Append Task ’( HA_Task) ‘Cyclic t#10ms t#10ms 60ms‘NewTask’ ‘Append Program Call HA_PRGAC500 HA HA_PRGHA HA HA_PRG PLC_PRG HA_PRG HA_CS31_DIAG HA_CS31_CONTROL PLC_PRGHA_CS31_DATA_SYNC HA_CS31_FBsHA_PRG ‘POUs HA_PRG HA_PRG HA_CS31_DIAG HA_CS31_CONTROL44.1 IPHA CPU CPU IP PLCA 192.168.0.1PLCA 192.168.0.2IP AC500 IP “ IP config tool IP ”4.2IP PS501 CPUA 192.168.0.1 CPUB 192.168.0.2CPUAIP PS501 ‘online’ ‘Communication Parameters’‘New’ ( 192.168.0.1) ‘Tcp/Ip’ (3S Tcp/ip driver) ‘OK’‘localhost’ CPU IP ( 192.168.0.1) ‘Port’ 1201 ‘Motorola byteorder’ ‘Yes’ ( ‘No’ ) ‘OK’ .‘online’ ‘Login’.CPU a CPU b ‘Yes’ CPUabCPU ‘online’ ‚‘Creat boot project PLC’AC500 CPU55.1CI590-CS31-HACI590-CS31-HA 8HA PWR CS31-A CS31-B I/O Bus S-ERR OFF RUN A RUN B ON CPU CPUCPUA/B CI590-CS31-HA CS31 CPU CS31-A CS31-BCPU CPU SYNC-ERR2HZ HA FALSE-TRUESYNC-ERR I\O Bus S-ERR5.2 HA,H A_CS31_DIAGDEC HEX Error description4129 16#1021 No configured CI590 slave is active (missing module)8193 16#2001 Wrong COM number at input COM8233 16#2029 CI590 slaves in line A and line B are mix-wired12291 16#3003 No CS31 protocol at COM12329 16#3029 CI590 slave configuration incompleteHA_CS31_CONTROLDEC HEX Error description4123 16#101B Remote CPU failure => Other CPU is off or out of order4129 16#1021 Own CI590 slave failure (missing module)4137 16#1029 Remote CI590 slave failure (missing module)8197 16#2005 CS31 Bus failure8211 16#2013 No Ethernet link8219 16#201B Remote CS31 bus failure => Other CPU's CS31 Bus is out of order8220 16#201C Numbers of CI590 devices configured in line A and line B are different 8226 16x2022 HA_DATA Reference table overflow8233 16#2029 Mix-wiring of the CS31 Masters between line A and line BHA_CS31_DATA_SYNCDEC HEX Error description8226 16#2022 HA_DATA Reference table overflow5.3HA5.3.1HA CPUA CPUBCPU CI590-CS31-HA PLC CPU CI590-CS31-HAHA_CS31_DATA_SYNC HA_CS31_FBs CPU CPU CPU CPU CPUCPU5.3.2HA1) CPUCPUCPUCPUCPUCPUCS31 CI590-CS31-HACS31 CI590-CS31-HAOPC Server OPC Server ConfigurationConfigurationPrimary CPUPrimary CPUSecondary CPUSecondary CPUOPC ServerOPC Server Configuration Configuration Primary CPUPrimary CPU Secondary CPUSecondary CPU2) CPU CPUCPUCPU CPU CPUCPUCS31 CI590-CS31-HA CS31 CI590-CS31-HA3) CPU CPUCS31CI590-CS31-HA CI590-CS31-HACI590-CS31-HA CPU4) CPU5.4 HAHA:1)2) CPUCPU STOP CPUCPU RUN “ CPU3) CPU CPUCPU STOP CPU CPUCPU RUN “ CPU4)66.16.1.1CPU CPU V1.2CPUPM573-ETH AC500 CPUAC500-eCo CPUCI590-CS31-HA DC551-CS31S500 I/O S500-eCo6.1.2PS501 V 1.36.1.3HA CS31 CS31 CS31 CS31 IO 192 I/O 600 I/O31 ( 3720 I/O )CS311)3131120 DI+120 DO8 AI+8AO2) Cluster6.1.41)HA CI590-CS31-HA2)CI590-CS31-HA3)CS314) 500m 2000m5) CI590-CS31-HA A CPU CPU A CPUCI590-CS31-HA B CPU CPU B CPU CS316.26.2.1HAHA HA HA_CS31_AC500_V20.lib ,1 HA_CS31_CONTROL HA2HA_CS31_DATA_SYNC HA3HA_CS31_DIAG HA4HA_CS31_DIAG_EXTD HA5HA_CS31_CALLBACK_STOP HA CPU STOP6HA_CS31_CTD HA7HA_CS31_CTU HA8HA_CS31_CTUD HA9HA_CS31_INTEGRAL HA10HA_CS31_PID HA PID11HA_CS31_PID_FIXCYCLE HA PID12HA_CS31_RAMP_INT HA13HA_CS31_RAMP_REAL HA14HA_CS31_TOF HA15HA_CS31_TON HA1)HA_CS31_CONTROLAC500 HA CPU CPU HA CPUHA_CS31_CALLBACK_STOPAC500 HA CPU STOP2)HA_CS31_DIAGCS31 CI590-CS31-HAHA_CS31_EXT_DIAGHA ;3)HA_CS31_DATA_SYNC2563…HA_CS31_FBsHA HAHA_CS31… CPU6.2.21) HA_CS31_DATA_SYNCR_TRIGR_TRIGHMI CoDeSys CPU2) HA_CS31_FBsPID HA_CS31_FBs7OPC7.17.1.1HA OPC OPC-Server CoDeSys OPC-Server AE V3.3 SP2OPC-Server OPC / OPC ServerCoDeSys CoDeSysOPC server“WinCoDeSysOPC.exe /RegServer”7.1.2 OPC Server1) OPC Server“WinCoDeSysOPC.exe”2) OPC server“WinCoDeSysOPC /UnRegServer” OPC server“WinCoDeSysOPC /Service” WinCoDeSysOPC.exe“dcomcnfg” WindowsWindows “CoDeSysOPCDAService”“CoDeSysOPCDAService”“System”7.1.3“CoDeSysOPCDAService”“CoDeSysOPCDAService”“ ”“Gateway.exe” “WinCoDeSysOPC.exe” “CNSIHUA”,7.2OPCOPC AC500HA OPCCoDeSys OPC PLCOPC Configurator OPC ServerOPC7.2.1 CoDeSys OPCHA CoDeSys OPC PLC OPC 3.3.23.3.3 PLCHA CPU7.2.2 OPC Configurator OPC ServerHA OPC Server PLC OPC OPC OPCOPCOPCCPUOPC 3.4 OPCPLC1 PLC2 CPU “Connection” “Address”“Connection” “Address” CPUA CPUB IP 192.168.0.1 192.168.0.2 PLC CM577-ETH 92.168.0.10 192.168.0.20Server “New Redundancygroup”, Redundant0Redundant0 “Available PLCs” PLC1 “>>” PLC2PLC CPUA PLC1PLC1 “select PLC in group to set master variable” HA “.fG_HA_PRIMARY” PLC2 “LifeCounter Variable(all PLCs in group)” HA “.dwG_HA_ServerAlive”HA7.3OPCOPC HA OPC SOclient.exe OPC OPC 4.OPC。
罗克韦尔ControlLogix 机箱 型号 1756-A4, 1756-A7, 1756-A10,
安裝說明ControlLogix 機箱型號 1756-A4, 1756-A7, 1756-A10, 1756-A13, 1756-A17, 1756-A4LXT, 1756-A5XT, 1756-A7LXT, 1756-A7XT, 1756-A10XT,1756-A4K, 1756-A7K, 1756-A10K, 1756-A13K, 1756-A17K產品綜述ControlLogix® 系統是需要 1756 ControlLogix 機箱的模組系統。
機箱的設計僅供水平背板固定。
可將任何模組放置於任何插槽。
背板提供模組之間的快速通訊路徑。
變更摘要我們在這些安裝說明中加入一個 10 個插槽的 ControlLogix-XT® 機箱，型號 1756-A10XT 。
主題 頁次需要之工具4需要的零件5具有無備援電源供應器的系統間隔要求6安裝規模8安裝機箱12機箱接地13規格16其他資源17ControlLogix機箱ATTENTION: Read this document and the documents listed in the Additional Resources section about installation, configuration and operation of this equipment before you install, configure, operate or main-tain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice.If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.注意：在安装、配置、操作和维护本产品前，请阅读本文档以及“其他资源”部分列出的有关设备安装、配置和操作的相应文档。
RockwellABPLC基础培训入门篇
Rockwell AB PLC 基础培训入门篇,7天熟悉AB PLC系统开发第一篇AB的PLC产品长期以来一直被认为最可靠、最高端的PLC产品，产品的质量和性能为世界顶级，AB品牌属于美国ROCKWELL公司，其生产的PLC2（可能很多人并不知道，P LC5知道的人很多，在之前还有PLC2,PLC3产品）产品目前在世界上仍然有很多地方继续在工作。
AB的PLC大致可以分如下几类：1.Logix平台产品，细分如下：ControlLogix、CompactLogix、FlexLogix该系列产品全部采用Logix5000软件进行编程组态2.SLC500平台产品SLC500、MicroLogix该系列产品全部采用Logix500软件进行编程组态3.PLC5,PLC3,PLC2等老产品PLC5采用RsLogix5软件进行编程组态,某些老的型号采用DOS版6200软件进行编程PLC3,PLC2采用DOS版6200软件进行编程组态其中PLC2有几款第3方开发的编程软件，全运行在DOS环境下由于PLC5等产品非目前主流产品，正在逐步被淘汰，因此本文不将其作为讨论的主要内容。
RsLinx技术介绍：RsLinx软件为ROCKWELL产品提供了统一的通讯平台，是进行编程的必要软件之一。
RsLinx软件根据六个版本分为：RSLinx Lite、RSLinx Single Node、RSLinx OEM、RSLinx P rofessional、RSLinx Gateway、RSLinx SDK。
版本在RSLinx OEM以后的4个版本均支持开发OPC应用程序或C-API客户程序，并在RSLinx S DK中包括了开发OPC应用程序或C-API客户程序的技术资料。
标准版，Lite版本，此版本为免费版本，仅支持PLC编程通讯专业版，Professional版本，提供了OPC DDE SERVER功能，可以作为组态软件的通讯驱动，并且支持RSLINX C API开发的应用程序或驱动OEM版，单节点版，很少见，名如其意，也能支持OPC DDE SERVER网关版，Gateway版本，比专业版本增加了Remote 远程访问的能力，如远程OPC等。
AB增强冗余系统版本（精）
AB增强冗余系统版本（精）Release NotesControlLogix Enhanced Redundancy System, Revision 16.81Redundancy Module Catalog Numbers1756-RM, 1756-RMXTController Catalog Numbers1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64Communication Module Catalog Numbers1756-CN2/B, 1756-CN2R/B, 1756-CN2RXT/B, 1756-EN2T,1756-EN2TXT Topic Page About This Redundancy Firmware Bundle2Compatible Software Versions3FactoryTalk View Software Considerations4About the Redundancy Module Configuration Tool4Enhancements5Enhancements with Revision 16.815Enhancements with Revision 16.805Enhancements with Revision 16.548Corrected Anomalies10Corrected Anomalies with Revision 16.8110Corrected Anomalies with Revision 16.8110Corrected Anomalies with Revision 16.5416Known Anomalies17Restrictions19Application Notes22EtherNet/IP Networks and Redundant Systems22Minimum Value for the Watchdog Time22Synchronizing After Disqualification22Using a Redundant System and CIP Equipment Phases24Using the EquipmentPhase.StepIndex Tag24Using Unit Tags26Multiple CIP Data Servers with One FactoryTalk Batch Server26Publication 1756-RN650D-EN-E - February 20102 ControlLogix Enhanced Redundancy System, Revision 16.81About This PublicationThese release notes describe enhancements, corrected anomalies, and known anomalies specific to redundancy system firmware revision /doc/e513220948.htmlrmation newly-added to this release note is indicated by change bars like the one shown to the right of this paragraph.About This Redundancy Firmware BundleThis redundancy firmware bundle is comprised of firmware revisions for each of the modules listed in this table. Upgrade From An Enhanced Redundancy Revision28Store a Project to Nonvolatile Memory While Your Process is Running44AdditionalResources46Topic Page IMPORTANT Only the modules specified in the table below can be used in the enhanced redundancy system and this firmware revision.Modules that are not listed in the table are not compatible with the enhanced redundancy system and are not supported by this redundancy firmware revision.Cat. No.Module DescriptionSeries Firmware Revision1756-CN2ControlLogix ControlNet bride module B 20.0111756-CN2R ControlLogix redundant ControlNet bridge moduleB 1756-CN2RXT ControlLogix-XT redundant ControlNet bridge moduleB 1756-EN2T ControlLogix EtherNet/IP bridge module Any 2.0071756-EN2TXT ControlLogix-XT EtherNet/IP bridge moduleAnyPublication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 3The firmware bundle can be downloaded at: . It is identified as /doc/e513220948.htmlpatible Software Versions Use these versions of software with this redundancy firmware bundle.Software Version FactoryTalk Services Platform2.10.01 (CPR 9, SR1(1(1Use the most recent FactoryTalk Services Platform Patch Roll-up withthis redundancy firmware revision. For the most recent patch roll-up,see Rockwell Automation’s Knowledgebase Answer ID 56184,accessible at: .FactoryTalk Alarms and Events2.10.00 (CPR 9FactoryTalk Batch10.00.26FactoryTalk View Site Edition5.00.00 (CPR 9Redundancy Module Configuration Tool6.2.10RSLinx Enterprise5.17 (CPR 9, SR1(2(2See FactoryTalk View Software Considerations on page 4 for useconsiderations.RSLinx Classic2.54(3(3If your redundant system is comprised of ControlLogix-XT modulesplaced in a 1756-A5XT chassis, RSLinx Classic software, version 2.55,or later, is required.RSLogix 500016RSNetWorx for ControlNet8.00 (CPR 9, SR11756-L61ControlLogix5561 controllerAny 16.811756-L62ControlLogix5562 controller1756-L63ControlLogix5563 controller1756-L63XT ControlLogix-XT controller1756-L64ControlLogix5564 controller1756-RM ControlLogix redundancy moduleA 2.051756-RMXT ControlLogix-XT redundancy module Cat. No.Module DescriptionSeries Firmware RevisionPublication 1756-RN650D-EN-E - February 20104 ControlLogix Enhanced Redundancy System, Revision 16.81FactoryTalk View Software ConsiderationsFactoryTalk View software is required for use only with these human-machine-interfaces (HMIs:?PanelView Plus terminal?VersaView industrial computer running a Windo ws CE operating system ? RSView Supervisory Edition softwareAbout the Redundancy Module Configuration ToolThe Redundancy Module Configuration Tool (RMCT is required for use with the 1756-RM module. Use the RMCT to:? configure redundancy system parameters. F or example, to configure the Auto-Synchronization parameter.?view redundancy system event logs when troubleshooting your system.The RMCT is not packaged with this redundancy firmware revision.RSLinx Classic software includes the RMCT, however, it is not likely to be the version that is compatible with this firmware revision. Complete these steps to obtain the compatible version of the RMCT.1. Access Knowledgebase Answer ID 29511 (available at: . 2. Download the version listed for this redundancy firmware revision. 3. Open the executable file and use the Installation Wizard to install the tool. For information about checking the version of your RMCT, see Upgrade the Redundancy Module Configuration Tool (RMCT on .IMPORTANT If you are using FactoryTalk View Site Edition software, install the RSLinx Enterprise HOTFIX. The HOTFIX improves the EtherNet/IP switchover time. For more information, see Knowledgebase document R154640079. To access Rockwell Automation’s Knowledgebase, go to .Publication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 5 Enhancements These enhancements are provided with enhanced redundancy firmwarerevisions 16.81, 16.80, and 16.54.Enhancements with Revision 16.81This enhancement is provided with standard redundancy firmware revision16.81.Enhancements with Revision 16.80These enhancements are provided with enhanced redundancy firmwarerevision 16.80. System ComponentEnhancement 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64The false execution time of Add-On Instructions have been improved.With previous revisions, the false execution time of an Add-On Instruction was dependent on the number of parameters (input, output, and inout configured for the instruction. The more parameters configured, the longer thefalse execution time of the Add-On Instruction.With this revision, the false execution time of an Add-On Instruction is now constant if a scan false routine is not created. To determine the false execution time of Add-On Instructions based on your controller, reference the values published in the Logix5000 Controllers Execution Time and Memory Use Reference Manual, publication . Lgx00106477Enhancements with Revision 16.80System Component Enhancement 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64Support for redundant controller use with alarm features of FactoryTalk Alarms and Events software.This redundancy firmware revision provides support for alarms as supported by FactoryTalk Alarms and Events software. Alarms can now be embedded in the controller with two new instructions, ALMD and ALMA, available inRSLogix 5000 software. These digital and analog alarm instructions are fully self-contained.Support for redundant controller use with equipment phases.This redundancy firmware revision provides support for equipment phases that can be implemented by using FactoryTalk Batch software and the RSLogix 5000PhaseManager feature. See the Application Notes on for more information about using a redundant system and equipment phases.Publication 1756-RN650D-EN-E - February 20106 ControlLogix Enhanced Redundancy System, Revision 16.811756-RM, 1756-RMXT Auto-qualification and synchronization processes of the 1756-RM module are stopped after a chassis pair first fails tosynchronize.In previous firmware revisions, if the Auto-Qualification parameter is set to Always and the controller in the secondary chassis faulted, or a communication module was removed from the chassis, the 1756-RM module would continuously attempt to qualify the redundant c hassis. As a result of the c ontinuous attempts to qualify, the event logs became filled with synchronization failure events, thus making the originating fault more difficult to troubleshoot.With this firmware enhancement, the 1756-RM module stops auto-qualification and synchronization attempts after the first fault occurs. This makes troubleshooting the original fault easier.Lgx00080574Synchronization failure reports enhanced by adding ’Partner Module not Found’ cause.In previous revisions, if synchronization failed due to partner modules being at incompatible firmware revisions or a secondary module was not installed or powered, then failure was indicated by the same cause statement in the synchronization log of the RMCT. For both types of failures, ’Module Pair Incompatible’ was indicated as the cause. With this firmware revision, the 1756-RM module can differentiate between partner incompatibilities and a missing secondary module. The RMCT indicates a missing secondary module by stating ’Partner Module not Found’ in the Cause column of the Recent Synchronization Attempts log.Lgx00083165Enhancements with Revision 16.80System ComponentEnhancement Module is not installed or powered in chassisModules are at different firmware revisions.Publication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 7Enhancements with Revision 16.80Publication 1756-RN650D-EN-E - February 20108 ControlLogix Enhanced Redundancy System, Revision 16.81Enhancements with Revision 16.54These enhancements were provided with enhanced redundancy firmwarerevision 16.54.Enhancements Provided with Revision 16.54System ComponentDescription 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64Firmware revision 16.54 provides redundancy support for controller programming with Add-On Instructions.Synchronization points for programs within the RSLogix 5000 project can beconfigured.Redundancy firmware revision 16.54 provides the ability to limit which programs are followed by synchronization anddata crossloading. In many applications, changing this can reduce the overall impact to the task scan time by reducing the number of times a data area is synchronized. Removing a synchronization point results in 1 ms of overhead time saved.However, reducing the number of syncronization points may delay the switchover time because more programs may need to be re-scanned by the new primary controller as it starts at the last synchronization point.Synchronization is performed at the end of the last program in the task's program list, regardless of the program’s Synchronize Data after Execution setting.To change the synchronization setting of a program, access the program’s Program Properties dialog box and check or uncheck Synchronize Data after Execution.1756-L64The ControlLogix5564 controller is supported for use in the redundant system with this firmware revision.Redundancy Module Configuration Tool (RMCTSystem Event History accessible via the Redundancy Module Configuration Tool (RMCT.A system event history tab is available in the RMCT and is visible only when the session is launched while onlinewith the 1756-RM module. This feature automatically captures key events occurring in the redundant system that tell why a switchover occurred or why redundancy was lost.Certain events also indicate what caused the chassis pair to become synchronized. There are 10 most recent entries available for viewing. Each entry has a user comment attached to it that can be used to enter system maintenance information.For more details, see the online help of the RMCT.Lgx00073250Event Log provides additional module information.The 1756-RM module is able to report any changes in the application firmware revision and the backplane serial number via entries posted to the Event Log. This information indicates that a firmware upgrade took place and whether the chassis location of the 1756-RM module was changed.Lgx00073278Publication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 9Redundancy Module Configuration Tool (RMCTThe Synchronization Status tab provides module type and firmware revision data.Within the RMCT, the Synchronization Status tab displays the product-name string and firmware revision ofredundancy-compliant modules in the chassis.Lgx000737291756-RM, 1756-RMXT User-identity parameters are retained through a power-cycle.The user identity parameters are now 64 characters in length and are stored in nonvolatile memory of the 1756-RM modules. The parameters are saved to nonvolatile memory whenever a change is made.Lgx00073247The qualification state of the redundant chassis pair is indicated on the module status display.The 1756-RM module in the secondary chassis displays a “QFNG” four character code when the redundant chassis pair is qualifying for synchronization.Lgx00073276The primary 1756-RM module is the Wall Clock Time (WCT master for the secondary 1756-RM module.The 1756-RM module in the primary chassis is the master of the currentTime attribute of the WCT object. When a secondary 1756-RM module is connected, the currentTime attribute in the primary 1756-RM module will be copied over to the secondary 1756-RM m odule to make them the same. The currentTime attribute on the secondary 1756-RM module will be synchronized every second.Lgx00073248The 1756-RM module may be accessed when in a major fault state.In some applications, it may be possible to communicate with the 1756-RM module even if it has already experienced a major nonrecoverable fault. This allows the fault code to be read remotely and facilitates the retrieval of event logs while in the faulted state.Lgx00073258Enhancements Provided with Revision 16.54System ComponentDescriptionPublication 1756-RN650D-EN-E - February 201010 ControlLogix Enhanced Redundancy System, Revision 16.81Corrected AnomaliesThese redundancy system anomalies have been corrected in enhancedredundancy firmware revisions 16.80 and 16.54.Corrected Anomalies with Revision 16.81These anomalies have been corrected with standard redundancy firmwarerevision 16.81.System ComponentDescription 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64A Digital Alarm (ALMD configured to trigger when the input condition of the alarm is false, does not trigger if the alarm condition is false when you conduct a a download or return to run mode.When the Condition parameter of the ALMD instruction is not set (that is, Input = 0 and either the program hasrecently been downloaded to the controller, or the controller has been changed from Run to Program and back to Run mode, the alarm is not activated (that is, the InAlarm bit is not set.These behaviors may result, depending on your application:Programming designed to respond to the activated alarm is not executed.Messages designed to be indicat ed at the operator station in response to the activated alarm are not indicated.The alarm’s history log does not indicate that the alarm was activated.If you choose not upgrade to this revision, you must toggle the Condition parameter from set (that is, Input = 1 to not set (that is, Input = 0 to activate the alarm.If your Condition parameter is set, then the alarm activates as expected after a download or change to the controller mode.Lgx000103444Publication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 111756-L61,1756-L62, 1756-L63, 1756-L63XT, 1756-L64Fault handlers can be defined at the controller and program scope levels. These fault handlers are typically used to handle major recoverable faults that can o ccur during runtime execution of an application due to programming errors. A typical example of this would be handling indirect addressing that has gone out of range; MyTag[index ], where index is larger than the size of the array.Faults can also be handled by the controller during pre-scan of the controller program on the transition to Run mode.Again, for example, the handling of indirect addressing that has gone out of range.There is an anomaly when these methods attempt to handle a fault.These are the possible ways the anomaly can manifest itself:The controller will experience a major non-recoverable fault. I/O goes to their configured safe state, and the user application is cleared from memory. At this point, a Code 1 Type 60 or 61 major recoverable fault will be logged inthe controller. This requires you to redownload the application.Tag data corruption.Online saving or uploading failures.Anomalous program execution.For example, if a rung is being scanned false and there is an instruction that has false execution, the faulthandler executes so the remainder of the rung will scan true. In the example below, the OTE instruction has anindex out of range. After returning from the fault handler, the ADD instruction will execute, even though therung input conditions are false.On redundancy systems only, when the fault handler or power-up handler contains an Add-On Instruction, the new primary controller may fault with a major non-recoverable fault on the second switch-over. These fault conditions can leave the redundancy system without a running primary controller.Lgx00106481, Lgx00107423, Lgx00100766, Lgx00106478System ComponentDescriptionPublication 1756-RN650D-EN-E - February 201012 ControlLogix Enhanced Redundancy System, Revision 16.81Corrected Anomalies with Revision 16.80These anomalies have been corrected with enhanced redundancy firmwarerevision 16.80. The descriptions in this table describe the anomalous behaviorthat you may experience if you do not update to this revision.Corrected Anomalies with Enhanced Redundancy Firmware Revision 16.80System ComponentAnomaly Description1756-CN2, 1756-CN2R, 1756-CN2RXT The 1756-CN2, series B module cannot use a ControlNet network address of 96, or greater, in a redundant chassis pair. If you set the switches on the 1756-CN2, series B module to 96 or greater, and place it in a secondary chassis,the module faults.With this firmware revision, the node address switches of the ControlNet module in the secondary chassis can be setat an address of 98, or less.Lgx00082110A connection closing during phase two of redundant chassis qualification results in a synchronization failure.With this firmware revision, a connection closing during qualification does not cause a synchronization failure.Lgx00092857Attempts to use the ControlNet bridge modules on an unconfigured ControlNet network results in a failure to qualifyand synchronize the redundant chassis.With this firmware revision, ControlNet modules in a redundant chassis can qualify and synchronize when the ControlNet network is not scheduled.Lgx00091856After an event on a 1756-CN2 or 1756-CN2R module causes disqualification of the redundant chassis pair, the secondary chassis continues to appear to be synchronized for up to 30 seconds after the disqualifying event. Even though the redundant chassis pair does not indicate disqualification immediately, the PartnerChassisRedundancyState attribute immediately indicates that no partner is present.During the delayed disqualification, a switchover cannot successfully occur.With this firmware revision, the secondary chassis disqualifies without delay.Lgx000901201756-CN2, 1756-CN2R, 1756-CN2RXT Upon powerup, the OK status indicator of the 1756-CN2 or 1756-CN2R modules may be red and the module status display indicates either:CmdConnOpen.cpp Line 630.RMEventLog.cpp Line 841.This is a result of the ControlNet module inaccurately detecting the size of the redundant chassis.With this firmware revision, the correct chassis size is accurately detected.Lgx00082907Publication 1756-RN650D-EN-E - February 2010ControlLogix Enhanced Redundancy System, Revision 16.81 131756-EN2T After a power cycle switchover and HMI loading, CIP Sync functions of the 1756-EN2T module fail when used in aredundancy system.Rarely, the 1756-EN2T module may powerup and not synchronize CIP Sync time to the grandmaster or may synchronize with an incorrect time.With this firmware revision, the CIP Synch time of the 1756-EN2T module synchronizes with the grandmaster on powerup.Lgx00083465, Lgx00082870As a result of a delayed 1756-EN2T module-response, the 1756-RM module failed and indicated communication error EAE8 after power to the redundant chassis was cycled.With this firmware revision, no delayed response of the 1756-EN2T module occurs.Lgx00079052The 1756-EN2T module refuses all outbound connections via the Ethernet port.After cycling power on the Ethernet switch or router that the 1756-EN2T module is connected to, the 1756-EN2T module may become unresponsive. The affected module does not respond to Ethernet network, backplane, or USB traffic, even though the status indicators remain green and the status display shows no errors.With this revision, the 1756-EN2T module maintains outbound connections.Lgx00081018After a switchover, the new primary 1756-EN2T module resets if the partnered 1756-EN2T module that was the primary is faulted. This may result in a slight delay of the new primary chassis taking control.With this firmware revision, if the primary 1756-EN2T module is faulted, the partnered 1756-EN2T module becomes。
AB_PLC系统组成及简介
常用模块
CPU : 1756L6X、1756L7X系列
通讯模块
1756-ENBT : 以太网通讯
1756-CNB : 工控网通讯
模拟量输入模块
1756-IF16 : 16通 道模拟量输入模 块，支持4~20mA, 电流信号和1~5伏 电压信号
接线时单数号端子要全部短接
1756-IR6I : 6通道 模拟量输入模块， 支持电阻信号。
组态串口
评估控制器内存运 用（离线）
子程序
子程序是真正的执行, 所有的控制代码都被编写在子程序中，有四种编程 形式：
•
梯形图LD 最常采用的编程模式，是由梯级组成的程序结构，完成
逻辑时序控制的程序编辑。
•
顺序功能流程图SFC 将工作流程细化到步，用SFC来编辑步的执
行顺序和结构，而每个步都是执行代码的组成。
• 通讯模块 对应通讯网络的模块 -- 1756-ENBT / 1756-EN2T(R) -- 1756-CNB/CNBR -- 1756-DNB -- 1756-DHRIO
EtherNet ControlNet DeviceNet DH+
ControlLoix 控制器
上锁键
背板连接器 电池
模块标签 RS-232串口
1756-OB32 : 32 通道数字量输出 模块，支持数字 信号
硬件故障
1. 电源模块故障：当前机架无电源供电，所有模块 停止工作，上位机部分数据异常；如主机架电源 故障，上位机所有数据异常；
2. 通讯故障：上位机所有数据异常，ENBT模块故 障或当前交换机损坏；上位机部分数据异常， CNB模块故障或远方交换机损坏；
1756-IT6I : 6通道 模拟量输入模块， 支持热电偶电势 信号。
AB-1756ENBT, 1756-L72,1756-DNB,1734-AENT-通讯模块更换方法
AB-RS LINKS 通讯模块更换模块更换实例：更换分站通讯模块，如下图，更换后拨好地址后在线，情形如下，显示该站有错误，右键点击该站，选择属性，出现对话框，选择最后的classis size，然后点击set classis in module，出现对话框，点击确定就可以了。
（如果是更换有地址的模块，需要将模块改成888，消掉地址，将地址改成888，上电，会有红灯闪，然后断电，拨到999.）模块更换实例：更换主站1756ENBD；更换后在线的情形，两种方式更改地址可以，我用的是RSLINKS，rslinls在线后，右键点击configure module，然后在出现的对话框里设置IP地址后确定。
更换1756L72模块：更换后在线的时候，会显示以下对话框，如果选择在线的话，就会出先固件更新的选项，选择update firmware ，会出现让你选择更新固件的选择，默认的就是只有1756L72，点击update ，然后依次确定。
固件更新完毕后，会出现下载程序对话框，此时模块显示没有工程，点击下载后正常。
更换1756DNB 模块：按照设备使用的件设置拨码开关，三个拨码都在9的位置，然后在线上传的配置，本来是00站的主站模块在这里是63号站，不行，然后报各种报警，63.77.14.11.13，最后将模块地址改为00，然后打开原来上载的设备组态，在线，扫上来的设备组态就相同了，然后点击主站模块，点击里面的下载，就OK 了，。
更改完毕后，发现所有变频的36，38，39，40，数值恢复了出厂值，改为36=5. 38=5。
39=0.3. 40=0.3.ok 。
也就是说上载配置的时候，要将主站里的参数上载，还要上载变频的参数、。
的是点动，所以修改点动块里的加减时间就可以了。
设备运行一段时间后，设备如果出现机械间隙，会报警随动误差的，E19，那么就修改如下图的参数，如果干大胎报警转矩故障的话，就是修改第5个参数，最大值可以跳到百分之250.下图的D指令那里是延时，。
AB PLC 说明Controllogix
DI
处理器
08/14/00
Copyright © 2000 Rockwell International
31
标准数字量输入模板的特性 (续)
–周期性发送 • 根据用户选定的时基周期性地发送
DI
处理器
DI
08/14/00
Ethernet ControlNet
RIO, DH+
ControlNet
DeviceNet
–各种网络接口的混合配置 –按需要增减网络的接口
08/14/00
Copyright © 2000 Rockwell International
23
基板和网络通讯
• 灵活方便的网桥
–各网络间的桥接和路由通过 基板完成而不需要处理器的 参与 –支持排定/非排定的I/O, 对等通讯
5
ControlLogix 系统的基板设计
• ControlLogix 通过提供多主的 Producer/ Consumer (生产者/客户) 方式的, 基于并行通讯网络技术的信 息交换, 打破了传统的控制模式:
– 将ControlNet 的producer/consumer 技术直接应用到系统的基板 (1 to 1, 1 to n)
4
传统控制系统的基板设计
• 传统控制系统设计方法: 采用单一的主/从地址总线
–由单一设备管理总线, 控制通讯 –单点故障: 当控制器或总线“仲裁器”故障时, 整个系统“Down”掉 –集中式的设计方法
CPU及 总线控制器
08/14/00
Copyright © 2000 Rockwell International
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
对第1个机架进行如下操作：
(1) 设置各以太网模块的地址
例如： 对EN2T设置成 192.168.1.1
对EN2TR 设置成 192.168.21.1
(2) 断开冗余相关的同步光纤及以太网连接。
(3) 安装controlflash固件更新软件
(4) 打开controlflash，选择Local，点下一步；
(5) 更新CPU及冗余同步模块（CPU需20.05以上版本）
（6）RSLogix 5000程序中设置CPU为冗余模式，下载程序。
(7)在机架独立的环境下对机架2重复以上操作，各地址完全相同（成功同步后会有一个机
架的EN2T 及EN2TR 的IP地址都自动+1，）
(8)设置子站机架（连接DI,DO,等模块）的IP地址为192.168.21.3；
(9)在RSLinx Classic中配置主机架中EN2TR如下图
(10)不得有任何IO模块设置成Use Unicast Connection over EtherNet/IP。