Cabling and adapter pinouts

Under Channel 0 emulation, the configured serial port on the computer running the software acts like the Channel 0 port on a processor.

The following diagram shows the basic cabling for Channel 0 emulation. On PLC-5 processors, Channel 0 is a 25-pin female connector (requiring a 25-pin male connector on the cable). The cabling is basically straight-through, with a null modem on one end of the cable.

For serial devices and computers with 9-pin serial ports, use the Rockwell Software C13 or C13B adapters. The following diagrams show the pinouts for these adapters.

To connect to Channel 0 of a SLC 500 processor, use a null-modem (transmit and receive lines are swapped on one end) nine-pin to nine-pin serial cable, available at most electronics stores.

What are Debug files..??

Debug files are files used to simulate the actions of I/O in your system. RSLogix Emulate does not recognize I/O, and therefore does not emulate I/O operations. If you need to simulate actions of I/O to increase the accuracy of your emulation, you will need to program these files.

Debug file strategies

Debug files can be the most powerful tools in RSLogix Emulate. This section provides some strategies for using and manipulating debug files.

When to use debug files

Debug files are ladder logic. Your program uses ladder logic to control a process; a debug file uses ladder logic to simulate the process.

Anytime your program acts on a specific sequence of events (e.g., parts coming down an assembly line), you can simulate the process by programming ladder logic in a debug file. The following is an example.

Let's suppose you have a process that monitors a part's progress down an assembly line. There is a bit in your process that controls the conveyor motor. You have proximity switches that trigger operations when a part reaches specific areas of the assembly line. A debug file can easily simulate the part moving down the assembly line.

The first rung is conditioned on the start button for the process. The process starts, and TR1 starts timing. The preset should be approximately the time to get a part to the first station.

When TR1 is done timing, the PROX_1 proximity switch turns on. Since the proximity switch is on, the process at station 1 should activate.

By expanding on this concept, you could emulate the movement of a part down the entire assembly line.

Emulating block transfer reads

By using debug files, you can emulate the activity of Block Transfer Read (BTR) instructions.

BTR instructions take a specific number of words from an I/O module, and place those words in an area of the processor's data table. Since there is no real I/O while emulating a process, BTR instructions have no data to read.

To emulate a BTR, place a Sequencer Output (SQO) instruction in a debug file. Program the SQO so that the destination address of the SQO is the same as the BTR's Data File address. Enter the test data into the source words of the SQO. (You might want to enter a few values that are out of range for your process to test how the ladder logic program handles the erroneous data.)

When the SQO is executed by the emulator, it passes the data to the BTR's Data File. Your process can then use the data. You can execute the SQO automatically by triggering it off the done bit (.DN) of a free running timer in the same debug file.

Emulating many inputs

You can use the SQO instruction to emulate inputs. Program an SQO with a destination address in the input data table file. This way, you can send entire bit patterns to the input words instead of changing the individual bits.

Note Remember that the inputs will remain in their last states while emulating. If you want to reset your inputs, you will need to reset them manually. You could use an FFL instruction for this purpose.

Emulating fault routines

The status and fault bits in the processor are used by RSLogix Emulate. If you have a fault routine or shutdown sequence in your ladder program, you can test it by generating a fault or shutdown signal in a debug file.

Limit your debug files

If you try to program a single debug file to simulate the inputs for your entire process, you could end up with a debug file that is larger than your entire ladder logic program! Try to break down your process into pieces and create debug files to handle each piece. As you debug the pieces of your ladder program, you can combine your debug files to test a larger portion of your ladder program.

Uploading and downloading with debug files

With all of these debug files in your project, you may wonder what happens when you download to your processors. What happens to the debug files? The programming software filters out debug files -- they are not downloaded to your processors. That's both a good thing and a bad thing: it's good that the processor doesn't get filled with debug logic that could mess things up, but it's bad that your debug files aren't saved online. When you upload from a processor into a project that has debug files, the debug files get overwritten.

