GFK 1918K
GFK 1918K
Version 5.80
April 2008
GFK-1918K
All rights reserved. No part of this publication may be reproduced in any form or by any electronic or mechanical means,
including photocopying and recording, without permission in writing from GE Fanuc Intelligent Platforms, Inc.
Disclaimer of Warranties and Liability
The information contained in this manual is believed to be accurate and reliable. However, GE Fanuc Intelligent Platforms, Inc.
assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the foregoing, GE Fanuc
Intelligent Platforms, Inc. disclaims any and all warranties, expressed or implied, including the warranty of merchantability and
fitness for a particular purpose, with respect to the information contained in this manual and the equipment or software
described herein. The entire risk as to the quality and performance of such information, equipment and software, is upon the
buyer or user. GE Fanuc Intelligent Platforms, Inc. shall not be liable for any damages, including special or consequential
damages, arising out of the use of such information, equipment and software, even if GE Fanuc Intelligent Platforms, Inc. has
been advised in advance of the possibility of such damages. The use of the information contained in the manual and the
software described herein is subject to GE Fanuc Intelligent Platforms, Inc. standard license agreement, which must be
executed by the buyer or user before the use of such information, equipment or software.
Notice
GE Fanuc Intelligent Platforms, Inc. reserves the right to make improvements to the products described in this publication at
any time and without notice.
© 2008 GE Fanuc Intelligent Platforms, Inc. All rights reserved. * Trademark of GE Fanuc Intelligent Platforms, Inc. Any other
trademarks referenced herein are used solely for purposes of identifying compatibility with the products of GE Fanuc
Intelligent Platforms, Inc.
We want to hear from you. If you have any comments, questions, or suggestions about our documentation, please send them
to the following e-mail address:
doc@gefanuc.com
3
Contents
1 Welcome 1
Proficy Logic Developer - PLC . . . . . . . . . . . . . . . . . . . . . . . . . .2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Product Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Hardware Key Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Software Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Contact GE Fanuc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
General Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Americas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Europe, the Middle East, and Africa (EMEA) . . . . . . . . . . . . . . . .9
Asia Pacific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
3 GE Fanuc Targets 29
Adding, Configuring and Converting Targets . . . . . . . . . . . . . . . . .30
Adding Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Configuring Controller Targets . . . . . . . . . . . . . . . . . . . . . . . .31
Converting Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Configuring Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Interacting with a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Validating a Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Offline, Online: monitor mode, programmer mode . . . . . . . . .39
Upload/Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Run/Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4 Hardware Configuration 49
PACSystems* RX7i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring PACSystems* RX7i Hardware . . . . . . . . . . . . . . . 50
PACSystems* RX3i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuring PACSystems* RX3i Hardware . . . . . . . . . . . . . . . 52
Configuring Controller Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 53
I/O variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Hot Redundancy Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring Hot Redundancy Systems . . . . . . . . . . . . . . . . . . 63
PACSystems* RX3i and Series 90*-30: DSM324i and Motion Mate
DSM314 Motion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Series 90*-70 Genius Remote I/O Scanner . . . . . . . . . . . . . . . 69
VersaMax*Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Index 145
SYSTEM REQUIREMENTS
To use Logic Developer - PLC* and its tools, you require the following:
■
Windows XP Professional Service Pack 2, Windows 2000 Professional Service
Pack 4, or Windows Vista.
Note: Windows Vista SP1 is also supported, but Windows XP Tablet PC Edition
and Windows XP Embedded are not supported.
■
Internet Explorer version 7.0, Internet Explorer version 6.0 Service Pack 1 or
later, or Internet Explorer version 5.5 with Service Pack 2 Q810847 or later.
Note: You must install Internet Explorer before installing Machine Edition*.
■
TCP/IP network protocol-based workstation (if you use an Ethernet connection).
■
Requirements for processor speed and memory are as follows:
Minimum: 1 GHz Pentium-based processor with 256 MB RAM
Recommended: 2 GHz Pentium-based processor with 512 MB RAM
Note: For projects with more than 75,000 variables or variable elements, at
least 1 GB RAM is strongly recommended.
■ .NET Framework 2.0. If the Microsoft .NET Framework is not yet installed, it is
automatically included during installation of Machine Edition*.
■
1 GB hard disk space. Additional space is required for your projects and
temporary files.
INSTALLATION
For last-minute information, release notes, and supported hardware lists for
Machine Edition* products, see the Important Product Information (IPI) document
on the CD. There are several ways to view this document
■ When installing Machine Edition*, select Important Product Information on
the initial Launcher screen.
■
When running Machine Edition*, from the Help menu, choose Important
Product Information.
If you have a previous version of Machine Edition* installed on your computer, you
must uninstall it before installing the latest version. You can do so by selecting the
“Uninstall Machine Edition*” option from the Machine Edition* Start menu group.
All of your existing projects, settings, and authorizations are preserved following
an uninstall operation.
Note: See the IPI Release Notes for information on troubleshooting installation
problems.
PRODUCT AUTHORIZATION
Before you can start developing projects in with Logic Developer - PLC*, you must
authorize the software. If you do not do so, you will have unrestricted use of the
software’s features only for a short trial period. The authorization process takes
only a few moments and enables you to take advantage of any product support for
which you qualify.
There are two types of authorization available: software key authorization and
hardware key authorization. Machine Edition* products can use a mixture of
authorization types on a single computer.
To see which products you are currently authorized for, on the Machine Edition*
Help menu, point to Product Authorization and choose Authorize Software. This
displays the Product Authorization dialog box. If you have a hardware key plugged
in a USB port, you can select the Show Hardware Keys check box to view the
authorizations provided by that key.
Typically, the USB port is located on the front or back of your tower case, or in the
side of a laptop computer. In some cases, a USB port can be found on your
computer’s monitor.
2. Plug the hardware key into the USB port.
The first time you plug the key into a USB port, a progress dialog box indicates that
Windows has detected new hardware and is updating its system settings. After the
dialog box disappears, the settings stored in the hardware key are active and you
can use the Machine Edition* products that it authorizes.
You must leave the hardware key in the port while using Machine Edition*. If you
remove the key from the port, authorization for those products vanishes, though
you can still use products previously authorized by means of a software key.
To move the authorization to another computer, remove the hardware key from the
source computer and plug it into a USB port on the destination computer.
Software Key
When authorizing Machine Edition* products with a software key, you need to
contact us by telephone, fax, or e-mail. If you want to authorize your software by
telephone, note that authorization personnel are available only during regular
business hours (between 6 a.m. and 6 p.m. MST).
Software key authorization is specific to a single computer. If you want to work
with Machine Edition* on a different computer, you must move the authorization
to that second computer (see page 7).
To aut h orize a copy o f Mach in e E dit ion * wit h a s oft wa re k e y
1. Have your serial numbers ready.
The serial numbers can be found on the License Key sheet that came with your
product.
2. Run the Product Authorization program from the Start menu > Programs > GE Fanuc > Proficy Machine
Edition> Product Authorization.
The Product Authorization dialog box appears.
3. Click Add.
4. In the dialog box that appears, select the means by which you are authorizing: Internet, Phone/Fax/E-mail, or
Floppy Disk Transfer. Click Next.
If you choose the Internet option, follow the instructions on the web site.
If you choose the Phone/Fax/E-mail option, proceed to step 5.
If you choose the Floppy Disk Transfer option, ensure you have an authorization
disk before proceeding.
5. Fill in the fields in the dialog box.
Fields that are identified with an asterisk (*) must be filled in.
6. If authorizing by:
■
Phone, click Phone/Fax and call the number on the screen to receive one or
more new key codes.
■
Fax, click Phone/Fax. In the dialog box that appears, click Print FAX. Fax the
Product Authorization Request to us, using our fax number on the printout. We
will reply by fax with your new key code(s).
■ E-mail, click Send E-mail. In the dialog box that appears, click Authorize to e-
mail us. We will reply by e-mail with your new key code(s).
Product Authorization is complete after you enter the new key code and it has
been accepted. Depending on the products you have purchased, you may need to
run the Product Authorization program a number of times.
T o mo ve th e s of t w a re ke y a u th or i z a t i on to a n ot h er c om p ut e r
You can run the software only on the computer that has Product Authorization. To
develop your projects on a different computer, you need to complete the following
steps to move the software key authorization from one computer to another.
1. Install Logic Developer - PLC* on the computer that the authorization will be moved to. Run the Product
Authorization program: Start menu > Programs > GE Fanuc > Proficy Machine Edition > Product
Authorization.
The Product Authorization dialog box appears.
2. Click Move, and then click OK.
There is a Target Site Code on the top right hand side of the screen. Write down
this site code carefully. It must be correct for the move to work. You need the Target
Site Code when you move the authorized software from the source computer.
3. Click Authorize by disk.
4. Go to the source computer that has the authorized software.
5. From the source computer, run the Product Authorization program.
6. Click Move and then click OK. Enter the Target Site Code that you wrote down at step 2 and click Next. Verify that
the site code is correct and click OK.
7. Insert a blank formatted floppy disk into the floppy drive and click Next.
The authorization code is moved to the disk and a message box appears telling you
it was successful.
8. Click OK.
9. Go back to the computer to which you are moving the authorization and insert the floppy disk.
The dialog box that is asking for an authorization disk is displayed.
10. Click Next, and then click Finish.
A dialog box appears telling you the move was successful.
11. Click OK.
To upg rade a s oftw are k e y au th ori zation to a ha rdwa re k e y auth ori zation
1. Order a hardware key.
Your software authorization remains valid until you complete the following steps.
2. When you receive the hardware key, locate a free USB port on your computer.
3. Plug the hardware key into the USB port.
Technical Support
If you have technical problems that cannot be resolved with the information in this
guide, please contact us by telephone or email, or on the web at
www.gefanuc.com/support.
Americas
Online Technical Support: www.gefanuc.com/support
Phone: 1-800-GE FANUC (1-800-433-2682)
International Americas Direct Dial: 1-434-978-5100
Technical Support Email: support@gefanuc.com
Customer Care Email: customer.care@gefanuc.com
Primary language of support: English
Asia Pacific
Online Technical Support: www.gefanuc.com/support
Phone: +86-400-820-8208
+86-21-3217-4826 (India, Indonesia, and Pakistan)
Technical Support Email: support.cn@gefanuc.com (China)
support.jp@gefanuc.com (Japan)
support.in@gefanuc.com (remaining Asia customers)
Customer Care Email: customercare.apo@gefanuc.com
Remote I/O
I/O Modules
Motors/Drives
Internet/Intranet
Web Access
QUICK START
Machine Edition makes it easy to get started developing a project.
To s t ar t Mac hin e Ed it io n
1. On the Windows toolbar, click Start, point to Programs, then GE Fanuc, then Proficy Machine Edition,
and then click Proficy Machine Edition. (See also page 26.)
When Machine Edition initializes for the first time following installation, the
Environment Themes dialog box appears.
You can change the default theme later by clicking the Window menu and choosing
Apply Theme.
2. Choose the environment theme you want to work in.
3. Click OK.
When you open a project, the appearance of your Machine Edition screen will
match the preview in the Environment Themes dialog box. As you work, you will
likely modify the environment – opening and closing windows, changing the
selected toolbars, and so on. Any changes you make are retained in your default
environment setup.
Select this option to choose from Select this option to choose from all
those projects that have been existing projects
used recently.
4. Select the appropriate option to open a project. The Open an existing project option is selected by default.
Notes:
■
If you select either Empty project or Machine Edition template, the New Project
dialog box appears to let you create a new project.
■
If you select Open an existing project, you can choose from Recent Projects (the
default) or All Projects. You may need to also specify the location of the project:
whether it is located on the local computer (My Computer), in a shared folder
(Shared Projects), or on Manager Server (Server).
5. If you selected the Open an existing project option, select the project that you want to open from the list.
Existing projects include samples and tutorials that you can use to familiarize
yourself with Machine Edition.
6. If desired, select the Don’t show this dialog box on startup option.
7. Click OK.
Your project opens in the Machine Edition environment that you specified in the
Environment Themes dialog box. For more information, see “Machine Edition
Projects” on page 25.
Toolchest:
Navigator: Contains
Organizes and displays preconfigured objects
project information in a that can be dragged
tree structure. into Machine Edition
projects.
Navigator tabs:
Conveniently layers
information about your InfoViewer:
projects. An embedded
browser used to
Inspector: display reports and
Displays the properties comprehensive help.
of a selected object.
Feedback
Companion: Zone: Displays
A dynamic help window
output information
that provides
information based on generated by
what you’re doing. Machine Edition
components.
Getting Help
There are many ways to access the Machine Edition online help system.
■
Press F1 on any selected item for context-sensitive help.
■
Browse through the table of contents in the InfoView tab of the Navigator.
■ Perform a full-text search of the help in a separate HTML Viewer window: on
the Help menu, choose Search.
■
Search for keywords using the index: on the Help menu, choose Index.
■
Use the Companion to dynamically display a brief description about
whatever item you have selected.
You can also access additional help on the web. In Machine Edition on the Help
menu, point to GE Fanuc on the Web, and then choose:
■
Technical Advisor.
■
GE Fanuc Home Page.
Machine Edition provides two kinds of Help windows to display help information:
the Companion and the InfoViewer.
For detailed context-sensitive help, select any item (in this
case, a button on a graphical panel) and press F1.
The Companion is a
dynamic help window
that displays snippets
of information on any
selected item.
Getting Help
Companion The Companion window displays brief information about whatever item you
happen to be working with, anywhere in Machine Edition. Whether you need the
meaning of a property, the purpose of a node in the Navigator, or an explanation of
errors generated during validation, the Companion is always there for you.
By default, the Companion is open while editing projects. If it’s been turned off,
click on the Tools toolbar to open it again.
InfoViewer The InfoViewer window is an embedded HTML browser that provides more
detailed and procedural help. It is launched whenever you access help topics from
the InfoView Tab, the help index, or by pressing F1 on a selected item.
Want to know more? In the Help Index, look up Help and choose “Finding information in the
Help”.
InfoViewer
Navigator Companion
Control I/O Toolchest
Feedback Zone Data Watch
Inspector
Tools Toolbar
If you are not sure of the name of a tool within a toolbar, hover the mouse pointer
over the tool’s button to display its name in a tool tip.
Want to know more? In the Help Index, look up “Toolbars: an Overview”.
T o o p e n a p r oj e ct i n th e N a vi g a t or
1. In the Manager tab of the Navigator, right-click an existing project listed under My Computer and choose
Open.
The project is opened in Machine Edition. The Variables and Project tabs are
added to the Navigator and the nodes change to reflect those components that
make up the project you just opened.
The Project tab organizes your project. Use it The Variables tab contains all the variables
to navigate around your project, and add, in your project. Use it to add, delete, move,
delete, and configure the items that make up and otherwise manipulate variables.
your project.
Inspector In Machine Edition, practically every object has properties. Properties are simply
attributes and information about that object. For example, the properties of a box
on an HMI graphical panel include Height, Width, Fill Color, and Outline Color.
The properties of an object are edited in the Inspector window:
■
To edit an object’s properties, select it with the Inspector open. The Inspector
will show all those properties associated with the selected object.
■
When a property changes an object’s appearance, you’ll see the results of the
change immediately in the object’s editor.
■ To see more properties for an object, select a tab at the bottom of the Inspector.
The Static tab contains The Auto tab displays variables A Watch List tab contains all variables in your
variables that you add to the associated with the item currently project that have been added to the currently-
Data Watch tool. selected in an editor or tool. selected Watch list.
Smart Lists
While working in Machine Edition editors, you are frequently required to input
variable names, instruction mnemonics, and other data items. The Smart List can
speed text entry of these items.
Smart List Display For example, if you typed “fill” in the Smart
List, the FillLevel variable would be
highlighted. If you want to use an existing
variable (in this case, “FillLevel”), use the
Down arrow to select the highlighted item,
then press ENTER. To create a new variable
called “fill”, simply press ENTER without using
the Down arrow.
The Toolchest
Toolchest Window
Definitions of most preconfigured objects within the Toolchest are displayed in the
Companion.
Feedback Zone The Feedback Zone (available only while editing a project) is an interactive
window that displays output information generated by Machine Edition-enabled
components. Using the Feedback Zone, you can keep track of project information,
locate validity errors within your project, display generated reports, and more. It is
organized into several tabs. Click on a message to display more information about
the error in the Companion Window.
Want to know more? In the Help Index, look up “Feedback” and choose “Feedback Zone
Tool Window”.
The Import tab displays a list of errors and warnings The Reports tab displays a list of all reports
from an import operation (for example, generated during the current session. Double-click
errors/warnings will be listed when you import a report in the list to redisplay it in the InfoViewer.
variables from a PLC into a Machine Edition project).
Feedback Zone
Managing Variables
Variables are named storage spaces for data values defined in Machine Edition
projects. A variable could store the current velocity of a motion controller motor,
the height of a robotic arm, or any other value that an application needs to keep
track of. Most variables in a project can be shared among various components and
targets, such as View panels and Logic Developer - PC’s ladder logic.
You manage variables in the Variables tab of the Navigator, also called the
Variable List. Like most items in Machine Edition, you configure variables by
editing their properties in the Inspector.
The values a variable can store depends on its data type. For example, a DINT data
type indicates that the variable can store “Double Integers”, 32-bit values. The
location where a variable’s value is stored is indicated by its data source. Typically,
a variable’s value is either stored internally in the target’s memory or is retrieved
(and sent) to external PLC hardware, via an I/O terminal or other connection.
Available data types and data sources depend on the target type and (if applicable)
components added to the target.
You can also use arrays and structure data types in Machine Edition projects. An
array is a series of variable elements with identical data types, referenced by a 0-
based index (as in “MyArray[3]”). A structure data type is a group of variable
elements that may or may not have the same data type, referenced by the name of
each element (as in “MyStructure.MyElement”). Custom structure data types are
created with fxClasses in the Toolchest.
Want to know more? In the Help Index, look up “STRUCTURE data types”.
Property Columns In addition to the Inspector, with the three buttons at the top of the Navigator, you
can edit variable properties in a spreadsheet-like column view.
Click to open and close the property column display. This button is available only in the Variables tab.
Click to dock and undock the Navigator window. Undocking the Navigator (that is, making it work like
an Editor window) can make it easier to work with properties in the column view.
Click to display a list of available property columns. Double-click a property to add it to the current set.
When opened, the Navigator’s property columns view consists of a grid of cells:
Variable Reports While you can generate reports on many things in Machine Edition, they are
especially useful for the Variable List. Among the available reports are:
■
All variables by name, filtered or unfiltered.
■
Cross-references to variables (that is, the places they are used in the project).
■
All forced variables (Logic Developer - PC and Logic Developer - PLC only).
■
Unused variables (that is, variables with no references anywhere in the project).
The unused variables report also has a link that lets you delete all unused
variables from the project at once.
Reports are displayed as HTML pages in the InfoViewer. To generate a report, click
anywhere in the Variables tab then, on the File menu, select Report.
Want to know more about Variables? Look up the following in the Help Index:
■
For information on variables in general, choose “Variables: an Overview”.
■ For information on variables in View, choose “Variable support in View Developer”.
■
For information on variables in QuickPanel projects, choose “Variable support in
QuickPanel applications”.
■ For information on variables in Logic Developer - PC, choose “Variable support in Logic
Developer - PC”.
■
For information on variables in Logic Developer - PLC, choose “Variables in Logic
Developer - PLC vs. Memory in GE Fanuc PLCs: an Overview”.
■
For information on variables in Motion Developer, choose “Variable support in Motion
Developer”.
■ For information on importing variables from other applications or database files, choose
one of the “Importing Variables...” topics.
To r un a sa mp le pr oject
1. Run Machine Edition from the Start menu | Programs | GE Fanuc | Proficy Machine Edition.
2. In the Manager tab of the Navigator, double-click one of the sample applications listed under the
My Computer folder.
Sample applications include
■ Alarm Trends: an HMI application that demonstrates alarms and charts.
■
Animation Features: an HMI application that depicts the various types of
animation available in View.
■
Brewery: an HMI and logic brewery application that runs on a Windows NT
target.
■ Car Wash: an HMI and logic application that runs on a Windows NT target.
This application is built in an SFC document.
■
ControlStation HMI Features: an HMI and logic application that runs on a
Windows NT target. This application also shows some web documents.
■
FC2000 Brewery: an HMI and logic brewery application that runs on a
ControlStation/ViewStation CE. (Projects containing a logic component cannot
be downloaded to a ViewStation, as ViewStation CEs do not support logic.)
■ FC2000 Zone Control: an HMI and logic application that runs on a
ControlStation/ViewStation CE. This application runs a four-zone ventilation
logic system. It is to be used with the ControlStation/ViewStation CE Tutorial.
(Since ViewStation CE targets do not support logic, projects with a logic
component cannot be downloaded to a ViewStation.)
■
ST - Lunar Lander: an HMI and logic application that runs on a Windows NT
target. This project demonstrates the Structured Text (ST) language and its
interaction with UDFBs (User Defined Function Blocks).
Tutorials include
■
Animation: an HMI application that illustrates and provides details on the
various animations that you can use in your HMI.
■
AppExec: an HMI application that demonstrates the AppExec Script function.
■
Keystrokes: an HMI application that displays the analog values associated with
the keys on your keyboard.
■
Logging: an HMI application that demonstrates how to log production data to
an ASCII text file.
■
Recipes: an HMI application that shows how one would load and modify
recipes.
■
Scripting: an HMI application that demonstrates some of View Developer’s
scripting capabilities.
3. Browse through the project in Machine Edition.
Open the project’s graphical panels, ladder logic, and SFCs (if they exist) in their
respective editors. To open an editor, right-click the appropriate node in the
Project tab of the Navigator and choose Open.
Also, take a look at the properties of the various nodes and objects. To view an
object’s properties, open the Inspector window, and then select an object.
4. In the newly opened project, press F9 to validate, download, and run the sample application.
The F9 key is a shortcut for the Run command which automatically starts View
Runtime and the Controller.
The sample application should now be running in both View Runtime and the
Controller. View Runtime appears, displaying the first panel of the project’s HMI.
You can see the real-time status of the logic by going online to the Controller. For
information about going online to the Controller, see “To go online to the
Controller” on page 27.
T o g o o n li n e t o the C o n tr o ll er
If you have chosen a project that contains logic and/or an SFC document, you can
go online to the application and watch the logic being executed.
1. Minimize the Runtime window (but don’t close it) and return to Machine Edition.
2. In the Project tab of the Navigator, right-click the Target node and choose Go Online.
You are now online to the Controller (that is, you are working with the application
while it is running). The Controller is the part of the Runtime that solves logic and
SFCs.
3. In the Project tab of the Navigator, open the Ladder Editor by double-clicking the Ladder Program node or
open the SFC Editor by double-clicking the SFC node.
In the editor, you can watch the logic being solved as the Controller operates. You
can start and stop Runtime and the Controller by right-clicking the target,
pointing to Online Commands, and selecting Start/Stop Runtimes from the
submenu. To go offline from the Controller, right-click the target and choose Go
Offline.
To c r ea te and develop a pr oj ec t
The following procedure introduces the general steps involved in creating a project
using a template, and downloading a project to a target computer.
1. Start Machine Edition from the Start menu | Programs | GE Fanuc | Proficy Machine Edition.
2. Create a project using a template.
In the Manager tab of the Navigator, right-click My Computer and choose
New. The New Project dialog box appears.
If you’re using shared projects, you can also add new projects under the Shared
Projects folder. Or, if you are working on a Manager system, you can add new
projects to the Machine Edition folder under the Server.
3. In the New Project dialog box, type a name for the new project, select a template, and click OK.
A description of the template appears below your selection. You can click
hypertext links in the description for details on the template components.
At this point, you need to know the type of target hardware to which your project
will download, as this will determine which template you choose. In some project
templates (such as the “View/Control” template), you can select this as one of
several parameters within an HTML page on the template dialog box.
The project is opened in Machine Edition and the Navigator changes to reflect
those components that make up the project you just created.
Want to know more? In the Help Index, look up templates and choose “Creating a New
Machine Edition Project” or “Creating a new project under a Change
Management system”.
With View, create the graphical panels and animation for your project. If the
template you chose did not include an HMI component, then add one now—right-
click the target, point to Add Component, and choose HMI. (If a target has both an
HMI and a Logic component, you’ll typically create the Logic component first.)
■
In the Project tab of the Navigator, open the Panel Editor by double-clicking
a panel node.
■
Use the Graphical Panel toolbar to create your HMI and/or drag graphical
objects from the Toolchest onto a panel. You can find a set of fully-configured
objects (complete with animation) in various Toolchest Expert Objects drawers.
With Motion Developer, begin by running the Motion Expert wizard.
■ If necessary, open the “Main Wizard” home page by right-clicking the target
and choosing Main Wizard.
■
In the wizard page, click Motion Expert and follow the instructions on screen.
For more information on using wizards, see page 100.
6. If necessary, configure the I/O hardware connections for your project.
■
For Logic Developer - PC, set up Control I/O in the Control I/O Drivers
folder (in the Project tab of the Navigator). To add a driver, right-click the
Control I/O Drivers folder and choose New Driver. Use the Control I/O tool to
configure your drivers. Map variables to I/O terminals.
Want to know more? In the Help Index, look up “Control I/O Tool: an Overview”.
■ For View, set up PLC Access I/O in the PLC Access Drivers folder. To add a
driver, right-click the PLC Access Drivers folder and choose New Driver.
Configure the drivers in the Inspector window. On NT targets, you might want
to set up OPC I/O in the OPC Client folder.
7. When your project is complete; validate, download, and run your project by pressing the F9 function key.
Machine Edition saves the project, performs a validation, builds the run-time files,
and attempts to establish a connection to the target computer.
When fixing project errors, use the F4 function key to scroll through errors in the
Feedback Zone, jumping to their locations in the project.
The download process involves two steps. The first step creates (or “builds”) all the
run-time files necessary for a target to perform its role in a completed project. The
second downloads those files to the target devices or computers.
■
For Motion Developer, the easiest way to set up the motion control device for
downloading is with the Set Communication Parameters wizard. Open the
Main Wizard page for the target (right-click the target and select Main Wizard).
Then, point to Target Configuration and select Communication Parameters.
Click Finish when you’re done.
■
To download a View or Logic Developer - PC project to the Windows NT
computer on which you are developing (a local target), ensure that the target
property Computer Address is set to “.” (without the quotation marks).
Otherwise—for remote targets—type the IP address or computer name of the
remote computer you want to download to, in the Computer Address property.
■ To download a QuickPanel project, ensure that the target property Computer
Download Port is set to the applicable COM port.
Additional basic information on setting up Windows NT and CE targets follows.
4. Within your Machine Edition project, specify the IP address or computer name of the remote NT target in the
Computer Address target property. This enables Machine Edition to locate and connect to the NT target computer.
Want to know more? In the Help Index, look up “Preparing Windows NT targets for
downloading”.
network server using DHCP. If you want to use a fixed IP address, you must
manually set the IP address on the Windows CE unit.
Want to know more? In the Help Index, look up “Preparing CE and QuickPanel View/Control
targets for downloading”.
Before you can use Quick Test, your project must have been downloaded at least
once to the target computer. If you want to Quick Test a graphical panel from a
Windows CE unit (or a QuickPanel View/Control) project, you must set the target’s
Use Simulator property to True and perform at least one download after changing
the setting.
PROJECTS
You can create and edit Machine Edition* projects by using products such as View,
Logic Developer - PC, Motion, Logic Developer - State, and Logic Developer -
PLC*. These products share Machine Edition tools to provide a high level of
integration between the various parts of your project.
You can import folders created with Logicmaster, Control, or VersaPro.
With Logic Developer - PLC*, you can build multiple projects to suit your specific
requirements.
T o cre a t e a n e w p roj e ct u si n g a te m p l at e
Before creating a project, there are some things you should know:
■
The primary components your project will contain.
■
The GE Fanuc Controller your project will run on.
1. From the File menu, choose New Project, or click on the File toolbar.
The New Project dialog box appears.
T o ope n a n e x i s ti ng p r oje ct f or e d i ti ng
1. Open the Navigator and select the Manager tab.
A list of projects appears.
2. Do one of the following:
■
Right-click a project and choose Open.
- or -
■ Double-click a project.
Your project loads and is ready for editing.
To import a fold er
1. Open the Navigator and select the Project tab.
2. Select the target that you want to import the folder into.
3. Right-click the target, point to Import, and choose the folder type.
4. In the dialog box that appears, navigate to and double-click the folder you want to import.
Want to know more? In the online help index, look up “importing Control folders”, “importing
Logicmaster folders”, or “importing VersaPro folders”.
TOOLS
Project development is supported by the Machine Edition* tools. Each tool is
opened by means of a button on the Tools toolbar.
A description of each tool’s function is provided below.
Navigator InfoViewer
Feedback Zone Companion
Inspector Toolchest
Data Watch
Nav igat o r The Navigator is a docking tool window containing a set of tabs. Each tab displays
information about your development system in a hierarchical tree structure similar
to Windows Explorer. The available tabs depend on which Machine Edition
products you have installed and what kind of work you are developing or
managing. The Project tab shows the overall organization of your application.
F eedback Zon e The Feedback Zone window is a docking window used to display several types of
output information generated by Machine Edition components. This interactive
window uses category tabs to organize the output generated from the Machine
Edition products you have installed.
I ns pe ct or The Inspector lists the properties and current settings for a selected object or
element. You can edit these properties directly in the Inspector. When you select
several objects, the Inspector window lists the properties common to all of them.
The Inspector window provides a simple method of viewing and setting properties
for all Machine Edition objects.
D at a Wat ch The Data Watch tool is a run-time debugging tool that enables you to monitor and
edit the values of variables. This tool is useful while working online to a target.
With the Data Watch tool, you can monitor individual variables or user-defined
lists of variables. Data Watch lists can be imported, exported, or saved with a
project.
T o olch e st The Toolchest is a powerful storehouse of objects you can add to your project. You
can drag most items directly from the Toolchest into Machine Edition editors. You
can choose from predefined objects or create your own reusable fxClasses. The
Toolchest adds true object-oriented capability to Machine Edition.
The Companion provides useful tips and information while you work. While the
C ompan ion
Companion is open, it tracks your moves and displays help on whatever item is
currently selected in the Machine Edition* environment. It is context-sensitive and
displays a description of whatever you click in Machine Edition.
I nfo Viewer The InfoViewer is an embedded Web browser used mainly to display the
following:
■
Machine Edition help.
■
Machine Edition reports.
■ The documentation associated with a project or target.
If you are familiar with Internet Explorer or Netscape Navigator, then you are
already familiar with the basic InfoViewer interface. Like the Companion, the
InfoViewer is context-sensitive. Press F1 to get help on any item you select in the
Machine Edition environment.
A table of contents is found in the InfoView tab of the Navigator.
Want to know more? In the online help index, look up “Tools: an Overview”.
VARIABLES
A variable is a named storage space for data. That is, the variable name represents
a memory location in the target Controller. The way in which the variable
represents a memory location is determined by the value of the variable’s Ref
Address property. A variable's Ref Address property can be set to any of the
following:
■ A reference address, for example, %R00001. This is the GE Fanuc Controller
memory location that contains the variable's value. This can be an I/O register
or an internal memory register on the Controller.
■
A blank. On a PACSystems*, if you leave a variable's Ref Address property
blank, the variable is a symbolic variable. Machine Edition* handles the
mapping for you in a special portion of PACSystems* user memory space. On
Series 90* and VersaMax* Controllers, you cannot leave the Ref Address
property blank.
■
An I/O variable address, for example %IX0.6.0.1. (PACSystems* only.) This
Navigator: Variables tab. This tab
displays all the variables used in a represents the PACSystems* Hardware Configuration terminal that contains an
project. I/O variable's value. For example, this can be a physical discrete or analog I/O
point on a module or Genius device, a discrete or analog status returned by the
module, or global data.
■ A name. This makes the current variable an alias variable of the name, that is, a
variable that points to the same memory location as the name. The following
names may be valid:
✐ The name of a parameterized LD block parameter (provided the alias
variable is local to the same block)
✐ The name and index of an array element, for example,
MyComplexArray[255,3]
✐ The name of a structure element, for example, MyStructure.MyElement
✐ The name of another variable that is not used as an alias variable.
Want to know more? In the online help index, look up “Reference Address (GE Fanuc
Controllers)”, “Symbolic Variables”, “I/O Variables”, and ”Alias Variables”.
T o cre at e a v ariab le
1. In the Variables tab of the Navigator, right-click Variable List, point to New Variable and then
choose the data type of the variable.
The New Variable dialog box appears.
Variable names can range from 1 through 32 characters, begin with a letter or the
$ character, contain upper or lower case letters, use numbers between zero and
nine, and use the underscore character (“_”).
3. Select the target the variable will be used in.
4. If the new variable is an array, select the Array check box and enter the size(s).
5. Click OK.
Want to know more? In the online help index, look up “Bit references in non-BOOL
variables”.
OPTIONS
The Options tab of the Navigator contains option and preference settings. Options
are organized into folders and pages. Click or to expand or collapse folders.
Examples:
Controller > General > Duplicate Addresses: Indicates whether to prevent,
warn about, or ignore mapping two variables of the same data size (1, 8, 16, 32, or
64 bits) and length (array size) to the same reference address.
Controller > Hardware Configuration > New Reference Assignment: The
way in which default reference addresses are assigned when modules are added to
the Hardware Configuration.
Editors > Ladder > View > Coil Justification: The default column in
which coils are placed; also the column where the right power rail resides. The
Navigator: Options tab
default is 10.
Machine Edition > Preferences > Visual Style: The visual style used for the
Machine Edition* environment, including the appearance of toolbars, tool
windows, and menus. You can choose from several visual styles based on different
versions of Microsoft products and the Windows operating system: Classic (based
on Windows 2000), XP, 2003, and 2005.
Companion Help
The Companion is a Machine Edition help system that provides useful tips and
information while you work. While the Companion is open, it displays help on
whatever item is currently selected in the Machine Edition environment.
To use Co mp anio n he l p
1. Ensure that the Companion is open. To open it, press Shift+F11.
2. Click any item in Machine Edition, outside the Companion.
InfoViewer Help
The InfoViewer, another Machine Edition* help system, provides detailed
information. The InfoViewer has the following features:
■ its own toolbar for navigating the help system
■
a Table of Contents (in the InfoView tab of the Navigator)
■
an index
■ a full-text search engine.
InfoViewer help is context-sensitive. Click an item on the screen and press F1 to
display the appropriate topic in the InfoViewer.
T o use t he He lp i n d e x
1. From the Help menu, choose Index.
2. Enter a keyword in the top text box or select one in the middle text box.
3. Click List Topics.
A list of topics appears in the bottom text box. The topics are sorted by their rating
or likelihood of containing the correct information.
4. In the bottom text box, select a topic to display.
5. Click Display.
2. Enter a search word or phrase in the top text box. SURROUND A PHRASE WITH QUOTATION MARKS.
3. Click to perform a boolean search; that is, use AND, OR, NEAR, or NOT to create a boolean search expression.
4. Click List Topics.
A list of topics appears in the Select topic box. The topics are sorted by their rating
or likelihood of containing the search term, terms, or phrase.
5. In the Select topic box, select a topic to display.
6. Click Display.
Tips:
■ To narrow the search results, click the Location heading. The listed topics are
sorted by location and then by rating.
■
When using the HTML Help Viewer window, you may get better results if you
select the “Search titles only” check box and/or clear the “Match similar words”
check box.
T o loo k up t op i c s i n t he He lp T a b l e of C ont e n t s
1. Click the InfoView tab of the Navigator.
A table of contents for the entire help system appears.
2. Expand Libraries and Books to locate a topic of interest
3. Double-click a topic.
The topic is displayed in the InfoViewer.
Adding Targets
Typically a target is present in a project when you use a template to create the
project (see page 14). A project can contain multiple targets. Before grouping
targets into a project or isolating each target in its own project, consider the
following:
■
How large are the targets? For example, a target that contains 200,000 variables
should probably be by itself in a project.
■
Are the targets related? For example, a PACSystems* with a relatively small
program is connected to twenty GE Fanuc Remote I/Os (RIOs). Size is not an
issue because RIO targets use little memory in a project. Grouping all the
targets into one project is appealing because it makes navigation much easier
from one target to another than if the PACSystems target and RIOs are isolated
in 21 separate projects. For another example, if you have various targets that do
not communicate with one another or do not serve a common purpose, there
may be little value in grouping them in one project.
One target is required for each Controller or remote I/O adapter your project
accesses, except when you are using CPU redundancy. In this case, one target
contains a Primary Hardware Configuration and a Secondary Hardware
Configuration, which correspond to the primary Controller and the redundancy
Controller, respectively. For more information, see page 61.
Existing targets can be converted from one Controller family to another. For more
information, see page 32.
Other properties are available depending on the value of the Family property and
the CPU model.
To c on figu re a C on tr oll e r t ar ge t
1. In the Project tab of the Navigator, right-click a target and choose Properties.
The properties of the target appear in the Inspector.
2. In the Inspector, configure the properties as needed.
Converting Targets
With Logic Developer - PLC*, you can convert targets from one GE Fanuc
Controller family type to another. For example, you can take the Hardware
Configuration and logic written for a Series 90*-70 Controller and convert them for
use on a PACSystems* RX7i. However, target conversions are irreversible; when
logic blocks are deleted during a conversion, they cannot be restored. It is
recommended that you make a backup of your project before converting a target.
There may also be logic execution differences when converting an application
from one GE Fanuc Controller family type to another, especially if a Series 90*-70
is involved in the conversion. You must validate the application execution prior to
deployment into a production environment.
T o con ve rt a t a r ge t
1. In the Project tab of the Navigator, right-click a target and choose Properties.
The Inspector displays the target’s properties.
2. In the Inspector, click Family.
3. From the list, choose the new GE Fanuc Controller Family you want to convert the target to.
CONFIGURING COMMUNICATION
For Logic Developer - PLC* to communicate with a target Controller, a connection
must be properly configured. The properties of a target are adjustable to
accommodate your connection(s).
2. In the MAC Address field, specify the MAC address for the target.
3. In the IP Address to Set field, specify the temporary IP address you want to set on the target.
4. If required, select the Network Interface Selection check box and specify the network interface the target is located
on.
5. Click the Set IP button.
Want to know more? In the online help index, look up “Configuring communications with GE
Fanuc Controller targets” and “Set Temporary IP Address utility”.
3. Choose the Communications tab and select the communications module you want to add.
4. Click OK.
The Parameter editor displays the configuration settings for the module.
5. In the Settings tab, double-click the IP Address parameter.
T o se t a n I P a d d r e ss f o r a S e r i e s 9 0 *- 3 0 C PU 3 6 4 , CP U3 7 4 , N IU 0 0 4, or a V er sa M a x * CP UE 05
Note: An Ethernet adapter is built into CPU364, CPU374, NIU004, and CPUE05.
For other Series 90*-30 CPUs, Ethernet connections are supported through an
optional expansion slot on the rack.
1. Obtain an IP address, perhaps from your network administrator.
2. In the Project tab of the Navigator, expand the Hardware Configuration and expand the main rack.
3. Right-click the slot containing the CPU364, CPU374, NIU004, or CPUE05 and choose Configure.
T o se t a n I P a d d r e ss f o r o t he r S er ie s 9 0 *-3 0 CP Us ( no t CP U 3 64 or C PU 3 7 4 )
1. In the Project tab of the Navigator, expand the Hardware Configuration.
2. Right-click the slot containing an Ethernet Interface Module (IC693CMM321) and choose Configure.
The Parameter editor displays the configuration settings for the module.
3. In the Settings tab, double-click the IP Address field.
The IP address is assigned to the Controller and the rest of the Hardware
Configuration is downloaded to the Controller.
7. Right-click the target and choose Go Offline.
8. Right-click the target and choose Properties.
9. In the Physical Port property, select Ethernet.
The next time you go online, Machine Edition* will use an Ethernet connection
with the specified IP address.
Validating a Target
Validating your target detects syntax and configuration errors on the target. Error
messages are generated for each error and displayed in the Feedback Zone. A
target containing errors cannot be downloaded. A target is automatically validated
before a download operation.
change any values on the Controller. Depending on your level access on the
Controller and your Change Management permission levels, you can upload from
the Controller.
When online in programmer mode, you can make changes on your computer and
the Controller and can monitor the Controller while it is executing. You can edit
any type of Controller logic on your computer. Depending on your level access on
the Controller and your Change Management permission levels, you can upload
from the Controller, control the Controller while it is executing, and change values
on the Controller, including downloading to the Controller. When editing LD logic
while online, you can make word-for-word changes (see page 91); on PACSystems,
you can also use the test edit feature (see page 90).
When online in either mode, if the project stored on the Controller is equal to the
current project in Logic Developer - PLC*, the LD editor displays a graphical
representation of LD logic as it executes.
Want to know more? In the online help index, look up “Offline (Logic Developer - PLC*)”.
Note: When online to a GE Fanuc Controller, the target icon in the Project tab of
the Navigator appears as (equal), (not equal), or (stop faulted).
Upload/Download
The download process builds and validates all run-time files necessary for a target
to perform its role in a completed project. The compiled project is then transferred
to the target hardware over the communication connection previously configured.
For more information, see page 34.
The upload process acquires a project from the active GE Fanuc Controller target
and transfers it to Logic Developer - PLC* for editing.
Note: If the Controller is running, you can download only logic that is not equal to
the Controller’s current logic and the Download to Controller dialog box does not
appear. On a PACSystems*, some source files that do not affect equality are also
downloaded.
3. Choose the items you want to download and click OK.
Note: Only one project can be downloaded to a target at a time. If you download
to a target Controller that already has a project on it, the existing project is
overwritten.
For each target that you download, Machine Edition* performs a validation. Any
errors that occur are displayed in the Build tab of the Feedback Zone. If there
are no errors, Machine Edition* builds and sends all the necessary run-time files to
the Controller.
Want to know more? In the online help index, look up “downloading to GE Fanuc
Controllers”.
The selected items are uploaded to Logic Developer - PLC*. If you already had a
version of the project open, the uploaded project merges with the existing project.
Because variable names are not stored on Series 90* or VersaMax* Controllers, if
you upload to an empty target, all variables are assigned default names. For
example, %R00001 is named R00001.
Want to know more? In the online help index, look up “uploading from GE Fanuc
Controllers”.
Run/Stop
When you are online in programmer mode, you can set a target GE Fanuc
Controller to Run or Stop mode. In Stop mode, you can choose to enable or
disable the outputs.
T o st op a GE F an uc Co nt ro lle r
1. Do one of the following:
■ In the Project tab of the Navigator, right-click a target, point to
Online Commands, and choose Stop Controller.
- or -
■
Click on the Online toolbar:
The Stop Controller dialog box appears, prompting you to enable or disable the
Controller’s outputs.
2. Select an option.
3. Click OK.
Fault Tables
The Controller and I/O Fault Tables display fault information logged by the CPU or
modules in the Controller. This information is used to determine if there are
problems with the Controller hardware or software running in the Controller’s
CPU.
T o vie w t h e f a u lt ta b le r e p ort s
• Do one of the following:
■
In the Project tab of the Navigator, double-click the target you want a
fault table report on, or right-click it and choose Diagnostics.
- or -
■
In the status bar, at the bottom of the Machine Edition* window, double-click
the target.
Note: To view the Controller and I/O fault tables, your computer must be online to
the Controller. To clear faults, you must be in online programmer mode.
(When in online
programmer mode
only.) Clear fault
information by clicking
here.
Want to know more? In the online help index, look up “fault” (in lower case), then select
“Working with the Fault Tables”.
T o cre a t e a u se r- de f i n ed R e f e re nc e V i e w T a b l e
• In the Project tab of the Navigator, right-click the Reference View Tables folder and choose New.
A new Reference View Table with a default name is added to the folder.
T o wor k wi th a u se r- de f i n e d R e f e re n ce V i ew Tab le
1. In the Project tab of the Navigator, expand the Reference View Tables folder and double-click the
table you want to view.
The Reference View Table appears in the main Machine Edition* window.
2. Add reference addresses to the table as required.
Want to know more? In the online help index, look up “RVT”, then select “Working with user-
defined Reference View Tables” or “Working with default Reference View Tables”.
Reports
Reports provide summaries and tables of information about your project. Most
reports are displayed in the InfoViewer (see page 23). The Reports tab of the
Feedback Zone contains a list of all reports generated since the last Machine
Edition* project was opened. The following are types of reports and logic printouts
available in Logic Developer - PLC*:
T o ge ne r ate re po rt s
• In the Project tab of the Navigator, right-click a node and choose Report to generate a report on that
node.
A report is automatically generated and displayed in the InfoViewer.
Note: To generate a Forces in Controller report for a target, you must be online to
the target. Right-click the target and choose Report. In the Select a Report dialog
box, select Forces in Controller Report and click OK.
To prin t LD Bloc ks
1. In the Project tab of the Navigator, expand the Logic node.
2. Right-click the Program Blocks node and choose Print LD Blocks.
The Print dialog box appears.
3. Select the blocks to print.
■
To print all of the target's LD blocks in alphabetical order, select the All option.
■ To print only some of the target's LD blocks, select the Selection option, then
select the check box in front of each block you want to print. To determine in
which order to print the blocks, select them one at a time and click Up or Down
until the selected blocks appear in the desired order.
4. Select options as required and click OK.
T o prin t S T bl ock s
1. In the Project tab of the Navigator, expand the Logic node.
2. Right-click the Program Blocks node and choose Report of ST Blocks.
The Structured Text Blocks logic printout is automatically generated and displayed
in the InfoViewer.
Want to know more? In the online help index, look up “Reports” and “printing ST logic”.
PACSYSTEMS* RX7I
The PACSystems* RX7i is pictured below.
Power Supply
Rack
CPU
I/O Modules
The PACSystems* RX7i consists of a main rack and up to seven expansion racks.
The PACSystems* RX7i supports a few types of main racks. It supports five types of
Series 90*-70 expansion racks. All main racks and expansion racks support a few
non-intelligent Series 90*-70 fan kits.
The PACSystems* RX7i main racks have 10 or 18 single-width VME slots. Slot 0
supports one of the power supply modules. Slots 1 and 2 are used to house a
double-width CPU. PACSystems* RX7i supports a few CPU models. Each
PACSystems* RX7i CPU has an embedded Ethernet adapter. In addition to the
Ethernet adapter, up to seven IC698ETM001 Ethernet modules can be installed in a
PACSystems* RX7i main rack. An Ethernet module occupies only one slot. All of
the IC698... modules are supported only on the main rack.
PACSystems* RX7i supports most Series 90*-70 modules. Most Series 90*-70
modules are double-width, that is, they occupy two slots on the main rack, but
they occupy only one slot on a Series 90*-70 expansion rack. You can plug
double-width modules into any two adjacent slots of the main rack except slots 0,
1, or 2. Because slot 17 is a double-width slot, any module in slot 17 occupies
only slot 17. Slot 17 can also accept a single-width module.
PACSystems* RX7i supports the following Series 90*-70 bus expansion modules:
■
IC697BEM711
■ IC687BEM713
■
IC697BEM713
PACSystems* RX7i also supports Series 90*-70 Genius Bus Controllers, which
support numerous Genius devices.
PACSYSTEMS* RX3I
The PACSystems* RX3i, pictured below, is the newest family of GE Fanuc
Controllers. The PACSystems* RX3i is an upward compatible upgrade for Series
90*-30 Controllers, offering more memory, faster clock speed, and an enhanced
backplane bus.
Rack
Power Supply
The PACSystems* RX3i consists of a main rack and up to seven expansion racks.
Six types of Series 90*-30 expansion racks are supported; they have IC693CHSnnn
catalog numbers and are colored black, in keeping with the Series 90*-30 color
scheme. Two expansion racks have IC694CHSnnn catalog numbers. These are
identical to the IC693CHSnnn expansion racks of the same numbers except that
they are colored blue, in keeping with the PACSystems* RX3i color scheme.
The main rack and all expansion racks support most Series 90*-30 modules; these
have IC693NNNnnn catalog numbers and are colored black, in keeping with the
Series 90*-30 color scheme. Almost all of the IC693NNNnnn modules supported
by PACSystems* RX3i also come as IC694NNNnnn modules that have identical
functionality. The only difference is that the IC694NNNnnn modules are colored
blue, in keeping with the PACSystems* RX3i color scheme. For example, the
IC693DSM314 and IC694DSM314 are functionally identical and both can be used
interchangeably in a Series 90*-30 rack system or a PACSystems* RX3i rack
system. The only hardware difference is their color.
When you configure a PACSystems* RX3i rack system, you can select
IC693NNNnnn or IC694NNNnnn racks or modules. When you configure a Series
90*-30 rack system, however, you can select only IC693NNNnnn racks or
modules. Even if you are physically using IC694NNNnnn racks or modules,
selecting IC693NNNnnn racks or modules in Logic Developer - PLC* is adequate.
The PACSystems* RX3i default main rack, IC695CHS012, has 13 slots: Slots 0
through 12. The alternate main rack, IC695CHS016, contains 17 slots: Slots 0
through 16.
On either main rack, slot 0 is reserved for a power supply or the CPU, but the
power supply or CPU does not have to be in slot 0. The last slot is reserved for the
Serial Bus Transmitter module (IC695LRE001). The slot just before the last slot can
contain any single-width module native to PACSystems* RX3i (IC695...) except the
Serial Bus Transmitter. Any other slot can contain any single-width module native
to PACSystems* RX3i (IC695...) except the Serial Bus Transmitter, and if the next
slot is empty, they can contain any supported double-width module.
The IC695PSA040 and IC695PSA140 power supplies and the CPU are two-slot
modules. The IC695PSD040 and IC695PSD140 power supplies are one-slot
modules. PACSystems* RX3i supports many Series 90*-30 modules: each one
occupies a single slot.
The default CPU specified in the project template for a PACSystems* RX3i is the
IC695CPU310.
To replac e a CP U
1. In the Project tab of the Navigator, expand the Hardware Configuration.
All racks are revealed.
2. Expand the main rack.
3. Right-click the CPU slot and choose Replace Module.
Note: PACSystems* supports only one CPU; it can be replaced with itself to update
it to the latest catalog version, that is, the latest set of parameters supported for the
HWC right-click menu CPU in Logic Developer - PLC*.
A dialog box appears asking if you want to retain the settings from the existing
CPU.
6. Click Yes or No.
T o con f i g ure a CP U
1. In the Project tab of the Navigator, right-click a slot containing a CPU and choose Configure.
The Parameter editor displays all configurable settings for the CPU.
2. Modify the settings as required. For information on any parameter of a PACSystems* CPU, select the parameter.
Tip: To open the Companion, press SHIFT+F11 or click on the Tools toolbar (see
page 16).
To replac e a rac k
1. In the Project tab of the Navigator, right-click a rack and choose Replace Rack.
The Catalog dialog box appears listing available rack types.
HWC configuration
5. Select the fan kit you want to add and click OK.
3. In the Communications tab of the Catalog, select the Ethernet Module and click OK.
Want to know more? In the online help index, look up “configuring PACSystems* RX3i rack
system”and “Parameter editor features”.
T o mo ve a m o d ule
1. In the Project tab of the Navigator, expand the Hardware Configuration and then the rack
that contains the module.
2. Do one of the following:
■ To move the module from one target to another: press SHIFT while dragging and
dropping the module onto an appropriate empty slot.
- or -
■
To move the module within a target: drag and drop the module onto an
appropriate empty slot without pressing any keys.
You cannot move modules between different types of Controller targets, for
example from a Series 90*-30 to a PACSystems* RX7i.
The module is removed from the original slot and inserted into the empty slot.
Notes: (PACSystems*)
■ You can drag a double-width module to a main rack slot only if both the slot
and the slot after it are empty. Exceptions: The last slot on a PACSystems* RX7i
can contain a double-width module or one single-width module. The last slot
on a PACSystems* RX3i main rack can contain only an IC695LRE001.
■
Only PACSystems* RX3i supports moving a power supply or CPU module.
To copy a modu le
1. In the Project tab of the Navigator, expand the Hardware Configuration and then the rack that
contains the module.
2. Do one of the following:
■
To copy the module from one target to another: drag and drop the module onto
an appropriate empty slot without pressing any keys.
- or -
■
To copy the module within a target: press CTRL while dragging and dropping
onto an appropriate empty slot.
You cannot copy modules between different types of Controller targets, for
example from a Series 90*-30 to a PACSystems* RX7i.
A copy of the module is inserted into the empty slot.
Notes: (PACSystems*)
■
You can drag and drop a double-width module to a main rack slot only if both
the slot and the slot after it are empty. Exceptions: The last slot on a
PACSystems* RX7i can contain a double-width module or one single-width
I/O VARIABLES
An I/O variable is a variable mapped to a terminal in the Hardware Configuration
of a PACSystems*. A terminal, for example, can be one of the following:
✐
A physical I/O discrete or analog point on a PACSystems* module or on a
Genius device
✐
A discrete or analog status returned from a PACSystems* module
✐
Genius global data
Memory required to support I/O variables counts against your user memory. When
you configure the PACSystems* CPU (see page 54), select the Memory tab and set
the I/O Discrete (# of Bits) and I/O Non-Discrete (# of Words) parameters to
configure the space available for I/O variables.
If the Variable Mode property is read-only and set to False, the module doesn't
support I/O variables.
5. In the dialog box that appears, click Yes.
If you enable I/O variables for a Genius bus Controller, I/O variables are enabled
for all the Genius devices on the Genius bus.
Note: When you enable I/O variables for a module, the Hardware Configuration
and logic become coupled. This means that they must be downloaded, uploaded,
or cleared together. You cannot change or add I/O variables in Run Mode Store.
4. In the Terminals tab, right-click a terminal node that has no I/O variable mapped to it and choose Map Variable.
The Variables smart list appears.
5. In the smart list, do one of the following:
■
Enter a name that is not used elsewhere in the PACSystems* target. A new I/O
variable by that name is created and mapped to the terminal. Its Ref Address
property is set to an I/O variable address. If the terminal is discrete, the new I/O
variable’s data type is set to BOOL. If the terminal is analog, the data type is set
to INT, but you can change it to another 16-bit data type: UINT or WORD.
- or -
■
Enter the name of an existing CPU-mapped variable, symbolic variable, or alias
variable. (There are some mapping limitations.) The variable becomes an I/O
variable mapped to the terminal and its Ref Address property is changed
accordingly.
Want to know more? In the online help index, look up “I/O Variables (PACSystems*)”,
“working with I/O variables (PACSystems*)”, and “Coupled Hardware Configuration and
Logic”.
■
Basic CPU Redundancy
■
Genius Redundancy
■
CPU Redundancy Over Genius
■
Single Bus with Preferred Master (Series 90*-70 CPUs CGR772 and CGR935
only): uses a single Genius bus with one or more bus Controllers in each
Controller. The primary unit is always chosen as the active unit when the units
initially synchronize.
■
Single Bus with Floating Master (PACSystems* RX7i and Series 90*-70): uses a
single Genius bus with one or more bus Controllers in each Controller. No
switchover occurs on initial synchronization to make the primary unit the active
unit.
Navigation: Project Tab ■
Dual Bus with Floating Master (PACSystems* RX7i and Series 90*-70): uses
HWC Node
dual busses with one or more bus Controllers in each Controller. No switchover
CPU Redundancy
(PACSystems* RX7i and Series 90*-70
occurs on initial synchronization. Bus Switching Modules (BSMs) are required
only) in accordance with configuration of a dual bus network. This option provides
redundancy of both the CPU and the Genius bus.
Gen iu s Re du ndan cy
A Genius redundancy system contains duplicate components that are configured
to keep the Genius system operating properly even if one of the duplicate
components fails or is taken out of service. Genius redundancy systems can be
used in combination with PACSystems* RX7i and Series 90*-70 CPU redundancy
systems.
You can configure five types of Genius redundancy systems:
■
Genius dual bus redundancy (paired GBC internal)
■
Genius dual bus redundancy (paired GBC external)
■
Genius dual GBC redundancy (paired GBC internal)
■
Genius dual GBC redundancy (paired GBC external)
■
Genius dual bus & dual GBC redundancy
To set u p th e pr imary Ha rdwa re C on figu ratio n for h ot CP U redu ndan cy ( PA CS ystems* R X7i an d Se ri es 90* -70)
1. In the Project tab of the Navigator, expand the target for which you want to set up CPU redundancy.
2. Right-click Hardware Configuration, point to Redundancy, and choose Wizard.
The Redundancy Wizards dialog box appears, with the Set up a Primary Hardware
Configuration for CPU Redundancy option selected by default.
The wizard adds a redundancy CPU and other redundancy modules to the
configuration.
The target property, Dual HWC, is now available in the Inspector and is set to False
by default.
To add Ge n ius B us Co nt ro llers ( G BC) to you r sy stem (P A CS ystems* R X7i an d S e ries 90*- 70)
1. In the Project tab of the Navigator, expand the target for which you want to set up Genius
redundancy.
2. Right-click
Hardware Configuration, point to Redundancy, and choose Wizard.
The Redundancy Wizards dialog box appears.
3. Select Add GBCs for Genius Redundancy.
4. Click Next and follow the wizard to the end. The wizard enables you to select a Genius redundancy system and the
location of the GBC modules. You can run this wizard multiple times to configure additional pairs of redundancy
busses in the same system.
Note: When you add a Genius Bus Controller (GBC) to a PACSystems* RX7i or
Series 90*-70 rack, a new Genius bus network is automatically created and
associated with that slot and GBC module. Up to 31 Genius I/O devices (blocks)
can be connected to a GBC through its Genius bus.
T o con fig ure t he se con dar y Hardw are Con fig ur at ion ( PA CS yst e m s* R X7i an d Se ri es 90* -70)
1. In the Project tab of the Navigator, select the Hardware Configuration.
2. Right-click Hardware Configuration, point to Redundancy, and choose Mirror to Secondary Hardware
Configuration.
A secondary rack system that is a copy of the primary rack system is generated. The
target now displays two Hardware Configurations (HWCs), one labeled [Primary]
and the other, [Secondary]. The Primary HWC is bolded because it is currently
selected. The target property Dual HWC is now set to True. To select which
Controller to interact with, set the Selected HWC property, just below the Dual
HWC property.
Note: You can mirror as many times as necessary to synchronize the two HWCs
after modifying the primary HWC. Each time you mirror the primary HWC, the
secondary HWC is updated to reflect those changes.
Want to know more? In the online help index, look up “Redundancy: an Overview”.
The following picture displays some of the selections available for a PACSystems*
RX3i.
4. Click OK.
2. Configure the DSM324i or Motion Mate DSM314 by using the Parameter editor..
Want to know more? In the online help index, look up “IC693DSM314: Motion Mate
DSM314” and “IC693DSM324: DSM324i”.
REMOTE I/O
A Remote I/O Scanner resides in Slot 1 of the Series 90*-70 main rack. I/O
modules can be inserted into the other slots of the main rack and on all the slots of
the expansion racks. As such, the Remote I/O Scanner is represented by a target in
the Project tab of the Navigator, and is also represented by a module in slot 1 of the
main rack of that target.
The device is added to the bus configuration with the SBA you selected.
5. When prompted to add a new target for the Remote I/O Scanner, click Yes.
A new GE Fanuc Remote I/O target appears in your project. This target
represents the Remote I/O Scanner. In the Hardware Configuration of the new
target, the Remote I/O Scanner also appears in Slot 1 of the main rack.
6. Configure the communication with the Remote I/O Scanner target.
7. Add and configure I/O modules for the rack system of the Remote I/O Scanner target.
8. Configure the Remote I/O Scanner module’s parameters in Slot 1 of the main rack of the Remote I/O
Scanner target.
9. Set up the Remote I/O Scanner Genius device in the same SBA node.
The I/O Map of both Remote I/O Scanner configurations must match (at the
Remote I/O Scanner target level and at the Remote I/O Scanner Genius Bus device
level). Now whenever you update the I/O map on the Remote I/O Scanner, the I/O
map is automatically updated to the GBC.
10. Download the Hardware Configuration of the new GE Fanuc Series 90*-70 Remote I/O target.
11. Download the Hardware Configuration of the original GE Fanuc Controller target that contains the GBC.
Want to know more? In the online help index, look up “IC697BEM733: Remote I/O
Scanner”.
VersaMax*Remote I/O
VersaMax* remote I/O consists of a Network Interface Unit (NIU) (Ethernet, Genius
or Profibus), and one or more I/O modules. You can use Logic Developer - PLC* to
configure this hardware. Once configured, the remote I/O can be controlled by a
VersaMax Controller or a PC Controller. The differentiating factor between a
VersaMax* remote I/O and a Controller is that a remote I/O is simply an
input/output device with a communication interface. Unlike a Controller, a remote
I/O has no CPU.
With Logic Developer - PLC*, you can add racks, configure the power supply, and
configure modules in the VersaMax* Remote I/O Hardware Configuration.
Remote I/O targets are generally added to a project when you create a project from
a template. You can also add a GE Fanuc Remote I/O target to an existing project.
Note: The Series 90*-70 Genius option is a Series 90*-70 Remote I/O Scanner (see
page 69).
3. From the list, select the power supply that you want to configure for your system.
4. Click OK.
4. Select the carrier/base that you want to add to the remote I/O target.
Note: You can add a maximum of eight carrier modules to each VersaMax* rack.
5. Click OK.
3. From the Module Catalog, select the module that you want to install.
4. Click OK.
Want to know more? In the online help index, look up “Hardware Configuration”.
Each C program is a named section of executable code. The main program and
the Motion program contain blocks; that is, named sections of executable code
that can be written in various languages.
Main Program
Most GE Fanuc Controllers support only a main program. The main program
consists of a block of logic named _MAIN and optionally, one or more of the
following kinds of blocks of logic, found under the Program Blocks folder in
Navigator: Project tab
the Logic folder of a GE Fanuc Controller target:
Programs ■
Called blocks developed in various languages:
✐
Ladder Diagram (LD) Blocks
✐
Structured Text (ST) Blocks
✐
Function Block Diagram (FBD) Blocks
✐
Instruction List (IL) Blocks
✐
C Blocks
■
Called parameterized blocks (LD, ST, FBD, and/or C).
■
Interrupt blocks (LD, ST, FBD, C, and/or IL) scheduled to execute at certain time
intervals or when specific memory registers reach certain values.
■
User-defined function blocks (UDFBs) in LD, ST, and FBD, of which
independent instances with their own data structures and local memory can be
used in logic.
Want to know more? In the online help index, look up “UDFB“ then choose “User-Defined
Function Blocks (UDFBs) (PACSystems*)”.
■
Specialty function blocks, like HART utilities. Like UDFBs, you can create
independent instances of specialty functions blocks with their own instance
data (a structure variable). Unlike UDFBs, you cannot edit the logic of specialty
function blocks because they are read-only and provided to you by GE Fanuc.
Want to know more? In the online help index, look up “Specialty Function Blocks
(PACSystems*)“.
■ All GE Fanuc Controllers support LD blocks, but only certain Controller families
or models support one or more of the other kinds of blocks.
The _MAIN block can be in various languages, depending on the Controller family
or model.
You download the main program to the Controller as logic; that is, after you initiate
a download, a dialog box presents you with various Download to Controller
options and you select the Logic option. If the Logic option is not present, select
the Program option.
C Programs
Series 90*-70 CPUs firmware version 6.00 and later support either the main
program, or various C programs, or a combination of a main program and C
programs. You download these various programs to the Controller together as
logic; that is, after you initiate a download, a dialog box presents you with three
Download to RAM options and you select the Logic option.
If there is no _MAIN block, then there is no main program. In this case, you would
have only one or more C programs and possibly various standalone interrupt
blocks (LD or C). These standalone interrupt blocks do not constitute a main
program if there is no _MAIN block.
A C program can be named _MAIN only if the target contains no LD blocks.
A C program is not the same as a C block. For more information, see “C Programs”,
on page 125.
Motion Program
In addition to the main program, Series 90*-30 CPUs firmware version 10.00 and
later, as well as PACSystems* RX3i CPUs firmware version 2.80 and later, support a
Motion program for use on a DSM324i or Motion Mate DSM314 module. The
Motion program consists of:
■
CAM profiles
■ CAM blocks
■
Local Logic block
■
Motion blocks
You download the Motion program to the Controller as part of its Hardware
Configuration (HWC); that is, after you initiate a download, a dialog box presents
you with various Download to RAM options and you select the Hardware
Configuration option. If you want to download the main program at the same time,
you also select the Logic option. If neither option is present, select the Program
option to download both the Hardware Configuration and the Logic. For more
information about the Motion Program, see page 133.
Scheduling Programs
On GE Fanuc Controllers that support only one program (the main program), the
program as a whole cannot be scheduled. Every scan, logic execution begins with
the _MAIN block. You can schedule individual interrupt blocks of logic but not the
_MAIN block.
When you execute both a main program and a Motion program on a Series 90*-30
Controller with a CPU firmware version 10.00 and later, or on a PACSystems* RX3i
with a firmware version of 2.80 or later, you cannot schedule the programs
because they are executed concurrently in two different locations.
■ In the CPU, every scan, logic execution begins with the _MAIN block of the
main program.
■
In the DSM324i or Motion Mate DSM314 module, the Motion program
executes independently of CPU scan times.
■
You can schedule individual interrupt blocks of logic in the main program
(except the _MAIN block).
Series 90*-70 CPUs firmware version 6.00 and later support scheduling programs.
On targets that contain such CPUs, you can schedule any program, even the main
program. That is, logic execution of any scan does not have to begin with the
_MAIN block of the main program: you can schedule any C program to begin the
logic execution part of the scan. Within the main program, you can further
schedule individual interrupt blocks of logic (except the _MAIN block). If you have
no main program, that is, if your logic has no _MAIN block, you can still have
stand-alone interrupt blocks that you can schedule individually.
Note: If you made any entries, they are validated when you click OK. You must
correct any errors before you can click OK to close the dialog box.
Want to know more? In the online help index, look up “Programs on GE Fanuc Controllers: an
Overview”.
T o cre a t e a u se r- de f i n ed f o lde r
1. In the Project tab of the Navigator, expand the target with the main program you want to organize
and then expand the Logic folder.
2. Right-click the Program Blocks folder, point to New, and choose Folder.
A new user-defined folder appears with a default name.
3. Optionally enter a new folder name, which must be unique among the folders directly under the parent folder.
Want to know more? In the online help index, look up “organizing logic (main program of a
GE Fanuc Controller)”.
Note: With Logic Developer - PLC*, you can search for some text in an entire
target or portions thereof, which you can specify. Various options are available to
narrow a search.
Want to know more? In the online help index, look up “Global” and select the “Conducting a
Global Search” help topic.
Indirect References
The LD, ST, and FBD editors support indirect references. An indirect reference
treats the value of a variable assigned to an instruction operand as a pointer to
other data, rather than as actual data. Indirect references are sometimes referred to
as relative pointers.
Indirect references can be used only as follows:
■
With PACSystems* CPUs and Series 90*-70 CPUs.
■
In the LD, ST, and FBD editors.
■ With %R, %AI, %AQ, %P, %L, and %W memory areas.
■
On instructions that support indirect references.
Notes for PACSystems*
■ The index for an indirect reference to %W is a 32-bit DWORD value.
■
Indirect references cannot be used to address bits in 16-bit memory.
■
Indirect references are not supported on symbolic variables or I/O variables.
Possible Uses
■
To perform the same operation to many registers.
■
To avoid repetitious logic within the application program.
■ In loop situations where each register is incremented by a constant or by a
value specified until a maximum is reached.
T o assi gn an i ndi re ct r e fe re nc e
• Where a variable operand is expected, type the @ symbol, followed by a valid reference address or variable name.
The LD, ST, or FBD editor converts a reference address to a variable name or the
editor substitutes the name of a variable already mapped to the address.
Notes:
■ The actual variable name does not contain the @ symbol. The @ symbol, when
used at the start of a reference address or variable name, merely indicates that
the address or variable must be treated as an indirect reference.
■
The @ symbol can be thought of as an operator with the lowest precedence. In
other words, MyArray[2,5] becomes a reference address that is used for the
indirect reference. Another way to think of this is @(MyArray[2,5]) as opposed
to (@MyArray)[2,5].
The following are valid indirect references:
■ @R0001 (a variable name automatically created from a reference address)
■
@MyArray[2, 5] (an array reference)
■
@$MainSwitch (a universal variable)
■ @MyTimer.PV (a structure element)
LD EDITOR
The Ladder Diagram (LD) editor is used to create programs with the Ladder
Diagram programming language. LD logic graphically represents the programmed
actions performed by a Controller as it executes.
The LD editor is cell-based with rungs constructed of horizontal sequences of
instructions that are wired together. A given instruction and its operands can
occupy one or more cells.
You can work with the LD editor while offline to edit a disk copy of a project, or
while online to monitor the execution of the logic while you fine tune the project,
Navigator: Project tab for example by making word-for-word changes (see page 91).
An LD Block You can customize the appearance and behavior of the LD editor by setting
options (see page 22).
An LD block is a named section of LD Logic that is compiled and downloaded to
the Controller represented by the associated target.
T o cus to m i z e t h e L D ed i t or
1. In the Options tab of the Navigator, expand the Editors folder and then the Ladder folder.
2. Right-click a page (Confirmations, Editing, Font and Colors, or View), and choose Properties.
The configurable options appear as properties in the Inspector.
3. In the Inspector, adjust settings as required.
To create a n LD bl ock
1. In the Project tab of the Navigator, right-click Program Blocks, point to New, and then choose LD
Block.
A new LD block with a default name is created.
2. Rename the block as desired.
Drag variables to
instruction
operands to assign
them.
Right-click to Drag LD
insert an instructions
instruction. from the
Toolchest.
Use the
Inspector to
configure
Displays a
address and
list of the
length for
places the
instructions
selected
The Companion variable is
automatically used.
provides
information on
what you click.
To ins e rt an ins tr uc ti on
1. In the LD editor, right-click an empty cell and choose Place Instruction.
Note: If you attempt to place an instruction that has inputs into the first column, it
is pushed to the second column and a horizontal wire is inserted in the first
column.
To assi gn in stan ce data to a bui lt-i n fun ctio n blo ck in stan ce an d ass ign a len gth to an in stru ctio n
There are two methods.
First method
1. In the LD editor, insert a built-in function block or insert an instruction that requires a Length.
In the following example, a built-in function block instance has a length. Most
built-in function blocks do not require their instances to have a length.
Four question marks indicate that the Address property of the function block instance has not been initialized. As a
result, no instance data has been assigned to the instance.
“ 1“ is the default value of the Length
property of an instruction
Address Field
Length Field
3. In the Address property, enter a variable name or a reference address to specify the start of a memory block used
for the instance data of the function block instance.
Note: If you type a reference address, it is converted to a variable name
automatically.
4. In the Length property, enter the number of bits or 16-bit registers on which the function block instance or
instruction is to operate.
Second method
1. In the LD editor, insert a built-in function block or insert an instruction that requires a Length.
2. Double-click the function block instance or instruction or select it and press ENTER.
When you double-click a function block instance, the Function Block Properties
dialog box appears, as pictured below. When you double-click an instruction, the
Function Properties dialog box appears, in which the Address property is
unavailable.
3. In the Address property, enter a variable name or a reference address to specify the start of a memory block used
for the instance data of the function block instance.
Note: If you type a reference address, it is converted to a variable name
automatically.
4. In the Length property, enter the number of bit or 16-bit registers on which the function block instance or instruction
is to operate.
Machine Edition* checks the block for errors. Any messages or errors are displayed
in the Build tab of the Feedback Zone.
A horizontal wire was inserted in the first cell to make room for the ADD_DINT
instruction’s operands and the operands were inserted in their proper places. In the
keyboard entry, “AD“ stood for “ADD_DINT“, because ADD_DINT is the first
available instruction that begins with “AD“ in the smart list. A semicolon separates
the ADD_DINT instructions. The required horizontal wires are supplied
automatically.
Want to know more? In the online help index, look up “Keyboard Method to insert LD
instructions”.
A powerful extension of typing logic into the LD editor is the ability to write LD
logic in any text editor and copy and paste it into the LD editor, or to copy and
paste logic from the LD editor to a text editor. You can copy an entire block of LD
logic from the Navigator to any text editor, or copy sections of LD logic as text from
the LD editor to any text editor. You can then edit the logic in the text editor and
copy the edited logic back into the LD editor.
When LD logic is copied as text, a verbose format is used to make it easier to read,
but when you edit the logic as text you can use the same shorthand used in the
keyboard method of entering LD logic in the LD editor.
T o cop y t e x t i nt o t he L D e d i t or
1. In the text editor, select and copy the text representing LD logic to the Windows clipboard.
2. In the LD editor, do one of the following:
■ Select the cells that you want to overwrite.
- or -
■
Click the cell that will be at the upper left corner of the LD logic you want to
paste.
3. Right-click and choose Paste.
Existing cells in the LD editor are overwritten with the content of the Windows
clipboard.
Online status is indicated by Rung Number Power flow is indicated by bolded lines. The contacts and coils that are set to ON
the lightning bolt. become green when the Controller is active.
Online Status
is indicated
by the color
of the target A red, underlined
icon. variable indicates that it
has been forced ON.
Right-click a
variable to
force it.
Controller
Status and
sweep time
are displayed
in real-time in
the Inspector.
Feedback Zone
indicates the status of
operations like
Monitor and change values in real-time with the Data downloads.
Controller Status is indicated in the
Watch tool. status bar.
Three methods are at your disposal to make changes in your LD logic and
download the changes to an online running Controller:
■ Test Edit (PACSystems* only): see page 90.
■ Word-for-word changes: see page 91.
■ Go not equal, keep working, and download changes: see page 92.
You can also affect BOOL variables during execution. See page 92.
T o b e gin e d i ti ng i n Te s t E di t
1. In the LD editor, start modifying the logic.
The Logic Change Options dialog box appears.
2. Select Enter Test Edit Mode and click OK.
The LD editor is placed in Online Edit mode, with some visual cues to remind you
that a Test Edit session is in progress. Because Test Edit is an extension of the Run
Mode Store (RMS), only changes supported for an RMS are supported in Test Edit
mode. At any time, you can test the modified logic.
T o b e gin t e st i n g t he m od i f ie d l ogi c
1. Click anywhere inside the LD editor.
2. From the Debug menu, choose Begin Test.
The modified logic is downloaded to the PACSystems*, which then executes the
modified logic. The original block of logic is retained in PACSystems* memory as
an inactive block.
You now have three possible courses of action:
■
Cancel the test and continue editing the logic while in Test Edit mode.
■ Cancel Test Edit mode and restore the original logic in the PACSystems*.
■
Accept the changes you tested and commit them to the PACSystems*.
Word-for-Word Changes
A word-for-word is a small change in logic made while online that fits in the same
amount of memory as the original logic. For example, changing the type of contact
or coil or changing an operand is usually a word-for-word change.
Word-for-word changes can be completed online to PACSystems*, Series 90*-70,
Series 90*-30, VersaMax*, and Series 90* Micro Controllers. (VersaMax* Nano /
Micro Controllers do not support word-for-word changes.)
LD Instructions
The following is a list of all LD instructions available in Logic Developer - PLC*.
Companion help indicates which Controllers support the instructions.
Want to know more? In the online help index, look up “LD Instructions”.
Adv anc e d M at h
ACOS ATAN EXP LN_LREAL*p SIN_LREAL*p TAN
p p p p
ACOS_LREAL* ATAN_LREAL* EXP_LREAL* LN_REAL* SIN_REAL*p TAN_LREAL*p
ACOS_REAL*p ATAN_REAL*p EXP_REAL*p LOG SQRT_DINT TAN_REAL*p
ASIN COS EXPT LOG_LREAL*p SQRT_INT
p p p p
ASIN_LREAL* COS_LREAL* EXPT_LREAL* LOG_REAL* SQRT_LREAL*p
ASIN_REAL*p COS_REAL*p LN SIN SQRT_REAL
Coi ls
COIL NCCOIL NTCOIL*p PTCOIL*p SETCOIL
CONTCOIL NEGCOIL POSCOIL RESETCOIL
Con t act s
CONTCON HIALR* NCCON NOCON NTCON*p PTCON*p
FAULT* LOALR* NEGCON* NOFLT* POSCON*
Con t rol
DO_IO EXIT_FOR* MASK_IO_INTR R_TRIG* p SUS_IO* SWITCH_POS* P
DRUM F_TRIG* P PID_IND SCAN_SET_IO* p SUSP_IO_INTR
END_FOR* FOR_LOOP* PID_ISA SER SVC_REQ
An asterisk followed by the letter P (*p) indicates the instructions exclusive to PACSystems*
Controllers. An asterisk followed by “ 70“ (*70) indicates the instructions exclusive to Series 90*-
70 Controllers. A simple asterisk (*) indicates the instructions shared by PACSystems* and Series
90*-70 Controllers and exclusive to them.
Con ve r sion s
BCD4_TO_INT DEG_TO_RAD_REAL* P INT_TO_DINT* RAD_TO_DEG_REAL* P TRUNC_INT
BCD4_TO_REAL DINT_TO_BCD8* INT_TO_REAL REAL_TO_DINT UINT_TO_BCD4*
BCD4_TO_UINT* DINT_TO_INT* INT_TO_UINT* REAL_TO_INT UINT_TO_DINT*
P P P
BCD8_TO_DINT* DINT_TO_LREAL* LREAL_TO_DINT* REAL_TO_LREAL* UINT_TO_INT*
P
BCD8_TO_REAL* DINT_TO_REAL LREAL_TO_REAL* REAL_TO_UINT* UINT_TO_REAL*
DEG_TO_RAD DINT_TO_UINT* RAD_TO_DEG REAL_TO_WORD WORD_TO_REAL
P
DEG_TO_RAD_LREAL* INT_TO_BCD4 RAD_TO_DEG_LREAL* P TRUNC_DINT
Cou nt e rs
DNCTR UPCTR
Dat a Mo ve
BLK_CLR_WORD BUS_TS_BYTE* P DATA_INIT_REAL* SHFR_WORD
P
BLKMOV_DINT* BUS_TS_DWORD* DATA_INIT_UINT* SWAP_DWORD*
P
BLKMOV_DWORD* BUS_WRT_BYTE* DATA_INIT_WORD* SWAP_WORD*
BLKMOV_INT BUS_WRT_DWORD* P MOVE_BOOL VME_CFG_READ*70
BLKMOV_REAL BUS_WRT_WORD* P MOVE_DINT* VME_CFG_WRITE*70
BLKMOV_UINT* COMM_REQ MOVE_DWORD* VME_RD_BYTE* 70
BLKMOV_WORD DATA_INIT_ASCII* MOVE_INT VME_RD_WORD* 70
BUS_RD_BYTE* P DATA_INIT_COMM* MOVE_LREAL* P VME_RMW_BYTE* 70
BUS_RD_DWORD* P DATA_INIT_DINT* MOVE_REAL VME_RMW_WORD* 70
BUS_RD_WORD* P DATA_INIT_DLAN MOVE_UINT* VME_TS_BYTE* 70
BUS_RMW_BYTE* P DATA_INIT_DWORD* MOVE_WORD VME_TS_WORD* 70
BUS_RMW_DWORD* P DATA_INIT_INT* SHFR_BIT VME_WRT_BYTE* 70
BUS_RMW_WORD* P DATA_INIT_LREAL* P SHFR_DWORD* VME_WRT_WORD* 70
Data Table
ARRAY_MOVE_BOOL FIFO_WRT_WORD* SEARCH_GE_UINT* SEARCH_NE_DINT
ARRAY_MOVE_BYTE LIFO_RD_DINT* SEARCH_GE_WORD SEARCH_NE_DWORD*
ARRAY_MOVE_DINT LIFO_RD_DWORD* SEARCH_GT_BYTE SEARCH_NE_INT
ARRAY_MOVE_DWORD* LIFO_RD_INT* SEARCH_GT_DINT SEARCH_NE_UINT*
ARRAY_MOVE_INT LIFO_RD_UINT* SEARCH_GT_DWORD* SEARCH_NE_WORD
ARRAY_MOVE_UINT* LIFO_RD_WORD* SEARCH_GT_INT SORT_INT*
ARRAY_MOVE_WORD LIFO_WRT_DINT* SEARCH_GT_UINT* SORT_DINT*
ARRAY_RANGE_DINT* LIFO_WRT_DWORD* SEARCH_GT_WORD SORT_WORD*
ARRAY_RANGE_DWORD* LIFO_WRT_INT* SEARCH_LE_BYTE TBL_RD_DINT*
ARRAY_RANGE_INT* LIFO_WRT_UINT* SEARCH_LE_DINT TBL_RD_DWORD*
ARRAY_RANGE_UINT* LIFO_WRT_WORD* SEARCH_LE_DWORD* TBL_RD_INT*
ARRAY_RANGE_WORD* SEARCH_EQ_BYTE SEARCH_LE_INT TBL_RD_UINT*
FIFO_RD_DINT* SEARCH_EQ_DINT SEARCH_LE_UINT* TBL_RD_WORD*
FIFO_RD_DWORD* SEARCH_EQ_DWORD* SEARCH_LE_WORD TBL_WRT_DINT*
FIFO_RD_INT* SEARCH_EQ_INT SEARCH_LT_BYTE TBL_WRT_DWORD*
FIFO_RD_UINT* SEARCH_EQ_UINT* SEARCH_LT_DINT TBL_WRT_INT*
FIFO_RD_WORD* SEARCH_EQ_WORD SEARCH_LT_DWORD* TBL_WRT_UINT*
FIFO_WRT_DINT* SEARCH_GE_BYTE SEARCH_LT_INT TBL_WRT_WORD
FIFO_WRT_DWORD* SEARCH_GE_DINT SEARCH_LT_UINT*
FIFO_WRT_INT* SEARCH_GE_DWORD* SEARCH_LT_WORD
FIFO_WRT_UINT* SEARCH_GE_INT SEARCH_NE_BYTE
Mat h
ABS_DINT* ADD_REAL DIV_UINT* MUL_MIXED* SUB_DINT
ABS_INT* ADD_UINT* MOD_DINT MUL_REAL SUB_INT
P
ABS_LREAL* DIV_DINT MOD_INT MUL_UINT* SUB_LREAL* P
ABS_REAL* DIV_INT MOD_UINT* SCALE_DINT* P SUB_REAL
P
ADD_DINT DIV_LREAL* MUL_DINT SCALE_INT SUB_UINT*
P
ADD_INT DIV_MIXED* MUL_INT SCALE_UINIT*
ADD_LREAL* P DIV_REAL MUL_LREAL* P SCALE_WORD
Pr og ram F lo w
ARG_PRES* p END H_WIRE LABEL MCRN
CALL ENDMCR JUMP LABELN V_WIRE
COMMENT ENDMCRN JUMPN MCR
Re l ati on al
CMP_DINT* EQ_LREAL* P GE_UINT* LE_INT LT_REAL RANGE_DINT
CMP_INT* EQ_REAL GT_DINT LE_LREAL* P LT_UINT* RANGE_DWORD*
P
CMP_LREAL* EQ_UINT* GT_INT LE_REAL NE_DINT RANGE_INT
P
CMP_REAL* GE_DINT GT_LREAL* LE_UINT* NE_INT RANGE_UINT*
P
CMP_UINT* GE_INT GT_REAL LT_DINT NE_LREAL* RANGE_WORD
EQ_DINT GE_LREAL* P GT_UINT* LT_INT NE_REAL
EQ_INT GE_REAL LE_DINT LT_LREAL* P NE_UINT*
T i m e r F un ct i o n B lo ck s
OFDT_HUNDS ONDTR_HUNDS TMR_HUNDS TOF* P
OFDT_SEC* ONDTR_SEC* TMR_SEC* TON* P
OFDT_TENTHS ONDTR_TENTHS TMR_TENTHS TP* P
OFDT_THOUS ONDTR_THOUS TMR_THOUS
FBD EDITOR
The Function Block Diagram (FBD) editor is used to create logic with the Function
Block Diagram programming language. FBD is a process language. FBD logic
graphically represents the programmed actions performed by a Controller as it
executes.
The FBD editor is free form; that is, instructions and text boxes can be placed
anywhere on the FBD editor where there is empty space. Sequences of instructions
can be wired together horizontally and vertically.
You can work with the FBD editor while offline to edit a disk copy of a project, or
Navigator: Project tab you can edit an FBD block of logic online, but this causes the logic to become not
An FBD Block
equal until you download the FBD block.
You can customize the appearance and behavior of the FBD editor by setting
options (see page 22).
An FBD block is a named section of FBD Logic that is compiled and downloaded
to the Controller represented by the associated target.
T o cus to m i z e t h e F B D e d i t o r
1. In the Options tab of the Navigator, expand the Editors folder, then expand the Function Block Diagram
folder.
2. Right-click the Colors and Preferences page and choose Properties.
The configurable settings appear as properties in the Inspector.
3. In the Inspector, adjust settings as required.
Hover over a
variable to see
information related
to the variable
Use the
Inspector to edit
the number of
inputs for some
FBD instructions Displays a list of the
places the selected
variable is used or a
list of the blocks the
selected block is
called from
The Companion
automatically
provides Right-click in an
information on empty space in the
what you click FBD editor and
choose an
instruction to insert
To ins e rt an ins tr uc ti on
1. In the FBD editor, right-click an empty cell and choose Insert Instruction.
Note: Inside the rectangle of the ADD instruction, the “1“ indicates the solve order
of the instruction. Under the variable myCounter, the “1“ is the initial value of
myCounter.
Second method (outside the FBD editor)
1. In the Variables tab of the Navigator, or the Data Watch tool, select a variable.
3. When the mouse pointer appears as , release the left mouse button to assign the variable to a parameter of the
FBD instruction.
For example, the following diagram shows that you can assign a parameter to the
FBD SUBTRACT instruction at the output connection point named Q.
After you have assigned the parameter, the instruction may appear as follows:
Note: In the above diagram, “61“ is the initial value of myResult. “4“ inside the
rectangle of the FBD instruction indicates its solve order.
Want to know more? From the Help menu, select Search. Look up “solve order”. Select “FBD
Editor: an Overview“.
To assi gn a para meter abov e a n FBD ins t ruc ti on or f un ction bl ock ins t ance
The FBD Call instruction and every function block instance (an instance of a
counter, PID, timer, HART utility, or user-defined function block) require a
parameter to be assigned immediately above the instruction or instance.
1. In the FBD editor, hover with the mouse pointer immediately above an FBD Call or function block instance so that the
mouse pointer appears as .
A smart list appears. If this is an FBD Call instruction, the smart list contains a list of
all callable blocks of logic in your target. If this is an FBD function block instance,
the smart list contains a list of variables that you can choose from to assign
instance data to the function block instance. Normally you would choose or create
instance data that is not used by any other function block instance, but you can
assign the same instance data to multiple function block instances if you want.
4. In the smart list, enter or choose an existing block of logic, or enter a new variable, or enter or choose an existing
variable.
The block appears as the destination of the FBD Call or the variable is assigned as
instance data to the function block instance.
Machine Edition* checks the block for errors. Any messages or errors are displayed
in the Build tab of the Feedback Zone.
To change the number of inputs for FBD instructions (ADD, AND, MUL, OR, SUB, XOR)
1. In the FBD editor, select an ADD, AND, MUL, OR, SUB, or XOR instruction.
2. In the Inspector, select the Number of Inputs property, and then enter or choose from the list the number of inputs
you need.
3. If required, draw a wire or assign a variable or constant to the input and output parameters.
Want to know more? In the online help index, look up “FBD Block”. Click the Related Topics
button and choose “FBD Controller logic: an Overview“.
To draw a wi re
Notes:
■ At least two instructions must exist in the FBD editor.
■
You cannot draw a wire to or from a Text box.
1. In the FBD editor, hover the mouse pointer above a connection point of an FBD instruction or function block instance.
When the mouse pointer appears as , you can start a wire. See the diagram
below.
2. Hold down the left mouse button, and then drag the mouse pointer to a connection point of another FBD instruction
3. Continue to hold down the left mouse button and drag the mouse pointer to a connection point of another FBD
instruction, until the mouse pointer appears as .
This indicates that the current location is a valid end point for the wire. See the
diagram below.
The newly drawn wire appears as a solid (analog) or a dashed (discrete) line in the
FBD editor. See the diagram below.
2. Right-click a BOOL variable assigned to a connection point, for example, in the diagram above, BOOL1.
3. In the list box that appears, choose Negate. The diagram now appears as shown below.
Note: Negating a BOOL parameter while online causes logic to be not equal;
turning a BOOL parameter ON/OFF while online does not affect logic equality.
T o ne ga te an F BD w ire
(For discrete FBD wires only.)
1. If required, draw the FBD wire from a connection point that requires a BOOL variable, to a connection point that also
requires a BOOL variable.
If the wire is discrete, it appears as a dotted line .
2. Right-click the wire, and then choose Negate.
T o zoom in or zo om o ut an F BD blo ck
Note: To zoom in an FBD block display in the FBD editor makes the FBD appear
larger; to zoom out an FBD block display makes the FBD appear smaller.
1. Click anywhere in the FBD editor.
2. Do one of the following:
■
In the Inspector, expand the Diagram Settings group of properties, and then
set the zoom property.
- or -
■ To zoom out, press the “-“ key. To zoom in, press the “+“ key.
Online Status
is indicated
by the color
of the target A wire with a solid line
icon. indicates analog
Right-click a
variable to
force it.
Controller
Status and
sweep time
are
displayed
in real-
time in the Monitor and change
Inspector. values in real-time
The Companion with the Data Watch
automatically tool.
provides
information on Feedback Zone indicates
what you click. the status of the Controller. Controller Status is
indicated in the status
Note: Forcing a variable ON or OFF overrides any actions the logic may take
during runtime. That is, if a variable is forced OFF (0), but FBD logic is trying to
turn it ON (1), it stays OFF.
Want to know more? From the Help menu, select Search. Enter “Working with Variables and
FBD Logic Online“ (including the quotation marks).
Adv anc e d M at h
ABS ASIN COS EXPT LOG SQRT
ACOS ATAN EXP LN SIN TAN
Com pa riso n
CMP GE LE NE
EQ GT LT RANGE
Co nt ro l
DO_IO MASK_IO_INTR PID_ISA SCAN_SET_IO SUSP_IO_INTR
F_TRIG PID_IND R_TRIG SUS_IO SVC_REQ
Cou nt e rs
DNCTR UPCTR
Dat a Mo ve
BUS_RD BUS_RMW_WORD BUS_WRT MOV
BUS_RMW_BYTE BUS_TS_BYTE COMM_REQ
BUS_RMW_DWORD BUS_TS_WORD FANOUT
Mat h
ADD MOD NEG SUB
DIV MUL SCALE
Pr og ram F lo w
ARG_PRES CALL
T i m e r F un ct i o n B lo ck s
OFDT_HUNDS ONDTR_HUNDS TMR_HUNDS TOF
OFDT_SEC ONDTR_SEC TMR_SEC TON
OFDT_TENTHS ONDTR_TENTHS TMR_TENTHS TP
OFDT_THOUS ONDTR_THOUS TMR_THOUS
T yp e Con ve rs ion
BCD4_TO_INT DINT_TO_DWORD INT_TO_DINT REAL_TO_DINT UINT_TO_DINT
BCD4_TO_REAL DINT_TO_INT INT_TO_REAL REAL_TO_INT UINT_TO_INT
BCD4_TO_UINT DINT_TO_LREAL INT_TO_UINT REAL_TO_LREAL UINT_TO_REAL
BCD8_TO_DINT DINT_TO_REAL INT_TO_WORD REAL_TO_UINT UINT_TO_WORD
BCD8_TO_REAL DINT_TO_UINT LREAL_TO_DINT TRUNC_DINT WORD_TO_INT
DEG_TO_RAD DWORD_TO_DINT LREAL_TO_REAL TRUNC_INT WORD_TO_UINT
DINT_TO_BCD8 INT_TO_BCD4 RAD_TO_DEG UINT_TO_BCD4
IL EDITOR
Instruction List (IL) is a programming language specified by the IEC 61131-3
standard. This text language is accumulator-based and much like the assembly
languages used for programming microprocessors. The instructions executed by an
IL block modify or use an accumulator that is located in Controller memory. Two
types of accumulators are defined: one analog accumulator for numeric and
bitwise operations and eight boolean accumulators for discrete logic to support
eight levels of nested boolean expressions. The IL editor is free-form with an option
to apply a standard formatting rule. The appearance and behavior of the IL editor is
user-configurable.
Navigator: Project tab
Note: Only Series 90*-30, VersaMax* Controllers, and VersaMax* Nano/Micro
An IL Block
support IL logic.
The ending address is calculated automatically. The memory area must be %R,
%AI or %AQ.
T o cre at e a n IL blo ck
1. In the Project tab of the Navigator, right-click the Program Blocks folder, point to New, and choose IL
Block.
An empty IL block with the default name ”ILBkn” is added to the folder, where n
represents a unique number.
2. Rename the block as desired.
T o ope n a n I L b lock f or e d i t i n g
• In the Project tab of the Navigator, right-click an IL Block and choose Open.
The block opens in the IL editor.
Note: You can have multiple blocks open for editing. To navigate to another open
IL block, click the tab displaying its name at the top of the editor window.
A description of a
variable pops up when
you hover the mouse
over it.
Configure the
accumulators in the
Inspector.
The Build tab of the
Feedback Zone lists
The Companion error messages
automatically when you validate.
provides information
on what you click.
To ins e rt an ins tr uc ti on
1. In the IL editor, right-click and choose Insert Keyword.
2. Type, or choose from the list, a variable name or reference address and then press ENTER.
T o i ns e rt a n i nl ine com m e n t
1. In the IL editor, click where you want to insert an inline comment.
2. Type an apostrophe (‘) followed by comment text.
3. Press ENTER to complete the comment.
T o i ns e rt a b lo ck c om m en t
1. In the IL editor, click where you want to insert a block comment.
2. Type (* followed by comment text.
A block comment can contain any number of characters and can span multiple
lines.
3. Type *) to complete the block comment.
T o re for ma t IL lo gic
• In the IL editor, right-click and choose Beautify Source.
The entire content of the IL editor is reformatted according to the default formatting
(indentation) rules.
Target icon
changes to
indicate
status of the
Controller.
Hover the mouse
pointer over a
variable to show a
popup of its value.
Right-click a
BOOL to
change or The Feedback Zone
force its state. indicates that a
connection has been
established with the
Controller.
The
Companion Monitor and
automatically change variable
provides values in the Data
information Watch.
on what you
click. Controller Status is
indicated in the
status bar.
To mo ni to r a da ta v alue
• Click anywhere in the IL editor and hover the mouse pointer over a variable.
A tooltip appears, showing the variable’s current value. This value, however, does
not update automatically: you must move the mouse pointer away and back over
the variable to update the value.
The state of the variable in the target Controller changes when the command is
received. It remains in that state until acted on by the Controller’s logic.
IL Instructions
The following is a list of all IL instructions available in Logic Developer - PLC*.
Companion help indicates which Controllers support the instructions.
Basi c Ins t ruc ti ons
ADD GT LT OR ST_DINT XOR
AND LD_BOOL MOD ORN ST_INT XORN
ANDN LD_ENO MUL PT ST_REAL
DIV LD_INT NE R ST_WORD
EQ LDN_BOOL NOT S STN_BOOL
GE LE NT ST_BOOL SUB
Adv anc e d M at h
ACOS COS LN SQRT_DINT TAN
ASIN EXP LOG SQRT_INT
ATAN EXPT SIN SQRT_REAL
Con t rol
DO_IO DRUM PID_IND PID_ISA SER SVC_REQ
Con ve r sion s
BCD4_TO_INT DINT_TO_REAL RAD_TO_DEG REAL_TO_WORD WORD_TO_REAL
BCD4_TO_REAL INT_TO_BCD4 REAL_TO_DINT TRUNC_DINT
DEG_TO_RAD INT_TO_REAL REAL_TO_INT TRUNC_INT
Cou nt e rs
DNCTR UPCTR
An asterisk (*) indicates the instructions exclusive to VersaMax* Controllers.
Dat a Mo ve
BLK_CLR_WORD BLKMOV_REAL COMM_REQ MOVE_BOOL MOVE_REAL SHFR_BIT
BLKMOV_INT BLKMOV_WORD MOVE_INT MOVE_WORD SHFR_WORD
Data Table
ARRAY_MOVE_BOOL SEARCH_EQ_INT SEARCH_GT_DINT SEARCH_LT_BYTE SEARCH_NE_WORD
ARRAY_MOVE_BYTE SEARCH_EQ_WORD SEARCH_GT_INT SEARCH_LT_DINT
ARRAY_MOVE_DINT SEARCH_GE_BYTE SEARCH_GT_WORD SEARCH_LT_INT
ARRAY_MOVE_INT SEARCH_GE_DINT SEARCH_LE_BYTE SEARCH_LT_WORD
ARRAY_MOVE_WORD SEARCH_GE_INT SEARCH_LE_DINT SEARCH_NE_BYTE
SEARCH_EQ_BYTE SEARCH_GE_WORD SEARCH_LE_INT SEARCH_NE_DINT
SEARCH_EQ_DINT SEARCH_GT_BYTE SEARCH_LE_WORD SEARCH_NE_INT
Mat h
ADD_DINT DIV_DINT MOD_DINT MUL_DINT SCALE_WORD* SUB_REAL
ADD_INT DIV_INT MOD_INT MUL_REAL SUB_DINT
ADD_REAL DIV_REAL MUL_INT SCALE_INT* SUB_INT
Pr og ram F lo w
CAL CALCN END_MCRN JMPC MCRN RETC
CALC END JMP JMPCN RET RETCN
Re l ati on al
EQ_DINT GE_DINT GT_DINT LE_DINT LT_DINT NE_DINT RANGE_DINT
EQ_INT GE_INT GT_INT LE_INT LT_INT NE_INT RANGE_INT
EQ_REAL GE_REAL GT_REAL LE_REAL LT_REAL NE_REAL RANGE_WORD
T i m e r F un ct i o n B lo ck s
OFDT_HUNDS ONDTR_HUNDS TMR_HUNDS
OFDT_TENTHS ONDTR_TENTHS TMR_TENTHS
OFDT_THOUS ONDTR_THOUS TMR_THOUS
ST EDITOR
Structured Text logic is a programming language specified by the IEC 61131-3
standard. The Structured Text (ST) Editor is a free-form text editor for editing
Structured Text logic in the Machine Edition* environment. With the ST editor, you
can work on a disk copy of a structured text block (offline) or monitor the
execution of an ST block running in the Controller (online). You can edit an ST
block online, but this causes the logic to become not equal until you download the
ST block.
ST is a high-level language that uses various operators and functions. ST logic is
Navigator: Project tab supported by PACSystems* Controllers.
An ST Block
T o cus to m i z e t h e S T E di t or
1. In the Options tab of the Navigator, expand the Editors folder and then the Text folder.
2. Right-click a
page (Colors or Preferences), and choose Properties.
The configurable settings appear as properties in the Inspector.
3. In the Inspector, adjust the settings as required.
T o cre a t e a n ST b lo ck
1. In the Project tab of the Navigator, expand the Logic folder, right-click the Program Blocks
folder or a user-defined folder, point to New, and then choose ST block.
A new ST block with a default name is created under the Program Blocks folder or
under a user-defined folder.
2. (Optional.) Rename the block.
T o cre a t e a p a r a m e te r i z e d S T b loc k
1. Create an ST block.
2. Do one of the following:
■
In the Inspector, set parameters for the block.
- or -
■ Set the block’s Block Type property to Parameterized Block, and then optionally
schedule the parameterized block.
Notes:
■
By assigning parameters to the block, its Block Type property is automatically
changed to Parameterized Block.
■
A parameterized block cannot have both interrupt scheduling and parameters.
Want to know more? In the online help index, look up “Parameterized Block“.
A description of a
variable pops up when
you hover the mouse
pointer over it. Right-click in the ST
editor to perform
various operations.
Configure the
variables in the
Inspector.
The Build tab of
the Feedback
Zone lists error
The Companion
messages when
automatically
you validate.
provides information
on what you click.
T o i ns e rt a li ne com m e nt
1. In the ST editor, click where you want a line comment to begin.
2. Type an apostrophe (’) or // followed by comment text.
3. Press ENTER to complete the line comment. The line comment ends when a new line starts.
T o i ns e rt a b lo ck c om m en t
1. In the ST editor, click where you want a block comment to begin.
2. Type (* followed by comment text. A block comment can contain any number of characters and can span multiple
lines.
3. Type *) to complete the block comment.
T o se le ct a r ang e o f S T log ic
1. In the ST editor, click at the beginning of the range.
2. Press and hold shift and then click at the end of the range. All logic within the range is selected.
Tips:
■
You can also click and drag from the beginning of the range to the end.
■
After selecting a range of logic, you can click anywhere in it and drag it to
another area in the ST editor.
Target icon
changes to Hover the mouse
indicate pointer over a
status of the variable to see its
Controller. value in a tool tip.
Monitor variable
values in the Data
Watch. In online
Right-click a programmer mode,
BOOL to you can change the
change or values
force its state.
St a t e m e nt s
:= (Assignment) Comment Function block invocation Repeat ... until
Block call Exit Function call Return
Case For ... do If While ... do
Adv anc e d M at h
ACOS ATAN EXP LN SIN SQRT_REAL
ACOS_LREAL ATAN_LREAL EXP_LREAL LN_LREAL SIN_LREAL TAN
ACOS_REAL ATAN_REAL EXP_REAL LN_REAL SIN_REAL TAN_LREAL
ASIN COS EXPT, **, or ^ LOG SQRT_DINT TAN_REAL
ASIN_LREAL COS_LREAL EXPT_REAL LOG_LREAL SQRT_INT
ASIN_REAL COS_REAL EXPT_LREAL LOG_REAL SQRT_LREAL
Con t rol
DO_IO MASK_IO_INTR SCAN_SET_IO SUSP_IO_INTR SWITCH_POS
F_TRIG R_TRIG SUS_IO SVC_REQ
Con ve r sion s
ANGLES LREAL to DINT or REAL
BCD4 to INT, REAL, or UINT REAL to DINT, INT, LREAL, or UINT
BCD8 to DINT or REAL TRUNC_DINT, TRUNC_INT
DINT to BCD8, DWORD, INT, LREAL, REAL, or UINT UINT to BCD4, DINT, INT, REAL, or WORD
DWORD to DINT WORD to INT or UINT
INT to BCD4, DINT, REAL, UINT, or WORD
Dat a Mo ve
COMM_REQ
Pr og ram F lo w
ARG_PRES
Mat h F un ct ion s
ABS_DINT ABS_LREAL SCALE_DINT SCALE_UINT
ABS_INT ABS_REAL SCALE_INT
Re l ati on al Operators
= (Equal) >= (Greater than > (Greater than) <= (Less than or < (Less than) <>, != (Not equal)
or equal) equal)
T i m e r F un ct i o n B lo ck s
TOF TON TP
C BLOCKS
A C block is an independent section of executable code written in the C
programming language that is downloaded to and executed on the target
Controller. C blocks are created externally using GE Fanuc’s C Programming
Toolkit and then imported into a project. A C block compiled for PACSystems* has
a .gefelf extension. A C block compiled for Series 90*-70 or Series 90*-30 has a
.exe extension. C Blocks can be called as a subroutine from another block (LD, ST,
FBD, or IL) but cannot call another block.
For more information on developing C Blocks, refer to C Programmer’s Toolkit for
Series 90* Controllers (GFK-0646) and PACSystems* RX7i C Toolkit User’s Guide
Navigator: Project tab (GFK-2259).
A C Block
To import a C bloc k
1. In the Project tab of the Navigator, right-click the Program Blocks folder and choose Add C block.
The Open dialog box appears.
2. Browse to the .exe or .gefelf file you want to import and click Open.
The selected file is added to the Program Blocks folder with the same name as
the .exe or .gefelf file.
Note: You can then move the C Block to a user-defined folder.
Want to know more? In the online help index, look up “C block” and “User-Defined Folder“.
For information on the required parameters, refer to the written documentation for
the C block. The names you enter will display in the CALL instruction that calls the
C block. The names and descriptions will display in a tooltip when you hover the
mouse pointer over the CALL instruction.
Want to know more? In the online help index, enter “Parameterized” and select the “C Block”
help topic.
C PROGRAMS
Note: C programs are supported only on Series 90*-70 CPUs, firmware release
6.00 and later.
A C program is an independent section of executable code, written in C language,
that is downloaded to and executed on the associated target Controller. To develop
a C program, use GE Fanuc's C Programmer's Toolkit for Series 90* Controllers
User's Manual (GFK-0646). You then import it into a project.
A C program has access to all the % reference tables of the Controller except for
the _MAIN LD block’s %P memory and the %L memory of any other LD block. A
C program can also call any of the numerous Controller-embedded functions that
Navigator: Project Tab
are included in the C Programmer’s Toolkit.
A C Program
A C program cannot be called as a subroutine. Execution is controlled only
through scheduling. A C program cannot call a block as a subroutine.
By setting the parameters of a C program, you enable it to access memory directly.
When a C program begins to execute, it reads the data for all the parameters and
makes a copy of the data. If the C program’s execution is interrupted or time-sliced
over multiple scans, the C program, when it resumes execution, uses the copy of
the data that it made when it began to execute.
C programs can coexist with a main program and with State Logic on a Series 90*-
70 Controller. For such a target, the State Logic is compiled into a C program. This
C program is named _MAIN if there is no LD logic; however, if State Logic coexists
with LD logic, the State Logic is compiled into a C program named _STATE and
one LD block must be named _MAIN.
Se t t i n g a C p rog ram ’s p a r a m e te r s
Note: You must provide a list of all the input and output parameters that the C
program requires. The main program does not use parameters.
1. In the Project tab of the Navigator, right-click a C program and choose Properties.
The Inspector displays the C program’s properties.
2. In the Inspector, select the Parameters property and click .
The Parameters dialog box appears.
3. On the Input and Output tabs, enter up to 8 input and up to 8 output parameters. Each parameter has its own row on
the tab. For each parameter, double-click the following cells and enter the required data:
■ Name: The parameter’s name.
■ Type: The parameter’s data type.
■ Length: The length of the input or output reference.
■ Variable: The first data item associated with the parameter.
■ Description: (Optional.) The parameter’s description.
Want to know more? In the online help index, choose “C Program”.
matches the produced exchange exactly. At this point, the only thing left to do is to
map the variables of the exchange to memory on the EGD consumer, or to replace
some or all of the unmapped variables with mapped variables that already exist on
the EGD consumer.
Using the EGD Configuration Server also provides you with extra EGD validation
that is unavailable without the server.
Using the EGD Configuration Server also enables you to use EGD Signatures.
When a PACSystems* is configured to use signatures, then every scan, it compares
the signature of every consumed exchange with the signature of its corresponding
produced exchange to determine whether the configuration of the consumed
exchange matches the configuration of the produced exchange; if not, the
exchange is not consumed.
The EGD Configuration Server keeps track of which produced exchanges
published on the server are consumed by EGD devices that are connected to the
server. You can then obtain an Unconsumed Data report. You can also obtain
reports that compare the produced or consumed exchange information on your
computer with that on the server.
The EGD Configuration Server is not the authoritative source of the EGD
configuration. It does not store past versions of EGD configurations. It contains
only the latest snapshots of the EGD configurations published to it. The EGD tools
are the authoritative source, while the server simply enables the tools to share
information. It is possible to delete the server contents completely and restore
them again by using the tools in a two-step process: publish the authoritative
information from all the tools to the server, and then have each tool read the
information it needs from the server and confirm to the server that it has received
it.
Want to know more? In the online help index, look up “Ethernet Global Data in Logic
Developer - PLC*: an Overview” and “EGD Configuration Server: Integration with Logic
Developer - PLC*”.
The EMT enables the EGD configuration of devices by launching the appropriate
EGD Configuration Tool from the graphical display.
Want to know more? Refer to the online help in the EGD Management Tool.
Note: For Ethernet modules that support EGD uploads, the EGD component is
automatically added when you upload the Hardware Configuration and EGD
configuration. The EGD component is also automatically added to a target when
you import a folder that contains an Ethernet Global Data (EGD) configuration or
import a Hardware Configuration that contains an EGD configuration. In such
Navigator: After the Ethernet Global Data cases, the Consumed Exchanges and Produced Exchanges folders are
component has been added to the target
automatically populated.
T o i ns t a ll t he EG D Ma nag em e n t T oo l (EM T ) o n yo ur co mp ut e r
1. Insert the Machine Edition* 5.80 supplemental CD into your computer.
2. On the Machine Edition* 5.80 supplemental CD, navigate to the EGD Server and Tools folder.
3. Double-click the EgdManagementTool Setup.msi file.
The EGD Management Tool is installed on your computer.
To publ ish a targ et's pr odu ced ex c han ges to the EGD Co nfi gu ration Se rv er, by u sin g the Validate meth od
1. In the Project tab of the Navigator, right-click the target and choose Set as active target.
If the option is unavailable, the target has already been set as the active target.
2. Right-click the target and choose Validate.
Any errors found in the target's EGD configuration, Hardware Configuration, or
logic are listed in the Build tab of the Feedback Zone.
3. Correct any errors found and repeat step 2 of this procedure.
4. When the Build tab of the Feedback Zone displays no errors, click the Messages tab of the Feedback Zone.
If the message "EGD Produced Data published" appears, the target's produced
exchanges have been updated (published) from your computer to the EGD
Configuration Server.
To publ ish a targ et's pr odu ced ex c han ges to the EGD Co nfi gu ration Se rv er, by u sin g the Bin d an d Bui ld meth od
1. In the Project tab of the Navigator, right-click the target and choose Set as active target.
If the option is unavailable, the target has already been set as the active target.
2. Expand the target.
3. Right-click the Ethernet Global Data folder and choose Bind and Build.
Any errors found in the target's EGD configuration are listed in the Messages tab of
the Feedback Zone. Some of these errors may pertain to consumed exchanges. If
you want context-sensitive help on the errors, we recommend that you use the
Validation method instead of the Bind and Build method.
4. If errors are found pertaining to produced exchanges, correct them and repeat step 3 of this procedure.
The message "EGD Produced Data published" appears when the target's produced
exchanges have been updated (published) from your computer to the EGD
Configuration Server.
If an error is found pertaining to a consumed exchange, you typically need to
synchronize the consumed exchange.
1. If any of the following conditions is true, validate the target that contains the producer. (See “Validating a Target”,
on page 39.)
■
You have uploaded the Hardware Configuration and EGD configuration from
the producer Controller to your computer
■ You have converted the target that contains the producer
■
You have deleted the Ethernet Global Folder from the target that contains the
producer and added it again.
Validating the target that contains the producer updates the EGD Configuration
Server with the produced exchange that this consumed exchange consumes.
2. In the Project tab of the Navigator, expand the target.
3. Expand the Ethernet Global Data folder and then expand the Consumed Exchanges folder.
4. If you have changed the Local Producer ID property of the producer that the consumed exchange consumes from,
right-click the consumed exchange and choose Properties. Then, in the Inspector, set the Producer ID property on
the consumed exchange to the same value as the new Local Producer ID.
5. In the Project tab of the Navigator, right-click the consumed exchange and choose Synchronize to Server.
Want to know more? In the online help index, look up “Developing EGD systems with the
EGD Configuration Server: Possible work flow” and “Troubleshooting EGD”.
• In the Project tab of the Navigator, right-click the target, point to Add Component, and then choose
Motion.
A Motion Program node is added to your project. Included are empty
Motion Blocks, Local Logic, CAM Profiles and CAM Blocks folders.
MOTION EDITOR
Logic Developer - PLC* includes a Motion Editor, which enables you to create
Motion blocks for the DSM324i and the DSM314. This text-based editor is
configurable as to its appearance and behavior. Comments and white space are not
considered to be Motion block statements. The Motion block programming syntax
is different from Local Logic syntax (see page 137).
Motion Blocks
T o ope n a m ot i on b loc k f or e d i t i ng
1. In the Project tab of the Navigator, expand the Motion Program.
2. Expand Motion Blocks and double-click the Motion Block you want to open.
The block opens for editing in the Motion editor.
T o ins e rt a co mm an d
1. In the Motion editor, right-click and choose Insert Keyword.
Insert a Motion
command by
choosing a keyword.
Insert a Motion
variable by selecting
a variable from the
smart list.
The Companion
automatically
provides
information on
what you click.
Want to know more? In the online help index, choose “Motion Editor”.
Motion Commands
ACCEL The ACCEL statement sets the axis acceleration for subsequent moves
and remains in effect in a given block unless changed. Note: If a move
instruction is executed before ACCEL, the tag Acceleration is used.
BLOCK NUMBER Block numbers can be used as the destination of JUMP commands.
Block numbers must be unique and can be between 1 and 65535.
CAM The CAM statement starts CAM motion and specifies exit conditions.
CAM-LOAD CAM-LOAD loads a parameter register with the starting location for a
CAM slave axis.
CAM-PHASE CAM-PHASE sets the phase for CAM commands.
CALL The CALL command executes another block as a subroutine.
CMOVE The CMOVE command programs a continuous move using the specified
position and acceleration mode.
DWELL DWELL causes motion to cease for a specified time period before
processing the next command.
ENDPROG The ENDPROG statement terminates a Motion program definition.
ENDSUB The ENDSUB statement terminates a Motion subroutine definition.
JUMP Jump to a block number or a sync block within the current program or
subroutine. The jump may be unconditional or conditional based on the
status of a CTL bit.
LOAD Initializes or changes a parameter data register with a 32-bit twos-
complement integer value.
PMOVE The PMOVE command programs a positioning move using the specified
position and accelerator mode.
PROGRAM The PROGRAM statement is the first statement in a motion program. The
program statement identifies the program number (valid range: 1
through 10) and the axis configuration. Program definitions cannot nest.
SUBROUTINE The SUBROUTINE statement is the first statement in a motion
subroutine. The subroutine statement identifies the subroutine number
(valid range: 1 through 40) and the axis configuration.
SYNC BLOCK A sync block is a special case of a block number. A sync block can be
used only in multi-axis programs.
VELOC Sets the process VELOCITY used by subsequent motion program move
commands and remains in effect until changed by another VELOC
statement.
LOCAL LOGIC
A Local Logic block runs synchronously with the Motion block, but is independent
of the Controller’s CPU scan. This enables the DSM324i or DSM314 to interact
much more quickly with motion I/O signals on its faceplate connectors than would
be possible if the logic for the signals were handled in the _MAIN program running
on the Controller.
Local Logic language uses free-form, text-based circuits and contains basic
mathematical and logical constructs. The Local Logic syntax enables you to assign
a variety of logic tasks to your motion programs while working in conjunction with
Controller Logic programs and motion blocks to yield a flexible programming
environment. Because it uses straightforward, understandable syntax, it is easy to
gain proficiency with this editor.
The Local Logic programming language supports assignments, conditional
statements, arithmetic, logical, and relational statements. Local Logic provides you
with access to motion Controller data, parameters using a fixed set of variables,
Navigator: Project tab control bits, and status bits:
Local Logic ■
Parameter data - accessible from Local Logic host Controller and motion blocks.
The parameter data are similar to variables in a program.
■ CTL bits - enable the Local Logic block or host Controller to signal the motion
block to start an event.
■
Motion block numbers - the current block number can be used within the Local
Logic block or host Controller to make an action occur only during a specific
motion programming section.
Click a heading to
sort the table in
ascending order.
Click again to sort
in descending
order.
Right-click a name
to copy it to the
clipboard.
T o vie w t h e L L V T
1. In the Project tab of the Navigator, expand the Motion Program.
2. Right-click Local Logic and choose Local Logic Variable Table.
The “Which LLVT do you want?” help topic appears.
3. Select Motion Mate DSM314 or DSM324i.
The LLVT appears in the Infoviewer, displaying variables or data on each tab:
Axis 1 Variables specific to axis 1
Axis 2 Variables specific to axis 2
Axis 3 Variables specific to axis 3
Axis 4 Variables specific to axis 4
Global Global data such as module status code
CTL bits DSM general Control/Status bits
Parameter Registers DSM parameter data
A smart list appears prompting you to choose a Local Logic variable name.
2. Select a variable in the list and press ENTER.
Want to know more? In the online help index, choose “Local Logic: an Overview”.
CAM EDITOR
The Cam editor is an accessory for Logic Developer - PLC* motion programming
that provides a means to create, edit, and manage electronic Cam profiles. Each
Cam profile is a user-defined curve that specifies the response of a slave servo to a
master position index. Cam profiles are referenced by name in the parent motion
program and grouped into Cam blocks. Each block is intended for download to a
specific motion module via its Controller. The hardware components are specified
in the Hardware Configuration (HWC) of the parent target.
You can reuse a Cam profile by including it in multiple Cam blocks. To include a
Cam profile in a Cam block, see “To add an alias to a Cam block”, on page 144.
T o cre a t e a C am b l ock
1. In the Project tab of the Navigator, expand the Motion Program.
2. Right-click Cam blocks and choose New.
A new Cam block with a default name is created.
3. Rename the block as desired.
Curves of the
profile can be
Navigator adjusted and
displays Cam edited
profiles and graphically.
blocks.
Cam profile
table enables Secondary
numeric editing curves show
and curve order the velocity,
grouping. acceleration
and jerk of
Configure the Cam
profiles and profile.
blocks in the
Inspector.
The Companion
automatically
provides
information on
what you click.
To ed it a Ca m pro file
1. In the Project tab of the Navigator, expand the Motion Program.
2. Right-click Cam Profiles and double-click a Cam profile.
A graphical representation of your profile appears in the profile editor and a
numeric representation appears in the profile table.
3. Insert and move points in the profile editor or table.
4. Group points into sectors in the profile table and assign curve fit order to each sector.