GFK 2053a
GFK 2053a
Max-ON
Software
User's Manual
GFK-2053A May 2009
GFL-002
Warnings, Cautions, and Notes
as Used in this Publication
Warning
Warning notices are used in this publication to emphasize that hazardous voltages,
currents, temperatures, or other conditions that could cause personal injury exist in this
equipment or may be associated with its use.
In situations where inattention could cause either personal injury or damage to
equipment, a Warning notice is used.
Caution
Caution notices are used where equipment might be damaged if care is not taken.
Note
Note: Notes merely call attention to information that is especially significant to
understanding and operating the equipment.
This document is based on information available at the time of its publication. While efforts
have been made to be accurate, the information contained herein does not purport to cover all
details or variations in hardware or software, nor to provide for every possible contingency in
connection with installation, operation, or maintenance. Features may be described herein
which are not present in all hardware and software systems. GE Fanuc Automation assumes no
obligation of notice to holders of this document with respect to changes subsequently made.
Related Publications
CIMPLICITY® HMI Software GFK-1189 Important Product Information
GFK-1180 HMI User’s Manual
GFK-1181 Device Communications Manual
GFK-1353 Server Redundancy Operations Manual
Field Control™ I/O GFK-0826 Field Control I/O Modules User’s Manual
GFK-0825 Field Control Genius Bus Interface Unit User’s Manual
Genius® I/O GEK-90486 Genius I/O System and Communications User’s Manual
GFK-1034 Series 90-30 Bus Controller User’s Manual
GFK-0695 Series 90-30 Enhanced Genius Communications Module User’s Manual
GFK-0412 Series 90-30 Genius Communications Module User’s Manual
GFK-0450 Genius PowerTRAC Block User’s Manual
GFK-0415 Genius High-Speed Counter User’s Manual
Series 90™-30 Programmable GFK-0356 Series 90-30 Programmable Controller Installation Manual
Control Products GFK-0467 Series 90-30/20/Micro Programmable Controllers Reference Manual
GFK-0898 Series 90-30 I/O Module Specifications Manual
GFK-0255 Series 90-30 Programmable Coprocessor and Support Software User’s
Manual
GFK-0487 Series 90 PCM Development Software (PCOP) User’s Manual
GFK-0293 Series 90-30 High Speed Counter User’s Manual
GFK-0412 Series 90-30 Genius Communications Module User’s Manual
GFK-1034 Series 90-30 Genius Bus Controller User’s Manual
GFK-0582 Series 90 PLC Serial Communications User’s Manual
VersaMax™ I/O GFK-1504 VersaMax Modules, Power Supplies, and Carriers User’s Manual
GFK-1535 VersaMax Genius NIU User’s Manual
VersaPro™ Software GFK-1670 VersaPro Programming Software User’s Guide
GFK-2053A iii
Contents
GFK-2053A v
Contents
Configure Ethernet Interface for Ethernet I/O LANS for PLC B (if used) .............. 6-12
Configure Genius Bus Controllers for PLC B (if used) ........................................... 6-13
Configure I/O Devices on the Primary and Secondary Busses for PLC B .............. 6-14
Copying PLC A Configuration to PLC B Configuration ......................................... 6-14
GFK-2053A Contents ix
Chapter Introduction
1
Welcome
Thank you for choosing Max-ON software and GE Fanuc controllers to implement your critical
control project.
Max-ON software consists of several software components, some of which execute in a pair
of Hot-Standby PLCs, and some of which execute upon your programming workstation.
The controller-based software consists of a set of application blocks that perform the
Redundancy portion of the Hot Standby application. These application blocks are provided as
part of a Proficy™ Machine Edition Project that is the starting point of your redundant
automation application. Using GE Fanuc’s Proficy Logic Developer PLC programming
software, you add your application logic to this project, and then store the overall project to
each of the Hot Standby controllers.
The Max-ON Configuration Utility, which is launched from the Logic Developer PLC Project,
provides a utility to allow the control system designer to customize the functionality of the
redundant system.
A Proficy View Project is also provided to monitor the status of the Redundant System and to
display diagnostic information.
GFK-2053A 1-1
1
2. It is recommended that you close all applications including virus checking, Internet
Explorer, and HMI software that might be running in the background. You may need
to check the task manager to determine if other applications are running. As a further
precaution, it is also recommended that you re-boot the PC to make sure components
that Max-ON Configuration Utility needs to update are not running during the
installation process.
If the computer has other GE Fanuc software products installed, Max-ON Software can be
uninstalled without removing any files needed by those applications. To uninstall Max-ON
Software, do the following:
2. A dialog box appears asking if you are sure you want to uninstall.
▪ All files relating to Max-ON Software will be removed from the hard drive. Any files
used by both Max-ON Configuration Utility and another application will be left on the
system.
▪ All registry entries relating to Max-ON Software will be removed from the systems
registry.
▪ Icons for Max-ON Software will be removed from the Start Menu.
▪ Any data you created (for example, Project that you have created) will be left on the
system.
Note: You may also uninstall Max-ON Software by choosing Add/Remove Programs from
the Control Panel, then selecting Max-ON Tools.
The Max-ON Tools components are installed in the tree structure as shown below:
The Max-ON Configuration Utility is located in the Max-ON Tools directory. It is launched by
double-clicking on the Max-ON configuration file (config.mxn) located in the Proficy Logic
Developer PLC project.
The default Max-ON Hot Standby Redundancy application project, named Max-ON LD Project
vx_yy.zip, is located in the Redundancy LD directory. This project must be brought into your
Proficy Machine Edition development environment using Proficy Machine Edition’s File >
Restore Project… menu.
A Proficy View Diagnostic project is located in the Diagnostics VIEW directory. When it is
active, this diagnostic utility displays key information regarding the operation and state of the
redundant CPU pair. This project must also be brought into your Proficy Machine Edition
development environment using Proficy Machine Edition’s File > Restore Project… menu.
Navigate to the Proficy Components directory, then to the Redundant LD directory. Make
certain that the selection for Files of Type has been set to Proficy Machine Edition (*.zip).
When you click on Open, a new project will be added to the Proficy Navigator window.
Now you may give this new Project a descriptive project name. You may also use this project
to create a Machine Edition project template that can me used as a starting point for future
Max-ON projects.
• PLC_A_HW – This target contains the hardware configuration for PLC A. It must be
edited to reflect the hardware settings and components in your system. Then it must
be downloaded to PLC A (only).
• PLC_B_HW – This target contains the hardware configuration for PLC B. It must be
edited to reflect the hardware settings and components in your system. It will be very
similar to PLC A hardware configuration, except for certain items such IP addresses,
Genius bus controller settings, etc. In a similar fashion, this configuration must be
downloaded to PLC B (only).
• PLC_COMMON_CODE – This target contains the core logic for the Max-ON
redundancy application. You must add your application logic starting in the rung that
follows the call to the core Max-ON logic (hbr_000). The logic from this target will be
downloaded to both PLC A and PLC B. Note that the download consists of the PLC
Logic Only, the Hardware Configuration option must be unchecked.
2. Expand the tree structure so that the Supplemental Files folder named Documentation
Files is visible.
3. Double-click on Documentation Files. This will launch Windows Explorer for this
directory.
4. Click on the Max-ON Project directory to display its contents. The Explorer window will
be similar to what is shown below.
5. Double-click on the Max-ON Configuration file named config.mxn. This launches the
Max-ON Configuration Utility.
6. You may now examine and edit the parameters of the Max-ON redundant system.
Technical Support
Technical Support is available at no charge for 90 days after purchase. A support agreement
can be purchased from your local GE Fanuc distributor if extended support is required.
If problems arise that can’t be solved using the information in your product manual, online
Help system, Proficy GlobalCare knowledge base, or the GE Fanuc Technical Advisor
knowledge base, contact us by telephone, fax, or mail. When contacting us, call from a
telephone near your computer and have your Machine Edition software running. Have the
following information handy to help us assist you as quickly as possible:
• Proficy Machine Edition software installation serial number, the Proficy Machine
Edition software Product name, and version number from the Help >About dialog box.
North America
Support Hotline: 1-800-GEFANUC (1-800-433-2682) Fax: (780) 420-2049
Internet: http://globalcare.gefanuc.com/ Email: support@gefanuc.com
Comments about our manuals and help: doc@gefanuc.com
Mailing Address: GE Fanuc, 2700 Oxford Tower, 10235 - 101 St., Edmonton, AB, Canada, T5J 3G1
Asia
Japan: Telephone 81-3-5405-7555; fax 81-3-5405-7550
China: Telephone 0086-21-32224555 x200; fax 0086-21-62793066
South America
Telephone: +58 (261) 760 2862 Fax: +58 (261) 765 0909
Internet: http://www.gefanuc.com/ (visit our Portuguese web site at http://www.gefanuc.com.br/)
E-Mail: luis.wilhelm@gefanuc.com
Mailing Address: GE Fanuc Automation Latin America, Calle 120 con Av. 17, Los Haticos -GE Turbimeca
Maracaibo, Venezuela
2
Architecture
A Max-ON Series 90-30 Hot Standby Redundancy system consists of two Series 90-30
Controllers, at least one Genius bus used to transfer key system data, and an I/O system.
The I/O devices may share the Genius bus that is used to transfer the system data.
Max-ON for the 90-30 PLCs is available in three different models. The models are
distinguished from each other by the number of I/Os than may be serviced, the number of
Genius I/O LANs supported, the quantity of synchronized data that may be transferred, and
the use of one or more optional Ethernet LAN(s) for application data transfers.
The I/O system may be implemented using a combination of Genius I/O, Field Control I/O,
VersaMax I/O, or Remote I/O drops based upon Series 90-30 I/O.
Product Selections
Max-ON is available in three different models. By offering scaleable solutions, you may chose
the product that matches your I/O requirements as well as data synchronization performance.
(For high performance systems, you should investigate the GE Fanuc PACSystems family of
Hot-Standby processors.)
GFK-2053A 2-1
2
Max-ON Lite
Max-ON Lite is the entry level product offering in the Series 90-30 Critical Control Family.
CPU - A Model 35x, 36x, or 374 CPU - B Model 35x, 36x, or 374
Up to 29
I/O Devices
GENIUS LAN - A
I I I I I I
/ / / / / /
O O O O O O
Max-ON Standard
Max-ON Standard is the mid-level product offering in the Series 90-30 Critical Control Family.
It has been designed to satisfy the majority of the application requirements. This product has
been enhanced over the Lite product by adding support for a dual I/O bus, increased I/O
capacity, larger synchronized data transfers, extra I/O diagnostics, and analog input scaling.
Up to 29
I/O Devices
GENIUS LAN - A
I I I I I I
/ / / / / /
O O O O O O
Max-ON Extended
Max-ON Extended is the high-level product offering in the Series 90-30 Critical Control
Family. It has been designed to satisfy applications that have higher performance
requirements.
This product has been enhanced over the Standard product by adding support for up to 8
simplex or 4 dual I/O busses and additional I/O. Data synchronization is implemented using
one or two Ethernet LANs. Genius LAN(s) is still available if you decide that Ethernet is not
necessary. (Genius LANs also provide additional backup in the event the Ethernet LANs fail.)
CPU - A CPU - B
Model 351, 352, 36x, 374 Model 351, 352, 36x, 374
Up to 29
I/O Devices
GENIUS I/O LAN
I I I I I I
/ / / / / /
O O O O O O
Software Components
Max-ON software consists of several components, some of which execute in the Hot Standby
Controllers, and some of which execute in your programming workstation. A Logic Developer
PLC Project provides the basic template for the Logic of the Redundant System. This project
is modified by the system designer to add the other necessary Logic to perform the user
application, and then the final application is stored in the Controllers using Proficy Logic
Developer PLC.
You may think of the software provided in the Project template for the Controllers as “drivers”
that handle the complex tasks associated with Hot Standby redundancy. These drivers allow
the two Controllers to behave as a single Controller from the perspective of your application.
The Max-ON Configuration Utility allows the system designer to customize the parameters of
the Max-ON drivers and to specify the hardware that is contained within the system. The
Max-ON Configuration Utility software operates in Windows XP Professional, Windows NT4.0,
and Windows 2000 Professional.
The Max-ON Configuration Utility software allows you to define the way your system is
constructed and how you want the system to operate. It provides additional information that is
not included in the Hardware Configuration files produced by Logic Developer PLC.
The Max-ON software includes a Proficy View Diagnostic Project that allows you to observe
the way your system is operating and helps you to diagnose problems. This Project displays
the operational status of the redundant system in real time.
The Max-ON software also includes a set of projects to configure Series 90-30 Remote
Genius Drops.
The Max-ON software components are organized as follows:
Failover Time
There are two factors that contribute to failover time.
Token Rotation Time: This time interval varies somewhat from one Genius bus to
another. It is defined as the update period for the I/O LAN. This period is a function of
the number of devices on the LAN, the quantity of input/output data associated with each
device, the LAN’s baudrate, and the quantity of global data being transferred. Generally
this time period ranges from a few milliseconds to perhaps 100 milliseconds.
Mastership Time: This is the time interval for the Backup PLC to recognize that the
Master PLC has failed. It takes one or two PLC scans to determine that the Master has
failed. Then it takes an additional scan to activate the output data stream in the Backup
PLC.
The actual failover time is the longer of either...
3 Token Rotation Times, or
1 Mastership Time.
Lacking output data from the current Master’s GBC, each output circuit on each device on the
I/O LANs will hold its last state for up to 2.5 seconds before it assumes the Default State
unless there is output data from the Backup GBC. (This assumes that each device has been
configured for either BSM present or for long timeout.) Then the output device will begin
using output data from the other GBC.
Quantities
For each Synchronized Data type, the system will sum the lengths in each configured group
to arrive at a total amount. The total for each data type must not exceed any of the
maximums listed in the table below:
Note: If one attempts to configure a transfer having a larger value than is allowed,
then the CPU with the invalid configuration will post a fault message and then shutdown
immediately. It cannot be restarted until a valid configuration having a proper quantity has
been stored.
With a Max-ON system, you may select I/O devices based upon functionality, cost, physical
design, items carried in spare parts inventory, or personnel expertise.
Product Authorization
A Max-ON system will operate in demonstration mode for 22 days. In this mode, all of the
system’s capabilities are fully operational. At the end of the period, PLC A will either stop
immediately (if it is the backup) or begin an orderly transfer of Mastership to PLC B. If the
transfer is successful, then PLC A will shutdown automatically. At this point, the system will
be operating in a non-redundant manner.
A Max-ON system that is installed in a production environment MUST be authorized in order
to allow PLC A to run indefinitely.
For additional details on product authorization, refer to Chapter 8.
3
Max-ON Project
Max-ON encapsulates your entire application within a single Machine Edition Project. Using a
generic Max-ON Project, you can create a new Max-ON Redundancy project. The generic
project contains all of the base Max-ON redundancy application components needed to perform
the redundant application. You add the hardware configuration information for each PLC in your
application, add your application logic, and define the parameters of the Redundant System
using the Max-ON Configuration Utility that was launched from the Logic Developer PLC
Project.
Max-ON Drivers
GFK-2053A 3-1
3
Project Workflow
Step 1 - Gather Information
Gather the information about your system:
I/O Bus topologies and addresses
Synchronization LAN locations
Module types and locations
I/O Devices including bus assignment, bus addresses, circuit references, number of
circuits and I/O family type.
Step 2 - Create a New Max-ON Project
In Proficy Logic Developer PLC:
Create a new project based on the Generic Max-ON Project. The redundant ladder project is
added to the Machine Edition project Navigator by using the File > Restore Project… menu
item. Select the Project Navigator window making certain that there is no project open at this
time.
Navigate to the Proficy Components directory, then to the Redundancy LD directory. Make
certain that the selection for Files of Type has been set to Proficy Machine Edition (*.zip).
When you click on Open, a new project will be added to the Proficy Navigator window.
I/O Bus
Make certain that the Genius LAN(s) have been installed correctly... LAN polarity and shield
IN/OUT are connected consistently and correctly. Also make certain that terminating resistors
are installed at each end of the LAN(s).
Genius and Field Control – Using a Handheld Monitor, verify that output devices may be turned
ON or OFF from the LAN.
Use the Handheld Monitor check the LAN for any Bus Error activity.
I/O Devices
When Interfacing to CPU A:
With the I/O operating, place CPU A in RUN mode and CPU B in STOP mode.
Verify that the system input devices return real-time values properly.
Verify that system output devices may be controlled from the Output Reference Tables.
Note: This might require that you place a temporary JUMP in your application.
The JUMP should be placed immediately after the CALL to HBR_000. The
companion label should be placed at the end of _MAIN.
Make certain that the I/O did not dropout during the transfer.
Place CPU B into RUN mode.
Make certain that it becomes a Backup properly.
Make certain that Synchronized Data is transferred properly to CPU B.
4
The Max-ON Configuration Utility is used to create or edit the operating parameters used by
the Max-ON redundancy drivers. These parameters specify such things as, bus topologies,
I/O addresses, and definitions for the ranges of synchronized data transfers.
Max-ON Projects
A Max-ON Project is a collection of items needed to define the elements of a redundant
system. If you inspected a Max-ON Project using Logic Developer PLC, you would see that it
consists of a Machine Edition Project with 3 Targets:
• PLC_A_HW – This target contains the hardware configuration for PLC A. It must be
edited to reflect the hardware settings and components of PLC A in your system.
Then it must be downloaded to PLC A (only).
• PLC_B_HW – This target contains the hardware configuration for PLC B. It must be
edited to reflect the hardware settings and components of PLC B in your system. It
will be very similar to PLC A hardware configuration, except for certain items such IP
addresses, and Genius bus controller settings. In a similar fashion, this configuration
must be downloaded to PLC B (only).
• PLC_COMMON_CODE – This contains the core redundancy logic for the Max-ON
redundancy application. You must add your application logic starting in the rung that
follows the call to the core Max-ON logic (hbr_000). The logic from this target will be
downloaded to both PLC A and PLC B. Note that the download consists of the PLC
Logic Only, the Hardware Configuration option must be unchecked.
GFK-2053A 4-1
4
Max-ON Drivers
When creating a Max-ON Project, the best approach is to start with the generic project that is
supplied with the Max-ON software. This assures that all of the basic components of the Max-
ON redundant application are included in the project.
1. Create a new project based on the generic Max-ON Project. A new Max-ON Project is
added to the Machine Edition project Navigator by using the File > Restore Project…
menu item. Select the Project Navigator window, making certain that there is no
project open at this time.
3. Navigate to the Proficy Components directory where the Max-ON Tools software has
been installed, then to the Redundant LD directory. Make certain that the selection
for Files of Type in the Restore dialog has been set to Proficy Machine Edition (*.zip).
4. When you click on Open, a new project will be added to the Proficy Navigator window.
2. Expand the tree structure so that the Supplemental Files folder named Documentation
Files is visible.
3. Double-click on Documentation Files. This will launch Windows Explorer for this
directory.
4. Click on the Max-ON Project directory to display contents. The Explorer window will be
similar to what is shown below.
5. Double-click on the Max-ON Configuration file named config.mxn. This launches the
Max-ON Configuration Utility. You may now examine and edit the parameters of the
Max-ON redundant system.
The Cfg_Dat.exe file in the Max-ON Project directory is the C Block that is modified by the
Max-ON Configuration Utility. After the utility has updated this file, you must update the
Cfg_Dat C Block that is located in the PLC_COMMON_CODE target in the Max-ON
Project.
Once a rack has been selected, you may access more options by selecting Configure, then
Selected Rack on the main menu bar. The following drop down list of menu items will appear:
To Add a Bus –
1. Either select an empty slot location or double-click on an empty slot location. The
Select Module Type dialog box will appear.
After you have entered the bus controller, you must enter the starting address for the device
status words.
2. Either right click the slot to display the popup menu, or use the menu Configure, then
IO Properties. The I/O Properties dialog box will appear.
3. Enter a status address. (A suggested practice is to address devices such as Genius
bus controllers, Ethernet modules, etc., at high addresses. This leaves the low
addresses to Input devices connected to your field sensors.)
4. Click Ok to complete the session.
6. Select the I/O Type for the device, using the drop down list selections. If your I/O
device does not match with any of the selections, then select Generic. Also, you
should select Generic if the device is a Remote 90-30 drop.
7. Without changing the row, click on the Edit button
8. The Configure dialog box will appear.
Starting Address The first reference address used within the discrete input group.
Length The number of discrete references that are to be included on this
device.
Max-ON redundancy drivers detect when inputs are reporting into the secondary reference
area and then map the inputs automatically from the secondary area into the primary address
locations. This permits the user-application to be written with references to the primary
addresses only.
Starting Address The first reference address used in the secondary (alternate)
reference table. You cannot enter a value here. However, you may
select the desired reference table for the alternate location.
• If the Primary Address Length is a multiple of 16, then the inputs
will be mapped into the 90-30 register table.
• If the Length is an odd multiple of 8, then the inputs may be
mapped into either %I or %G references.
Length The number of discrete references that are to be included on this
device. This is a read-only value that is generated from the number
that was entered into the Primary Address box.
Max-ON redundancy drivers detect when the inputs are reporting into the secondary
reference area and then map the inputs automatically from the secondary area into the
primary address locations. This permits the user-application to be written with references to
the primary addresses only.
Starting Address The first reference address used in the secondary (alternate)
reference table. You cannot enter a value here. The reference will
always be equal to the primary reference plus an offset of 1024.
Length The number of discrete references that are to be included on this
device. This is a read-only value that is generated from the number
that was entered into the Primary Address box.
Circuit Configurations –
Analog input scaling is used to convert raw values received from the input device into scaled
values. Because many bus devices are able to perform their own scaling. This option may
be enabled for devices that do not provide scaling inherently. Please be aware that enabling
this option adds to overall scan time and consumes additional configuration memory.
If the raw value produced by the analog circuit is less than the Raw Units Low value OR if the
value is greater than the Raw Units High value, then an alarm will be generated for the analog
circuit.
Notes:
• Many of the GE Fanuc analog input devices are capable of performing scaling
independently. It is better to use the built-in capabilities of the devices. This will reduce the
PLC scan time by eliminating the extra processing associated with the scaling function. Also,
it reduces the amount of configuration memory consumed.
• If the device is configured to be on a dual bus, then the backup analog input
addresses will be at the primary address plus an offset of 1024. For example, %AI00001 will
have an associated backup address at %AI01025.
Inputs from the secondary bus controller are placed into an alternate area and then the Max-
ON PLC driver remaps the alternate states into the table area used by the primary.
Remapping occurs whenever the device is detected as being present on the secondary bus,
but not present on the primary. (In most instances the data will be available on one of the
busses, but not both. The exception is for Remote 90-30 drops, in which case, there are bus
controllers on each bus.)
Analog Inputs –
For analog inputs, the alternate addressing is fixed at the primary’s address reference plus
1024. Thus an analog input circuit addressed at %AI00001 will have an alternate, or
secondary address, at %AI01025.
Discrete Inputs –
For discrete inputs, the addressing is more flexible.
• If the primary address is on a word multiple (i.e, 1, 17, 33, etc.) AND the length
is a word multiple (i.e., 16, 32, 48, etc.), then the secondary addresss will be mapped
into %R space.
• If the primary address does not meet the criteria above, then the user may
select an alternate address at either a %G reference or a %I reference.
The network interface may be implemented using the built-in port on a CPU364 or CPU374.
Or the interface may be implemented using a CMM321. If you are using a dual LAN topology,
then you may use two CMM321 modules in each PLC for the Sync LANs. Or, you may use
one CMM321 and a built-in CPU port.
When the Ethernet module (or CPU) has been entered, you must enter the corresponding
device status address. Generally, it is a good practice to place these bits in the upper area of
the %I references (configurable range 1..2048).
When dual Ethernet LANs are employed, you must specify which device is to be the primary
device and which is to be the secondary device. Each module must be configured separately.
If no Ethernet LAN is enabled, then all Sync Data transfers will occur by way of the Genius
Bus (Busses) that have been configured to act as the System Bus (Busses.)
Synchronized Data
%M00001 ....%M02048
%Q00001 ....%Q02048
%AQ0001....%AQ0256
%R00001 ....%R08000
Groups
Synchronized data may be transferred in up to 6 groups for each of the data types listed
above. This allows transfer of non-contiguous data areas. The general format uses a
Starting Reference, paired with a Length.
Discrete Outputs
Analog Outputs
Internal Coils
Registers
Maximum Quantities
For each Synchronized Data type, the system will sum the lengths in each configured group
to arrive at a total amount for that data type. The total must not exceed the size listed in the
table below:
Note: If one attempts to configure a transfer having a larger value than is allowed, then the
CPU with the invalid configuration will post a fault message and then shutdown immediately.
It will not restart until a valid configuration has been stored.
Project Information
Configuration Report
The configuration summary provides information about your project. You determine the
content of the report by the options which are checked. Each time an option box is changed,
the report will update automatically.
End-User Information
First Name:* John
Last Name:* Smith
Title: Project Manager
Company:* Acme Manufacturing
Address:* 1122 Oak Blvd.
City:* Charlottesville
State/Province:* VA
Country:* USA
Zip/Postal Code:* 22901
Phone Number:* 804-555-1234
Fax Number:* 804-555-4321
E-mail Address: john@acme-mfr.com
Product Serial Number:* 1234-555-6789
Site Contact: John Smith
CPU-A Key Code: 4299
Hardware Configuration
[Rack 0, Main]
[Slot 1] Catalog: IC693CPU364
Description: CPU; 240Kb; 1-RS485; 1-ENET
Status Reference: %I01825
PLC A IP Address: 0.0.0.0
PLC B IP Address: 0.0.0.0
[Slot 2] Catalog: IC693CMM321
Description: Ethernet Module
Status Reference: %I01905
PLC A IP Address: 0.0.0.0
PLC B IP Address: 0.0.0.0
[Slot 3] Catalog: IC693BEM331
Description: 90-30 Genius® Bus Controller
Status Reference: %I02017
[Slot 4] Catalog: IC693BEM331
Description: 90-30 Genius® Bus Controller
Status Reference: %I01985
Primary Controller
Status Reference: %I02017
Model: IC693BEM331, 90-30 Genius® Bus Controller
Series Six Reference: 0
Rack: 0
Slot: 3
Secondary Controller
Status Reference: %I01985
Model: IC693BEM331, 90-30 Genius® Bus Controller
Series Six Reference: 0
Rack: 0
Slot: 4
SBA Input1 Length Input2 Length Output1 Length Output2 Length
1 %R16001 4 %AI1025 16 %Q0001 32 %AQ0001 16
Synchronized Data
Discrete Outputs
%Q00001, length 64
Analog Outputs
%AQ00001, length 16
Memory
%M00001, length 64
%M00257, length 64
Registers
%R00001, length 300
%R01001, length 100
%R02001, length 100
%R03001, length 100
%R04001, length 100
%R05001, length 100
Project Validity
The authorization codes are not valid for the current project type (IC641HBR302)
Authorization Codes
%R9011 4299 (CPU-A Key from most recent connection)
%R9012 0000
%R9013 0000
%R9014 0000
%R9015 0000
%R9016 0000
%R9017 0000
%R9018 0000
%R9019 0000
%R9020 0000
%R9021 0000
System Options
Product Version A dropdown list provides a selection of Max-ON products that may be
used as the base for this project. Once the project has been
selected, it may not be changed.
Fast Offline Detection Enabling this option directs the PLCs to detect an offline condition
within one PLC scan. If the option is not enabled, then it will require
two consecutive scans to produce an offline condition.
Dual Sync LANs Enabling this option instructs the system to expect two channels for
Synchronized Variable and System data exchange. The channels
are always implemented via Genius LANs.
Program Change Audit Trail Checking this box instructs the system to monitor the program for
changes to logic. If there is a change, the value in the change
counter (%R9003/9004; type double) will be incremented by one, and
a date/time (%R9005.9007, packed BCD) will be posted for the
moment at which the change occurred.
Default Multiplexer Period This value is the default time period used to advance the
Synchronized Data multiplexer. It is useful when there are Remote
90-30 Drops present in the system.
Adding an alarm -
1. Make certain that your current project file has been opened.
2. From the main menu, select Configuration, then User-Defined Alarms.
3. The User-Defined Alarms dialog box will be displayed.
4. Place the cursor in the first available alarm field. Enter the Alarm Number. (The
valid alarm numbers must be within the range 3840 to 4095, decimal.) If you attempt
to enter a number outside this range you will receive an error message.
5. Move the cursor to the descriptor area and enter an alarm legend.
6. Repeat steps 3 and 4 for any additional user-defined alarms
7. Close the Alarm Configuration Window.
8. Save your project.
Deleting an alarm -
1. Make certain that your current project file has been opened.
2. From the main menu, select Configuration, then User-Defined Alarms.
3. Place the cursor in the row that is to be deleted.
4. Click on the Delete pushbutton.
5. Repeat steps 3 and 4 for any additional user-defined alarms
6. Close the Alarm Configuration Window.
7. Save your project.
Note: In order for User-Defined Alarms to be active, ladder logic must be added to the
application. The logic passes the user specified alarm number to the Alarm handler. (See
Max-ON Advanced Programming topic: User-Defined Alarms.)
5
This chapter provides additional information on programming considerations and system
resources for the Max-ON product. In many cases, Max-ON System Variables have been
predefined to use in application logic in order to interact with the Max-ON redundancy driver.
Reserved References
Max-ON redundancy drivers make use of a small number of variable references. Some of
these references are used for the internal operation of the drivers to hold system state
information. Many are available to your application logic to provide both information on the
system and to control the operation of the redundancy drivers.
I/O References
%I00001 to 2048 Available to all applications
%Q00001 to 2048 Available to all applications
%AI00001 to configured limit Available to all applications
%AQ00001 to configured limit Available to all applications
Boolean References
%G00001 to 1024 Available to all applications
%G01025 to 1280 Reserved by Max-ON
%M00001 to 0928 Available to all applications
%M00929 to 1024 Reserved by Max-ON
%M01025 to 4096 Available to all applications
%S (all) Available to all applications
%T00001 to 256 Available to all applications
Word References
%R00001 to 8000 Available to all applications
%R08001 to 16384 Reserved by Max-ON
%R16385 to configured limit Available to all applications
GFK-2053A 5-1
5
%M01017 ID Flag for CPU A (ID_A) – This flag is ON in the CPU identified as PLC A.
(Setting the CPU Identity)
%M01018 ID Flag for CPU B (ID_ B) – This flag is ON in the CPU identified as PLC B.
(Setting the CPU Identity)
%M01019 CPU is in RUN Mode (CPU_RUN) – This flag is ON if the CPU is in RUN
Mode. It is OFF if the CPU is in STOP/Disabled or STOP/Enabled.
%M01020 Master Flag (MASTER) – This flag is ON in whichever CPU is the current
Master.
%M01021 All Data has been Synchronized (SYNC_OK) – This flag is always ON in the
CPU identified as the current Master. It is ON in the Backup CPU at the
moment when all Synchronized Data items have been updated.
Indicating Mastership
Using the System Status Flag %M01020 (Master) and the System Status Flags %M01017
and %M01018 (the CPU Identity flags), you may determine which PLC is the current Master.
By combining these flags it is possible to link discrete outputs to indicator lamps, link to
internal coils to provide status points to an HMI, or even link discrete outputs to data switches
to route communications lines from a peripheral to the CPU serial ports.
In the example below, the Flags are used to control discrete outputs that are attached to
indicator lamps.
%M01017 %M01020
This is CPU A This CPU is CPU A is the
Master Master
%M01018 %M01020
This is CPU B This CPU is CPU B is the
Master Master
%M00961 Authorization Alarm (AUTH_ALM) – This alarm bit indicates that the
corresponding PLC is operating in DEMO mode. In a system that has been
properly authorized, this flag will be OFF.
%M00962 Remote CPU Offline (REM_OFF)– The companion PLC is offline. This may
be due to the CPU being in STOP, Fault, or Power-OFF. Also, it may be due
to a cable problem or Ethernet Interface failure.
%M00963 Program Changed (PROG_CHG) – The program in the Local CPU has
changed.
%M00969 Power Up (PWR_UP) – The Local CPU has undergone a power-up event.
%M00970 Program Restart (PRG_RST) – The Local CPU has been switched from
STOP mode to RUN mode.
%M00971 System Ethernet Bus Primary Offline (E1_OFFL) – The primary Ethernet
LAN is offline. This may be due to a cable problem, a transceiver problem, a
hub/switch problem, an ETM001 module failure or a LAN configuration error.
%M00973 - Reserved
%M00992
%M00993 Authorization Alarm – This alarm bit indicates that the corresponding PLC is
operating in DEMO mode.
%M00994 Authorization Fault – This fault bit indicates that the system was operating in
DEMO mode for over 22 days and has subsequently shutdown. The PLC Fault
Table will indicate shutdown due a Service Request.
%M00995 Remote CPU Offline – The companion CPU is offline. This may be due to the
CPU being in STOP, Fault, or Power-OFF. Also, it may be due to a cable
problem or Ethernet Interface failure.
%M00996 Program Changed – The program in the Local CPU has changed.
%M00997 HW Config Changed – The hardware configuration in the Local CPU has
changed.
%M00998 Programs Miscompare – The program in CPU A is not the same as the
program in CPU B.
%M01002 Program Restart – The Local CPU has been switched from STOP mode to
RUN mode.
%M01003 Max-ON Fault Present – There is at least one fault entry in the Local CPU’s
Max-ON Alarm Table.
%M01004 Max-ON Fault Table Full – The Local CPU’s Max-ON Alarm Table is full.
%M01005 Config Fault – The Max-ON configuration has exceeded one or more limits for
the allowable size of Synchronized Data transfers.
%M01006 - Reserved
%M01008
The flags below are latched. They may be cleared by resetting the alarms (see Command
Flags). If the alarm condition persists, then the flag(s) will be set again.
Reference Description
%M00929 Remote is Offline
%M00930 Remote Forces (Overrides) Present
%M00931 Remote PLC Low Battery
%M00932 Remote Config Mismatch
%M00933 Remote Loss of I/O Module
%M00934 Remote Loss of Option Module
%M00935 Remote Option Module Hard Fault
%M00936 Remote Option Module Soft Fault
%M00929 Remote is Offline – CPU is offline, or there has been a bus failure on a
system that uses a single Ethernet Sync bus, or on a system using dual Sync
busses, both have failed.
%M00930 Remote Forces (Overrides) Present – There is at least one force (override)
present in the remote, same as #OVR_PRE (%S0011) in the remote.
%M00931 Remote PLC Low Battery – Same as #PLC_BAT (%S0014) in the remote.
%M00933 Remote Loss of I/O Module – Same as #LOS_IOM (%SA0014) in the remote.
%M00935 Remote Option Module Hard Fault – Same as #HRD_SIO (%SA0027) in the
remote.
%M00936 Remote Option Module Soft Fault – Same as #SFT_SIO (%SA0031) in the
remote.
%M00938 Remote I/O Fault Present – Same as #IO_PRES (%S0013) in the remote.
%M00939 Remote HBR Fault Present – there is at least one fault in the Max-ON fault
table.
%M00940 Remote HBR Fault Table Full – The Max-ON fault table is full.
%M00941 Remote Program Changed – The user application in the remote has
changed.
%M00942 Remote HW Config Changed – The hardware configuration in the remote has
changed.
%M00944 Remote Program Restart – The remote has undergone a Program Stop-to-
Run event.
%M00945 Remote Authorization Alarm –The Remote CPU is operating in DEMO mode.
%M00946 - Reserved
%M00960
%M01012 Auto Sweep Mode –When this is set to ON, the Backup CPU will be set to
Constant Sweep mode automatically, and the Master will be set to Normal
Sweep mode automatically. (See PLC Sweep Mode.)
%M01014 Clear Remote Alarms (self-resetting) - When issued to the Master, CLEARS
the alarms in the Backup CPU only. If it is set ON, the Max-ON driver will reset
it to OFF automatically.
%M01015 Clear Local Alarms (self-resetting) - Clears the alarms in the CPU to which it
is directed. Is reset automatically.
%M01016 Clear All Alarms (self-resetting) - When issued to the Master, CLEARS the
alarms in the Master and Backup CPUs. Is reset automatically.
Mastership Modes
You may specify the Mastership mode of operation for the Hot Standby CPUs. This may be
accomplished by setting the states of the System Command Flags, SEL_A (%M01009) and
SEL_B (%M01010). Both CPUs must have the states set identically in order to function
properly. The truth table shown below illustrates the operation of the Mastership Command
Flags.
SEL_A SEL_B Description
%M01009 %M01010
0 0 Float
1 0 A Preferred
0 1 B Preferred
1 1 Float
▪ B Preferred - In this mode, SEL_A (%M01009) is OFF and SEL_B (%M01010) is ON.
The description is similar to A Preferred, except that the roles are transposed.
▪ Float - Either CPU may be the Master. Mastership will not change unless the current
Master fails or is placed into STOP or RUN-Outputs Disabled mode. When the
failed/stopped CPU is restored to service, the current Mastership does not change.
While the system is in Float Mode, Mastership may be changed by setting the System
Command Flag, SW_MSTR (%M01011). Float Mode is required if you intend to
switch Mastership using an HMI.
In the example that follows, the switch contacts are wired to discrete inputs SEL_A (%I01009)
and SEL_B (%I01010). When the switch is in the A position, only SEL_A (%I01009) is ON.
When the switch is in the B position, only SEL_B (%I01010) is ON. When the switch is in the
center (Float) position, SEL_A (%I01009) and SEL_B (%I01010) are both OFF.
You may set a permanent, Preferred Master. In this mode, if the corresponding CPU fails (or
is placed in STOP), then the companion CPU will assume Mastership. As soon as the
Preferred Master resumes operating normally, and its Synchronized Data has been updated,
then the Mastership will transfer.
First, you must set the system for Floating Mastership. (Refer to Setting the System for
Floating Master.)
Then include the following logic to implement the Toggle Master function.
If a command to set SW_MSTR (%M01011) has been issued, then the system will operate in
the following manner.
▪ If both CPUs receive the command, and there is no Preferred Master, then the
Mastership will change as soon as data synchronization is complete.
▪ If only the Master receives the command, and the Backup is available, and there is no
Preferred Master, and data synchronization is complete, then the transfer will occur.
▪ If one or both of the CPUs receive the command, and the Master is the Preferred
Master, then the request is discarded.
▪ If only the backup receives the command, then no transfer will occur.
▪ After the relevant conditions above have been evaluated, SW_MSTR (%M01011) will
be reset automatically.
Assuming that there is no preferred Master set in either CPU, then the transfer will occur as
soon as data synchronization is complete. In most cases, this will happen immediately.
You must set the system for Floating Mastership. (Refer to Setting the System for Floating
Master.) No other logic is required.
Advanced Topics
PID Function Blocks
The PID function block uses a data structure consisting of 40 registers. These registers
contain not only configuration parameters, but also intermediate and final terms used in the
internal calculations. Some of the internal calculations are based upon values from the PLC’s
system clock. Because the internal clocks in the two CPUs are not synchronized precisely to
each other, it is necessary to include a small amount of logic to compensate for the difference.
Also, it will be necessary to include the PID registers in one or more of the %R Synchronized
Data Groups. This ensures that the PID in the Backup CPU tracks the Master.
The ladder logic is straightforward. Two rungs are used for each PID loop. For this example
the following PLC references are used:
%M00501 PID01_Man PID01: Set in Manual
%M00502 PID01_UP PID01: Set in Manual
%M00503 PID01_DN PID01: Set in Manual
%R00501 PID01_SP PID01: Set in Manual
%R00502 PID01_PV PID01: Set in Manual
%R00503 PID01_CV PID01: Set in Manual
%R01001..1040 PID01 PID01: Parm Block
The first Rung allows the PID to be placed in Manual by an HMI or a local control station.
This is accomplished by setting P01_MAN. (Note that %M00501 is active only in the Master
CPU. If P01_MAN is SET in the Backup, then it will be reset before the rung containing the
PID is solved.)
The following table describes how the PID behaves as a function of Mastership and Manual
states.
Master = TRUE Master = FALSE
In this example, the PID parameters begin at PID_P01 (%R01001). For PID loop 01, there
must be a synchronized data group configured that assures that registers %R01001 through
%R01040 are transferred. You must include the registers associated with other PID functions
as well. Also, it is customary to include the Setpoint word in the Synchronized Data set.
User-Defined Alarms
The user may post self-defined faults from within the application by performing the following
steps.
Note: User defined Alarms are not available in this version the Max-ON VIEW Diagnostic
Tool.
2. In most cases, move a value 0 into FLT_CKT (%R9761). However, you may define
your own identifier that may be MOVed into this register.
3. Call the subroutine named HBR_005. This must be done for only once, otherwise
each subsequent call will post an additional alarm into the alarm table. In the sample
logic shown below, ua_0002 (%M02050) has been used as an alarm latch. The user-
defined alarm will be posted only if the coil is not already set. Note that a setcoil is
used so that the alarm state will be retained through a loss of power. Also, a rung has
been provided that resets the coil if the alarm clear flags are invoked.
Process a User A larm
PSH_1402 ua_0002 MOVE MOVE CA LL ua_0002
I NT I NT hbr_005
RST_A LL ua_0002
%M01016 %M02050
Reset A ll User_0002:P1
A larms (os) 402 High
Pressure
A larm
RST_LOC
%M01015
Reset Local
A larms (os)
Bytes 6..7 Bytes 6 and 7 contain the decimal value of an I/O circuit reference. The value in
this pair of bytes must be interpreted in the context of the Alarm Class that has
generated the message. The Alarm Class is contained in Byte 9. The value will
be zero for CPU or system-level hot standby faults.
Byte 8 This byte contains the Alarm Subclass code. The subclass contains the rack
number in the upper nibble and the slot number in the lower nibble. This number
implies different fault descriptions depending upon the value of the Alarm Class
contained in byte 9.
Byte 9 This byte contains the Alarm Class code. The valid range is 0000..4095.
Alarm Class Alarm Circuit Reference Alarm Class Description
Subclass Range (Integer)
(Offset 9)
(Offset 8) (Offset 6/7)
00 00..FF Always 0 System level faults
01 00..FF 0001..2048 Discrete input circuit
02 00..FF 0001..2048 Discrete output circuit
03 00..FF 0001..1024 Analog input circuit
04 00..FF 0001..0256 Analog output circuit
05 00..FF 00..31 I/O LAN device
06..0E 00..FF --- Not defined
0F 00..FF -32768..32767 User-defined
6
A Max-ON Project contains three Targets that are used to distinguish between hardware
configurations for PLC A and PLC B, and the user application that is common to both of the
CPUs. The figure shown below illustrates the various components contained in the Generic
Project named MaxON Extd IC641HBR302v2_05
GFK-2053A 6-1
6
When a Max-ON project is created, a hardware configuration Target is provided for PLC A
and one is provided for PLC B. In most aspects, these targets are very similar to each other.
The significant differences between the two hardware configurations are:
• Identity settings for the CPUs (via logic checksum words)
• Serial communication port settings and SNP ID
• Ethernet interface IP addresses
• Genius bus controllers configuration
Many of the configuration items are completed during the process of developing the Project.
The following sections provide details on the configuration of these elements.
Configuring PLC A
Open the Hardware Configuration for PLC_A_HW
In the Max-ON Project, select and expand the Hardware Configuration node of the
PLC_A_HW target.
Verify that the Checksum Words parameter value is set to 11. If it is not 11, change the
parameter to this value.
Select the Memory tab of the CPU configuration and verify that these values have been
configured. Please note the memory limits may be larger than these values for use in your
application.
You may display the summary by using the Project menu and then click on Configuration
Summary.
Limit the information displayed on the summary page by clearing all of the check boxes
except for Hardware Configuration.
Add the Ethernet Interface module(s) to the appropriate slot(s) in the Hardware Configuration
for PLC A and configure its parameters to match the Max-ON Configuration Summary.
Add the Genius bus controllers to the appropriate slot(s) in the Hardware Configuration for
PLC A and configure its parameters to match the Max-ON Configuration Summary.
Inputs Default
Input Default should be set to Off.
Output at Start
Outputs at Start must be set to Disabled.
Scroll down to the rows for Serial Bus Addresses 30 and 31 and set the reference types,
starting addresses and lengths according to the table shown below.
SBA Device Input 1 Length Input 2 Length Output 1 Length Output 2 Length
# Type Address Address Address Address
30 Generic %R09872 62 %AI0001 0 %Q00001 0 %AQ0001 0
31 Controller %R09936 62 %AQ0001 0
Scroll down to the rows for Serial Bus Addresses 30 and 31 and set the reference types,
starting addresses and lengths according to the table shown below.
SBA Device Input 1 Length Input 2 Length Output 1 Length Output 2 Length
# Type Address Address Address Address
30 Generic %R09808 62 %AI0001 0 %Q00001 0 %AQ0001 0
31 Controller %R09936 62 %AQ0001 0
Add Genius devices to the GBC’s configuration and configure the Genius device parameters
to match. A sample is shown below.
Repeat this process for each Genius device in the Max-ON configuration.
Repeat the above process until there are no more bus controllers to be configured.
Note: VersaMax I/O is no longer configured automatically by the PLC Max-ON drivers.
Please make certain that you use the Remote I/O Manager in Machine Edition to set and
download the configurations.
If there are no Secondary busses in the system then store the configuration into CPU A.
Otherwise, configure the secondary bus as explained next.
You can use the Copy Genius Bus function in the hardware configuration to facilitate the
speedy duplication of Genius bus configurations.
Select the location for the duplicate Genius Bus and an exact copy will be made to the
destination slot location.
Configuring PLC B
Open the Hardware Configuration for PLC_B_HW
In the Max-ON Project, select and expand the Hardware Configuration node of the
PLC_B_HW target.
Verify that the Checksum Words parameter value is set to 12. If it is not 12, change the
parameter to this value.
Configure Ethernet Interface for Ethernet I/O LANS for PLC B (if used)
Configure the Ethernet Interfaces used in conjunction with any Ethernet NIUs that are part of
your system.
Input Default
Inputs should be set to Force OFF.
Output at Start
Outputs must be set to Disabled at Start.
To export the Hardware Configuration from the PLC_A_HW target and import it into the
PLC_B_HW target:
Specify a file name for the configuration, or use the default name PLC_A_HW.hwc.
Now modify the Hardware Configuration for PLC_B_HW Target to match the parameters of
PLC B in your system.
7
Configuring the Ethernet I/O Devices
Before you may use your system, you must configure the Ethernet I/O devices that are to be
installed on the Ethernet I/O bus. For Max-ON RX3i the Ethernet devices may consist of
PACSystems RX3i ENIUs and/or Series 90-30 ENIUs.
For a complete description of how to configure and use the PACSystems RX3i ENIUs, please
see GFK-2434, titled PACSystems RX3i Ethernet Network Interface Unit. A summary of the
process to configure this ENIU is as follows:
1. Determine the IP Addresses for the Primary (PLC A) and Secondary (PLC B)
Controllers and the Ethernet NIU.
2. Add the PACSystems ENIU target(s) to your Machine Edition Project by selecting the
Add Target > GE Fanuc Remote I/O > PACSystems RX3i Ethernet menu.
3. Set the IP Address and Subnet Mask on the Ethernet Transmitter module(s) ETM001
in the Ethernet NIU target, Set Gateway IP Address if required.
4. Set the Ethernet Global Data Local Producer ID in the Ethernet NIU.
5. Add the input and output modules to the Ethernet NIU configuration. If you add or
change modules later in the project, EGD Exchanges in the ENIU and controller may
need to be updated.
6. Complete the Ethernet Global Data Exchanges for the ENIU.
7. If the ENIU has any Local Logic, develop this logic for the ENIU target. The RX3i
Ethernet NIU allows the addition of up to 20K bytes of logic to be executed locally in
GFK-2053A 7-1
7
the I/O Station. A LD logic block named “Local User Logic” is provided for this
purpose.
8. Repeat steps 2 through 7 for each ENIU.
9. Store this information to each ENIU.
10. Add the Ethernet Global Data component to the Primary (PLC_A_HW target) and
Secondary (PLC_B_HW target) Controllers.
Redundant Controllers
Using the Genius Handheld Monitor (HHM), set each Genus device for Redundant Controllers
= YES.
BSM Present
Using the Genius Handheld Monitor (HHM), set the BSM Present configuration parameter to
YES. This is required whether or not a dual Genius I/O bus is being used.
When this parameter is configured as YES, then the output default period is extended from 3
token rotation time periods to 2.5 seconds. The extra time allows the RX3i PLCs to exchange
mastership correctly.
BSM Controller
If the Genius I/O device is attached directly to a dual bus, either by a Bus Switching Module
(BSM) or a Bus Interface Unit (BIU), then you must configure this device to be a BSM
Controller.
In the case of Field Control connecting to the BIU, setting the parameter to be a BSM
Controller directs the BIU to activate its internal bus switching circuitry.
If the device is connected to a “stub” downstream of another device that controls the
switching, then set BSM Controller to NO.
3. Expand the Hardware Configuration and then click on the Genius NIU component
(IC200GBI001)
Serial Bus Address: Set this in accordance with the addressing scheme for
your project.
BSM Controller: Set this to Yes if there are two Genius busses that
connect directly to the NIU. Set this to No, if there is a
single bus connection.
7. Connect a serial programming cable to your workstation and to the VersaMax I/O
drop.
9. Repeat this for any other VersaMax I/O drops in the system.
A Scanner routine executes in the drop’s CPU. This routine scans all input devices and
transmits the input states to the Hot Standby PLCs by way of the I/O bus.
1. Create a new project based on the appropriate Remote 90-30 Genius Drop template.
The Remote 90-30 Genius Drop project is added to the Machine Edition project
Navigator by using the File > Restore Project… menu item. Select the Project
Navigator window making certain that there is no project open at this time.
When you click on Open, a new project will be added to the Proficy Navigator window.
Primary Bus
The Genius bus controller should be configured as follows:
In the Settings Tab
Serial Bus Address (SBA): Any address from 0 to 29 is acceptable. (Note: Normally a
Genius Handheld Monitor normally is set for SBA=0. It is
standard practice to avoid 0 when using Field Control or
Genius I/O.)
Status Reference Type: %I00481 for M23, M31, and M40 drop folders
%I02017 for M5S and M5L drop folders
In the Global Data Tab
At the GBC’s Address:
At SBA 30:
At SBA 31:
At SBA 30:
At SBA 31:
For example, assume that your Remote Drop is implemented using a model IC693CPU323.
This CPU supports a maximum of 512 discrete output addresses. Your Hot Standby CPUs
are each a model IC695CMU310. This CPU supports 32640 output addresses. The mapping
process allows a portion of the output addresses in the range %Q00001..02048 to be mapped
into the range %Q00001..00512 at the remote drop.
4. In the first MOVE function, a constant is moved into the reference named M_Q_ST
(Master CPU Starting Q Ref) Enter the starting reference for the outputs that are to be
received from the Hot Standby PLCs.
5. In the second MOVE function, a constant is moved into the reference named L_Q_ST
(Local Rack Starting Q Ref) Enter the starting reference for the outputs in the Remote
Drop in that you wish to place the Hot Standby values.
6. In the third MOVE function, a constant is moved into the reference named L_Q_LN
(Local Rack Q Length (bits)) Enter the number of outputs that are to be mapped into
the Remote Drop.
1 1 1
1 IN Q M_Q_ST 1 IN Q L_Q_ST 256 IN Q L_Q_LN
%R09288 %R09289 %R09290
Master CPU Local Rack Local Rack Q
Startng Q Ref Startng Q Ref Length (bits)
For example, assume that your Remote Drop is implemented using a model IC693CPU323.
This CPU supports a maximum of 512 analog output addresses. Your Hot Standby CPUs are
each a model IC695CMU310. This CPU supports up to 32640 analog output addresses. The
mapping process allows a portion of the output addresses in the range %AQ00001..32640 to
be mapped into the range %AQ00001..00032 at the remote drop.
1 1 1
1 IN Q M_A Q_ST 1 IN Q L_A Q_ST 25 IN Q L_A Q_LN
%R09291 %R09292 %R09293
Master CPU Local Rack Local Rack
Startng A Q Startng A Q A Q Length
Ref Ref (words)
For example, in the configuration shown below, remote drops would be able to access
discrete outputs only within the range %Q00001..00064. No other discrete output data is
being broadcast in the global data exchange, and thus no other discrete output data is
available for the remote drops.
Without a valid product authorization, a Max-ON system will operate in demonstration mode for
22 days. While operating in this mode, all of the system’s capabilities are fully functional. At the
end of the demo period, PLC A will initiate an orderly transfer of Mastership to PLC B. Then
PLC A will shutdown automatically.
GFK-2053A 8-1
8
2. Select the menu item Project, then End-User Information. The form shown below will be
displayed.
3. Enter the information into the text boxes on the form, making certain that you fill in all of the
items that are marked with an asterisk (*). Although not required, please fill the other entries
as well.
4. Verify that the PLC Key Code is visible, and that it agrees with the most current value in
CPU A, register %R09011. (If the Key Code is not visible, then you may retrieve the value
using the Proficy View project Max-ON Diagnostics.)
6. Disable all checkboxes except for the one labeled End-User Information.
7. Using Max-ON Tools, select the menu item File, then either Print Configuration Summary (to
print a hard-copy of the End-User Information) or Save Config Summary to RTF File (to
produce an electronic copy of the information.)
2. Enter the values that you received from GE Fanuc into the corresponding text boxes.
4. Using Max-ON Tools, select the menu item File, then Save Project Folder. Max-ON Tools
will verify the authorization codes. If the authorization codes are valid, then you
6. If the report contains the response, “The authorization codes are invalid”, then there has
been an error entering one or more of the codes. Correct your entry (entries) and then
repeat steps 3..5.
7. If the report contains the response, “The project is valid”, then the utility has revised your
project folder to include the new authorization codes.
8. Save the project configuration. This will update the project file and also update the c-block
that is used by the PLC.
3. Click on Update. A dialog box similar to the one shown below will be displayed. (Note that
you may have to navigate to the folder containing the c-block. In a default Machine Edition
installation, the basepath will be “c:\Program Files\Cimplicity MACHINE
EDITION\SecurWORX\Temp\...”
2. Make certain that you have available functional communications with both PLCs. (This can
be Ethernet or Serial.) Also, make certain that the communication drivers are updated to
reflect Ethernet settings or Serial Port settings.
3. Start the View project by pressing F9. The following window will appear:
4. Using the mouse, click on the Authorization tab. The following window will be displayed:
5. Verify that the authorization codes are valid. You may have to wait up to a minute for the
form to update. (This is because the authorization codes are validated once per minute.)
• Make certain that you have selected and stored the correct folder to CPU A.
• Make certain that you that the PLC Key Code agrees with the value that you
submitted to GE Fanuc.
• Make certain that in the section above, the Configuration Summary indicated The
project is valid.
Restarting CPU A
If CPU A has halted due to an Authorization fault, it may be restarted by performing the
following procedure.
1. While CPU A is in STOP mode, set the internal coil reference %M1016 (Reset All Alarms)
2. Restart CPU A. This will reset the timer that is associated with the Authorization Alarm and
Authorization Fault. Also, this will reset the internal coil references %M0993 (Authorization
Alarm) and %M0994 (Authorization Fault).
3. Wait approximately one or two minutes and then check to make certain that the
Authorization Fault (%M0993) remains cleared.
9
This chapter explains how to upgrade the Max-ON program blocks in your application to a
newer version of Max-ON using the Proficy Toolchest.
Overview
The general sequence for updating an application is as follows:
• Update the existing hardware configuration for the target named PLC_A_HW.
• Update the existing hardware configuration for the target named PLC_B_HW.
• Delete the Max-ON driver blocks (except for Cfg_Dat) from the target named
PLC_COMMON_CODE.
• Ctrl-Drag new Max-ON drivers from the Toolchest into the target named
PLC_COMMON_CODE.
• Select the hardware target that is associated with the Backup PLC. Set it as the Active
Target.
• Download (Hardware only) the appropriate hardware target to the Backup PLC.
• Go offline.
• Select the hardware target that is associated with the new Backup PLC. Set it as the
Active Target.
GFK-2053A 9-1
9
• Download (H9ardware only) the appropriate hardware target to the Backup PLC while it
is in STOP mode.
• Go offline.
• Adjust the target’s Ethernet I.P. address to match the address of the Backup PLC. (Or if
using a serial connection, connect to the programming port on the Backup PLC.)
• Download (Logic only) the target named PLC_COMMON_CODE into the Backup PLC.
• Go offline.
• Adjust the target’s Ethernet I.P. address to match the address of the Backup PLC. (Or if
using a serial connection, connect to the programming port on the Backup PLC.)
• Download (Logic only) the target named PLC_COMMON_CODE into the Backup PLC.
1. Make certain that all projects are closed so that only the current projects are displayed in
the Navigator window.
3. Right-click on the project and the following menu list will be displayed.
5. Navigate to the directory in which you wish to save the backup copy of the project.
6. Make certain that the file is saved as a Zip File (*.zip), and then click on Save.
f. Press the Open button. This will add the drawer to your Toolchest.
3. Delete the Max-ON Driver blocks that start with “hbr_” from the MaxON_Components
folder.
4. Add the version Max-ON Drivers to the MaxON_Components folder directory using
the Ctrl-Drag-and-Drop operation from the Toolchest.
The Blocks must be added to the Machine Edition Project in the following order:
b. hbr_099
d. hbr_000
6. An _MAIN Block is also available in the Toolchest Drawer. This Block has a
comment in the first rung that details the revision history. However, this block is not
normally imported.
7. Validate your Max-ON application to verify that all Max-ON Driver blocks are properly
located in the Project.
8. You can also verify the version of each hbr_ Block by checking the description in the
Block Properties:
10
A Proficy View project is included on the Max-ON installation CD that provides diagnostic
functions for your redundant system. Max-ON Diagnostics may be used to obtain real-time
status, alarms and historical operating information relating to the Max-ON redundancy PLCs.
1. Create a new project based on the generic Max-ON Diagnostic Tool project. This
project is added to the Machine Edition project Navigator by using the File > Restore
Project… menu item. Select the Project Navigator window, making certain that there
is no project open at this time.
GFK-2053A 10-1
10
3. Navigate to the Proficy Components directory, then to the Diagnostics VIEW. Make
certain that the selection for Files of Type has been set to Proficy Machine Edition
(*.zip).
When you click on Open, a new project will be added to the Proficy Navigator window.
2. Expand the PLC Access Drivers node in the Navigator for the View target and select
the PLCA device.
3. Modify the Address of PLCA in the Inspector to match the IP address of PLC A in your
Max-ON system.
5. Select the Download and Start Active Target toolbar button to start the Max-ON
Diagnostic program, or press the F9 key.
System Status Clicking on this tab displays the Real-time Status page. The page
contains information on scan times, update rates, and PLC status.
Alarms Clicking on this tab will bring up the Alarm Table display page. This
page lists any alarms that have been archived within the PLCs that
have active connections. Alarms may be cleared from this display
page.
Project Info Clicking on this tab will display the Project Information page. Catalog
number, version number, program checksum, and other items are
displayed.
Authorization Clicking on this tab will display the Authorization page that indicates if
the system is operating in Demo mode or not.
Please note that if the Diagnostic Tool is not communicating with the PLCs, a will be
displayed for the items.
The symbol indicates a Latched Alarm condition, where a symbol indicates a current
Alarm condition.
System Status
You may view items that relate to the current operating characteristics of your system on the
System Status page. An example is shown in the picture above.
PLC A and PLC B Status Indicates the operating status of the corresponding PLC, either
Running or Stopped.
Local Scan Time The scan time, in milliseconds, for the Local PLC.
Remote Scan Time The scan time, in milliseconds, for the Remote PLC.
%R Update Time This is the time required to update synchronized data of type %R.
The time is reported in seconds.
%AQ, Q, M Update Time This is the time required to update all configured synchronized data
of the types %AQ, %M, and %Q. The time is reported in seconds.
Failover Mode This field indicates the mastership status of the corresponding PLC,
either Master or Backup. There never should be two Masters or two
Backups in a system that is operating properly.
PLC A and PLC B Identity A-Preferred, B-Preferred, or Float
Program Restart The local CPU has been switched from STOP mode to RUN mode.
Power Up The local CPU has undergone a power-up event.
Remote CPU Offline The companion PLC is offline. This may be due to the CPU being in
STOP, Fault, or Powered Off. Also it may be due to a cable problem
or Ethernet Interface failure.
Data Sync OK This field indicates the completion status for the transfer of
synchronized data. The Backup CPU will indicate either Synced (all
Synchronized Variables have been received) or Not Synced. The
Master CPU always indicates Synced (ON). It is ON in the Backup
CPU at the moment when all Synchronized Data items have been
updated.
Authorization This indicates that PLC A is operating in DEMO mode. PLC A will
operate for up to 22 days in this mode. At the end of the 22 day
period, Mastership will transfer to PLC B (if it is available). At this
point, PLC A will transition to STOP mode.
Alarms
Historical information is stored in the alarm table. This table contains archived information for
up to 32 alarm records for each PLC. The records store information for both system alarms
and optional user-defined alarms. Each alarm record consists of an identifier for the event
that initiated the entry, along with a date/time stamp to indicate when the event occurred.
Typical events include change of Hot Standby mastership, loss of PLC power, program
restart, and loss of I/O devices.
Note: User defined alarms are not available in the current version of Max-ON Diagnostic
Tools.
Project Information
You may view certain items that relate to the general nature of your system. Select the
Project Info tab.
PLC Catalog Number The catalog number for the Max-ON drivers that are running in the
corresponding PLCs.
SW Version The current version number of the Max-ON PLC drivers
User Version Number If Audit trail has been enabled, then this represents the number of
times the application logic has been changed. If Audit trail has not
been enabled, then the Max-ON drivers will not update any value
here.
User Version Date If Audit trail has been enabled, then the current date and time will be
posted here each time the application logic is changed. If Audit trail
has not been enabled, then the Max-ON drivers will not update any
value here.
Program Size An approximate program size. There will be a slight difference
between the value displayed in Logic Developer PLC and the value
displayed here. The Max-ON value shows the total for program logic,
Authorization
You may view the information related to the authorization of your system by selecting the
Authorization tab.
Max-ON Key Code This field displays the current decimal value of the keycode contained
in PLC A, register %R09010.
Authorization Codes The left pane indicates if the current Authorizations codes are valid
for the Max-ON system.
The right pane displays the ten Authorization codes that are set in
the Max-ON drivers.
Ethernet Hardware
The Series 90-30 PLC offers two classes of modules that support Ethernet connectivity.
I/O Module
The IC693CMM321 module installs in the 90-30 rack to provide one network link. The module
provides an AAUI connector that supports one link to a 10 megabit network by way of an
external Ethernet transceiver.
CPU Modules
The IC693CPU364, IC693CPU370, IC693CPU372 and IC693CPU374 contain a built-in
10BaseT port. The CPU link has considerably higher throughput than the IC693CMM321 link.
GFK-2053A A-1
A
2. Prior to the call to HBR_000, enter a rung that sets %M1012 to ON.
3. Store the application folder into CPU A.
4. Store the application folder into CPU B.
Manual Mode –
The second method is to configure the CPUs to execute in Constant Sweep mode. The
configuration is entered via the Hardware Configuration utility. Both of the hardware
configuration targets (PLC_A_HW and PLC_B_HW) must be set and then stored into the
corresponding CPUs.
Why you should consider this approach –
By having the Master in Constant Sweep mode, Ethernet communications with HMIs may be
improved dramatically.
Prerequisite: The system has been completed and is operating in its normal fashion (i.e., all
application logic has been finished, HMIs are attached and communicating, and all peripherals
are connected and operating normally.)
The procedure is as follows:
1. Record the peak PLC scantime in the Master CPU. You should observe the system for
several minutes to obtain this value.
2. Add 75 to the value you obtained in step 1. Round this value up to the next multiple of 5.
3. Open the hardware configuration folder for CPU A.
4. Zoom into the CPU module. Click on the Scan tab.
5. Set the Sweep Mode to Constant Sweep.
6. Set the Sweep Timer to the value calculated in step 2.
7. Store the configuration into CPU A.
8. Open the hardware configuration folder for CPU B.
9. Repeat steps 4 through 6.
10. Store the configuration into CPU B.
11. Open your application folder.
12. Prior to the call to HBR_000, enter a rung that resets %M1012 to OFF.
13. Store the application folder into CPU A.
14. Store the application folder into CPU B.
My two CPUs stop immediately after I store my Max-ON project. What did I do wrong?
One or more of the Synchronized Data types that you have configured is greater than the
maximum quantity allowed for the product on which the project is based.
GFK-2053A B-1
B
I stopped one of my CPUs and then disabled the Max-ON PLC drivers in the remaining CPU. Now
my output devices aren’t working. What has happened?
You will need to change the configuration in the Genius bus controllers. Set Output at Start to
Enabled. Don’t forget to change the configuration to Disabled when you are ready to run the
Max-ON drivers again.
CPU A has stopped. I know that the authorization period has expired, but I can’t get the CPU
running again. What can I do?
Make certain that you turn ON %M1016 while CPU A is in STOP. Then restart the CPU. This
will authorize CPU A for an additional 22 days.
G
A Genius and Field Control I/O, 7-3
Adding a Secondary Bus to an Existing Genius and Field Control I/O (Config. I/O),
Bus, 4-12 7-3
Adding an I/O Device, 4-14 Genius Bus Controllers, 6-6, 6-7, 6-13
Authorization, 2-11, 8-1 Genius Bus Controllers - CPU A, 6-7
Genius Bus Controllers - CPU B, 6-13
B
BSM Controller, 7-4 I
BSM Present, 7-3 I/O Bus Topologies, 2-9
I/O devices, 6-9, 6-10, 6-14
C adding, 4-14
deleting, 4-16
Configuring Analog Inputs, 4-17, 4-19, 4-20, 4- editing, 4-16
22 Identity - CPU A, 6-3
Configuring Data Transfers, 4-25 Identity - CPU B, 6-11
Configuring the Analog Output Range, 7-13 Indicating Mastership, 5-3
Configuring the Drop's GBC, 7-9
Configuring the Ethernet Interface, 4-24
Configuring The Hot Standby GBCs, 7-14
K
Configuring the I/O Devices, 7-1, 7-3 Key code, 8-1
Configuring the Secondary Address, 4-23
Create the Authorization Request Form,
8-1 M
Creating a Connection to a PLC, 10-3 Mastership Modes, 5-11
Creating a New Project, 4-2 Memory, 6-4, 6-12
Creating Connections to the PLCs, 10-3
Creating the Drop Folder, 7-6
O
D Obtain the Authorization Codes, 8-3
Online Project Information, 10-7, 10-9, 10-11
Deleting a Module, 4-8
Deleting a Rack, 4-7
Deleting an I/O Device, 4-16 P
Diagnostics, 10-1 PID Function Blocks, 5-17
PLC Sweep Mode, A-1
E Product authorization, 8-1
Product Authorization, 2-11
Editing an I/O Device, 4-16 Programming, 5-1
Enter the Authorization Codes, 8-3 Project information, 10-7, 10-9, 10-11
Ethernet Hardware, A-1 Project workflow, 3-2
F R
Failover Time, 2-7 Redundant Controllers, 7-3
Fault Record Structure, 5-21 References, iii
Fault Table, 5-21 Related publications, iii
Frequently Asked Questions, B-1 Remote 90-30 Drops, 7-6
Remote Drop Status Word, 7-8
Remote Status Flags, 5-8
Retrieve the PLC Key Code, 8-1
GFK-2053A Index-1
Index
S
Secondary bus
adding, 4-12
Selecting a Master, 5-11
Setting a Preferred Master, 5-13
Simplex Genius Bus, 4-9
Synchronized Data Transfers, 2-7
System Command Flags, 5-10
System Data Registers, 5-16
System Level Alarms, 5-25
System Options, 4-32
System Status Flags, 5-2
T
Time Stamp Record Structure, 5-21
Troubleshooting
diagnostic tools, 10-1
frequently asked questions, B-1
U
Uninstalling Max-ON Tools, 1-4
V
Verifying the Authorization Codes, 8-5
W
Welcome, 1-1
Working with Projects, 4-1