You will want to save debug files in a separate ladder logic project, or save the debug files as libraries to load back into your project. See the documentation for your ladder logic editing software for information on saving projects to different file names and using program libraries. 

Emulation

Emulation is simulation of operation -- in the case of RSLogix Emulate, the software emulates a programmable logic controller. 

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.

Glossary

Breakpoint

Breakpoints stop your program when conditions you define become true. For example, you can set a breakpoint to stop execution when a particular rung executes. Breakpoints are very useful for debugging and troubleshooting.

Breakpoint hit

A hit is when a breakpoint condition goes true. Breakpoint hits cause RSLogix Emulate to stop executing your program, freezing the ladder logic and data table in the state that caused the breakpoint condition to become true.

Channel 0

Channel 0 is a special communications channel on certain programmable logic controllers that allow the controllers to send and receive serial communications data. RSLogix Emulate can emulate Channel 0 communications, allowing you to check out these communications through the software.

DBF files

DBF files are standard database files -- most database and spreadsheet packages can read and write this format.

Debug files

Debug files are files used to simulate the actions of I/O in your system. The software does not recognize I/O, and therefore does not emulate I/O operations. If you need to simulate actions of I/O to increase the accuracy of your emulation, you will need to program these files.

Emulate

Emulation is simulation of operation -- in the case of RSLogix Emulate, the software emulates a programmable logic controller.

Halt mode

Stops program execution. Identical to Program Mode.

Hit (breakpoint)

A hit is when a breakpoint condition goes true. Breakpoint hits cause the software to stop executing your program, freezing the data table in the state that caused the breakpoint condition to become true.

One-rung mode

Scans the program one rung at a time. Allows you to step through execution in one rung increments.

Program mode

Stops program execution. Identical to Halt Mode.

Single-scan mode

Goes through one program scan, then halts execution. Allows you to step through execution one scan at a time.

Watchdog timer

The watchdog timer is a processor function that makes sure your ladder logic programs do not take more than a specified amount of time to execute through a complete scan. If the watchdog timer expires before a program scan is complete, the processor sets a major fault. The software can emulate the function of the watchdog timer -- you can also turn off this feature.

Troubleshooting

Here are a few of the most common problems people have with RSLogix Emulate, and how to get around them.

Q. When I run a project in RSLogix Emulate, my system seems to slow down drastically. What's wrong?

A. The software runs your ladder logic projects as fast as it can. Sometimes, that means that the software will "take over" your computer's CPU. You can stop this from happening changing the Priority setting in the Emulation Settings dialog.

Q. Timers are not updating.

A. You may need to increase the priority of the running program. Change the Priority setting in the Emulation Settings dialog.

Q. The screen does not refresh fast enough.

A. You may need to increase the priority of the running program. Change the Priority setting in the Emulation Settings dialog.

Q. Why do I keep getting a "watchdog timer" fault? There isn't that much ladder logic in my project.

A. Because the software isn't the only program being run on your computer, the emulator runs projects slower than a programmable controller will run them. You can adjust the watchdog timer setting in the Fault Options dialog.

Q. RSLogix Emulate doesn't seem to perform exactly like my PLC-5 or SLC 500 processor.

A. The software does not perform all of the functions of a PLC-5 or SLC 500 processor. Check the Emulator exceptions list. If you are seeing behavior that can't be explained from that list, please contact Rockwell Software Technical Support.

Q. What's wrong with all my I/O instructions?

A. The software doesn't know about I/O. Most instructions having to do with I/O operations are not executed. Check the Emulator exceptions list. For a more detailed description about how the software works, see the What RSLogix Emulate does topic.

Q. Why can't I see emulated projects in RSLinx or WINtelligent LINX?

A. Make sure you have configured a communications driver for the RSLogix Emulate product you are using. See the Communications setup topic for more information.

RSLogix Emulate messages

