rsemu getting results

7/22/2019 RSEMU Getting Results

1/60

Doc ID LGEM5K-GR013A-EN-P

Getting Results Guide


2/60

ii

Contacting

Rockwell Software

Technical Support Telephone1-440-646-5800

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.


3/60

CONTEN

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

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

What RSLogix Emulate 5000 Can and Cannot do. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Floating Point Calculations and the Emulator . . . . . . . . . . . . . . . . . . . . . . . . .

A Brief Outline of Using RSLogix Emulate 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Using the Chassis Monitor 1

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 2

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

Setting a Logic Project to Use the Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Communications in the Logic Project . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Connecting the Emulator to RSView 2

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

Creating a Communications Node in an RSView Project . . . . . . . . . . . . . . . . . . . . . .

Adding Tags from Your Logic Project to Your RSView Project . . . . . . . . . . . . . . .

6 Simulating I/O 3

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


4/60

GETTINGRESULTSWITHRSLOGIXEMULATE5000

iv

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

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

7 Programming Breakpoints and Tracepoints 3Programming Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Programming Tracepoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

String Formats for Tracepoint and Breakpoint Instructions . . . . . . . . . . . . . . . . . . . .

Using Trace Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 Software Activation 4

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 5
http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/http://0.0.0.0/


5/60

1 Installing 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 Requirement

on page 2for more information.

2. Install RSLogix Emulate 5000. SeeInstalling RSLogix Emulate 5000on page 2for

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.

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 log

project developed with version 12 of RSLogix 5000, you must use version 12 of RSLogix Emula

5000.

For this component: Use:

Personal computer Any with an IntelPentium 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


6/60


2

Software Requirements

The following software must be installed before installing RSLogix Emulate 5000.

Installing RSLogix Emulate 5000

To install RSLogix Emulate 5000:

1. Log onto the computer on which you want to install the emulator as an administrato

(or a user with administrative privileges).

2. Insert the RSLogix Emulate 5000 CD-ROM into the computers CD-ROM drive. Th

setup program should start automatically. If it does not, open the CD-ROM drive wi

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.

For this software

component: Install: Notes:

Operating system Microsoft Windows XP

Professional Edition or Windows

XP Home editions (either one with

Service Pack 1 or higher)

- or -

MicrosoftWindows 2000 (with

Service Pack 2 or higher)

- or -

MicrosoftWindows NT 4.0

(with Service Pack 6a or higher)

The emulator will not run on other

versions of Windows.

Logix5000 programming

software

RSLogix 5000, version 12.0 or

higher

Required to program the emulator a

observe its operation.

Communication software RSLinx, version 2.41 or higher Required for communicating with t

emulator.

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)

remove the emulator.


7/60

1 INSTALLINGRSLOGIXEMULATE50

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, enteryour name, the name of the company you work for, and your ten-digit software seria

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\RSLog

Emulate 5000 folder. If you want to change the location where the software will be

installed, click Browseand select a new location for the software. After choosing th

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 Foldersfield, or choose afolder that already exists from the Existing Folderslist.

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 Monito

application. If you want an icon for the Chassis Monitor added to your desktop, clic

Yes. If not, click No. (If you do not place the Chassis Monitor icon on your deskto

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 filecheck 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 Diskcheck box.

11. Click Finishto 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. Thi

program will move the activation file from the RSLogix Emulate 5000 Master Disk

(provided with the software) to your hard drive.

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

drive.

The activation file is required for the proper operation of RSLogix Emulate 5000. See Chapter

for more informationabout software activation.


8/60


4

b. On the EvMove window, set the From Drivebox to the letter for your computer

floppy disk drive (usually A:). Set the To Drivebox 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 thactivation on the master disk and the activations that are already installed on you

hard disk.

d. Click the activation you want to move from the master disk (WED32.EXE), the

click Move.

e. After EvMove moves the activation, it displays the Move Summary window. Th

window informs you about the activations that were moved. Click OK.

2. Click Move.

1. Click the activation

you want to move

(WED32.EXE)


9/60


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 an

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, RSTestStan

can be easily and quickly configured to represent a wide variety of processes discrete

through continuous. Once configured, the system can respond automatically to differencontrol signals. In addition, the product provides an extensive user interface that lets yo

dynamically interact with your control program through the process checking for erro

and determining system response to out-of-range conditions.

You can get information about the full RSTestStand product from the Rockwell Softwar

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 administrato(or a user with administrative privileges).

2. Insert the RSLogix Emulate 5000 CD-ROM into the computers CD-ROM drive. Th

setup program should start automatically. If it does not, open the CD-ROM drive wi

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.


10/60


6

This screen also asks for a serial number. Since you are installing the Lite version o

RSTestStand, there is no serial number provided with the software, but you will nee

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.


11/60


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.)

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 clicOK.

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.

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.


