LGEM5K-GR013A-EN-P_Ttlpg.

qxd

3/1/04

5:12 PM

Page 1

Getting Results Guide

Doc ID LGEM5K-GR013A-EN-P

Contacting Technical Support Telephone1-440-646-5800

Rockwell Software Technical Support Fax1-440-646-5801
World Wide Webwww.software.rockwell.com
Copyright Notice 2002-2004 Rockwell Software Inc. All rights reserved
Printed in the United States of America
This manual and any accompanying Rockwell Software products are copyrighted by Rockwell
Software Inc. Any reproduction and/or distribution without prior written consent from Rockwell
Software Inc. is strictly prohibited. Please refer to the license agreement for details.
Trademark Notices The Rockwell Software logo, RSLogix Emulate 5000, RSLogix 5000, Logix5000, RSTestStand,
RSView32, RSView ME, RSView SE, and RSLinx are trademarks of Rockwell Automation Inc.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.
Pentium is a trademark of Intel Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.
Warranty This Rockwell Software product is warranted in accord with the product license. The product's
performance will be affected by system configuration, the application being performed, operator
control and other related factors.
The product's implementation may vary among users.
This manual is as up-to-date as possible at the time of printing; however, the accompanying
software may have changed since that time. Rockwell Software reserves the right to change any
information contained in this manual or the software at anytime without prior notice.
The instructions in this manual do not claim to cover all the details or variations in the equipment,
procedure, or process described, nor to provide directions for meeting every possible contingency
during installation, operation, or maintenance.

ii

Contents
1 Installing RSLogix Emulate 5000

Process of Installing RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware and Software Requirements for RSLogix Emulate 5000 . . . . . . . . . . . . . . .
Installing RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing RSTestStand Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Assistance with RSLogix Emulate 5000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 An Overview of RSLogix Emulate 5000

1
1
2
5
8

Components of RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What RSLogix Emulate 5000 Can and Cannot do. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Floating Point Calculations and the Emulator . . . . . . . . . . . . . . . . . . . . . . . . . 11
A Brief Outline of Using RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Using the Chassis Monitor

Starting the Chassis Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigating in the Chassis Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an Emulation Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Simulated I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Chassis Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Connecting the Emulator to

RSLogix 5000

13
13
14
16
18
21
22

25

Creating a Communications Driver for the Emulator . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting a Logic Project to Use the Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring Communications in the Logic Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 Connecting the Emulator to RSView

29

Creating an OPC Topic for the Emulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating a Communications Node in an RSView Project . . . . . . . . . . . . . . . . . . . . . . 29
Adding Tags from Your Logic Project to Your RSView Project . . . . . . . . . . . . . . . 31

6 Simulating I/O

33

Configure Simulated I/O in the Logic Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

iii

CONTENTS

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Configuring Produced and Consumed Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Using RSView or RSTestStand to Simulate I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Programming Breakpoints and Tracepoints

Programming Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming Tracepoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
String Formats for Tracepoint and Breakpoint Instructions . . . . . . . . . . . . . . . . . . . .
Using Trace Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 Software Activation
About the Activation Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two Methods for Activating RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . .
Activating RSLogix Emulate 5000 after Installation. . . . . . . . . . . . . . . . . . . . . . . . . .
Protecting Your Activation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reactivating a Damaged Activation Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index

iv

37
37
39
41
43

47
47
47
49
50
50
51

53

Installing RSLogix Emulate 5000

You cannot install RSLogix Emulate 5000 on a computer that has a SoftLogix5800 controller
installed.
You must use a version of RSLogix Emulate 5000 that matches the version of RSLogix 5000
used to develop the logic project you want to emulate. For example, if you want to emulate a logic
project developed with version 12 of RSLogix 5000, you must use version 12 of RSLogix Emulate
5000.

Process of Installing RSLogix Emulate 5000

The process of installing RSLogix Emulate 5000 is as follows:
1. Install prerequisite software for RSLogix Emulate 5000. See Software Requirements
on page 2 for more information.
2. Install RSLogix Emulate 5000. See Installing RSLogix Emulate 5000 on page 2 for
more information.

Hardware and Software Requirements for RSLogix Emulate 5000

Hardware Requirements
The computer on which you are installing RSLogix Emulate 5000 must meet the
following minimum requirements.
For this component:

Use:

Personal computer

Any with an Intel Pentium Pro, Pentium II, Pentium III, or Pentium 4
CPU running at 300 MHz or higher

RAM

128 MB or more

Monitor and video card

Any capable of displaying a resolution of 800 x 600 pixels or higher

Hard drive

50 MB of available hard drive space

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Software Requirements
The following software must be installed before installing RSLogix Emulate 5000.
For this software
component:
Operating system

Install:

Notes:

Microsoft Windows XP
The emulator will not run on other
Professional Edition or Windows
versions of Windows.
XP Home editions (either one with
Service Pack 1 or higher)
- or Microsoft Windows 2000 (with
Service Pack 2 or higher)
- or Microsoft Windows NT 4.0
(with Service Pack 6a or higher)

Logix5000 programming
software

RSLogix 5000, version 12.0 or

higher

Required to program the emulator and

observe its operation.

Communication software

RSLinx, version 2.41 or higher

Required for communicating with the

emulator.

Installing RSLogix Emulate 5000

You cannot install RSLogix Emulate 5000 on a computer that has a SoftLogix5800 controller
installed.
If you are reinstalling RSLogix Emulate 5000, you must uninstall it before proceeding with the
installation.
Use the Windows Add/Remove Programs application (located in the Windows Control Panel) to
remove the emulator.

To install RSLogix Emulate 5000:

1. Log onto the computer on which you want to install the emulator as an administrator
(or a user with administrative privileges).
2. Insert the RSLogix Emulate 5000 CD-ROM into the computers CD-ROM drive. The
setup program should start automatically. If it does not, open the CD-ROM drive with
Windows Explorer and run the AUTORUN.EXE program on that drive.
3. The Setup program displays a menu of choices. Click Install RSLogix Emulate
5000.
4. The Setup program displays a welcome screen. Click Next.

5. The Setup program displays the License Agreement for the software. Read the
agreement carefully. If you choose to adhere to the terms of the agreement, click Yes.
If you do not accept the terms of the license agreement, the Setup program stops.
6. The Setup program displays the Customer Information screen. In this screen, enter
your name, the name of the company you work for, and your ten-digit software serial
number (provided with the software) in the fields provided. Click Next.
7. The Setup program asks you to choose a location for installing the software. By
default, the software is installed in the C:\Program Files\Rockwell Software\RSLogix
Emulate 5000 folder. If you want to change the location where the software will be
installed, click Browse and select a new location for the software. After choosing the
folder, click Next.
8. The Setup program asks you to choose the folder in the Start menu that will contain
the icons for the emulator. You can choose to use the default folder (Rockwell
Software), type a different folder name in the Program Folders field, or choose a
folder that already exists from the Existing Folders list.
9. The Setup program installs the software. When the software is installed, the Setup
program asks if you want an icon for the Chassis Monitor added to your Windows
desktop. The icon will give you a shortcut to starting the emulators Chassis Monitor
application. If you want an icon for the Chassis Monitor added to your desktop, click
Yes. If not, click No. (If you do not place the Chassis Monitor icon on your desktop,
you will need to access the Chassis Monitor through the Start menu.)
10. The RSLogix Emulate 5000 setup program displays a screen saying that its
installation is complete. If you want to display the release notes for the software,
check the I would like to view the README file check box. The README file
contains information concerning the software that has changed since the publication
of this book. If you have not already installed the activation for the software, check
the I would like to Move Activation to my Hard Disk check box.
11. Click Finish to end the RSLogix Emulate 5000 setup program. The setup program
ends. If you chose to view the README file in step 10, the file opens.
If you chose to move the activation file in step 10, the EVMove program starts. This
program will move the activation file from the RSLogix Emulate 5000 Master Disk
(provided with the software) to your hard drive.
The activation file is required for the proper operation of RSLogix Emulate 5000. See Chapter 8
for more information about software activation.

a. Insert your RSLogix Emulate 5000 master disk into your computers floppy disk
drive.

1 INSTALLING RSLOGIX EMULATE 5000

GETTING RESULTS WITH RSLOGIX EMULATE 5000

