Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation
Technologies, Inc. is strictly prohibited. Please refer to the license agreement for details.
Allen-Bradley, ControlLogix, FactoryTalk, Rockwell Automation, Rockwell Software, RSLinx, RSView and the
Rockwell Software logo are registered trademarks of Rockwell Automation, Inc.
The following logos and products are trademarks of Rockwell Automation, Inc.:
AdvanceDDE, ControlView, Data Highway Plus, DH+, RSView32, RSView32 Resource Kit, and WINtelligent.
FactoryTalk Activation, FactoryTalk Live Data, and FactoryTalk Transaction Manager.
RSLinx Classic, SLC 5, SLC 500, and SoftLogix.
ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe, Windows,
Windows ME, Windows NT, Windows 2000, Windows Server 2003, Windows XP, and Windows Vista are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA).
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
OLE for Process Control (OPC) is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.
This product is warranted in accordance with the product license. The product’s performance may be affected by
system configuration, the application being performed, operator control, maintenance, and other related factors.
Rockwell Automation is not respon sible for these interv ening factors. The instructions in this document do not cover
all the details or variations in the equipment, procedure, or process described, nor do they provide directions for
meeting every possible contingency during installation, operation, or maintenance. This product’s implementation
may vary among users.
This document is current as of the time of release of the product; however, the accompanying software may have
changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this
document or the software at anytime without prior notice. It is your responsibility to obtain the most current
information available from Rockwell when installing or using this product.
i
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? ............................................................................................. 1-1
Thank you for choosing RSView32™. RSView32 is an integrated
package for developing and running automation applications.
Designed for use with Microsoft
Edition
Pack 1 or later, Windows 2000 Server with Service Pack 4 or Windows
2000 Professional with Service Pack 4, and Windows Vista Business
with Service Pack 1 or later (32-Bit) or Windows Vista Home Basic
with Service Pack 1 or later (32-Bit), Windows 7 Professional and
Windows Server 2008 Standard Edition, RSView32 gives you all the
tools you need to create effective monitoring and supervisory control
applications.
with Service Pack 2, Windows XP Professional with Service
About the documentation
The RSView32 documentation set includes:
Getting Results with RSView32: A quick start guide to get you up and
running with RSView32.
RSView32 User’s Guide: Comprehensive information about RSView32,
procedures for creating and running an automation application, and
reference information.
®
Windows® Server 2003 R2 Standard
RSView32 Runtime User’s Guide: Information on how to install, start,
and use RSView32 Runtime.
Help: Online procedures and reference information.
Release Notes Additional information about RSView32. Read this file
before you begin working with the software.
P–1
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.
When you call
When you call, be at your computer and ready to give the following
information:
the product serial number
You’ll find this number on the Activation disk label and in the help
About dialog box that you access from the RSView32 Project
Manager.
the product version number
the type of hardware you are using
the exact wording of any messages that appeared on your screen
a description of what happened and what you were doing when the
problem occurred
how you tried to solve the problem
P–2 RSView32 User’s Guide
Chapter
1Working 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 .rsv file contains general project information such as a list of
project components and their directory locations and version
numbers. By default, all project components are located locally in
folders under the project folder, but they can also be located in other
directories or on other computers.
1–1
Project files
The following table lists the RSView32™ folders and the types of files
they contain.
FolderContentsFile
extensions
Project nameRSView32 project file, system files, and
.rsv
the folders described below
System files: User accounts
Security command list
.act
.sec
ActlogActivity log files.dbf
AlmlogAlarm log files.dbf
AlsAlarm summary files.als
Cab
ActiveX
®
control setup files
.cab
CacheRSView32 internal files.ctl, .dat, .idx
ComprfInternal information on channels,
.csv, .ctl
nodes, and scan classes
DlglogData log models
Data log files
Information for current file set
Information for historical file sets
.mdf
.dbf
.dns
.dlg
DtsDerived tag files.dts
EdsEvents files.eds
GfxGraphic display files.gfx
KeyGlobal key files.key
McrMacro files.mcr
ParParameter files.par
RcpRecipe files.rcp
TagTag database files
1–2 RSView32 User’s Guide
Tag cache file
.db, .ctl, .dat
.cac
FolderContentsFile
Project name
Component
TgsTag monitor files.tgs
VbaVBA program files.vba
Working in the Project Mana ger
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.
extensions
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. As you create project components, they are
displayed in the right pane.
Working with projects 1–3
Component
The path to the
selected
component . . .
This is a
shortcut to a
component that
is not in the
default project
directory.
. . . is displayed in the status bar.
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.
1–4 RSView32 User’s Guide
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. Instead, you are creating a link to the file’s location outside of
the project. The advantage of using this option is that there is only one
copy of the file, and changes made to it are available to all projects
using the file. The disadvantage of using this option is that it is more
difficult to copy or move projects, because the files are not all located
in the same place.
If you copy a component into a project using My Computer,
Windows
to the project using the Copy Existing Component into Project
option. Instead, use the Create Shortcut to Existing Component
option to add the component to the Project Manager.
®
Explorer, or File Manager, you cannot add the component
When you highlight the component in the right pane of the Project
Manager, the path to the file is displayed in the status bar. Files that are
located outside of the project have an arrow symbol on the
component icon, as shown above for the Detail component.
If you move or delete a file using My Computer, Windows Explorer,
or File Manager, the file reference is broken and the component name
is greyed out in the Project Manager until the file reference is updated.
To update the file reference, use either the Copy Existing Component
into Project option or the Create Shortcut to Existing Component
option.
Working with projects 1–5
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.
Click and Shift-click to select a group of components, or Ctrl-click
to select multiple individual components.
4. Click Open. The components appear in the right pane of the
Project Manager.
Renaming, removing, and deleting components
Use the items on the context menu to rename, remove, and delete
components. The Remove item removes a component from the
Project Manager. The Delete item deletes a component and its
associated file from disk.
1–6 RSView32 User’s Guide
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.
Working with projects 1–7
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.
Deleting a component and file
If you no longer want to use a particular file in any project, you can
delete the component and its associated file using the Delete item on
the context menu. Deleting a component deletes both the file
reference and the physical file from disk.
To delete a component and file:
1. Select the component in the right pane of the Project Manager.
2. Right–click and then click Delete.
Naming files
RSView32 supports long file names. File names, including the path,
can be up to 200 characters long. For example, the following path and
file name contains 30 characters:
C:\Bakery1\Gfx\Bakery Overview
1–8 RSView32 User’s Guide
Printing
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. When using file names with spaces in
commands, you do not need to enclose the file names in double
quotes (“ ”) except when using the /P parameter with the Display
command. For details about commands, see Appendix A, RSView32 commands.
Each RSView32 editor has a Print item on its File menu.
To print selections:
1. Select the item you want to print. The item can be a record in an
editor’s spreadsheet or it can be an object in a graphic display.
2. On the File menu, click Print.
3. Under Print Range, click Selection.
4. Click OK.
To print the entire contents of the window:
1. On the File menu, click Print.
2. Under Print Range, click All.
3. Click OK.
Working with projects 1–9
Selecting a printer
IMPORTANT
You can select only a printer that has been installed on your system.
For information on installing a printer, see your Windows
documentation.
The settings in the Print Setup dialog box do not affe ct 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.
1–10 RSView32 User’s Guide
2. If you don’t want to use the default printer, specify another printer.
3. Choose the appropriate orientation and paper options.
4. Click OK.
Selecting printer setup options
For detailed information about printer options, refer to your Windows
documentation.
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. For example, create a button
object, display key, or global key with the PrintDisplay command as
the press action, or provide a command line in the graphic display. For
more information about creating graphic displays, see Chapter 11,
Creating graphic displays.
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.
Using the Project Documentor
The Project Documentor is a utility that provides you with detailed
information on RSView32 projects. This utility is a browser that allows
you to view the contents of the project’s components and the tags used
in these components. You can also print and export the information.
For more information, see the Project Documentor Help, included on
the RSView32 Resources CD-ROM, and also available from the
RSView32 Tools menu on the Windows Start menu.
Working with projects 1–11
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.
1–12 RSView32 User’s Guide
Chapter
2Setting up direct driver
communications
RSView32™ uses a direct connection to the drivers in RSLinx® to
®
communicate with most Allen–Bradley
SoftLogix
driver communications.
™
5 devices. This chapter describes how to set up direct
devices, as well as
You can also use DDE (Dynamic Data Exchange) or OPC
Process Control) to connect to third-party devices or servers, as
described in Chapter 3, Setting up OPC and DDE communications.
You must use an OPC or DDE connection to handle unsolicited
messages and to communicate with the PLC–5
®
ControlLogix
messages see RSView32 Technical Notes on the RSView32 Tools
menu.
5550 device.For instructions on using unsolicited
®
/250 or
Overview of direct driver communications
Communication through direct drivers involves:
channels
communication devices
communication driver software (RSLinx)
nodes (control devices)
®
(OLE for
2–1
The following illustration shows an RSView32 station and its channel
r
RSView32
Communication
channel
Nodes
Programmable controll
Network
Programmable controller
and nodes.
Programmable controlle
Communication channel
2–2 RSView32 User’s Guide
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. You can use internal devices, such as the 1784–KT/
KTX, or you can use external devices connected through the serial
port.
Communication driver
IMPORTANT
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. This is done by scanning its nodes.
Setting up direct driver communication to
programmable controllers
The instructions below summarize the steps for connecting to Allen–
Bradley or SoftLogix 5 devices.
You cannot connect to an Allen–Bradley PLC–5/250 or
ControlLogix 5550 using direct drivers. To connect to these types of
programmable controllers, use OPC- or DDE–based
communications as described in Chapter 3, Setting up OPC andDDE communications.
Setting up direct driver communications 2–3
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.
Summary of steps
Follow the steps below to set up direct driver communication with
Allen–Bradley or SoftLogix 5 programmable controllers.
1. Start RSLinx. Configure and load the appropriate communication
driver.
2. Start RSView32 and create or open a project.
3. In the Channel editor, select a channel and assign the appropriate
4. In the Node editor, create nodes for each programmable controller
2–4 RSView32 User’s Guide
network type to it.
In the Primary Communication driver field, assign a driver to the
channel. If you do not have drivers loaded, click None Loaded.
For details, see “Configuring channels” on page 2-7.
you wish to communicate with.
For details, see “Creating a node” on page 2-13.
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.
Configuring RSLinx drivers
RSLinx drivers provide a direct connection between RSView32 tags
and Allen–Bradley or SoftLogix 5 programmable controllers. For
details about configuring any of the RSLinx drivers, see your driver
documentation.
You can also use RSLinx with OPC and DDE communications, as
described in Chapter 3, Setting up OPC and DDE communications. You
must use an OPC or DDE connection to handle unsolicited messages
and to communicate with the PLC-5/250 or ControlLogix 5550
device.For instructions on using unsolicited messages see RSView32
Technical Notes on the RSView32 Tools menu.8.
Setting up direct driver communications 2–5
Using the drivers
IMPORTANT
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.
You must use the version of RSLinx that came with your RSView32
software. This version has been tested for compatibility with
RSView32. Other versions may not function correctly.
Selecting a driver in RSView32
To select a driver in RSView32, the driver must first be configured in
RSLinx. All configured drivers appear in the RSView32 Channel
editor Primary or Secondary Communication Driver fields.
If the Channel editor is open when you add a driver in RSLinx, close
the Driver list by clicking another part of the editor, and then re–open
the list.
2–6 RSView32 User’s Guide
Configuring channels
Define up to four different communication channels.
Specify the
type of
network you
are using.
When you
select a
network type,
these fields
become active.
Click here
to display
the list of
drivers for
the
selected
network
type.
Define up to four
different
communication
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
Setting up direct driver communications 2–7
3. Select a channel and fill in the following information:
Network Type
Using the following table as a guide, select a network type:
ToSelect
Communicate with programmable controllers on a
ControlNet network
Communicate with programmable controllers on local
or remote DH networks
Communicate with programmable controllers on local
™
or remote DH+
networks
or
Communicate with SLC
™
controllers on remote DH–
485 networks
or
Connect to Channel 0 of an Enhanced PLC
Communicate with SLC controllers on local DH–485
networks
or
Connect to an SLC with an RS–232 port
Communicate with Ethernet
®
programmable
controllers directly connected to the TCP/IP network
ControlNet
DH
DH+
DH–485
TCP/IP
2–8 RSView32 User’s Guide
or
Communicate with SoftLogix 5 controllers
or
Communicate with SLC 5/05 controllers
ToSelect
IMPORTANT
Communicate with programmable controllers through
the Ethernet interface of a Pyramid Integrator
RSLinx Gateway
Not use a channel
or
Clear a channel configuration
™
, or
TCP/IP
Bridge
None
Loaded
To set a configured channel’s network type to None Loaded, first
issue the ComStatusOff command. Because setting a configured
channel’s network type to None Loaded deletes all the comstatus
system tags from the tag database, you cannot set a configured
channel’s network type to None Loaded if the ComStatusOn
command has been issued.
Of the four communication channels you can co nfigure, only
one can be configured for TCP/IP. For example, you cannot
configure one channel for TCP/IP and another for a TCP/IP
bridge.
To run a SoftLogix 5 controller with RSLinx and RSView32,
configure the TCP/IP channel and use the SOFT5 driver or the
AB_ETH driver.
For the SOFT5 driver, when configuring the SoftLogix 5 driver in
RSLinx, enter the IP address or UNC name of the SoftLogix 5
controller in the Internet Address Mapping table.
If the SoftLogix 5 controller is not running on the same computer
as RSLinx, the Windows
®
XP, Windows 2000 user account that is
running RSLinx must be a member of the SoftLogix
Administrators group on the SoftLogix 5 computer.
For the AB_ETH driver, when configuring the Ethernet driver in
RSLinx, enter the IP address of the SoftLogix 5 controller in the
Internet Address Mapping table. You must also enable the
WinSock TCP/IP driver in SoftLogix 5.
Setting up direct driver communications 2–9
Messages
IMPORTANT
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.
Primary and Secondary Communication Drivers
The primary driver is the one your system will use most of the
time. By default, this driver is the active driver. The secondary
driver is a backup. Primary and secondary drivers must use the
same network type.
Do not select a secondary communication driver for TCP/IP or
TCP/IP Bridge channels. To create communications
redundancy, use a second Ethernet card and co nfigure each
card uniquely in Windows. Then use the NodeSwitch command
at runtime to change the IP number if communication errors are
detected.
2–10 RSView32 User’s Guide
To specify a driver, select the appropriate driver from the list. This
list contains the drivers installed and running in RSLinx that are
valid for the selected network type.
To configure communications without the appropriate hardware or
software installed, select None Loaded as the driver.
To test your project without the appropriate hardware installed, see
“Developing your project without a communication network” on
page 2-22.
For details about configuring drivers, see “Configuring RSLinx
drivers” on page 2-5.
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.
Changing the channel configuration
To change the channel configuration once nodes have been
assigned—for example, to move a project from a computer using
DH+ to a computer using TCP/IP—create a new channel of the
correct type. Re–assign the channel number for each node, then delete
the original channel configuration.
Switching communication drivers at runtime
If the primary network fails at runtime, your system can switch to a
driver on a pre–defined secondary network. You can set up your
project so drivers switch automatically, or so operators manually
switch the drivers.
Setting up direct driver communications 2–11
Commands for switc h ing drivers
Use the following commands to switch drivers:
DriverPrimary <channel>
Switches from the secondary driver to the primary driver on the
specified channel.
<channel>The number of the channel (1 through 4) that is
being switched from its secondary to primary driver.
DriverSecondary<channel>
Switches from the primary driver to the secondary driver on the
specified channel.
<channel>The number of the channel (1 through 4) that is
being switched from its primary to secondary driver.
DriverToggle<channel>
Switches from the current driver to the one not being used on the
specified channel.
<channel>The number of the channel (1 through 4) that is
Switching drivers automatically
To switch drivers automatically, create an event in the Events editor. In
the Action field of the Events editor, type a driver command as the
action that will be triggered when an expression results to true. In the
Expression field, create an expression that will trigger the action.
2–12 RSView32 User’s Guide
being switched from one driver to another.
Example: An event for switching drivers
In the Events editor, use the following:
ActionDriverToggle 1
Expressioncomm_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. When the operator activates the button, the driver
on the specified channel is switched.
displaying a command line. When the operator enters a driver
Creating a node
A node allows you to assign a logical name and an address to each
programmable controller that RSView32 will communicate with. Each
programmable controller is then referred to throughout RSView32 by
this name. The node name carries all its configuration information, so
attributes such as type of programmable controller, station number,
and network type need not be repeated.
command on the command line, the driver on the specified
channel is switched.
Setting up direct driver communications 2–13
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.
For details about the OPC Server and DDE Server data sources,
see Chapter 3, Setting up OPC and DDE communications.
Name
Type a name of your choice up to 40 characters long. This name
represents the programmable controller. The name can have upper
2–14 RSView32 User’s Guide
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.
When a tag uses a disabled node at runtime, the tag’s state will
change from valid to disabled. A tag’s state can be seen by viewing
the tag in the tag monitor.
To disable nodes, clear the Enabled check box.
You can also enable and disable nodes at runtime, using the
NodeEnable and NodeDisable commands. For more information
see Appendix A, RSView32 commands.
Channel
Select the channel number on which this node resides.
Station
Type the station address of the programmable controller. For
addressing syntax, see Appendix E, Station addressing for nodes connecting to Allen–Bradley devices.
If RSLinx 2.0 or later is installed and running on your computer,
click the ... button next to the Station field to open the RSWho
window that displays all active PLC stations for the selected
channel. When you select a station from the RSWho window, the
Station and Type fields are filled in automatically. RSView32
substitutes PLC-5 (Enhanced) for all PLC-5 series device types.
Change the entry in the Type field to PLC-5 if you are using the
PLC-5/10, 5/12, 5/15, or 5/25.
Setting up direct driver communications 2–15
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.
To communicate with a SoftLogix 5 device you must use an
RSLinx driver and a TCP/IP channel.
Timeout
Type the number of seconds you want RSView32 to wait before
reporting a communication error. A timeout period of three
seconds is usually enough.
4. Click Accept to save the node configuration.
5. When you finish configuring nodes, click Close.
2–16 RSView32 User’s Guide
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 <node name> <station>
<node name>The name of the node that you want to change to
another programmable controller address.
<station>For device nodes, the physical address for the
programmable controller you want to change to.
When you use the NodeSwitch command to change a node’s address,
the change appears in the Node editor’s spreadsheet. If the Node
editor is open when you use the command, the change will not appear
until you have refreshed the display by closing and re–opening the
editor.
You can also enable and disable nodes at runtime, using the
NodeEnable and NodeDisable commands. For more information see
Appendix A, RSView32 commands.
Scanning for new tag values
When your RSView32 project is running, it must periodically update
its tag values in the value table. This is done by scanning.
For projects communicating through direct drivers, values are updated
by scanning the programmable controller address at the foreground
and background scan rates specified by the scan class.
Setting up direct driver communications 2–17
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. The background period applies to any
component that performs a continual background activity, such as
derived tags, events, alarms, and data log.
If the same tag is used by both a foreground and background
component, the tag is scanned at the faster period. If a value is not
required by a foreground or background component, its address is not
scanned, greatly reducing system overhead.
Guidelines for configuring scan classes
Set foreground scan periods to be shorter than or equal to
background scan periods.
A scan period of zero means scan as quickly as possible. You can
set foreground scan periods to zero, but never set background scan
periods to zero. For foreground periods, using zero is not
recommended because this setting can result in so much traffic
that overall system communication slows down.
Set scan periods for optimal efficiency. Specify a frequent scan rate
for tags representing fast–moving devices and a less frequent scan
rate for tags representing devices that change less often.
This approach optimizes system performance, providing high–
speed scanning where required and using less frequent scanning,
which saves system resources, where acceptable.
2–18 RSView32 User’s Guide
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. Open the Scan Class editor by doing one of the following:
double–click the Scan Class icon
right–click the Scan Class icon and then click Show
Setting up direct driver communications 2–19
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. You can use fractional seconds.
For example, if you type .6 the address is scanned every six tenths
of a second.
4. To save the configuration for a scan class without closing the
editor, select another scan class.
5. When you finish configuring scan classes, click OK.
Monitoring communications
Use any of the following methods to monitor communications:
Activities—In the Activity Log Setup editor, ensure
communication errors, warnings, and remarks are enabled and are
set up to log to the log file and activity bar. At runtime,
information appears in the log file and activity bar, indicating any
problems.
Communication status—Ensure communication status is turned
on, otherwise communication errors will not be logged to the
activity log file or activity bar (even if they have been configured to
do so in the Activity Log Setup editor). By default, communication
status is turned off until you run the project. To turn
communication status on, use the ComStatusOn command.
2–20 RSView32 User’s Guide
Tag monitor—Use the tag monitor to check the communication
status for a device tag. The states are:
Disabled if the node has been disabled in the Node editor or
disabled 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
None if there is a problem with the tag definition such as it is
not a valid tag type or if the tag database has been accessed with
a third–party tool such as Microsoft
®
Access. If the underlying
tag type is valid, editing and saving the tag and then redisplaying
the tag monitor will fix the problem.
System\com tags—Use the system\com tags to receive a more
detailed error message. If the tag monitor reports an error, move
to an empty cell in the tag monitor, type system\com* and, when
the dialog box appears, click Select All. For a complete list of
system\com tags, see Appendix B, System tags.
Setting up direct driver communications 2–21
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.
Using the None Loaded driver type allows you to add or change
tags without causing communication errors.
To set a configured channel’s network type to None Loaded, first
issue the ComStatusOff command. Because setting a configured
channel’s network type to None Loaded deletes all the comstatus
system tags from the tag database, you cannot set a configured
channel’s network type to None Loaded if the ComStatusOn
command has been issued.
4. Disable the node by clicking the Enabled check box to deselect it.
2–22 RSView32 User’s Guide
Chapter
3Setting 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
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.
If you will be connecting to communication devices using direct
drivers, see Chapter 2, Setting up direct driver communications.
OPC servers provide a way to connect an RSView32 station (the OPC
client) to:
™
to
communication devices, using RSLinx
For details, see the topics in this chapter.
third-party communication devices, using vendor-specific or third-
party OPC servers (such as KEPServerEnterprise
Modicon
For details, see the topics in this chapter.
®
)
®
as an OPC server
™
, Siemens, or
3–1
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.
a third–party application with OPC server support, either on the
same computer or on a network
For details about connecting to third–party applications on the
same computer, see “Sharing tag values locally” on page 16-26. For
information about connecting to third-party applications on a
network, see “Connecting to RSLinx Gateway as a remote OPC
server” on page 17-9.
DDE servers provide a way to connect an RSView32 station (the
DDE client) to:
communication devices such as Siemens or Modicon
a third–party DDE server such as Microsoft
3–2 RSView32 User’s Guide
For details, see the topics in this chapter.
®
Excel or Visual
®
Basic
For details about connecting to third–party applications on the
same computer, see “Sharing tag values locally” on page 16-26.
Overview of OPC communications
RSView32
RSView32 OPC client module
Third-party
OPC server
Third-party
application
with OPC
server
support
Non-Allen-Bradleyprogrammable controller
Non-AllenBradley
device
Remote
computer *
RSView32
OPC server
RSServer
PLC networkNetwork or
third-party communication link
Remote
computer *
RSLinx
Gateway
(OPC server)
Remote
computer *
3rd-party
OPC server
OPC network link via
DCOM
Computer running RSView32
RSView32
RSView32 OPC client module
RSServer
Third-party
OPC server
Non-AllenBradley
®
programmable
controller
–
–
–
Network or
third-party
communication
link
The following illustration shows the different ways RSView32 can use
OPC for communications.
2
3
w
e
i
V
S
R
g
n
i
n
n
u
r
r
e
t
pu
om
C
Setting up OPC and DDE communications 3–3
Overview of DDE communications
RSView32
RSView32 DDE module
Third-party
DDE server
CF_Text or
AdvanceDDE
*
AdvanceDDE
CF_Text or
XLTable
Modicon,
GE, Siemens,
or other
programmable
controller
Other
non-AllenBradley
device
Third-party application, such as Microsoft Excel
* The third-party server can use AdvanceDDE format if
the server uses the Rockwell Software server toolkit.
RSServer
PLC network
Network or communication link
Computer running RSView32
RSView32
TM
*
Third-party
application,
such as
Microsoft
Excel
RSServer
Third-party
DDE server
Network or
communication link
The following illustration shows the different ways RSView32 can use
DDE for communications.
2
3
w
e
i
V
S
R
g
n
i
n
n
u
r
r
e
t
pu
om
C
3–4 RSView32 User’s Guide
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. In the Tag Database editor, create tags and select Device as the
data source and assign the nodes that you have created.
For details, see Chapter 4, Creating tags.
Creating an OPC node
An OPC node allows you to assign a logical name, server name, and
update rate for each OPC server you want to communicate with. The
OPC node name can then be used throughout RSView32.
Setting up OPC and DDE communications 3–5
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:
3–6 RSView32 User’s Guide
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.
For details about the DDE Server data source, see “Creating a
DDE node” on page 3-12. For details about the Direct Driver data
source, see Chapter 2, Setting up direct driver communications.
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. 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 device.
When a tag uses a disabled node at runtime, the tag’s state will
change from valid to disabled. A tag’s state can be seen by viewing
the tag in the tag monitor.
To disable nodes, clear the Enabled check box.
You can also enable and disable nodes at runtime, using the
NodeEnable and NodeDisable commands. For more information
see Appendix A, RSView32 commands.
Server
Do one of the following:
Click ... beside the Name field and select a server from the list
of registered servers. RSView32 fills in the remaining Server
fields.
To use another RSView32 station as your OPC server, select
RSI.RSView32OPCTagServer. Select Remote as the Type, and
specify the Server Computer Name or Address as described
next.
Setting up OPC and DDE communications 3–7
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:
<Vendor>.<DriverName>.<Version>
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.
Local if the server is an .exe file running on the same
computer as the OPC client.
Remote if the server is an .exe file running on a different
computer connected to the OPC client computer via a
network.
3–8 RSView32 User’s Guide
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 syntaxFor this
format
\\ComputerNameUNC
Example
\\DTB1
(Universal
Naming
Convention)
ComputerName.Domain.comDNS (Domain
DTB1.NET2.COM
Name System)
XXX.XX.XXX.XXXRaw TCP/IP
134.87.167.148
address
You set up the computer’s name or address in the Windows
®
Control Panel, as described in “Identifying the RSView32
server computer” on page 17-6.
For more information about IP (Internet Protocol) addresses,
see page E-10.
Setting up OPC and DDE communications 3–9
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.
For information about the syntax for the access path, see your
OPC server documentation.
If you use this field, and you are communicating with RSView32
using OPC, the access path is the name of the current project on
the server.
If you use this field, and you are communicating with an RSLinx
OPC server, the access path is the name of a DDE/OPC topic on
the server. If you leave the access path blank, you must specify the
DDE/OPC topic as part of the tag’s address when you create the
tag using the Tag Database editor.
Update Rate
Specify the fastest rate at which the OPC server sends data to the
OPC client. The default is every 1 second.
The rate that the OPC server uses may be slower than the rate you
specify. Type 0 to specify that the server use the fastest possible
rate.
If the OPC server’s access path is a DDE/OPC topic, the update
rate should not be faster than the topic poll rate.
4. Click Accept to save the node configuration.
3–10 RSView32 User’s Guide
5. When you finish configuring nodes, click Close.
The server name appears in the spreadsheet's Station or Server column.
Some columns do not apply to OPC
nodes and are left blank.
The server
name appears in
the
spreadsheet’s
Station or
Server column.
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.
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.
Setting up OPC and DDE communications 3–11
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.
Creating a DDE node
A DDE node allows you to assign a logical name for each DDE
application and topic you wish to communicate with. The DDE node
name can then be used throughout RSView32.
3–12 RSView32 User’s Guide
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.
For details about the OPC Server data source, see “Creating an
OPC node” on page 3-5. For details about the Direct Driver data
source, see Chapter 2, Setting up direct driver communications.
Setting up OPC and DDE communications 3–13
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. 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 device.
When a tag uses a disabled node at runtime, the tag’s state will
change from valid to disabled. A tag’s state can be seen by viewing
the tag in the tag monitor.
To disable nodes, clear the Enabled check box.
You can also enable and disable nodes at runtime, using the
NodeEnable and NodeDisable commands. For more information
see Appendix A, RSView32 commands.
Application
Type the name of the DDE server or other Windows application
that RSView32 will communicate with. For example, if Microsoft
Excel is the server, type Excel.
Topic
Type the subject of the DDE communication. For example, if
Excel is the application, the topic is a particular Excel spreadsheet.
4. Click Accept to save the node configuration.
5. When you finish configuring nodes, click Close.
3–14 RSView32 User’s Guide
Example: Configuring a DDE node
The application and topic appear in the spreadsheet's Station or Server column, separated by a vertical bar.
Some columns do not apply to DDE
nodes and are left blank.
The application
and topic appear in
the spreadsheet’s
Station or Server
column, separated
by a vertical bar.
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. The
CPU ID is CPUID1, the connection ID is PORT5, and the poll rate
is 10.
Setting up OPC and DDE communications 3–15
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 <node name> <parameter>
<node name>The name of the node that you want to change to
another server.
<parameter>One of the following:
<\\computer For OPC servers, the computer name, server name,
name\server and access path (if in use) for the OPC server you
name[|access want to switch to. Separate the access path from the
path]>server name with the | character.
<applicationFor DDE servers, the application and topic,
|topic>separated by the | character, for the DDE server you
want to switch to.
When you use the NodeSwitch command to change a node’s server
information, the change appears in the Node editor’s spreadsheet. If
the Node editor is open when you use the command, the change will
not appear until you close and re–open the editor.
For more information about the NodeSwitch command, see
Appendix A, RSView32 commands, or see Help.
You can also enable and disable nodes at runtime, using the
NodeEnable and NodeDisable commands. For more information see
Appendix A, RSView32 commands.
3–16 RSView32 User’s Guide
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. For
more details about setting the poll rate, see your server
documentation.
For projects using DDE, values are updated by the server at the rate
specified in the server product. When the server detects a change, it
provides the changed value to RSView32. For more details about
setting the poll rate, see your server documentation.
Scan class rates have no effect on DDE or OPC communications.
They affect only direct driver communications.
Setting up OPC and DDE communications 3–17
Chapter
4Creating 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.
The current value of a tag, when required, is updated from the device
it is connected to and stored in computer memory—referred to as the
value table—so it is immediately accessible to all parts of RSView32.
For example, graphic displays use tag values to control animation or
update a trend, alarm monitoring compares current tag values to pre–
defined limits, and data logging stores tag values to create a historical
record.
4–1
Tag types
RSView32 uses the following types of tags:
TagType of data stored
AnalogRange of values.
These tags can represent variable states such as
temperature or the position of rotary controls.
Digital0 or 1.
These tags can represent devices that can only be on or
off, such as switches, contacts, and relays.
StringASCII string, series of characters, or whole words
(maximum of 255 characters).
These tags can represent devices that use text, such as a
bar code scanner which uses an alphanumeric product
code.
SystemInformation generated while the system is running,
including alarm information, communication status,
system time and date, and so on.
4–2 RSView32 User’s Guide
RSView32 creates system tags when it creates a project.
The system tags are stored in the folder called “system”
in the tag database. You cannot edit system tags. You can
use system tags anywhere you would use any other type
of tag.
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
Tags with Device as the data source count toward the total tag limit
you purchased (150, 300, 1,500, and so on).
®
or DDE server.
Memory
A tag with Memory as its data source receives its data from the
RSView32 internal value table. A memory tag can be used to store
values internally. Tags with Memory as the data source do not count
toward the total tag limit.
Organizing tags
Organizing tags makes database creation faster and simpler. To
organize tags:
establish naming conventions
use folders to group related tags
Naming conventions enable you and operators to use the
RSView32 wildcards most effectively when searching for and
displaying tags during development and runtime.
Creating tags 4–3
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.
When a tag name starts with a number or contains a dash, enclose the
name in braces { } when you use it in an expression, for example,
{N33–0}. Also use braces when using wildcards to represent multiple
tags in an expression, for example, {alarm*}. For more information
about using tags in expressions see Chapter 14, Creating expressions.
Using folders to group tags
To organize tags, create a folder and include tags that are related to
one another. To separate the folder name from the rest of the tag
name, use a backslash (\). For example, tags in the folder called Pump
would start with Pump\. For greater organization, you can nest
folders. For example, you can organize the tag database first by area,
then by machines in the area, and finally by devices in each machine.
The result might be Area1\Machine1\Pump.
4–4 RSView32 User’s Guide
The tag database editor
Form
t
Folder
Hierarchy
Query
Box
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.
Spreadshee
Creating tags 4–5
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).
Select the Alarm check box to define alarm conditions for an analog
or digital tag. To edit alarms once they have been defined, click the
Alarm button.
RSView32 supports 40,000 tags with alarms. Of these, 5,000 can be
analog tags.
Using the query box
Use the query box to select the tags you want displayed in the
spreadsheet. This allows you to edit tags in different folders without
browsing the folder hierarchy. You can:
select a single tag by typing the tag name
select multiple tags by typing wildcards. The wildcards are:
4–6 RSView32 User’s Guide
This
character
?Matches any single character.
*Matches any number of characters, including the
Does this
backslash (\) character.
Use this wildcard by itself to display all the tags in
the tag database.
When you do searches, remember that the backslash in a folder name
This folder contains one or more folders.
This folder does not contain another folder.
Create Folder
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. For example, the system folder
holds the system tags that come with RSView32. For a complete list of
the system tags, display the contents of the folder or see Appendix B,
System tags.
You can nest folders. If a folder has a plus (+) sign, it contains one or
more folders. If a folder is blank, it does not contain any other folders.
Creating a folder
1. Click New Folder on the Edit menu or click the Create Folder
button on the toolbar.
2. Type the folder name.
Creating tags 4–7
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. Select the folders by doing one of the following:
2. Press Enter.
4–8 RSView32 User’s Guide
click a folder and then drag the mouse up or down
click a folder and Shift–click other folders immediately above
or below the first selected folder
click a folder and Ctrl–click other folders anywhere in the
hierarchy
The tags in the selected folders are displayed in the spreadsheet.
Adding tags to a folder
Create 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
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.
When you nest folders, remember that the backslash in a folder name
counts as one character in the tag name.
Creating tags 4–9
To view a series of nested folders, resize the hierarchy box. To resize it,
IMPORTANT
Duplicate
Tag Folder
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.
Be sure to choose Duplicate Folder rather than Duplicate. Duplicate
only duplicates individual tags.
To duplicate a folder and its tags:
1. Select the folder in the hierarchy.
2. Click Duplicate Folder on the Edit menu or click the Duplicate
Tag Folder button on the toolbar.
3. In the To field, type the new folder name.
4. Click OK.
4–10 RSView32 User’s Guide
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.
Moving through the spreadsheet
To scroll through the spreadsheet rows, do one of the following:
use the Prev or Next buttons in the form area
use the up arrow and down arrow keys
use the scroll bars on the spreadsheet
To select a row, click anywhere in the row or click the row number.
Resizing columns and rows
To resize a column or row:
1. Place the cursor over the division between the column or row, in
the top or side border, until it changes to a double arrow.
2. Drag the column or row to the required size.
Creating tags 4–11
Adding a tag
Insert
Row
Duplicate
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.
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
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. The new row
contains all the same information except the tag name.
3. In the Tag Name field, type the name for the new tag.
4. Click Accept.
Editing a tag
You can edit all parts of a tag except the tag name and tag type.
1. Select the tag you want to edit.
The details of the tag appear in the form area.
2. Edit any details except the tag name or type.
4–12 RSView32 User’s Guide
Deleting a tag
Delete
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
Delete
toolbar.
Configuring tag type
The topics below describe how to complete the fields for analog,
digital, and string tag types. For a description of how to complete the
Data Source fields, see “Specifying a data source” on page 4-19. 3.
Configuring an analog tag
1. If the tag is part of a folder, select that folder in the folder
hierarchy. The folder name appears in the Name field and is the
first part of the tag name.
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
3. For Type, select Analog.
Creating tags 4–13
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. These values do not affect
what is read from the programmable controller or server. For
example, if you specify a minimum of 0 and a maximum of 100,
RSView32 would be able to read a value of 200 from a PLC and
store it in the value table, but would not be able to write this value
to the PLC.
The range between the minimum and maximum values cannot
exceed the maximum floating point value (3.402823E
38
).
4–14 RSView32 User’s Guide
Scale and Offset
IMPORTANT
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. The offset is a fixed value—after the value
from the PLC is multiplied by the scale, the offset amount is
added. This formula shows the relationship between the PLC value
and the amount stored in the RSView32 value table:
RSView32 value = (PLC value scale) + offset
Values from the programmable controller are first scaled, then
added to the offset. When a value is written to the
programmable controller, the process is reversed: the offset is
subtracted and the scale is used for division. This ensures that
the correct, unchanged value is sent to the programmable
controller.
Units
Type a text label, for display only, up to 20 characters long. This
specifies how the tag value is measured (for example, gallon, PSI,
min, sec).
Creating tags 4–15
Data Type
The data types are:
Data typeDescriptionRange
DefaultDepends on the data
See below.
source and node type:
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.
Unsigned IntegerUnsigned 16–bit integer0 to 65,535
IntegerSigned 16–bit integer-32,768 to 32,767
Long IntegerSigned 32–bit integer-2,147,483,648 to
-2,147,483,647
Floating PointSingle–precision (32–bit)
floating point
-3.402823E
1.175494E
+38
to -
-38
,
0,
1.175494E
3.402823E
-38
+38
to
4–16 RSView32 User’s Guide
ByteUnsigned 8–bit integer0 to 255
3–Digit BCD3–digit binary–coded
0 to 999
decimal
Data typeDescriptionRange
IMPORTANT
4–Digit BCD4–digit binary–coded
0 to 9,999
decimal
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.
For tags with Memory as the data source, select the data type that
matches the format of the data you will store in the tag. Choosing
Default is the same as choosing Floating Point.
For a tag with a Long Integer data type, if the minimum,
maximum, scale, offset, or initial value is used with a decimal
point, RSView32 stores the value in floating point format. This
means that the maximum value for the tag is 16,777,216, which
is the maximum integer value for single–precision floating point
numbers.
Configuring a digital tag
1. If the tag is part of a folder, select the folder in the folder hierarchy.
The folder name appears in the Name field and is the first part of
the tag name.
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
3. For Type, select Digital.
Creating tags 4–17
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. The off and on
labels must be different. One or the other, but not both, can be
blank.
Configuring a string tag
1. If the tag is part of a folder, select the folder in the folder hierarchy.
The folder name appears in the Name field and is the first part of
the tag name.
2. Type a tag name. If the tag is part of a folder, type the name after
the backslash (\).
4–18 RSView32 User’s Guide
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. RSView32 will accept only a length that is a
multiple of the size of the Allen–Bradley
controller data element you are addressing.
Specifying a data source
The following topics describe how to complete the Data Source fields.
For details about configuring analog, digital, and string tag types, see
“Configuring tag type” on page 4-13.
®
programmable
Creating tags 4–19
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
RSLinx
®
direct drivers
™
5 programmable controllers through
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. Supply a node name by doing one of the following:
type a node name
double–click in the Node Name field to add a new node
click to open a selection list and select a node name
3. If you are connecting to Allen–Bradley or SoftLogix 5 devices
through direct drivers, select a scan class.
4–20 RSView32 User’s Guide
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.