12/60


8

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-ma

BYPHONE

To contact Rockwell Automation Technical Support by phone, call 440.646.5800.

BYFAX

To contact Rockwell Automation Technical Support by fax, dial 440.646.5801.

BYE-MAIL

To contact Rockwell Automation Technical Support by e-mail, send your message to

[email protected]

Support Information on the World Wide Web

To obtain support information from Rockwell Automations World Wide Web site, go to

http://support.rockwellautomation.com.


13/60

2 An Overview of RSLogix Emulate 5000RSLogix Emulate 5000 is a software product that emulates the behavior of Logix5000processors. 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.

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 doRSLogix Emulate 5000 simulates most of the behaviors of Logix5000 processors. Ther

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.

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.


14/60


10

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

Professional, Single Node, OEM, or

Gateway)

DDE/OPC (requires RSLinx

Professional, Single Node, OEM,

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

instructions)Supportedb 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 3

Trending Yes Yes

Online editing of sequential

function chart and structured

text programsc

Yes Yes

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 oth

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!


15/60

2 ANOVERVIEWOFRSLOGIXEMULATE50

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 language

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 bein

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 5000program performs "a = n / m" where the data types for "a", "n", and "m" are real, intege

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 poin

divide between "n" and "m" and places the answer into "a", with no conversion needed.

"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 an

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 an

"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.


16/60


12

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 emulato

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 RSLogix5000.

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 projec

(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.


17/60

3 Using the Chassis MonitorThe Chassis Monitor is a software application used to configure RSLogix Emulate 5000and I/O simulation modules.

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 th

Chassis Monitor from the Windows System Tray.

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:

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 log

project developed with version 12 of RSLogix 5000, you must use version 12 of RSLogix Emula

5000.

For version 13 of RSLogix 5000 Emulate: Unlike the SoftLogix 5800 controller, RSLogix Emula

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.


18/60


14

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.)

System Tray Icon Status Indicators

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

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 Monitorslots, 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.

This icon: Means:

Normal operation. No faults.

(Red triangle, white

exclamation point)

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

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 Emula

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.

This is the

Chassis Monitor

icon in the

Windows System

Tray.


19/60

3 USINGTHECHASSISMONITO

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 thre

simulated I/O modules.

These "slots" hold emulator or

simulated I/O modules. Click Slot

> CreateModule to create a

module.

This is an

emulator module.

This is a simulated I/O module.

You can click on the module's

terminal cover to open it.

The RSLinx

module in slot 0

cannot be

removed.

The red box surrounding this

module indicates it is selected

You can right-click modules to

display a configuration menu.

This button allows you to

contract the Chassis Monitor into

a smaller display. This smaller

display hides slots 9 through 16.


20/60


16

Creating an Emulation Module

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 Slotfield, enter the slot where you want the emulator to reside. The emulator

can be in any slot (except for slot 0).

4. Click OK to accept your changes and add the emulator to the virtual chassis.

You can click Cancelif 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, chec

the Load Saved Controller Image from Previous Instancecheck box.

c. Click Nextto continue.

You can have up to 16 emulation modules in the Chassis Monitor at one time. However, you

computers performance may be impaired significantly if you run multiple emulation modules

simultaneously.

If you modify the project to use a physical Logix5000 processor, make sure your rack and slo

configurations in your project match those in your control system. Otherwise, you may not beable to communicate properly with the physical controller, the physical controller may fault, or