The following is a description of many of the most common messages that can come from RSLogix Emulate 5 and RSLogix Emulate 500. If you get a message that is not listed here and you can't determine what you should do, call Rockwell Software Technical Support.

"This SLC500 program must be compiled before it can be emulated."

SLC 500 programs are compiled before downloading to processors. Use your ladder logic editor to compile the SLC 500 program before trying to emulate it.

"OLE initialization failed. Make sure that the OLE libraries are the correct version."

RSLogix Emulate was unable to initialize the OLE subsystem of Windows. You may need to reinstall Windows.

"This SLC OS is not currently supported."

The ladder logic project you are loading was compiled for an SLC 500 operating system that is not currently supported in RSLogix Emulate. Either recompile the logic for an earlier series and revision of the SLC 500, or contact Rockwell Software for a newer version of RSLogix Emulate.

"File Is Not SLC500"

RSLogix Emulate is unable to recognize the ladder logic file you are opening as a SLC 500 ladder logic file. Either the file is corrupt or it never was intended to be a ladder logic file.

"File is corrupt (bad data file, program file, or data file count)"

RSLogix Emulate detected corruption in your ladder logic file. Recompile the ladder logic and try again.

"The copy protection for RSLogix Emulate 500 (or RSLogix Emulate 5) cannot be found. This application does not have a DEMO mode, therefore, you will not be able to run this program without copy protection."

The copy protection system for the software has failed. Either the copy protection was never installed, or the protection files have been compromised in some way. You need to install the software according to the directions that came with it, or contact Rockwell Software Technical Support for assistance.

"Start Value Out of Range"

The value for the start rung cannot exceed the number of rungs in the program.

"Destination station X is a duplicate"

The station number you entered has to be unique -- just as if you were working with a Data Highway Plus or Data Highway 485 network.

"Destination station must be specified"

You need to specify a destination station number. The number must be unique.

"Main File Must Be Ladder"

You cannot set the main program file to be anything other than a ladder logic file.

"Debug File Must Be Ladder"

You cannot set the debug program file to be anything other than a ladder logic file.

"Invalid Customer Registration Information, Verify the Program Installation."

Make sure you have installed RSLogix Emulate correctly. If you still get this error, call Rockwell Software Technical Support for assistance.

"The maximum number of users has been reached. See your network administrator."

On a network installation of RSLogix Emulate, there is a maximum number of people who can use the software at any given time. Check with your network administrator to make sure that there are not too many people using the software -- if there are, you may need to purchase additional RSLogix Emulate licenses. If there are not too many people using the software at one time, there may be a problem with the installation.

"This Program contains an unsupported instruction X in file Y rung Z"

RSLogix Emulate detected an instruction it did not understand at the specified program file and rung number. You may need a newer version of RSLogix Emulate, or your ladder logic program may be corrupt.

"Station number out of range (0-31) (or 0-77 octal)"

Data Highway 485 station numbers are limited to 0-31. Data Highway Plus station numbers are limited to 0-77 (octal). Enter a station number in that range.

"The Trend file address is invalid"

The trend file you are trying to use with your project contains an address that is not in your ladder logic project.

"The Trend file address type is invalid, or doesn't match the processor"

The trend file you are trying to use with your project contains an address type that is invalid for the SLC 500 model you are using.

"The Trend file is larger than the destination can hold"

You are trying to read in a trend file that is too large. You can edit the trend file to make it smaller.

"Record number out of range"

You asked for a trend file record that is not in the trend file.

"OLE 2.01 initialization failed"

RSLogix Emulate was unable to initialize the OLE subsystem of Windows. You may need to reinstall Windows.

"Main File Value Out of range (2-255)"

You tried to enter a main file number outside the range available for SLC 500 processors.

"Debug File Value Out of range (2-255) or 0 to Disable"

You tried to enter a debug file number outside the range available for SLC 500 processors.

"File Number out of range (2-255)"

The file number in question is outside the range available for SLC 500 processors.

