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

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. See String formats for tracepoint and breakpoint instructions.
Trace This:	The tag you want to trace.	An INT, BOOL, SINT, DINT, or REAL tag. You cannot trace tag structures (for example, entire timers or counters). However, you can trace individual structure members.

You can trace a large number of tags with the TPT instruction, but 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 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"). Click here for more information about formatting strings.

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

Configuring a tag in RSView32

Once you have created an OPC node for the emulator, you can add tags from your logic project to your RSView32 tag database. To do this:

1. Open your RSView32 project.
2. In your project’s System folder, open the Tag Database editor.
3. In the Data Source section of the Tag Database editor, click Device.
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 RSView32 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 RSView32).
Maximum	The maximum value for the tag (as used in RSView32).
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 RSView32 project.

Creating a communications node in an RSView32 project

To create a communications node in RSView32 that uses the OPC topic for the emulator:
1. Open your RSView32 project.
2. In your project’s System folder, open the Node editor. In RSView32, 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.
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 selected.
Server	Click the button next to the Server Name field. If the emulator is running on the same computer as RSView32, select RSLinx OPC Server. Otherwise, select RSLinx Remote OPC Server.
Type	If the emulator is running on the same computer as RSView32, select In-Process. Otherwise, select Remote and enter the name of the computer running the emulator in the Server Computer Name or Address field.
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.

4. Click Accept. This saves the node configuration.

Format of .DBF trend files

The following is an example of the format of RSLogix Emulate-compatible .DBF files, as shown in a Microsoft Excel spreadsheet. The first record in the file is the time the record was logged and the symbol names/addresses logged (RSTrend saves the symbol name, if one is available).

The trend player expects this format. You can have any number of addresses in the .DBF file, but they need to be arranged in the manner shown above.

Where are the addresses?

Note that the .DBF file does not necessarily contain address information. For the trend player to work, the address information must either be in the .DBF file, or addresses must be assigned to the .DBF file in the trend player.

If you are using RSTrend and logging data from addresses, the address record in the .DBF file contains "symbolic versions" of the address. The trend player in RSLogix Emulate interprets this address information as addresses.

If you are using RSTrend and logging data from symbols (or any other method other than from addresses), the addresses record differently in the resulting .DBF file. The example shown above is from RSTrend logging data from symbols. If this is the case, you will need to assign addresses to the .DBF file records.

Note The trend player is designed to work primarily with RSTrend, and therefore the trend player expects to see DBF files in the same format as the files generated by RSTrend. This means that if you want to include the address information in the DBF file (and avoid having to tell the trend player which addresses go with which records), the address information contained in the DBF file must be in the format described in the table below.

Address Type	Format	Example
Word address	nx_w (where n is the file radix, x is the file number, and w is the word number)	N57:0 becomes N57_0
Word address with mnemonic	nx_w_m (where n is the file radix, x is the file number, w is the word number, and m is the mnemonic)	T4:0.ACC becomes T4_0_ACC

Where to get .DBF files

Two Rockwell Software packages, RSTrend and RSView, save process trend data in .DBF files. You can also create .DBF files in several applications, such as dBase®, Lotus 1-2-3®, Microsoft Excel®, and others.

It is more accurate and simpler to sample actual process data rather than create data on your own, especially for large numbers of samples. RSTrend is ideal for sampling live process data. For more information on these software packages, please call Rockwell Software or your local distributor.

Once you have sampled a process and gathered data into a .DBF file, you can open a project in RSLogix Emulate, and feed the data into the project from the .DBF file.

Note The play trend feature uses only word address values. Bit values are not supported at this time. If you need to use a bit address in a simulation, use the entire word containing the bit.

Keyboard shortcuts

The following keyboard commands operate on the currently selected file, which is the file shown in the file selection listbox in the toolbar, and is also the checked file in the File menu. The complete path name of the current file is displayed on the title bar at the top of RSLogix Emulate's window.

To perform this operation:	Use this keyboard command:
Open a new file	[Ctrl-O]
Reload the current project	[Ctrl-L]
Close the current file	[Ctrl-C]
Place the current file in Halt mode	[Ctrl-H]
Place the current file in Run mode	[Ctrl-R]
Place the current file In Single-scan Mode	[Ctrl-S]
Place the current file in One-rung Mode	[Ctrl-G]
Execute one scan of the current file	[Ctrl-Spacebar]