your control program may have unexpected results.

Using a previously loaded controller image may result in unexpected operation. Make sure thprogram is correct before running your emulations.


21/60


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

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

5. Click Next. The software displays a window for setting additional features of the

emulator.

6. Click Finish. The Chassis Monitor places an emulator module in the slot you

selected.

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 whateve

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. M ake this equal to the memory si

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 s

specify how often (minutes). The default is enabled for 10 minutes.

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 an

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 on

CPU, set the CPU that you want to run the emulator (the emulator crun 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 emula

Channel 0 of the Logix5000 processor.

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.


22/60


18

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, the

click Configure Emulation. The Configure Emulation window opens. This windo

is illustrated below.

These controls

allow you to

control the

"speed of time"

These controls

allow you to

configure trace

displays

Active tracesappear in this list

This control

allows you to log

traces to a file


23/60


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 slow

program execution by an amount proportional to the percentage you select. For exampl

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:


2. Right-click the emulator module for which you want to display the configuration, theclick 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.

Click this to stop

program execution

immediately

Use the slider to adjust

the speed of time in one

percent increments

Click this to set

the speed of

time to 100%

immediately

This field shows

the last value set

for the speed of

time

If you use the slider or

type a percentage, clickthis button to confirm

the change

You can also

type the

percentage in

this field


24/60


20

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. SeeProgramming

Breakpoints and Tracepointson page 37for information about programming theseinstructions.

To configure how the emulator handles and displays these traces:


2. Right-click the emulator module for which you want to display the configuration, the

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 bein

traced. If the button is indented, the trace displays will ignore thos

traces where the value does not change.

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

Nonerecords no time information in the trace displays.

Deltarecords the difference between the current trace and the last

trace.

Absoluterecords the time that the trace triggered. The time is in th

number of milliseconds since the computer running the emulator w

last rebooted.

Display all new traces Check this box if you want all new traces to display automatically i

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 l

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, seeLog Traces to Diskon page 21


25/60


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 Browsebutton.

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 namefield.

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 th

traces, or cancel.

6. Execute your logic. When a TPT instruction executes, the trace information is logge

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).

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 Chass

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 Sele

Module window.

2. In the Select Module window, select the 1789-SIM 32 Point Input/Output

Simulatorfrom the Module Typelist. Set the Slotfield to the slot number into whic

you want to place the SIM module. Click OK. The software displays the SelectDevice window.

3. The Select Device window displays the device serial number (actually the slot

number for the module).

You can log data to a file with any extension (or with no extension at all). However, to be able

view traces with a text editor (such as Windows Notepad), use a TXT file extension.

If you try to open the log file without closing it in the emulator configuration, you will see an err

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.


26/60


22

a. If you deleted a SIM module from this slot without clearing its configuration, th

software displays a message saying that previous configuration information exis

for the module. You can retain the previous configuration, or you can reset the

configuration to default values. To retain the previous configuration, click Usethe 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 Marqueefield. (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 Tagson page 34for informatio

about configuring these tags.

Configuring the Chassis Monitor

You can configure the behavior and display of the Chassis Monitor. The following tabl

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

simply want the Chassis Monitor to take up less space on-

screen)

View > Hide Slots 9-16

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

it is displayed

Options > Always On Top

Set the Chassis Monitor to start in a minimized state (the

window is not opened immediately and the application is

available from the Windows Taskbar)

Options > Start Minimized

Remove the Chassis Monitor from the Windows Taskbar

when you minimize its window (the Chassis Monitor icon

remains in the System Tray)

Options > Hide When Minimized


27/60


When you delete a module, automatically check the Clear

Chassis Monitor module configuration check box.

(If this feature is not set, the software does not

automatically check that box for you.)

Options > Clear Configuration on Remove

To set the Chassis Monitor to: Click this menu option:


28/60


24


29/60

4 Connecting the Emulator toRSLogix 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. Th

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

Typeslist.

3. Click Add New. The Add New RSLinx Driver window appears. This window allow

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 Driverslist. Click Close.


30/60


26

Setting a Logic Project to Use the Emulator

