Page 1 of 5 What's new? The following features have been added in RSLogix Emulate 5000 v17.00 (CPR 9 SR1): You can quickly change the mode (Program or Run), save the current state, and restore a previously stored state for one or more controllers at one time. When adding a module in the Chassis Monitor, only those modules that can be added to RSLogix Emulate 5000 v17.00 (CPR 9 SR1) are displayed: Emulator RSLogix Emulate 5000 Controller 1789-SIM 32 Point Input/Output Simulator RSLogix Emulate 5000 Release Notes The release notes for RSLogix Emulate 5000 v17.00 (CPR 9 SR1) contain information about the following topics: What's new? System requirements Product revision information Installation procedure Anomalies fixed Known anomalies Application notes Contact information Warning: Do not depend on the emulator to match your physical controller s performance or operation. Some instructions are interpreted differently in the emulator than in a physical controller, and the execution times for instructions and program files will be significantly different in an emulated controller than in a physical controller. System requirements Copyright 2008 Rockwell Automation Technologies, Inc. All rights reserved. v17.00 (CPR 9 SR1) Modified: 7/8/2008 7:37:43 You can run RSLogix Emulate 5000 v17.00 (CPR 9 SR1) on the following operating systems: Microsoft Windows 2000 with Service Pack 4 (recommended) Microsoft Windows XP Professional Edition or Microsoft Windows XP Home Edition with Service Pack 2 Microsoft Windows Server 2003 with Service Pack 2 or Microsoft Windows Server 2003 R2 with Service Pack 2 For RSLogix Emulate 5000 v17.00 (CPR 9 SR 1) to run effectively, the computer must have at least: Intel Pentium 4 1.6GHz (single core, dual-core, and hyperthreaded CPUs are supported) A minimum of 256 MB of RAM 150 MB of hard disk space free 800 X 600 video resolution Any Windows-compatible pointing device Product revision information RSLogix Emulate 5000 v17.00 (CPR 9 SR1) requires the following software product compatible versions: RSLinx Classic 2.50.00 or higher Note: RSLinx Classic 2.54.00 (CPR 9 SR1) is required if you want to position RSLinx Classic in a slot other
Page 2 of 5 than slot 0. See the RSLinx Classic online help for more information. RSLogix 5000 v12.00 (or higher) Note: To emulate a controller that has been released with a specific version of RSLogix 5000, the matching version of RSLogix 5000 is required. For example, if you want to emulate a v17 controller, you must use RSLogix 5000 v17. FactoryTalk Activation (CPR 9) or higher Installation procedure To install RSLogix Emulate 5000 v17.00 (CPR 9 SR1), perform the following steps: Note: RSLogix Emulate 5000 cannot be installed on any machine that already has SoftLogix5800 installed on it. Please use the "Add/Remove Programs" applet in the control panel to remove previous versions of SoftLogix5800. While performing an install or uninstall, please note any messages that recommend a system reboot. Failure to follow the reboot instructions can render your installation inoperable. Note: RSLinx Classic should be installed before installing the RSLogix Emulate 5000 product. If RSLinx Classic is installed after RSLogix Emulate 5000, please run the SIRegEDS.exe program that can be found in the RSEMU5000 directory on the installation CD. 1. Log onto the computer on which you want to install RSLogix Emulate 5000 as an administrator (or a user with administrative privileges). 2. Insert the RSLogix Emulate 5000 v17.00 (CPR 9 SR1) CD-ROM into the computer s CD-ROM drive. The setup program should start automatically. If it does not, open the CD-ROM drive with Windows Explorer and run the AUTORUN.EXE program on that drive. 3. The Setup program displays a menu of choices. Click Install RSLogix Emulate 5000. Please refer to the RSLogix Emulate 5000 Getting Results Guide for further details on installing this product. The RSLogix Emulate 5000 Getting Results Guide can be viewed with the Adobe Acrobat Reader by opening the file LGEM5K-GR016B-EN-E.pdf located at <CD-drive letter>\documentation on the RSLogix Emulate 5000 CD. Note: If you want to reinstall the same version as is currently installed, please use the "Add/Remove Programs" applet in control panel to remove the existing version of RSLogix Emulate 5000. While performing an install or uninstall, please note any messages that recommend a system reboot. Failure to follow the reboot instructions can render your installation inoperable. Note: After RSLogix Emulate 5000 and RSLinx Classic have been installed, you must first add the Virtual Backplane driver in RSLinx Classic in order to connect to the SoftLogix engine. Even if you plan to remotely program the controller over a ControlNet or Ethernet link, you must add the Virtual Backplane driver via RSLinx Classic software. If you do not, persistent storage will not function. Additionally, when you reboot the computer, the controller will come up with cleared memory (the program will not get re-loaded). Anomalies fixed The following anomalies have been fixed in RSLogix Emulate 5000 v17.00 (CPR 9 SR1): In previous releases, mathematical computations that included mixed data types produced different results in RSLogix Emulate 5000 and ControlLogix controllers. This has been resolved so that mathematical computations of mixed data types provide matching results. Known anomalies Keep the following known anomalies in mind when using RSLogix Emulate 5000 v17.00 (CPR9 SR1): Note: For additional information, you can also refer to the SoftLogix 5800 Release Notes. Even if you plan to remotely program the controller over a ControlNet or Ethernet link, you must add the Virtual Backplane driver via RSLinx Classic software. If you do not, persistent storage will not function. Additionally, when you reboot the computer, the controller will come up with cleared memory (the program will not get re-loaded). Data Execution Prevention (a feature of Microsoft Windows also known as DEP) is not supported by RSLogix Emulate 5000. If your computer's CPU supports DEP, we advise using DEP for only essential Windows programs and services. (This is the default setting for Windows XP; for Windows Server 2003, DEP is on by default for all programs and services.) If DEP is turned on for RSLogix Emulate 5000, you may experience unexpected results. See your Windows documentation for information regarding DEP.
Page 3 of 5 p ( ), p p subroutines in reverse order from the order in a physical controller (the last parameter is passed first in an emulated controller). Do not use JSR instructions in a manner where the order in which parameters are passed to a subroutine matters. If you make multiple online edits to a rung without assembling edits or cancelling edits between changes, rung logic can be stored incorrectly. While performing edits online to a RSLogix Emulate 5000 controller, it is possible to cause incorrect storage of rung logic, leading to unexpected execution of the rung. This situation can occur if you accept or test edits to a rung and then re-edit the rung logic without either assembling the existing edit or completely canceling the existing edit. The following steps can lead to incorrectly stored rung logic during an online edit: 1. Edit an existing rung (for example, add an XIO instruction). 2. Accept pending rung edits. 3. Test the accepted edits. The rung logic executes as expected. 4. Untest the accepted edits. 5. Start another edit on the same rung without assembling edits or cancelling edits (for example, change XIO to XIC). 6. Accept pending rung edits. 7. Test the accepted edits. The rung logic does not execute as expected. To avoid this anomaly, you must follow one of these recommendations: If you are not satisfied with an existing online edit, cancel edits prior to making additional changes to the same rung logic. If you are satisfied with an existing online edit, assemble edits prior to making additional changes to the same rung logic. Once this anomaly occurs, you must go offline and re-download the program to restore correct operation. A PI function block appears to stop executing (for example, the output does not change and instruction faults are not logged). Due to the use of the single-precision floating point values, it may be possible (depending on the values of WLD and KP) for the ITerm value to be small enough (for example, less than 0.0000001) and lost when adding to the ITerm,n-1. For more information regarding the PI instruction, see the Logix5000 Process Controls and Drives Instructions User Manual, Publication 1756-RM006. To verify that the timeout change is used by the controller, you must download the program to the controller after each change to the timeout variable. A Major Non-Recoverable Fault may occur when the following elements are present in the program: Within an SFC, a JSR instruction is used to jump to another SFC, also known as a nested SFC. One or more of the nested SFC instructions contains Simultaneous Branches. The Last Scan of Active Steps option (specified in the SFC Execution tab of the controller Properties dialog) is set to Automatic Reset. To avoid a Major Non-Recoverable Fault when these elements are present, set the Last Scan of Active Steps to Don t Scan or to Programmatic Reset. During the first scan of an SFC step, the Step.FS bit is set. In addition, the S:FS bit is set, which allows the logic in any associated actions to easily detect the first scan state. This behavior is useful when a subroutine that is called by multiple actions (actions that may be connected to other steps) is used. The first scan state can be detected without programming a reference to the tag of a specific step. Many function blocks contain internal data that must be initialized before the block can be used. One of the methods a block uses to determine if it should initialize is by evaluating the S:FS bit, which the function block identifies as the first scan following a prescan. Attempts to call an SFC routine either directly from a FOR instruction or indirectly via a JSR instruction originating from a FOR instruction can cause a Major NonRecoverable fault on the controller due to a system level access violation. To work around this anomaly, ensure that SFCs are never executed in the same control path after a FOR instruction. If you cannot ensure this to be the case, replace the role of FOR instructions with a manually constructed loop iterator when needing to employ SFCs in your application. If you do not specify X2 and Y2 parameters in an FGEN instruction when used with a RSLogix Emulate 5000 controller that has been upgraded to firmware revision 17, your program may not download to the controller. As a workaround, declare a dummy array with a size equal to 1 or more, for example, REAL DUMMY[1], and use that array for both the X2 and Y2 parameters. Additionally, make sure the XY2SIZE member in the backing tag is its default value of 0.
Page 4 of 5 An SFC R action continues to post-scan on the specified action. This anomaly only occurs if the SFC Last Scan of Active Steps option is set to Programmatic Reset or Automatic Reset. When the default, Don t Scan, is set, the anomaly does not occur. The intention of a reset action, type R, is to terminate the execution of another action that was previously stored. When configured as described earlier, the reset action causes logic to execute a final scan. The reset action does not check to verify that an action is stored before it completes the final scan. As a result, each time the reset action is scanned, the target logic will be scanned one last time. Observable behaviors that may result include: The timer of the stored action will continue to time even though the action is no longer active. The logic in the stored action will be executed in the configured mode. At Automatic Reset, non-retentive outputs are cleared. At Programmatic Reset the logic will execute. In this situation, the action logic checks for the final scan condition (action.a = 1 and action.q = 0) and performs some shutdown operations. This is the code that will be executed. When an InOut array is passed to any of the following instructions in the form of an array element (for example, array [0]), the instruction uses the AOI's parameter definition to compute its end address, not that of the InOut array passed in. Therefore, if the array's argument and parameter sizes do not match the array may only get partially processed. This anomaly may impact use of the following instructions: ARD, ARL, AWA, AWT, BSL, BSR, COP, CPS, DEDT, DDT, FBC, FGEN, FFL, FFU, FLL, GSV, LFL, LFU, MAOC, MAPC, MATC, MAVE, MCCM, MCCP, MCLM, MCSV, MCT, MCTP, MSTD, PXRQ, RMPS, SQL, and SSV. The RSLogix Emulate 5000 controller has the following restrictions: If your RSLogix Emulate 5000 controller experiences repeated minor faults, it may display a red X. This only happens in systems in which minor faults are repeatedly generated on each program scan. To avoid this, correct any programs that may cause repeated minor faults to occur. Running or stopping a Trend momentarily blocks the RSLogix5800 thread from executing. Depending on your application and system performance, this can affect motion by causing increased errors in axis position or velocity. Controllers containing programs that generate motion should be in Program mode when starting or stopping a Trend. Do not perform a download to a RSLogix Emulate 5000 controller in the chassis while another controller in the same chassis is running a motion application. Doing so can cause the motion application to glitch. Do not double-click the RSLogix Emulate 5000 button on the installation browser screen. This can cause two copies of the RSLogix Emulate 5000 installation procedure to launch. If two copies of the installation program start, you may not be able to perform a normal uninstall. If this occurs, you will see this error message when an uninstall is attempted: Failed to load dll: _UninstallTmp. If this situation occurs, you have to manually uninstall the program. The manual uninstall procedure is available as the P19762551 technical note document. For maximum portability across platforms, it is best to avoid mixed operand types between the destination and its inputs. If getting identical results for similar operations across languages is important to you, make sure to perform floating point operations. The tradeoff is that floating point operations come at a price in terms of performance. Other considerations exist as well (for example, how compatible your operands are with that of the I/O being used). See the following sections for more details on typed operations across Logix platforms and 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 (if necessary). In this example, n is converted to 800.0 and m is converted to 1000.0. The result of the operation is 0.8. That result then gets converted to an integer where rounding rules apply and the final destination value is 1. This difference between ladder and function block instructions applies to all Logix platforms. Function block instructions only perform floating point operations. Application notes The following application notes are available for RSLogix Emulate 5000 v17.00 (CPR 9 SR1): Placing an emulator controller in slot 0 using RSLogix 5000 Perform the following steps to place an emulator controller in slot 0 using RSLogix 5000: 1. Open your emulator controller project in RSLogix 5000. 2. Select File > Save As and export the emulator controller project to an.l5k file. Perform the following: a. In the Save in field, navigate to the location where you would like to save the file. b. In the File Name field, specify a file name. c. In the save as Type field, select RSLogix 5000 Import/Export File (*.L5K). When complete, click Save.
Page 5 of 5 ( p, p ), p p 4. Scroll through the content of the.l5k file until you find the MODULE section in the Local block. In this section, locate the Slot entry. Change the value from its current slot value to slot 0. When complete, click File > Save. 5. In RSLogix 5000, select File > Open. The Open/Import Project dialog appears. 6. Locate and select the.l5k file that you saved in step 5, and click Open. The Save Imported Project As dialog appears. 7. The.L5K file is highlighted in the File name field, and includes an.acd extension. Click Import. 8. Navigate to the I/O Configuration folder. You will see that the emulator controller now exists in slot 0. 9. Open RSLogix Emulate 5000. Select slot 0, right-click, and select Create. The Select Module dialog appears. 10. Select Emulator RSLogix Emulate 5000 Controller, and then click OK. The General dialog box appears. 11. Click Next, then click Finish. 12. Select Communications > Download. The Download dialog appears. Read the information, and then click Download. The controller project is downloaded to the emulator controller at slot 0. Tip: If you change the slot position of the emulator controller on the Controller Properties dialog to a slot position other than slot 0, you cannot later return the slot position to 0 on the Controller Properties dialog. To obtain these results, you must repeat the process defined earlier. This also applies if you convert from a real controller to an emulated controller. Contact information For information about all of the products available from Rockwell Software or for technical support, select one of the following: http://www.rockwellautomation.com/rockwellsoftware/ http://www.rockwellautomation.com/support/ http://www.rockwellautomation.com/knowledgebase/ If you cannot connect to the Internet or cannot find answers to your questions in this help file or on the Technical Support Web site, you can call Technical Support. Phone: 440-646-3434 in North America When you call you should be at your computer and be prepared to give the following information: the product version number the type of hardware you are using the exact wording of any messages that appeared on your screen a description of what happened and what you were doing when the problem occurred a description of how you tried to solve the problem Version information can be found on the Help > About... screen.