"File Doesn't exist"

The file number you entered does not exist.

"File Must be LADDER"

The file number you entered is not a ladder logic file.

"Invalid Rung Number"

The rung number you entered does not exist in your ladder logic program.

"Rung Number is out of range (0-X)"

The rung number you entered does not exist in your program file.

"DH station and Emulation station must NOT be the SAME"

RSLogix Emulate and each emulated ladder logic project must have a unique station number.

"An Unknown Fault Has Occurred"

RSLogix Emulate experienced a fault that it does not recognize. Call Rockwell Software Technical Support for assistance.

"An attempt was made to execute an invalid Program file"

RSLogix Emulate tried to execute your project, but found a program file that it could not interpret. Either the program file is corrupt (in which case you should recompile your project), or you need a newer version of RSLogix Emulate (in which case you should call Rockwell Software Technical Support).

"An attempt was made to execute an invalid Opcode"

RSLogix Emulate tried to execute your project, but found an instruction that it could not interpret. Either the program file is corrupt (in which case you should recompile your project), or you need a newer version of RSLogix Emulate (in which case you should call Rockwell Software Technical Support).

"An Invalid direct instruction parameter was decoded"

RSLogix Emulate tried to execute your project, but found an instruction that contained an address it could not interpret. Either the program file is corrupt (in which case you should recompile your project), or you need a newer version of RSLogix Emulate (in which case you should call Rockwell Software Technical Support).

"An Indexed address was out of range"

The result of processing an indirect address resulted in a direct address that does not exist in the ladder logic project. This is a major fault. Use boundary tests before executing instructions containing indirect addresses.

"A File POS value was out of range"

A file address using a position word (.POS) was out of range -- the position specified for the file does not exist. This is a major fault. Use boundary tests to help trap this condition.

"A File LEN value was out of range"

A file address using a length word (.LEN) was out of range -- the length specified for the file does not exist. This is a major fault. Use boundary tests to help trap this condition.

"A NEGATIVE Timer Accum value was encountered"

A timer accumulator value (.ACC) was set to a negative value. This is a major fault. If you are writing values into a timer accumulator address, use boundary tests to make sure you are not writing a negative value.

"Rung contains too many nested branches"

Nested branches may be only eight levels deep. Exceeding eight levels deep faults the processor.

"A Breakpoint was executed"

A breakpoint you set executed, halting program execution.

"The Watch Dog Timer (S28) has timed out"

This is a major fault. The ladder logic project has taken too long to execute. You can adjust how RSLogix Emulate handles the watchdog timer in the Emulation Settings dialog.

"Too many nested subroutine calls (8 MAX)"

You can nest only up to eight subroutine calls. Any more than that results in a major fault.

"No LBL was found for a JMP instruction"

Your ladder logic contains a jump (JMP) instruction for which there is no label instruction (LBL). This results in a major fault.

"Minor Fault was set at end of scan"

A minor fault bit was set at the end of the program scan. This results in a major fault. You may need to test for and correct minor faults in your ladder logic.

"Invalid presets loaded to HSC"

There is a high-speed counter (HSC) instruction in your ladder logic with invalid presets. This results in a major fault.

"Index address outside of data file space"

An indexed address resulted in a direct address outside of the currently defined data table. This is a major fault. You may need to perform boundary tests to make sure your indexed addresses are valid before executing instructions involving them.

"Indirect element reference exceeds data file length"

An indirect address element resulted in a direct address outside of the currently defined data table. This is a major fault. You may need to perform boundary tests to make sure your indirect addresses are valid before executing instructions involving them.

"Indirect subelement reference of I/O slot does not exist"

A reference to an I/O address made indirectly results in a slot number that does not exist. This is a major fault. You may need to perform boundary tests to make sure your indirect addresses are valid before executing instructions involving them.

"The Ladder file you are trying to emulate is corrupt. There is no status file(data file 2). Use your Ladder Editor to fix the corrupted file."

