State Industries GFK-0827 manual Incompatible Configurations

Page 67

4

4.System Configuration verified.

5.System interrogated and initialized.

6.Presence of other CPU detected and RCMs initialized.

7.Complete user program verification.

8.Synchronize with the Redundant CPU.

When powering up the unit configured as the Secondary Unit in a Redundant system and no remote unit (the Primary Unit) is detected, the Secondary Unit will wait up to 15 seconds to see if the remote unit will also power up. If after 15 seconds, the remote unit has not completed its power up sequence, then the Secondary Unit will assume that no remote unit is present. If at this time, the Secondary Unit transitions to RUN mode, it will do so as a stand-alone unit.

If the unit configured as the Primary Unit completes its power-up sequence before the remote unit (the Secondary Unit) the Primary Unit does not wait for the remote unit to complete its power-up sequence. If the Primary Unit is setup to transition to RUN on power-up (that is, was powered-down in RUN mode), it will transition to a stand-alone unit without waiting for the remote unit. When the remote unit completes its power-up sequence, it will attempt to establish communications with the Primary Unit and will synchronize if also transitioning to RUN mode.

In either case, if one CPU fails to notify the other CPU that it is either present or powering up, this CPU will proceed to power-up as a stand-alone CPU and will become the active CPU. The other CPU will resynchronize once the power-up sequence is complete.

Note

In applications where it is desired to have a fully redundant system upon power-up, the Secondary Unit must complete power-up first but no more than 15 seconds before the Primary Unit. The way to be sure that this happens is to apply power to the Secondary Unit first.

Incompatible Configurations

When two units have incompatible configurations stored (for example, both units configured for PRIMARY or differing blocks for data transfer), then only one of the units can go to RUN mode. If the other unit attempts to go to RUN mode or both units attempt to go to RUN mode at the same time, a FATAL incompatible configuration fault will be logged.

If one unit is configured for CPU Redundancy and the other has no configuration, then both units may go to RUN mode at the same time but they will not be synchronized and only the unit that has been configured will drive outputs.

56

Series 90-70 Hot Standby CPU Redundancy User's Guide ± December 1993

GFK-0827

Page 66 Page 68
Image 67
Page 66 Page 68
Contents GE Fanuc Automation GFL±002 Related Publications Content of this ManualWe Welcome Your Comments and Suggestions PrefaceContents Chapter System Components Chapter Configuration Chapter Operation System Operation Fault Detection and Control Actions Synchronized Hot Standby CPU Redundancy System Configuration Contents Hot Standby CPU Redundancy Product Chapter IntroductionGFK-0827 Benefits of the Hot Standby CPU Redundancy Product Features of the Hot Standby CPU Redundancy ProductCable Connections Systems for Hot Standby CPU Redundancy SystemsGenius I/O System Local I/O SystemControl Strategy Basic Hot Standby OperationSynchronized Hot Standby CPU Redundancy System Configuration Redundancy Communications Module Redundancy CPU ModuleEffect on Scan Time Bumpless SwitchingSwitch to Backup Unit Time Synchronized CPUsOn-Line Programming Configurable Backup Data SizeOn-Line Repair Programming Considerations Configuration RequirementsTerm Definition Definition of TermsAcronym Definition Commonly Used AcronymsRedundancy CPU Chapter System ComponentsCPU Architecture Watchdog TimerCapacities for Redundancy CPU, IC697CPU780 Redundancy CPU IC697CPU CPU FeaturesValid Operating Mode Selection CPU Mode SwitchBattery Connectors Memor y Protect KeyswitchCPU Status LEDs Expansion Memory Board Serial Port ConnectorExpansion Memory Boards for CPU Redundancy Communications Module RCM FeaturesBoard OK RCM System Status LedsUnit Selection Pushbutton RCM ConnectorsBus Transmitter Module LED Status IndicatorsBus Receiver Module BTM ConnectorsBRM Connectors Bus Signal TerminationGenius Bus Controller Genius Bus Controller User Features Racks GBC ConnectorsConfiguring a Hot Standby CPU Redundancy System Chapter ConfigurationRedundancy System Requirements Basic Redundancy System SetupLogicmaster 90 Configuration System ConfigurationMonitor or Online mode Screens for Fault Category ConfigurationHandling Folders Configuration with LogicmasterConfiguration of a Redundancy CPU Module GFK-0827 Redundant CPU Requirements Redund Type Normal Sweep ModeBackground Window Constant Sweep Mode Constant Window Sweep ModeFail Wait Ctrl StrgyShared I/O Shared I/O Reference Values Shared I/O Data ParametersReference Type ReferenceSize CalculationforNumberofBytes Transfer Data SizeConfiguring a CPU Expansion Memory Board Configuration of a Redundancy Communications Module Configuration Paired GBC Parameter Configuration of a Genius Bus ControllerSerial Bus Address Configuring a Primary Redundant PLC Select the Redundancy CPU Module Select an Expansion Memory Board Configure the Redundant Communications Module Configure a Genius Bus Controller Configuration Configure Genius I/O Blocks Configure the Bus Transmitter Module Configuring a Secondary Redundant PLC Change Redund Type GFK-0827 Chapter Operation Power-Up Sequence of a Redundant CPUIncompatible Configurations Resynchronization of the Redundant CPU Hot-Standby Redundancy Control Strategy First Data Transfer %I, %AI and Synchronization Synchronous ScanData Transfer from Backup Unit to Active Unit Second Data Transfer %Q, %AQ, %R, and %M Switching Control to Backup UnitRole Switch Svcreq Definition for% S Reference for Redundancy Status References for CPU RedundancyRedundancy CPU Considerations Differences in Operation for CPU RUN Disabled ModeRUN/ENABLED Locrdy Locact Remrdy Remact Configuration of Fault Actions Background Window Time Stop to RUN Mode TransitionWords per Sweep = Ovrpre %S Reference Timed ContactsGenius Bus Controller Switching Fault Categories Fault DetectionChanging Fault Category Actions Fault Zoom Help Text for Redundancy Error Codes PLC Fault TableFaulting RCMs, Losing Links, and Terminating Communications GFK-0827 Maskable Fault Group Descriptions Fault Actions in a CPU Redundancy SystemUserConfigurable Maskable Fault Group ActionsNon-Maskable Fault Action Descriptions Non-Maskable Fault Group DescriptionsMaintaining Parallel Bus Termination On-Line RepairOn-Line Repair Recommendations Redundancy Communications Module and Cables Power SupplyRacks Central Processor UnitBus Transmitter Module Redundancy Communications Link FailuresGenius Bus Controller GeniusBlocks Genius BusRedundancy Alternatives Appendix Redundancy AlternativesRedundancy Option Key See Table PLC RedundancyOptionsSeries 90-70 Redundancy Through Application Logic Index Index Index Index Index
Top Page Image Contents