Forcing I/O

Since the software acts so much like a real processor, many users will attempt to force I/O without considering an important fact about emulation: There is no I/O.

Caution: Support for forcing in the software is there for your convenience in an attempt to emulate how the processor will behave. There are differences between how a real processor forces and how the software forces, and you should be aware of those differences. If you are not familiar with forcing in a real processor, see your processor's documentation for information about forcing. Do not rely on your background in forcing in the software when attempting to force I/O in a real processor. Unexpected machine movement could result, causing damage to equipment and injury to personnel.

When you force an input or output in a real processor, the force takes place in the I/O image table, not in the processor data table. Since the software relies on only the data table, forcing does not always work the same way as in a real processor. The following table describes the differences:

This bit type:	In this force mode:	When enabling forces:	When disabling forces:
Input	ON	In a real processor, forcing an input ON forces a bit in the I/O image table. When the processor updates the Data Table, the forced bit in the image table appears as ON in the input data table file. In the software, forcing an input ON sets the address in the data table ON (1) at the beginning of the program scan. The value of the input is still dictated by the ladder program.	In a real processor, removing or disabling an ON force removes the force and allows the input address value to be dictated by the state of the real I/O. In the software, removing or disabling an ON force allows the input address value to be dictated by the state of real I/O. Since there is no real I/O, the input remains ON until manually reset to OFF (0).
	OFF	In a real processor, forcing an input OFF forces a bit in the I/O image table. When the processor updates the Data Table, the forced bit in the image table appears as OFF in the input data table file. In the software, forcing an input OFF sets the address in the data table OFF (0) at the beginning of the program scan. The value of the input is still dictated by the ladder program.	In a real processor, removing or disabling an OFF force removes the force and allows the input address value to be dictated by the state of the real I/O. In the software, removing or disabling an OFF force allows the input address value to be dictated by the state of real I/O. Since there is no real I/O, the input remains OFF until manually reset to ON (1).
Output	ON	In a real processor, forcing an output ON forces a bit in the I/O image table. Values in the data table are not affected by the force. In the software, forcing an output ON forces a bit in the I/O image table. Values in the data table are not affected by the force.	In a real processor, removing or disabling an ON force removes the force and allows the output address value to be dictated by the state of the I/O image table. In the software, removing or disabling an ON force removes the force and allows the value of the output data table address to be dictated by the ladder program.
	OFF	In a real processor, forcing an output OFF forces a bit in the output image table. This causes the output on the real I/O module to turn off. The value in the output data table is not affected by the force. In the software, forcing an output ON forces a bit in the I/O image table. Values in the data table are not affected by the force.	In a real processor, removing or disabling an OFF force and allows the value of the output image table address to be dictated by the output data table. In the software, removing or disabling an OFF force removes the force and allows the value in the output data table to be dictated by the ladder program.

Setting up WINtelligent LINX to communicate with RSLogix Emulate

Here's how to set up communications between WINtelligent LINX and RSLogix Emulate:

1. Open WINtelligent LINX.
2. Click Comms > Communications Hardware.
3. From the Hardware Devices list, select DH+ Emulator (for RSLogix Emulate 5) or DH485 Emulator (for RSLogix Emulate 500).
4. Click the Add New button. A configuration dialog appears.
5. Type a station number for RSLogix Emulate in the Sta# field. Remember, RSLogix Emulate is being treated as if it were a hardware device, so it needs a unique station number. You can also type a name for RSLogix Emulate in the Station Name field.
6. Click the OK button.

When RSLogix Emulate is running with programs in memory, you can perform a Who Active and see the programs as if they were in PLC-5s on a Data Highway Plus or SLC 500s on a DH-485. Other applications that use WINtelligent LINX can also access the programs as if they were on a communications network.

Setting up RSLinx to communicate with RSLogix Emulate

If you have set up your communications for your physical processors, you'll find setting up communications for RSLogix Emulate a simple procedure. Basically, you'll set up communications between RSLogix Emulate and RSLinx exactly as if RSLogix Emulate is a hardware device.

Here's how to set up communications between RSLinx and RSLogix Emulate:

Open RSLinx.

In RSLinx, click Communications > Configure Drivers. RSLinx displays the Configure Drivers dialog.

From the Available Driver Types list, select PLC-5 (DH+) Emulator or SLC-500 (DH485) Emulator, and click the Add New button. RSLinx displays a dialog for naming the driver you selected. Click OK to continue.

RSLinx displays a dialog for configuring the driver. Type a station number for RSLogix Emulate in the Station Number field. Remember, RSLogix Emulate is being treated as if it were a hardware device, so it needs a unique station number. You can also type a name for RSLogix Emulate in the Station Name field.

When you have configured the driver, click OK. The driver configuration dialog closes.

When RSLogix Emulate is running with programs in memory, you can use the Who Active or RSWho functions and see the emulator as if it was a PLC-5 on a Data Highway Plus network or an SLC-500 on a DH485 network. Other applications that use RSLinx can also access the programs as if they were on a communications network.

Emulation exceptions

Instruction exceptions

There are several instructions that RSLogix Emulate will not emulate . These are listed in the table below:

Mnemonic	Instruction	Execution
BTR	Block Transfer Read	There is no real I/O to read. The software will not emulate the actual transfer of data, but the enable (.EN) and done (.DN) bits are emulated. When a BTR is "executed," the enable bit is set during the first scan, then the done bit is set during the second scan. If you wish, you may use debug files to emulate the data transfer.
BTW	Block Transfer Write	There is no real I/O to read. The software will not emulate the actual transfer of data, but the enable (.EN) and done (.DN) bits are emulated. When a BTW is "executed," the enable bit is set during the first scan, then the done bit is set during the second scan. If you wish, you may use debug files to emulate the data transfer.
COR	Custom Output Routine	The COR instruction passes parameters to a Custom Application Routine (CAR) file. CAR files are not emulated in any way. The instruction is not executed.
CPW	Copy Word	(SLC 500 only) This instruction is not executed.
DLG	Data Log	(MicroLogix 1500 only) The data logging function is not emulated. The instruction is not executed.
GCD	Gray Code	(SLC 500 only) This instruction is not executed.
HSC	High Speed Counter	(SLC 500 only) This instruction is not executed.
IDI	Immediate Data Input	There is no I/O image table to update in the software. This instruction is not executed.
IDO	Immediate Data Output	There is no I/O image table to update in the software. This instruction is not executed.
IID	I/O Interrupt Disable	(SLC 500 only) There is no I/O to generate an interrupt, therefore this instruction has no effect.
IIE	I/O Interrupt Enable	(SLC 500 only) There is no I/O to generate an interrupt, therefore this instruction has no effect.
IIM	Immediate Input with Mask	(SLC 500 only) There is no I/O to update, therefore this instruction has no effect.
IIN	Immediate Input	There is no I/O image table to update in the software. The instruction is not executed.
INT	Specialty I/O Interrupt	(SLC 500 only) There is no I/O to trigger an interrupt, therefore this instruction has no effect.
IOM	Immediate Output with Mask	(SLC 500 only) There is no I/O to update, therefore this instruction has no effect.
IOT	Immediate Output	There is no I/O image table to update in the software. The instruction is not executed.
MSG	Message	Even though the software provides Data Highway Plus emulation and Channel 0 emulation, the MSG instruction emulates only the enable (.EN) and disable (.DN) bits. When the emulator scans a MSG instruction, the EN bit is set during the first scan, and the DN bit is set during the second scan. If you wish, you may use debug files to emulate the data transfer.
PID	Proportional, Integral, Derivative	The software does not attempt to execute the PID instruction or change any of the PID control bits or words.
PTO	Pulse Train Output	(MicroLogix 1200 and 1500 only) There are no outputs. The instruction is not executed.
PWM	Pulse Width Modulation	(MicroLogix 1200 and 1500 only) There are no outputs. The instruction is not executed.
RCP	Recipe	(MicroLogix 1500 Series C only) This instruction is not executed.
REF	I/O Refresh	(SLC 500 only) There is no I/O to refresh, therefore this instruction has no effect.
RPI	Reset Pending I/O Interrupt	(SLC 500 only) This instruction is not executed.
RPI	Reset Pending I/O Interrupt	(SLC 500 only) There is no I/O to generate an interrupt, therefore this instruction has no effect.
RTA	Real Time Clock Adjust	(MicroLogix 1200 and 1500 Series C) This instruction is not executed.
SVC	Service Communications	(SLC 500, MicroLogix 1200 and 1500) There are no processor communications to service, therefore this instruction has no effect.