The ladder logic file you are trying to emulate contains no status file. You will need to create one using your ladder logic editor before you can emulate the file.

"Unable to open COMx for Channel 0 Emulation "

The COM port you selected for Channel 0 emulation is currently being used by another software package or device. Choose another COM port.

"No NXT was found for a FOR instruction"

There was a Next instruction (NXT) without a corresponding For instruction (FOR). This is a major fault.

"An INDEXED (S24) Address was outside the file limits"

An indirect address resulted in a direct address outside of the currently defined data table. This is a major fault. You may need to perform boundary tests to make sure your indirect addresses are valid before executing instructions involving them.

Data Highway 485/DF1 emulation

When you run RSLogix Emulate software, you can place your computer on a simulated DH485 (for SLC 500 emulation) or DF1 (for PLC-5 emulation) network, connecting it with a computer running operator interface software such as RSView. With this setup, you can test your operator interface before connecting it to a physical processor. (If you want to simulate using Channel 0 with ASCII devices, see the Channel 0 emulation topic.)

To use Data Highway 485/DF1 emulation:

1. Set the station number for your project to 1. To do this, click Settings > Emulation, then set the Station # field to 1. (The DF1 or DH 485 emulation will not work unless the station number is set to 1.)
2. Connect a serial cable (a straight-through cable) to connect one of your computer's serial ports (COM ports) to a COM port on the computer running the operator interface software.
3. In RSLogix Emulate, click Settings > Channel 0 Data Highway. The software displays a dialog allowing you to set up a COM port to simulate communications.
4. From the Port listbox, select the COM port you want to use. (Make sure the COM port you choose is not occupied by another device, such as a mouse.)
5. From the Baud listbox, select the communication speed for your connection. You should select the same speed as the connection between the operator interface computer and the physical processor.
6. From the Parity listbox, select the parity for the connection. You should use the same parity as the connection between the operator interface computer and the physical processor.

Playing trends

One of the most powerful features of the software is the play trend feature. This feature allows you to take data gathered from your process, and see what would happen if you change your ladder logic or other address values.

The play trend feature "feeds" data to the software from .DBF files, replaying the processor's actions in response to the data. You can then monitor your ladder logic, looking for the effects of your changes.

Caution: While the software's play trend feature is useful for examining scenarios involving changes to ladder logic programs, you must not rely solely on your findings from the software to make changes to your process. RSLogix Emulate does not exactly simulate all the functions of a processor. The software does not run at the same speed as your processor, has differences in floating point calculations, and other differences that make it imperative that you carefully consider any changes you make to your process based on findings from a simulation.

Once it's set up, the trend player is as simple to operate as a tape player.

Setting up the trend player

Here's how to set up the trend player feature of RSLogix Emulate:

1. Obtain a .DBF format file from your process.
2. In RSLogix Emulate, load the project into which you want to play a trend.
3. In RSLogix Emulate, click Ladder > Play Trend. RSLogix Emulate displays the trend player dialog.
4. You need to tell RSLogix Emulate where the .DBF file is, and other parameters for your simulation. To do this, click the Setup button. RSLogix Emulate displays the trend player setup dialog.
5. Click the Open button. RSLogix Emulate opens a file selection dialog, allowing you to select a .DBF file to use in the simulation. Select the file you wish to use, and click the OK button.
6. If you like, you can set up the trend player to start and stop at any record number you like. To do this, type record numbers in the Start Play At and Stop Play At fields. By default, the trend player starts at record 0 (the first record) and ends at the last record in the .DBF file.
7. You can adjust the rate at which the trend player feeds data to RSLogix Emulate by moving the Playback slider bar. Moving the slider to the right increases the rate, and moving it to the left decreases the rate.

Note The rate at which RSLogix Emulate performs depends on several factors, including: CPU speed, number of applications running, and memory in your computer.

Assigning addresses in the trend player

If your .DBF file does not contain address information, you must assign addresses to the .DBF file records for the trend player to work.