b. On the EvMove window, set the From Drive box to the letter for your computers
floppy disk drive (usually A:). Set the To Drive box to the letter for your
computers hard drive (usually C: or D:).
c. Click OK. The setup program displays the License Move Utility. This shows the
activation on the master disk and the activations that are already installed on your
hard disk.
1. Click the activation
you want to move
(WED32.EXE)

2. Click Move.

d. Click the activation you want to move from the master disk (WED32.EXE), then
click Move.
e. After EvMove moves the activation, it displays the Move Summary window. This
window informs you about the activations that were moved. Click OK.

Installing RSTestStand Lite

About RSTestStand Lite
RSTestStand Lite gives you a better user interface to your debugging process helping
you shorten commissioning time by having better tested logic for your Logix5000
controller.
The functions in RSTestStand Lite are a subset of the features in the full RSTestStand and
Control Planner/ Simulator products. The Lite version acts like a hardware test stand or
button panel. Op Console devices replace common hardware elements (such as push
buttons and pilot lights) that are traditionally used to test programs.
The full RSTestStand product replaces the field inputs and outputs to your PLC with a
simulation of your process. Unlike traditional hardware-based test systems, RSTestStand
can be easily and quickly configured to represent a wide variety of processes discrete
through continuous. Once configured, the system can respond automatically to different
control signals. In addition, the product provides an extensive user interface that lets you
dynamically interact with your control program through the process checking for errors
and determining system response to out-of-range conditions.
You can get information about the full RSTestStand product from the Rockwell Software
Web site (http://www.software.rockwell.com) or by contacting your local Rockwell
Automation sales office.

Installing RSTestStand Lite

To install RSTestStand Lite:
1. Log onto the computer on which you want to install the emulator as an administrator
(or a user with administrative privileges).
2. Insert the RSLogix Emulate 5000 CD-ROM into the computers CD-ROM drive. The
setup program should start automatically. If it does not, open the CD-ROM drive with
Windows Explorer and run the AUTORUN.EXE program on that drive.
3. The Setup program displays a menu of choices. Click Try Out RSTestStand.
4. The Setup program displays a welcome screen. Click Next.
5. The Setup program displays the License Agreement for the software. Read the
agreement carefully. If you choose to adhere to the terms of the agreement, click I
accept the terms of the license agreement. If you do not accept the terms of the
license agreement, click Cancel (the Setup program for RSTestStand Lite stops).
6. The Setup program displays the Customer Information screen. In this screen, enter
your name, the name of the company you work for.

1 INSTALLING RSLOGIX EMULATE 5000

GETTING RESULTS WITH RSLOGIX EMULATE 5000

This screen also asks for a serial number. Since you are installing the Lite version of
RSTestStand, there is no serial number provided with the software, but you will need
to enter a ten-digit number in the Serial Number field. (Any ten-digit number will do.)
After entering this information, click Next.
7. The Setup program asks you to choose a setup type. You can choose whether you
want the Setup program to install RSTestStand Lite to its default folder (\Program
Files\Rockwell Software\RSTestStand) or to another folder. You can also choose
whether or not you want to install certain components of RSTestStand Lite.

If you want to have all components of RSTestStand Lite installed to the default
folder, click Standard Feature Set Installation to Default Location.
If you want to choose the folder into which you want to install RSTestStand Lite
or choose the components you want to install, click Custom Location Selection
and/or Custom Feature Selection.

If you chose Custom Location Selection and/or Custom Feature Selection:

a. Click Next. The Setup program displays the Custom Setup screen.

b. By default, all the components of RSTestStand Lite will be installed. Select the
components you do not want to install, and then click This feature will not be
available. (You cannot deselect the RSTestStand Lite component.)
To deselect a
component, click the
icon for the
component and then
click This feature
will not be
available.
(You cannot
deselect the
RSTestStand Lite
component.)

To change the folder into which you want to

install RSTestStand Lite, click Change.

c. To change the folder into which you want to install RSTestStand Lite, click
Change. The Setup program displays a window that will allow you to select an
existing folder or create a new folder. Select the folder you want to use, then click
OK.
4. Click Next. The Setup program displays a window saying it is ready to install the
software.
5. Click Install. The Setup program installs the software. When the software is
installed, the Setup program displays a window saying the InstallShield Wizard is
complete.
6. Click Finish. The Setup program closes.

1 INSTALLING RSLOGIX EMULATE 5000

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Getting Assistance with RSLogix Emulate 5000

Online Help
You can access the online help for RSLogix Emulate 5000 through the Chassis Monitor.
Open the Chassis Monitor and click Help > Help Topics.

Rockwell Automation Technical Support

You can contact Rockwell Automation Technical Support by telephone, fax, or by e-mail.
BY PHONE
To contact Rockwell Automation Technical Support by phone, call 440.646.5800.
BY FAX
To contact Rockwell Automation Technical Support by fax, dial 440.646.5801.
BY E-MAIL
To contact Rockwell Automation Technical Support by e-mail, send your message to
racleasktheexpert@ra.rockwell.com

Support Information on the World Wide Web

To obtain support information from Rockwell Automations World Wide Web site, go to
http://support.rockwellautomation.com.

An Overview of RSLogix Emulate 5000

RSLogix Emulate 5000 is a software product that emulates the behavior of Logix5000
processors. The emulator allows you to experiment with and debug your Logix5000
programs in a safe, controlled environment without investing in physical controllers and
I/O modules. Additionally, RSLogix Emulate 5000 allows you to test your HMI
applications without using a real controller.
Logix5000 processors include: ControlLogix, CompactLogix, FlexLogix, SoftLogix, and
DriveLogix controllers. For more information about the Logix5000 family of controllers, see the
Allen-Bradley Web site (http://www.ab.com) or contact your local Rockwell Automation sales
office.

Components of RSLogix Emulate 5000

There are two components of RSLogix Emulate 5000:

The Chassis Monitor, which is a software application that allows you to configure
emulation and simulated I/O modules
Emulation modules, which are Windows services that simulate the behavior of
Logix5000 processors and certain I/O modules

Emulation modules run as Windows services, which are applications that run without
interfaces of their own. The Chassis Monitor serves as an interface to the emulation
modules, allowing you to create and configure instances of the modules.

What RSLogix Emulate 5000 Can and Cannot do

RSLogix Emulate 5000 simulates most of the behaviors of Logix5000 processors. There
are exceptions, and you should keep those exceptions in mind as you use the emulator.
The following table shows the differences between Logix5000 processors and RSLogix
Emulate 5000.

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Features:

Logix5000 Processor

RSLogix Emulate 5000

Breakpoints and tracepoints

Not supported

Supporteda

Control real I/O

Supported

Not supported

Forcing

Supported

Supported

Interface to non-Rockwell
Software HMI software

DDE/OPC (requires RSLinx

DDE/OPC (requires RSLinx
Professional, Single Node, OEM, or Professional, Single Node, OEM, or
Gateway)
Gateway)

Programming languages

Ladder diagram, function block,

sequential function chart, and
structured text

Ladder diagram, function block,

sequential function chart, and
structured text

Messaging

Supported

Supported (local only)

Motion instructions

Supported

Supported (virtual axes only)

Jump to external routines (JXR Supportedb

instructions)

Not supported

Communications through
RS232 ports

Supported

Supported

Communications with RSView Supported

Supported

Time scaling

Not supported

Supported

Single Scan Mode

Not supported

Supported

Network cards

Yes

Remote programming only

Task priority levels

16

Trending

Yes

Yes

Online editing of sequential

function chart and structured

Yes

Yes

text programsc
a.Supported only in ladder diagram programming.
b.Supported only in SoftLogix5800 controllers.
c.Supported only in version 13.

Program execution times in RSLogix Emulate 5000 will be different from the times you can
expect in a Logix5000 processor. Execution times will also vary depending on how many other
applications (including other emulation and I/O simulation modules) are running at the same
time as the emulator. Do not depend on execution time in the emulator as a guide to how
fast a physical Logix5000 processor will execute the same program!

10

About Floating Point Calculations and the Emulator

For maximum portability across platforms, avoid mixed operand types between
destinations their inputs. If getting identical results for similar operations across languages
is important to you, make sure to perform floating point operations. However, floating
point operations execute somewhat more slowly than integer operations. There are also
other considerations, such as how compatible your operands are with that of the I/O being
used, and so on. See below for more details on typed operations across Logix platforms
and across languages.
Because RSLogix Emulate 5000 is based on open systems technology, the controller
performs computational operations much the same way as open systems platforms and
tools do it. This becomes important when performing mixed typed operations such as
dividing two integers and storing the result in a real.
Integer operations typically truncate the rational portion of a computation result while
floating point operations preserve it. For example, when a RSLogix Emulate 5000
program performs "a = n / m" where the data types for "a", "n", and "m" are real, integer,
and integer respectively, this specifies an integer divide between "n" and "m" and places
the answer into "a", performing an integer to real conversion. If "n" = 800 and "m" =
1000, the result is 0 and gets stored into "a" as 0.0.
When a ControlLogix program performs the same "a = n / m" where the data types for
"a", "n", and "m" are real, integer, and integer respectively, this specifies a floating point
divide between "n" and "m" and places the answer into "a", with no conversion needed. If
"n" = 800 and "m" = 1000, the result is 0.8 and gets stored into "a" as 0.8. In RSLogix
Emulate 5000, the input operand types dictate the operation while in ControlLogix, if any
of the operands are real, a floating point operation is performed. RSLogix Emulate 5000
performs the operation exactly like a C routine would.

Typed operations across languages

There are instruction differences across programming languages as well as across Logix
platforms. The following examples use the operation "i = n / m" where all the operands
are integers. Ladder DIV instructions perform an integer divide operation and store the
immediate result in the destination. For "n" = 800 and "m" = 1000, "i" is equal to 0. The
DIV function block instructions only does floating point operation. The function block
instruction converts the inputs to reals (if necessary) and then converts the result from a
real to the destination type is (if necessary). In this example, "n" is converted to 800.0 and
"m" is converted to 1000.0. The result of the operation is 0.8. That result then gets
converted to an integer where rounding rules apply and the final destination value is 1.
This difference between ladder and function block instructions applies to all Logix
platforms. Function block instructions only perform floating point operations.

11

2 AN OVERVIEW OF RSLOGIX EMULATE 5000

GETTING RESULTS WITH RSLOGIX EMULATE 5000

A Brief Outline of Using RSLogix Emulate 5000

Typically, RSLogix Emulate 5000 is used to check logic (or the logic behind HMI
systems, etc.) before that logic is put into physical controllers. Heres a brief outline of
how you can implement RSLogix Emulate 5000 in your project development.
1. In RSLogix 5000, create a new project using the Emulator processor type.
2. Set up the projects I/O configuration to match that of the Chassis Monitor,
configuring I/O simulation modules or additional emulator modules to emulate your
application.
3. Develop the logic program for your application, configuring it to run on the emulator.
Use symbolic tags for your I/O points and alias them to simulated I/O modules or
other emulators (using produced and consumed tags). You can also use tags in
RSTestStand or RSView to simulate I/O.
4. Download your program to the emulator and debug it using the tools in RSLogix
5000.
5. After verifying your programs operation with the emulator, save a copy of your
project for reference.
6. In RSLogix 5000, change the processor type of your project to use the physical
processor that will run your application. Reconfigure your projects I/O to use the
modules for your application.
7. Re-alias the I/O points in your project to use the I/O modules for your application.
8. Remove any tracepoint and breakpoint instructions you may have used in the project
(these will not work in a physical processor).
9. Verify your project and correct any errors. You can then download your project to
your physical controller.

12

Using the Chassis Monitor

The Chassis Monitor is a software application used to configure RSLogix Emulate 5000
and I/O simulation modules.
You must use a version of RSLogix Emulate 5000 that matches the version of RSLogix 5000
used to develop the logic project you want to emulate. For example, if you want to emulate a logic
project developed with version 12 of RSLogix 5000, you must use version 12 of RSLogix Emulate
5000.

Starting the Chassis Monitor

There are three methods for starting the Chassis Monitor. You can launch the Chassis
Monitor from the Windows Start menu, you can click the Chassis Monitor icon on the
Windows desktop (if you chose to place it there during installation), or you can launch the
Chassis Monitor from the Windows System Tray.
For version 13 of RSLogix 5000 Emulate: Unlike the SoftLogix 5800 controller, RSLogix Emulate
5000 stops and starts with the Chassis Monitor. RSLogix Emulate 5000 does not run when the
Chassis Monitor is not running.
For version 12 of RSLogix 5000 Emulate: The emulator starts and stops like a SoftLogix 5800
controller, operating as a Windows service.

Starting the Chassis Monitor from the Start Menu

To start the Chassis Monitor, click Start > Programs > Rockwell Software > RSLogix
Emulate 5000 > RSLogix Emulate 5000 Chassis Monitor.

Starting the Chassis Monitor from the Windows Desktop

If you chose to place an icon for the Chassis Monitor on the Windows Desktop, you can
start the Chassis Monitor by double-clicking the icon. The icon looks like this:

13

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Starting the Chassis Monitor from the System Tray

If the Chassis Monitor is running, you can click the Chassis Monitor icon located in the
Windows System Tray. (The System Tray is located on the Windows Taskbar. By
default, the System Tray is in the lower right corner of your computers screen.)
This is the
Chassis Monitor
icon in the
Windows System
Tray.

System Tray Icon Status Indicators

The System Tray icon indicates the state of the emulators in the Chassis Monitor.
This icon:

Means:
Normal operation. No faults.

(Red triangle, white

exclamation point)

Major emulator fault. One or more emulators in the Chassis Monitor

has faulted.

(Yellow triangle, black

exclamation point)

Minor emulator fault. I/O not responding.

For version 13 of RSLogix 5000 Emulate: Unlike the SoftLogix 5800 controller, RSLogix Emulate
5000 stops and starts with the Chassis Monitor. RSLogix Emulate 5000 does not run when the
Chassis Monitor is not running.
For version 12 of RSLogix 5000 Emulate: The emulator starts and stops like a SoftLogix 5800
controller, operating as a Windows service.

Navigating in the Chassis Monitor

The Chassis Monitor is where you can create and configure RSLogix Emulate 5000
emulation modules and simulated I/O modules. Modules reside in the Chassis Monitors
slots, much as they would reside in a physical chassis.
Menus available at the top of the Chassis Monitor window and from right-clicking slots
and modules allows you to configure your chassis with the modules you need.

14

The RSLinx module represents a communication module for the chassis. This module
cannot be removed or moved to another slot.
The following illustration shows a Chassis Monitor window with three emulator and three
simulated I/O modules.
This is a simulated I/O module.
You can click on the module's
terminal cover to open it.
The red box surrounding this
module indicates it is selected.
You can right-click modules to
display a configuration menu.

This is an
emulator module.

The RSLinx
module in slot 0
cannot be
removed.

This button allows you to

contract the Chassis Monitor into
a smaller display. This smaller
display hides slots 9 through 16.
These "slots" hold emulator or
simulated I/O modules. Click Slot
> Create Module to create a
module.

15

3 USING THE CHASSIS MONITOR

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Creating an Emulation Module

You can have up to 16 emulation modules in the Chassis Monitor at one time. However, your
computers performance may be impaired significantly if you run multiple emulation modules
simultaneously.

To create an emulation module:

1. Click Slot > Create Module.
2. From the Module Type field, choose the type of module you want to create. Choose
Emulator RSLogix Emulate 5000 Controller.
3. In the Slot field, enter the slot where you want the emulator to reside. The emulator
can be in any slot (except for slot 0).
If you modify the project to use a physical Logix5000 processor, make sure your rack and slot
configurations in your project match those in your control system. Otherwise, you may not be
able to communicate properly with the physical controller, the physical controller may fault, or
your control program may have unexpected results.

4. Click OK to accept your changes and add the emulator to the virtual chassis.
You can click Cancel if you wish to cancel creating the emulator.
5. If you have previously created a emulator module in the same slot and you did not
delete the configuration for the module when you removed it, the software tells you
there is previous configuration information for the module. The software asks
whether you want to use the previous configuration, or reset the configuration to
default values.
a. To use the previous configuration, click Use the Configuration from the
Previous Controller. To reset the configuration, click Reset the Configuration
to Default Values. (Even if you reset the configuration to its default values, the
name of the emulator remains the same as the one that was deleted.)
b. If there was a program in the deleted emulator module, the software shows the
controller name and the date the program was last downloaded into the controller.
If you want to load this program into the emulator module you are creating, check
the Load Saved Controller Image from Previous Instance check box.
Using a previously loaded controller image may result in unexpected operation. Make sure the
program is correct before running your emulations.

c. Click Next to continue.

16

4. A configuration wizard appears to allow you to enter module-specific properties. The

first screen of the wizard allows you to enter general properties for the emulator.
For this:

Select or type:

Startup mode

The mode in which you want the emulator to start when it first
launches. It can start either in Remote Program mode or in whatever
mode it was in when the emulator service is stopped (when the
computer was shut down or the emulator was stopped manually).

Memory size

The memory size for the emulator. Make this equal to the memory size
of the controller you are emulating.

Periodic Save Interval

Specify whether you want to save the current controller information

(program, data, and configuration information) periodically, and if so,
specify how often (minutes). The default is enabled for 10 minutes.

5. Click Next. The software displays a window for setting additional features of the
emulator.
For this:

Select or type:

Continuous Task Dwell Time

Specify the timeslice (0-1000 ms) made available for all other
Windows applications. The default is 10 ms.
The dwell time is the time between the end of the continuous task and
the start of the next execution of the continuous task.

CPU Affinity

If you are running the emulator on a computer that has more than one
CPU, set the CPU that you want to run the emulator (the emulator can
run on only one CPU).

Channel 0 Serial Port

If you want to emulate serial communications with a Logix5000

processor, set the computer serial port that you want to use to emulate
Channel 0 of the Logix5000 processor.

6. Click Finish. The Chassis Monitor places an emulator module in the slot you
selected.
If you right click on the virtual chassis on the slot where you wish to create your module, and
then choose Create, the slot number is automatically filled in for you.

17

3 USING THE CHASSIS MONITOR

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Configuring the Emulator

Configuring the emulator is done through the Chassis Monitor.

Display the Emulator Configuration

To display the configuration for an emulator:
1. Open the Chassis Monitor.
2. Right-click the emulator module for which you want to display the configuration, then
click Configure Emulation. The Configure Emulation window opens. This window
is illustrated below.
These controls
allow you to
control the
"speed of time"

These controls
allow you to
configure trace
displays

This control
allows you to log
traces to a file

Active traces
appear in this list

18

Set the Speed of Time

The speed of time setting allows you to slow down program execution in the emulator.
When you slow the speed of time, timers slow down, and additional time is added to the
program scan time, allowing you more time to observe program execution as it happens.
The speed of time is set as a percentage of real time. When the speed of time is set to
100%, program execution is in real time. Setting the speed of time to another value slows
program execution by an amount proportional to the percentage you select. For example,
setting the speed of time to 60 percent makes actions that normally take one second take
around 1.67 seconds.
Changes to the speed of time setting take effect as soon as they are set.
To set the speed of time:
1. Open the Chassis Monitor.
2. Right-click the emulator module for which you want to display the configuration, then
click Configure Emulation. The Configure Emulation window opens.
3. Set the speed of time using the controls displayed in the window. The illustration
below shows how the controls work.
Use the slider to adjust
the speed of time in one
percent increments
Click this to stop
program execution
immediately

This field shows

the last value set
for the speed of
time

Click this to set

the speed of
time to 100%
immediately

You can also

type the
percentage in
this field
If you use the slider or
type a percentage, click
this button to confirm
the change

19

3 USING THE CHASSIS MONITOR

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Configure Trace Displays

When tracepoint and breakpoint instructions execute, the emulator opens a trace display.
To set a trace, program a tracepoint or breakpoint instruction. See Programming
Breakpoints and Tracepoints on page 37 for information about programming these
instructions.
To configure how the emulator handles and displays these traces:
1. Open the Chassis Monitor.
2. Right-click the emulator module for which you want to display the configuration, then
click Configure Emulation. The Configure Emulation window opens.
3. Refer to the following table for the settings.
This setting:

Does this:

Ignore If No Value Changed

This button toggles whether the trace displays should record every
trace or only those traces where there are changes to the value being
traced. If the button is indented, the trace displays will ignore those
traces where the value does not change.

TimeStamp

Set this to record how you want time recorded in traces.

None records no time information in the trace displays.
Delta records the difference between the current trace and the last
trace.
Absolute records the time that the trace triggered. The time is in the
number of milliseconds since the computer running the emulator was
last rebooted.

20

Display all new traces

Check this box if you want all new traces to display automatically in a
trace window.

Log new traces to disk

Check this box if you want new traces to automatically log to disk.

Display All Traces

Click this button to display all of the current traces in their trace
windows. (The current traces are listed by name in the Configure
Emulation window.)

Close All Traces

Click this button to close all of the open trace windows.

Remove All Traces

Click this button to remove all of the current traces from the trace list.

Close Log File

Click this button to stop logging traces to a file.

Trace Log File

This field shows the currently set log file. To set the log file, click
Browse. For more information, see Log Traces to Disk on page 21.

Log Traces to Disk

You can configure the emulator to log traces to a text file. To do this:
1. Display the emulator configuration.
2. Check the Log new traces to disk check box.
3. Click the Browse button.
4. Select the text file you want to hold trace information. If you want to create a new
file, type the name of the new file in the File name field.
You can log data to a file with any extension (or with no extension at all). However, to be able to
view traces with a text editor (such as Windows Notepad), use a TXT file extension.

5. Click Open. If the file you selected already has data in it, the software asks if you
want to append your traces to the end of the file, overwrite the data in the file with the
traces, or cancel.
6. Execute your logic. When a TPT instruction executes, the trace information is logged
to the file you selected.
7. When you are ready to view the traces stored in the log file, display the emulator
configuration, then click Close Log File. You can then open the log file in a text
editor (such as Windows Notepad).
If you try to open the log file without closing it in the emulator configuration, you will see an error
message saying that the file cannot be accessed. You must close the log file in the emulator
before it can be viewed by another application.

Creating Simulated I/O

You can use a 1789-SIM module to simulate discrete I/O with the emulator. (This is the
only form of I/O you can simulate with the emulator.) This module resides in the Chassis
Monitor and provides sixteen inputs and outputs that you can use in logic programs.
To create a SIM module in the Chassis Monitor:
1. In the Chassis Monitor, click Slot > Create Module. The software displays the Select
Module window.
2. In the Select Module window, select the 1789-SIM 32 Point Input/Output
Simulator from the Module Type list. Set the Slot field to the slot number into which
you want to place the SIM module. Click OK. The software displays the Select
Device window.
3. The Select Device window displays the device serial number (actually the slot
number for the module).

21

3 USING THE CHASSIS MONITOR

GETTING RESULTS WITH RSLOGIX EMULATE 5000

a. If you deleted a SIM module from this slot without clearing its configuration, the
software displays a message saying that previous configuration information exists
for the module. You can retain the previous configuration, or you can reset the
configuration to default values. To retain the previous configuration, click Use
the Previous Configuration. To reset the module to its default values, click
Reset the Configuration to Default Values.
b. Click Next.
3. The software displays the General window. In this window, you can label the SIM
module with a text string that will scroll across the face of the module to help you
identify it while it is in the Chassis Monitor. Type the name for the module in the
Label for 1789-SIM Module Marquee field. (If you do not type a name, the
software uses the words Simulator Module.)

Using Produced and Consumed Tags

Another method for simulating I/O is to use another emulator module to produce and
consume tags. See Configuring Produced and Consumed Tags on page 34 for information
about configuring these tags.

Configuring the Chassis Monitor

You can configure the behavior and display of the Chassis Monitor. The following table
shows how to configure the Chassis Monitor.
To set the Chassis Monitor to:

Click this menu option:

Hide slots 9-16 (if you are not using those slots or you
View > Hide Slots 9-16
simply want the Chassis Monitor to take up less space onscreen)
Hide the computer name

View > Compact

Change the rate at which the module display updates

Options > Auto Refresh Rate > (High,

Normal, or Low)

Keep the Chassis Monitor on top of other windows when Options > Always On Top
it is displayed
Set the Chassis Monitor to start in a minimized state (the Options > Start Minimized
window is not opened immediately and the application is
available from the Windows Taskbar)
Remove the Chassis Monitor from the Windows Taskbar Options > Hide When Minimized
when you minimize its window (the Chassis Monitor icon
remains in the System Tray)

22

To set the Chassis Monitor to:

Click this menu option:

When you delete a module, automatically check the Clear Options > Clear Configuration on Remove
Chassis Monitor module configuration check box.
(If this feature is not set, the software does not
automatically check that box for you.)

23

3 USING THE CHASSIS MONITOR

GETTING RESULTS WITH RSLOGIX EMULATE 5000

24

Connecting the Emulator to

RSLogix 5000
Connecting RSLogix Emulate 5000 to RSLogix 5000 requires making some changes to
your logic project.
1. In RSLinx, create a driver for the emulator.
2. In RSLogix 5000, set your logic project to use the emulator.
3. Configure communications in the logic project to use the emulator driver.
4. Add the simulated I/O to your logic project.
5. Program breakpoint and tracepoint instructions.

Creating a Communications Driver for the Emulator

In RSLinx, you need to create a communications driver for RSLogix Emulate 5000. This
driver will allow other applications to communicate with the emulator.
To create the communication driver:
1. In RSLinx, click Communications > Configure Drivers. The Configure Drivers
window appears.
2. Select the Virtual Backplane (SoftLogix 58xx) driver from the Available Driver
Types list.
3. Click Add New. The Add New RSLinx Driver window appears. This window allows
you to name the driver. You can keep the default name, or type a name of up to 15
characters. Click OK.
4. The new driver appears in the Configured Drivers list. Click Close.

25

GETTING RESULTS WITH RSLOGIX EMULATE 5000

1.

Select the Virtual

Backplane (SoftLogix
58xx) communications
driver

2. Click Add New.

3. Click Close.

Setting a Logic Project to Use the Emulator

Before you can emulate a logic project, you must configure the project's processor type to
use the emulator. To do this:
1. In RSLogix 5000, open the project that you want to emulate.
2. Click Edit > Controller Properties. The Controller Properties window opens.
3. On the General tab of the Controller Properties window, set the Slot field to
correspond with the slot in the Chassis Monitor containing the emulator you want to
use to emulate the project.
4. Click Change Type. The Change Controller Type window opens.

26

1. Click Change Type.

2. Select RSLogix
Emulate 5000
Controller.

2. Click OK.

5. From the To list, select Emulator RSLogix Emulate 5000 Emulator.

6. Click OK.

Configuring Communications in the Logic Project

Before you can download to or go online with the emulator, you must configure
communications in your logic project. To do this:
1. In RSLogix 5000, open the project you want to emulate.
2. Click Communications > Who Active. The Who Active window opens.
3. The Who Active window displays a tree of the available network nodes using the
communication drivers you have configured in RSLinx. In the tree, click the emulator
you want to use for this project.
4. Click Set Project Path. This sets the communication path to use the emulator.

27

4 CONNECTING THE EMULATOR TO RSLOGIX 5000

GETTING RESULTS WITH RSLOGIX EMULATE 5000

28

Connecting the Emulator to RSView

RSLogix Emulate 5000 uses OLE for Process Control (OPC) to communicate with
RSView. Connecting the emulator to an RSView project requires creating an OPC topic
in RSLinx, then creating a communications node and tags in the RSView project that uses
the OPC topic.
Please see the documentation for RSView for more information.

Creating an OPC Topic for the Emulator

To create an OPC topic for the emulator:
1. Open the Chassis Monitor, and make sure your emulator is running.
2. In RSLinx, open an RSWho window (click Communications > RSWho). The
emulator should be visible in the RSWho window. If it is not, make sure there is a
communication driver for the emulator. See Creating a Communications Driver for
the Emulator on page 25 for more information.
3. In the RSWho window, right-click the emulator, then click Configure New DDE/
OPC Topic. This creates a new OPC topic, and displays the DDE/OPC Topic
Configuration window with a new topic for the emulator.
4. Click Done. This closes the DDE/OPC Topic Configuration window and saves the
topic for your emulator.

Creating a Communications Node in an RSView Project

To create a communications node in RSView that uses the OPC topic for the emulator:
1. Open your RSView project.
2. In your projects System folder, open the Node editor. In RSView, a node represents a
communications device, usually a programmable controller or another Windows
application. In the Node editor, we will create a node that represents the emulator.

29

GETTING RESULTS WITH RSLOGIX EMULATE 5000

3. Set up the Node editor window as shown in the following table.

For this field or control:

Set or enter:

Data Source

OPC Server

Name

Enter a name for the node (representing the emulator). This can be the
name of the emulator, if you like.

Enabled

Make sure this check box is checked.

Server

Click the button next to the Server Name field, choose RSLinx OPC
Server, then click OK.

Type

Select In-Process.

Access Path

Leave this blank.

Update Rate

This defaults to 1.000 seconds (one update per second). If you need a faster
or slower update rate, enter the update frequency.

2.

Enter a name
for the node.

3. Make sure the Enabled

checkbox is checked.
1. Click OPC
Server.

4. Click this button, click

RSLinx OPC Server,
then click OK.

5. Make sure In-Process

is selected.

6. Set the Update Rate to

the frequency at which
you want data to update
your RSView project.

4. Click Accept. This saves the node configuration.

30

7. Click
Accept.

Adding Tags from Your Logic Project to Your RSView Project

Once you have created an OPC node for the emulator, you can add tags from your logic
project to your RSView tag database. To do this:
1. Open your RSView project.
2. In your projects System folder, open the Tag Database editor.
3. Select the data
type for the tag.

1. Click Device.

2. Click this button and

select the OPC node
you created for the
emulator.

4. Click this button to

display the OPC
Address Browser.
5. Browse for the
address you want to
use with the tag in
this tree.

6. Select the address.

7. Click OK.

3. In the Data Source section of the Tag Database editor, click Device.

31

5 CONNECTING THE EMULATOR TO RSVIEW

GETTING RESULTS WITH RSLOGIX EMULATE 5000

4. Click the button next to the Node Name field. This displays the Node Browser. Select
the OPC node you created for the emulator and click OK.
5. In the Tag section of the Tag Database editor, select the type of tag you want to create
from the Type list.
6. In the Data Source section of the Tag Database editor, click the button next to the
Address field. This displays the OPC Address Browser.
7. In the OPC Address Browser, select the address you want to use with the tag and click
OK.
8. Finish creating the tag by filling in the fields in the Tag Database editor.
For this field or control:

Set or enter:

Name

The name of the tag you want to create.

Security

If you have set up security for your RSView project, set the security class
associated with the tag.

Description

Type a description of the tag (optional).

Minimum

The minimum value for the tag (as used in RSView).

Maximum

The maximum value for the tag (as used in RSView).

Scale

A scaling value for the tag.

Offset

A value to add to the tag.

Units

The units for the tag.

Data Type

Select the data type for the tag.

9. Click Accept. The tag is stored in the tag database. You can now use the tag in your
RSView project.

32

Simulating I/O
There are two methods of simulating I/O with RSLogix Emulate 5000. You can use a
simulated I/O module to simulate discrete I/O, or you can use another emulation module
to produce and consume tags of any type. You can use both methods simultaneously.
Additionally, you can use other software products such as RSView and RSTestStand to simulate
I/O.

Configure Simulated I/O in the Logic Project

To be able to address simulated I/O in your logic project, you must create the simulated I/
O modules in the project. These modules are created just like any other I/O modules.
To create a simulated I/O module in your RSLogix 5000 project:
1. In RSLogix 5000's Controller Organizer, right click on the I/O Configuration folder,
and click New Module. The software displays the Select Module Type window.
2. Select 1789-MODULE from the modules list, then click OK.
3. The software displays the Module Properties window. Enter the following parameters
for the module:
For this parameter:

Enter:

Name

A name for the module

Description (optional)

A description of the module and its function in the system

Comm Format

Set this to reflect the type of I/O you are simulating.

Slot

The slot in the virtual chassis that contains the module.

4. Specify the connection parameters for the module as shown in the following table.

33

GETTING RESULTS WITH RSLOGIX EMULATE 5000

For read/write connections:

For listen only connections:

Input Assembly Instance

Input Assembly Instance

Input Size

Input Size

Output Assembly Instance

Output Assembly Instance

Output Size

Output Size

Configuration Assembly Instance

16

Configuration Assembly Instance 16

Configuration Size

Configuration Size

5. Click Next. The software displays another Module Properties window.

6. Specify the Requested Packet Interval (RPI).
You must enter at least 50.0 ms for the RPI. The connection will fail if the RPI is less than 50
ms. Because this module uses the generic module profile, the default RPI is 5.0 ms. You must
change this value.

7. Click Finish.

Configuring Produced and Consumed Tags

Another method for simulating I/O for your emulated project is to produce and consume
tags from another emulation module. (See the documentation for your Logix 5000
processor for background information about produced and consumed tags.)

Configuring a Produced Tag

To configure a produced tag in the emulator:
1. Open the logic project for the emulator in RSLogix 5000. You must be offline to
perform this procedure.
2. In the logic project, open the Controller Tags folder. (Produced tags must be scoped
to the controller.)

34

3. Right-click the tag you want the emulator to produce, then click Edit Tag Properties.
This displays the Tag Properties window.
A produced tag must be one of the following data types:

DINT

REAL

an array of DINTs or REALs

user-defined

A produced tag must also be less than 500 bytes.

4. In the Tag Properties window, select the Produce tag type. Set the number of
consumers equal to the number of emulators that will consume the tag.
5. Click OK.

Configuring a Consumed Tag

Configuring an emulator to consume a tag is a two-step process. First, you must make the
emulator that is producing the tag an I/O module of the emulator that will consume the
tag. Second, you must create a consumed tag to accept the data from the producer.
MAKING

THE

PRODUCER

AN

I/O MODULE

OF THE

CONSUMER

To make the producing emulator an I/O module of the consuming emulator:

1. Open the logic project for the consuming emulator in RSLogix 5000. You must be
offline to perform this procedure.
2. In the logic project, right-click the I/O Configuration folder, then click New Module.
This displays the Select Module Type window.
3. In the Select Module Type window, select the Emulator module type (RSLogix
Emulate 5000 Emulator).
4. Click OK. This displays the Module Properties window.
5. In the Module Properties window, type the name of the producing emulator in the
Name field. Set the slot number for the producing emulator in the Slot field.
6. Click Finish. The producing emulator is now an I/O module of the consuming
emulator.
CREATING

CONSUMED TAG

To create a tag that consumes data from the producing emulator:

1. In the logic project for the consuming emulator, create a tag (scoped either to the
processor or to a program). You must be offline to perform this procedure.

35

6 SIMULATING I/O

GETTING RESULTS WITH RSLOGIX EMULATE 5000

2. Right-click the tag you want the emulator to consume, then click Edit Tag
Properties. This displays the Tag Properties window.
A consumed tag must be of the same data type (including array size) as the produced tag it
uses. If it is not, the emulator consuming the tag will experience an I/O fault.

3. In the Tag Properties window, choose the Consumed tag type.

4. Select the producing emulator from the Producer drop-down list box.
5. Type the name of the tag that the producer is producing in the Remote Tag Name
field.
6. In the RPI field, set the Requested Packet Interval (RPI) to the amount of time (in
milliseconds) you want the consuming emulator to wait between data requests for this
tag. This is the minimum rate at which the emulator will consume data.
7. In the Data Type field, enter the data type for the consuming tag. This must be the
same data type (including array sizes) as the produced tag it consumes.
8. Click OK.

Using RSView or RSTestStand to Simulate I/O

You can also simulate I/O by using other software packages, such as RSView or
RSTestStand. RSView is an HMI design and runtime environment, and RSTestStand is a
test stand simulation environment.
RSTestStand Lite, a demonstration version of the RSTestStand test stand simulation product, is
available from the RSLogix Emulate 5000 installation disk.

36

Programming Breakpoints and

Tracepoints
Breakpoint and tracepoint instructions allow you to monitor the state of your logic when it
is in conditions that you determine. Breakpoints stop program emulation when a rung is
true. Tracepoints log data you select when a rung is true.
Breakpoint and tracepoint instructions are supported only in ladder diagram programs running
in the emulator. These instructions are not supported by physical Logix5000 processors.

Programming Breakpoints
Breakpoints are programmed with the Breakpoint output instruction (BPT). When the
inputs on a rung containing a BPT instruction are true, the BPT instruction stops program
execution. The software displays a window indicating that the breakpoint triggered and
the values that triggered it.
When a breakpoint triggers, the emulator displays a window informing you that a
breakpoint occurred. The title bar of the window shows the slot containing the emulator
that encountered the breakpoint.

When you click OK, the emulator resumes program execution. If the conditions that
triggered the breakpoint have not changed, the breakpoint will trigger again.
In addition, the emulator opens a trace window for the breakpoint. Information about the
breakpoint and the values it traces are displayed in the trace window.
When a breakpoint triggers, you will not be able to edit your project until you permit execution to
continue. You can go online with the emulator to observe the state of your project, but you will
not be able to edit it. If you try to accept a rung edit while a breakpoint is triggered, you will see a
dialog box saying the controller is not in the correct mode.

37

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Programming the BPT instruction

The Breakpoint (BPT) instruction has two kinds of parameters:
This parameter: Contains:

Requires:

Format

A string that sets the formatting for the

text that appears in the trace window for
the breakpoint.

A STRING tag. See String Formats for

Tracepoint and Breakpoint Instructions on
page 41.

Trace This:

The tag that has a value you want to

display in the trace window.

An INT, BOOL, SINT, DINT or REAL tag.

You cannot trace tag structures (such as
entire timers, counters, etc.). However, you
can trace individual structure members.

You can display a large number of tag values with the BPT instruction, however, the
formatting string can contain only 82 characters. Because two characters are required in
the formatting string for each tag you want in the breakpoint, the maximum number of
tags you could trace with a single BPT instruction is 41. However, you will probably want
to include spaces and other formatting to separate tag data in your traces, so the resulting
number of tag values that can be effectively displayed by one BPT instruction is
significantly lower than 41.
EXAMPLE:
The following rung shows a breakpoint that stops program execution when an analog
value is greater than 3.02 or less than 2.01.

We want to display the breakpoint information in a particular format. That format is

contained in the Format string (myformat). In this case, the format string contains the
following text:

38

Breakpoint:The input value is %f

When the breakpoint triggers, the breakpoint trace window shows the characters before
the colon (Breakpoint) in the title bar of the trace window. The other characters make
up the traces. In this example, %f represents the first (and in this case, the only) tag to be
traced (analogvalue). (See String Formats for Tracepoint and Breakpoint Instructions
on page 41 for more information about formatting strings. The resulting traces appear as
shown in the following illustration.

Programming Tracepoints
Tracepoints are programmed with the tracepoint output instruction (TPT). When the
inputs on a rung containing a TPT instruction are true, the TPT instruction writes a trace
entry to a trace display or log file. (To configure how traces are displayed or logged, see
Configure Trace Displays on page 20.)

Programming the TPT Instruction

The tracepoint (TPT) instruction has two kinds of parameters:
This parameter: Contains:

Requires:

Format

A string that sets the formatting for the

trace reports (both on-screen and logged
to disk).

A STRING tag. SeeString Formats for

Tracepoint and Breakpoint Instructions on
page 41.

Trace This:

The tag you want to trace.

An INT, BOOL, SINT, DINT or REAL tag.

You cannot trace tag structures (such as
entire timers, counters, etc.). However, you
can trace individual structure members.

39

7 PROGRAMMING BREAKPOINTS AND TRACEPOINTS

GETTING RESULTS WITH RSLOGIX EMULATE 5000

You can trace a large number of tags with the TPT instruction, however, the formatting
string can contain only 82 characters. Because two characters are required in the
formatting string for each tag you want to trace, the maximum number of tags you could
trace with a single TPT instruction is 41. However, you will probably want to include
spaces and other formatting to separate tag data in your traces, so the resulting number of
tags that can be effectively traced by one TPT instruction is significantly lower than 41.
EXAMPLE:
The following rung triggers a trace of three analog values when any one of them exceeds
a given value (30.01).

We want to display the tracepoint information in a particular format. That format is

contained in the Format string (myformat). In this case, the format string contains the
following text:
Analog inputs trace:Analog inputs = %f, %f, and %f

When the tracepoint triggers, the characters before the colon (Analog inputs trace)
appear in the title bar of the trace window. The other characters make up the traces. In
this example, the %f characters represent the tags to be traced (analogvalue1,
analogvalue2, and analogvalue3). (See String Formats for Tracepoint and
Breakpoint Instructions on page 41 for more information about formatting strings.

40

The resulting traces appear as shown in the following illustration.

When this trace is logged to disk, the characters before the colon appear in the traces.
This indicates which tracepoint caused which trace entry. The following is an example of
a trace entry. Analog inputs trace: is the heading text from the tracepoint's format
string.
Analog inputs trace:Analog inputs = 31.00201, 30.282000, and 30.110001

String Formats for Tracepoint and Breakpoint Instructions

The Format string in the tracepoint and breakpoint instructions allows you to control how
the traced tags appear in the traces or breakpoint windows. The format of the string is as
follows:
heading:(text)%(type)

where heading is a text string identifying the tracepoint or breakpoint, text is a string
describing the tag (or any other text you choose), and %(type) indicates the format of the
tag. You need one type indicator for each tag you are tracing with the tracepoint or
breakpoint instruction.
For example, you could format a tracepoint string like this:
My tracepoint:Tag 1 = %e and Tag 2 = %d

The %e formats the first traced tag as double-precision float with an exponent, and %d
formats the second traced tag as a signed decimal integer. See the table below for more
information.

41

7 PROGRAMMING BREAKPOINTS AND TRACEPOINTS

GETTING RESULTS WITH RSLOGIX EMULATE 5000

In this case, you would have a tracepoint instruction that has two Trace This parameters
(one for a REAL and one for an INT, although the value of any tag can be formatted with
any flag).
The resulting tracepoint window that would appear when the tracepoint is triggered would
look like:
The slot number
indicates the slot
containing the
emulator module that
has the tracepoint or
breakpoint being
traced in the trace
window

The text for the REAL

(represented in the
format string as %e)
appears here

The heading (the text

before the colon in the
format string) appears
here

The text for the INT

(represented in the
format string as %d)
appears here

Types for Formatting Tag Values

The following table shows the available types for formatting tag values. Any type can be
used for formatting any tag. (The types are similar to those used by the C++ printf
function.)

42

This type:

Formats the tag value as:

Example:

%d

Signed decimal integer. REAL values are

truncated.

45.3202 is rendered as 45.

%o

Unsigned octal integer. Non-octal values are

45.3202 is rendered as 55.
converted to octal. REAL values are truncated.

This type:

Formats the tag value as:

Example:

%x

Unsigned hexadecimal integer with letters

rendered in lowercase. Non-hex values are
converted to hex. REAL values are truncated.

45.3202 is rendered as 2d.

%X

Unsigned hexadecimal integer with letters

rendered in uppercase. Non-hex values are
converted to hex. REAL values are truncated.

45.3202 is rendered as 2D.

%e

Signed floating point value with exponent. The 45.320200 is rendered as

exponent delimiter (e) is rendered in lowercase. 4.532020e+001.

%E

Signed floating point value with exponent. The 45.320200 is rendered as

exponent delimiter (E) is rendered in uppercase 4.532020E+001.

%f

Signed floating point value without exponent.

%g

Signed floating point value in %e or %f

45.320200 is rendered as 45.3202.
format, whichever results in a more compact
433222556.34322 is rendered as
display. Trailing zeros are truncated, and the
4.3323e+008.
decimal point appears only if one or more digits
follow it. The exponent delimiter (e) is rendered
in lowercase (when it is appropriate).

%G

Signed floating point value in %e or %f

45.320200 is rendered as 45.3202.
format, whichever results in a more compact
433222556.34322 is rendered as
display. Trailing zeros are truncated, and the
4.3323E+008.
decimal point appears only if one or more digits
follow it. The exponent delimiter (E) is rendered
in uppercase (when it is appropriate).

45.320200 is rendered as
45.320200.

Using Trace Windows

Opening and Closing Trace Windows
By default, tracepoint and breakpoint windows display automatically when a tracepoint or
breakpoint instruction first executes. (You can configure the emulator to not display these
windows automatically. See Configure Trace Displays on page 20 for more information
about configuring the behavior of trace displays.)
If you close a tracepoint or breakpoint window, it is still available to you. You can access
active traces through the Configure Emulation window (right-click the emulator, then
click Configure Emulation). The Configure Emulation window allows you to perform
the following operations on trace windows:

43

7 PROGRAMMING BREAKPOINTS AND TRACEPOINTS

GETTING RESULTS WITH RSLOGIX EMULATE 5000

To perform this function:

Do this:

Have traces automatically open whenever a new

tracepoint or breakpoint instruction executes.

Check the Display all new traces check box.

Open an active trace.

Double-click the trace name.

Open all active traces.

Click Display All Traces.

Close all open trace windows.

Click Close All Traces.

Remove all active traces from the trace list.

Click Remove All Traces.

Check Display all new

traces to automatically
display trace windows
when new tracepoints or
breakpoints execute
Click Display All
Traces to open all of
the active traces
Clicking Close All
Traces closes all open
trace windows
Click Remove All
Traces to remove all
active traces

Active traces
appear in this list
-- double-click a
trace to display it

44

Trace Window Controls

Trace windows have several controls that allow you to control their behavior.
This button:

Does this:

Freeze Display

Stops the trace window from updating. Use this when you want to read
values from a rapidly updating trace.

Clear Display

Clears traces from the trace window.

Freeze Log

When you are logging a trace to disk, this button stops and starts logging.
When the button is pressed, logging stops. If you are not logging the
trace to disk, this button has no effect.

Click Freeze Display to

stop the trace window
from updating

Click Clear Display to

clear the traces from
the window

Click Freeze Log to

stop logging the trace
to disk.

45

7 PROGRAMMING BREAKPOINTS AND TRACEPOINTS

GETTING RESULTS WITH RSLOGIX EMULATE 5000

46

Software Activation
Rockwell Software uses activation files to provide copy protection for its Windows-based
software packages. These activation files reside on the Activation disk. During
installation, the software prompts you to insert the Activation disk and move the
activation key from the disk to the drive where you are installing RSLogix Emulate 5000.

About the Activation Disk

RSLogix Emulate 5000 comes with a separate Activation disk that activates the software.
Without activation, the software will not run.
The activation file on the Activation disk contains:

An activation key, which is the software that activates RSLogix Emulate 5000.
Depending on your requirements, the Activation disk will have one or more activation
keys. For example, if your company purchases four RSLogix Emulate 5000
installations, the Activation disk will contain four keys. Multiple copies of the same
software require activation keys with matching serial numbers. All of the activation
keys can be on the same Activation disk.

A file called EVMOVE.EXE that moves activation keys to and from computers

A file called RESET.EXE that reactivates a damaged activation key

You can move activation keys off and on the Activation disk. The files EVMOVE.EXE
and RESET.EXE always stay on the Activation disk.

Two Methods for Activating RSLogix Emulate 5000

Depending on your needs, you can activate the software from a:

Diskette drive. Use this method if you will typically use the software on more than

one computerfor example, if you want to run the software on a desktop computer
and a portable computer.

Hard drive. Use this method if you will typically use the software on only one

computer. This is the default method if you activate the software during installation.
To run the software on a different computer, move the activation key back to the
Activation disk, and then reactivate the software.

47

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Using the Activation Disk as an Activation Key

To use the activation key from a diskette drive, modify the ROCKSOFT.INI file so that
RSLogix Emulate 5000 searches the diskette drive for the activation key. Once you
modify this file, you must use the Activation disk each time you start the software.
TO MODIFY

THE

ROCKSOFT.INI FILE

1. Install RSLogix Emulate 5000 as described in Chapter 1.

2. When the Activation window opens, click Cancel to bypass the activation procedure.
3. Locate the directory containing the ROCKSOFT.INI file (the directory where
Windows is installed, typically C:\WINNT).
4. Open the ROCKSOFT.INI file.
5. Locate the string that says: KEYDISK=FALSE. (If this string is not present, add it to
the end of the file.)
6. Edit this string so it says: KEYDISK=TRUE.
7. Save and close the ROCKSOFT.INI file.
TO ACTIVATE RSLOGIX EMULATE 5000
1. Insert the Activation disk into the diskette drive.
2. Start RSLogix Emulate 5000.
RSLogix Emulate 5000 automatically searches the diskette drive for the activation
key.
MOVING ACTIVATION KEYS BACK

TO THE

ACTIVATION DISK

You can move activation keys from the hard drive back to the Activation disk at any time.
Move activation back to the Activation disk:

to run the software on a different computer

before installing or using software that could damage the activation files (see
Protecting Your Activation Files on page 50 for a list of operations that can damage
activation)

before sending the computer to a technician

TO

MOVE ACTIVATION KEYS BACK TO THE

ACTIVATION

DISK

1. Insert the Activation disk in a diskette drive.

2. In Windows, run the EVMOVE program from the Activation disk. The EvMove
window appears.

48

3. In the EvMove window, select the drive where the activation key is currently stored in
the From box. In the To box, select the drive containing the Activation disk. Click
OK.
4. Do one of the following:

To move activation keys for all installations, click Move.

To change the number of activations to move to the Activation disk, select
RSLogix Emulate 5000, and then click the Edit Selected button. In the Move box,
type the number of activation keys to move. Click OK, and then click Move.

5. To close the EvMove Summary box, click OK.

Activating RSLogix Emulate 5000 after Installation

You might need to reactivate RSLogix Emulate 5000 after moving activation keys back to
the Activation disk or after resetting a damaged activation key. To reactivate the software,
you move the activation key from the Activation disk back to the hard drive.
By default, when you move activation to a hard drive from the Activation disk, the
software moves only one activation key for the software. However, when moving to a
network drive, the software moves all activation keys by default. When reactivating the
software, you can accept a default or choose the number of activation keys to move.

To Reactivate RSLogix Emulate 5000

1. Insert the Activation disk in a diskette drive.
2. In Windows, run the EVMOVE program from the Activation disk. The EvMove
window appears.
3. In the EvMove window, select the drive containing the Activation disk in the From
box. In the To box, select the drive to which you want to move the activation. Click
OK.
4. Do one of the following:

To move activation keys for all installations, click Move.

To change the number of activations to move to the Activation disk, select
RSLogix Emulate 5000, and then click the Edit Selected button. In the Move box,
type the number of activation keys to move. Click OK, and then click Move.

5. To close the EvMove Summary box, click OK.

49

8 SOFTWARE ACTIVATION

GETTING RESULTS WITH RSLOGIX EMULATE 5000

Protecting Your Activation Files

Performing certain operations on the hard drive can damage activation files. Always move
activation from the hard drive back to the Activation disk before doing any of the
following. After completing the operation, it is safe to move the activation back to the
hard drive and reactivate the software.
Move activation files back to the Activation disk before:

Upgrading or installing the computers operating system. Upgrading, installing,

and uninstalling operating system software or networking system software can
damage the activation files.
Compressing or decompressing the computers hard drive. Compressing the hard
drive with some compression software programs can damage activation software. In
addition, decompressing a hard drive with activation files on the compressed drive can
damage activation.

Reactivating a Damaged Activation Key

If the activation key becomes damaged for any reason, contact Rockwell Software
Technical Support for a reset code. Our World Wide Web address and telephone numbers
appear on the inside front cover of this book.

When You Call

When you call or access our web site, you should be at a computer with the Activation
disk available. You do not have to use the same computer where your software is installed.
However, you must have the Activation disk with a serial number that matches the copy of
RSLogix Emulate 5000 you want to reactivate.
The support representative will explain how to find the product ID and system ID from
the Activation disk and then will assign a reset code for the activation key. After obtaining
a reset code from Rockwell Software Technical Support, reset the key, and then reactivate
the software.

To Reactivate a Key with a Reset Code

1.
2.

50

Insert the Activation disk in a diskette drive.

In Windows, run the RESET program from the Activation disk. The Reset window
appears.

3.

In the Reset Code box, type the reset code, and then click OK.

4.

Reactivate the software.

Troubleshooting Activation
If activation is not working:

Are you using the right Activation disk? Check the serial number for RSLogix
Emulate 5000 against the serial number on the Activation disk label. The serial
numbers must match.
Does the computer have a virus? Boot sector viruses can damage the Activation disk.
The Rockwell Software support team recommends using a commercial virus
protection program.
Did you save other files on the Activation disk? Saving any files to the Activation disk
can damage the activation software.
Did you perform an operation on the hard drive that damaged the activation software?
See Protecting Your Activation Files on page 50 for information about actions that can
damage activation.

51

8 SOFTWARE ACTIVATION

GETTING RESULTS WITH RSLOGIX EMULATE 5000

52

Index
Numerics
1789-SIM module

21

A
activating
after installation 49
from diskette drive 47
from hard drive 47
reactivating damaged key 50
running on multiple computers 47
troubleshooting 51
with reset code 50
Activation disk 47
moving activation keys 48
protecting files 50
using as a key 48

B
BPT. See breakpoints.
breakpoints
example 38
format string 38
programming 37, 38
string formats for 41
traced tags 38
types for the format string
when triggered 37

C
calculations
floating point 11
Channel 0 serial port 17
Chassis Monitor
configuring 22
navigating in 14
starting 13
clear display 45
communications driver 25
communications node

42

configuring in RSView 29
comparison of Emulate 5000 and Logix5000
processors 9
Configuration Size 34
Configure Emulation window 18
configuring an emulator 18
consumed tags 22
continuous task dwell time 17
CPU affinity 17

D
dwell time

17

E
e-mail
technical support 8
emulation module
creating 16
emulation modules 9
emulator
configuring 18
EVMOVE.EXE
on Activation disk 47
execution time 10

F
fax number
technical support 8
floating point 11
folder
default installation 3
freeze display 45
freeze log 45

H
hardware requirements
help
accessing 8

53

GETTING RESULTS WITH RSLOGIX EMULATE 5000

I
I/O
Configuration Assembly Instance 34
Input Assembly Instance 34
Input Size 34
Output Assembly Instance 34
Output Size 34
simulating 33
ignore if no value changed 20
installation
activating after installation 49
default folder 3
procedure 2
process 1
required software and hardware 1
running on multiple computers 47

L
license agreement 3, 5
License Move Utility 4
limitations of the software 9
log
freezing and unfreezing 45
log traces to disk 21
Logix5000 processors
compared to Emulate 5000 9

M
master disk 3
memory size 17
module
1789-SIM 21
creating emulator 16
Moving
activation keys 48
RSLogix Emulate 5000 to another computer
47

N
node
configuring in RSView

29

O
OLE for Process Control. See OPC.

54

OPC 29
configuring topic for emulator
operating system
version required 2
overview 9
of using Emulate 5000 12

29

P
periodic save interval 17
phone number
technical support 8
produced tags 22

R
reactivating RSLogix Emulate 5000 49
README file 3
reset code
damaged activation 50
ROCKSOFT.INI
modifying 48
RSLinx
creating communication driver for emulator
25
RSLogix 5000
configuring communications for the
emulator 27
connecting to the emulator 25
setting project to use the emulator 26
RSTestStand
using to simulate I/O 33, 36
RSView
communications node 29
configuring tag 31
connecting the emulator to 29
using to simulate I/O 33, 36

S
serial number 3
serial number for RSTestStand Lite 6
simulated I/O
configuring in a logic project 33
creating 21
simulating I/O 33
software requirements 2
speed of time 19

startup mode

17

T
tags
configuring in RSView 31
consumed 22, 34
configuring 35
produced 22, 34
configuring 34
technical support 8
Technical Support Services
resetting damaged activation 50
time
dwell 17
of execution 10
speed of 19
timeslice 17
timestamp 20
TPT. See tracepoints.
trace
configuring display 20
logging to disk 21
windows
controls on 45
trace log file 20
tracepoints
configuring display 20

example 40
format string 39
programming 39
string formats for 41
traced tags 39
types for the format string
troubleshooting
activation 51

42

U
uninstallation 2
user name 3, 5
using Emulate 5000

12

V
version required for installation
operating system 2
Windows 2
virus
protecting activation files 51

W
Web site
technical support 8
Windows
version required 2

55

INDEX

GETTING RESULTS WITH RSLOGIX EMULATE 5000

56