Processor feature exceptions

Processor Feature	Execution
Checksum tests	The emulator cannot perform a processor checksum. If you attempt to access the emulator from a computer other than the one running the emulator, RSLogix 5 will attempt to get the emulator to perform a checksum calculation. This calculation will fail, and RSLogix 5 will appear to hang. You can cancel the calculation and continue.
Partial downloads	The emulator does not support partial downloads.
Custom Application Routines (CARs)	CARs are not ladder logic and are not executed in any way.
Floating Point and other Math Functions	Floating point and other math instructions are emulated by the software. However, since the software and the processors use different microprocessors (PLC-5 and SLC 500 processors use Motorola CPUs and the software uses your computer's CPU), the results of the calculations may differ, particularly in floating point math and in integer math involving rounding.
I/O Status	None of the I/O status information is used by the software.
Multiple Main Control Programs (MCPs)	You can execute one program file at a time. Subroutines called by the single program will be executed.
Processor Configuration	The software does not use all of the information stored in the processor configuration. The STI configuration, fault file configuration, and watchdog timer are all used by the software. In the case of the watchdog timer, you can set the timeout value to zero to disable the watchdog timer while emulating. Note that the processor will fault immediately upon being switched into Run mode if the watchdog timer is set to zero. You can use the fault options dialog to set how the software handles the watchdog timer.
Processor Input Interrupt (PII)	The software makes no attempt to emulate the PII. There are no real inputs to generate the interrupt.
Processor Status	Active Node Status, EEPROM status, etc. are not emulated. Processor status bits and fault codes are emulated. Processor scan time and maximum scan time are updated. The first-scan bit is emulated, but only on a Program to Run mode transition.
Sequential Function Charts	You can emulate individual step and transition files, but the SFC cannot be emulated.
User Interrupt File	You may emulate the user interrupt file, but there is no means to trigger its execution. You could emulate it by making it the main file, or by programming a JSR instruction to go to the interrupt file.

Creating an OPC topic for the emulator

Tip: You must use one of the following products to create the OPC topic: RSLinx Classic Single Node, RSLinx Classic OEM, or RSLinx Classic Gateway. RSLinx Classic Lite does not support OPC communication. For more information about using RSLinx Classic, see the RSLinx Classic documentation.

To create an OPC topic for the emulator:

1.      Open the Chassis Monitor, and make sure your emulator is running.

2.      In RSLinx Classic, 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.

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.

About connecting the emulator to RSView32

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

Please see the documentation for RSView32 for more information.

How to Browse for tags from the emulator in FactoryTalk View ME or FactoryTalk View SE

After you have configured the RSLinx Enterprise server for your FactoryTalk View SE or FactoryTalk View ME project, you can then browse for tags from the emulator whenever you need to do so in your project.

When you use the FactoryTalk View tag browser, you will see a folder corresponding to the shortcut you created in the RSLinx Enterprise server Communication Setup window. The folders inside that shortcut folder contain tags from the emulator.

The Online folder contains controller tags, and the folders for each program file contain program tags.

How to Configuring an RSLinx Enterprise server for your emulator

To configure an RSLinx Enterprise Server for your emulator:

1.      Make sure the emulator is running.

2.      Open your FactoryTalk View SE or FactoryTalk View ME project.

3.      In the FactoryTalk View Explorer tree, right-click the area of your project where you want to create the RSLinx Enterprise data server, and then click Add New Server > Rockwell Automation Device Server (RSLinx Enterprise). (You can also create the server in the root of your FactoryTalk View project.)

4.      Type a name for the RSLinx Enterprise server in the Name field. Optionally, you can type a description for the server in the Description field.

5.      In the Computer hosting the RSLinx Enterprise server field, enter the name of the computer running RSLogix Emulate 5000. If this computer is the same as the computer running FactoryTalk View, enter either the name of the computer or localhost. (For FactoryTalk View ME systems, localhost is the only possible name.)

6.      In the Explorer tree for your FactoryTalk View project, open the RSLinx Enterprise server and then open Communication Setup. The Communication Setup window for the server opens.

7.      In the Communication Setup window, you need to create a "device shortcut" to the emulator. The shortcut allows you to identify which tags are coming from the emulator in the FactoryTalk View tag browser.

·         Click the Add button, and then type a name for the shortcut. This is the name that will appear in the FactoryTalk View tag browser.

·         Open the virtual backplane and select the emulator. 

·         Click Apply. You are prompted to apply your changes. Click Yes; this associates the shortcut with the emulator

·         Click OK. This closes the Communication Setup window.

About connecting the emulator to FactoryTalk View ME or FactoryTalk View SE

You can use either RSLinx Enterprise or RSLinx Classic to connect RSLogix Emulate 5000 to your FactoryTalk View ME or FactoryTalk View SE projects. Both methods use OLE for Process Control (OPC) to communicate, but it is easier to use RSLinx Enterprise to create the necessary connections. This topic describes only how to use RSLinx Enterprise to produce those connections—for information about using RSLinx Classic to create those connections, see the FactoryTalk View ME or FactoryTalk View SE documentation.

Using RSLinx Enterprise to connect the emulator to an FactoryTalk View project requires installing RSLinx Enterprise on both the computer running the emulator and on the computer running FactoryTalk View.

RSLinx Enterprise uses FactoryTalk to automatically connect tags for Rockwell Software applications. Once RSLinx Enterprise is installed and configured, you do not need to configure anything else to use tags from the emulator in FactoryTalk View projects. Once a tag is used in RSLogix Emulate 5000, the tag becomes available to FactoryTalk View ME or FactoryTalk View SE.

Prerequisites

For FactoryTalk View SE projects, RSLinx Enterprise must be installed on both the computer running FactoryTalk View SE and the computer running RSLogix Emulate 5000, and both computers must be using the same FactoryTalk Directory. (If RSLogix Emulate 5000 and FactoryTalk View SE are installed on different computers, both computers must use the same network Directory.)

Tip: You can install RSLinx Enterprise and the FactoryTalk platform from your FactoryTalk View ME or FactoryTalk View SE installation disks.

For FactoryTalk View ME projects, RSLinx Enterprise, RSLogix Emulate 5000, and FactoryTalk View ME must be installed on the same computer. In this case, the FactoryTalk Directory used must be the local Directory (FactoryTalk View ME does not support using a network Directory).

The RSLinx Enterprise Module in the Virtual Chassis

When RSLogix Emulate 5000 runs on a computer that is also running RSLinx Enterprise, an RSLinx Enterprise module appears in the emulator’s virtual chassis. This module will occupy the first unoccupied slot in the chassis and cannot be removed (other than by uninstalling RSLinx Enterprise).

For example, if you install RSLinx Enterprise and then install RSLogix Emulate 5000 from scratch, the first time you open RSLogix Emulate 5000, slot 0 will be occupied by the RSLinx Classic module and slot 1 will be occupied by the RSLinx Enterprise module.

If you already have modules in your virtual chassis when you install RSLinx Enterprise, the RSLinx Enterprise module appears in the first empty slot.

How to 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.

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

Tip: 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.

How to Configure trace displays

When tracepoint and breakpoint instructions execute, the emulator opens a trace display. To configure how the emulator handles and displays traces:

1.      Display the emulator configuration.

2.      Refer to the following table for information about the settings available for traces.

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. (If you have a time stamp mode selected and you change it while a trace window is displayed, subsequent traces use the new time stamp mode.) None records no time information in the trace displays. Delta records the difference between the current trace and the last trace for that particular trace window. The first trace for the window always shows 0 milliseconds. Absolute records the time that the trace triggered. The time is in the number of milliseconds since the emulator was last changed to the Run mode.
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. (See Trace Log File, below.)
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. (See Trace Log File, below.)
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.

How to 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 immediately.

To set the speed of time:

1.      Display the emulator configuration.

2.      Set the speed of time using the controls illustrated in the following graphic.

3.      If you use the slider control or type a percentage, click the Confirm Time % Change button.

How to 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.