Before you can emulate a logic project, you must configure the project's processor type t

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 Generaltab of the Controller Properties window, set the Slotfield 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.

2. ClickAdd New.

1. Select the Virtual

Backplane (SoftLogix

58xx) communications

driver

3. Click Close.


31/60

4 CONNECTINGTHEEMULATORTORSLOGIX50

5. From the Tolist, select EmulatorRSLogix 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 emulat

you want to use for this project.

4. Click Set Project Path. This sets the communication path to use the emulator.

1. Click Change Type.

2. Select RSLogix

Emulate 5000

Controller.

2. Click OK.


32/60


28


33/60

5 Connecting the Emulator to RSViewRSLogix Emulate 5000 uses OLE for Process Control (OPC) to communicate withRSView. Connecting the emulator to an RSView project requires creating an OPC topi

in RSLinx, then creating a communications node and tags in the RSView project that use

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). Theemulator 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 Emulatoron page 25for 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 ProjectTo create a communications node in RSView that uses the OPC topic for the emulator:

1. Open your RSView project.

2. In your projects Systemfolder, open the Nodeeditor. In RSView, a node represents

communications device, usually a programmable controller or another Windows

application. In the Node editor, we will create a node that represents the emulator.


34/60


30

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

4. Click Accept. This saves the node configuration.

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 fas

or slower update rate, enter the update frequency.

1. Click OPC

Server.

2. Enter a name

for the node.

3. Make sure the Enabled

checkbox is checked.

4. Click this button, click

RSLinx OPC Server,

then click OK.

6. Set the Update Rateto

the frequency at which

you want data to updateyour RSView project.

7. Click

Accep

5. Make sure In-Process

is selected.


35/60

5 CONNECTINGTHEEMULATORTORSVIE

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 Systemfolder, open the Tag Databaseeditor.

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

1. Click Device.

3. Select the data

type for the tag.

2. Click this button and

select the OPC node

you created for the

emulator.

4. Click this button to

display the OPCAddress Browser.

5. Browse for the

address you want to

use with the tag in

this tree.

6. Select the address.

7. Click OK.


36/60


32

4. Click the button next to the Node Name field. This displays the Node Browser. Sele

the OPC node you created for the emulator and click OK.

5. In the Tagsection of the Tag Database editor, select the type of tag you want to creat

from the Typelist.

6. In the Data Sourcesection of the Tag Database editor, click the button next to the

Addressfield. This displays the OPC Address Browser.

7. In the OPC Address Browser, select the address you want to use with the tag and clic

OK.

8. Finish creating the tag by filling in the fields in the Tag Database editor.

9. Click Accept. The tag is stored in the tag database. You can now use the tag in you

RSView project.

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 cla

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.


37/60

6 Simulating I/OThere are two methods of simulating I/O with RSLogix Emulate 5000. You can use asimulated I/O module to simulate discrete I/O, or you can use another emulation modul

to produce and consume tags of any type. You can use both methods simultaneously.

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

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 Configurationfolde

and click New Module. The software displays the Select Module Type window.

2. Select 1789-MODULEfrom the modules list, then click OK.

3. The software displays the Module Properties window. Enter the following paramete

for the module:

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

Additionally, you can use other software products such as RSView and RSTestStand to simula

I/O.

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.


38/60


34

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

6. Specify the Requested Packet Interval (RPI).

7. Click Finish.

Configuring Produced and Consumed Tags

Another method for simulating I/O for your emulated project is to produce and consum

tags from another emulation module. (See the documentation for your Logix 5000

processor for background information about produced and consumed tags.)

Configuring a Produced TagTo 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 Tagsfolder. (Produced tags must be scope

to the controller.)

For read/write connections: For listen only connections:

Input Assembly Instance 1 Input Assembly Instance 1

Input Size 2 Input Size 2

Output Assembly Instance 2 Output Assembly Instance 3

Output Size 1 Output Size 1

Configuration Assembly Instance 16 Configuration Assembly Instance 16

Configuration Size 0 Configuration Size 0

You mustenter at least 50.0 ms for the RPI. The connection will fail if the RPI is less than 50ms. Because this module uses the generic module profile, the default RPI is 5.0 ms. You mu

