RSEmulate5000RN_v16.txt RSLogix Emulate 5000 V16 Release Notes 13 August 2007

Transcription

1 RSLogix Emulate 5000 V16 Release Notes 13 August 2007 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. This readme file contains information on the following: * System Requirements * Product Revision Information * Installation Procedure * Technical Information * Known Anomalies * Contact Information System Requirements: Base Platform Requirements: * 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 Operating System: * Microsoft Windows 2000 with Service Pack 4 (recommended) * Microsoft Windows XP with Service Pack 1 or higher (recommended) * Microsoft Windows 2003 Server * Note: RSEmulate 5000 V16 does not support Windows Vista Product Revision Information: * RSLogix Emulate 5000 Version requires the following: * Software Product Compatible Versions: * RSLinx or higher * RSLogix5000 Version Installation Procedure: Product Installation: Begin the installation of the product by running the setup.exe file located at the root of the CD media. This will launch a CD browser that provides a means to install the RSLogix Emulate 5000 product, and also displays pertinent product information. Please use the "Add/Remove Programs" applet in 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. 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 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. Please refer to the RSLogix Emulate 5000 Getting Results Guide for details on installing this product. This document can be viewed with Adobe Acrobat Reader by opening the file LGEM5K-GR016A-EN-P.pdf located at <CD-drive letter>\documentation on the RSLogix Emulate 5000 CD. IMPORTANT: Page 1

2 RSLogix Emulate 5000 cannot be installed on any machine that already has SoftLogix5800 installed on it. 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. After the products are installed, you must first add the Virtual Backplane driver in RSLinx Classic in order to connect to the RSLogix Emulate 5000 engine. Technical Information: Refer to the RSLogix Emulate 5000 Getting Results Guide for more information about using this product. This document can be viewed with the Adobe Acrobat Reader by opening the file LGEM5K-GR016A-EN-P.pdf located at <CD-drive letter>\documentation on the RSLogix Emulate 5000 CD. Known Anomalies: IMPORTANT: A situation exists that causes CPR 6 RSView ME/SE and FTAP to fail to operate correctly when FTA installs CPR 7 Diagnostics on the same computer. A Tech Note and patch will be made available as soon as possible. The tech note will also state that the preferred solution is to update the affected products (RSView ME/SE and FTAP) to CPR 7. If you are unable to do so, the patch can be used to fix the problem. 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 and 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 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. Jump to Subroutine (JSR) instructions do execute in the emulator. However, the instruction passes parameters to 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. RSLogix Emulate 5000 V16 specific issues: (also refer to the SoftLogix 5800 Release Notes) Making multiple online edits to a rung, without performing an assemble edits or cancel edits between changes, can cause rung logic to 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 the user accepts or tests edits to a rung and then re-edits 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. Add an XIO instruction. 2. Accept pending rung edits. 3. Test accepted edits. 4. Rung logic executes as expected. 5. Untest accepted edits. 6. Start another edit on the same rung without assembling edits or performing a cancel edits (change XIO to XIC, etc.) 7. Accept pending rung edits. Page 2

3 8. Test accepted edits. 9. Rung logic does not execute as expected. Temporary Workarounds - 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, the user must go offline and re-download the program to restore correct operation A PI function block appears to stop executing as the output does not change and no instruction faults are 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, less than , to be 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 16, 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. 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 above, 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. Page 3

4 * 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 instructions listed below in the form of an array element (e.g., 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 on 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 P 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 such as how compatible your operands are with that of the I/O being used, etc. See below for more details on typed operations across Logix platforms and across languages. Keep in mind the following when performing typed operations: Due to the fact that the RSLogix Emulate 5000 family is based on open systems technology, the controller performs computational operations much the same way as open systems platforms and tools do it. This becomes important when performing mixed typed operations such as dividing two integers and storing the result in a real. Integer operations typically truncate the rational portion of a computation result while floating point operations preserve it. For example, when a RSLogix Emulate 5000 program performs a = n / m where the data types for a, n, and m are real, integer, and integer respectively, this specifies an integer divide between n and m and places the answer into a, performing an integer to real conversion. If n = 800 and m = 1000, the result is 0 and gets stored into a as 0.0. Alternatively, when a ControlLogix program performs the same a = n / m where the data types for a, n, and m are real, integer, and integer respectively, this specifies a floating point divide between n and m and places the answer into a, with no conversion needed. If n = 800 and m = 1000, the result is 0.8 and gets stored into a as 0.8. In RSLogix Emulate 5000, the input operand types dictate the operation while in ControlLogix, if any of the operands are real, a floating point operation is performed. RSLogix Emulate 5000 performs the operation exactly like a C routine would. 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 Page 4

5 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 and m is converted to 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. 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 16, 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 the Y2 parameters. Additionally, make sure the XY2SIZE member in the backing tag is its default value of 0. Contact Information: If you have any problems installing or running this software, please contact: Rockwell Automation Technical Support Phone: WEB: Page 5