VW32-UM001D-EN-E 5/1/07 4:12 PM Page 1 RSView 32 ® USER’S GUIDE PUBLICATION VW32-UM001F-EN-E–July 2011 Supersedes Publication VW32-UM001E-EN-E
Contact Rockwell Customer Support Telephone — 1.440.646.3434 Online Support — http://support.rockwellautomation.com Copyright Notice © 2011 Rockwell Automation Technologies, Inc. All rights reserved. Printed in USA. This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation Technologies, Inc. is strictly prohibited.
Contents Preface About the documentation ............................................................................ P-1 Technical support services ........................................................................ P-2 When you call ............................................................................................................... P-2 Chapter 1 Working with projects What is a project? .............................................................................................
Chapter 2 Setting up direct driver communications Overview of direct driver communications .....................................2-1 Communication channel..............................................................................................2-2 Communication device ................................................................................................2-2 Communication driver.................................................................................................
Chapter 3 Setting up OPC and DDE communications Overview of OPC communications ........................................................ 3-3 Overview of DDE communications ........................................................ 3-4 Summary of steps.............................................................................................. 3-5 Creating an OPC node .................................................................................... 3-5 Creating a DDE node ..................................
Using the spreadsheet................................................................................. 4-11 Moving through the spreadsheet............................................................................. 4-11 Resizing columns and rows...................................................................................... 4-11 Adding a tag................................................................................................................ 4-12 Duplicating a tag .........................
Chapter 5 Creating derived tags How to use derived tags............................................................................... 5-1 How to use multiple derived tag files ................................................. 5-2 Summary of steps.............................................................................................. 5-2 The Derived Tags editor ............................................................................... 5-3 Using the Accept and Discard buttons ...................
The Alarm Setup editor ............................................................................... 6-23 Specifying where to store alarm log files ...................................... 6-24 Creating log files.............................................................................................. 6-25 Monitoring disk space............................................................................................... 6-26 Creating files periodically..................................................
Creating an alarm summary..................................................................... 6-54 Creating an alarm summary file ............................................................................... 6-55 Creating an alarm summary object.......................................................................... 6-55 The parts of an alarm summary............................................................................... 6-56 Inserting headings...................................................
Example of short file names for narrow .dbf format .............................................7-7 Example of short file names for wide .dbf format..................................................7-8 The ODBC storage format ............................................................................7-8 How ODBC tables are named....................................................................................7-9 Using an existing ODBC data source..........................................................
Editing the data log model ........................................................................ 7-41 Changing logging paths using RSView32 Runtime .............................................. 7-41 Changing logging paths using the DataLogPath command................................ 7-42 Making runtime changes without editing the data log model ........................................................................................................................
Using the Activity Log Viewer ............................................................... 8-17 Selecting a record....................................................................................................... 8-18 Understanding records.............................................................................................. 8-19 Tracking system usage .............................................................................................. 8-19 Starting and stopping activity logging ...
Configuring security codes....................................................................... 10-4 Security codes ............................................................................................................. 10-5 The default .................................................................................................................. 10-5 Setting up security by inclusion ...............................................................................
Chapter 11 Creating graphic displays About graphic displays and graphic objects ............................... 11-1 The Graphic Display editor ....................................................................... 11-2 The editor’s main components................................................................................ 11-2 Mastering basic techniques .................................................................... 11-3 Using the context menu...................................................
Displaying graphics more quickly...................................................... 11-27 Removing displays from the cache ....................................................................... 11-28 Types of graphic objects .......................................................................... 11-28 Creating simple objects ............................................................................ 11-29 Drawing a rounded rectangle..................................................................
Replacing text associated with objects ....................................... 11-67 Creating and editing OLE objects ...................................................... 11-69 Other methods for inserting OLE objects .......................................................... 11-71 Converting OLE objects ........................................................................................ 11-71 Creating and editing ActiveX objects .............................................
Peeking at objects ...................................................................................... 11-105 Creating a background for your display ...................................... 11-107 Objects that cannot be converted ....................................................................... 11-107 Importing graphic files from third–party applications ...... 11-108 Transparent backgrounds for image files...........................................................
Configuring color animation .................................................................. 12-13 The parts of the list box ......................................................................................... 12-14 Configuring fill animation ........................................................................ 12-18 Configuring horizontal position animation .................................. 12-20 Configuring vertical position animation ........................................
Editing display and object keys .......................................................... 12-56 Modifying a key ........................................................................................................ 12-57 Removing a key ........................................................................................................ 12-57 Removing all keys .................................................................................................... 12-57 Viewing the key list at runtime ....
Creating a legend...................................................................................................... 13-16 Pen configuration .......................................................................................... 13-18 Configuring the tag or value .................................................................................. 13-18 Configuring pen style .............................................................................................. 13-19 Configuring pen scale........
Creating expressions .................................................................................... 14-3 Expression buttons.................................................................................................... 14-4 Cutting, copying, and pasting expressions................................... 14-4 Formatting expressions .............................................................................. 14-6 Using the = (Equal) command............................................................
The tools ................................................................................................................ 15-7 Precedence .................................................................................................................. 15-7 Creating macros ............................................................................................... 15-7 Using parameters .....................................................................................................
Creating a pivot table in Microsoft Excel .................................... 16-19 Starting the PivotTable Wizard.............................................................................. 16-20 Selecting the data source......................................................................................... 16-20 Joining tables and selecting data ............................................................................ 16-22 Organizing the pivot table...............................................
Chapter 18 Running your project Summary of steps ........................................................................................... 18-1 Specifying startup settings ...................................................................... 18-1 Preferences.................................................................................................................. 18-3 Startup .........................................................................................................................
Appendix B System tags Alarms ........................................................................................................................B-1 Communications ................................................................................................B-2 Graphics ...................................................................................................................B-4 Time .............................................................................................................
Trends ........................................................................................................................C-8 ControlView features integrated into RSView32 .......................C-8 Appendix D Addressing syntax for Allen–Bradley programmable controllers PLC addressing syntax ................................................................................. D-2 SLC addressing syntax ...............................................................................
P Preface Thank you for choosing RSView32™. RSView32 is an integrated package for developing and running automation applications.
Technical support services If you have questions about RSView32, please consult the user’s guides or the Help. If you can’t find the answer, contact Rockwell Software Technical Support at: Telephone: 440–646–3434 Internet Support: www.rockwellsoftware.com or www.support.rockwellautomation.com Support staff are available Monday to Friday from 8 A . M . to 5 P . M . Eastern Standard Time, except during holidays.
1 Chapter Working with projects This chapter describes: files and components adding, renaming, removing, and deleting components printing from editors using the Project Documentor and Project Transport Wizard as you develop your project What is a project? A project consists of a folder on your hard disk that contains, at a minimum, the following items: project file (.rsv) tag folder comprf (communications profile) folder cache folder The .
Project files The following table lists the RSView32™ folders and the types of files they contain. 1–2 Folder Contents File extensions Project name RSView32 project file, system files, and the folders described below .rsv System files: User accounts Security command list .act .sec Actlog Activity log files .dbf Almlog Alarm log files .dbf Als Alarm summary files .als Cab ActiveX® control setup files .cab Cache RSView32 internal files .ctl, .dat, .
Folder Contents File extensions Tgs Tag monitor files .tgs Vba VBA program files .vba Working in the Project Manager The Project Manager is the main tool for working with RSView32. Each time you create a project, a Project Manager appears showing the project name. Project name Component The Project Manager window is divided into two panes. When you first create a project, the left pane appears with a series of folders and the right pane is empty.
Component The Project Manager manages components, not files. A component is a file reference that is associated with the physical file’s name and path. The file can be located in a folder under the project directory, outside the project directory, or on another computer. Viewing component locations To view the location of the component’s file, select the component in the Project Manager and then check the location displayed in the status bar.
Adding components to a project You can use the same files in more than one project by adding components to a project. You can do this using two different methods. When you add a component in the Project Manager using the Copy Existing Component into Project option, you are creating a copy of the file in the project. When you add a component using the second option, Create Shortcut to Existing Component, you are not creating a copy of the file in the project.
To add a component to a project or update its file reference: 1. Select the editor that was used to create the desired component. For example, to add a graphic display component, highlight the Graphic Display editor. 2. Right–click to display the context menu, and then click Copy Existing Component into Project or click Create Shortcut to Existing Component. 3. In the dialog box, locate the component you want to add or update, and click it.
Renaming a component Renaming a component changes the physical file name. If you change the name of a file that is referenced by another project, the component (file reference) will be greyed out in the other project. To update the file reference, select the component in the Project Manager, click Rename, and then type the new file name. To rename a component: 1. Select the component in the right pane of the Project Manager. 2. Right–click and then click Rename. 3. In the To field, type the new name.
4. Click OK. Removing a component If you no longer want to use a particular file in a project, you can remove the component (file reference) from the project using the Remove item on the context menu. Removing a component removes the component from the Project Manager. It does not affect the physical file. To remove a component: 1. Select the component in the right pane of the Project Manager. 2. Right–click and then click Remove.
Some file servers do not support file names longer than eight characters. If your server does not accept long file names and you type a name longer than eight characters, you will receive a message. To avoid problems when issuing commands, do not use command names to name component files. For example, suppose you want to call an alarm summary file Summary 5. To avoid confusion with the Summary command, call the file Summary5. File names can contain spaces.
Selecting a printer You can select only a printer that has been installed on your system. For information on installing a printer, see your Windows documentation. IMPORTANT The settings in the Print Setup dialog box do not affect runtime log printing set up in the Activity Log Setup and Alarm Setup editors. To select a printer: 1. On the File menu in any RSView32 editor, click Print Setup. 2. If you don’t want to use the default printer, specify another printer. 3.
Selecting a network printer RSView32 can print to a network printer. For detailed information about setting up network printers, refer to your Windows documentation. Printing at runtime You can also print graphic displays at runtime using the PrintDisplay command. You must provide the operator with a way to issue the command when you create the display.
Using the Project Transport Wizard The Project Transport wizard lets you: rename a project copy a project delete a project back a project up to a .zip file restore a project that has been backed up to a .zip file. For more information, see the Transport Help, included on the RSView32 Resources CD-ROM, and also available from the RSView32 Tools menu on the Windows Start menu.
2 Chapter Setting up direct driver communications RSView32™ uses a direct connection to the drivers in RSLinx® to communicate with most Allen–Bradley® devices, as well as SoftLogix™ 5 devices. This chapter describes how to set up direct driver communications. You can also use DDE (Dynamic Data Exchange) or OPC® (OLE for Process Control) to connect to third-party devices or servers, as described in Chapter 3, Setting up OPC and DDE communications.
The following illustration shows an RSView32 station and its channel and nodes. RSView32 Communication channel Network Nodes Programmable controller Programmable controller Programmable controll Communication channel The communication channel is the connection from the RSView32 station to the network the programmable controllers are attached to. Communication device The communication device connects the communication channel to the computer.
Communication driver The communication driver is the software that permits the computer to communicate with the communication device. For communication with most Allen–Bradley programmable controllers, use RSLinx. For communication with SoftLogix 5 programmable controllers, you must use an RSLinx driver. Node (control device) The node is a programmable controller attached to a data highway or network. Once the RSView32 station is set up, it must periodically update its value table.
Setting up communications without hardware or software You can set up communications in RSView32, even if you do not have one or both of the following: RSLinx drivers installed the appropriate communications hardware installed To do so, follow the steps in the next section, but skip step 1 and start with step 2. To test your project without the appropriate hardware installed, see “Developing your project without a communication network” on page 2-22.
5. If you want to change the default rate at which nodes are scanned, open the Scan Class editor and edit the scan classes. For details, see “Scanning for new tag values” on page 2-17. 6. In the Tag Database editor, create tags. For each tag, select Device as the data source and assign the nodes and scan classes that you have defined. For details, see Chapter 4, Creating tags. 7. Monitor communications. For details, see “Monitoring communications” on page 2-20.
Using the drivers To configure and use the RSLinx drivers with a direct connection, the drivers must be installed on the same computer as RSView32. Once the drivers are configured, RSView32 automatically starts the driver software whenever communication with a programmable controller is required—for example, to test run a graphic display or to run a project. IMPORTANT You must use the version of RSLinx that came with your RSView32 software. This version has been tested for compatibility with RSView32.
Configuring channels To configure a channel: 1. In the Project Manager, open the System folder. 2. Open the Channel editor by doing one of the following: double–click the Channel icon right–click the Channel icon and then click Show Define up Define up toto four four different different communicatio communication n channels. channels. Click here to display the list of drivers for the selected network type. Specify the type of network you are using.
3.
To Select Communicate with programmable controllers through the Ethernet interface of a Pyramid Integrator™, or RSLinx Gateway TCP/IP Bridge Not use a channel None Loaded or Clear a channel configuration To set a configured channel’s network type to None Loaded, first issue the ComStatusOff command.
Messages Type a number between 1 and 10. This is the number of messages RSView32 will send on a channel before requiring a reply. These messages are stored in the buffers of the programmable controllers on the channel (each controller has its own buffer). If a buffer overflows at runtime, a communication error is generated. If this happens, reduce the number of messages. The Messages field applies to both the primary and secondary communication drivers.
Active Driver The active driver can be Primary, Secondary, or None. By default, the Primary driver is active. To disable a channel temporarily without removing its configuration, click None. At runtime, users can switch between drivers if necessary. For details, see “Switching communication drivers at runtime” on page 2-11. 4. When you finish configuring channels, click OK.
Commands for switching drivers Use the following commands to switch drivers: DriverPrimary Switches from the secondary driver to the primary driver on the specified channel. The number of the channel (1 through 4) that is being switched from its secondary to primary driver. DriverSecondary Switches from the primary driver to the secondary driver on the specified channel.
Example: An event for switching drivers In the Events editor, use the following: Action DriverToggle 1 Expression comm_err(tag1) where tag1 is a tag that is configured with a node on channel 1. When the expression evaluates to true, the action is triggered. Switching drivers manually To switch drivers manually, operators must have a way to issue a driver command. Possible methods are: creating a button and specifying one of the driver commands as the press action.
Before you can configure a device node, you must set up communication channels. For details, see “Configuring channels” on page 2-7. To create a node: 1. In the Project Manager, open the System folder. 2. Open the Node editor by doing one of the following: double–click the Node icon right–click the Node icon and then click Show 3. Fill in the following information for each node: Data Source Select Direct Driver.
and lower case letters, numbers, dashes, and underscores. Spaces are not permitted. Enabled Normally nodes are enabled, allowing collection of values from the programmable controller. However, during setup or troubleshooting you might want to disable a node to prevent communication timeouts or invalid data. When a node is disabled, tag values can still be read and written, but the values are read from and written to the value table instead of the programmable controller.
For the SOFT5 driver, enter the UNC name of the SoftLogix 5 controller without the backslashes. For example, if the UNC computer name is \\ORION, type ORION. The computer name must be 8 characters or less. For SoftLogix 5 controllers using the AB_ETH driver, enter the controller’s IP address. Type Select the type of device you are using.
Changing node information at runtime To permanently change a node’s station number at runtime, use the NodeSwitch command. This command allows you to set up node– level redundancy. That is, if the programmable controller that a node is pointing to fails, you can immediately switch to another programmable controller. NodeSwitch The name of the node that you want to change to another programmable controller address.
RSView32 scan classes Any tag that communicates with Allen–Bradley or SoftLogix 5 programmable controllers through direct drivers must be assigned to an RSView32 scan class. Each tag can then be assigned different foreground and background scanning periods. In this way, you determine how often a tag value is updated. A scan class has two scan periods: the foreground period and the background period. The foreground period applies to graphic displays and the tag monitor.
Set the scan period to match the expected rate of change for the tag’s data. For example, if you scan every five seconds for a change of state that occurs once an hour, the system is needlessly burdened. Conversely, if you scan too slowly, the system cannot monitor value changes that might occur between scans. To configure a scan class: 1. In the Project Manager, open the System folder. 2.
3. Select a scan class and fill in a foreground and background period. The period specifies, in seconds, how often the programmable controller address is scanned when its value is required by a foreground or background component. The foreground period applies to graphic displays and the tag monitor. The background period applies to any component that performs a continual background activity, such as derived tags, events, alarms, and data log. To specify a period, type a number.
Tag monitor—Use the tag monitor to check the communication status for a device tag.
Developing your project without a communication network You can develop your RSView32 project to use direct drivers without having an Allen–Bradley network or programmable controller. To do so, use the None Loaded driver type. 1. Open the Channel editor. 2. Select a channel and, in the Network Type field, select a network for the channel. 3. In the Primary Communication Driver field, click None Loaded.
3 Chapter Setting up OPC and DDE communications OPC® and DDE connections allow you to communicate with a wide range of local and remote devices. OPC is OLE for Process Control, used to connect RSView32™ to communication devices via vendor-specific OPC servers. DDE is Dynamic Data Exchange, used with external DDE servers such as third–party servers, to connect RSView32 to communication devices. RSView32 supports the OPC 1.0a and OPC 2.0 specifications.
another RSView32 station acting as a remote OPC server on a network. By connecting an RSView32 station set up as an OPC client to another RSView32 station set up as an OPC server, you achieve peer-to-peer communication of tag values across a network. For information about setting up RSView32 OPC peer-to-peer communication on a network, see“Using OPC for peer–to–peer network communications” on page 17-5.
Overview of OPC communications The following illustration shows the different ways RSView32 can use OPC for communications.
Overview of DDE communications The following illustration shows the different ways RSView32 can use DDE for communications.
Summary of steps The instructions below summarize the steps for setting up RSView32 as an OPC or DDE client. 1. Start the OPC or DDE server. 2. Start RSView32 and create or open a project (the client). 3. In the Node editor, create nodes for each OPC or DDE server and/or topic you wish to communicate with. In the node’s Data Source field, select OPC Server or DDE Server. For details, see “Creating an OPC node,” next, or “Creating a DDE node” on page 3-12. 4.
To create an OPC node: 1. In the Project Manager, open the System folder. 2. Open the Node editor by doing one of the following: double–click the Node icon right–click the Node icon and then click Show 3. Create a node by filling in the following information: Data Source Select OPC Server. The Tag Database editor does not check addressing syntax for programmable controllers that communicate through an OPC server. If the syntax is invalid, an error will be generated at runtime.
Name Type a name of your choice to represent the OPC node. The name can be up to 40 characters long and can have upper and lower case letters, numbers, dashes, and underscores. Spaces are not permitted. Enabled Normally nodes are enabled, allowing collection of values from the device. However, during setup or troubleshooting you might want to disable a node to prevent communication timeouts or invalid data.
Fill in the Server fields manually. You can fill in the fields for an OPC server that has not been installed yet and install the server later. Name Type the name of the OPC server that RSView32 will communicate with, typically in this format: .. If the OPC server is RSView32 or RSLinx, you don’t need to specify a version number. For RSLinx, you don’t need to specify the vendor name, either. Type Select the OPC server type: In-Process if the server is a .dll file.
Server Computer Name or Address If the OPC server is remote, type the server computer’s name or address, or click ... and select a server computer from the list that appears. You can use these formats to specify the name or address: Use this syntax For this format Example \\ComputerName UNC (Universal Naming Convention) \\DTB1 ComputerName.Domain.com DNS (Domain Name System) DTB1.NET2.COM XXX.XX.XXX.XXX Raw TCP/IP address 134.87.167.
Access Path Use of this field is optional. Use the access path field in the Node editor when: you want to be able to switch between PLCs using the NodeSwitch command for node redundancy you want all tags in RSView32 to have the same update rate You must leave the access path blank if you want to use different update rates for different tags in the tag database. If you leave the access path blank in the Node editor, specify the access path in the Tag Database editor’s tag address field.
5. When you finish configuring nodes, click Close. Example: Configuring an OPC node The following example describes how to create a node to connect to a local OPC server using RSLinx. Server Name: RSLinx OPC Server or RSLinx Remote OPC Server. If you are using RSLinx 2.0, the driver name is RSLinx OPC Server. If you are using RSLinx 2.1, the driver name is RSLinx Remote OPC Server. You don’t need to specify a vendor or version number.
Once you have created the node, assign it to a tag in the Tag Database editor. The address tells RSView32 where in the node to get the data. Address: N7:12 The PLC-5® programmable controller called PLC_HVAC1 has been previously set up as a DDE/ OPC topic in RSLinx; N7:12 is the address in the PLC-5/250. If you don’t include the Access Path when configuring the node, you can enter the tag’s address as [PLC_HVAC1]N7:12. The figure below shows how the tag looks in the Tag editor.
To create a DDE node: 1. In the Project Manager, open the System folder. 2. Open the Node editor by doing one of the following: double–click the Node icon right–click the Node icon and then click Show 3. Create a node by filling in the following information: Data Source Select DDE Server. The Tag Database editor does not check addressing syntax for programmable controllers that communicate through a DDE server. If the syntax is invalid, an error will be generated at runtime.
Name Type a name of your choice to represent the DDE node. The name can be up to 40 characters long and can have upper and lower case letters, numbers, dashes, and underscores. Spaces are not permitted. Enabled Normally nodes are enabled, allowing collection of values from the device. However, during setup or troubleshooting you might want to disable a node to prevent communication timeouts or invalid data.
Example: Configuring a DDE node The following example describes how to create a node to connect to a GE programmable controller using the RSServer for GE Series 90 protocol. Application: SNPWIN The application name is the server’s name. Topic: cpuid[@connection_ID][:poll_rate] The topic name is made up of a CPU ID string, an optional connection ID string (preceded by the @ character) and an optional poll rate (preceded by the : character). The figure below shows how the node looks in the Node editor.
Changing node information at runtime To change an OPC node’s server name and access path or a DDE node’s application and topic at runtime, use the NodeSwitch command. This command allows you to set up node–level redundancy. That is, if the server that a node is pointing to fails, you can immediately switch to another server. NodeSwitch The name of the node that you want to change to another server.
Scanning for new tag values When your RSView32 project is running, it must periodically update its tag values in the value table. For projects using OPC, values are updated by the OPC server at the rate specified in the server product. The update rate you specify in the Node editor is the requested data rate. The server uses this rate to determine the fastest rate at which to notify your RSView32 project (the OPC client) of tag value changes, if there are any changes.
4 Chapter Creating tags This chapter describes: tags and the tag database the importance of organizing tags how to create analog, digital, and string tags Tags and the tag database In the tag database, you define the data you want RSView32™ to monitor. Each entry in the database is called a tag. A tag is a logical name for a variable in a device or in local memory (RAM). For example, a tag can represent a process variable in a programmable controller.
Tag types RSView32 uses the following types of tags: Tag Type of data stored Analog Range of values. These tags can represent variable states such as temperature or the position of rotary controls. Digital 0 or 1. These tags can represent devices that can only be on or off, such as switches, contacts, and relays. String ASCII string, series of characters, or whole words (maximum of 255 characters).
Data sources When defining an analog, digital, or string tag, you must specify a data source. The data source determines whether the tag receives its values externally or internally. Device A tag with Device as its data source receives its data from a source external to RSView32. The data can come from a direct programmable controller driver or from an OPC® or DDE server. Tags with Device as the data source count toward the total tag limit you purchased (150, 300, 1,500, and so on).
Naming tags Tag names can be up to 255 characters long. If you create a folder, the folder name becomes part of the tag name. The tag name can contain the following characters: A to Z 0 to 9 underscore (_) and dash (-) The tag name can be mixed case. Tag names preserve upper and lower case for readability but are not case sensitive. For example, the tag name MixerValve1 is the same as mixervalve1.
The tag database editor To open the Tag Database editor: 1. In the Project Manager, open the System folder. 2. Open the Tag Database editor by doing one of the following: double–click the Tag Database icon right–click the Tag Database icon and then click Show The Tag Database editor has the following parts: form, query box, folder hierarchy, and spreadsheet. Each part is described on the following pages.
Using the Accept and Discard buttons When you enter information, the Prev and Next buttons change to Accept and Discard buttons. Click Accept to save tag and alarm information. Click Discard to cancel changes to a tag. Using the form Use the form to create a tag. In the upper part of the form, define the basic characteristics of the tag, such as tag name, type, security, and specifics related to the tag type. In the lower part of the form, define the data source (where the tag’s values will come from).
When you do searches, remember that the backslash in a folder name counts as one character in the tag name. Using the folder hierarchy The hierarchy and spreadsheet work together. The hierarchy shows the tag folders and the spreadsheet shows the tags within the folders. A folder icon known as root is always present in the hierarchy window, at the top of the folder hierarchy. This folder contains all the tag folders you and RSView32 create.
3. Click OK. The new folder appears in the hierarchy window. Opening a folder When you open a folder, its contents are displayed in the spreadsheet. To open a folder, do one of the following: double–click the folder select the folder and press Enter To open multiple folders: 1.
Adding tags to a folder Once you have created a folder, you can add tags to it. 1. Select a folder in the folder hierarchy. The folder name is displayed in the Name field of the form. 2. After the backslash (\), type the new tag name. Nesting a folder Create Folder 1. Select a folder in the folder hierarchy. 2. Click New Folder on the Edit menu or click the Create Folder button on the toolbar. 3. Type a backslash (\) followed by the new folder name. 4. Click OK.
To view a series of nested folders, resize the hierarchy box. To resize it, place the cursor over the right border of the box until it changes to a double arrow. Drag the border to the required size. Duplicating a folder When you duplicate a folder, all the tags in the folder are automatically given the new folder name. If the folder contains folders, those folders are also duplicated. IMPORTANT Be sure to choose Duplicate Folder rather than Duplicate. Duplicate only duplicates individual tags.
Deleting a folder Delete Folder 1. Select one or more folders in the hierarchy. 2. Click Delete Folder on the Edit menu or click the Delete Folder button on the toolbar. Using the spreadsheet Use the spreadsheet to view tags. Use the query box or folder hierarchy to select the tags you want to view.
Adding a tag To add a tag, do one of the following: click the New button in the forms area. This inserts a new row above the highlighted row. Insert Row click Insert Row on the Edit menu or click the Insert Row button on the toolbar. This inserts a new row above the highlighted row. Duplicating a tag Duplicate 1. Select the tag you want to duplicate. 2. Click Duplicate on the Edit menu or click the Duplicate button on the toolbar. A new row is inserted below the highlighted row.
Deleting a tag Delete tags carefully. Once you click the Delete button, the tag is deleted. There is no confirmation message and you cannot undo the deletion. 1. Select the tag you want to delete. 2. Click Delete on the Edit menu or click the Delete button on the toolbar. Delete Delete Configuring tag type The topics below describe how to complete the fields for analog, digital, and string tag types.
4. Fill in the fields as outlined below: Security To restrict access to this tag, select a security code. If access is restricted, operators cannot change a tag value without the proper security code. For detailed information about security, see Chapter 10, Adding security. Description Type a description of this tag, up to 128 characters long. Minimum and Maximum Type the minimum and maximum values that can be written to the programmable controller or server.
Scale and Offset Type a number. For the scale, do not use 0. To disable the scale, type 1. To disable the offset, type 0. The scale and offset modify the “raw data” that comes from and goes to the programmable controller before it is saved in the value table. The scale and offset also modify the value specified in RSView32 before it is written to the programmable controller. The scale is a multiplication factor—the value from the PLC is multiplied by the scale.
Data Type The data types are: Data type Description Range Default Depends on the data source and node type: See below. If Device is the data source, for direct driver nodes RSView32 matches the data format specified by the address, for example, N7:0=Integer, F8:0=Floating Point. Do not use Default for OPC or DDE nodes, as this might produce unexpected results. If Memory is the data source, Default is Floating Point.
Data type Description Range 4–Digit BCD 4–digit binary–coded decimal 0 to 9,999 For tags with Device as the data source, select the data type that matches the format of the data stored in the programmable controller or Windows® application. If you are using direct driver nodes, use the Default data type to automatically match the data format specified by the address. If you are using OPC or DDE nodes, do not use the Default data type because the default might not be as expected.
4. Fill in the fields as outlined below: Security To restrict access to this tag, select a security code. If access is restricted, operators cannot change a tag value without the proper security code. For detailed information about security, see Chapter 10, Adding security. Description Type a description of this tag, up to 128 characters long. Off Label and On Label Type text up to 20 characters long that describes the off state (value = 0) and on state (value = 1) of the tag.
3. For Type, select String. 4. Fill in the fields as outlined below: Security To restrict access to this tag, select a security code. If access is restricted, operators cannot change a tag value without the proper security code. For details, see Chapter 10, Adding security. Description Type a description of this tag, up to 128 characters long. Length Type a number between 1 and 255 to specify the length of the string tag in characters.
Specifying device as the data source A tag with device as its data source receives its data from a source external to RSView32. The data can come from: 5. 6. Allen–Bradley or SoftLogix™ 5 programmable controllers through RSLinx® direct drivers programmable controllers through an OPC or DDE server another Windows program through an OPC or DDE server To specify device as the data source: 1. Click Device. 2.
For more information about scan classes, see page 2-18. 4. In the Address field, do one of the following: to connect to Allen–Bradley and SoftLogix 5 devices, specify the physical memory location in the programmable controller. The address syntax depends on the programmable controller. For addressing syntax, see Appendix D, Addressing syntax for Allen–Bradley programmable controllers. to connect to other devices, specify the name of the tag in the OPC server or specify the DDE item.
2. In the Initial Value field, type the tag’s starting value. When you first run a project, a memory tag has the value defined in the Initial Value field. All subsequent runs of the project use the tag’s last value before the project stopped. To ensure a memory tag uses a particular value when the project starts, use the Set or = (Equal) commands in a startup macro to specify the tag’s value. The value of a memory tag can also be set using derived tags, events, or graphic objects.
Creating tags as needed in other RSView32 editors Any editor that uses tags has access to the tag database. You can access the database by doing one of the following: click the Browse button or the Tags button, whichever is available, to open the Tag Browser Browse button button Browse type a new tag name. When you try to save or close, a message appears prompting you to create the tag.
Using the Tag Browser When you click a Browse or Tags button, the Tag Browser opens.1. In the Tag Browser, you can: select a tag by double–clicking it, or by highlighting it and then clicking OK view the tag’s description by highlighting it edit a tag by highlighting it and then clicking Edit Tag. The Tag Editor dialog box opens so you can edit the tag’s definition. create a new tag by opening the desired folder and clicking New Tag. The Tag Editor dialog box opens so you can define the tag.
Importing tags from a PLC database Button Button in in Tag Tag Browser Browser DB Browser Button in Tag Database editor To open the PLC Database Browser, click the Other DB button in the Tag Browser or click the DB Browser button on the toolbar in the Tag Database editor. Use the PLC Database Browser to selectively import tags from an Allen–Bradley PLC database into the RSView32 tag database. Tags imported in this way are copied into the database—they are not shared with the source database.
For PLC and SLC addresses, the PLC Database Browser shows only addresses that are used in the symbol or address list of the PLC programming software. For RSLogix Frameworks symbols, you can import Frameworks global symbols for use with DDE nodes. To import tags from a PLC database: 1. Specify the data source for the tag by typing the node name and scan class if the node type is direct driver. 2.
3. To filter the tag list so that only certain addresses or symbols are displayed, type a character string, then click Search. If you want to search on names only, check the Symbols button so that only symbol names are displayed. If an address does not have a symbol name it will not be displayed. Use the filter if the address or symbol list is too big to display entirely. 4. Highlight the symbol, or symbols you want to import. 5.
To use the wizard: 1. Click the Windows Start button, point to Programs, Rockwell Software, RSView32 Tools, and then click Database Import & Export Wizard. 2. Read the wizard’s Help for details about how to use the wizard. Creating tags using the RSView32 Object Model and VBA You can use the RSView32 Object Model with programming languages like Visual Basic® or VBA to create tags. For more information about using the RSView32 Object Model, see Help.
Logging tag values Any tag value can be logged. To set up logging, use the Data Log Setup editor. For details, see Chapter 7, Configuring data logging. Using the tag monitor Use the tag monitor to view information about tags, such as changing tag values and tag status information.
Creating a tag monitor object 1. Open the Graphic Display editor. 2. Open the Tag Monitor editor by doing one of the following: on the Objects menu, click Advanced Objects, and then click Tag Monitor click on the Drawing Tools toolbox The cursor changes to the tag monitor drawing tool: 3. Drag the mouse to create a box the size you want for the tag monitor. When you release the mouse, a tag monitor appears. The Graphic Display editor’s menu bar changes to the menu bar for the tag monitor.
Creating a tag monitor file 1. In the Project Manager, open the System folder. 2. Open the Tag Monitor editor by doing one of the following: double–click the Tag Monitor icon right–click the Tag Monitor icon and then click New 3. On the View menu, click Form to display both the form and the spreadsheet. 4. Select the tags you want to display as described below. 5. On the File menu, click Save, and then type a name for the file.
If you use a wildcard, the Select Tag Names dialog box opens. Using the Select Tag Names dialog box The Select Tag Names dialog box lists all the tags that matched a wildcard. You can use some or all of the listed tags. A tag monitor can contain up to 100 tag names. This box lists all the tag names that matched the wildcard. Click this button to select all the listed tags. To select all tags: 1. Click Select All. 2. Click OK. To select a range of tags: 4–32 1.
3. Click OK. To select individual tags: 1. Click the first tag name you want to select. 2. Press and hold down Ctrl while you click one or more tag names. 3. Click OK.
Understanding what you see The following illustration shows the tag monitor file called Hopper1. A single tag is displayed in the form. All selected tags are displayed in the spreadsheet. The following table describes the columns in the spreadsheet: This column Displays ? Y if the tag name is valid. N if the tag name is not valid (in other words, the tag has not been created in the tag database). 4–34 Tag Name The tag name, whether valid or not, as entered in the tag database.
This column Displays State Disabled if the node has been disabled in the Node editor or by using the NodeDisable command. Error if RSView32 has tried to acquire a value but could not because of some kind of communication error, such as a node not being available or a DDE server not running. Stale if the tag value has been acquired before but does not have an updated value. Uninitialized if the value has never been acquired. Valid if RSView32 has a valid value for the tag.
To change the spreadsheet font: 1. On the View menu, click Spreadsheet Font. 2. Select the font, style, and size you want. To change the color of the font, click Spreadsheet Colors on the View menu, as described next. 3. Click OK. To change the color of text in the tag monitor spreadsheet: 1. On the View menu, click Spreadsheet Colors. 2. Select the item for which you want to specify a color.
Viewing details To see more detailed information about a tag: 1. Select a tag by clicking it in the spreadsheet or by clicking the Next and Prev buttons until the tag is displayed in the form section of the tag monitor. 2. Click Show Details on the View menu or click the Details button in the form section of the tag monitor. The Tag Details dialog box opens. To see the details for another tag, select the tag. You do not have to close the Tag Details dialog box.
5 Chapter Creating derived tags A derived tag is a tag whose value is the result of an expression. The expression can be made up of mathematical operations, tag values from the value table, if–then–else logic, and other special functions. You should not write to derived tags, because the derived tag is only evaluated when the expression changes.
How to use multiple derived tag files You can create multiple derived tag files. At runtime, up to 20 derived tag files containing a maximum of 1,000 tags can run simultaneously.
The Derived Tags editor To open the Derived Tags editor: 1. In the Project Manager, open the Logic and Control folder. 2. Open the Derived Tags editor by doing one of the following: double–click the Derived Tags icon right–click the Derived Tags icon and then click New Using the Accept and Discard buttons When you enter information in the editor, the Prev and Next buttons change to Accept and Discard. Click Accept to save information. Click Discard to discard information.
Setting up the evaluation interval To set up the evaluation interval for the derived tag file: 1. On the menu bar, click Setup, and then click Derived Tag Setup. 2. In the Derived Tag Setup dialog box, type a brief description of the derived tag file. This description is for your information only—it does not appear anywhere else. For example, if you were creating a derived tag file for a certain area of your plant, you might type “West Wing Assembly Line” to identify the area. 3.
4. Click OK. Creating derived tags Derived tags are created in the Derived Tags editor. The following illustration shows a derived tag file. IMPORTANT Do not create derived tags that depend on the results of other derived tags. At runtime, tags are not processed sequentially and the time it takes to process a tag can vary.
To create a derived tag: 1. In the Tag Name field, specify the name of the tag that will hold the derived tag value. This tag can be analog, digital, or string and can have device or memory as the data source. The tag name is also the name of the derived tag file. IMPORTANT Limit the use of tags with device as their data source. If the system is continuously writing the derived value to the device, it can flood the communication channel with traffic.
If you change the derived tag file at runtime, the changes do not take effect until you stop running the file and then start it again. Starting and stopping derived tag processing There are many ways to start and stop derived tag processing. Choose the way that works best for your project. For a complete list of RSView32 commands and their command syntax, see Appendix A, RSView32 commands, or see Help.
Ways to stop derived tag processing When a project stops, derived tag processing stops as well. To stop derived tag processing without stopping the project, use any of the methods below. In the Graphic Display editor, specify the DerivedOff command in the Shutdown field in the Display Settings dialog box. When the display closes derived tag processing stops.
6 Chapter Configuring alarms In RSView32™, you can set up a complete alarm system. Alarms are an important part of most plant control applications because an operator must know the instant something goes wrong. It is often equally important to have a record of the alarm and whether the alarm was acknowledged.
use the AlarmEvent command to respond to your own alarm detection algorithms for annunciation, logging, printing, and for display in alarm summaries Key concepts An alarm occurs when something goes wrong. It can signal that a device or process has ceased operating within acceptable, predefined limits or it can indicate breakdown, wear, or a process malfunction. Set up a system of alarms in the Tag Database editor by linking alarms to tags you want monitored.
Example: Alarm thresholds Alarm security levels Threshold values Thresholds Increasing 5,000 6 4,000 5 3,000 4 2,000 3 1 * 4 * 8 Safe zone 8 Decreasing 1,000 2 6 1 1 4 Time Thresholds must be set up in ascending order * These alarms are triggered only if the check box ‘Generate alarms when approaching normal operating range’ is selected in the Alarm Setup dialog box. The illustration shows the changing values of a tag monitoring a motor’s revolutions per minute (rpm).
If the motor speed It triggers an alarm of this severity falls below 2,000 rpm 8 falls below 1,000 rpm 6 falls below 1 rpm 4 * These alarms are triggered only if “Generate alarms when approaching normal operating range” is selected in the Alarm Setup dialog box. You can specify whether or not to generate alarms when an analog tag value is moving back to normal operating range and recrosses the alarm trigger threshold.
Alarm faults A variable threshold must not become higher than the threshold above it or lower than the threshold below it. If this happens, an alarm fault is generated for the monitored tag. To correct an alarm fault, you must reconfigure the variable threshold so it does not overlap either of its neighbors. This can become complex when the neighboring thresholds are themselves variable, because these boundaries are determined dynamically at runtime.
The following illustration shows an increasing threshold of 4,000 rpm with a deadband value of 500 rpm. In this example, the rpm would have to fall to 3,500, and then rise above 4,000 rpm before it would retrigger the alarm. rpm In alarm again In alarm 5,000 4,000 Deadband 3,500 3,000 Threshold Out of alarm 2,000 1,000 0 IMPORTANT Time n Use the deadband carefully in safety–critical applications.
Alarms for digital tags Digital tags are either on or off. Therefore, alarms for digital tags do not have thresholds. They have alarm states. 2. The alarm states are: On Triggers an alarm when a tag has a value of 1. Off Triggers an alarm when a tag has a value of 0. Any Change* Triggers an alarm when a tag value changes from 0 to 1 or from 1 to 0. Changes to On* Triggers an alarm only when a tag value changes from 0 to 1. Changes to Off* Triggers an alarm only when a tag value changes from 1 to 0.
Alarm messages Alarm messages report information about alarms. There are three types of messages: In Alarm message: generated when a tag goes into alarm Out of Alarm message: generated when a tag goes out of alarm Acknowledged message: generated when an operator acknowledges an alarm For each message, you can use the default message or create your own message, and you can selectively route alarm messages to a log file and/or printer. Alarm log file The alarm log file records alarm incidents that occur.
Alarm displays Alarm information can be displayed in: alarm log viewer alarm summary graphic objects and displays tag monitor When alarms are generated, they are recorded in two places: the alarm log file and the computer’s memory. The alarm log viewer displays the records in the alarm log file. The alarm summary displays the records in the computer’s memory. Alarm log viewer The alarm log viewer displays the contents of the alarm log file.
Alarm summary The alarm summary displays the alarm information recorded in the computer’s memory. The summary is configurable, so you can determine what and how alarm information is viewed. The summary can list up to 1,000 alarms. As new alarms occur, they appear at the top of the list. When the alarm summary becomes full, one alarm is dropped from the bottom of the list for each new alarm that appears at the top. Alarms are also dropped when they are out– of–alarm and acknowledged.
Graphic objects and displays You can customize graphic displays to show specific information about alarms. RSView32 makes all alarm status information available to graphic displays through a set of system tags (see below). Use these tags with numeric and string display objects. Attach visibility and color animation to affect the appearance of the objects. The Alarm Information graphic library contains graphic objects you can drag and drop into your display.
This tag Type Displays this information system\AlarmMostRecentTime String The time of the most recent, most severe alarm. system\AlarmMostRecentUnits String The units of the most recent, most severe alarm. system\AlarmStatus String The number of unacknowledged and suppressed alarms. system\AlarmSummaryItems Analog The number of alarm transactions in an unfiltered alarm summary. system\AlarmSummaryItemsUnacked Analog The number of unacknowledged alarms in an unfiltered alarm summary.
To acknowledge alarms, operators can: click the Acknowledge or Acknowledge All button in the alarm summary use the RSView32 Acknowledge command by itself, or with parameters to name a tag or group of tags use the RSView32 AcknowledgeAll command Unless an alarm is acknowledged, it remains outstanding until the system is shut down, the alarm summary is full, or alarm monitoring is turned off. Alarm suppression You can suppress alarm monitoring for tags.
a different command, macro, or VBA program for each tag, for example to run a different help file for each tag’s alarm conditions. About the Execute button With the Execute button, you can specify a command or macro that operators can run with reference to the highlighted alarm in an alarm summary. The Execute command can be appended with data items derived from the highlighted alarm, for example the tag name, alarm type, severity, value, date and time, and the tag type.
About the Identify button With the Identify button, you can specify a command or macro that operators can run when a tag is in alarm. Use this button to provide information about an alarm. For example, use the Display command to open a display that contains instructions on how to handle a motor that is running too fast. To set up the Identify button, specify a command or macro in the Alarm Identification field in the Advanced tab of the Analog Alarm editor or Digital Alarm editor.
For example, if the system detects that a tag is in alarm, it sets an internal alarm bit, and resets the bit when the tag is out of alarm. The following expression checks if a tag is in alarm: ALM_IN_ALARM (tag) where tag is the name of the tag you want to check for alarms. When a tag is in alarm, the expression result is 1. When a tag is out of alarm, the expression result is 0. One way to use this expression is to animate the visibility of a graphic object in a display.
Using wildcards in alarm expressions For built-in alarm functions, you can use wildcards in the expression to retrieve information about multiple tags at once. This wildcard Does this * Matches any number of characters, including the backslash (\) character. ? Matches any single character. For example, the following expression checks if any of a group of tags is in alarm: ALM_IN_ALARM (alarm*) where alarm* represents all tags whose names begin with “alarm.
Set up acknowledge bits in any of the following ways: one acknowledge bit for each tag When an alarm is acknowledged on one RSView32 station, that alarm is automatically acknowledged on all other RSView32 stations. Keep in mind, however, that RSView32 will be monitoring each bit so using many acknowledge bits can result in substantial system overhead.
By default, handshaking is off. To turn on handshaking, do one of the following: use the /H parameter with the AlarmOn command use the HandshakeOn command For detailed information about commands, see Appendix A, RSView32 commands, or see Help. Alarm events You can customize and extend the RSView32 alarm monitoring system by writing your own alarm detection algorithms using PLC ladder logic, VBA programs, or any other appropriate tools.
How event–based alarms work Alarm events let you create alarms, even without setting up tags in the tag database. Event–based alarms work just like tag–based alarms. They appear in alarm summaries, they can be used with alarm system tags, and they can be logged to disk or printer. You can filter event–based alarms the same way you filter tag–based alarms in alarm summaries. You can acknowledge event–based alarms, either individually, or with wildcards, using the Acknowledge command.
Naming alarm events A name must be associated with each alarm event. The event name can, but need not be, a tag defined in the tag database. An alarm event name cannot be an alarm tag in the database. Alarm event names can be up to 255 characters long. The alarm event name can contain the following characters: A to Z 0 to 9 underscore (_) and dash (-) The alarm event name can be mixed case. Alarm event names preserve upper and lower case for readability but are not case sensitive.
For detailed information about the AlarmEvent command, see Appendix A, RSView32 commands, or see Help. Summary of steps The main steps involved in setting up alarms are described below. You do not have to complete the steps in this order. 1. Set up the general features of all alarms in the Alarm Setup editor. To do this: configure the alarm log file. The alarm log file is a record of alarm incidents.
The Alarm Setup editor To open the Alarm Setup editor: 1. In the Project Manager, open the Alarms folder. 2. Open the Alarm Setup editor by doing one of the following: double–click the Alarm Setup icon right–click the Alarm Setup icon and then click Show Specify where to store alarm log files. Specify when to delete log files. Configure alarm severity. Create alarm messages that will replace the system default messages.
Specifying where to store alarm log files To specify where to store log files: 1. In the Alarm Setup editor, click the Setup tab. 2. If you want to change where the log files are stored, specify a new path. By default, alarm log files are stored in the ALMLOG subdirectory of your project. When log files are created, they will be stored in the directory specified here. 3.
4. If you want to log activities in a format that is compatible with projects running in RSView32 version 6.0 or earlier, click Use RSView32 6.0 Log File Format. 5. If you want your alarm log files to be named using the MS-DOS® eight–character file name and three–character extension format, click to deselect Use Long File Names. If the path where the log files are stored supports long file names, the date stamp part of the log file name includes a four–digit year. 6. Click OK.
Monitoring disk space If your computer’s hard disk is full, alarm logging stops and no more log files are created. To monitor disk space, see page 18-14. To specify when to start new files: 6–26 1. In the Alarm Setup editor, click the File Management tab. 2. Under Start New Files, click a button to specify when you want to have new files created. See the topics below for information on the various times.
Creating files periodically Click Periodic, and then click a time period. A new file is created after the specified interval has elapsed.
Example: Creating a new file To start a new file every Wednesday at 2:00 am and every Friday at 2:00 pm, type the following start times: Creating files when a particular event occurs 1. Click On Event. 2. In the Expression field, create the expression that will trigger creation of a new file. For details on creating expressions, see Chapter 14, Creating expressions.
Never creating new files Click Never. Logged data is added to a single file. To manage disk space if a log file grows too large, stop alarm monitoring, delete the alarm log file, and then restart alarm monitoring. You cannot delete an alarm log file while RSView32 is monitoring alarms. For details about how to monitor disk space, see “Monitoring disk space” on page 18-14. Deleting log files You can delete log files after a specified period or once a specified number of files has been created.
To specify when to delete files: 1. In the Alarm Setup editor, click the File Management tab. 2. Under Delete Oldest Files, select one or both check boxes and type a number to specify when to delete the log files. If you select both check boxes, files are deleted after the maximum time or after the maximum number of files is reached, whichever happens first. If you do not want files deleted, leave the check boxes under Delete Oldest Files blank.
number. For example, if you specify 10, you will have a maximum of 11 alarm log files at any time—10 old ones and the current one. When a new set is started, the oldest file is deleted. If you have set up File Management to delete the oldest files when a new one is started, and you are exporting data to an ODBC database, make sure you export the data before the oldest file is deleted. About alarm log files Alarm information is stored in dBASE IV (.dbf) format.
Example: Log file name The log file named 19971028bl.dbf was created in the year 1997, month 10, and day 28. The b indicates that this is the second file created that day. The l indicates that this is an alarm log file. Exporting alarm log files to ODBC format Using the command, AlarmLogSendToODBC, you can export logged alarms from their native dBASE IV (.dbf) format to an ODBC database. If the table in the database to which you are attempting to export data is not ODBC–compliant, the export will fail.
1. If required, using the ODBC Administrator, set up an ODBC data source name. For an example, see page 7-16. 2. Double–click Events in the RSView32 Logic and Control folder. 3. In the Expression box, type: time(“01:00”). This expression runs the command or macro you type in the Action box at 1:00 am every day. 4.
To configure alarm severity: 1. In the Alarm Setup editor, click the Severities tab. 2. Select an alarm severity or an incident. 3. Specify the logging destination. You can log to the alarm log file, to a printer, or to both.
If you want alarms logged to a printer, click the Printers button to display a list of available printers. To select a printer, it must already be set up on your system. For information on installing a printer, see your Windows® documentation. IMPORTANT 4. Page printers, such as laser printers, are not supported. For an alarm severity, specify how you want the alarm to be annunciated. Internal Bell The internal bell is a sound produced by the computer running RSView32.
alarm is acknowledged or silenced, the bit in the programmable controller is reset and the logic in the programmable controller turns off the audio device. 5. Click OK. Configuring alarm messages Alarm messages report information about alarms. There are several types of messages. You can define the content of each message or you can use the system defaults.2 Alarm messages appear in the description field of the alarm log file only. You cannot display them in alarm summaries.
To use the default messages for all alarms and alarm events, do not change anything. The default messages will be used automatically. Alarm events use system messages if you don’t specify a log message string using the /L parameter with the AlarmEvent command. These are the placeholders:34 This placeholder Is replaced with \C Current value of tag in alarm. \D Date when message is sent. \L Alarm label specified in the Alarm Label field of the Analog Alarm and Digital Alarm editors.
Example: Message placeholders An out–of–alarm message like this: \11D \8T Tag \10N is out of alarm. is displayed like this: 03/09/97 11:45:00 Tag PUMP3 is out of alarm. Do not give placeholders too much space, or your messages might not fit in the alarm log. In the example above, the tag name has 10 spaces (\10N). User default messages The user default messages are messages you create to replace the system default messages.
To create a user default message, type a message in the appropriate field. To select the user message as the default message, click the User Defaults button when you are configuring analog and digital alarms. Custom messages Custom messages apply on a per–tag basis. To create a custom message, type any message you want. For more information see“Configuring alarms for analog tags” on page 6-43 and “Configuring alarms for digital tags” on page 6-48.
Adding remarks to the alarm log file at runtime Using the AlarmLogRemark command, you can add information to the alarm log file at runtime. Alarm log remarks appear in the alarm log file, and can also be printed. You cannot display alarm log remarks in alarm summaries. The AlarmLogRemark command has parameters that let you add a text comment, the alarm severity, and the tag name to the alarm log file.
Specifying alarm conditions for analog and digital tags For each analog and digital tag that will be monitored for alarms, specify the alarm conditions in any of the following ways: by configuring alarm tags in the Tag Database editor. For more information about using the Tag Database editor to configure alarms, see this section. by importing tags into the tag database using the Database Import & Export Wizard. For more information about using the Database Import & Export Wizard, see page 4-27.
To open the Tag Database editor: 1. In the Project Manager, open the System folder. 2. Open the Tag Database editor by doing one of the following: double–click the Tag Database icon right–click the Tag Database icon and then click Show To add an alarm to a tag, select this check box. When a tag has an alarm, an X appears in this column. When can I configure an alarm for a tag? You can configure an alarm for a tag at the time you create the tag or later.
Configuring alarms for analog tags These are the main steps to configure alarms for analog tags: 3. configure the alarm threshold, and choose the message that will appear if the threshold is crossed configure the messages that are sent when a tag goes out of alarm and when an operator acknowledges an alarm configure advanced features, such as deadband and handshake Alarm thresholds 1. Click the Alarm Thresholds tab. 2. Select a threshold.
can configure thresholds 1, 2, 5, and 8 as long as you configure them in that order. 3. Fill in the fields as follows: Threshold To define a constant threshold, type a number. To define a variable threshold, specify a tag name. IMPORTANT At runtime a variable threshold must not become higher than the threshold above it or lower than the threshold below it, or an alarm fault will be generated for the tag. Increasing/Decreasing To monitor for a rising value that passes the threshold, click Increasing.
4. To configure additional thresholds, select another threshold and fill in each field. When you select another threshold, the information you configured for the previous threshold is saved. Alarm messages 1. Click the Alarm Messages tab. 2. Select the file and printer messages for when a tag goes out of alarm and when an operator acknowledges an alarm. If you click Custom Message, type the message in the File and/or Printer fields. You can use both words and placeholders.
Advanced 1. Click the Advanced tab. 2. Fill in the fields as follows: Alarm Identification Type a command or macro file name, or click the Browse button to open the Command Wizard. Browse button This command or macro runs in RSView32 when you highlight the alarm in the alarm summary and click Alarm Identify on the menu. The command or macro also runs when you use the Identify command, whether or not the tag is in alarm.
message can also appear in the alarm banner, if the banner is configured to display it. Deadband Click Absolute or Percentage and then type a value. The deadband is a buffer zone on the edge of an alarm threshold. For more information, see “Deadband” on page 6-5. Alarm Acknowledge In the Acknowledge Bit field, type the name of the tag that refers to the acknowledge bit’s address. When the operator acknowledges the alarm, the acknowledge bit is set to 1 and RSView32 logs an alarm acknowledgment.
Configuring alarms for digital tags These are the main steps to configure alarms for digital tags: configure alarm states configure the messages that are sent when a tag goes out of alarm and when an operator acknowledges an alarm configure advanced features, such as handshake Alarm states 1. 6–48 Click the Alarm States tab.
2. Fill in the fields as follows: Alarm Type Select a type. For a description of types, see “Alarms for digital tags” on page 6-7. Alarm Label Type a description of the alarm up to 21 characters long. This description is displayed in the alarm summary and alarm banner. Severity Select a severity level. Severity 1 is most severe, Severity 8 is least severe. Severities are configured in the Alarm Setup editor. For details, see “Configuring alarm severity” on page 6-33.
Alarm messages 1. Click the Alarm Messages tab. 2. Select the file and printer messages for when a tag goes out of alarm and when an operator acknowledges an alarm. If you click Custom Message, type the message into the File and/ or Printer fields. You can use both words and placeholders. For detailed information about messages, see “Configuring alarm messages” on page 6-36.
Advanced 1. Click the Advanced tab. 2. Fill in the fields as follows: Alarm Identification Type an RSView32 command or a macro, or click the Browse button to open the Command Wizard. Browse button This command or macro runs in RSView32 when you highlight the alarm in the alarm summary and click Alarm Identify on the menu. The command or macro also runs when you use the Identify command, whether or not the tag is in alarm.
message can also appear in the alarm banner, if the banner is configured to display it. Alarm Acknowledge In the Acknowledge Bit field, type the name of the tag that refers to the acknowledge bit’s address. When the operator acknowledges the alarm, the acknowledge bit is set to 1 and RSView32 logs an alarm acknowledgment.
Viewing the alarm log file The Alarm Log Viewer displays the description, user, and logging station fields from the alarm log file. The contents of this file will depend on how you configured alarm severities in the Alarm Setup editor. By default, the alarm log file will have a record of all alarms that are generated. 5 For information about all the fields in the alarm log file, see page 16-9. To view the alarm log file: 1. In the Project Manager, open the Alarms folder. 2.
One or more log files is displayed. The number of files depends on how you set up file management in the Alarm Setup editor. 4. Click the file you want to view. The contents of the file are then displayed in the viewer. 5. To close the viewer, click Close on the File menu. Or right click any tab in Alarm Log Viewer, such as Description, User and so on. Click Select Log File from Records menu, and then select the file you want to view.
No matter where you create the alarm summary, you use the same methods to customize how the information will appear. Embedding the alarm summary as an object in a graphic display offers better screen management than creating an alarm summary file. When the summary is embedded in a graphic display you can use the Display command, which allows you to specify screen properties such as size and position.
To create the alarm summary object: 1. Open a graphic display. 2. On the Objects menu, click Advanced Objects, and then click Alarm Summary. The cursor changes to the Alarm Summary tool: 3. Drag the mouse to create a box approximately the size you want for the alarm summary. When you release the mouse, an empty alarm summary window appears. The menu bar changes to display the menus for the Alarm Summary editor. 4.
A new alarm summary looks like this: Header area: Use the commands on the Insert menu to insert headings here. Divider: Use the mouse to move the divider up and down. Body area: The area where alarm information is displayed at runtime. Button bar: Use the commands on the Format menu to specify what buttons to include on this bar and to specify where to place the bar. Inserting headings The Insert menu contains the items that can appear in the summary.
When you click an item on the Insert menu, two boxes appear in the alarm summary. Drag the boxes to position them. When you release the mouse button, the item name appears. To reposition items, click them and drag them with the mouse. To resize items, click them and then drag a handle with the mouse. To change an item, you only have to select one box—when you move or resize one box, the other box is also moved or resized. To edit the text in a box, double–click the box. The Modify Text dialog box appears.
Choosing fonts The header and body fonts can be different. For example, you might choose a larger font for the header and a smaller font for the body. To change a font, click Body Font or Header Font on the Format menu. The fonts listed here depend on which fonts you have installed in Windows. Choose the font, style, and size you want. When you are finished, click OK. To increase the size of the header area so a large font is more easily displayed, drag the divider down.
You can configure the blink style of: Severity 1 through 8 messages Out of Alarm and Fault State messages To configure colors and blink styles, click Colors on the Format menu. Blink colors appear to the right of the solid colors when you select Blink. Click an item and then select the colors you want. To select a color, place the cursor over the color box, click to open the color palette, and then click a color in the palette.
default colors are the highlight text and highlight background colors reversed. When you are finished, click OK. Formatting buttons You can specify which buttons you want on the button bar and where you want the bar located. To choose which buttons to include, click Buttons on the Format menu. The Buttons dialog box appears. If you do not want certain buttons displayed, clear the check boxes for those buttons. When you are finished, click OK.
The following table describes what the buttons do: This button Does this Ack Current Marks the highlighted alarm as acknowledged. If a bell is associated with the alarm, acknowledging the alarm turns off the bell. If the tag has gone out of alarm, it is removed from the alarm summary when it is acknowledged. Ack Page Marks all alarms on the screen as acknowledged. If a bell is associated with an alarm, acknowledging the alarm turns off the bell.
This button Does this Identify Runs a macro for the alarm if one was created and entered in the Alarm Identification field of the Advanced tab in the Analog Alarm or Digital Alarm editor. Filter Opens the Filter dialog box, so alarm information can be temporarily filtered out of the alarm summary. Sort Opens the Sort dialog box, so alarm information can be temporarily sorted.
Positioning the button bar To specify the location of the button bar, click Button Bar Position on the Format menu, and then click a location. In the following illustration, Left was chosen as the button bar position. Choosing data Use the Filter and Sort items in the Data menu to specify which alarm information is displayed. Use Filter to filter out information—that is, to specify information you do not want displayed in the alarm summary.
You can use wildcards or tag placeholders in the alarm summary filter. Tag Names Specify the tag names you want to appear in the alarm summary, entering each tag on a separate line. You can use wildcards to select tags. These are the wildcards: This wildcard Does this * Matches any number of characters, including the backslash (\) character. ? Matches any single character. ~ When placed before a tag name, excludes the tag. When placed before a folder name, excludes the tags in the folder.
the alarm summary. A tag placeholder is the cross-hatch character (#) followed by a number from 1 to 500. The placeholder can also contain wildcards and folder names. See “Using tag placeholders” on page 11-37 for more information. If you use tag placeholders, at runtime you must specify the tag each placeholder represents, either by using a parameter file or by typing the tag names on the command line. You can also use wildcards in the parameter file or on the command line.
If you leave the Out of Alarm state unchecked, the alarm summary item changes color when the tag goes out of alarm. Tags that are out of alarm remain in the alarm summary until they are acknowledged. If you want to see only the tags that are in alarm in the summary, click Only show tags currently In Alarm. Digital change of state alarms and InAndOutOfAlarm events are not displayed in the alarm summary when you select this checkbox.
and date, these alarms are presented in order of severity. If any alarms have the same time and date and the same severity, they are then presented by tag name. You can sort data that has been filtered. Using alarm data with commands Use the Execute item in the Data menu to execute a command (whether an RSView32 command, an RSView32 macro, or a VBA program) and to append data items derived from the highlighted alarm to the command.
separated by a space, unless you click Separate Parameters with commas. IMPORTANT A space is not automatically appended to the end of the command text. If you are using parameters and require a space between the end of the command, macro, or VBA program and the first parameter, be sure to include the space with the command text. Severity and value are shown only for alarms of type IntoAlarm. For alarm types OutOfAlarm and IntoFault, severity is 0.
Example: Using the AlarmLogRemark command with the Execute button in an alarm summary You cannot change the order in which parameters are passed to the command line for the alarm summary Execute button.
To suppress alarm printing for all tags, use the RSView32 AlarmPrintOff command. To re–enable printing of alarms, use the RSView32 AlarmPrintOn command. Alarms will print when the AlarmOn command is issued, unless the AlarmPrintOff command was issued before the AlarmOn command was issued in the same session of RSView32. The AlarmPrintOff and AlarmPrintOn commands are not retained across RSView32 sessions. The AlarmPrintOff and AlarmPrintOn commands have no arguments.
The wildcards are: This wildcard Does this * Matches any number of characters, including the backslash (\) character. ? Matches any single character. Viewing suppressed tags The Suppressed List shows which tags are suppressed—that is, which tags are not being monitored for alarms. To open the Suppressed List: 1. In the Project Manager, open the Alarms folder. 2.
Click a tag name and then click here to turn off suppression for that tag. Click here to turn off suppression for all tags. More RSView32 commands You can also use RSView32 commands to turn off suppression and to open the Suppressed List. For details, see Appendix A, RSView32 commands, or see Help. Starting and stopping alarm monitoring There are many ways to start and stop alarm monitoring. Choose the way that works best for your project.
In the Graphic Display editor, create a button object and specify the AlarmOn command as the press action. When the button is pressed, alarm monitoring starts. In the Graphic Display editor, create a graphic object and attach touch animation with the AlarmOn command as the action. When the object is touched, alarm monitoring starts. In the Events editor, specify the AlarmOn command as the action for an event. On the command line, type AlarmOn and then press Enter.
7 Chapter Configuring data logging Data log is an RSView32™ component that collects and stores tag values (data). You specify the type of data to collect, when to collect it, and where to store it by defining a data log model. The data that is collected is stored in dBASE® IV (.dbf) format or ODBC (Open Database Connectivity) format.
How to use multiple data log models At runtime, up to 400 models can run simultaneously.
relational database software to retrieve and manipulate the data. If the database becomes inaccessible, RSView32 logs the data to backup files in binary format. If you need to use data in multiple formats, define multiple data log models for the same tags. The .dbf file format Data logged in the .dbf format can be stored in narrow or wide format. The data file names vary depending on which format you choose. Narrow .dbf file format The narrow .
This is one snapshot of data. Date1 Time1 Tag1 value Tag2 value Tag3 value Date2 Time2 Tag1 value Tag2 value Tag3 value Date3 Time3 Tag1 value Tag2 value Tag3 value Date4 Time4 Tag1 value Tag2 value Tag3 value Date5 Time5 Tag1 value Tag2 value Tag3 value Date6 Time6 Tag1 value Tag2 value Tag3 value Choosing between narrow and wide .dbf file formats The following table summarizes the features of each file format: 7–4 Narrow Wide Limit of 10,000 tags in the model.
How .dbf log files are named When a .dbf log file is created, it is named automatically. The name is based on the date the file was created and the type of data it contains. Long file names RSView32 gives you the option to use long file names. When you choose this option, at runtime RSView32 creates data log files with long file names unless either the primary or secondary path does not support long file names, or unless either path is inaccessible when data logging starts.
Example: Long file name The log file named 1997 10 28 0004 Oven Temperatures (Wide).dbf was created in the year 1997, month 10, and day 28. The 0004 indicates that this is the fourth file set created that day. Oven Temperatures is the log file identifier string, which the user defined to help identify the data. (Wide) indicates that this file is in wide file format and may contain both floating point and string tag data.
Example of short file names for narrow .dbf format For narrow .dbf file format, data log files are created in sets of three. Even if your project does not contain a particular type of data, three files are created. If data is not available for a file, the file remains empty. Example: Narrow .dbf short log file name The log file named 971028cs.dbf was created in the year 97, month 10, and day 28. The c indicates that this is the third file set created that day.
Example of short file names for wide .dbf format For wide .dbf file format, data log files are created in sets of two. Example: Wide .dbf short log file name The log file named 971028dw.dbf was created in the year 97, month 10, and day 28. The d indicates that this is the fourth file set created that day. The w indicates that this file is in wide file format and may contain both floating point and string tag data. Example: Wide .
String table (optional)—stores string tag values For a detailed description of the tables’ contents, see page 16-17. ODBC backup files are stored as binary files with the extension .obf. You cannot view the contents of the .obf files. How ODBC tables are named The ODBC tables are created with the default names TagTable, FloatTable, and StringTable. However, you can edit these names before creating the tables, or specify different tables to use, in the Data Log Setup dialog box.
To use the tables in an existing ODBC data source: 1. Add fields for the data log data to the tables in the ODBC database. See the example on page 7-16 for information about adding fields to an existing table. “Data log—ODBC format” on page 16-17 describes the order and type of fields needed to log data to an ODBC database. Edit the tables as described in the documentation for the ODBC relational database you are using. 2. Set up your data log model, as described in “Setting up a model” on page 7-11.
The Data Log Setup editor To open the Data Log Setup editor: 1. In the Project Manager, open the Data Log folder. 2. Open the Data Log Setup editor by doing one of the following: double–click the Data Log Setup icon right–click the Data Log Setup icon and then click New Set up general aspects of the model. Specify the paths to which to log the data. Specify when you want log data created and deleted. Specify how and when logging should occur. Specify which tags to log data for. Setting up a model 1.
for the data log files. For more information about long file names see “Long file names” on page 7-5. If you choose the ODBC storage format in step 4, long file names apply to the backup files only. You can change the log file identifier string at runtime, as described on page 7-44. However, the runtime change affects the current data log session only. When you stop and restart the model RSView32 uses the string you set up here. 4. Click a file storage format.
Digits After Decimal Point Type the number of digits after the decimal point that are to be stored for floating point numbers. Use this field and the Number of Digits field to achieve the precision you want. For example, if your process has very large numbers, you can increase the total number of digits and reduce the number of digits after the decimal point. Number of Characters in String Type the number of characters to be logged for all string tags in the model.
Type the path and file name of an existing ODBC data source, or click the Browse button to select an existing data source or create a new one. Browse button If you click the Browse button the Select Data Source dialog box appears. To use an existing file-based ODBC data source, select it from the Data Source Name list box or click ... to browse for the file folder that contains the data source.
To choose a table from the existing tables at the data source, click the ... button. Select a table from the Select ODBC Table dialog box that appears. To view the order, type, length, and precision of the fields in the table, highlight the table and click Details. If you don’t specify a table name for the tag table, the tag name is used instead of a tag index in the float and string tables. This uses more database space than using a separate tag table.
Example: Creating a new ODBC data source This example shows how to create a new ODBC data source that connects to an SQL Server database called Bakery. The SQL Server is called Athena. The new data source will be called Bakery_Stats. The data source will be used on the current computer only, but will be used by multiple users at the computer. In this example, you will set up the ODBC data log tables manually using Microsoft Query. First, create the ODBC data source. Then set up the ODBC tables.
4. Select SQL Server from the list of ODBC drivers installed on the computer, and click Next. Click Finish. 5. In the ODBC SQL Server Setup dialog box, enter the data source name (Bakery_Stats) and a description. 6. In the Server field, select Athena, the name of the server where the SQL database is located. Click Options.
7. In the Database Name field, type Bakery, the name of the SQL database to log the data to. 8. Clear the check box Generate Stored Procedure for Prepared Statement. Click OK. 9. In the Select Data Source dialog box, select Bakery_Stats and click OK. Note that you could also create the ODBC data source in the Windows Control Panel, then select the data source in the ODBC Data Source field of the Data Log Setup editor.
To set up the ODBC data tables: You must have access to the SQL Server to log in and create the tables. 1. Double-click Microsoft Query in the MSOffice directory and choose Table Definition from the File menu. 2. In the Select Data Source dialog box, specify the data source you just created and click Use. Enter your login ID and password. 3. Click New in the Select Table dialog box. 4.
8. 9. 10. Enter the following to set up the fourth field in the table. Field Name: TagDataType Type: smallint Click Create. Repeat steps 4 through 7 to add the FloatTable and StringTable. See page 16-15 for information about the field types and lengths. If you want to edit a table that already exists, after you log in choose the table name and click View. The order of the data log fields must match the order listed in the tables beginning on page 16-15.
become unavailable because of network failures, or because of lack of disk space on the primary path or where the ODBC database is located. If the primary path or ODBC database becomes unavailable, RSView32 begins to store the data in a buffer. The buffer can hold up to 64 Kb of data. When the buffer fills, or when the maximum amount of time to buffer data has elapsed, if the primary path or ODBC database is still unavailable RSView32 switches to the secondary or backup path.
For models that use the dBASE IV format, RSView32 creates a new file set each time the logging path changes. Specifying logging paths You can specify the .dbf primary and secondary file paths and the ODBC backup file path by editing the data log model in the RSView32 Works Project Manager, as described next. You can also change the logging paths at runtime using RSView32 Runtime, as described in “Changing logging paths using RSView32 Runtime” on page 7-41. To specify .
Relative To Project Click this to store the log files in the project directory. RSView32 creates a directory called Dlglog and a subdirectory with the same name as the model name and stores the files there. Absolute Path Click this to specify a particular path. If the path you type does not exist, RSView32 will create it. The first time data logging runs, RSView32 creates a subdirectory with the same name as the model name and stores the files there. 3.
For .dbf data log files, if you used this default path as your primary path, specify a different path for the secondary path. Absolute Path Click this to specify a particular path. If the path you type does not exist, RSView32 will create it. The first time data logging runs, RSView32 creates a subdirectory with the same name as the model name and stores the files there. 4. If you choose to use a secondary or backup path, click Advanced.
In all other cases, RSView32 checks whether the primary path has become available after the specified time has elapsed. Minimum free disk space required for auto switchback (MB) For data log models that use dBASE IV storage format, specify an amount that is high enough to prevent RSView32 from frequently switching between paths due to low disk space on the primary path.
primary path or ODBC database. You must move it manually using the DataLogMergeToPrimary command. RSView32 also switches back to the primary path or ODBC database when you use the DataLogMergeToPrimary command. Note that you cannot switch manually from the primary path or ODBC database to the secondary or backup path. You can give operators ways to issue these commands at runtime. For example, you can create a button object and use the DataLogSwitchBack command as the press action.
To restore the secondary or backup data, give operators a way to issue the DataLogMergeToPrimary command or the DataLogMergeToPrimary * command at runtime. For example, you can create a button object and use the command as the press action. Creating .dbf log files If your data log model uses the ODBC format, data is added continually to the same database, and this section does not apply. If your data log model uses the dBASE IV format, RSView32 logs the data to sets of files.
To specify when to start new .dbf files: 1. In the Data Log Setup editor, click the File Management tab. 2. Under Start New Files, click a button to specify when you want to have new files created. See the topics below for information on the different times. Creating files periodically Click Periodic, and then click a time period. A new file is created after the specified interval has elapsed.
Creating files at specified times Click At Specified Times, and then type a time or list of times when you want data to be logged to a new file. Start a new line for each new time and allow at least five minutes between start times. Use any of the following to specify time: Time Format Day Sun, Mon, Tue, Wed, Thu, Fri, or Sat Date 1 – 31 Specifying 31 means that months that do not have 31 days will not have new log files.
Creating files when a particular event occurs 1. Click On Event. 2. In the Expression field, create the expression that will trigger creation of a new file. For details about expressions, see Chapter 14, Creating expressions. You can use on-event logging to create sets of data for use with filebased trending. For more information, see Chapter 13, Configuring trends.
Using the DataLogNewFile command to create files You can also create new ODBC backup files and .dbf log files with the DataLogNewFile command or the DataLogNewFile * command. The DataLogNewFile command creates a new file set for the specified data log model. The DataLogNewFile * command creates a new file set for all data log models that are currently running. Use these commands anywhere an RSView32 command or macro can be entered.
press action. When an operator presses the button, the command is issued, a new file is created, and data is logged to that file. Deleting ODBC database records and .dbf log files If your data log model uses the ODBC database format, you can purge old records from the database using standard relational database tools or SQL queries. You can also configure RSView32 to delete (purge) records in the ODBC database after a specified time. If your data log model uses the dBASE IV format, you can delete .
To specify when to delete .dbf files or ODBC database data: 1. In the Data Log Setup editor, click the File Management tab. If you are using the ODBC storage format, go to step 3. 2. If you are using dBASE IV storage format, under Delete Oldest Files, select one or both check boxes and type a number to specify when to delete the .dbf log file sets. If you select both check boxes, files sets are deleted after the maximum time or after the maximum number of files is reached, whichever happens first.
maximum of 11 data log file sets at any time—10 old ones and the current set. When a new set is started, the oldest file set is deleted. These options apply to .dbf files on the primary path only, not the files on the secondary path. RSView32 deletes files on the secondary path only when the DataLogMergeToPrimary command is issued. When you have finished specifying options for deleting .dbf files, go to “Specifying when to log data” on page 7-35. 3.
Specifying when to log data You can set up logging so tag values are logged: periodically (periodic logging) only when a tag value changes (on–change logging) when a particular event occurs and triggers the DataLogSnapshot command (on–demand logging) DataLogSnapshot is the RSView32 command for logging data for a single data log model on demand, where is the name of the data log model.
2. Click a button to specify a log trigger and fill in any additional information. See the topics below for information on the different types of log triggers. Logging periodically Periodic logging is used to take a snapshot of all tag values at a particular point in time. You can use the dBASE IV (narrow), dBASE IV (wide), or ODBC storage format for periodic logging. For periodic logging to dBASE IV files, the dBASE IV (wide) file format is most efficient for storing the data. 1. Click Periodic. 2.
all tags, whether their values have changed or not, making the wide format inefficient. 1. Click On Change. 2. In the Change Percentage field, type the percent the tag value has to change in order to trigger logging. You can type a decimal value, if desired. The percentage is based on the tag’s minimum and maximum values as configured in the Tag Database editor. Only the tags that change by the specified percentage are logged. Zero means all changes are logged. 3.
Using the DataLogSnapshot command You can record tag values using the DataLogSnapshot command or DataLogSnapshot * command. The DataLogSnapshot command records tag values for all tags in the specified model at the instant the command is executed. The DataLogSnapshot * command records tag values for all tags in all running models at the instant the command is executed. Use these commands anywhere an RSView32 command or macro can be entered.
Combining logging You can combine periodic or on–change logging with on–demand logging. This enables data to be captured at particular times, as well as when a particular event occurs. 4. To combine logging: 1. In the Data Log Setup editor, choose Periodic or On Change as the log trigger. 2. Type the DataLogSnapshot command or the DataLogSnapshot * command anywhere an RSView32 command or macro can be used.
Choosing the data to log For narrow–format dBASE IV models and ODBC models, the model can contain up to 10,000 tags. For wide–format dBASE IV models, the model can contain up to 100 tags. To specify tags: 1. In the Data Log Setup editor, click the Tags in Model tab. 2. In the Tag(s) to Add field, specify the tags that will be logged by: typing the tag names, separating multiple tag names by a space or a comma using the selection button to open the Tag Browser and then selecting tags.
then click Remove. To remove all tags, click Remove All. Tags that you remove appear in the Tag(s) to Add field. Delete the tags you want to remove from the Tag(s) to Add field before you click OK. Editing the data log model You can edit a model during development or runtime. If you change a model at runtime, the changes will not take effect until you stop data logging and then restart it.
the backup path for ODBC data log models. You cannot change the ODBC database using RSView32 Runtime. To edit the logging paths: 1. In the Project Manager, open the Data Log folder. 2. Open the Data Log Path editor. 3. Specify paths as described in “Specifying logging paths” on page 7-22. Changing logging paths using the DataLogPath command The operator can also change logging paths at runtime using the DataLogPath command, where refers to the data log model you want to change paths for.
Making runtime changes without editing the data log model You can change certain data log parameters at runtime without editing the data log model. These runtime changes take effect immediately, but are not retentive: changing the log rate for periodic logging changing the log file identifier string Use these commands anywhere an RSView32 command or macro can be entered. For example, type the command directly on the command line.
Changing the log file identifier string You can change the log file identifier string that is used as part of the file name for dBASE IV log files that use long file names. The log file identifier string is also used in the names of ODBC backup files that use long file names. To change the string, use the DataLogRenameFile command.
Ways to start data logging In the descriptions below, represents the name of the data log model. In the Startup editor, select the Data Logging check box and specify a data log model. If you want to start more than one data log model for a project, include the DataLogOn command in a startup or login macro. In the Macro editor, create a startup or login macro that includes the DataLogOn command.
To stop a single data log model, use the DataLogOff command where is the name of the data log model. To stop all data log models, use the DataLogOff * command. In the Graphic Display editor, specify the DataLogOff command or the DataLogOff * command in the Shutdown field in the Display Settings dialog box.
8 Chapter Configuring activity logging Activity log records information about various types of system activity. The information is stored in dBASE® IV (.
authorizes the action. For tag writes, the activity log also records the old value and the new value. Summary of steps By default, RSView32™ is set up to log activities. You can change the default settings and specify: where to store activity log files when to create and delete log files which activities to log The Activity Log Setup editor To open the Activity Log Setup editor: 1. In the Project Manager, open the System folder. 2.
Set up the file path, select a printer, and specify details about the log file. Specify when you want log files created and deleted. Specify which activities to log. RSView32 versions 6.2 and later contain extra fields in the dBASE IV file format for storing activity log data. The newer .dbf file format logs details about the computer on which the logging server is running.
Specifying where to store activity log files To specify where to store log files: 1. In the Activity Log Setup editor, click the Setup tab. 2. If you want to change where the log files are stored, type a new path. By default, activity log files are stored in the ACTLOG subdirectory of your project. When log files are created, they will be stored in the directory specified here. 3. If you want activities logged to a printer, click the Printer button to display a list of available printers.
4. If you want to log activities in a format that is compatible with projects running in RSView32 version 6.0 or earlier, click Use RSView32 6.0 Log File Format. 5. If you want your activity log files to be named using the MS-DOS® eight–character file name and three–character extension format, click to deselect Use Long File Names. If the path where the log files are stored supports long file names, the date stamp part of the log file name includes a four–digit year. 6. Click OK.
Monitoring disk space If your computer’s hard disk is full, activity logging stops and no more log files are created. To monitor disk space, see page 18-14. To specify when to start new files: 1. In the Activity Log Setup editor, click the File Management tab. 2. Under Start New Files, click a button to specify when you want to have new files created. See the topics below for information on the different times. Creating files periodically Click Periodic, and then click a time period.
Daily Each day approximately at midnight Weekly Each Sunday approximately at midnight Monthly On the first day of each month approximately at midnight Creating files at specified times Click At Specified Times, and then type a time or list of times when you want activities to be logged to a new file. Start a new line for each new time and allow at least five minutes between start times.
Creating files when a particular event occurs 1. Click On Event. 2. In the Expression field, create the expression that will trigger creation of a new file. For details about expressions, see Chapter 14, Creating expressions. Example: Creating a new file for a new shift You can set up your project so it creates a new log file at the end of a shift or batch process. For example, create a tag called NextShift. In the Activity Log Setup editor, click On Event and type NextShift as the expression.
Deleting log files You can delete old log files after a specified period or once a specified number of files has been created. If you never want files deleted, leave the check boxes under Delete Oldest Files blank. Activity log files are deleted only when a new file is created. So, if your project creates a new file each day and deletes the oldest file every third day, your project will have files for the three previous days’ data as well as a file for the current day. To specify when to delete files: 1.
third day so you always have the two previous days’ data and the current day’s data. After Maximum Files The oldest log file is deleted after the specified maximum has been reached. The files currently being logged to are not included in this number. For example, if you specify 10, you will have a maximum of 11 activity log files at any time—10 old ones and the current one. When a new file is started, the oldest file set is deleted. About activity log files Logged activities are stored in dBASE IV (.
Example: Log file name The activity log file named 971028bi.dbf was created in the year 97, month 10, and day 28. The b indicates that this is the second file created that day. The i indicates that this is an activity log file. Exporting activity log files to ODBC format Using the command, ActivityLogSendToODBC, you can export logged activities from dBASE IV (.dbf) format to an ODBC database.
1. If required, using the ODBC Administrator, set up an ODBC data source name. For more information about setting up an ODBC data source, see page 7-16. 2. Double–click Events in the RSView32 Logic and Control folder. 3. In the Expression box, type: time(“01:00”). This expression runs the command or macro you type in the Action box at 1:00 am every day. 4.
Specifying which activities to log To specify which types of activity to log: 1. In the Activity Log Setup editor, click the Categories tab. 2. In the Select Category area, click a category: This activity category Logs Commands The execution of a command. Applications Applications such as security logins and data logging. ActiveX® events if the event has been set up to do so in the ActiveX Control Events dialog box. Remarks Remarks entered using the Remark command.
This activity category Logs Communication s Communication errors for device, DDE, or OPC® tags. Important: To log communication errors, you must also select the Communication Status check box in the Startup editor, or type the command ComStatusOn at the command line. Tag Write Any tag write (not write errors). Tag writes are done by the = (Equal), Ramp, Set, and Toggle commands, as well as by downloading data from numeric input, string input, and recipe fields in a graphic display.
You can also use the EchoOff and EchoOn commands to control activity logging. For more information see Appendix A, RSView32 commands. Editing activity log setup You can edit the activity log setup during development or runtime. If you change the activity log setup at runtime, the changes will not take effect until you stop activity logging and then restart it. To edit the activity log setup: 1. Open the Activity Log Setup editor. 2. Make the required changes. 3. Save the changes.
Act Activity Activity bar bar Status bar Status bar To show and hide the activity bar, click Activity Bar on the View menu for the Project Manager. When Activity Bar has a check mark beside it, the activity bar is visible. You can also use the ActivityBarOn and ActivityBarOff commands to show and hide the activity bar. To undock the activity bar, place the pointer over the grey area between the Clear and Clear All buttons, and then drag the mouse until the bar is where you want it.
To undock the activity bar, place the pointer here and drag the mouse. When the activity bar is undocked, you can make it any size you like, for example to view more than one message at a time. To resize the bar, grab an edge or corner and drag until the bar is the desired size. Messages in the activity bar The types of messages that appear in the activity bar depend on what is set up in the Categories tab of the Activity Log Setup editor. Activity messages are preceded by a blue, yellow, or red icon.
Query. For more information, see “Tracking system usage” on page 8-19 and “Activity log files” on page 16-7. To open the Activity Log Viewer: 1. In the Project Manager, open the System folder. 2. Open the Activity Log Viewer by doing one of the following: double–click the Activity Log Viewer icon right–click the Activity Log Viewer icon and then click Show Selecting a record When the Activity Log Viewer opens, it displays the contents of the most recent log file. To select another file: 1.
Understanding records The Activity Log Viewer displays up to 32,767 records. A record is made up of the items shown below: Record Drag to resize columns. The icon at the beginning of the record can be red, yellow, or blue. The colors provide a visual cue to the importance of the record. Red indicates an error, yellow indicates a warning, and blue indicates information.
Starting and stopping activity logging By default, activity logging is on when you start a project. However, if you need to start or stop activity logging, you can use any of the following methods: Ways to start activity logging In the Macro editor, create a startup or login macro that includes the ActivityOn command. In the Graphic Display editor, create a button object and specify the ActivityOn command as the press action. When the button is pressed, activity logging starts.
In the Events editor, specify the ActivityOff command as the action for an event. On the command line, type ActivityOff and then press Enter. For a complete list of RSView32 commands and command syntax, see Appendix A, RSView32 commands, or see Help.
9 Chapter Configuring events Events are expressions that trigger actions. Expressions are equations containing tag values, mathematical operations, if–then–else logic, and other built–in RSView32™ functions. Actions are RSView32 commands, symbols, or macros.
Summary of steps The main steps for configuring events are: set up the evaluation interval for the event file in the Event Setup dialog box create the events in the Events editor The Events editor To open the Events editor: 1. In the Project Manager, open the Logic and Control folder. 2.
Using the Accept and Discard buttons When you enter information in the editor, the Prev and Next buttons change to Accept and Discard. Click Accept to save information. Click Discard to discard information. Setting up the evaluation interval To set up the evaluation interval for the event file: 1. On the menu bar, click Setup and then click Event Setup. The Event Setup dialog box opens. 2. Type a brief description of the event file.
using tags, don’t specify an evaluation interval faster than the scan class background period, DDE server polling rate, or OPC® server update rate. 4. Click OK. Creating events An event is made up of an expression and an action. When the expression changes from false on the previous evaluation to true on the current evaluation, the action is triggered. The following illustration shows an event file.
To create an event: 1. In the Action field, type an RSView32 command, a macro, or a symbol that will run when the expression goes from false to true (but not from true to false). IMPORTANT Do not create events that depend on other events. Events are not processed sequentially. For a complete list of RSView32 commands, see Appendix A, RSView32 commands, or see Help. For more information about macros and symbols, see Chapter 15, Setting up navigation. 2. To disable the event, clear the Enabled check box.
Editing events You can edit events during development or when you run the project using RSView32 Works. 1. Open the event file you want to edit. 2. Use the Prev and Next buttons to move among events. Make the required changes. 3. Save the changes. If you change the event file while running the project, the changes won’t take effect until you stop running the file and then restart it. Starting and stopping event processing There are many ways to start and stop event processing.
In the Graphic Display editor, create a graphic object and attach touch animation with the EventOn command as the action. When the object is touched, event detection starts. On the command line, type EventOn and then press Enter. Ways to stop event processing When a project stops, event processing stops as well. To stop event processing without stopping the project, use any of the methods below.
10 Chapter Adding security This chapter describes the RSView32™ security system, and outlines how to: configure security codes secure RSView32 commands, macros, graphic displays, OLE objects, and tags configure user accounts use the electronic signature button to keep track of tag writes and command usage secure the RSView32 Project Manager prevent users from going outside of the project About security Use security to prevent users from accessing certain parts of the system.
Security is based on a system of codes. Each code allows users with security privileges for that code to access the RSView32 features allowed by that code. Users can be assigned combinations of security codes, allowing each user to access a different set of features. Security function The user_haspermission security function allows you to check whether the current user has a specific security code. You can use this function anywhere that expressions are used.
Example: Assigning security codes The following security codes are set up: the DataLogOn command is assigned security code B a graphic display named Boiler is assigned security code D a tag named Tag1 is assigned security code E In the User Account editor, the following security codes are assigned: Alice is assigned security codes B, D, and E Simon is assigned security codes B and D This means that Alice has access to the command, the display, and the tag.
assigning security codes to users in the User Accounts editor Before you begin Before you begin, gather a list of: RSView32 commands and macros For a complete list of RSView32 commands, see Appendix A, RSView32 commands, or see Help. graphic displays, OLE objects with verb animation, and tags users or groups of users requiring accounts Configuring security codes In the Security Codes editor, you create a list of RSView32 commands and macros and then assign a security code to each item in the list.
Security codes RSView32 has 17 security codes: an asterisk (*) and the letters A through P. The asterisk is for unlimited access, and the letters are for limited access. The letters are not hierarchical—that is all letters provide the same level of security. You do not have to use all of the security codes, nor do you have to assign the codes in a particular order. For example, you can choose to use only the codes D and P and you can assign P before you assign D.
Setting up security by inclusion Security by inclusion means all RSView32 commands and all macros requiring security are listed in the Security Codes editor. 1. For Default, leave the security code as *. 2. In the Command field, type the command or macro you want to assign security to. If you assign security to the Login and Logout commands, be sure to give all users, including Default, access to these commands. Otherwise, users might be locked in or out of the system.
4. If you like, type a descriptive remark in the Description field. 5. Repeat steps 2 through 4 for each command and macro. 6. Save the configuration by choosing Close. Preventing access to the Security Codes and User Accounts editors Both the Security Codes editor and the User Accounts editor have commands that can be used at runtime to open these editors. The Security command opens the Security Codes editor and the Account command opens the User Accounts editor.
objects configured with touch animation Alarm Identification field in the Tag Database editor By default, strict security is on. For most projects, strict security is desirable. IMPORTANT Strict security always applies to graphic displays, OLE verbs, and tags. If you assign security to any of these items, their security is always checked. Turning off strict security If you turn off strict security, security access to graphic displays, OLE verbs, and tags is still checked.
Assigning security to a graphic display Security is assigned to a graphic display in the Graphic Display editor. You can assign security while you are creating a graphic display, or you can assign it later. 1. In the Graphic Display editor, open Display Settings by doing one of the following: click Display Settings on the Edit menu right–click the mouse button and then click Display Settings Select a security code. 2. Select a security code. 3. Click OK.
Assigning security to an OLE object Security is assigned to a graphic object with OLE verb animation in the Graphic Display editor. IMPORTANT Once an OLE object is activated, there is no security within the associated application. Therefore, the only way to secure the application is to assign security to the OLE object. 1. Open the Graphic Display editor. 2. Select the OLE object you would like to secure. 3.
7. Click Apply. Assigning security to a tag Security is assigned to tags in the Tag Database editor. By assigning security, you can restrict write access to a tag so a user cannot change the tag’s value. 1. Open the Tag Database editor. 2. Select the tag that requires security. 3. Select a security code. Select securitycode. code. Select aa security 4. Click Accept.
Configuring user accounts Once you have assigned security codes to RSView32 components, assign these codes to users. You can configure user accounts in the User Accounts editor, or, if you are using Windows Server 2003, Windows XP, Windows 2000, or Windows Vista, you can use the Windows user list instead of configuring a custom RSView32 list. To open the User Accounts editor: 1. In the Project Manager, open the System folder. 2.
About the default user The default user account is active when no user is logged into the system. When setting up security, keep the following in mind: You can change the security codes for the default user account, but you cannot change the account ID, or add a password. For a completely secure project, clear all security codes for the default user account. This ensures that the default user does not have any privileges.
Once you have added users from the Windows user list, you will have to specify security access for each user you added in the RSView32 User Accounts editor. To create user accounts using the User Accounts editor: 1. In the Account ID field, type a user ID up to 20 characters long. The ID can include letters and numbers, but cannot include spaces, or the characters / \ [ ] ; : | = , . + * ? < >. The ID also cannot be NULL.
To create users from the Windows domain user list: 1. On the Setup menu, click Windows Security Options. In the Windows Security Options dialog box you select which Windows users you want to make up the RSView32 user accounts list. All users must be in the same Windows domain. All Windows users added to the RSView32 User Accounts will have the same security codes as DEFAULT in the User Accounts editor. You will have to specify individual users’ security access in the User Accounts editor’s main dialog. 2.
logout macro could contain commands to close all active screens and redefine sensitive keys. 5. For more information on macros, see “Creating macros” on page 15-7. Using electronic signatures to prevent unauthorized actions Use the electronic signature button to prevent unauthorized users from writing values to tags and running commands. You can set up the button so that the action the button press performs must be approved by a pre-authorized verifier before the action is initiated. 6.
Preventing users from going out of the RSView32 project To prevent users from going outside of the RSView32 project, do one or more of the following: do not include title bars or minimize and maximize buttons on graphic displays by deselecting the appropriate options in the Graphic Display editor’s Display Settings dialog box. For details, see page 11-17.
create a button and use the Login command as the press action. When a user presses the button, the following dialog box appears: If your project does not require users to log in when the project opens, and you are not using the Windows Security Options, the user called DEFAULT is logged in automatically.
The new password is typed here to confirm it. The new password is also added to the Password field of the User Accounts editor. IMPORTANT If your project is using the Windows Security Options, and you change your password using the RSView32 Password command, your password for Windows Server 2003, Windows XP, Windows 2000, or Windows Vista domain will automatically be changed as well.
11 Chapter Creating graphic displays This chapter describes the Graphic Display editor and outlines how to: set up the drawing environment draw, edit, and arrange graphic objects use objects from the Graphic Library editor About graphic displays and graphic objects A graphic display represents the operator’s view of plant activity. The display can show system or process data and provide operators with a way to write values to an external device such as a programmable controller.
The Graphic Display editor To open the Graphic Display editor: 1. In the Project Manager, open the Graphics folder. 2. Open the Graphic Display editor by doing one of the following: double–click the Display icon right–click the Display icon and then click New The editor’s main components The figure below shows the main components of the Graphic Display editor. Each component is briefly described in the table on the following page.
The Graphic Display editor’s main components are: Toolbar Contains buttons for commonly used menu items. The figure on the previous page shows only one toolbar but there are several, including toolbars for drawing tools, line and fill colors, and fill patterns. You can hide or show toolbars using the View menu, and you can move the toolbars anywhere on the screen. For more information about toolbars, see page 11-4 Drawing area Is the area for creating graphic displays.
When you right-click an object . . . . . . the context menu opens. It contains menu items for working with the selected object. Switching between normal and test modes Test mode Test mode Normal mode mode Normal To quickly test objects in a graphic display, use test mode. When you are finished testing, switch back to normal mode to continue editing. To switch between test and normal modes, use the buttons on the toolbar or the items on the View menu.
dock them to an edge of the window (except the ActiveX Toolbox) A toolbar that is docked. Toolbars that are floating.
Selecting a drawing tool The Drawing Tools toolbox contains tools for creating, selecting, and rotating objects. The tools are also available on the Objects menu. Drawing Tools toolbox Objects menu Before you can draw an object, you must select the appropriate tool. To select a drawing tool, click the tool in the toolbox or on the Objects menu. When you click a tool, the pointer changes to show which tool is active.
Selecting colors The color palettes contain the colors you can assign to objects. To show and hide the color palettes, click them on the View menu. You can also select colors using the color items on the Attributes menu. You can select colors before you draw an object, or you can apply them to an existing object. Use the Line Color palette to select a color for the outline of an object, for text, or for hollow objects.
Selecting and deselecting objects Select tool tool Select To work with an object, you must first select it with the Select tool. You can click this tool in the Drawing Tools toolbox or on the Objects menu. To deselect a drawing tool, click the Select tool in the toolbox or on the Objects menu. To select Do this An object Click the object. Several objects Click the first object, Ctrl–click additional objects. All objects in an area Drag diagonally to draw a selection border around the objects.
The grid can be active or passive. If you turn on Snap to Grid, the grid is active and all the objects you draw or position are pulled to the closest grid point. This makes it easy to align and size objects. If you turn off Snap to Grid, the grid is passive and does not affect your drawing or the position of your objects. Turn off the grid to either draw or position an element between the grid lines. Turn on the grid and the next object you draw or place will automatically be aligned with the grid.
To rotate an object: 1. Click the Rotate tool. 2. Click the mouse button. A small circle with a crosshair appears. This is the anchor point that is used as the center of rotation. To move the center of rotation, drag the crosshair. You can place the crosshair inside an object... ... or you can place it outside an object. 3. Place the pointer on an edge of the object and drag the object to rotate it. To rotate the object in five–degree increments, press Ctrl while you drag. 4.
Zooming in and out Zoom In Zoom In Zoom ZoomOut Out To magnify or reduce your view of a graphic display, use Zoom In and Zoom Out. Zoom In magnifies objects, Zoom Out reduces magnification. To zoom in on objects: 1. Select the objects you want to zoom in on. 2. Click Zoom In on the View menu or click the Zoom In button on the toolbar. To zoom out: Click Zoom Out on the View menu or click the Zoom Out button on the toolbar. You can also click Cancel Zoom on the View menu.
Setting up the display To set up a graphic display, use the Display Settings dialog box. To open the Display Settings dialog box, do one of the following: click Display Settings on the Edit menu right–click in an empty area of the display and then click Display Settings on the context menu The Display Settings dialog box contains many options for defining the appearance of a graphic display. You can edit these options any time during the drawing process.
Creating a default To create your own default settings, click Set as Default. When you open a new graphic display, it will use the display settings you have configured. Note that if you click Set as Default the settings for the current display are not saved. You must also click OK to save the settings for the current display. Using the Display Settings dialog box The Display Settings dialog box has two tabs, Properties and Behavior.
These options are described in the sections that follow. Specifying the display type Replace Replace is the default display type. Use this option if you want the graphic display to replace other open graphic displays when it opens. RSView32™ will close any graphic display that the newly opened display overlaps. This way you don’t need to issue separate commands to close the other displays. Overlay Use this option if the graphic display doesn’t need to replace others or appear on top.
than one graphic display of the On Top type is open at once, the display that has focus, or had the most recent focus, appears on top. Use the PullForward, PushBack, and SetFocus commands to cycle through multiple On Top and Overlay screens. Allowing multiple running copies Use this option with displays of type Overlay or On Top. Check this box to allow more than one copy of the graphic to be displayed at runtime.
Specifying caching Cache After Displaying Select Yes to load the graphic display into the display cache when it is displayed for the first time. Placing the graphic in the cache makes subsequent displays of the graphic faster because it does not have to be read from disk. You can have up to 200 graphic displays in the cache. We suggest you use this option for large or complex displays only, to minimize the use of system resources.
Specifying the title bar and other display attributes Title Bar To have a title bar appear on the graphic display at runtime, select the Title Bar check box. If the Title Bar check box is not selected, the check boxes for the System Menu, Minimize button, and Maximize button are not available (because these items all appear on the title bar). You can also type a title for the graphic display, which will appear in the title bar at runtime in place of the component name.
Size to Main Window at Runtime If you select this check box, the graphic display will be the size of the RSView32 main window when the display starts running. The graphic display is panned or scaled, depending on which option is selected under Resize. See page 11-20 for more information. RSView32 has resolution–independent graphics. This means that no matter what resolution you use to create your graphic displays, they will automatically resize to fit the monitor on which they are displayed.
Preventing scroll bars on the RSView32 main window If a graphic display is larger than the RSView32 main window, scroll bars will appear on the main window and will remain there even if subsequent displays are smaller than the main window. To prevent scroll bars, all graphic displays must be smaller than the working area in the RSView32 main window.
Specifying display size To set the display size, do one of the following: select Use Current Size. When you save the graphic display, the size of the window at that time becomes the default size. select Specify Size in Pixels, and type values in the Width and Height fields. The window size and position you specify here can be overridden by the RSView32 Display command. The Display command accepts size and position parameters, which override the Display Settings options.
When Resized Select Pan or Scale. Pan resizes the display so objects retain their original size when the display size changes. For example, if the display was resized to one quarter its original size, only one quarter of the display would be visible. In this case scroll bars appear for viewing the rest of the display. Scale resizes the display so objects in the display are magnified or reduced to retain their size in relation to the display size.
For more information about the Display command, see Appendix A, RSView32 commands, or see Help. Specifying a security code To restrict access to the graphic display, select a security code. For detailed information about security, see Chapter 10, Adding security. Specifying background color To select a background color, click the Background Color box, and then click a color on the palette. 4.
Specifying startup and shutdown commands Type commands or macros in the Startup and Shutdown fields, or click the ... buttons to open the Command Wizard and select the commands or macros. To run RSView32 commands or macros each time this graphic display starts or stops, specify the commands or macros. The startup command runs before the graphic opens so commands such as UploadAll or RecipeRestore will not work in a startup macro.
Specifying colors for input fields Input fields are created with the Numeric Input, String Input, and Recipe drawing tools. At runtime, operators can use these fields to read values from or write values to the programmable controller. Click the colored boxes to open the color palette, and then choose colors. Text color is the color of the text in the input field. Fill color is the background color of the input field. The text changes to white and the background to red if an error occurs at run time.
You can create a tab sequence for interactive objects that use index numbers. For details, see “Creating a tab sequence” on page 12-47. Beep on Press Check this box if you want the computer to beep when a button object or an object with touch animation is clicked. Highlight When Cursor Passes Over It Check this box to turn on the highlight for interactive objects. Click the colored box to open the color palette and then choose the highlight color.
The following illustration shows the two types of highlight: This object is an interactive object, but it is not the object with input focus. This object is the one with focus*as indicated by the cursor. The highlight box is a different color than the highlight box for the interactive object. An object can have both types of highlight at one time.
The keypad for numeric input fields allows numeric entry only. Displaying graphics more quickly Graphic displays appear more quickly if they have been stored in the display cache. You can place up to 200 graphic displays in the cache. To cache displays: select the Cache After Displaying option in the Display Settings dialog box. For details, see page 11-16. use the [cache] parameter with the Display command. The [cache] parameter loads a graphic display into the cache without displaying it.
example, the command Display Bakery /Z loads the graphic display called Bakery into the cache but does not display it. When the graphic is called up, it is displayed quickly. The command Display Bakery /ZA loads the display into the cache and continually updates the values in the display. For more details about the Display command, see Appendix A, RSView32 commands, or see Help. Removing displays from the cache To remove all graphic displays from the display cache, use the FlushCache command.
ActiveX objects (formerly called OLE custom controls or OCXs): control objects such as gauges, sliders, and buttons, and objects you create yourself using a tool like Visual Basic®. These objects allow an external action, such as a mouse click, to initiate an action within RSView32. The ActiveX objects that are available depend on the software installed on your system. Most objects, including OLE objects, can have animation attached to them. For more information, see Chapter 12, Animating graphic objects.
Drawing a rectangle or square Rectangletool Rectangle tool Rectangle tool Use the Rectangle tool to draw a rectangle or square. 1. Click the Rectangle tool. 2. To draw a rectangle, drag the drawing tool diagonally until the object is the size you want. To draw a square, hold down Ctrl while you drag. Drawing an ellipse or circle Use the Ellipse tool to draw an ellipse or circle. Elliipsetool Ellipse tool tool Ellipse 1. Click the Ellipse tool. 2.
You can also use the Snap to Grid option to draw straight lines. You can change the style and width of lines using Line Properties on the Attributes menu. For details, see page 11-103. Drawing a polyline or polygon A polyline is a series of connected line segments. A polygon is a closed polyline shape. Polylinetool tool Polyline Polygon Polygontool tool Polyline Hollow polygon Filled polygon 1. Click the Polyline or Polygon tool. 2. Drag the drawing tool to create the first segment of the object.
Drawing a freehand object Drawing freehand is similar to drawing with a pen on paper. Freehand tool Freehand tool 1. Click the Freehand tool. 2. Drag the drawing tool to create the shape you want. Drawing an arc or wedge Arcs and wedges are drawn in two steps: first you create a circle, and then you reshape the circle. Arc tool tool Arc To draw the arc or wedge in 45–degree increments, hold down Ctrl while you draw. Wedge Wedge tool tool Arc Hollow wedge Filled wedge 1.
You can also use the Arc and Wedge tools to reshape any arc, ellipse, or wedge. Creating text 1. Text tool tool Text Click the Text tool. The pointer becomes an I–beam ( ). 2. Type the text. Once the Text tool is selected, you can create more than one text object. To do so, move to an empty spot in the drawing area, click, and then type the text. To edit text, select the text object and double–click. The I–beam appears. To delete text characters, use the Backspace and Delete keys.
3. Select the font style, size, and effects you want. IMPORTANT You can select any font you have installed, but TrueType™ fonts are recommended. These fonts can be resized with graphic scaling. The fonts listed here depend on the fonts you have installed in Windows. 4. Click OK. You can also choose font color using the Line Color palette or using the Line Color item on the Attributes menu.
Reshaping simple objects You can easily reshape any simple object. To reshape lines, rectangles, polylines, and polygons: 1. Place the pointer on the object you want to reshape and double– click, or right–click and then click Edit Object. The cursor changes to the Polygon tool. 2. Move the cursor over any line in the object. A handle with a cross–hair appears. 3. Drag the handle until the object is the desired shape.
Creating advanced objects To create advanced objects, use the drawing tools in the Drawing Tools toolbox or the items under the Advanced Objects sub–menu. The basic steps are: 1. Click a drawing tool and drag it to create a box approximately the size you want for the object. When you release the mouse button, a dialog box opens. 2. Configure the object by entering the required information. Most advanced objects display information about a tag.
To supply a tag name, do one of the following: type a tag name in a Tag Name field or in an Expression field Browse button click the Browse button and select a tag from the list Using tag placeholders Tag placeholders provide a way to use one graphic display to represent a number of similar operations. 4. For example, imagine you are creating displays for a plant that cans corn and beans. The machinery used in both processes is identical.
Creating a tag placeholder A tag placeholder is the cross–hatch character (#) followed by a number from 1 to 500, as shown in the example below: You can also add a folder name to the placeholder. For example, #1\PV is a valid placeholder and requires only one parameter (the folder name). For tag placeholders in alarm summary objects (when they are contained in graphic displays only), you can use wildcards in the placeholder. For example, #1\PV* is a valid placeholder.
To create a parameter file: 1. Open the Parameters editor. 2. Type one entry for each unique placeholder in the display, associating the placeholder with a tag name. For example: #1 = bean_weight #2 = bean_level #3 = bean_temp 3. Save the file with a meaningful name (for example, Beans). For tag placeholders in alarm summary objects in graphic displays only, you can use wildcards in the parameter file. For example, #1 = bean_* is a valid parameter entry.
Example: Using a Parameter File to Replace Tag Placeholders To run the display called Canning with the parameter file called Beans, type: Display Canning /PBeans Listing tag names to replace tag placeholders When you run a graphic display, you can specify the tag names using the RSView32 Display command with the /T parameter.
Example 1: Replacing tag placeholders by listing tag names To run the display called Canning with the tags Pea_Weight, Pea_Level, Pea_Temp: Type: Display Canning /TPea_Weight,Pea_Level,Pea_Temp Example 2: Replacing tag placeholders by using a folder name In the following example, the tag database contains these tags: Corn\Weight Corn\Level Corn\Temp Bean\Weight Bean\Level Bean\Temp Anywhere a tag name is required, the placeholder #1 is used for the folder name.
Creating numeric and string input fields Numeric Numeric Input Inputtool tool String Input Inputtool tool String Use the Numeric Input tool to create fields that operators can use to enter data for analog and digital tags. Use the String Input tool to create fields that operators can use to enter data for string tags. When the display runs, operators can use these fields to write values to the value table.
controller and/or save them to a recipe file. For more information on recipe files, see “Creating a recipe field” on page 11-61. If an upload fails because of a communication error, question marks appear in the numeric input fields. Colors for input fields are set in the Display Settings dialog box. For details, see “Specifying colors for input fields” on page 11-24. To create a Numeric Input field: 1. Click the Numeric Input tool. 2. Drag the mouse to draw the field. 3. Release the mouse button.
4. 11–44 Fill in the fields as follows: In this field Do this Tag Name Type a tag name or a placeholder for an analog or digital tag. For details about placeholders, see “Using tag placeholders” on page 11-37. Index Either leave the default as it is or type a number other than the default. Index numbers determine the Tab sequence for interactive objects such as input objects and buttons, and are also used in recipe files. For details, see “Using index numbers” on page 12-45.
5. In this field Do this Justification Select Left, Center, or Right to specify how the values will be aligned within the field. Leading Character Select Blanks or Zeroes. Click OK. To create a String Input field: 1. Click the String Input tool. 2. Drag the mouse to draw the field. 3. Release the mouse button.
4. Fill in the fields as follows: In this field Do this Tag Name Specify a tag name or a placeholder for a string tag. For details about placeholders, see “Using tag placeholders” on page 11-37. Index Either leave the default as it is or type a number other than the default. Index numbers determine the tab sequence for interactive objects such as input objects and buttons, and are also used in recipe files. For details, see “Using index numbers” on page 12-45.
Continuously updating tag values This field is in display mode. This field is in pending write mode. This field is in input mode. When a numeric or string input field is set to update continuously and display tag values, its appearance changes to reflect which mode the field is in. When the field is displaying a value from the programmable controller or server (display mode), the border around the field is dotted.
Keys Operators can use the following keys to retrieve data from and send data to the value table. You can re–assign these actions to other keys or assign them to button objects.
UploadAll: uploads all the values from the value table and displays them in the input fields For detailed information about commands, see Appendix A, RSView32 commands, or see Help. Using the on–screen keyboard Displays can be set up so that an operator can use an on-screen keyboard for input entry in numeric, string, and recipe input fields.
This button Does this Download For numeric and string input fields, closes the onscreen keyboard and downloads the value or text the operator typed. For recipe fields, closes the on-screen keyboard, opens the Recipe dialog box, and inserts in the Recipe File field the text the operator typed. Cancel Discards the operator’s changes and closes the on-screen keyboard. For information about setting up displays to use the on-screen keyboard see “Displaying the on–screen keyboard” on page 11-26.
4. Fill in the fields as follows: In this field Do this Expression Create an expression. At runtime, the numeric result of this expression is displayed in the Numeric Display field. For details about expressions, see Chapter 14, Creating expressions. Field Length Type a value to specify the maximum number of characters that will be displayed in this field. Be sure the field is long enough to accommodate the result of the expression. Format Select a number base for the value.
5. In this field Do this Leading Character Select Blanks or Zeroes. Justification Select Left, Center, or Right to specify how the values will be aligned within the field. Click OK. To create a String Display field: 11–52 1. Click the String Display tool. 2. Drag the mouse to draw the field. 3. Release the mouse button.
4. Fill in the fields as follows: In this field Do this Expression Create an expression. At runtime, the string result of this expression is displayed in the String Display field. For details about expressions, see Chapter 14, Creating expressions. Dimensions Type a value to specify the maximum number of characters that will be displayed in this field. Be sure the field is long enough to accommodate the result of the expression.
Creating labels Label Label tool tool Use the Label tool to create fields that display different types of tag information at runtime. All the information comes from fields you configure for the tag in the Tag Database editor. You can create the following types of labels: This label Displays Minimum An analog tag’s minimum value Maximum An analog tag’s maximum value Status The current status of a digital tag.
Select a label from the list. 4. Fill in the fields as follows: In this field Do this Tag Name Specify a tag name or placeholder. For information on placeholders, see “Using tag placeholders” on page 11-37. Field Length Type a value to specify the maximum number of characters that will be displayed in this field. Be sure the field is long enough to accommodate the label. The maximum field width depends on the type of label you are creating. 5. Label Type Select a type.
Vertical arrows move up or down in relation to a tag’s minimum and maximum values. Horizontal arrows move left and right in relation to the minimum and maximum values. For vertical arrows, if the value is less than or equal to the minimum value, the arrow is at the bottom. If the value is equal to or greater than the maximum value, the arrow is at the top. For horizontal arrows, if the value is less than or equal to the minimum value, the arrow is at the left.
4. 5. Fill in the fields as follows: In this field Do this Expression Create an expression. At runtime, the numeric result of the expression positions the arrow. For details about expressions, see Chapter 14, Creating expressions. Range To use the minimum and maximum values for the first tag in the expression, clear the Specify check box. To specify a minimum and maximum value that is different than the first tag’s, enter values in the Min and Max fields. Direction Select Vertical or Horizontal.
4. Fill in the fields in each tab to configure how you want the button to look and act, as described in the sections that follow. When finished, click OK. General 1. In the General tab, click a button style. 3D, Recessed, and Raised styles can be used only for rectangular– shaped buttons. The Beveled style supports rectangular and polygonal shapes. If you change a 3D, recessed, or raised button to another shape, or rotate it, the button automatically changes to beveled.
2. To have the cursor captured when the button is pressed at runtime, check the Capture cursor check box. When the cursor is captured, it will not move off the button until the button is released. Use this feature when you need to ensure that a button’s release action is carried out. If the Capture cursor check box is not selected, the button will behave like standard Windows buttons, allowing the user to ‘cancel’ the release action by holding the mouse and moving off the button. 3.
Momentary On: Sets the specified tag to 1 when the button is pressed (mouse button is pressed and held down) and sets the tag to 0 when the button is released (mouse button is released). Momentary Off: Sets the specified tag to 0 when the button is pressed (mouse button is pressed and held down) and sets the tag to 1 when the button is released (mouse button is released). Runs the specified RSView32 command or macro.
Down Appearance In the Down Appearance tab, specify what the button will look like when it is pressed. If you want the button to appear the same when it is not pressed and pressed, click Same as “Up Appearance”. If you want the button to appear differently, choose different options. See “Up Appearance,” above, for details about the fields. Editing a button object To edit a button object, double–click the button object to open the Button Configuration dialog box.
having to enter values one by one. Operators can then write all these values to the programmable controller with another keystroke. IMPORTANT A graphic display can have only one recipe field. To create a recipe field: 1. Click the Recipe tool. 2. Drag the mouse to draw the field. 3. Release the mouse button. 4. In the Default File Name field, type the name of the recipe file to and from which values will be saved and restored. Do not include a file extension. 5.
RSView32 automatically assigns index numbers to input objects and button objects as you create them. To check the index number for an object, double–click the object to open its configuration dialog box, and then check the number in the Index field. For details about index numbers, see “Using index numbers” on page 12-45.
4. At runtime, type values in the input fields. 5. Type a file name in the recipe field and press Enter. The recipe dialog box opens with the name in the recipe file field. If the display has been set up to use the on-screen keyboard, pressing Enter brings up the on-screen keyboard. Pressing the Download button on the on-screen keyboard opens the Recipe dialog box, where you can save the recipe file. 6. To save the values in the input fields and at the same time create a recipe file, click Save.
This is the recipe file that was created: Index number Index number Value Value Tagname name Tag Using a recipe at runtime At runtime, operators can restore values from a recipe file into input fields and send those values to the programmable controller or server. Operators can also upload values from a programmable controller or server into input fields, and then save those values to a recipe file. If an upload fails because of a communication error, question marks appear in the numeric input fields.
If the display has been set up to use the on-screen keyboard, pressing Enter brings up the on-screen keyboard. Pressing the Download button on the on-screen keyboard opens the Recipe dialog box, where you can save the recipe file. To download recipe values to a programmable controller or server: 1. Restore the values from a recipe file as follows: a. In the recipe field, type the name of a recipe file and press Enter, or click in the recipe field and press Enter. The Recipe dialog box opens.
To save recipe values from a programmable controller or server: 1. Upload the values to the input fields by pressing PgUp, or by using the RSView32 Upload or UploadAll command. 2. Save the values to the recipe file as follows: a. In the recipe field, type the name of a recipe file and press Enter, or click in the recipe field and press Enter. The Recipe dialog box opens.
Tag substitution does not work for text objects you create using the Text tool. To replace text: 1. Select an object or group of objects. To select all the objects in the display, click Select All on the Edit menu. 2. On the Edit menu, click Tag Substitution. 3. Click the down arrows to display a list of the possible text items you can search for and replace, or type text in the Search for and Replace with fields.
To replace the text, click Replace or click Replace All. To move to the next selected object that uses the text string, click Next. 5. When all replacements are done, click Close. Creating and editing OLE objects OLE stands for Object Linking and Embedding. OLE objects are objects created in other Windows applications and linked to or embedded in an RSView32 graphic display. RSView32 is an OLE client application, which means it cannot be embedded in other Windows applications.
embedding pastes the object into the graphic display and allows it to be edited. If the source file is changed, the object in the display is not affected. When you double–click an embedded object to edit it, the Graphic Display editor’s toolbar is replaced by the application’s toolbar. A border appears around the object to indicate that it can be edited. This is called in–place editing. If you move your project, embedded objects are automatically moved with the project. To create an OLE object: 1.
6. Click OK. Other methods for inserting OLE objects You can also insert OLE objects by: copying the information from the source file onto the clipboard and then choosing Paste Special choosing Insert Object on the Edit menu. You can then select an object type or file. Converting OLE objects The reasons to convert an object are: to change any type of embedded vector–based object into a polygon that is more readily manipulated7.
To convert an object: 1. Do one of the following: select the object and cut it to the clipboard copy the object from its source application to the clipboard 2. On the Edit menu, click Paste Special. The Paste Special dialog box opens. 3. Click the Paste or Paste Link button. Paste copies the contents of the clipboard into the active graphic but does not link to the source application. This is an embedded object.
Creating and editing ActiveX objects An ActiveX object is a software component that is supplied independently from RSView32 through products such as Microsoft® Visual Basic, Office 97, and many other third–party applications. An ActiveX object provides functions that can be accessed through the object’s properties, events, and methods.
from other controls and could trigger other events. You can use the RSView32 Invoke command as the external event that calls a method. For details about attaching control to an object’s methods, see page 12-39. To create an ActiveX object: 1. Click ActiveX Control on the Objects menu or click the ActiveX Control tool in the Drawing Tools toolbox.
The object appears in the graphic display. To edit the object’s properties, right–click the object, then click ActiveX Property Panel on the context menu. For details, see “Using the ActiveX Property Panel,” next. To attach control to the object so it can interact with RSView32, use the ActiveX Property Panel and the ActiveX Control commands on the Animation context menu. For details, see “Configuring ActiveX control” on page 12-33.
Click for help on the selected property. Drag splitter bar to see more properties. Click for help on the property panel. 3. In the column on the right, type the value for the property. You cannot specify values for properties that are read only. If a selection list or window is available for the property, when you click in the column the selection list or window opens. Select the value to use for the property. 4.
these controls, see the ActiveX Forms 2.0 sample graphic displays in the Samples project. To add tools to the ActiveX Toolbox: 1. If the toolbox is not open, click ActiveX Toolbox on the View menu. 2. Select the page of the toolbox to add objects to. 3. Right-click the page and click Additional Controls. 4. Click the checkboxes of the tools to add from the list of installed controls, then click OK.
3. Click Rename or Delete Page on the context menu. 4. If renaming the page, type a name in the Caption field. You can also type descriptive text in the Control Tip Text field. This text appears when the operator positions the cursor over the page tab at runtime. Note that the page with focus is deleted when you choose Delete Page, even though the tab for that page may not be visible. When a tab has focus (is selected) a dotted line appears around the label text.
Recording and authorizing run-time changes using electronic signatures RSView32 includes an electronic signature verification and authorization feature that provides a way to secure operations by verifying the identity of the operator before an action can occur. When the operator clicks this button, the RSView Electronic Signature dialog box opens, and the user must be authenticated before writing a new value to the tag.
For added security, the signature button can also be set up so that authorization by another person, such as a supervisor, is required before the operation can be carried out. At run time, the action can be prevented from being carried out and an error message can be displayed if a user name or password is incorrect, or if other information, such as an operator’s comment, is required but not provided.
4. In the Insert an ActiveX Control dialog box, click RSView32 Signature Button, and then click OK. 5. Double-click the button to set it up. 6. In the RSView32 Signature Button Properties dialog box, fill in the fields in each tab to set up the button’s appearance and what it does, as described in the sections that follow. 7. When you are finished, click OK.
Setting up the runtime behavior of the signature button When the operator clicks the signature button at run time, the authentication dialog box appears. In the Signature tab, set up how the authentication dialog box behaves at run time. Operation Click an operation in the list: Set Value sets the value of a tag. Send Command issues a command. Type the title that is displayed in the title bar of the authentication dialog box at run time.
set for the tag. If maximum and minimum are the same value, they are ignored. When you click an option here … … the options displayed change here. Tag Name Minimum Specify the tag to write a value to at run time. Specify the minimum allowable value that the tag can be set to. Maximum Specify the maximum allowable value that the tag can be set to. Specify the number of decimal places that are used to show current and entered tag values in the authentication dialog box.
If the button’s operation is Send Command, type the command string, or click the Browse button to open the Command Wizard. The command string must include the command name and the parameters required for the command. RSView32 command When you click an option here … … the options displayed change here. Type the name of the domain the operator and approver are members of, or click the Browse button, and then select a domain.
Specify the name of the group that the approver must be a member of. If the Approver group box is blank, the approver does not need to belong to any group. Approver group Specifying colors for the signature button In the Color tab, specify the colors for the background and foreground of the signature button. Properties Select the property for which you want to specify a color. Click the color set you want to use. You can use either a standard set of colors, or you can select the Windows System Colors.
You can also use the ActiveX Property Panel to change other properties for the button, such BackColor, Height, and Width. For details about using the ActiveX Property Panel, see page 11-75. Naming graphic objects Once you have drawn a graphic object, you can name it. Naming a graphic object allows you to manipulate the object using commands (for example, when using the Invoke command with an ActiveX object). You can also give the object a tooltip description.
5. Click OK to save the changes, or click Cancel to discard the changes. Working with objects Once you have drawn an object, you can select the object and edit it. You can: move objects copy objects duplicate objects resize objects (except text objects) Moving objects You can move objects using the mouse or the keyboard. The keys give you fine positioning, allowing you to move objects in small increments. To drag objects: 1. Select one or more objects. 2.
You can move several objects at once by selecting them all and then dragging one of the selected objects. To move objects in small increments: 1. Select one or more objects. 2. Hold down Shift while you press an arrow key. Holding Shift is the same as pressing the left mouse button. Use the plus (+) and minus (-) keys to increase or decrease, per press, the distance moved by the arrow keys.
When you press Ctrl, a plus sign is added to the cursor. 3. When the object is where you want it, release the mouse button and Ctrl key. A new copy of the object is created. Copying and pasting objects You can cut, copy, or paste objects using the menu items on the Edit menu or the buttons on the toolbar. When an object is copied, any animation attached to the object is also copied. If a group is copied, the new copy of the group can be ungrouped to individual objects, just like the original.
To remove the original object, click Cut. To retain the original object, click Copy. To paste objects: Paste 1. Click in the Graphic Display editor. 2. Click Paste on the Edit menu or click the Paste button on the toolbar. To delete objects: Select one or more objects and then click Delete on the Edit menu, or press Delete on the keyboard. Duplicating objects Unlike Cut and Copy, Duplicate does not use the clipboard. Duplicate 1. Select one or more objects. 2.
Duplicate also duplicates actions. For example, if you duplicate an object, move it, and then duplicate it again, the second Duplicate will, in one step, duplicate and move the object. This is useful for creating a series of objects with an equal distance between them. Duplicate works until you deselect the object. When an object is duplicated, any animation attached to the object is also duplicated.
3. Drag the handle until the object is the desired size or shape. For perfect circles and squares, hold down Ctrl while you drag a corner handle. To maintain the object’s original proportions (width to height), hold down Shift while you drag a corner handle. When advanced objects, such as input fields, are resized, the font is resized to fit the new boundary. To resize an object in small increments using the keyboard: 1. Select the object. 2. Place the pointer on one of the handles.
align objects with each other space objects horizontally or vertically flip objects horizontally or vertically Grouping and ungrouping objects Grouping combines several objects into a single object so you can manipulate them as a single object. You can attach animation to a group, and any animation attached to individual objects in the group remains active. To group objects: Group 1. Select all the objects you want grouped. 2. Click Group on the Arrange menu or click the Group button on the toolbar.
To ungroup objects: Ungroup 1. Select the objects you want to ungroup. 2. Click Ungroup on the Arrange menu or click the Ungroup button on the toolbar. The handles around the group are replaced with handles around each object. Select the group. Ungroup it. Ungrouping deletes any animation attached to the group, because the group no longer exists. However, animation attached to the individual objects that were in the group remains active.
To use group editing, double–click on the grouped object. A rope–like border appears around the group. Double–click inside this box to access another group or to access the individual objects. Double-click to select the object. A rope-like border appears. This border indicates that this is a group. Click again. Handles appear. The handles show the individual objects within the group. When you double–click, you are in group edit mode.
To bring an object to the front: 1. Select an object. 2. Click Bring to Front on the Arrange menu or click the Bring to Front button on the toolbar. Bring to Front Select the object from behind. Bring the object to front. To send an object to the back: Send to Back 1. Select an object. 2. Click Send to Back on the Arrange menu or click the Send to Back button on the toolbar. Select the object. Send the object to back.
Aligning objects Objects can easily be aligned with each other and with the grid. Align objects with each other when you want the tops, bottoms, or sides to line up. 1. Select the objects you want to align. 2.
Aligning objects left, right, and center Select objects Align left Select objects Align right Select objects 11–98 RSView32 User’s Guide Align center
Aligning objects top, middle, and bottom Align top Align middle Align bottom Spacing objects With Space Vertical and Space Horizontal, objects are moved vertically or horizontally to have the same amount of space from the center point of each object. 1. Select the objects you want to space. 2. Click the appropriate button or menu item: This button or menu item Does this Space Horizontal Places the centers of the selected objects an equal distance apart horizontally.
Centers are separated by an equal vertical distance Select objects Space vertically Centers are separated by an equal horizontal distance Select objects Space horizontally Flipping objects Flipping an object creates a mirror image of that object. You can flip most objects. 1. Select an object. 2.
Select object Flip vertical Select object Flip horizontal Applying colors You can define both line and fill colors for an object. Line color applies to the outline of an object. Fill color applies to the inside of an object. To make objects blink, attach color animation to the objects. For details, see page 12-13. To apply colors before drawing: 1. Select line and fill colors from the color palette or from the Attributes menu. 2. Select a drawing tool and draw the object.
Applying colors to text To apply color to text, use the Line Color palette, or click Font on the Attributes menu and then click a color in the Font dialog box. Applying fill patterns Fill patterns apply to the interior of objects. Closed objects such as rectangles, circles, polygons, text objects, and wedges are completely filled. Open or partially open objects, such as polylines or freehand objects, can also take a fill pattern.
To apply a fill pattern before drawing: 1. Select a drawing tool. 2. Select a fill pattern from the Attributes menu. To apply a fill pattern to an existing object: 1. Select one or more objects. 2. Select a fill pattern from the Attributes menu. How colors and patterns work Color is applied to graphic objects with patterns as follows: the pattern is the selected line color the background is the selected fill color Changing line properties You can change line width and style.
2. Specify a line width and style. Line styles are available only when the line width is 1. The styles are: Solid Dash Dot Dash-Dot Dash-Dot-Dot 3. Click OK. 4. Click Line Color or Fill Color on the Attributes menu to apply line or fill colors. Line style uses both the line color and fill color attributes. Line color applies to the line, and fill color applies to the spaces in the line. For example, to obtain the dash–dot line, choose black as the line color, and choose white as the fill color.
Peeking at objects Use Peek to view any or all of the following objects in a graphic display: obscured (hidden) objects numeric or string input objects the recipe object objects with animation objects linked to a particular tag When Peek is turned on, a red box appears around all selected graphic objects.
To specify which objects you want to peek at: 1. On the View menu, click Peek Settings. 2. Select the check boxes for the objects you want to view. To select animated objects, check the Animated Objects check box, and then select the individual types of animation. When you check By Tag, the field below it is active. To list the tags associated with a graphic display, either type a tag name, or click the arrow beside the By Tag field and scroll through the list.
To turn Peek on and off: click Peek On on the View menu click Activate Peek in the Peek dialog box When Peek is on, the cursor looks like this: Peek is automatically turned off as soon you do any action in the Graphic Display editor. For example, if you are peeking at objects and then move an object, Peek is turned off. Creating a background for your display You can create a background for your graphic display by converting objects to wallpaper.
To convert objects to wallpaper: 1. Select one or more objects. 2. On the Edit menu, select Wallpaper and click Convert to Wallpaper. To unlock wallpaper: On the Edit menu, select Wallpaper and click Unlock Wallpaper. All objects that were previously converted to wallpaper will be unlocked. Importing graphic files from third–party applications RSView32 can import the following types of files: File extension Type of file .gfx Graphics .mgx, .mgl ControlView™ for MS-DOS® graphic files .wmf, .
To import files: 1. In the Graphic Display editor, click the File menu and then click Open. 2. In the Open dialog box, go to Files of type and select the type of file you want to import. 3. Select the directory and file to open. 4. Click Open. 5. If the Convert Object dialog box appears, click Yes to convert the object to a native RSView32 object or click No to leave the object in its original format. Transparent backgrounds for image files RSView32 supports transparent backgrounds for .
Using bitmaps Bitmaps consume Windows resources, so when using bitmaps follow these guidelines: Use device–dependent bitmaps Device–dependent bitmaps (.bmp files) display faster than display– independent bitmaps (.dib files) because the RSView32 Graphic Display editor is optimized for device–dependent bitmaps. Also, you can in–place edit device–dependent bitmaps using the Microsoft Paint program. Avoid unnecessary color depth Create bitmaps in the lowest color depth possible.
dither colors (that is, alternate pixels of different colors to approximate another color). Do not use the Scale option The Scale option in the Display Settings dialog box causes the contents of a graphic display to change size to suit the size of the graphic display’s window. To speed up the display of a graphic containing bitmaps, choose Pan rather than Scale because bitmaps take longer to draw when they are scaled to a size different from their original size.
Using graphic libraries RSView32 comes with a set of libraries that contain graphic objects and displays. Additional libraries are installed if you install the RSView32 Resource Kit. Many of the objects are preconfigured with animation. You can: look at the objects and displays to get ideas for your own project drag and drop objects from the libraries into your own displays Use the objects as they are or change them to suit your needs.
double–click the Library icon right–click the Library icon and then click New 3. When you are finished creating the library, click Save or Save As on the File menu and name the library. The library name is added to the other names in the right pane of the Project Manager. To add a library to a project: 1. In the Project Manager, open the Graphics folder. 2. Right–click the Library icon and then click Create Shortcut to Existing Component. 3. In the dialog box, select the library file you want. 4.
object, display key, or global key with the PrintDisplay command as the press action, or provide a command line in the graphic display. When you use the PrintDisplay command RSView32 prints the entire display, even if parts are covered by other displays. You can also use the ScreenPrint command to print an image of whatever shows on the monitor. For more information about these commands see Appendix A, RSView32 commands, or see Help.
12 Chapter Animating graphic objects This chapter describes the various types of animation you can attach to graphic objects, and outlines how to: use tag names, tag placeholders, expressions, and commands when attaching animation use Object Smart Path™ (OSP) to quickly define an object’s range of motion attach object and display key animation attach animation to OLE objects attach control to ActiveX® objects Types of animation Once you have created graphic objects, you can: attach animation that links an
attach control to ActiveX objects so you can: map tags to an ActiveX object’s properties so changes to the object’s properties change the tag’s value and, in some cases, changes to the tag’s value change the object’s properties map commands to an ActiveX object’s events so commands run based on the object’s events map tags to event parameters Which objects can have animation? All graphic objects can have animation attached to them. Groups of objects can also have animation attached.
To attach key animation, use the Object Key and Display Key dialog boxes. For information about key animation, see “Associating objects and displays with keys” on page 12-42.
About the Animation dialog box The Animation dialog box is a floating dialog box, which means you can have it open all the time and can move it around the screen, select other objects, and open other dialog boxes. Animation tabs Expression area Expression result Minimum and maximum values Animation Tabs Click the tab for the type of animation you want to configure. Expression Area Create one or more expressions either by typing them, choosing the Expression button, or both.
For more information about creating expressions, see Chapter 14, Creating expressions. Expression Result Specify how the object’s appearance should change based on the result of the expression. The fields in this area change for each type of animation. For some types of animation, you have to specify a change of state. For example, an object with visibility animation will switch between visible and invisible. For other types of animation, you have to specify a range of motion.
Close: Prompts to apply changes and closes the dialog box. Using Object Smart Path to visually set animation Because the Animation dialog box stays open, you can go back and forth between the dialog box and the graphic display. This makes it easy to set the range of motion for an object because you do not have to know how many pixels you want an object to move. Instead, use the RSView32 Object Smart Path (OSP) feature. For details, see “Defining a range of motion” on page 12-9.
Tag names You can use tag names that you have already added to the tag database or you can use a new tag name. Tag placeholders Tag placeholders allow you to create displays that can be used with different tags. A placeholder is a cross–hatch character (#) followed by a number between 1 and 500. Tag names are substituted for placeholders when the display is run. Folder names can also be substituted for part of the tag name. For example, #1\#2\MotorValve.
Using expressions Many types of animation require an expression. You can use expressions involving tag values, constants, mathematical equations, and if–then–else program logic for animation. A tag name or tag placeholder can be included as part of an expression, or it can stand alone as the entire expression. This chapter does not provide detailed information on creating expressions. If you are not familiar with the expression language, see Chapter 14, Creating expressions, before you begin.
On the other hand, you might want to limit the range of values, which you can also do by specifying minimum and maximum values yourself. For example, if you specify a minimum of 0 and a maximum of 100, the object will not react to values outside of this range. So, even if the expression results to 200, the object does not change from its At Maximum position. If an expression uses more than one tag, the first tag in the expression is used for the minimum and maximum values.
Example: Using OSP to define the range of motion for horizontal slider animation To define a range of motion for a slider object: 12–10 1. In the Graphic Display editor, create a slider object or copy a slider object from a library. 2. Open the Animation dialog box and click the Horizontal Slider tab. 3. In the Graphic Display editor, select the slider button. 4. In the Tag field of the Animation dialog box, specify a tag name. 5.
In the Animation dialog box, set this position by clicking the At Minimum check box. 6. In the Graphic Display editor, drag the button object to the position that will indicate the highest number in the range. In the Animation dialog box, set this position by clicking the At Maximum check box. 7. To save the settings, click Apply. When you finish configuring the button object, it returns to its starting position.
Configuring visibility animation With visibility animation, an object becomes visible or invisible based on a tag value or the result of a logical expression. If an object is invisible, no other animation attached to the object is evaluated to prevent unnecessary processing. To configure visibility animation: 1. Select the object. 2. Click the Visibility tab in the Animation dialog box. 3. Create an expression. The expression can be a tag name or a more complex expression.
5. Click Apply. Configuring color animation With color animation, an object changes color based on a tag value or the result of a logical expression. Specify up to 16 color changes (A to P) for any object. Colors can be solid or blinking. For each color change, specify the value or threshold at which the color is to change and specify the colors to change to. At runtime, when the value reaches or crosses the threshold, the color changes.
The parts of the list box color Fill Line color Fill color color The boxes show the line and fill colors for each threshold. If you select white as the line and the fill color, the boxes will not be visible over the white background of the dialog box. A box with two colors shows the colors the object will alternate between when blinking. Threshold value Threshold To configure color animation: 1. Select the object. 2. Click the Color tab in the Animation dialog box. 3. Create an expression.
color, place the cursor over the box, click to open the color palette, and then click the desired color. Specify the solid color here. Specify the blinking colors here. Solid colors have only one line and one fill color. Blinking colors have two line and two fill colors, which are the line and fill colors the object will alternate between when blinking. If you select blink, the two colors must be different. 7. In the Blink Rate field, specify how many seconds each blink cycle will be.
in the list box, click threshold A leave the value in the Value field as 0 for Line color, click Blink (only line color affects text) click each color box to open the color palette and then click a color 4. Click Apply. Example 2: Creating an object that changes color as the fill level changes This example describes how to create a rectangle object that changes color as the object’s fill level increases. This example uses a tag called Hopper1\FlourLevel. The tag has a range of 1 to 100.
5. Open the Animation dialog box, and click the Fill tab. Attach fill animation as follows: in the Expression field, type Hopper1\FlourLevel (this is the tag that controls the fill level) for Fill Direction, click Up click Apply 6. Click the Color tab.
for Line and Fill colors, click Blink for Line and Fill, open the color palettes and click gray for the first color and yellow for the second color Configure the color for the second warning in the list box, click C in the Value field, type 95 Red Gray Gra y for Line and Fill colors, click Blink for Line and Fill, open the color palettes and click gray for the first color and red for the second color 7. Click Apply.
To configure fill animation: 1. Select the object. 2. Click the Fill tab in the Animation dialog box. 3. Create an expression. The expression can be a tag name or a more complex expression. If a tag name is used, the tag’s value determines the fill levels. 4. Specify At Minimum and At Maximum values for the fill percentage levels. 5. Click a fill direction. 6. Select the Inside Only check box if you want the object’s outline to remain constant so only the inside fill level varies. 7.
Configuring horizontal position animation With horizontal position animation, an object moves horizontally based on the result of an expression in relation to its minimum and maximum values. The object’s horizontal position is proportional to the value of the expression. For example, if the value of the expression is halfway between the minimum and maximum values, the object will be halfway between its minimum and maximum pixel offset. To configure horizontal position animation: 12–20 1.
6. To specify minimum and maximum values, click the Specify check box and type the values. 7. Click Apply. Configuring vertical position animation With vertical position animation, an object moves vertically based on the result of an expression in relation to its minimum and maximum values. The object’s vertical position is proportional to the value of the expression.
4. Set the starting point for the object by dragging the object or by typing a value. Click the At Minimum check box. 5. Set the ending point for the object by dragging the object or by typing a value. Click the At Maximum check box. 6. To specify minimum and maximum values, click the Specify check box and type the values. 7. Click Apply. Configuring width animation With width animation, an object’s width changes based on a tag value or the result of an expression.
2. Click the Width tab in the Animation dialog box. 3. Create an expression. The expression can be a tag name or a more complex expression. If a tag name is used, the tag’s value determines the object’s width. 4. Set the minimum width for the object by doing one of the following: click a handle on the left or right side of the object and drag it to resize the object type the width you want the object to be when the expression evaluates to its minimum value Select the At Minimum check box. 5.
Configuring height animation With height animation, an object’s height changes based on a tag value or the result of an expression. The object’s height is proportional to the value of the expression. For example, if the value of the expression is halfway between the minimum and maximum values, the object will be half the full height. To configure height animation: 1. Select the object. When the object is first selected, its height is 100 percent. 12–24 2.
4. Set the minimum height for the object by doing one of the following: click a handle on the top or bottom of the object and drag it to resize the object type the height you want the object to be when the expression evaluates to its minimum value Click the At Minimum check box. 5.
halfway between the minimum and maximum values, the object will rotate half the specified amount. 9. Text, advanced objects except arrows, OLE objects, ActiveX objects, and bitmaps cannot be rotated. RSView32 does not support rotation animation for rounded rectangles because of Windows limitation. To configure rotation animation: 12–26 1. Select the object. 2. Click the Rotation tab in the Animation dialog box. 3. Create an expression.
Using the Default Center Points To use the default center points, select a button. Why use the default center points? If you set the center of rotation with the default center points, the object will rotate around the same point even if the object is resized. For example, the top– middle corner will always be the center of rotation no matter what size the object is. Specifying Coordinates The default coordinates 0,0 are the center of the object; all coordinate values are relative to the center.
To set the maximum, do one of the following and then select the At Maximum check box: click the Rotate tool and visually set the degree of rotation type the desired degree of rotation (this value is relative to the object’s current position). For clockwise rotation, use a positive number. For counterclockwise rotation, use a negative number. 6. To specify minimum and maximum values, click the Specify check box and type the values. 7. Click Apply.
To configure touch animation: 1. Select the object. 2. Click the Touch tab in the Animation dialog box. 3. In the Press Action field, type an RSView32 command or a macro. Separate multiple commands or macros with a semi–colon (;) or place them on separate lines. Multiple commands are executed in the order they are listed. If you want repeat and release actions, type commands or macros in these fields as well. Press and release actions occur when the object is pressed or released.
Configuring horizontal slider animation With horizontal slider animation, you can create a graphic object that sets the value of a tag. To do this, define a path for the object and then use the mouse to move the object horizontally. The pixel position of the object is translated into values that are written to the tag. An object can have both vertical and horizontal slider animation. To configure horizontal slider animation: 12–30 1. Select the object. 2.
7. Click Apply. Configuring vertical slider animation With vertical slider animation, you can create a graphic object that sets the value of a tag. To do this, define a path for the object and then use the mouse to move the object vertically. The pixel position of the object is translated into values that are written to the tag. An object can have both vertical and horizontal slider animation. To configure vertical slider animation: 1. Select the object. 2.
6. To specify the minimum and maximum values that will be written to the tag, click the Specify check box and type the values. 7. Click Apply. Configuring OLE verb animation With OLE (Object Linking and Embedding) verb animation, you can set up OLE objects to perform certain actions. When the expression evaluates to true—that is, when the expression does not equal zero— the specified OLE verb is activated. The verbs available depend on the OLE object. Typical verbs include open, edit, and run.
4. In the OLE Verb field, click the down arrow to display the OLE verbs available for the selected OLE object. Click a verb in the list. 5. Click a security code. To restrict access to this object, assign the appropriate security code. For example, you might want to restrict access so only a senior operator can edit an embedded spreadsheet. For more information about security, see Chapter 10, Adding security. 6. Click Apply.
The object’s properties versus RSView32 animation Each ActiveX object has a set of properties. To view the object’s properties, right–click the object, then click ActiveX Property Panel on the context menu. The content of the property panel is determined by the application that created the object, not by RSView32. To link the ActiveX object to RSView32, you must attach ActiveX control to the object. IMPORTANT The runtime behavior of ActiveX objects depends on the vendor’s implementation.
2. Configure the control for properties and events as described on the following pages. Naming an ActiveX object All objects have a default name. You can change the default name of all objects, including ActiveX objects. The object’s name is used when logging events for that object. The object’s name is also used for the Invoke command—to use the Invoke command to call a method, you must specify the name of the object in which the method is implemented.
To name an object: 1. Select the ActiveX object. 2. Click the right mouse button to open the context menu and then click Object Name/Tooltip. 3. Type a name for the object, or accept the default name. Each object in a graphic display must have a unique name. Object names are case sensitive. The first character of the name must be a letter, but subsequent characters can use numbers or the underscore character (_). 4. Click OK. To name an object using the ActiveX Property Panel: 1.
knob changes position accordingly. Likewise, when the slider’s knob changes position (for example, by being dragged with the mouse) the slider’s value is written to Tag1. Not Bindable—When the tag value changes, the property value changes. However, the reverse is not true. For example, if the slider object described above has a property Value that is Not Bindable, Tag1’s value will not change when the slider’s knob is changed but the slider’s knob will change when Tag1’s value changes.
The middle column indicates whether the property updates the tag or the tag updates the property: A left arrow indicates the tag updates the property A right arrow indicates the property updates the tag A double arrow indicates the tag and property update each other 3. Click in the Tag column to specify the tag to use for the property. Type the tag name or click the ... button to open the Tag Browser and select a tag.
To attach RSView32 commands or macros: 1. Select the ActiveX object. 2. Click the right mouse button to open the context menu, point to Animation, point to ActiveX Control and then click Events. 3. Select the event you want to attach the command or macro to. 4. Type the command or macro name, or click the ... button to open the Command Wizard, and then click a command or macro. Separate multiple commands or macros with a semi–colon (;) or place them on separate lines.
For more information about the object and its methods, click this button. To view an object’s method description: 1. Select the ActiveX object. 2. Right–click to open the context menu, point to Animation, ActiveX Control, and then click Methods. 3. Select the method you want to view the description for. Using the Invoke command to call an ActiveX method To call an ActiveX method, the object must have a name. You then use the RSView32 Invoke command to call the method for the named object.
With the Invoke command you can: call an object’s method assign the value returned by a method to a tag set an object’s property to a tag value or a constant set a tag to the value of an object property To call a method on an object: On the command line or anywhere else that accepts a command, type the following command: Invoke file.object.method(parameter1, parameter2, . . .) file The name of the graphic display that contains the ActiveX object. me can be used instead of file.
Associating objects and displays with keys You can associate RSView32 commands with graphic objects in a display and with the display itself using object keys and display keys. A key is either a key on a keyboard or keypad, or a button on a touch screen that is connected to the computer or monitor an operator uses to interact with your RSView32 project at runtime. Operators can use these keys to perform actions such as moving between screens, setting tag values, and so on.4.
Example: Using object keys Imagine you have a display showing a tank with two valves. The two valves control the flow in and out of the tank. Both valves have been configured with object key animation as follows: Valve 1 F2 = Open F3 = Close Valve 2 F2 = Open F3 = Close At runtime, operators can select either valve, press F2 to open it and press F3 to close it. To create an object key: 1. Select an object. 2. On the Animation menu, click Object Keys. 3. Click Add.
4. Specify a key. If desired, select one or both modifiers. Some keys are normally reserved for use by Windows and RSView32. For details about assigning reserved keys as object, display, or global keys, see “Reserved keys” on page 15-17. 5. Click OK. The key you added is displayed in the Key field. If you specified a modifier, the first letter of that modifier is also displayed. If you create a label, in the next step it is also listed in this field.
The repeat action repeats at the rate specified in the Keyboard properties of the Windows Control Panel. 9. 10. If, at runtime, you want a highlight box to appear around the object when it has input focus, select the Highlight check box. For details, see “Specifying the behavior of interactive objects” on page 11-24. Click OK. For details about the Index field, see “Using index numbers” on page 12-45. For details about the Current [Tag] field, see “Using the Current [Tag] parameter” on page 12-48.
specify which tag value goes into which numeric or string input field in a recipe file. For details about recipe files, see “Creating a recipe file” on page 11-62. Checking an object’s index number To check an object’s index number, double–click the object and check the number in the Index field. The selected object has index number 1. Changing index numbers Once you have created two or more objects with index numbers, you can change the index numbers.
number 1. However, you cannot change input field 4 to index number 5, because you have not created five input fields. When you change an index number, other numbers are adjusted so two objects do not have the same number and there are no gaps in the numbering. To change an index number: 1.
To move through a tab sequence: press Tab to move through the objects from lowest index number (1) to highest index number. press Shift–Tab to move through the objects from highest index number to lowest index number (1). Example: Creating a selection order In the display below, pressing the Tab key moves users through the objects in a left to right pattern. The valves are objects with object key animation. The boxes are numeric input fields. The buttons are button objects.
For example, if you want F2 to set the value of a selected object’s tag to 0, you would set up a display key for F2, using the [tag] parameter, and then set up object keys for each object on the screen, specifying which tag to use for each object. Summary of steps 1. Create a graphic object. 2. In the Display Keys dialog box, associate a key with an RSView32 command. Use the [tag] placeholder as the command’s parameter.
Examples For ways to use the [tag] parameter, see these examples: Example 1: Creating display–wide keys to open and close valves Imagine you have a graphic display containing 20 valves and you want operators to be able to open and close all the valves with the same two keys. Instead of specifying the tag name for each valve, use the [tag] parameter with display keys. 12–50 1. In the Display Keys dialog box, assign two display keys. For the press action, type Set [tag]. 2.
Type tag name here. . the Type the name of the help file here. Valve1 At runtime, the operator can select any valve object, and press F2 to open the valve and F3 to close it. Example 2: Opening object–specific Help Imagine you have a graphic display containing various graphic objects that represent plant–floor equipment. If something goes wrong with a piece of equipment, you want operators to be able to select the appropriate object and display a Help file that suggests steps for correcting the situation.
1. In the Display Keys dialog box, assign a display key. In the Press Action field, type Help [tag]. 2. In the Object Keys dialog box, type the appropriate help file name in the Current [Tag] field for each equipment object. Type the name of the help file here. At runtime, when an operator selects any equipment object and presses F4, the help file for that piece of equipment is displayed.
Example 3: Opening an object–specific alarm summary Imagine you want to have alarm information available for a specific machine. If something goes wrong and causes an alarm, you want the operator to be able to display an alarm summary for that machine. 1. Create an alarm summary that uses a filter to display only the alarms for the machine. For more information about creating an alarm summary, see page 6-54. 2. In the Display Keys dialog box, assign a display key.
Type the name of the alarm summary object. At runtime, when the operator selects an equipment object and presses F5, the alarm summary for that piece of equipment appears. Creating display keys Display keys associate graphic displays with keys. Using the keys, operators can interact with the graphic displays at runtime. Example: Using a display key Suppose you want the Home key to display a main menu display.
If the Main Menu display is of the Overlay display type, you must use the Abort command to close the active display. For details about how keys and other interactive objects work at runtime, see “Specifying the behavior of interactive objects” on page 11-24. To create a display key: 1. On the Animation menu, click Display Keys. 2. Click Add. 3. Specify a key and, if desired, select one or both modifiers.
Some keys are reserved for use by Windows and RSView32. Reserved keys do not appear in the Key field in the Add Key dialog box. 4. Click OK. The key you added is displayed in the Key field. If you specified a modifier, the first letter of that modifier is also displayed. If you create a label in the next step, it is also listed in this field. The information in the Key field is used in the key list, which appears at runtime so operators know which keys are associated with an object and a display.
Modifying a key 1. On the Animation menu do one of the following: to modify object keys (you must have an object or group of objects selected first), click Object Keys to modify display keys, click Display Keys 2. In the Key field, select the key you want to modify. 3. Click the Modify button. 4. Make the necessary changes, and then click OK. Removing a key 1.
Viewing the key list at runtime At runtime, users can use the key list to see which keys are associated with an object and display, and to see what actions the keys will perform. 3. Key Modifiers Label Key Modifiers Label The key list displays the keys listed in the Key fields of the Object Keys and Display Keys dialog boxes. All object keys are displayed and then all display keys.
Applying animation to groups You can apply animation to objects and then group those objects and apply animation to the group. When the display is running, animation is evaluated from the inside out. To apply animation to objects within groups, use the group edit feature. For details, see page 11-94.
To view the animation on an object using the menu: 1. Select an object. 2. View the animation by doing one of the following: on the menu bar, click Animation and see which items have a check mark place the cursor over the object and press the right mouse button to display the context menu. Then click Animation from this menu and see which items have a check mark. The object has visibility animation. To view the animation on an object using the Animation dialog box: 1. Select an object. 2.
Using Peek Use Peek to view the animation attached to a graphic object or group of objects. In the Peek Settings dialog box, you specify what type of animation you want to check. When Peek is turned on, any objects with the type of animation you have specified are surrounded by a red box.
You can click as many types of animation as you want. However, Peek does not show the specific type of animation an object has. For example, if you choose color and visibility animation, all objects with these types of animation will be highlighted, but you will not know which objects have which types of animation. 3. If you want Peek to be active when you close the dialog box, click Activate Peek. Otherwise, specify the settings and save them.
Changing the animation on objects You can change the animation attached to a group of objects or to individual objects within the group. To access objects within a group, use the group edit feature. For details, see page 11-94. To change the animation on objects: 1. Select the object. 2. Open the Animation dialog box. 3. Make the required changes. 4. Click Apply. Copying or duplicating objects with animation You can copy or duplicate objects that have animation attached to them.
To copy objects with animation: 1. Select the objects. 2. Do one of the following: use the copy and paste commands on the Edit menu or toolbar, or use Ctrl–C to copy and Ctrl–V to paste in the same display, drag the object and then press Ctrl and drop the object between displays, drag and drop objects To duplicate objects with animation: 1. Select the objects. 2. On the Edit menu, click Duplicate.
13 Chapter Configuring trends This chapter describes trends, and outlines how to: create and configure a trend object layer trends to compare real-time and historical tag values use objects from the Trends graphic library provide buttons and sliders for controlling a trend at runtime About trends A trend is a visual representation of real-time or historical tag values. The trend provides operators with a way of tracking plant activity as it is happening.
Trend object Key concepts Trend object A trend object is created in the Graphic Display editor. It can be created and edited like any other advanced object. Trend dialog box The Trend dialog box contains two tabs for configuring the appearance and content of the trend: Trend Configuration and Pen Configuration. By filling in the fields under these tabs, you specify what kind of data the trend will plot and how the data will look.
Data source The data displayed in a trend can come from two sources. For realtime trends, data comes from the value table as it is collected. For historical trends, data comes from a data log model’s set of files. Historical trends can also be set up to display data from a single log file at a time. This is called file–based trending, and is useful if you want to display data from a particular shift or batch process.
Shading Use shading to show relationships between tags and to compare tag values to constants. The figure below calls attention to tag values in alarm. The difference between the tag’s value and the alarm’s level is shaded. Shading between pen values Legend Legend Include a legend at the bottom of the trend to identify the data that is being drawn by each pen. You can include some or all of the pens in the legend, and can label each pen.
Summary of steps These are the steps for creating a trend: create a trend object in the Graphic Display editor configure the trend in the Trend dialog box provide a method for controlling the trend Creating a trend object To create a trend object: 1. Open the Graphic Display editor. 2. Choose the Trend drawing tool by doing one of the following: open the Objects menu, click Advanced Objects, and then click Trend click in the Drawing Tools toolbox The cursor changes to the trend drawing tool: 3.
For detailed information about graphic objects, see Chapter 11, Creating graphic displays. Instead of creating a trend from scratch, you can use the trend in the Trends graphic library. For more information, see “Using the Trends graphic library” on page 13-35. Working in the Trend dialog box When you release the mouse button after drawing a trend object, the Trend dialog box appears. Click this tab to specify the appearance of the time and vertical axes and other features of the trend's appearance.
Trend configuration To configure the time axis, vertical axis, and other aspects of the trend’s appearance: 5. 1. In the Trend dialog box, click the Trend Configuration tab. 2. Fill in the fields. See the topics on the following pages for information about the fields. 3. Click OK.
To configure the time axis, fill in the following fields as outlined below. Start time for a real-time trend For a real-time trend, NEWEST is shown. Data will start plotting as soon as the trend starts, with the newest data available. You cannot modify the start time for a real-time trend. Start time for a historical trend Start times for historical data can be relative or absolute. With relative time, plotting always starts relative to the newest or oldest data in the log model or log file.
Example: Relative Time To display data starting 90 minutes from the oldest data in the log model, type: To specify absolute time: Absolute time is specified by the month, day, year, hour, minute, and second. For an absolute start time, type: MMM DD YYYY hh:mm:ss where: MMM is month DD is day YYYY is year hh:mm:ss is hours, minutes, seconds Time Range The time range determines the time span on the time axis.
Examples: Start Time and Time Range To plot real-time data in a 60–second window, specify: To display one day of data starting on Jan 19, 1998 at 1:30 pm, type: Divisions Specify the number of major and minor divisions you want marked on the time axis. Keep the number of divisions small so they will be visible. Scale Check this box to have a time scale appear at the bottom of the trend.
Panel. For more information about this option, see“Specifying time, date, and number formats” on page 18-12, or see your Windows documentation. Scroll Axis Check this box to have the grid for the time axis scroll across the trend. When this box is not checked, the grid for the time axis is fixed. Time Check this box to show the time in the scale. Time is displayed in the following format: HH:MM:SS (hour, minute, second).
Configuring the vertical axis The following illustration shows the components of the vertical axis: Minor division Vertical axis scale Major division To configure the vertical axis, fill in the fields as outlined below: Divisions Specify the number of major and minor divisions you want marked on the vertical axis. Keep the number of divisions small so they will be visible. Scale Check this box to display a scale with the range of values for a pen.
Digits Select the number of characters you want to display in the pen scale, including the decimal point. The values that appear in the scale are selected in the Pen Configuration tab. Specify enough digits so the scale is wide enough to display the minimum and maximum values for all your tags. If the pen value does not fit it appears in scientific notation. To display the division markings on the vertical axis without numbers, select 0.
For a local historical trend: To display historical data from a data log model in the project you are running, click Historical, then click Local and specify a data log model in the Model field. For a remote historical trend: To display historical data from a different project (from another location on the same computer or from another computer), click Historical, then click Remote. In the Model field, type the complete path to the logged data (to the .dlg file), or click ... and select a .dlg file.
remote data, type the complete path to the logged data (to the .dlg file), or click ... and select a .dlg file. Click Choose File to select the data file that will be used. For local data, specify a data log model in the Model field. For remote data, type the complete path to the logged data (to the .dlg file), or click ... and select a .dlg file. In the File field, select a data log file. For detailed information about how data log files are named, see Chapter 7, Configuring data logging.
For historical data, the rate determines how often the log file is checked for new data. Do not specify a rate faster than the rate at which the data is logged to the file. For example, if you set up periodic logging with a 20–second interval, do not specify a rate less than 20 seconds, because no new data will be available. Control Tag Type a name for the folder that will contain the trend control tags. Control tags are used to control the view of the trend at runtime.
The following illustration shows a trend with a legend: Pen value Legend Pen label Configuring trends 13–17
Pen configuration To configure the pens that will plot the data for the trend: 1. In the Trend dialog box, click the Pen Configuration tab. 2. Select a pen. For each pen you select, fill in the fields in this tab. The fields are described below. To begin configuring pens, select a pen here. When you select another pen, the configuration for the previous pen is saved. To move to another pen, select it in the Pen Selection field.
from 1 to 500. For details about placeholders, see “Using tag placeholders” on page 11-37. a value When you specify a value, the pen draws a constant horizontal line on the trend. Use horizontal lines to provide a frame of reference for your tags. For example, if you define values that are the limits within which a tag should operate, when a tag crosses one of these limits the tag’s alarm condition is obvious on the trend.
Line Interpolation Line interpolation determines how a line is drawn. The choices are: This item Does this Automatic Draws the appropriate type of line based on the tag type. For example, for a digital tag, digital interpolation is automatically used. For an analog tag, linear interpolation is automatically used. Linear Draws a straight line between two points, which suggests a gradual change from the first point to the second point.
Configuring pen scale The pen scale defines the range of numbers on the vertical axis. The vertical axis changes to reflect the minimum and maximum values for the selected pen’s tag. For example, if Tag1 has a minimum value of 10 and a maximum value of 100, the range on the vertical axis will be 10 to 100 when the Tag1 pen is selected. If Tag2 has a minimum of -10 and a maximum of 50, the range on the vertical axis will change to -10 to 50 when the Tag2 pen is selected.
Configuring shading Use shading to compare the values of different pens. To have shading, at least two pens must be defined. For the upper and lower boundaries, select the pens with which to compare values. When the pen you are defining plots above the value of an upper boundary pen, or below the value of a lower boundary pen, the area between the pen you are defining and the boundary pen will be shaded. The shading color will be the color you select under Style.
Example: Shading with three pens The upper pen, Pen 2, has a constant value of 75 and the lower pen, Pen 3, has a constant value of 25. Pen 1 represents the tag called VIN_LEVEL. The trend will be shaded whenever Pen 1 goes above Pen 2 or below Pen 3.
Example: Shading with two pens Whenever Pen 1 goes above Pen 2, the trend will be shaded like this: Pen 1 Color 1 Pen 2 42603 To produce the shading shown above, the following settings were used: Pen Tag Name Shading Upper Bound 13–24 Pen 1 VIN_LEVEL Pen 2 OIL_LEVEL RSView32 User’s Guide Pen 2 Lower Bound
Example: Shading between two pens Whenever Pen 1 goes above or below Pen 2, the trend will be shaded like this: Pen 1 Color 1 Pen 2 40065 To produce the shading shown above, the following settings were used: Pen Tag Name Pen 1 VIN_LEVEL Pen 2 OIL_LEVEL Shading Upper Bound Lower Bound Pen 2 Pen 2 Creating a legend To include a pen in the legend, leave the box checked. To label the pen, type a label such as a tag name or description.
Ensuring real-time trends have data Real-time trends collect data only while the trend is displayed. This means that a trend will not contain any data when it starts. To ensure a trend contains data once it has started, keep the trend updating in the background by loading it into the display cache. Example: Ensuring a real-time trend has data 1.
Comparing real-time and historical data You can layer trends, which is useful for comparing real-time and historical data in order to see process changes. To layer trends: 1. Create two or more trends of the same size. 2. Configure the trends. 3. Select the trend that will be on top. On the Attributes menu, click Hollow. 4. Move the trend that will be on top over the other trend. 5. With the trend still selected, click Bring to Front on the Arrange menu.
To create control tags, you have to type a name in the Control Tag field in the Trend dialog box. When you do, a folder with that name, containing the trend control tags, is created in the tag database. IMPORTANT If at runtime you display multiple trends that use the same control tags, changes to one trend affect all the other trends that use the tags, including trends that are loaded in the cache and are not visible. If you copy a trend, the new trend uses the same Control Tag folder name.
Tag name Function Read or Write? \Paused A tag value of 1 pauses the trend. Read and write A tag value of 0 resumes movement of the trend. For real-time trends, RSView32 reads the value of this tag when the trend is first displayed to determine whether to start the trend in paused or resumed mode. If this tag doesn’t exist, the trend is started in resumed mode.
Tag name Function Read or Write? \YMag Magnification of the vertical axis in percent. Read and write 0No magnification 100Twice the resolution (half the range) -100Half the resolution (twice the range) \YOffset Offset of the vertical axis in percent. Moves the view up or down but does not change the time range. Read and write How the trend control tags work When a trend is running, the data for a trend—either real-time or historical—is stored in a buffer. The trend is a view of this buffer.
The values for the trend control tags initially come from the information configured in the Trend dialog box. As the trend runs, some values are updated, such as the times of the newest and oldest data. The time of the oldest data changes when the trend’s buffer becomes full and the oldest data is discarded. The time of the newest data changes when new data is available for the trend.
To Use this expression Move two views to the right StartTime = StartTime + 2 TimeRange Pause the trend Paused = 1 Resume the trend Paused = 0 Specify the newest data log file as the current file* CurrentFile = Current File + NewestFile Move from the current file to one file earlier* CurrentFile = CurrentFile – 1 Move from the current file to one file later* CurrentFile = CurrentFile + 1 Specify the oldest data log file as the current file* CurrentFile = CurrentFile – OldestFile * Expressio
You cannot use binary numbers to set a value—you must use decimals.
To show Pen 10 again, use the bitwise OR operator and the pen’s decimal value: PenMask = PenMask | 512 Specifying a start time To specify an absolute trend start time, use the \StartTimeDate control tag. The \StartTimeDate control tag overrides the time specified in the Start Time field of the Trend dialog box. Create a string input object so that the operator can enter the date and time of the start time. 6.
Example: Specifying a start time one hour before the current time Display “Process Trend” Trend\StartTime=system\DateAndTimeInteger - 3600 When these commands run, RSView32 displays the trend graphic called Process Trend and sets the start time for the trend to the current time minus 3600 seconds (1 hour). You can specify the start time from a graphic object or from a macro. For example, create a button object and use the above commands as the press action for the button.
3. Double-click Trends. 4. Drag and drop one or more trend objects into your display. Setting the name of the Control Tag folder You can use the Control Tag folder name (“trend”) that has already been configured for the trend objects in the Trends graphic library, or you can change the name of the folder and then apply the new name to all objects associated with this trend. To change the trend’s Control Tag folder name and replace the old folder name: 1.
7. Click Replace. If the Confirm Replacements check box is not selected, all occurrences of the old folder name are automatically replaced with the new name. If the Confirm Replacements check box is selected, the name that is about to be replaced is displayed along with its usage. Choosing fonts, colors, and lines The following table summarizes where to choose fonts, colors, and lines for a trend. Before doing any of the actions described below, select the trend.
To choose Do this Pen line color In the Trend dialog box, choose the Pen Configuration tab, and then choose a color in the Color field. You must configure each pen separately. This color is also used for the vertical axis labels and for the pen values in the legend. Pen line width Choose Line Properties from the Attributes menu and then specify a width. If you use this method the width applies to all the pens in the trend.
To choose Do this Marker color Choose Font from the Attributes menu and then choose a color. For information about the marker see page 13-41. The marker color is also used for time axis labels (if used) and for the time and date in the legend. Text font family, size, and color Choose Font from the Attributes menu and then choose a font, size, and color. The font and size are used for all the text used for axis labels and all the text in the legend.
... the scale shows the minimum and maximum range for the pen. When you click this pen... Selecting points To view details about a specific point in the trend, use the marker. When the marker is over a point in the data, the pen’s date, time, and value at the marker’s location are displayed in the legend. Marker The marker is not over a point in the data for the Hopper1 Level pen, so “No Value” appears in the legend.
By default, the marker is at the right–most edge of the trend (and might not be visible). To move the marker, position the cursor on the trend and then click. The marker moves to the point you clicked. To hide the marker, click the vertical axis. Changing the marker’s color By default, the marker is black (which means it is not visible on a trend with a black background).
Editing the trend configuration 1. Open the Trend dialog box by doing one of the following: double–click the trend select the trend, place the cursor over it, right–click to display the context menu, and then click Edit Trend select the trend object, click Edit on the menu bar, and then click Edit Trend 2. Edit the information in any of the fields. For detailed information about the fields, see “Trend configuration” on page 13-7 and “Pen configuration” on page 13-18. 3. 13–42 Click OK.
14 Chapter Creating expressions This chapter includes: instructions for creating expressions description of the components used for building expressions About expressions Sometimes the data you gather from devices is only meaningful when you: compare it to other values combine it with other values create a cause–effect relationship with other values Expressions allow you to create mathematical or logical combinations of data that return more meaningful values.
Where you can use expressions Expressions can be used in the following editors: Graphic Display: You can define an expression to control various aspects of a graphic object’s appearance. You can also display the value of an expression in numeric and string display objects. Derived Tags: You can define an expression and specify the name of a tag that will store the result of the expression. Events: You can define an expression and associate it with an action.
Creating expressions All editors that use expressions include an Expression field. In some editors, you will also find: expression buttons an expression column The following illustration shows the items for creating an expression in the Events editor.
Expression buttons These are the expression buttons: This button Displays a list of This button Displays a list of If–then–else operators Bitwise operators Logical operators Built–in functions Relational operators Tags in the tag database Arithmetic operators Cutting, copying, and pasting expressions You can cut, copy, or paste an expression or parts of an expression. The method for performing these actions depends on whether the expression is in a window or in a dialog box.
To cut or copy expressions in a window: 1. Select the expression in the form or in the spreadsheet. 2. Do one of the following: click Cut or Copy on the Edit menu Cut click the Cut or Copy button on the toolbar Copy press Ctrl–X or Ctrl–C To paste expressions in a window: 1. Click where you want to paste the expression. You can paste into the Expression field in the form or into the Expression column in the spreadsheet. 2.
Formatting expressions You can format expressions so they are easier to read. However, do not let tag names, key words, function names, or function arguments span more than one line. When formatting expressions, you can use tabs, line returns, and multiple spaces. When you’re working in the Animation dialog box in the Graphic Display editor, type Ctrl-Tab to insert a tab in the expression.
A value or string, a tag name, or a more complex expression. Enclose tag names that contain dashes or start with a number in braces { } when you use them in an expression. This distinguishes the characters in the tag name from the characters in the expression. Also use braces when using wildcards (* or ?) to represent multiple tags in an expression. Enclose strings in quotes. The string can contain any character, and can include spaces. Do not use braces for the tag name before the equal sign.
Tank1\Message = “Tank1 Overflow” Sets the tag Tank1\Message to Tank1 Overflow. Using tag names and tag placeholders A tag name can be included as part of an expression or can stand alone as the entire expression. To supply a tag name, do one of the following: type a tag name You can type a tag name that does not exist in the tag database. When you click OK, a dialog box appears prompting you to create the tag.
Using tag placeholders instead of tag names The Graphic Display editor accepts tag placeholders instead of tag names. Placeholders allow you to use the same display with a variety of tags. You can use tag placeholders in the same way you use tag names. A tag placeholder is the cross–hatch character (#) followed by a number from 1 to 500. For detailed information about placeholders, see Chapter 11, Creating graphic displays.
Arithmetic operators Arithmetic operators calculate values based on two or more numeric values. The arithmetic operators are: Symbol Operator Example (For these examples, tag1 = 5 and tag2 = 7) + addition tag1 + tag2 returns a value of 12 - subtraction tag1 - tag2 returns a value of –2 * multiplication tag1 * tag2 returns a value of 35 / division tag1 / tag2 returns a value of 0.
Relational operators Relational operators compare two numeric or string values to provide a true or false result. If the statement is true, a value of 1 is returned. If false, 0 is returned.
Logical operators Logical operators determine the validity of one or more statements. There are three logical operators: AND, OR, and NOT. The operators return a non–zero value if the expression is true, or a zero if the expression is false. The logical operators are: Symbols Operator Action Example (For these examples, tag1 = 5 and tag2 = 7) AND, && and Returns a 1 if the statements to the right and to the left of the operator are both true.
Symbol Operator Action & AND Compares two integers or integer tags on a bit–by–bit basis. Returns an integer with a bit set to 1 if both the corresponding bits in the original numbers are 1. Otherwise, the resulting bit is 0. | inclusive OR Compares two integers or tags on a bit–by–bit basis. Returns an integer with a bit set to 1 if either or both of the corresponding bits in the original numbers are 1. If both bits are 0, the resulting bit is 0.
Example: Bitwise operators For these examples tag1 = 5 (binary 0000 0000 0000 0101), tag2 = 2 (binary 0000 0000 0000 0010) tag1 & tag2 Returns 0 (binary 0000 0000 0000 0000). tag1 | tag2 Returns 7 (binary 0000 0000 0000 0111). tag1 ^ tag2 Returns 7 (binary 0000 0000 0000 0111). tag1 >> 1 Returns 2 (binary 0000 0000 0000 0010). tag1 << 1 Returns 10 (binary 0000 0000 0000 1010). ~ tag1 Returns -6 (binary 1111 1111 1111 1010).
Many functions check for specific true and false conditions. They return 1 if the condition is true, and 0 if the condition is false. Tag functions The following built–in functions examine the status of a tag (tag) or multiple tags (tag*). This function Returns ALM_IN_ALARM(tag) or ALM_IN_ALARM(tag*) 1 (true) if the tag or alarm event is in alarm. ALM_ACK(tag) or ALM_ACK(tag*) 1 (true) if the tag or alarm event’s alarm has been acknowledged.
This function Returns ALM_FAULT(tag) or ALM_FAULT(tag*) 1 (true) if there has been an alarm fault for the specified tag. COMM_ERR(tag) 1 (true) if the last read or write operation for the specified tag indicated a communication failure. If examining multiple tags, 1 (true) if there has been an alarm fault for one or more of the tags. Note that you can examine the status of only one tag with this function. To examine multiple tags at once, use a wildcard in the expression argument.
This function Returns BEFORE_TIME(“time”) 1 (true) if the expression is evaluated before the specified time. AFTER_TIME(“time”) 1 (true) if the expression is evaluated after the specified time. INTERVAL(“interval”) 1 (true) if the specified time interval has elapsed—the interval timer starts running when an event file starts running. GetDayofWeek(D) Return value is from 1 to 7. 1 indicates Sunday and 7 indicates Saturday. The other values correspondingly represent each day of week.
Example: Specific time parameters The following all represent the same date and time, and are valid time parameters: “mon aug 18 1997 17:00” “mon aug 18 1997 17: :00” “:00 aug 18 mon 1997 17:” IMPORTANT The validity of the date is not checked. In the above example if Aug 18 1997 is not a Monday, this error is not detected. Example: Less specific time parameters Following are valid examples of time parameters: “17:00” Means any day at 5:00 pm. “ :30 ” Means any hour, on the half hour.
The interval parameter has this format: where is one of: mil (millisecond) sec (second) min (minute) hou (hour) day (day) wee (week) mon (month) yea (year) Examples: Time and interval functions TIME(“sun aug 18 1997 14:30”) Returns 1 (true) if it is exactly 2:30 pm and 0 seconds, on Sunday, Aug 18, 1997; otherwise returns 0 (false).
_____________________________ INTERVAL(“1 min”) Returns 1 (true) if a minute has elapsed since the expression last returned a 1. _____________________________ (tag1 > 500) and INTERVAL (“30 sec”) Returns 1 (true) when tag1 > 500 on some 30–second interval since the event file started running. (It does not mean 30 seconds after tag1 > 500.) File functions The following built–in functions check if a file exists and check the amount of free disk space.
This function Returns this value Example FREE_BYTES(drive) The number of bytes free on the specified drive. FREE_BYTES(c) returns the number of bytes available on drive C, up to a maximum of 2.1 GB. Use this function to display a message or trigger an alarm when disk space is getting low. If you want an expression containing these functions to be evaluated more than once, assign the expression to an event rather than to an object in a graphic display.
ARCCOSD (expression) The arc cosine of the expression in degrees ARCTAND (expression) The arc tangent of the expression in degrees Security function The following built–in function checks if the current user has the specified security code. The security parameter is the security code letter, from A to P.
Operators are evaluated in the following order: Evaluation order Symbols 1 (highest) () 2 NOT ~ 3 * / MOD, % ** AND, && & >> << 4 + OR, || | ^ 5 (lowest) EQ, = NE, <> LT, < GT, > LE, <= GE, >= Example: Evaluation order For these examples, tag1 = 5, tag2 = 7, and tag3 =10.
1. tag1 > tag2 = 0 2. tag 1 < tag3 = 1 3. 0 AND 1 = 0 The expression evaluates to 0 (false). _____________________________ tag1>tag2 AND tag3 is evaluated in this sequence: 1. tag2 AND tag3 = 1 2. tag1 > 1 = 1 The expression evaluates to 1 (true). _____________________________ NOT tag1 AND tag2 > tag3 ** 2 is evaluated in this sequence: 1. NOT tag1 = 0 2. 0 AND tag2 = 0 3. tag3 ** 2 = 100 4. 0 > 100 = 0 The expression evaluates to 0 (false).
else statements enable the expression to perform different actions in different situations and to repeat activities until a condition changes. To build conditional expressions, use the relational operators and the logical operators. The if–then–else structure is: if statement then value1 else value2 If the statement is true then the expression returns value1; if the statement is false then the expression returns value2.
Example 1: Nested if–then–else This expression: if (statement1) then (value1) else if (statement2) then (value2) else (value3) has this interpretation: enter statement1 true false statement2 true false value3 exit 14–26 RSView32 User’s Guide value2 value1
Example 2: Nested if–then–else This expression: if (statement1) then if (statement2) then (value1) else (value2) else (value3) has this interpretation: enter statement1 value3 exit statement1 false value3 true statement2 true value1 1 false value 2 2 exit Creating expressions 14–27
15 Chapter Setting up navigation An important part of the complete operator interface is the way operators navigate through and interact with your project. RSView32™ gives you the tools for linking displays and creating an overall project structure that is easy for operators to use.
The following illustration shows a display hierarchy.
Commands for moving among displays To open, close, and switch between displays, use these commands:1. RSView32 Command Function Display Opens the specified graphic display. If a display is already open and the display allows multiple running copies (specified in the Display Settings dialog box in the Graphic Display editor), this command will open another display and make it active. If the display is already open but does not allow multiple running copies, this command simply makes the display active.
The PullForward and PushBack commands provide quick display changes because displays are already up and running. However, be aware that the more displays that are open, the more memory is used. The display type you choose gives you additional control over how the operator navigates between displays. For example, use the On Top option to keep a display on top at all times, even when another display has focus. Or use the Replace option if you want a display to replace all other open displays when it opens.
Example of navigation methods Following are examples of various navigation methods: Example: Keyboard operation The following graphic display has been designed to act as a menu, listing keys users can press to open different displays. To create this display, the designer assigned various RSView32 commands to keys using the three types of key definitions: object, display, and global. In all cases, keys (not mouse buttons) were defined to run commands.
Example: Mouse/touch screen operation The following graphic display contains buttons that users can click with the mouse or press on a touch screen to call up detail displays. This display presents information and acts as a menu. The Line 1, Line 2, and Line 3 buttons have touch animation attached to them. To create the buttons, the designer used the Button drawing tool in the Graphic Display editor. The buttons can be selected with a mouse or with a touch screen.
The tools To build a complete operator interface, use: macros to replace a set of commands with a single command symbols to replace long commands or commands with parameters key definitions to assign commands, symbols, macros, or a series of replacement keystrokes to keys or mouse buttons Precedence At runtime, components are evaluated in the following order: symbols, commands, macros object keys, display keys, global keys For details about the order of precedence among object, display, and global keys, se
Instead of using macros to set tag values, you can also set tag values using the tag collections in the RSView32 Object Model’s WritePendingValues method. For more information about using the RSView32 Object Model, see Help. To create a macro: 1. In the Project Manager, open the Logic and Control folder. 2. Open the Macro editor by doing one of the following: double–click the Macro icon right–click the Macro icon and then click New 3. Type your macro commands and, if required, add command parameters.
more information about using the Command Wizard, see page A-5. 4. On the File menu, click Save As. 5. Type a file name. Remember, the file name is the macro name so ensure the name does not conflict with symbols or commands. If names conflict, only the symbol or command will run. At runtime, operators can type the macro name anywhere they can type an RSView32 command. For example, if you include a command line in your project, operators can run a macro by typing its name on the command line.
Screen1 appears, then the graphic display Screen2 appears, then the tag Valve23 is set to its open state. Note that you don’t need to put braces around tag names when using placeholders in commands. Using parameters Macros can accept parameters. To specify a parameter in a macro, type a percent (%) sign followed by a number. Up to nine parameters are allowed. B To run the macro and parameters, specify the macro name followed by the parameters. Separate multiple parameters with spaces.
Example: Nesting macros A macro called Draw contains: Display Overview Display Detail and a macro called Factory contains: Draw Valve23 = Open Typing Factory performs the same actions as the original Factory macro in the previous example. Creating a macro that starts when a project starts If you have created a project with components that must start in a particular order, create a startup macro. You can then configure the Startup editor to run this macro when your project starts.
You can define symbols in a macro or on the command line. However, symbols are mainly an operational convenience when using the system from the command line. To define a symbol: On the command line or in a macro, type: Define the abbreviated command, without spaces an existing command with or without parameters. It can contain spaces and other symbols.
To clear a symbol: On the command line or in a macro, type one of the following: This command Does this Undefine clears the symbol where is the name of the symbol you want to delete Undefine * clears all defined symbols Example: Undefining symbols Undefine Show Clears the symbol Show. Key definitions You can associate RSView32 commands with objects in a display and/ or with the entire display using object key animation, display key animation, and touch animation.
When deciding what type of key to create, use the following table as a guide: To Do this For details, see Associate a key with a specific graphic object (object key) Attach object key animation in the Graphic Display editor page 12-42 Associate a key with a specific graphic display (display key) Attach display key animation in the Graphic Display editor Page 12-54 Create a key that works everywhere (global key) Create a key definition file in the Global Keys editor Page 15-19 General rules about
Precedence and the F1 key When you are editing an RSView32 project, the F1 key always launches context–sensitive Help. At runtime, if a runtime editor has focus, F1 launches context– sensitive Help for that editor. If a graphic display has focus, and a press, release, or repeat action has been defined for the F1 key, F1 acts as a display, object, or global key instead of launching Help.
Precedence and embedded OLE objects The order of precedence for embedded OLE objects differs, depending on whether the OLE object is an RSView32 OLE object, for example, an embedded command line, alarm summary, or tag monitor object, or whether the object is a non–RSView32 OLE object, for example, an Excel worksheet.
Reserved keys The following keys and key combinations are normally reserved for use by Windows® and RSView32. This reserved key Does this + on the numeric keypad Displays the Recipe dialog box, or saves the recipe if Ctrl-W was pressed previously, or restores the recipe if Ctrl-R was pressed previously. Enter If Enter is pressed when a button has focus, the button’s press and release actions are executed. If Enter is pressed when an input field has focus, the field’s value is downloaded to the PLC.
This reserved key Does this Left Arrow, Right Arrow Moves the cursor one position left or right. Esc Closes the Object Key menu, or exits the input mode of a continuously– updating input field. Backspace Deletes the character to the left of the cursor. Del Deletes the character to the right of the cursor. Shift–End–Delete Deletes all characters from the cursor position to the end of the line. Home–Shift–End–Delete Deletes the contents of the input field.
If you use a reserved key or key combination as a global key, the key will perform both the actions of the global key you defined, as well as the action of the reserved key. Because the results can be unpredictable, defining global key actions for reserved keys is not recommended. Tips for using keys Keys with repeat actions are ideal for such tasks as ‘ramping’ a tag’s value. To define keys for running VBA programs or macros, define press actions and release actions only.
To create a global key: 1. In the Project Manager, open the Logic and Control folder. 2. Open the Global Keys editor by doing one of the following: double–click the Global Keys icon right–click the Global Keys icon and then click New 15–20 3. Click Add. 4. Specify a key and, if desired, click one or both modifiers.
Some keys are reserved for use by Windows and RSView32. Reserved keys do not appear in the Key field in the Add Key dialog box. 5. Click OK. The key you add is displayed in the Key field. If you specified a modifier, the first letter of that modifier is also displayed. If you create a label in the next step, it will also be listed in this field. As you continue to add keys, they will be listed here. 6. In the Label field, if you want, type a label for the key. 7.
Running global key files Use the RSView32 Key command to run global key files. Type this command in a macro or anywhere else you can use an RSView32 command. IMPORTANT You cannot run more than one global key file at a time. If you try to run more than one file, the files are not merged. Instead, the second file overrides the first file.
16 Chapter Sharing data with other Windows applications Methods for sharing data RSView32™ is based on standards that allow data to be accessed and shared among Windows® applications. With RSView32, you can: retrieve historical data using other Windows applications RSView32 stores all historical data in dBASE® IV (.dbf) format, so you can access data from log files using any software that supports this file format. With data logs, you also have the option of storing the data in ODBC-compliant databases.
This chapter describes how to set up RSView32 as a local server or client for OPC and DDE, and includes an example of setting up RSView32 as a DDE server that provides data to a Microsoft Excel worksheet. See Chapter 17, Using networks, for information about setting up RSView32 as a server or client on a network. use other Windows tools to manage tag databases RSView32 stores tag and alarm information in a format that is ODBC–compatible.
Retrieving historical data All logged data is stored in files in dBASE IV or ODBC table format, so you can retrieve data from log files using any software that reads these formats. (ODBC format is available for data logs only, not alarm or activity logs, unless you send the alarm log or activity log data to an ODBC database online.) Many software products are available for retrieving and analyzing data. This chapter briefly describes how to bring data from .dbf log files into Microsoft Excel.
Retrieving tag names from data log files For data log models, RSView32 often uses an index file or table for tag names. The file or table contains a list of all the tags used in the model, together with an index number for each tag. Other data log files or tables use the index number rather than the full tag name. This storage format Stores tag information in this file or table dBASE IV with short file names YYMMDDnt.dbf, where the t indicates this is the tag name file.
4. In the “Look in” field, choose a project directory and the subdirectory containing the log files.
This is a wide-format data log file. This format has multiple tag values per time stamp. Understanding the content of the log files Following is a description of the contents of the activity, alarm, and data log files. Unless otherwise indicated, the illustrations show log files that have been opened in Microsoft Excel.
Activity log files This column Contains Type The number of the activity type. The numbers are: 0 for error, 1 for warning, and 2 for information. 8. Id The number of the RSView32 component that sent the log message. This number is for RSView32 internal use only. Date The date the activity occurred. The date format is specified by the Regional Settings in the Windows Control Panel. Time The time the activity occurred.
Activity log—ODBC format ODBC format activity log data uses one table. The illustrations show ODBC tables that have been opened in Microsoft Query. For more information about how the log files are named, see “The ODBC storage format” on page 7-8. This column Contains SQL Data Type Length Type The number of activity type: 0 for error, 1 for warning, 2 for information.
This column Contains SQL Data Type Length UserStn For future use. SQL_VARCHAR or 15 SQL_CHAR LoggingStn The name of the computer on which the logging server is running. SQL_VARCHAR or SQL_CHAR 15 Alarm log files This column Contains Date The date the alarm was generated. Time The time the alarm was generated. Militime The number of milliseconds.
This column Contains TransType The type of alarm that was generated. The types are: InAlmIn Alarm (severities 1 through 8) OutAlmOut of Alarm AckedAcknowledged RmAckRemote Acknowledged InFltIn Fault OutFltOut of Fault SupOnSuppress On SupOfSuppress Off 16–10 TagName The name of the tag or alarm event that caused the alarm. TagValue The value of the tag at the time the alarm occurred. TagType The type of tag in alarm: A for analog, D for digital, S for string. ThreshVal The threshold value.
This column Contains UserStn For future use. LoggingStn The name of the computer on which the logging server is running. Alarm log files—ODBC format ODBC format alarm log data uses one table. The illustrations show ODBC tables that have been opened in Microsoft Query. For more information about how the log files are named, see “The ODBC storage format” on page 7-8. This column Contains SQL Data Type Length DateAndTime The time and date the alarm was generated.
This column Contains SQL Data Type Length TagType The type of the tag in alarm: A for analog, D for digital. SQL_VARCHAR or SQL_CHAR 1 ThreshVal The threshold value. SQL_DOUBLE or SQL_INTEGER or SQL_SMALLINT 8 or 4 or 2 ThreshNum The threshold number. SQL_SMALLINT or SQL_INTEGER 2 or 4 ThreshLabl The threshold label. SQL_VARCHAR or SQL_CHAR 20 Severity The alarm severity.
Data log files—narrow .dbf format Narrow .dbf format log files are created in sets of three. For more information about .dbf data log files, see “The .dbf file format” on page 7-3.9. Floating point and string data Log files for floating and string data are the same except one contains analog and digital tag data and the other contains string tag data. This column Contains Date The date the tag values were logged. Time The time the tag values were logged. TagIndex The index number for the tag.
This column Contains Marker B when the DataLogOn command was issued and logging began. E when the DataLogOff command was issued and logging ended. S when the DataLogSnapshot command was issued. Internal Information relevant to RSView32 only. Tag name This column Contains TagName The tag name. TTagIndex The index number assigned to the tag name.
Data log files—wide .dbf format Wide .dbf format data log files are created in sets of two. For more information about .dbf data log files, see “The .dbf file format” on page 7-3.10. Floating point and string data Tag name or index Status Tag values This column Contains Date The date the tag values were logged. Time The time the tag values were logged. Marker B when the DataLogOn command was issued and logging began. E when the DataLogOff command was issued and logging ended.
This column Contains Status D if a node is disabled. E if a communication error occurred while RSView32 was trying to acquire the tag value. S if the tag value is stale; that is, if the tag value was acquired but has not been updated. U if the tag is uninitialized. Blank if communications are working properly. Tag values The analog, digital, or string values for the tag. Tag name This column Contains Tagname The tag name. TTagIndex The index number assigned to the tag name.
Data log—ODBC format ODBC format log data uses up to three tables. The illustrations show ODBC tables that have been opened in Microsoft Query. For more information, see “The ODBC storage format” on page 7-8. Floating point and string data Log tables for floating and string data are the same except one contains analog and digital tag data and the other contains string tag data. This column Contains SQL Data Type Length DateAndTime The date and time the tag values were logged.
This column Contains SQL Data Type Length Status Blank if communications are working properly. SQL_VARCHAR or SQL_CHAR 1 SQL_VARCHAR or SQL_CHAR 1 D if a node is disabled. E if a communication error occurred while RSView32 was trying to acquire the tag value. S if the tag value is stale; that is, if the value has been acquired before but has not been updated. U if the tag is uninitialized. Marker B when the DataLogOn command was issued and logging began.
Tag name This column Contains SQL Data Type Length TagName The tag name. SQL_VARCHAR or SQL_CHAR 255 TagIndex The index number assigned to the tag name. SQL_SMALLINT or SQL_INTEGER 2 TagType The tag type: SQL_SMALLINT 1 SQL_SMALLINT 2 2—analog tag 3—digital tag 4—string tag TagDataType The tag data type: 0—long 1—float 2—string Creating a pivot table in Microsoft Excel Use a pivot table to display and analyze data from any narrow–format .dbf log file.
Once you have created the pivot table, you can then display the data in a chart. This additional step is also described. Starting the PivotTable Wizard 1. Open Microsoft Excel. 2. On the Data menu, click PivotTable Report. If you did not install the Microsoft Office Data Access components, the PivotTable Report item cannot be selected from the Data menu in Excel. The PivotTable Wizard appears. Selecting the data source 1. In the PivotTable Wizard, click External Data Source, and then click Next.
2. Click Get Data. This brings up Microsoft Query and the Select Data Source dialog box. This dialog box displays a list of the available data sources. If the ODBC data source you want to use (in this case, dBASE Files) is not listed, you can add it by clicking the Browse button and selecting a data source from the Program Files\Common Files\Odbc\Data Sources directory. 3. Click dBASE Files (not sharable), and then click OK. The Add Tables dialog box appears.
4. In the “Look in” field, choose a project directory. Then choose the directory containing the data log files. If you used the default logging path, the files will be in C:\Proj1\Dlglog\Model name, where Proj1 is the name of your project and Model name is the name of the data log model. 5. Under Table Name, choose the file with a “t” before the .dbf extension. For example: 990208at.dbf. The “t” stands for tag name.
When retrieving data from log files, you will likely want the tag names—not the tag index. Therefore, you have to retrieve data from more than one table. To do this, you have to join tables. When you join tables, you connect one or more fields in the tables. These fields must have the same name and must contain the same type of data. 1. Join the TTagindex field in the tag name field list to the Tagindex field in the other list.
3. When you have selected all the fields you want, open the File menu and then click Return Data to Microsoft Excel. When you are back in Microsoft Excel, click Next in the PivotTable Wizard. Organizing the pivot table After you have selected the data for your pivot table, specify how you want that data to appear. Use these buttons to organize your table. 16–24 1. In the Wizard, drag the field buttons and place them in the table. 2. When the table is set up, click Next. 3.
4. To display the table, click Finish. The pivot table is displayed in the worksheet. Creating a chart 1. To create a chart from the pivot table, select the data you want to use. 2. On the toolbar, click the Chart Wizard button. 3. Follow the instructions in the Wizard to create the type of chart you want.
When you finish, the chart will be displayed in the worksheet. Sharing tag values locally RSView32 works as both an OPC or DDE server and an OPC or DDE client. This means you can share tag values with a wide range of devices and other Windows applications. 4. The rest of this chapter explains how to use OPC and DDE to exchange values between different applications on the same computer (that is, locally).
To request data from RSView32, a third-party OPC client application on the same computer must use this information: Server: RSI.RSView32OPCTagServer Type: Local Server Computer Name or Address: Since the client and server are on the same computer, this field is inaccessible. Access Path: Project name. You can leave this blank. If you specify a name, use the name of the open project. Update Rate: A rate in seconds. Address: Name or address of the tag in the server.
Each DDE client application uses different delimiters to separate these three fields; use the delimiters that are appropriate to your application. Example: Using Microsoft Excel to read a tag value This example describes how to use Microsoft Excel to read a tag value. Microsoft Excel is the DDE client application. RSView32 is the server application.
Enabling RSView32 for tag writes By default, other applications cannot write to tags in RSView32. To enable writing to tags, you have to issue the RTDataWriteEnable command (from the command line or another RSView32 component). Example: Writing to a tag The following example shows a Microsoft Excel macro that will write to the Process\Ingred1\SP tag in the Samples project. Microsoft Excel is the DDE client and RSView32 is the DDE server.
Sending DDEExecute commands to other applications You can use RSView32 to send DDEExecute commands to other applications. However, RSView32 does not accept DDEExecute commands from other applications. To send commands to RSView32 from other applications, use the RSView32 Object Model with a programming language such as Visual Basic®. For more information about using the RSView32 Object Model, see Help. 1. Run the application to which the command is being sent. 2.
17 Chapter Using networks With RSView32™ on a network, you can: share project components among multiple workstations during development and runtime share data logged by one workstation use OPC® to share tag values among multiple workstations Sharing project components during development and runtime You can set up RSView32 to share project components during development and runtime by storing common components on a file server or shared drive.
Sharing components at runtime Sharing components at runtime allows you to centrally maintain a project. For example, you could store the following components on a central file server: security graphic displays activity, alarm, and data logs IMPORTANT You cannot share a tag database. When setting up a project to share components, ensure you have read and write access to the shared drive. The following illustration shows two workstations with RSView32 installed.
How to share components To share project components, follow these steps: 1. Create projects on each machine that will be accessing the shared components. 2. On each machine, use the Project Paths dialog box to set up paths to common components. For detailed information about the Project Paths dialog box, see “Setting the project path” on page 18-8.
2. On \\Computer2, in the Trend Configuration dialog box, select Historical, and choose Remote for the Data Source. Use the Browse button (...) to browse to this file: \\NetworkComputer\RSVProj\Datalog\LogModel\ LogModel.dlg. The LogModel folder and the LogModel.dlg file will not exist if data logging for LogModel has not been started yet. In this case, type this path in the Remote field: \\NetworkComputer\RSVProj\Datalog\LogModel\ LogModel.dlg 3.
If the data log model on Computer1 is configured to use the ODBC storage format and data source, Computer2 must have an ODBC data source configured with the same name in order for the remote historical trend to work. Using OPC for peer–to–peer network communications RSView32 supports the OPC 1.0a and 2.0 specifications. This section describes how to set up OPC to share tag values over a network.
Identifying the RSView32 server computer To uniquely identify an RSView32 server for OPC communications, the computer must have a name or address. The server computer can use Windows Server 2003, Windows XP, Windows 2000, or Windows Vista. To give the computer a name or address, you can use any of these methods: assign a name using the Universal Naming Convention assign a name using the Domain Name System set up a TCP/IP address For more information, see your Windows documentation.
Server: RSI.RSView32OPCTagServer Type: Remote Server Computer Name or Address: The name or address of the server computer. See “Server Computer Name or Address” on page 3-9 for information about the format to use. Access Path: Project name. You can leave this blank. RSView32 automatically uses the open project on the server computer. Update Rate: A rate in seconds. Address: Name or address of the tag in the server. (You specify the address when you assign the OPC node to a tag in the Tag editor.
the project on the Plant computer is called Bottling and it contains a tag called RejectCount RSView32 OPC client Computer name = Supervisor OPC Tag Values RSView32 OPC server on plant floor Computer name = Plant Project name = Bottling DH+ PLC Values Area1 How the Supervisor Gets Values In the Node editor, you create an OPC node called Plant_Computer that has the following information: 17–8 Server: RSI.
Access Path: Bottling (optional) Update Rate: 5.000 seconds You create a tag that points to the Plant computer. In the tag’s Node field, you assign the Plant_Computer node. In the tag’s Address field, you enter RejectCount, which is the tag you want values for. The information in the Address field is the OPC tag address. When the RejectCount tag is used anywhere in the Supervisor computer, it gets its value from the RejectCount tag in the Bottling project on the Plant computer.
enable RSLinx Gateway For information about configuring RSLinx Gateway, see the documentation supplied with RSLinx. Configuring RSView32 for use with RSLinx Gateway To use RSLinx Gateway with RSView32, do the following in RSView32: use the RSLinxOPCRemote program provided on the RSLinx CD to register the RSLinx Gateway on the computer on which RSView32 is installed. in the Node editor, set up a remote OPC node for each PLC. For more information about setting up an OPC node, see page 3-5. create tags.
driver name is RSLinx Remote OPC Server. You don’t need to specify a vendor or version number. Access Path: PLC_HVAC1 The access path is the DDE/OPC topic name in RSLinx. The figure below shows how the node looks in the Node editor. Once you have created the node, assign it to a tag in the Tag Database editor. The address tells RSView32 where in the node to get the data.
The figure below shows how the tag looks in the Tag editor.
18 Chapter Running your project Summary of steps Once you have developed your project, you are ready to run it.
To open the Startup Editor 1. In the Project Manager, open the System folder. 2.
Preferences To specify how the project window will look at startup: 1. Click the Preferences tab. 2. Under Show at Runtime, select the check box for each item you want at runtime. Each item is shown in the illustration on the following page. If Title Bar is not selected, or if Switch to other Apps is selected, these fields are grayed out.
Close button Maximize button Minimize button Title bar Control box Menu bar Project Manager Activity bar 3. Under Disable, select the check box for each item you want to disable. On Windows Server 2003, Windows XP, Windows 2000, and Windows Vista, you cannot disable Ctrl–Alt–Del through the Startup editor. To lock users into an RSView32 runtime application on these operating systems, use the Win2K XP DeskLock tool included in the RSView32 Tools program folder.
see Chapter 10, Adding security. For details about the ProjectShow command, see Appendix A, RSView32 commands, or see Help. Switch to other Apps: When Switch to other Apps is disabled, the following occurs at runtime: Alt–Tab, Alt–Shift–Tab, and Ctrl–Alt–Esc, which switch to other applications, are disabled Alt–F4, which closes RSView32, is disabled 4. Click OK.
Startup To specify the project components you want to run at startup: 1. Click the Startup tab. IMPORTANT 2. The order items appear in the Startup editor is not the order in which items will run. If you have created a project that has components that must start in a particular order, create a macro that will run when the project starts. Check the box for each item you want to run when the project starts. Where required, specify the file you want to run. Alarming Starts alarm monitoring.
Communication Status Logs communication errors to the activity log file and/or the activity bar if you set the project up to do this. To set this up, open the Activity Log Setup editor and ensure the Log File and Activity Bar check boxes are selected for the Communications category. OPC/DDE Server Enables RSView32 as an OPC® and DDE server. This is the same as using the RTDataServerOn command. Data Logging Starts running the specified data log model. This is the same as using the DataLogOn command.
Shutdown Macro Runs the specified macro. Any macro can be used as a shutdown macro. Initial Graphic Displays the specified graphic display file. 3. Click OK. Setting up a project in a new location It is important to test your project in the location from which it will run, if you will run the project from a different directory or different computer than the one on which you configured the project. 1.
When you copy a project from one computer to another, RSView32 automatically changes the default paths to the drive and directory the project has been copied to.
2. Change the application or database paths as described below. 3. Click OK. Changing application paths The Application Paths tab lists RSView32 editors and shows the current default path for all components associated with the editors. When you change the default path for an editor, any new components you create for it will automatically be stored in the new path.
To change the default path for new components: 1. In the Name field, select an editor. 2. In the Default Path field, specify a new path. 3. Click OK. To change the default path for existing components: 1. In My Computer, Windows Explorer, or File Manager, move the file to its new location. 2. In the RSView32 Project Paths dialog box, click the Application Paths tab. 3. In the Name field, select an editor. The components associated with the editor are displayed in the Components field. 4.
4. Select a component. 5. In the New Path For Component field, specify a new path. 6. Click OK. Specify the new path here. Changing the database path In the Database Paths tab, you can change the database that will be the data source for the project. 1. Click the Browse button beside the Path to Database field. 2. Select the new data source and then click Open. 3. Click OK. 4. Close and re–open the project to complete the operation.
3. In the dialog box that opens, select the language whose settings you wish to use. 4. Verify and/or customize the settings on the Numbers, Time, and Date tabs. 5. Click OK. For more information, see your Windows documentation. Running a project When you are developing a project, you can test it by clicking the Run Mode tab in the Project Manager and then clicking the Run Project button.
Running a project automatically You can set up a project to run automatically when Windows starts. 1. Click the Start button on the Windows task bar, point to Settings, and then click Taskbar or click Taskbar & Start Menu. 2. Click the Start Menu Programs tab or Advanced tab. 3. Click Add. 4. Type the path to RSView32 or click Browse and locate RSView32. Add the project name and the /r parameter to the command line.
use the System Agent utility available with the Windows 95 Plus Pack or Microsoft® Plus! 98. in the RSView32 Events editor, create an event that uses the free_bytes function and displays a message when disk space falls below 10 MB See page 14-21 for more information about the free_bytes function. See Chapter 9, Configuring events, for information about events.
execution of VBA programs stops, but events may continue to fire if your VBA program does not destroy its objects If a shutdown macro has been specified in the Startup editor, the macro will run once the above components have closed and stopped running.
A Appendix RSView32 commands This appendix describes: where and how to use RSView32™ commands how to use the command line RSView32 commands and their syntax Using RSView32 commands Where to use commands You can use commands in the following places: in a field that requires you to enter an action.
Parameters do not have to be entered in the order they are listed. Start each new command on a new line or separate commands on the same line with a semicolon (;). Separate multiple parameters with a space. Enclose long file names containing spaces with double quotes when the file names are used as parameters. For example ActivityLogSendToODBC “c:\mydsn\activity db.dsn” ActivityTbl /UDerek /Ppasswd The exclamation mark (!) indicates the start of a comment.
command will be truncated if the substituted tag values cause the command to exceed this length. Using dollar signs to create a placeholder in the command is an alternative to the Parse utility available in the RSView32 Resource Kit™. The dollar signs alternative offers better performance. Example 1: A macro using placeholders in commands Display Screen$Tag1$ Display $Tag3$$Tag2$ Valve23 = Open When the macro runs, Tag1 = 1, Tag2 = 2, and Tag3 = Screen. Note that these are all string tags.
Example 2: Changing the value of a tag and tag placeholders In this example, Tag1’s initial value is zero. The value 4 is assigned to the tag Tag1, which is then used in a macro. Type the following text in a button’s press action: Tag1 = 4 Sets the value of Tag1 to 4. Display_Detail Tag1 Executes the Display_Detail macro, using Tag1 as a parameter.
Using the command line Use the command line during development and runtime.
Building a command string 1. Open the Command Wizard. 2. In the Command Categories list, click a folder. When you click a category here . . . the commands for that category are listed here. To resize the list boxes, drag this bar to the left or right.
3. Select a command by clicking it in the Commands field. To change the order in which commands are listed, click the column title. To see all the information for a command, use the scroll bar. Command Name: Lists the commands in the open folder. Command Description: Form: Describes the command’s function. Shows the command syntax. Angle brackets < > indicate a required parameter. Square brackets [ ] indicate an optional parameter. 4. Click Next to add parameters or click Finish.
6. When the command is complete, click Finish. The RSView32 commands, listed alphabetically = (Equal) [&] = Writes the value resulting from an expression to a tag. [&] Forces the command to be executed asynchronously, which makes the command faster. The name of the tag that will store the result of the expression. A value, string, tag name, or a more complex expression.
Examples: The = (Equal) command &Tag1 = Tag1 + 1 Evaluates the command asynchronously. Increases the value of Tag1 by 1. Tag1 = Tag2 Sets the value of Tag1 to be the same as Tag2. Tag1 = Tag2 + Tag3 Adds the values of Tag2 and Tag3 and stores the result in Tag1. 1Pump = {Industry–2} + {2Pump} Adds the values of Industry–2 and 2Pump and stores the result in 1Pump. Braces surround Industry–2 because of the dash in the name. Braces surround 2Pump because the name starts with a number.
RSView32 command that opens the editor. See the examples below. * Closes all windows. Ctrl–F4 also closes the active window. Examples: The Abort command Abort Without a parameter, closes the window that has focus. Abort me Closes the window from which the command is executed. Abort Display Closes all open graphic displays. Abort Display Pumps or Abort Pumps Closes the graphic display called Pumps. Abort Monitor Closes all open tag monitors. Abort * Closes all windows.
Acknowledge Acknowledge [tag_name] Acknowledges an alarm or a group of alarms. This command gives no indication that it has run but will display a message if not executed properly. If an acknowledge bit is associated with an alarm, acknowledging the alarm sets the acknowledge bit. [tag_name] The name of the tag to be acknowledged. This can be a tag name, a name with wildcards, or the [tag] literal string. If no tag is specified, this command acknowledges the most–severe, most–recent unacknowledged alarm.
Acknowledge [tag] Acknowledges the alarm for the tag associated with the highlighted object in the active graphic display. AcknowledgeAll AcknowledgeAll Acknowledges all outstanding alarms. This command runs more quickly than Acknowledge *. It gives no indication that it has run but will display a message if not executed properly. If an acknowledge bit is associated with an alarm, acknowledging the alarm sets the acknowledge bit.
ActivityLogSend ActivityLogSendToODBC [/Wn] [/Uuser_name] [/Ppassword] ToODBC Exports activity log data from DBF files to the ODBC database. The connection to the ODBC database is maintained for the length of time specified by the wait (/W) parameter. A valid ODBC data source name. If the name has a space embedded in it, enclose the name in quotes (“”). The name of a table in the ODBC database where the data will be exported.
ActivityOn ActivityOn Starts activity logging. Activity logging is on by default. ActivityPrintOff ActivityPrintOff Turns off the printing of activity logging. By default, activity log printing is turned on when you start an RSView32 project. ActivityPrintOn ActivityPrintOn Turns on the printing of activity logging if it has been turned off by the ActivityPrintOff command. By default, activity log printing is turned on when you start an RSView32 project.
The type of alarm transaction, which must be one of the following: [IntoAlarm] or [In] Indicates that the tag has gone into alarm. [OutOfAlarm]Indicates that the tag has gone out or [Out] of alarm. [InAndOut OfAlarm] or [InAndOut] [TagType] Indicates that an alarm has occurred, but the tag is again immediately out of alarm, such as a digital change–of– state alarm.
The 24–hour military format for time. You must use this format for indicating the time. [Date] A date that can be specified in the same format as the Windows® date style configured for your computer. If you want to use a VBA program to set the date, you can use any date format that conforms to the MFC class COleDateTime. If you do not specify a date, the current date is used.
AlarmLog Remark AlarmLogRemark [“Text”] [/P] [/Sn] [/R] [/Ttagname] Adds the specified text string as a transaction in the alarm log file. [“Text”] [/P] A text string, up to 132 characters long. The text can contain the following placeholders: [\D] the current date [\T] the current time [\N] the tag name. If the tag is in a local tag database, you can also use the placeholders [\S] tag description and [\U] tag units.
alarm severity at runtime, but the operator cannot change the severity. AlarmLogSend ToODBC [/R] Logs the remark to a printer as well as to the alarm log file. If the alarm severity is not specified (/Sn parameter), the printer for Severity 1 is used. If no printer is assigned to the specified severity, the alarm log remark is not printed. [/Ttagname] The string that is logged in the Tagname column of the alarm log file.
the connection is established, RSView32 waits the specified time and, if another command is received to export data, the command is executed and the wait timer is reset. If no command is received within the wait time, the connection is closed. AlarmOff [/Uuser_name] A user ID that is valid on the data source. [/Ppassword] A password that is valid on the data source. AlarmOff Stops alarm monitoring. Once this command has run, it displays a message indicating that alarm monitoring has stopped.
AppAbort AppAbort Closes the specified Windows application. The name of a Windows application exactly as it appears in the application’s title bar. Example: The AppAbort command If Notepad is open and contains an untitled file, the Notepad title bar will read Untitled – Notepad.
Examples: The AppStart command AppStart c:windows\notepad c:\autoexec.bat Opens Notepad and displays the autoexec.bat file. AppStart c:\Program Files\Plus!\Microsoft Internet\Iexplore.exe Opens Microsoft® Internet Explorer. Beep Beep Runs a wave file to produce a sound from the computer speaker. The sound is a wave file assigned to the Default Beep in the Windows Control Panel. Channel Channel Opens the Channel editor. Class Class Opens the Scan Class editor.
ComStatusOn ComStatusOn Starts logging of communication errors if RSView32 is set up to do so. To log communication errors, ensure the Communications category is selected in the Activity Log Setup editor. To have error logging automatically start when a project starts, open the Startup editor and click the Communication Status check box. Database Database Opens the Tag Database editor. DatabaseSync DatabaseSync Makes RSView32 convert the tag database into binary format the next time the project opens.
DataLogChange Rate DataLogMerge ToPrimary DataLogChangeRate [unit] Changes the periodic log rate. The change affects the current logging session only, and won’t be retained if data logging is stopped and restarted. The name of a data log model, without a file extension. The numeric portion of the time interval for the log rate. For example, if you want to log data every 20 seconds, the value is 20. The value must be an integer from 1 to 64,000.
DataLogNewFile DataLogNewFile Creates a new data log file for the specified model or for all models, on the path RSView32 is currently logging to (either the primary path or the backup path). If RSView32 is logging to an ODBC database, RSView32 logs an End snapshot and then a Begin snapshot when you issue this command. DataLogOff The name of the data log model without a file extension. * Creates new files for all models that are currently running.
DataLogPath DataLogPath Opens the Data Log Path editor. You can use the editor to change the primary and secondary paths for dBASE® IV data log models, and the backup path for ODBC data log models. You cannot change the ODBC database using the Data Log Path editor. The name of a data log model without a file extension.
DataLogSwitch Back DDEExecute DataLogSwitchBack Switches data logging back to the primary dBASE IV file path or ODBC database for the specified model or for all models. This command switches data logging for a model only if the model is running, RSView32 is logging data to the secondary or backup path, and the primary path or ODBC database is available. For .dbf files, RSView32 creates a new set of files when it switches back to the primary path.
Examples: The DDEExecute command DDEExecute RSlinx|__Drivers [Who_Active()] Sends the Who_Active command, which displays the default RSLinx® RSWho window. Drivers must be preceded by two underscores. DDEExecute WINAB5|SYSTEM .SR 3 Sends WINtelligent LOGIC 5™ (WINAB5) the Dot command SR 3, which means search for Rung 3. DDEExecute WINAB5|SYSTEM .UI Sends WINtelligent LOGIC 5 (WINAB5) the Dot command UI, which displays the System Information window.
Define Define [string] Creates a symbol. A symbol is an abbreviation for a command or a command with parameters. The symbol can be used anywhere a command can be used. You cannot nest symbols. Symbol definitions are valid only during the current session; they must be re–defined each time RSView32 is restarted. Symbols are typically defined in a startup or login macro. The abbreviated command. It cannot contain spaces. [string] An existing command with or without parameters.
Derived Derived [file] In edit mode, without the parameter opens the Derived Tag editor. With the parameter, opens the specified derived tag file. [file] The name of a derived tag file without a file extension. DerivedOff DerivedOff Stops running the specified derived tag file. The name of a derived tag file without a file extension. DerivedOn DerivedOn Starts running the specified derived tag file. The name of a derived tag file without a file extension.
Do not cache more than 200 displays using the [cache] parameter and/ or the Cache After Displaying option. The name of a graphic display file without a file extension. [/B] Displays the specified graphic display in the background. [/E] Disables the Enter key so it does not download values in numeric input fields to the programmable controller or server, unless the Display On-Screen Keyboard option is selected (in the Behavior tab of the Display Settings dialog box).
display from the cache, use the FlushCache [file] command. [/Pfile] The name of the parameter file that contains the tag names to be substituted for placeholders in the display. If the display does not contain placeholders, do not use this parameter. If the parameter file has a long file name, enclose the file name in quotes, for example /P“Long file name”. [/Ttag_name] One or more tags, separated by commas and no spaces, to be substituted for placeholders in the display.
Examples: The Display command Display Sample The first time the graphic display called Sample is opened, it will be positioned and sized as specified in its Display Settings dialog box. When the display is closed, its size and position will be saved, so the next time it is opened it will be the same size and position as when it was last closed.
Download Download Writes the value in the selected input field of the active graphic display to the programmable controller or server. This command operates on the active graphic display. If no display is active, this command is ignored. Ctrl–PgDn also downloads the value in the selected input field. The Enter key also downloads the value in the selected input field.
DriverSecondary DriverSecondary Switches from the primary driver to the secondary driver on the specified channel. DriverToggle The number of the channel (1 through 4) that is being switched from its primary to secondary driver. DriverToggle Switches from the current driver to the one not being used on the specified channel. EchoOff The number of the channel (1 through 4) that is being switched from one driver to another.
EventOn EventOn Starts running the specified event file. The name of an event file without a file extension. To have an event file automatically start when a project starts, open the Startup editor, click the Event Detector check box and specify a file name. FlushCache FlushCache [file] Without the parameter, unloads all graphic displays from the display cache. With the parameter, unloads the specified graphic display from the display cache.
FTDataWrite Disable FTDataWriteDisable FTDataWrite Enable FTDataWriteEnable Graphic Graphic [file] Stops FactoryTalk Clients from writing values to RSView32 tags. This command has no parameters. Allows FactoryTalk clients to write values to RSView32 tags. This command has no parameters. In edit mode, without the parameter, opens the Graphic Display editor; with the parameter, opens the specified graphic display file. [file] HandshakeOff The name of a graphic file without a file extension.
Help Help [word] [/Ffile] Displays a Windows help file. [word] A word you want to search for in the help file. When you specify a search word, the command will either: open the help file at a topic if the word uniquely identifies that topic open a list of related topics [/Ffile] The name of a Windows help file. The default help file is for RSView32. If no search word is specified, the command opens the RSView32 help file and displays the Contents topic.
Examples: The Identify command Identify Hopper1\Divider Runs the Identify command or macro for the tag Hopper1\Divider, whether or not the tag is in alarm. Identify [tag] Runs the Identify command or macro for the selected tag in the active graphic display. Identify Runs the Identify command or macro for the most recent, most severe unacknowledged alarm. Invoke Invoke Use this command with ActiveX® objects.
object The name of the ActiveX object as specified in the Object Name dialog box in the Graphic Display editor. method The name of a function or sub–routine in the ActiveX object. The method is initiated by an external event such as the Invoke command. parameter The tag name or constant that the method will use. You must specify all of the parameters, even those that are optional. tag_name=file.object.method(parameter1, parameter2, . . .
KeyEdit KeyEdit [file] Without the parameter, opens the Global Key editor. With the parameter, opens the editor and the specified file. [file] LInsertStringTag The name of a key file without a file extension. LInsertStringTag [sheet] [tagname series] Use this command to select one or more string tags from the tag database and insert the tag names to an Excel spreadsheet if the tags do not exist in the spreadsheet. [sheet] The spreadsheet name of Excle file. [tagname series] A series of tag names.
Using this command with both parameters logs the user into the system. Using this command with only one parameter displays the login dialog box. Logout Logout Logs the current user off the system. LTagSubstitute LTagSubstitute [language] [sheet] Use this command to substitute string values of all the tags specified in the selected spreadsheet with the selected language. [language] The selected language name. [sheet] The spreadsheet name of Excel file. Space is not allowed in Excel spreadsheet name.
Monitor Monitor [file][/Xnnn] [/Ynnn][/Ttag_name] In edit mode, without the [file] parameter, opens the Tag Monitor editor; with the [file] parameter, opens the specified tag monitor file. In run mode, with the [file] parameter, opens the specified tag monitor file. With the [/Ttag_name] parameter, opens a tag monitor containing the specified tags. [file] The name of a tag monitor file without a file extension. [/Xnnn] Positions the tag monitor nnn pixels from the left edge of the screen.
Monitor Bread Displays the tag monitor file called Bread. NextPosition NextPosition Moves focus to the object with the next highest index number. This command operates on the active graphic display. If no display is active, this command is ignored. Tab also moves focus to the object with the next highest index number. See also Position and PrevPosition. NextWindow NextWindow Moves focus to another open graphic display. Ctrl–Tab and Ctrl–F6 also move focus to another open graphic display.
NodeSwitch NodeSwitch Permanently changes a device node’s address, an OPC® node’s computer name, server name, and access path, or a DDE node’s application and topic. The name of the node that you want to switch to another programmable controller address, server, or application. is one of the following: station For device nodes, the physical address for the programmable controller you want to switch to.
Password Password Displays the Password dialog box so users can change their password. Users must already be logged in to use this command. Pause Pause Specifies a pause between the execution of two commands. You can use this command in macros, from the command line, or as an action for a button. All commands or macros that follow the Pause command must not be asynchronous (preceded by the & sign), otherwise the Pause command has no effect.
See also PrevPosition and NextPosition PrevPosition PrevPosition Moves focus to the object with the previous index number. This command operates on the active graphic display. If no display is active, this command is ignored. Shift–Tab also moves focus to the object with the previous number. See also Position and NextPosition. PrevWindow PrevWindow Moves focus to another open graphic display. Ctrl–Shift–Tab and Ctrl–Shift–F6 also move focus to another open graphic display. See also NextWindow.
[/U] Initiates an update of tag values in all input fields before starting to print. This parameter is not necessary with input fields that are updated continuously. [/Pfile] Specifies the name of a parameter file that contains tag names to be substituted for placeholders in the display. [/Ttag_name] Specifies one or more tag names to be substituted for placeholders in the display. Separate multiple tag names with commas; do not use spaces.
ProjectHide ProjectHide Hides the Project Manager so it is not visible on the screen. Ctrl-Alt-P also hides the Project Manager if it is visible. ProjectRun ProjectRun Starts running the project. This is the same as choosing the Run Project button in the Run Mode tab of the Project Manager. ProjectShow ProjectShow Displays a hidden Project Manager. Ctrl-Alt-P also shows the Project Manager if it is hidden. ProjectStop ProjectStop Stops running the project.
PushBack PushBack Moves the specified graphic display behind all other windows. If the specified graphic display is of the On Top type, PushBack positions the display behind any other open On Top displays, and in front of any open displays of the Replace or Overlay type. The name of an open graphic display file without a file extension. If the specified display is of the On Top type, and if no other On Top displays are open, nothing happens when you issue this command.
The amount to add or subtract from the current programmable controller value, as follows: plus (+) or minus (-) a numeric value plus (+) or minus (-) a percentage of a numeric value in the form: +value% plus (+) or minus (-) a tag If Ramp calculates a value that is outside of the tag’s minimum and maximum range, it will write the highest or lowest allowable value to the programmable controller or server.
RecipeEdit RecipeEdit [file] Without the parameter, opens the Recipe editor. With the parameter, opens the specified recipe file. [file] RecipeRestore The name of a recipe file without a file extension. RecipeRestore Reads the values from a recipe file into all input fields in the active graphic display. This command is used with the Recipe field. The name of the file, without a file extension, tag values are read from. This command operates on the active graphic display.
Remark Remark Writes a text string to an activity log file, which is useful for operators to store comments. A string up to 132 characters long. The string can contain any characters, including spaces. Enclose the exclamation mark (!) and the semi–colon (;) in single or double quotes. To log comments, the Remarks category must be selected in the Activity Log Setup editor. RTDataServer Off RTDataServerOff Stops running the RSView32 real-time data server.
RTDataWrite Disable RTDataWriteDisable [/Quiet] [/NetDDE] Disables writes by external Windows applications running OPC or DDE, so these applications cannot change tag values in RSView32. The RSView32 OPC or DDE server is also known as the real-time data server. If the RSView32 real-time data server is not running— that is, if the RTDataServerOn command has not been run— RTWriteDisable also starts the RSView32 real-time data server.
you to specify the setting when you issue the command. [/NetDDE] Enables RSView32 as a NetDDE server to remote DDE clients. If the real-time data server is already running, this parameter is ignored. By default, writes are disabled. ScreenPrint ScreenPrint Generates a screen print on the default printer specified in Windows. See also PrintDisplay. Security Security Opens the Security Codes editor. To prevent users from changing security at runtime, restrict access to this command.
Special keys can be in upper and/or lower case letters. You can type any of the following to represent the special keys on the keyboard: Set Backspace, BkSp, BS Insert End Left Enter PgDn Escape, Esc PgUp Delete, Del PrtSc Down Right F1 to F12 Tab Home Up [&]Set [/V] Writes a value to a tag. IMPORTANT If a node has been disabled, the Set command changes the value in the value table but not in the programmable controller.
is one of the following, depending on the tag type: For analog tags: Numeric value within the range specified by the tag’s minimum and maximum values. Percentage of the total min/max range. The formula is: value = min + percentage/100 * (max – min) Tag name of another analog or digital tag. For digital tags: Numeric value of 0 or 1. Tag’s on or off label specified in the tag database. Setting a digital tag to its on label writes the value 1, and setting the tag to its off label writes the value 0.
Set Valve\23 open Valve\23 is a digital tag with its on label configured as open. This command uses the on label for the tag to write the value “1” to the programmable controller or server. Set Hopper1\Level Preset Hopper1\Level is a tag and Preset is a tag with a value of “90.” This command writes “90” to the programmable controller or server. Set String\string1 “open” String\string1 is a string tag. This command writes “open” to the programmable controller or server.
StartupConfig StartupConfig Opens the Startup editor. Summary Summary [/Xnnn] [/Ynnn] Runs the specified alarm summary file. Suppressed The name of an alarm summary file without a file extension. [/Xnnn] Positions the X coordinate of the alarm summary window to nnn pixels from the left edge of the screen. Valid range depends on screen resolution. [/Ynnn] Positions the Y coordinate of the alarm summary window to nnn pixels from the top edge of the screen.
SuppressOn SuppressOn Suppresses reporting of alarms for the specified tag. The name of a tag, or a wildcard. This command is useful when equipment repairs or maintenance would otherwise result in alarms being generated. All alarms for each threshold of the monitored tag are suppressed. Alarm suppression can take place before or after issuing the AlarmOn command.
Undefine Undefine Deletes a symbol definition that was created using the Define command. Example: The Undefine command Undefine test Deletes the definition for the symbol “test” that was previously created with the Define command. Undefine * Deletes all symbol definitions. See also Define. Upload Upload In a graphic display, reads a value from the programmable controller or server and displays it in the selected input field. This command operates on the active graphic display.
VBAEdit VBAEdit [program_name] Opens the VBA integrated development environment (IDE) so you can edit a VBA program. [program _name] VBAExec Any Sub statement in the ThisProject module. If you don’t specify a program name, the IDE opens at the first program. If you specify a program name, the IDE opens with the cursor at the specified Sub statement. The program name is not case sensitive. VBAExec [parameters] Runs a VBA program.
B Appendix System tags System tags are preconfigured tags created by RSView32™. Use system tags for read–only applications in your project. Alarms The following tags display alarm information: Tag Name Type Displays information about system\AlarmBanner String The most recent, most severe alarm. If an alarm of an equal or higher severity occurs, it replaces the first alarm, even if the previous alarm has not been acknowledged.
Tag Name Type Displays information about system\AlarmSummaryItems Analog The number of alarm transactions in an unfiltered alarm summary. system\AlarmSummaryItemsUnacked Analog The number of unacknowledged alarms in an unfiltered alarm summary. system\AlarmSuppressedCount Analog The number of tags with alarm suppression turned on. Communications The following tags record device communication information.
The following tags record OPC® client communication information. These tags are added to the system folder when you configure an OPC node in the Node editor. Tag Name Type Displays information about system\ComErrorStringOPC String Most recent OPC error message. system\ComErrorValueOPC Analog Internal number of most recent OPC error. system\ComStatusStringOPC String Current status of OPC communications. Will be the same as system\ComErrorStringOPC if the error condition still exists.
Graphics The following tags can be used to make graphic objects appear as though they are blinking on and off: Tag Name Type Function system\BlinkFast Digital Toggles on and off every 100 ms (10 times per second). system\BlinkSlow Digital Toggles on and off every 500 ms (twice per second). A more efficient way to make graphic objects blink is to use the blinking color option in color animation. For details, see page 12-13.
Time The following tags record time and date information in various formats: Tag Name Type Provides this data Read or write system\Date String System date. Read only system\ DateAndTimeInteger Analog Number of seconds elapsed since midnight (00:00:00) January 1, 1970, coordinated universal time (UTC). Read only system\ DateAndTimeString String Complete date and time display For example: Read only Monday, December 12 1997 10:47:50 AM system\DayOfMonth Analog Day of the month (1 – 31).
For example, if you typed Trend as the control tag, you would find a folder called Trend in the list of folders displayed in the Tag Database editor. The folder would contain the tags listed in the following table, but each tag would be prefixed with “Trend”. The \CurrentPen tag would be Trend\CurrentPen, and so on. Tag name Type Function Read or Write? \CurrentFile Analog Number of the current data log file. Data log files are numbered sequentially.
Tag name Type Function Read or Write? \PenMask Analog A 16–bit mask that controls the visibility of the trend pens. If the bit corresponding to a pen is set in this mask, the pen is displayed. For example: Read and write \StartTime Analog PenMask = 0000 0000 0000 0000 = 0 are displayed. No pens PenMask = 0000 0000 0000 0100 = 4 3 is displayed. Only Pen Integer tag specifying the time at the right margin of the time scale.
User The following tag contains the name of the current user in the activity log file: Tag Name Type Function system\User String Contains name of logged–in user. Windows memory resources The following tags that record Windows® resources are no longer valid. Tag Name Type Provides this data system\MemoryB1Meg Analog This tag is no longer valid and has a value of 0. system\MemoryGDI Analog This tag is no longer valid and has a value of 0.
C Appendix Differences between RSView32 and ControlView This appendix describes: how to import ControlView™ and ControlView Builder projects into RSView32™ differences between RSView32, and ControlView, and ControlView Builder Importing ControlView projects You can import most components from a ControlView or ControlView Builder project into RSView32 using the ControlView Project Import Wizard in the RSView32 Tools group. For details, see the documentation accompanying this tool.
Alarms Alarm banner and alarm status display The alarm banner and alarm status display are not preconfigured in RSView32. To include these items in your project, either use the objects in the graphic library called Alarms or create them yourself in the Graphic Display editor. The information for an alarm banner and alarm status display comes from system tags that report on alarms. System tags are preconfigured tags provided with RSView32. These tags are in the System folder in the Tag Database editor.
You can format an alarm summary in any way. The Alarm Summary editor has tools for formatting headings, fonts, colors, and buttons. You can also filter and sort data so only particular alarm information is displayed. Commands Obsolete commands The following table lists commands not supported in RSView32. If you import ControlView macros, event files, global key files, graphic displays, or alarm definitions that use these commands, you will have to revise them.
CVDos LPRConfig PCIMConfig TopLevelOn DataLogExport Macro Plot TouchConfig DataLogRpt Menu PMClear TouchOff DBExp MenuBar PMConfig TouchOn DBImp MenuBoxOff PMDisplay Trend DBRpt MenuBoxOn PMEventLog TrendRpt DCConfig MenuBoxToggle PMLimits Unload DerivedRpt ModDiag PMRealTime UnsCacheOff DeviceRpt ModemCommand PMSnapshot UnsCacheOn Dial ModemDirectory PMStatus WindowConfig ModemSetUp PMWaveform Renamed commands The following table lists ControlView commands that hav
Data log You cannot import ControlView data log models into RSView32. In RSView32, data log files are not stored in a circular file set. Instead, you configure when to create and delete files. Information in the data log file is stored in .dbf (dBase IV) file format or in ODBC storage format. You can access the information in the .dbf file with any third– party software that reads .dbf, such as Microsoft Excel, Crystal Reports, and Visual FoxPro, or store the data in any ODBC-compliant database.
The number of event files is limited only by memory and disk space. Each event file can contain up to 1,000 events as compared to ControlView’s limit of 600 events. You can run up to 20 event files simultaneously. Global keys You cannot import ControlView global key files into RSView32. In RSView32, you cannot run more than one global key file at a time. If you try to run more than one file, the files are not merged. Instead, the second file overrides the first file.
blinking color animation horizontal and vertical position horizontal and vertical size rotation horizontal and vertical fill horizontal and vertical slider OLE verb RSView32 does not contain a tool for drawing bar graphs. To create a bar graph, draw a rectangle and apply height, width, or fill animation. If you import a bar graph from ControlView, the bar graph will automatically be changed to a rectangle with the appropriate type of animation and will work as it worked in ControlView.
The I/O address syntax for the SLC 5/03 (OS301) and SLC 5/04 has not changed. If you import a ControlView project that references I/Os from these SLC types, ensure the Type field of the Node editor is set to SLC 5 (Enhanced). Tag database In RSView32, group tags and structure tags are not supported. Instead, folders are used to organize tags. In RSView32, a local tag is called a memory tag. Tag names can be up to 255 characters long.
log files. For real-time data, use RSView32’s OPC® or DDE server capabilities. Modem option—use Windows and third–party products to support a modem. C–Toolkit tasks—use a tool such as scripting in RSView32 or Visual Basic® to create custom Windows applications that access real-time data through the RSView32 Object Model or DDE, and access historical data through ODBC/.dbf.
D Appendix Addressing syntax for Allen–Bradley programmable controllers This appendix contains: addressing syntax for Allen–Bradley® PLCs addressing syntax for Allen–Bradley SLCs™ addressing syntax for SoftLogix™ 5 controllers mnemonic tables The information here is applicable only for tags that have device as their data source. For detailed information about creating tags, see Chapter 4, Creating tags.
PLC addressing syntax This section provides addressing syntax for these types of programmable controllers: PLC–2 PLC–3 PLC–5®, which includes the PLC–5/10, PLC–5/12, PLC–5/15, and PLC–5/25 PLC–5 (Enhanced), which includes the PLC–5/11, PLC–5/20, PLC–5/30, PLC–5/40, PLC–5/60, and PLC–5/80 PLC–2 aaaa/bb aaaa Address: 0 – 7777 octal bb (optional) Bit offset within word: 0 – 17 octal Example of digital address: 11/17 Example of analog and string address: 1264 D–2 RSView32 User’s Guide
PLC–3 data table sections Fnnn:wwww/bb F File type: A = ASCII B = Binary N = Integer D = Decimal (BCD) O = Output I = Input F = Floating point S = Status H = High order integer nnn File number: 0 – 999 decimal wwww Word address: For I/O section: 0 – 7777 octal For all others: 0 – 9999 decimal bb (optional) Bit offset within word: 0 – 17 octal Bit offset not permitted in the F and H sections.
PLC–3 timers and counters FWWW:nnnn/bb F File type: C = Counter T = Timer WWW Structured word: CTL = Control word PRE = Preset value ACC = Accumulated value nnnn Counter/Timer number: 0 – 9999 decimal bb Bit offset within word: 15 octal = done bit 16 octal = timing bit 17 octal = enable bit Example of digital address: TCTL:125/17 Example of analog address: CPRE:125 D–4 RSView32 User’s Guide
PLC–5 data files Fnnn:eee/bb F File type: B = Binary N = Integer D = Decimal (BCD) F = Floating point A = ASCII nnn File number: 3 – 999 decimal For direct driver communication, binary, integer, and floating point file types use the default file number if the file number is absent. The default numbers are 3 (binary), 7 (integer), and 8 (floating point). eee Element number: 0 – 999 decimal bb (optional) Bit offset within word: 0 – 15 decimal Not applicable to floating point file types.
PLC–5 I/O and status files F:ee/bb F File type: O = Output I = Input S = Status ee Element number: For I/O files: PLC–5/10: 0 – 037 octal PLC–5/12: 0 – 037 octal PLC–5/15: 0 – 037 octal PLC–5/25: 0 – 077 octal For status files: 0 – 31 decimal bb (optional) Bit offset within word: For I/O files: 0 – 17 octal For status files: 0 – 15 decimal Example: O:64/17 D–6 RSView32 User’s Guide
PLC–5 timers, counters, and control files Fnnn:eee.MNE/bb F File type: C = Counter T = Timer R = Control nnn File number: 3 – 999 decimal For direct driver communication, timer, counter and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
PLC–5 (Enhanced) I/O and status files F:eee/bb F File type: I = Input O = Output S = Status eee Element number: For I/O files: PLC–5/11: 0 – 037 octal PLC–5/20: 0 – 037 octal PLC–5/30: 0 – 077 octal PLC–5/40: 0 – 177 octal PLC–5/60: 0 – 277 octal PLC–5/80: 0 – 277 octal For status files: 0 – 127 decimal bb (optional) Bit offset within word: For I/O files: 0 – 17 octal For status files: 0 – 15 decimal Example: O:167/11 D–8 RSView32 User’s Guide
PLC–5 (Enhanced) binary, BCD, integer, ASCII, float, and string files Fnnn:eee/bb or Fnnn:eeee/bb F File type: B = Binary D = Decimal (BCD) N = Integer F = Floating point A = ASCII ST = String nnn File number: 3 – 999 decimal For direct driver communication, binary, integer, and floating point file types use the default file number if the file number is absent. The default numbers are 3 (binary), 7 (integer), and 8 (floating point).
PLC–5 (Enhanced) binary files: optional syntax Fnnn/bbbbb F File type: B = Binary nnn (optional) File number: 3 – 999 decimal For direct driver communication, the default file number 3 is used if the file number is absent.
PLC–5 (Enhanced) timer, counter, control, SFC status, message, PID, block transfer, and token data files FFnnn:eee.MNE[ss]/bb FF File type: T = Timer C = Counter R = Control SC = SFC status MG = Message PD = PID control BT = Block transfer TD = Token data nnn File number: 3 – 999 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC addressing syntax This section provides addressing syntax for these types of programmable controllers: SLC 5, which includes the fixed I/O SLC 5, SLC 5/01, SLC 5/02, and SLC 5/03 (OS300) SLC 5 (Enhanced), which includes the SLC 5/03 (OS 301), SLC 5/04, and SLC 5/05 SLC 5 I/O files F:ss.
In RSView32, the first physical module of each type (input or output) is address slot number 0. The next module of the same type in the next higher–numbered rack slot is address slot number 1, and so on. Example: SLC 5 I/O module addressing SLC Type Rack Configuration CV for MS-DOS® Address or APS Address RSView32 Address Fixed L40 I/O module slot 0 (fixed) I:0.0 or I:0 I:0.1 O:0 I:0.0 or I:0 I:0.1 or I:1 O:0 I module slot 2 I:2 I:2 I/O module slot 0 (fixed) I:0.0 or I:0 I:0.1 O:0 I:0.
SLC 5 status files F:ww/bb F File type: S = Status ww Word address: SLC 500™: 0 – 15 decimal SLC 5/01: 0 – 15 decimal SLC 5/02: 0 – 32 decimal SLC 5/03: 0 – 68 decimal bb (optional) Bit offset within word: 0 – 15 decimal Example: S:15/6 SLC 5 binary and integer files Fnnn:www/bb F File type: B = Binary N = Integer nnn (optional) File number: Binary: 3, 9 – 255 decimal Integer: 7, 9 – 255 decimal For direct driver communication, binary and integer file types use the default file number if the file
SLC 5 binary files: optional syntax Fnnn/bbbb F File type B = Binary nnn (optional) File number: 3, 9 – 255 decimal For direct driver communication, the default file number 3 is used if the file number is absent. bbbb Bit offset from start of file: 0 – 4095 decimal Example: B3/3999 SLC 5 timer, counter, and control files Fnnn:eee.
SLC 5 timer, counter, and control files bit member addressing: optional syntax Fnnn:eee/MNE F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 timer, counter, and control files bit member addressing by bit address: optional syntax Fnnn:eee/bb F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 timer, counter, and control files analog member addressing: optional syntax Fnnn:eee.o/bb F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 (Enhanced) I/O files F:ss.www/bb F File type: I = Input O = Output ss I/O slot number: 0 – 30 decimal www (optional) I/O word number expansion: 0 – 255 decimal bb (optional) Bit offset within word: 0 – 15 decimal When input slot is 0: 0 – 23 decimal Example: I:22.254/13 IMPORTANT Writing to the output files of an SLC 5 is not recommended. However, if you do, be sure the SLC is not in RUN mode.
SLC 5 (Enhanced) binary, integer, float, ASCII, and string files Fnnn:www/bb F File type: B = Binary N = Integer F = Floating Point A = ASCII ST = String nnn (optional) File number: Binary: 3, 9 – 255 decimal Integer: 7, 9 – 255 decimal Floating Point: 8, 9 – 255 decimal ASCII: 9 – 255 decimal String: 9 – 255 decimal For direct driver communication, binary, integer, and floating point file types use the default file number if the file number is absent.
SLC 5 (Enhanced) binary files: optional syntax Fnnn/bbbb F File type B = Binary nnn (optional) File number: 3, 9 – 255 decimal For direct driver communication, the default file number 3 is used if the file number is absent.
SLC 5 (Enhanced) timer, counter, and control files Fnnn:eee.MNE/bb F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 (Enhanced) timer, counter, and control files bit member addressing: optional syntax Fnnn:eee/MNE F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 (Enhanced) timer, counter, and control files bit member addressing by bit address: optional syntax Fnnn:eee/bb F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SLC 5 (Enhanced) timer, counter, and control files analog member addressing: optional syntax Fnnn:eee.o/bb F File type: T = Timer C = Counter R = Control nnn (optional) File number: Timer: 4, 9 – 255 decimal Counter: 5, 9 – 255 decimal Control: 6, 9 – 255 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
SoftLogix 5 addressing syntax This section provides addressing syntax for SoftLogix 5 controllers.
SoftLogix 5 binary, BCD, integer, long integer, ASCII, float, and string files Fnnnn:eeee/bb F File type: B = Binary D = Decimal (BCD) N = Integer L = Long integer A = ASCII F = Floating point ST = String nnnn File number: 3 – 4095 decimal For direct driver communication, binary, integer, long integer, and floating point file types use the default file number if the file number is absent. The default numbers are 3 (binary), 7 (integer), and 8 (floating point).
SoftLogix 5 binary files: optional syntax Fnnnn/bbbbb F File type: B = Binary nnnn (optional) File number: 3 – 4095 decimal For direct driver communication, the default file number 3 is used if the file number is absent.
SoftLogix 5 timer, counter, control, SFC status, message, PID, block transfer, and token data files FFnnnn:eeee.MNE[ss]/bb FF File type: T = Timer C = Counter R = Control SC = SFC status MG = Message PD = PID control BT = Block transfer TD = Token data nnnn File number: 3 – 4095 decimal For direct driver communication, timer, counter, and control file types use the default file number if the file number is absent. The default numbers are 4 (timer), 5 (counter), and 6 (control).
Mnemonic tables Timer mnemonics Mnemonic Instruction Type ACC Accumulator Value Analog DN Done Digital EN Enable Digital PRE Preset Value Analog TT Timing Digital A Counter mnemonics Mnemonic Instruction Type ACC Accumulated Value Analog CD Count Down Enable Digital CU Count Up Enable Digital DN Done Digital OV Overflow Digital PRE Preset Value Analog UN Underflow Digital Update Accumulator Value Digital For fixed I/O SLC only: UA D–30 RSView32 User’s Guide
Control mnemonics Mnemonic Instruction Type DN Done Digital EN Enable Digital ER Error Digital FD Found Digital IN Inhibit Digital LEN Length Analog POS Position Analog UL Unload Digital For all programmable controllers except the fixed I/O SLC and the SLC 5/01: EM Empty Digital EU Enable Unloading Digital Addressing syntax for Allen–Bradley programmable controllers D–31
PID mnemonics Mnemonic Instruction Type Submember Range ADDR[] Address of Master Loop % Analog 0–3 BIAS Output Bias % Analog CA Control Action Digital CL Cascaded Loop Digital CT Cascaded Type Digital DATA[] Reserved / Internal Use Analog DB Deadband Analog DO Derivative Of Digital DVDB Deviation Alarm Deadband Analog DVN Deviation Alarm - Analog DVNA Deviation High Alarm Digital DVP Deviation Alarm + Analog DVPA Deviation Low Alarm Digital EN Enable Digital ER
Mnemonic Instruction Type MINS Setpoint Minimum Analog MO Mode Digital OLH Output Limit High Digital OLL Output Limit Low Digital OUT Output Analog PE PID Equation Digital PV Process Variable Analog PVDB Process Variable Alarm Deadband Analog PVH Process Variable Alarm High Analog PVHA Process Variable High Alarm Digital PVL Process Variable Alarm Low Analog PVLA Process Variable Low Alarm Digital PVT Process Variable Tracking Digital SO Set Output % Analog SP S
Message mnemonics Mnemonic Instruction Type AD Done Digital AE Error Digital CO Continuous Digital DATA[] Reserved / Internal Use Analog DLEN Done Length Analog DN Synchronization Done Digital EN Enable Digital ER Synchronization Error Digital ERR Error Code Analog EW Enable Waiting Digital NR No Response Digital RLEN Request Length Analog ST Start Transmission Digital TO Time Out Digital D–34 RSView32 User’s Guide Submember Range 0 – 51
Block transfer mnemonics Mnemonic Instruction Type CO Continue Digital DLEN Done Length Analog DN Done Digital ELEM Element Number Analog EN Enable Digital ER Error Digital EW Enable Waiting Digital FILE File Number Analog NR No Response Digital RGS Rack Group Slot Analog RLEN Requested Length Analog RW Read Writes Digital ST Start Digital TO Time Out Digital Token data mnemonics Mnemonic Instruction Type LO Low Analog HI High Analog Addressing syntax fo
SFC status mnemonics D–36 Mnemonic Instruction Type DN Done Digital ER Step Error Digital FS Forced Scan Digital LS Last Scan Digital OV Timer Overflow Digital PRE Preset Analog SA Scan Active Digital TIM Active Time Analog RSView32 User’s Guide
E Appendix Station addressing for nodes connecting to Allen–Bradley devices This appendix describes: local station addressing remote station addressing Local station addressing The following table lists valid address entries for a node connected to the same network as the RSView32™ system: Communication Channel Valid Entries DH 0 – 376 (octal) DH+™ 0 – 77 (octal) DH–485 0 – 31 (decimal) TCP/IP Host name (as described next) E–1
Host name When entering a host name, use one of the following: a direct IP (Internet Protocol) address in the form www.xxx.yyy.zzz where www, xxx, yyy, and zzz are numbers from 000 to 255 an alias for the address. An alias is an alphanumeric string from one to eight characters. The first character must be a letter and the name is case–sensitive. Remote station addressing This section outlines valid address entries for a node connected to a remote network.
DH and DH+ networks bridged by a 1785–KA The format of the station address for nodes on remote DH and DH+ networks is: Remote Network Station Address DH ll.sss DH+ Valid Entries lllocal bridge address 0 – 77 (octal) sssstation address on remote DH 0 – 376 (octal) ll.rrr.ss lllocal bridge address 0 – 77 (octal) rrrremote bridge address 0 – 376 (octal) ssstation address on remote DH+ 0 – 77 (octal) or ll.
Example: Bridging DH and DH+ networks The following figure shows an RSView32 system connected to a DH+ network with a KT–family card. The local DH+ network is bridged to a remote DH network, which is bridged to a second remote DH+ network. The 1785–KA interface modules are used to bridge the networks. The valid station entries for the various nodes in the figure are: E–4 Station Address Valid Entries 14 14 220 7.220 21 7.310.21 or 7.
Remote DH+ 21 10 PLC-5 1785-KA Remote DH 310 207 220 PLC-3 1785-KA Local DH+ 7 10 14 PLC-5 RSView32 with KT-family Card Station addressing for nodes connecting to Allen–Bradley devices E–5
DH+ and DH–485 networks bridged by a 1785–KA5 Only bridging from DH+ to DH–485 is supported. The format of the station address for nodes on the remote DH–485 network is: Station Address Valid Entries ll.ss lllocal bridge address 0 – 77 (octal) ssstation address on remote DH–485 0 – 37 (octal) Note: The 1785–KA5 link ID is not required for addressing. IMPORTANT Only Enhanced SLC™ 5/03 (OS 301) nodes are supported.
SLC 5/03 (OS 301) DH-485 10 (decimal) SLC 5/03 (OS 301) 14 (decimal) 11 (decimal) Link 1 1785-KA5 17 (octal) DH+ RSView32 with KT-family card PLC-5/60 7 (octal) Link 2 PLC-5/40 4 (octal) Multiple DH+ networks connected by a Pyramid Integrator The format of the station address for nodes on a remote DH+ network is: Station Address Valid Entries ll:rrrrr.
The Pyramid Integrator (PI) link number for each DH+ network must be unique. Use the 6200 Series Programming Software to configure link numbers. A PI chassis contains one RM module with two network channels. It can also contain up to four KA modules, each with two network channels. Using the RM and four KA modules, an RSView32 system can communicate with programmable controllers on any or all of 10 DH+ networks.
1 R K M A Bridge Address 2 2 3 3 4 5 6 7 E I PI Link 4 PI Chassis DH+ 10 PLC-5 PI Link 3 DH+ 23 PLC-5 PI Link 2 2 DH+ 3 PLC-5 PI Link 1 DH+ 12 11 PLC-5 RSView32 with KT-family card Station addressing for nodes connecting to Allen–Bradley devices E–9
DH and DH+ connected to a TCP/IP network by a Pyramid Integrator You can use a Pyramid Integrator (PI) with an Ethernet interface to route requests from a TCP/IP network to either DH or DH+ networks. The PI chassis will contain one RM module with two network channels and up to four KA modules, each with two network channels. Using the RM and four KA modules, an RSView32 system can communicate with programmable controllers on any or all of 10 DH or DH+ networks.
if connected on a KA, type: mKA:n where m is the pushwheel number (1 to 4) on the KA and n is the KA channel number (2 or 3). station_address is one of the following: Remote Network Station Address Valid Entries DH lll local station address 0 – 376 (octal) DH+ ll local station address 0 – 77 (octal) DH bridged by a 1785–KA module ll.
Example: Bridging to a TCP/IP network The figure on the following page shows an RSView32 system connected to a TCP/IP network through an Ethernet interface with a PI. The valid station entries for the nodes in the following figure are: Station Address Valid Entries 110 orion::1KA:2.110 17 orion::1KA:3.17 4 orion::ORM:2.4 14 orion::ORM:3.14 220 orion::ORM.3.7.220 21 orion::ORM:3.7.310.21 The name “orion” is a host name that maps to an IP address.
Orion 1 R K M A 2 2 3 3 E I RSView32 Ethernet DH 110 PLC-3 DH+ 17 PLC-5 DH+ 4 PLC-5 DH+ 7 14 PLC-5 1785-KA DH 207 310 220 PLC-3 DH+ 1785-KA 10 21 PLC-5 Station addressing for nodes connecting to Allen–Bradley devices E–13
F Appendix Importing and exporting XML files This appendix describes: exporting, editing, and importing XML files. the XML file structure for RSView32 graphics. About XML XML is the Extensible Markup Language used to create documents with structured text information. It has a standardized format and structure. You can use XML to edit the elements and attributes needed to create or to modify graphic displays.
To export graphic display information to an XML file 1. In RSView32, click the Project menu. 2. On the Project menu, click Graphics Import Export Wizard. 3. Follow the instructions in the wizard. For more information about using the Graphics Import Export Wizard, see the RSView32 online help. RSView32 creates XML files for the selected graphic displays, in the location you specify. Editing XML files To edit XML files, you can use Notepad or any XML editors.
Importing graphic XML file You can import one single graphic display XML file at a time. You can also choose whether to create a new display or update an existing display. To import graphic display information from an XML file 1. In RSView32, click the Project menu. 2. On the Project menu, click Graphics Import Export Wizard. 3. Follow the instructions in the wizard. For more information about using the Graphics Import Export Wizard, see the RSView32 online help.
F–4 Element Description Contains information of the display with encoded data. This section cannot be changed. Indicates the end of Data element. Contains attributes of the display which can be modified. Contains each attribute for the display. Only the attribute value can be modified. Indicates the end of Property element. Indicates the end of ReplaceableFields element.
Index Symbols ??? in input fields 11-43, 11-47, 11-65 .bmp files 11-108, 11-110 transparent background for 11-109 .clp files 11-108 .dbf files activity log 8-1, 8-10, 8-18 alarm log 6-8, 6-31 data log 7-1, 7-2 retrieving data from 16-3 .dxf files 11-108 .gif files 11-108 transparent background for 11-109 .jpg files 11-108 .mgl files 11-108 .mgx files 11-108 .obf files 7-9 .pcx files 11-108 .rsv files 1-1 .tif files 11-108 .wav files 6-35, A-21, A-45 .
contents of 8-19, 16-7 creating 8-5 deleting 8-9 exporting to ODBC 8-11 labeling categories in 8-14 logging destinations 8-14 maximum number of files 8-10 maximum number of records 8-19 naming 8-10 short file names 8-5 sharing at runtime 17-2 storage format ODBC 16-8 storing in version 6.
sharing at runtime 17-2 storage format ODBC 16-11 storing in version 6.0 format 6-25 Alarm Log Viewer 6-9, 6-53 Alarm logging.
Animation dialog box 12-4 Animation types 12-1 color 6-11, 12-13 fill 12-19 height 12-24 horizontal position 12-20 horizontal slider 12-30 OLE verb 10-10, 12-32 rotation 12-26 touch 12-28 vertical position 12-21 vertical slider 12-31 visibility 6-11, 12-12 width 12-22 Application commands AppAbort A-20 AppActivate A-20 AppStart A-20 Applications Windows A-20 sharing data with 16-1, 16-3 Arc graphic object 11-32 Arithmetic operators 14-10 Arrow graphic object 11-55
startup and shutdown 11-23 using with alarms 6-14 Communications DDE configuring 3-1 devices 2-1, 2-2 direct driver configuring 2-1 errors 2-13, 14-15 logging 2-20, 8-14 monitoring 2-20, B-2 OPC configuring 3-1 setting up without hardware or software ControlView differences from RSView32 C-1 features no longer supported C-8 importing projects into RSView32 C-1 Counter mnemonics D-30 Crystal Reports 7-1, 8-1 C-Toolkit C-9 Ctrl-key combinations disabling 10-16, 18-5 Current {T
7-14 Data logging commands DataLog A-22 DataLogChangeRate A-23 DataLogMergeToPrimary 7-26, A-23 DataLogNewFile 7-31, A-24 DataLogOff 7-45, A-24 DataLogOn 7-44, A-24 DataLogPath 7-42, A-25 DataLogRenameFile A-25 DataLogSnapshot 7-38, 9-1, A-25 DataLogSwitchBack 7-25, A-26 Data source for tags 4-3, 4-19 Data types for tags 4-16 Database command A-22 Database Import & Export Wizard 4-22, 4-27, 4-28 DatabaseSync command A-22 dBASE IV. See .
secondary 2-10 selecting 2-6 setting up 2-3 setting up tags for 4-20 switching at runtime 2-11 Disk space monitoring 6-29 Display cache 11-16, 15-4 Display command 15-3, A-29 and events 9-1 and graphic displays 11-20, 11-22, 11-28 and key lists 12-58 and parameter files 11-38, 11-40 and trends 13-26 Display editor.
Execute button in alarm summaries 6-14, 6-68 Execute command 6-14 Exporting activity log to ODBC 8-11 alarm log to ODBC 6-32 Expressions 14-1 alarm events in 6-21 and animation 12-8 built-in functions in 14-14 constants in 14-9 copying 14-4 creating 14-3 formatting 14-6 if-then-else logic in 14-25 in activity logging 8-8 in alarms 6-15 in data logging 7-38 in derived tags 5-6 in events 9-5 in the = (Equal) command 14-6, A-8 operators in 14-10 evaluation order of 14-
G GE programmable controller 3-15 Global key commands Key 15-22, A-39 KeyEdit A-40 Global keys 15-5 creating 15-19 differences from ControlView C-6 precedence among key types 15-14 running a key file 15-22 on startup 18-7 Global Keys editor 15-20 Graphic display commands Abort 15-3, A-9 Display 15-3, A-29 and events 9-1 and key lists 12-58 and parameter files 11-38, 11-40 caching 11-28, 13-26 positioning 11-22 sizing 11-20 Download 11-48, 11-66, A-33 DownloadAll 11-4
alarm summary 6-10, 6-55 arcs 11-32 arrows 11-55 buttons 11-57 circles 11-30 electronic signature button 11-78, 11-79 ellipses 11-30 freehand 11-32 labels 11-54 lines 11-30 numeric display fields 6-11, 11-50 numeric input fields 11-42 OLE objects 10-10, 11-69 polygons 11-31 polylines 11-31 recipe fields 11-61 rectangles 11-30 simple objects 11-28 squares 11-30 string display fields 6-11, 11-50 string input fields 11-42 tag monitor 4-30 text 11-33 trend 13-5 we
and string input objects 11-46 Input field commands Display /U parameter A-30 Download 11-48, 11-66, A-33 DownloadAll 11-48, 11-66, A-33 NextPosition 12-45, A-43 Position 12-45, A-45 PrevPosition 12-45, A-46 SendKeys A-54 Upload 11-48, 11-67, A-60 UploadAll 11-49, 11-67, A-60 Input fields creating numeric 11-42 recipe 11-61 string 11-42 downloading values from 11-42, 11-47 highlight enabling or disabling 11-25 question marks in 11-43, 11-47, 11-65 specifying behavior for 11
MacroEdit command A-41 Macros 15-7 attaching to ActiveX events 12-39 creating 15-7 login and logout 10-15 startup and shutdown 11-23, 15-11, 18-7 using the Command Wizard A-5 nesting 15-10 precedence of 15-7, A-4 securing 10-6 using commands in 15-8 using in events 9-1 using in graphics 12-7 using parameters in 15-10 using to identify alarms 6-15 Memory tags 4-3, 4-21 Messages See also Alarm messages clearing in activity bar 8-17 mnemonics D-34 number of on a channel 2
O NodeEnable 3-16, A-43 NodeSwitch 3-16, A-44 RTDataServerOff A-52 RTDataServerOn 16-26, 17-6, A-52 RTDataWriteDisable A-53 RTDataWriteEnable 16-29, 17-6, A-53 OPC nodes assigning to tags 4-20 changing at runtime 3-16, A-44 creating 3-5, 17-8 enabling and disabling 3-7 Object keys 15-5 creating 12-42 editing 12-56 key list 12-44, 12-58 precedence among key types 15-14 Object Smart Path 12-6, 12-9 ODBC data logging.
among global, object, and display keys 15-14 and the F1 key 15-15 embedded ActiveX objects 15-15 embedded OLE objects 15-16 reserved keys 15-17 PrevPosition command 12-45, A-46 PrevWindow command A-46 Primary drivers 2-10 PrintDisplay command 11-114, A-46 Printers selecting 1-10 Programmable controllers E-8 See also PLC PLC addressing syntax D-2 SLC addressing syntax D-12 SoftLogix 5 addressing syntax D-26 Project commands ProjectHide A-48 ProjectRun A-48 ProjectShow 10-
RSLinx 2-4, 2-5 and DDE 16-30, A-27 and OPC 3-1, 3-11 setting up direct driver communications with 2-4 RSLinx Gateway and OPC 17-9, 17-10 RSView32 commands A-1 See also Commands, Individual command entries RSView32 Resource Kit RegConfig tool 6-16 RSView32 tools ControlView Project Import Wizard C-1 Logix 5000 Tag Import utility 4-27 Project Documentor 1-11 Project Transport Wizard 1-12 Win2K XP DeskLock 10-17, 18-4 RTDataServerOff command A-52 RTDataServerOn command 16-26, 17-
Silence command A-57 SilenceAll command A-57 SLC 5 (Enhanced) addressing syntax C-8, D-19 SLC 5 addressing syntax C-8, D-12 SoftLogix 5 2-3, 2-9, 2-16 addressing syntax D-26 Special keys Alt-F4 18-5 Alt-Shift-Tab 18-5 Alt-Tab 18-5 arrows, using with graphic objects 11-92 Ctrl copying objects with 11-88 drawing objects with 11-30, 11-31, 11-32 resizing objects with 11-92 rotating objects with 11-10 selecting objects with 11-8 Ctrl-Alt-P 10-16, 18-5 Ctrl-F6 A-43 Ctrl-PgDn
using for memory tags 4-22 Database A-22 DatabaseSync A-22 Monitor A-42 Ramp A-49 Set 4-22, 9-1, A-55 Toggle A-59 Tag Database editor 4-5, 6-22, 6-42 Tag folders 4-7 Tag Monitor editor 4-30 Tag monitor graphic object 2-21, 4-29 Tag placeholders 11-36, 12-6 creating 11-38 parameter for Display command A-31 replacing by listing tag names 11-40 replacing using a parameter file 11-38 using in commands A-32 using in expressions 14-8 using in trends 13-19 using the {tag] para
y-axis.