change this value.


39/60

6 SIMULATINGI

3. Right-click the tag you want the emulator to produce, then click Edit Tag Properties

This displays the Tag Properties window.

4. In the Tag Properties window, select the Producetag 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 th

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.

MAKINGTHEPRODUCERANI/O MODULEOFTHECONSUMER

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 Configurationfolder, then click New Module

This displays the Select Module Type window.

3. In the Select Module Type window, select the Emulatormodule 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

Namefield. Set the slot number for the producing emulator in the Slotfield.

6. Click Finish. The producing emulator is now an I/O module of the consuming

emulator.

CREATINGACONSUMEDTAG

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.

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.


40/60


36

2. Right-click the tag you want the emulator to consume, then click Edit Tag

Properties. This displays the Tag Properties window.

3. In the Tag Properties window, choose the Consumedtag type.

4. Select the producing emulator from the Producerdrop-down list box.

5. Type the name of the tag that the producer is producing in the Remote Tag Name

field.

6. In the RPIfield, set the Requested Packet Interval (RPI) to the amount of time (in

milliseconds) you want the consuming emulator to wait between data requests for th

tag. This is the minimum rate at which the emulator will consume data.

7. In the Data Typefield, enter the data type for the consuming tag. This must be thesame 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

test stand simulation environment.

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.

RSTestStand Lite, a demonstration version of the RSTestStand test stand simulation product,

available from the RSLogix Emulate 5000 installation disk.


41/60

7 Programming Breakpoints andTracepoints

Breakpoint and tracepoint instructions allow you to monitor the state of your logic when

is in conditions that you determine. Breakpoints stop program emulation when a rung i

true. Tracepoints log data you select when a rung is true.

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 programexecution. 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 emulato

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 th

breakpoint and the values it traces are displayed in the trace window.

Breakpoint and tracepoint instructions are supported only in ladder diagram programs runnin

in the emulator. These instructions are not supported by physical Logix5000 processors.

When a breakpoint triggers, you will not be able to edit your project until you permit execution

continue. You can go online with the emulator to observe the state of your project, but you wil

not be able to edit it. If you try to accept a rung edit while a breakpoint is triggered, you will see

dialog box saying the controller is not in the correct mode.


42/60


38

Programming the BPT instruction

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

You can display a large number of tag values with the BPT instruction, however, theformatting 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 wa

to include spaces and other formatting to separate tag data in your traces, so the resultin

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:

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 Instructionso

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 t

You cannottrace tag structures (such as

entire timers, counters, etc.). However, y

can trace individual structure members.


43/60

7 PROGRAMMINGBREAKPOINTSANDTRACEPOIN

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 b

traced (analogvalue). (See String Formats for Tracepoint and Breakpoint Instructions

on page 41 for more information about formatting strings. The resulting traces appear a

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, se

Configure Trace Displayson 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 Instructionso

page 41.

Trace This: The tag you want to trace. An INT, BOOL, SINT, DINT or REAL t

You cannottrace tag structures (such as

entire timers, counters, etc.). However, ycan trace individual structure members.


44/60


40

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 includespaces and other formatting to separate tag data in your traces, so the resulting number o

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 exceed

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 Instructionson page 41 for more information about formatting strings.


45/60


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 o

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 ho

the traced tags appear in the traces or breakpoint windows. The format of the string is afollows:

heading:(text)%(type)

where headingis a text string identifying the tracepoint or breakpoint, textis a string

describing the tag (or any other text you choose), and %(type) indicates the format of th

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 moreinformation.


46/60


42

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 wit

any flag).

The resulting tracepoint window that would appear when the tracepoint is triggered woulook like:

Types for Formatting Tag Values

The following table shows the available types for formatting tag values. Any type can b

used for formatting any tag. (The types are similar to those used by the C++ printf

function.)

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

converted to octal. REAL values are truncated.

45.3202 is rendered as 55.

The text for the INT

(represented in the

format string as %d)

appears here

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 slot number

indicates the slot

containing the

emulator module that

has the tracepoint or

breakpoint being

traced in the trace

window


47/60