To assign addresses:

1. In RSLogix Emulate, open the ladder logic project into which you want to play data.
2. Set up the trend player with the .DBF file containing the data you want to play into the project. .
3. From the trend player setup dialog, click the Address button. The software displays the Edit Trend Item Addresses dialog.
4. Click the first address you want to change, and click the Edit button. The address appears in the Assigned Address field at the bottom of the dialog.
5. Type the new address in the Assigned Address field, and click the Save button.
6. Repeat steps 4 and 5 for the remaining addresses you want to redefine.

Trend player controls

The trend player tells you the record number currently being played, and the time stamp on the record (from the .DBF file).

Starting the playback

To start a playback, click the start/restart playback button. The playback will run until the trend player runs out of records in the .DBF file, or until you stop or pause the playback.

Stopping the playback

To stop the playback, click the stop playback button. This stops playback and "rewinds" the trend player back to the first record in the .DBF file. To stop momentarily, click the pause playback button.

Pausing the playback

To pause the playback, click the pause playback button. This stops the playback, and leaves the trend player ready to resume playback at the .DBF file record where you paused it. To resume playback, click the start/restart playback button.

Moving through the .DBF File

You can "rewind" and "fast forward" through the .DBF file by clicking the reverse one record and forward one record buttons. Each click of these buttons moves the trend player back or forward one record in the .DBF file.

Breakpoints

To work with breakpoints , click Ladder > Breakpoints.

Breakpoints are defined by file number, rung number, whether the rung should be true or false, and the number of times the rung is true or false (Count).

Setting breakpoints

To set a breakpoint:

1. Click Ladder > Breakpoints. The software displays the Breakpoints dialog.
2. Click Add New.
3. In the File field, type the number of the ladder file in which you want to set the breakpoint.
4. In the Rung field, type the number of the rung for which you want to set the breakpoint.
5. In the Count field, type the number of scans you want to occur with the rung in the state you select. For instance, if you want to "hit the breakpoint when the rung is true for 40 scans, type 40 in the Count field.

Note This doesn't mean the rung must scan with the same condition consecutively. For instance, if you set a TRUE breakpoint with a count of 40 on a rung that goes true once per minute, the breakpoint would hit after 40 minutes.

6. From the list box under the Count field, select the state you want to examine with the breakpoint. For instance, if you want to count when the rung is true, select TRUE.

TRUE	when the rung is true
FALSE	when the rung is false
ANY	when the rung is scanned, regardless of the state of the rung

Example:

Rungs are considered TRUE when there is logical continuity from the beginning of the rung to at least one output. The examples below show how some rungs are assessed by RSLogix Emulate. The gray squares indicate which instructions evaluate as true.

7. Click Save. The software moves the breakpoint into the breakpoint list.

Editing breakpoints

To edit a breakpoint:

1. Click the breakpoint you want to edit.
2. Click Edit. The software moves the parameters for the breakpoint into the fields at the right of the dialog.
3. Edit the breakpoint's parameters. When you are through editing, click Save to save the changes.

Enabling and disabling breakpoints

You can disable breakpoints so that they are still in place, but will not stop program execution. To do this, click the breakpoint you want to disable, and click Toggle. The active/inactive state of the breakpoint is shown in the state column in the breakpoint list: A indicates an active breakpoint, and I indicates an inactive breakpoint.

Deleting breakpoints

To delete a breakpoint, click on the breakpoint you want to delete, then click Delete. The breakpoint is deleted.

Channel 0 emulation

The software's Channel 0 emulator can help you debug the interface between your ladder logic program and a serial device connected to Channel 0 of an Enhanced PLC-5 or SLC processor. The emulator uses your computer's serial ports to emulate the port. (If you want to use a serial port to simulate Channel 0 as a DF1 or DH-485 port, see the Data Highway 485/DF1 emulation topic.)

