Diese Richtung ist meiner Meinung nach nicht vorgesehen, die andere (von ME nach SE) geht bedingt, da müssen aber auch ein paar Dinge ggf. von Hand angepasst werden. Ich habe da noch folgendes auf dem Rechner liegen:
A126845002 - ME to SE Conversion revision 4.0
Last Modified: 04/04/2006
Overview
Purpose
This document will outline how to reproduce some of the common RSView ME
functionality in an RSView SE application. Once the application has been converted
into RSVSE (import feature), there are some manual steps required to ensure that the
application maintains similar functionality.
As RSVME and RSVSE differ in their features and objects, some of these
workarounds may include different development methods (i.e. RSVSE objects, event
detector, derived tags, etc). However, the focus has been to reproduce similar runtime
functionality.
Relevant Software
RSView Studio Machine Edition 4.0 (used as "RSVME" within this document)
RSView Studio Supervisory Edition 4.0 (used as "RSVSE" within this document)
*This document is based on an RSVME 4.0 application imported into RSVSE 4.0
Stand-alone application.
Intended Audience
Is it assumed that the user of this document is quite familiar with the runtime
functionality of the RSVME application. It is also assumed that the user is familiar with
the editors and Command Wizard of RSVSE.
It is also assumed that the user is familiar with the new features available in RSVME
4.0 including RSAssetSecurity configuration.
Although this document describes some of the steps for workarounds, it is not a
complete resource. It is intended to assist the user that is familiar with RSVSE
features, but unsure how to apply them for the converted application. If further detail is
required, please refer to the help files or the Online User's manual for RSVSE.
Application Note
General Category: s HMI (Visualization)
Product(s): RSView Enterprise SE; RSView Machine Edition
Catalog #:
Series / Revision: 4.00 (CPR 7)
Subject
(Keyphrases):
Summary of
Technote
Information:
Application Note Technote: ME to SE Conversion revision 4.0 Page 1 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
RSLinx Enterprise Configuration
In RSVME, there are two tabs in the RSLinx Enterprise configuration; Local and
Target.
The Local configuration is unique to a computer (not the application) so it is not part of
the import into RSVSE. If the same computer (as used to configure the RSVME
application) is used for the RSVSE import, the same device configuration will exist.
However, the shortcuts will have to be recreated.
The Target configuration corresponds to the runtime computer. The Target
configuration is "offline" to development and is saved into the RSVME runtime file
(*.mer). There is no Target configuration in RSVSE, so this is not imported.
System
Project Settings
Although there is no single equivalent in RSVSE to the "Project Settings", these
settings can be reproduced. The RSVSE Client configuration will contain most of the
Project Settings, except for two (Project display size and project window position).
These features can be configured on a per display basis in RSVSE. Right-click on the
desired display and select Display Settings. Configure the display size and location.
If you would like the display to fill the desktop size, be sure to enable the Maximize
Window option in the Client configuration. Then, enable the Size to Main Window at
Runtime option on the desired displays.
User Accounts
RSVME and RSVSE 4.0 both include the new feature RSAssetSecurity with some
slight differences in how the functionality is deployed between the two products. In
RSVME 4.0 the user has the option to generate runtime file (*.mer) for previous
versions of RSVME (Multi-Version Support). As a result RSView Studio for RSVME
has the ability to configure security for both 3.x and 4.0 versions the product. Multi-
Version Support is not currently a feature of RSVSE and thus there is no option in
RSVSE 4.0 to configure 3.x style security. As a result some of the RSAssetSecurity
configuration screens used in RSVME will not contain the 3.x options when the project
is migrated to RSVSE.
During the migration from RSVME to an RSVSE Stand-alone application
RSAssetSecurity user accounts and user groups remain available as they reside
within the FactoryTalk Local Directory and not within each individual RSVME project.
RSAssetSecurity configuration information is not migrated into the RSVSE project. In
order to maintain the same functionality in the RSVSE project as users had in RSVME
users will have to assigned the traditional A-P security codes as they had within the
RSVME project along with specific permissions to resources within the FactoryTalk
directory that are now available within RSAssetSecurity configuration.
Application Note Technote: ME to SE Conversion revision 4.0 Page 2 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
(1) Please refer to the RSVSE Help section entitled "Setting up Security" for specific
instructions on setting up RSAssetSecurity.
It may be possible that some parts of the RSVME application were configured for use
with specific usernames (ex. Visibility animation, based on whether the logged in user
equals "Admin"). If this is the case, any use of the tag "System\User" must be
replaced by the function "CurrentUserName()". The tag "System\User" is contained
within the "System" folder for migration purposes but is not used/updated by RSVSE.
Diagnostic List Setup
The Diagnostic List Setup is not converted into the RSVSE project. This will need to
be reconfigured manually. In RSVSE, select Tools>Diagnostics Setup for
configuration of the runtime Diagnostics log.
There does not appear to be a method to send the Diagnostic messages to a printer
or to automatically open the Diagnostics log viewer during runtime, based on new
activity messages. However, there are other methods of viewing the activity logs.
(1) Create a push button using the "AppStart" command to open the FT Diagnostics
Viewer program ("C:\Program Files\Rockwell Software\RSView
Enterprise\ActivityLogViewer.exe")
(2) Use the activity bar at the bottom of the runtime project (also appears during
development). This activity bar can remain open all the time, and will display activity
messages as configured in the Diagnostics List Setup.
Global Connections
There is no equivalent to this editor in RSVSE. As such, these settings will not be
imported into the RSVSE application.
Refer to the section "Monitoring a Tag to Execute an Event" on how to reproduce this
tag monitoring functionality. The code listed in that section can be easily modified to
set tag values or to execute Macro files.
There is one feature that is hardware specific, and this is the "Remote Backlight
Intensity" property. As this feature applies to only the PanelViewPlus and the
VersaViewCE terminals, this property has no direct equivalent in RSVSE.
Startup
The RSVME Startup settings are not converted into the RSVSE application. These
settings can be reconfigured in the RSVSE Client configuration. If necessary, create a
startup macro in RSVSE to complete other startup tasks, assigning this macro in the
Client Configuration.
Tags
The tag database will import into the RSVSE application. There should be no required
changes to the communications or tags within the application.
Tag Database
Application Note Technote: ME to SE Conversion revision 4.0 Page 3 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
Although the RSVME tag database will be converted during the application import,
there are some things to note.
(1) Block Tags are converted, but cannot be edited.
(2) System\User is not available. Replace all instances with the function
CurrentUserName().
Graphics
This section will briefly describe the exceptions for importing RSVME displays into an
RSVSE application. Below each topic, a list will describe the change of features in the
RSVSE application.
Displays
- "Display Number" is not supported
- "Cannot be Replaced" is not supported
- "Disable Initial Input Focus" is not supported
- Default displays (ex. [ALARM], [ACTIVITY], and [INFORMATION]) are not imported
Object Features
- Caption text does not have word-wrap; A Carriage Return must be added to the
caption text
- Image Color does not exist in RSVSE; set the Pattern Color in the RSVSE object
Objects Not Imported (no SE equivalent)
- Pause
- Next Pen
- Alarm Acknowledge
- Alarm Acknowledge All
- Clear Alarm History
- Print Alarm History
- Alarm Silence
- Alarm List
- Alarm Status List
- Alarm Banner
- Alarm Status Mode Button
- Clear Alarm Banner
- Clear Activity
- Clear All Activity
- Reset Alarm Status
- Print Alarm Status
- Silence
- Sort Alarms
- Diagnostic List
- Diagnostic Clear Button
- Diagnostic Clear All
- Information Acknowledge
- Information Message Display
- Go To Configure Mode Button
- Return To Display (although a button is created, RSVSE does not directly support
this operation)
Application Note Technote: ME to SE Conversion revision 4.0 Page 4 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
String/Numeric Input Box
The major difference between ME and SE for this object is the visual appearance. To
reproduce the borders offered by the ME object you will need to manually create a
"Panel" object behind the RSVSE input box.
- Numeric Input Cursor Point converts into an RSVSE Numeric Input Box
- Does not import the "Number of Input Characters"; set the Width property (String)
- Does not have "Fill Character"
- Does not have "Optional Expression" (ex. Used to scale User input)
- Does not have Enter Handshaking
- Does not have "Image"
- Does not have "Audio"
- Does not have RSVME border properties
String/Numeric Display
- No Border (can manually create a Panel object in RSVSE to reproduce the borders)
- Displays Decimal points by default for Integers (Numeric)
- No word-wrap; must define characters and lines (String)
Display Navigation
- Go To button is converted into RSVSE (border properties are different)
- Return To button is converted, however it is not functional (no RSVSE equivalent).
Either delete this object or configure it to open a specific display.
- Close Display button is converted into RSVSE (border properties are different)
- Display List Selector is identical object as in ME.
Trend Display Object
- Pause button is not converted into SE. To reproduce in SE, open the Trend
properties dialog and select the Display tab. Enable "Display scrolling mechanism" to
show the trend control buttons (ex. Pause, scroll, Home, End, etc).
- Next Pen button is not converted into SE. To reproduce the functionality in SE, open
the Trend properties dialog and select the Display tab. Enable and configure the Line
Legend properties.
Advanced Objects
- Login and Logout buttons are converted into the RSVSE Button object.
- Display Print button is converted into the RSVSE Button object
- Macro button is converted into the RSVSE Button object
- Shutdown button is converted into the RSVSE Button object
- GoTo Config Mode button is not converted and is removed. There is no equivalent in
RSVSE, but a Button object with the "DisplayClientClose" command would be similar.
Libraries
Libraries are specific to the development PC, and the development software (i.e.
RSVME or RSVSE). As such, RSVME library displays must be manually imported into
RSVSE.
Application Note Technote: ME to SE Conversion revision 4.0 Page 5 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
One method to manually import a library display is to:
(1) Right-click on "Libraries" in the application tree
(2) Select "Add component into Project…"
(3) Navigate to and select the RSVME library display that you wish to import.
When an RSVME library display is imported, it will convert in the same manner as an
application graphic display. Refer to the above section "Displays" for information on
how the display settings and objects are imported.
Images
The RSVME image files are imported automatically with the application.
Parameters
Parameter files are converted during the application import. These files are the same
in RSVSE as they are in RSVME.
Local Messages
Local Message files are converted during the application import. These files are the
same in RSVSE as they are in RSVME.
Alarms
RSVME alarms will not import into the RSVSE application. Also, none of the RSVME
alarm objects are supported in RSVSE. All of the RSVME Alarm objects will have to
be manually recreated in RSVSE, using the Alarm Summary object.
In RSVSE, alarms are based on thresholds and are configured on a per tag basis in
the Tag Database editor. In RSVME, alarms are based on trigger values and are
configured on a per trigger (tag or expression) basis in the Alarm Setup. In order to
reproduce this functionality in RSVSE, each alarm message must be configured by
using thresholds in the RSVSE Tag Database editor.
Alarm Messages
In order to reproduce the RSVME alarm functionality, an alarm threshold will have to
be configured for each alarm message. To do this, create alarm thresholds that are
just below and just above the desired trigger value (ex. Use 1.9 and 2.9 as thresholds
for a trigger value of 2).
For Expression Triggers
(1) Create a memory tag (to hold the value of the alarm expression)
(2) Enable alarming for the tag (Tag Database Editor), and configure the alarm
thresholds as described in the below section "For Tag Triggers"
Ex. For expression values of 1, 2, and 3, you could use
threshold values of 0.9,1.9, and 2.9.
Application Note Technote: ME to SE Conversion revision 4.0 Page 6 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
(3) Open a new/existing Derived Tag file.
(4) Select the memory alarm tag created in (1), and add the alarm expression
(5) Save and close the derived tag file
(6) Create a new Macro that uses the "DerivedOn" command to start the Derived Tag
file.
(7) Assign the macro as the startup macro in the Client Configuration.
For Tag Triggers
(1) Open the Tag Database editor, and select the tag that you wish to configure
alarming for.
(2) Check the box beside the "Alarm" button, and an alarm dialog will appear.
(3) Select Threshold 1, and enter a threshold value slightly less then the intended
trigger value. Ex. For a trigger value of 1, enter 0.9
(4) Ensure that the "Increasing" option is selected and define any of the other alarm
options if desired.
(5) Continue to add thresholds for each required trigger value. Ex. For trigger values
of 2, 3 & 4 add threshold values of 1.9, 2.9, & 3.9.
(6) Once all the thresholds have been defined, add a final threshold that exceeds the
last trigger value. Ex. If the last trigger value is 4, add a threshold of 4.9
(7) Change the alarm severity of the last threshold to 8 (lowest severity). Close the
alarm dialog and accept the tag.
(8) Open the Alarm Setup editor, and select the Alarm Severities tab.
(9) Disable alarm logging for severity 8.
These workarounds will produce the RSVME alarm functionality. However, there are
some things to note about this method:
(a) Only 7 trigger values can be defined for a single tag. A new tag will be necessary
in order to allow for more than 7 trigger values.
(b) Only 7 alarm severities can be used for alarms, as the last one (8) is used for the
"closing" alarm threshold.
Alarm Setup
The Alarm Setup information is not imported into the RSVSE project. This information
will need to be manually entered into the RSVSE Alarm setup editor and on a per tag
basis under the HMI Tags. Also, any direct reference alarm triggers in RSVME will
need to be recreated as HMI Tags within RSVSE.
RSVSE does not directly support expression alarms. An equivalent is to create a
derived HMI tag from the RSVME trigger expression and then add alarming to the
HMI tag.
RSVSE does not support the Message To Tag functionality from the RSVME Alarm
Setup.
Also, some other steps are required if the Alarm display is to be opened based on
new alarms.
(A) One option to open the Alarm display automatically is to monitor every alarm tag
as described in the below section "Monitoring a Tag to Execute an Event".
(B) It may be less effort to monitor a single tag and have the programmable logic
controller change the tag's value when an alarm occurs.
Application Note Technote: ME to SE Conversion revision 4.0 Page 7 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
The second solution is only valid if the PLC can easily determine an alarm condition.
Otherwise, a combination of both solutions may be needed.
Information
There is no equivalent of the Information Messages in RSVSE. The Information Setup
configuration and the Information Messages will not be imported into the RSVSE
application.
The Information Message files can be manually imported, and the Information
messages functionality can be reproduced by creating a new display.
Information Messages
The Information Message files are not imported during the application import.
However, these files can be manually added to the RSVSE application as Local
Message files.
(1) Use Windows Explorer to manually change the extension of the Information
Message file from *.ifm to *.loc
(2) In the RSVSE application, right-click on Local Messages in the application tree.
Select "Add Component into Project…".
(3) Navigate to and select the *.loc file you modified in step (1).
Information Setup
The Information Setup configuration is not imported into the RSVSE application. In
order to reproduce this functionality in RSVSE, you will need to perform the following
steps.
(1) Create a display using the Local Message object, and assign the imported
Information Message file.
(2) Follow the steps in the section "Monitoring a Tag to Execute an Event" to trigger
the Information Message display, based on a tag (named Value tag in RSVME)
Logic And Control
The RSVME macros will be imported into the RSVSE application.
Macros
The RSVME macros will be converted into RSVSE macros. Essentially, they are the
same with a small syntax difference.
RSVME uses {} around tags names (when necessary) in the Macro file, however
RSVSE simply precedes the tag name with the ampersand '&'. You will notice this
difference in the RSVSE macro editor, as it displays the macro file in the text format
(RSVME displays the macro as a spreadsheet).
Data Log
The RSVME data log files will be imported into the RSVSE application.
Application Note Technote: ME to SE Conversion revision 4.0 Page 8 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
Data Log Models
The data log models will be imported into the RSVSE application with the following
exceptions:
- RSVSE Data log model does not have "Maximum Data Points" setting (Setup tab)
Workaround
In RSVSE, use the File Management tab to configure how data log files will be
created and deleted (based on time or event).
Monitoring a Tag to Execute an Event
This section describes how to monitor a tag for changes, and then execute events
(such as opening a display) based on the tag value.
Adapted from the RSVSE User Forum>Graphic Displays>"VBA does not run at client."
Written by Marc Semkow The VBA code in a graphic provides a means of
implementing this functionality. Follow these steps:
(1) Using RSView Studio, create a screen with a numeric or string display. The tag
used in this display object will be what tells the VBA code which command to execute.
(2) From the Edit menu select "Display Settings". Change "Cache after display" to
"Yes" and check "Always Updating".
(3) After creating the display object, right-click on it (ex. Object name is
NumericDisplay1) and select "VBA code". This launches the VBA editor and creates a
subroutine called " NumericDisplay1_Change"
(4) Add the following code to the subroutine:
On Error GoTo ObjectErrHandler
Select Case NumericDisplay1.Value
Case Is = 1
ExecuteCommand "display screen1"
Case Is = 2
ExecuteCommand "display screen2"
Case Is = 3
ExecuteCommand "display screen3"
Else
MsgBox NumericDisplay1.Value & " is not one of the tested values."
End Select
Exit Sub
ObjectErrHandler:
MsgBox "There is a problem with the screen selector tag. Verify communications."
When the tag being used in NumericDisplay1is set to the value 1, the first Case
condition evaluates true. This executes the display command and shows the specified
screen. The tag could be set by an event, or even in the data table of a PLC. Also, it is
highly recommended that this screen be loaded into memory when the client is
Application Note Technote: ME to SE Conversion revision 4.0 Page 9 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
launched using the command DISPLAY /ZA. This will allow the screen to continue
working even if the visible window is closed.
Global Objects
The RSVME Global Objects will be imported into the RSVSE application.
Language
The RSVME language switching functionality will be imported into the RSVSE
application.
RecipePlus
The RSVME RecipePlus functionality does not exists in RSVSE and will not be
imported into the RSVSE application.
Related Links:
DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such
subjects. Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services.
Before making any decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB
SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED
HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT,
INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY
OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING
SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NONINFRINGEMENT.
Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.
Copyright © 2006 Rockwell Automation. All rights reserved.
Application Note Technote: ME to SE Conversion revision 4.0 Page 10 of 10
http://domino.automation.rockwell.com/applications/kb/RAKB.nsf/0/02A8A377DC2BB87D85257... 10.04.2006