Using Trace Windows

Opening and Closing Trace Windows

By default, tracepoint and breakpoint windows display automatically when a tracepoint o

breakpoint instruction first executes. (You can configure the emulator to not display thes

windows automatically. See Configure Trace Displayson 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 acce

active traces through the Configure Emulation window (right-click the emulator, then

click Configure Emulation). The Configure Emulation window allows you to performthe following operations on trace windows:

%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

exponent delimiter (e) is rendered in lowercase.

45.320200 is rendered as

4.532020e+001.

%E Signed floating point value with exponent. The

exponent delimiter (E) is rendered in uppercase


4.532020E+001.

%f Signed floating point value without exponent. 45.320200 is rendered as

45.320200.

%g Signed floating point value in %e or %f

format, whichever results in a more compact

display. Trailing zeros are truncated, and the

decimal point appears only if one or more digits

follow it. The exponent delimiter (e) is rendered

in lowercase (when it is appropriate).

45.320200 is rendered as 45.320


4.3323e+008.

%G Signed floating point value in %e or %f

format, whichever results in a more compact

display. Trailing zeros are truncated, and the

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.320


4.3323E+008.

This type: Formats the tag value as: Example:


48/60


44

To perform this function: Do this:

Have traces automatically open whenever a new

tracepoint or breakpoint instruction executes.

Check the Display all new tracescheck 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.

Click Display All

Tracesto open all of

the active traces

Check Display all new

tracesto automatically

display trace windows

when new tracepoints orbreakpoints execute

Active traces

appear in this list

-- double-click a

trace to display it

Clicking Close All

Tracescloses all open

trace windows

Click Remove All

Tracesto remove all

active traces


49/60


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 Clear Displayto

clear the traces from

the window

Click Freeze Displayto

stop the trace window

from updating

Click Freeze Logto

stop logging the trace

to disk.


50/60


46


51/60

8 Software ActivationRockwell Software uses activation files to provide copy protection for its Windows-basesoftware 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 500

About the Activation Disk

RSLogix Emulate 5000 comes with a separate Activation disk that activates the softwar

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 activatio

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.EXEthat moves activation keys to and from computers

A file called RESET.EXEthat 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.


52/60


48

Using the Activation Disk as an Activation Key

To use the activation key from a diskette drive, modify the ROCKSOFT.INIfile 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.

TOMODIFYTHEROCKSOFT.INI FILE

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

2. When the Activation window opens, click Cancelto bypass the activation procedur

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 t

the end of the file.)

6. Edit this string so it says: KEYDISK=TRUE.

7. Save and close the ROCKSOFT.INI file.

TOACTIVATERSLOGIXEMULATE5000

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.

MOVINGACTIVATIONKEYSBACKTOTHEACTIVATIONDISK

You can move activation keys from the hard drive back to the Activation disk at any tim

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 Fileson page 50for a list of operations that can damage

activation)

before sending the computer to a technician

TOMOVEACTIVATIONKEYSBACKTOTHEACTIVATIONDISK

1. Insert the Activation disk in a diskette drive.

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

window appears.


53/60

8 SOFTWAREACTIVATIO

3. In the EvMove window, select the drive where the activation key is currently stored

the Frombox. In the Tobox, 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 Selectedbutton. In the Movebo

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 t

the Activation disk or after resetting a damaged activation key. To reactivate the softwaryou 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


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 Tobox, 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 Selectedbutton. In the Movebo

type the number of activation keys to move. Click OK, and then click Move.

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


54/60


50

Protecting Your Activation Files

Performing certain operations on the hard drive can damage activation files. Always mov

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 har

drive with some compression software programs can damage activation software. In

addition, decompressing a hard drive with activation files on the compressed drive ca

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 number

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 installe

However, you must have the Activation disk with a serial number that matches the copy o

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 obtainin

a reset code from Rockwell Software Technical Support, reset the key, and then reactiva

the software.

To Reactivate a Key with a Reset Code


2. In Windows, run the RESET program from the Activation disk. The Reset windo

appears.

3. In the Reset Codebox, type the reset code, and then click OK.

rsemu getting results

Documents