Caution: RSLogix Emulate software does not support uploading from the emulator using another computer through an emulated Channel 0 port. Doing so may corrupt the emulated ladder logic program.

Configuring Channel 0 emulation for use with a serial device

To emulate Channel 0 connections to a serial device, you must configure one of your computer's COM ports to emulate Channel 0. To do this:

1. Click Settings > Channel 0 ASCII Instructions. The software displays the Channel 0 ASCII Instruction Settings dialog.
2. From the Port list box, select a COM port to connect to the serial device. Make sure you don't select a COM port that is used by another serial device (such as your mouse or other pointing device). Selecting None disables Channel 0 emulation.
3. From the Baud list box, select the baud rate (communication speed) for the port. Make sure the baud rate matches that of the serial device you are connecting to your computer.
4. From the Parity list box, select the parity mode you want to use with the port. Make sure the parity setting matches that of the serial device you are connecting to your computer.
5. There are two sets of radio buttons underneath the list boxes. These are used to select the number of bits in each packet, and how many stop bits are in each packet. Click the settings that match the settings on the serial device you are connecting to your computer.
6. Click OK. The software is now prepared to use the COM port as if it was Channel 0 while it emulates your ladder program.

Strategies for using Channel 0 emulation

In general, you should start Channel 0 emulation before attempting to communicate with your serial device.

Remember that the software scans a single main program file at a time. That program file and any subroutines it calls will be executed. Other files will not be scanned. If you are not communicating with your serial device, verify that the read and write instructions are actually being scanned.

Channel 0 emulation should work whether a debug file is defined or not. You can even change debug files without disturbing Channel 0 emulation. If you wish, you can specify blocks of program file and debug files to emulate, and Channel 0 emulation will still function normally.

Debug operations

Since there is no real I/O when emulating a ladder logic project, you can create and edit special program files to simulate the I/O. These files are called debug files . Debug files emulate a piece of your process, simulating inputs to your ladder logic program.

Use Rockwell Software ladder logic editors to create debug files. These editors include:

• RSLogix 500 (for SLC 500 projects)
• RSLogix 5 (for PLC-5 projects)
• WINtelligent LOGIC 5 (for PLC-5 projects)
• A.I. Series Ladder Logistics (for PLC-5 or SLC 500 projects)

Creating debug files

You create debug files with your ladder logic editing application. Rockwell Software applications for editing ladder logic all support creating debug files. For information about creating debug files with your ladder logic editing software, please see the documentation for that software package.

Select debug files for emulation

You can select which debug file you want to use with the emulation session. You can select the debug file when you first open the ladder logic file in RSLogix Emulate, or you can define it later. You can also change the debug file as RSLogix Emulate scans the ladder logic. You can have multiple debug files defined in your ladder logic program, but you can use only one at a time.

To specify which debug file you want to use:

1. Click Settings > Emulation. The software displays a configuration dialog.
2. In the Debug File # field, type the number of the debug file.
3. In the Start Rung field, type the number of the first rung to scan in the debug file.
4. In the End Rung field, type the number of the last rung to scan in the debug file.
5. Click the OK button. The software uses the new settings for the debug file.

Observing and tracing faults

The software acts as if it was a processor, down to telling you if the program faults. When the software detects a program fault, it displays a fault dialog.

The fault dialog indicates:

• which program file had the fault (the name of the program is displayed in the title bar of the dialog)
• the type of fault (in this case, the watchdog timer timed out)
• the location of the instruction that was executing when the fault occurred (program file, rung number, instruction)

You can keep the dialog on-screen as long as necessary to trace the fault in your ladder logic. When you have recorded where the fault occurred, click OK to close the dialog.

When a fault occurs, and you are online with the ladder logic through PLC-500 A.I. Series, PLC-5 A.I. Series, RSLogix 5, RSLogix 500, or WINtelligent LOGIC 5, you can trace the fault as if you were online with a processor, using the processor status displays to track the fault to its source, and clear the fault.