rsview se v4.0 cpr7+ distributed system design

RSView SE V4.0 CPR7+ Distributed System Design Considerations (Rev. 4, Sep. 2007)

This page left intentionally blank.

RSView SE V4.0 (CPR7+) Distributed System Design Considerations Rev. 4, September, 2007, page 2 of 46

Table of Contents Introduction............................................................................................................................................................7

Prerequisite reading before application development........................................................................................7 Revision History ....................................................................................................................................................7 RSView SE Component Terminology...................................................................................................................8

FactoryTalk Directory™....................................................................................................................................8 RSView Studio ..................................................................................................................................................8 RSView SE Server.............................................................................................................................................8 Data Server.........................................................................................................................................................8 RSView SE Client..............................................................................................................................................8 RSView SE Station............................................................................................................................................8 RSView Administration Console.......................................................................................................................8

New in RSView SE 4.0 (CPR7+) ..........................................................................................................................9 New in RSView SE 4.0 (CPR7) ............................................................................................................................9 Software Installation ............................................................................................................................................10 Software Installation Order..................................................................................................................................10 Activation Keys ...................................................................................................................................................10 Default File Locations for SE Distributed Applications......................................................................................11 Operating Systems ...............................................................................................................................................11

Installing a new Operating System on computers............................................................................................11 Server OS vs. Workstation OS.........................................................................................................................11

Workgroup vs. Domain........................................................................................................................................12 Workgroup .......................................................................................................................................................12 Domain.............................................................................................................................................................12

Domain Best Practices (New!).............................................................................................................................13 Name Resolution (New!) .....................................................................................................................................14

NetBIOS Name Resolution..........................................................................................................................16 Host Name Resolution .................................................................................................................................16 Name Resolution Requirements for Distributed Systems ...........................................................................17 Name Resolution Best Practices for Distributed Systems ...........................................................................17

User Accounts: Individual vs. Group...................................................................................................................18 Component Installation Best Practices (New!)....................................................................................................18 Networking (Updated!)........................................................................................................................................18

Hubs vs. Switches ............................................................................................................................................19 Hubs .............................................................................................................................................................19 Switches .......................................................................................................................................................19 Unmanaged Switches...................................................................................................................................19 Managed Switches .......................................................................................................................................19

Managed Switch Features for Control Applications........................................................................................20 Redundant Ethernet..........................................................................................................................................20 IP Addressing: Static vs. Dynamic ..................................................................................................................20 Changing Server IP Address............................................................................................................................20


Firewalls...........................................................................................................................................................20 Windows Firewall (XP Service Pack 2, 2003 Service Pack 1)........................................................................21 Microsoft components: DNS, WINS, IIS ........................................................................................................21 Windows Support Tools ..................................................................................................................................21

Boosting Server Performance (Updated!)............................................................................................................22 Boosting Client Performance (New!) ..................................................................................................................24 Redundancy (Updated!) .......................................................................................................................................24 System Modification (Updated!) .........................................................................................................................25

Runtime Editing Considerations ......................................................................................................................25 General System Modification Procedure (Redundant & Non-Redundant) .....................................................26 System Modification Procedure on Redundant Servers ..................................................................................26

Communications (Updated!)................................................................................................................................27 RSLinx Enterprise Predefined Items ...............................................................................................................28 How many tags can RSLinx poll in a given amount of time? .........................................................................28 RSLinx Classic vs. RSLinx Enterprise vs. 3rd Party OPC ...............................................................................29 RSLinx Classic Remote OPC Server...............................................................................................................30 RSOPC Gateway..............................................................................................................................................30 RSLinx Classic with a Logix Controller..........................................................................................................30

Security ................................................................................................................................................................31 FactoryTalk Security (Updated!) .........................................................................................................................31

Access to Open an Application........................................................................................................................32 Windows Terminal Services ................................................................................................................................33 Time Synchronization (Updated!) .......................................................................................................................33

Windows Time Service Technical Reference..................................................................................................33 Administering the Windows Time Service......................................................................................................33

HMI Tags and Direct Referenced Tags ...............................................................................................................34 Tag related limits .............................................................................................................................................34 Tag Database (HMI Tags) ...............................................................................................................................34 Direct Referenced Tags....................................................................................................................................34 Alarm Acknowledge Bit ..................................................................................................................................34 Calculate number of tags on-scan ....................................................................................................................35

Data Log...............................................................................................................................................................35 Data Logging to Secondary Path .....................................................................................................................35 Multiple data log models .................................................................................................................................36 Data Log Storage Formats ...............................................................................................................................36 Trending...........................................................................................................................................................36

Database Considerations......................................................................................................................................37 Language Switching.............................................................................................................................................37 Global Objects .....................................................................................................................................................37 Graphic Displays..................................................................................................................................................37

Importing and Exporting Graphic Display XML Files....................................................................................38 ActiveX Components.......................................................................................................................................38 Visual Basic for Applications ..........................................................................................................................39


RSView Enterprise Tools ....................................................................................................................................39 Naming Components ...........................................................................................................................................40 Overall Considerations.........................................................................................................................................40

How to determine what SE projects load when O/S initializes .......................................................................41 Designing A Multi-User System......................................................................................................................42 Languages ........................................................................................................................................................42 Misc. Procedure ...............................................................................................................................................42

RSView32 to RSView SE Conversions...............................................................................................................42 ControlLogix Redundancy (v13 and above) (Updated!) .....................................................................................43

Automatic IP Address Swapping .....................................................................................................................43 Tricks and Tweaks ...............................................................................................................................................43 Tools and Utilities................................................................................................................................................44 Additional Reference Links .................................................................................................................................44

FactoryTalk ......................................................................................................................................................44 RSView SE ......................................................................................................................................................44 RSView ME.....................................................................................................................................................44 RSBizWare ......................................................................................................................................................45 Communications ..............................................................................................................................................45 ControlLogix....................................................................................................................................................45 Security ............................................................................................................................................................46 Microsoft..........................................................................................................................................................46 General.............................................................................................................................................................46


This page left intentionally blank.


Introduction The intent of this document is to make a user aware of the numerous variables that come into play when designing an RSView SE distributed application. Once read, a user will be able to proactively evaluate the current state of a project and understand the areas that require additional detail, research, or instruction to be successful. Each subject will provide a brief synopsis of the material, decisions to be made, and may contain hotlinks to additional technical notes or reference sites for more specifics. The information provided within is a guide to assist a project team with critical decisions that need to be made in order for a successful implementation to occur. As with any project, the system integration team is responsible for these decisions. The Rockwell Automation Knowledgebase should always be consulted for information that may supersede this document.

Prerequisite reading before application development • RSView Supervisory Edition Install Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewse-in003_-en-p.pdf • RSView Supervisory Edition User's Guide Volume 1

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um004_-en-e.pdf • RSView Supervisory Edition User's Guide Volume 2

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um005_-en-e.pdf

Revision History

• Revision 4 (August 2007): URL Link updated for Windows Time Synchronization section. • Revision 3 (February 2007): URL links updated for the new Rockwell Automation Knowledgebase.

New content. See the table of contents for sections marked as “New!” or “Updated!” • Revision 2 (January 2007): New content. See the table of contents for sections marked as “New!” or

“Updated!” • Revision 1 (October 2006): New content in addition to updates applicable to CPR7+. See the table of

contents for sections marked as “New!” or “Updated!” • Revision 0 (November 2005): Initial release for CPR7.


http://www.rockwellautomation.com/knowledgebase/

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewse-in003_-en-p.pdf



RSView SE Component Terminology FactoryTalk Directory™ is software that supplies a directory of services (for example, RSView SE Servers, or OPC servers) and names (for example, areas, tags, graphic displays, log models, and so on) to any computer on the network that participates in RSView Supervisory Edition applications. RSView Studio is configuration software for developing and testing machine- and supervisory-level human-machine interface (HMI) applications. RSView Studio contains editors for creating a complete human machine interface application, and contains software for testing the applications you create. Use the editors to create applications that are as simple or as sophisticated as you need. The maximum number of RSView Studio clients that can have simultaneous access to an RSView Supervisory Edition application is 5. RSView SE Server stores HMI project components (for example, graphic displays), and serves these components to clients. The server also contains a database of tags, and performs alarm detection, and historical data management (logging). The RSView SE Server has no user interface. Once installed, it runs as a set of ‘headless’ Windows services that supply information to clients when they request it. The maximum number of HMI servers supported in an application is 10. In non-redundant scenarios, the maximum number of HMI servers that can be hosted on a single computer is 2. In redundant scenarios, the maximum number of HMI servers that can be hosted on a single computer is 1. Data Server is the software component that allows clients to access information in programmable controllers, devices and other data servers that comply with the OLE for Process Control-Data Access (OPC-DA) 2.0 specification. This data is used to populate HMI tags and display screens among others. Some examples of data servers are RSLinx Classic, RSLinx Enterprise and 3rd party OPC Servers (e.g., Kepware, Matrikon). RSView SE Client is software for viewing and interacting with supervisory-level applications developed using RSView Studio. The maximum number of RSView SE Clients that can have simultaneous access to an RSView Supervisory Edition application is 50. When counting clients, a client can be an RSView SE Client, an RSView SE Server, an RSSql FactoryTalk connector, RSView Studio, or the RSView Administration Console. RSView SE Station. A traditional “single box” HMI solution that packages a server and client as a single PC. RSView Administration Console is software for administering RSView Supervisory Edition applications after they have been deployed. RSView Administration Console contains a sub-set of the RSView Studio editors, so you can make minor changes to an application, without the need for installing RSView Studio. The Administration Console has a two hour time out. A warning message is displayed five minutes before this time expires. To continue using it you will have to shut it down and restart it.


http://www.opcfoundation.org/Default.aspx/01_about/01_whatis.asp?MID=AboutOPC

New in RSView SE 4.0 (CPR7+)

The following improvements and features are included in CPR7+: • String Spreadsheet Editing • RSView SE Runtime HMI Tag Property Editing Improvements • RSView SE Runtime Alarm Property Editing Improvements (including the new

ALARMACCEPTEDITS command) • RSView SE HMI Server Replication

See AID 34215 - CPR7+ Runtime Editing improvements, HMI Redundancy replication, and String Spreadsheet editing.

New in RSView SE 4.0 (CPR7)

• FactoryTalk Security. FactoryTalk Security authenticates user identities and authorizes user requests to access a FactoryTalk-enabled system. These security services are fully integrated into the FactoryTalk Directory and are included as part of the FactoryTalk Automation Platform. User authentication determines who can open, create, modify, and delete application components. You also use FactoryTalk Security to add user and group security accounts as well as Windows-linked accounts, and set up security for common actions such as tag writes, open, and delete.

• Runtime language switching. Provides the ability to set up multiple languages for an application and switch application languages dynamically at run time. Users specify an initial language for the application to be displayed in on the client when it starts up, which can be changed while the application is running on the client, using the Language command specified for the press action on a Button object.

• Global graphic objects. Allow you to link the appearance and behavior of a graphic object in a global object display to multiple copies of that object in other displays in the same application. When you make changes to the original (base) object, the copies (reference objects) are changed as well.

• RSLogix5000 process faceplates. RSView SE now includes global object-based process faceplate displays for Logix5000 instructions that are commonly used in process applications. These faceplates are easily added and connected to user applications, reducing the effort required to get up and running. RSLogix5000 process faceplates include a runtime help browser display and customizable HTML help files to allow users to create contextually relevant help messages or instructions for operators

• Patch File Validator utility. When multiple patch files need to be applied to a program, it is useful to be able to determine exactly which patch files have already been installed. The Patch File Validator utility is available in technical note AID 30393 - Patch File Validator Utility in the Rockwell Automation Knowledge Base.

• Adobe Reader 7.0. The Adobe Reader installed with RSView Enterprise has been upgraded from Version 6.0 to Version 7.0.


http://rockwellautomation.custhelp.com/cgi-bin/rockwellautomation.cfg/php/enduser/std_adp.php?p_faqid=34215



Software Installation As part of the installation process, RSView creates program folders and modifies the system registry. To make these modifications, the user that is currently logged in must have administrative rights on the computer on which RSView is installed (for example, the Windows 2000 Administrator account has these rights). You do not need administrative rights to run RSView.

Software Installation Order • Internet Information Server (IIS)

o To develop and test distributed applications on a single computer IIS must be installed. o Only install on HMI Servers for a distributed system. To create stand-alone applications, IIS

does not need to be installed. o IIS is installed using Add/Remove Programs and the files required can be found on the

Windows 2000, Windows 2003 or Windows XP CD-ROM. • FactoryTalk Automation Platform (FTAP)

o FactoryTalk Automation Platform must be installed first before installing any of the RSView Supervisory Edition software components.

o Install FTAP on all 3rd party OPC PC’s o If Microsoft.NET is not currently installed on the computer, it will automatically be installed at

this point. o Be sure to record the default administrator user name and password. Consider creating a second

administrator user in the event the primary becomes locked out or password is forgotten or lost. With the release of FactoryTalk Security you now have the ability to configure ‘local’ and ‘network’ users separately.

• RSView Supervisory Edition • Specify the location of FactoryTalk Directory. A reboot is required for changes to take affect. • RSLinx Enterprise (optional) • RSLinx for RSView and/or 3rd Party Servers (optional)

Activation Keys • Rockwell Software's Windows-based software packages are copy-protected. Only a computer with

access to the activation files can actually execute the software. • When a Rockwell Software product is launched, the software first checks the local hard drive, then

network hard drives, and finally local floppy drives for activation. Systems attached to extensive networks can take quite a while to search for activation files on all available drives. If the system fails to detect either the activation file or the Master Disk, the product fails to start, starts in Lite mode or starts in Demo mode depending on the software product.

• Installing all keys on the FactoryTalk server allows for a central management location. This configuration allows the user to be able to see what keys are in use and how many are still available. Loss of communication from clients to FTD will cause clients not to obtain a license, resulting in limited demo mode functionality.


• Installing keys on each computer guarantees that computers’ license will not be used by another computer.

• Use the move utility, EvMove, to move activation files. Attempts to copy, rename, move or e-mail an activation file by other means will damage the file and can render the software inoperative.

• For more information, please reference the online help for the product. • AID 2777 - Network Installation Of EVRSI.SYS Activations

Default File Locations for SE Distributed Applications Windows 2000:

Network FactoryTalk Directory File: C:\Documents and Settings\All Users\Application Data\Rockwell\RNAServer\Global\*.RnaD Application Files: C:\Documents and Settings\All Users\Documents\RSView Enterprise\SE\HMI Projects\

Windows XP & 2003:

Network FactoryTalk Directory File: C:\Documents and Settings\All Users\Application Data\Rockwell\RNAServer\Global\*.RnaD Application Files: C:\Documents and Settings\All Users\Shared Documents\RSView Enterprise\SE\HMI Projects\

Help Files (New Location with RSView SE 4.0): C:\Program Files\Common Files\Rockwell\Help Operating Systems The following technote lists the various versions of RSView SE and the tested operating systems and service packs: AID 42682 – Software Platform/Hardware Compatibility Matrix.

Installing a new Operating System on computers Be sure to always install the PC vendor supported or recommended OS if upgrading or modifying your system. In some cases there are not proper hardware drivers for a particular hardware/software combination. Using unsupported operating systems or drivers can cause the computer to be unstable. Obviously if the OS is unstable, it is too much to ask for any applications running on it to be stable. Please be aware that computer manufacturers can make modifications to an Operating Systems which may impact the installation or performance of our software products. It is recommended to use full versions of the intended operating system on all workstations.

Server OS vs. Workstation OS • It is highly recommended that the FactoryTalk Directory, HMI and Data Servers be installed on

Windows 2000/2003 Standard Edition servers. Windows XP and Windows 2000 Pro are workstation operating systems (they have a 10 connection limit). Multiple connections are established to each ‘server’ by every RSView SE Client (including RSView Studio).




• As a general rule, servers and clients should be in the same Windows OS ‘vintage’. For example, Windows 2000 clients should not be used with Windows 2003 (or Windows XP) ‘servers’. The combination of Windows XP SP2 ‘servers’ and Windows 2000 Professional SP4 clients has been problematic with both Rockwell Software and third-party products. See AID 32427 - RSView SE clients get no data when Windows XP SP2 hosts an OPC data server.

• RSView SE server side components are not supported on clustered servers. However, when using Windows 2003 Server and Terminal Services, you can install the SE Client component on 2003 Terminal Servers that are using Network Load Balancing (NLB).

• Virtualization is not supported in a production environment. See AID 30209 - Virtualization Software. However, there are no known issues with virtual computing environments and they can be utilized for HMI system development and testing.

• When you are running a distributed application on Windows XP Professional and using Windows workgroups, you must disable the default XP feature, 'simple file sharing', or RSView SE clients will not be able to authenticate. For details, see Help provided with Windows XP, or look under the heading 'RSView SE in a Windows workgroups environment' in the Known Issues topic of the release notes. AID 25595 - Cannot login to RSView using Windows security when computer belongs to a workgroup.

Workgroup vs. Domain

Workgroup Decentralized Administration

Advantages: • No Domain Controller (Windows Server OS) to purchase. • One less computer in network to maintain. • Recommended only for small SE applications where user accounts don’t change often.

Workgroup Rules:

• All computers participating in a single application must be members of the same Windows workgroup. • All users participating in the workgroup must be members if the Administrators group. • Create the same set of user accounts and passwords on every computer in an RSView Supervisory

Edition application. For details see Help provided with Windows.

Domain Centralized Administration

Advantages: • Centralized Administration • One place to manage Users, Groups and Security • Automate IP addresses with Dynamic Host Configuration Protocol (DHCP), and Name Resolution

and with Domain Name Service (DNS) and Windows Internet Name Service (WINS).







Domain Rules: • For applications consisting of more than 10 computers, a domain controller is required. • Rockwell Software components (including FactoryTalk) should not be installed on domain controllers.

Domain Best Practices (New!) Extensive information on Microsoft domains is beyond the scope of this document, however there are some key points that users of an RSView SE system with a Domain Controller should understand.:

• RSView SE supports the following domains: o Windows NT4: In addition to the Primary Domain Controller (PDC), we recommend at least

one backup Domain Controller (BDC) to provide high availability. o Windows 2000 Server Active Directory (in Native or Mixed mode): We recommend at least 2

domain controllers, where both are configured as Global Catalog Servers to provide high availability. Note: In Windows 2000 AD domains, PDC’s and BDC’s basically no longer exist, however, one domain controller serves as a “PDC Emulator” to provide certain backward compatible functionality.

o Windows Server 2003 Active Directory (in any functional level): We recommend at least 2 domain controllers, where both are configured as Global Catalog Servers to provide high availability. Note: In Windows Server 2003 Active Directory, the concept of a domain "mode" has been re-branded as a "functional level."

Note: Windows 2000 AD domains introduced the concept of a “forest.” A forest can consist of a single “domain tree”, or multiple domain trees. A domain tree can consist of a single domain (a.k.a. the “parent” domain) or multiple domains (a.k.a. the “child” domains). We recommend a single forest, single tree, single domain configuration. In Windows Server 2003 Active Directory, both domains and forests have individual functional levels. We recommend the default functional levels:

o Domain: Windows 2000 mixed o Forest: Windows 2000

To determine the Window 2000 domain mode, launch Active Directory "Domains and Trusts" (Start > Programs > Administrative Tools), right-click the domain and select "Properties". To determine the Window 2003 functional levels, the identical procedure is used.

• You should choose your internal domain names carefully. An Internet domain name (external) should

not be confused with a Microsoft Active Directory domain name (internal), and while they can be the same name, typically they are not. Consult your company’s IT department or the Microsoft Best Practice Active Directory Deployment for more information.

• When computers are joined to an AD domain, they will automatically be configured to periodically

update their clock using a domain controller (i.e., the PDC emulator). Therefore the DC that serves as the PDC emulator must be configured to get the correct time from an external time source (i.e., it should not point to itself). For more information, see the section entitled Time Synchronization later in this document.


http://technet2.microsoft.com/WindowsServer/en/library/da255f53-ae6c-4af8-80f1-9b3c046022311033.mspx?mfr=true

http://technet2.microsoft.com/WindowsServer/en/library/da255f53-ae6c-4af8-80f1-9b3c046022311033.mspx?mfr=true

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/plan/bpaddsgn.mspx

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/plan/bpaddsgn.mspx

• Prior to deploying RSView SE, both new and existing active directory domains should have their

operation verified using Microsoft’s Domain Controller Diagnostics (Dcdiag.exe) utility. This utility is included with the Windows Support Tools located on the Operating System CD and also available via download from Microsoft. Click here for more information on installing the Windows Support Tools. Click here for an overview of DCDIAG.

• Rockwell Software does not support our software on computers configured as domain controllers. The

following information comes from a Microsoft TechNet article posted at http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.mspx. The key sentence in this TechNote is "In general, Microsoft does not recommend running applications on computers configured as domain controllers, and certainly not applications that require more than Authenticated User privileges in order to run successfully." Installation of any application software on a domain controller can have adverse affects on the network and is the responsibility of the user to accept the risk.

Name Resolution (New!) FactoryTalk Applications require efficient computer name to IP address resolution for proper operation. Networks running Microsoft Windows operating systems use two basic types of names for computers and other resources: Network Basic Input/Output System (NetBIOS) names and Host names. While an in-depth explanation of Name Resolution is beyond the scope of this document, we will attempt to summarize the key issues for Name Resolution as it applies to FactoryTalk and RSView SE, beginning with a basic explanation of NetBIOS names (a.k.a. computer names) and Host names (a.k.a. DNS names). NetBIOS Names Every Windows computer has a NetBIOS name, which is established when you install the operating system. After the OS installation is complete, you can view (and change) the NetBIOS name using Control Panel > System > Computer Name > Change…> More…:


http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en

http://technet2.microsoft.com/WindowsServer/en/library/74787a10-6dff-4623-98ab-dc26f1faa6eb1033.mspx?mfr=true

http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.mspx

NetBIOS names are unique to Windows computers, and have been around since Windows computers began showing up on computer networks. NetBIOS names are limited to 15 characters and - as indicated in the dialog box - are typically used for interoperability with older Windows computers and services.

Note: You can also find the NetBIOS name for a Windows computer (along with other information about the Server service) by entering the command “net statistics server” from the command prompt. See the Windows On-line Help for more information.

The most common use of NetBIOS names is browsing My Network Places to look for shares (i.e., folders and printers) on other Windows computers. Rockwell applications like the ‘Specify FactoryTalk Directory Location’ utility also utilize NetBIOS names – because they leverage My Network Places when you click the browse button:

In order to connect (or browse) to a computer running TCP/IP via its NetBIOS name, the NetBIOS name must be resolved to an IP address. For more information, see the section below entitled “NetBIOS Name Resolution”. Host Names Host names are a byproduct of the TCP/IP protocol. Every computer running TCP/IP (whether it's a Windows machine or not) has a host name. A Windows computer's NetBIOS name should not be confused with its Host name (although they are typically the same). On a Windows computer, you can view (or change) the host name using Control Panel > System > Computer Name > Change…:

Host names are limited to 255 characters. Host names are used by TCP/IP applications such as web browsers, ftp, telnet, etc.


http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_statistics.mspx?mfr=true

Note: You can also find the host name for a computer by entering the commands “hostname” or “ipconfig/all” from the command prompt. A computer can actually have several host names (although this is not common).

In the dialog above, the ‘Full computer name’ (also known as the Fully Qualified Domain Name – or FQDN) is the domain name (ra.rockwell.com) appended to the computer name (usdencsthmipri). In order to connect to a computer running the TCP/IP protocol using its host name, the host name must be resolved into an IP address. For more information, see the section below entitled “Host Name Resolution”. NetBIOS Name vs. Host Name A NetBIOS name is unique to computers running a Windows operating system, while a host name applies to Windows and virtually all other operating systems (Unix, Linux, MacOS, etc.) that use the TCP/IP protocol. By default, the NetBIOS name and the Host name for a Windows computer are the same, and while it is possible for them to be different, this is seldom the case and should never be the case for a computer using Rockwell Software. Neither NetBIOS names nor Host names are case sensitive.

NetBIOS Name Resolution NetBIOS name resolution is unique to Windows networks and NetBIOS names are resolved to IP addresses using one of 3 methods:

1. Broadcasts – each computer announces its presence on the network at boot up. One computer is elected as the Master Browser and this computer keeps a list of all the computers on the network. This is the default NetBIOS Name Resolution method for Windows networks. While dynamic, this is a relatively inefficient and unreliable method due to the broadcast traffic and periodic elections of the master browser (and backup browsers). It is also limited to a single network segment (subnet) because NetBIOS messages are not routable.

2. LMHOSTS files - each computer has a static text file that lists the NetBIOS names and their corresponding IP addresses of all Windows computers on the network. This method is best for networks that seldom change and typically dictates that all computers use static IP addresses.

3. Windows Internet Name Service (WINS) – a Windows Server OS computer keeps a “database” of NetBIOS names and their corresponding IP addresses. This method is dynamic, but requires configuration and maintenance of the WINS server. Ideally, there is both a primary and a secondary WINS server on the network to provide redundancy.

Note: Some Microsoft tools used to diagnose NetBIOS name resolution problems are NBTStat.Exe (from the command line) and Network Diagnostics. See the Windows On-line Help for more information.

Host Name Resolution Host name resolution is the name resolution method of the internet and private Windows networks that use the Active Directory service provided with Windows Server 2003 and Windows 2000 Server. Host name (or FQDN) to IP address resolution on private Windows networks is accomplished in one of 2 ways:

1. HOSTS files - each computer has a static text file that lists the host names and their corresponding IP addresses of all computers on the network. This method is best for networks where the computers are static. Using HOSTS files typically dictates that you also use static IP addresses for your computers.


http://support.microsoft.com/default.aspx?scid=kb;en-us;323388

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/netdiag.mspx

2. Dynamic Domain Name System - a Windows Server OS computer keeps a “database” of host names and their corresponding IP addresses. This method is dynamic, but requires configuration and maintenance of the DNS server. Ideally, there is both a primary and a secondary DNS server on the network to provide redundancy.

Note: Some Microsoft tools used to diagnose host name resolution problems are Nslookup.Exe (from the command line) and Network Diagnostics. See the Windows On-line Help for more information.

Name Resolution Requirements for Distributed Systems Rockwell Software distributed systems require both NetBIOS and Host name resolution. Small RSView SE architectures (i.e., 10 computers or less) are typically deployed in workgroups and often times do not include a Server OS. In these scenarios, NetBIOS name resolution is typically accomplished by the broadcast (default) method. While this is sufficient in many cases, LMhosts files are preferred. Ideally, one or more server computers are available and both a primary and a secondary WINS server are provided. Once the WINS role has been added to a server(s), configuration and management is accomplished with the WINS Microsoft Management Console (MMC) located in the Administrative Tools program group. All computers using NetBIOS over TCP/IP need to know the IP address of the WINS server(s). The IP addresses of the primary and secondary WINS servers on the network are typically entered manually into the TCP/IP configuration of servers and supplied to clients via DHCP. Large RSView SE architectures (i.e., more than 10 computers) require a Windows Domain (NT 4, 2000 Active Directory and 2003 Active Directory are supported). Post-NT 4 Domain Controllers (i.e., Active Directory domains) require DNS and typically also host the DNS server role. Ideally, both a primary and a secondary DNS server are provided. Once the DNS role has been added to a server, configuration and management is accomplished with the DNS Microsoft Management Console (MMC) located in the Administrative Tools program group. All computers using TCP/IP need to know the IP address of the DNS server(s). The IP addresses of the primary and secondary DNS servers on the network are typically entered manually into the TCP/IP configuration of servers and supplied to clients via DHCP.

Name Resolution Best Practices for Distributed Systems • Name all RSView SE computers using 15 characters or less. This virtually guarantees that the

NetBIOS name and the host name are always the same. • Do not use underscores or periods, and do not include the product name “RSViewSE” in the computer

name. • If a Server OS is available, use a WINS server for NetBIOS name resolution (preferably 2 WINS

servers – a primary and a secondary). Recall that each WINS client computer must be configured with address(es) of the WINS server(s). This eliminates relying on the inefficient broadcast method for NetBIOS name resolution. In workgroups without a server OS, use LMHosts files.


http://technet2.microsoft.com/windowsserver/en/technologies/featured/dns/default.mspx

http://support.microsoft.com/kb/200525/en-us

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/netdiag.mspx

• If a Server OS is available, use a DNS server for Host name resolution (preferably 2 DNS servers – a primary and a secondary). Recall that each DNS client computer must be configured with address(es) of the DNS server(s). In workgroups without a server OS, use Hosts files.

• Prior to deploying RSView SE, DNS operation should be verified using Microsoft’s Domain Controller Diagnostics (Dcdiag.exe with the /Test:DNS switch) utility. This utility is included with the Windows Support Tools located on the Operating System CD and also available via download from Microsoft. Click here for more information on installing the Windows Support Tools. Click here for an overview of DCDIAG. Note: The /Test:DNS switch is only available in later versions of the Support Tools.

User Accounts: Individual vs. Group • Individual account allows the client computer to tell who the logged in user is and act on it in the VBA

environment. • Group accounts in an RSView SE application do not need to be modified when a Windows user

account is added or removed. Adding the new Windows user account to a group used within RSView SE is all that is needed to give that user access to the RSView SE application.

Component Installation Best Practices (New!) Due to the distributed nature of the components of RSView SE, there are numerous possible architectures for a given distributed system. For example, consider a small distributed system consisting of the following components: FTD, HMI Server, Data Server, 2 Clients. This system could be deployed several ways using only 2 PCs, here are just 2 examples:

1. PC #1 = FTD, HMI Server, Data Server, Client #1; PC #2 = Client #2 2. PC #1 = FTD, HMI Server, Client #1; PC #2 = Data Server, Client #2

The problem with both of these examples is the lack of server-client autonomy. It is highly recommended that server and client roles be hosted on separate PCs. The installation of a client on the same PC as the HMI server is a supported architecture, however many scenarios exist that require a reboot of the client PC. In such a configuration, the reboot of the client will also shutdown the HMI server which affects the other distributed clients that were connected to the same HMI server. The implementer of such configuration is knowingly accepting this behavior. Therefore, a preferred solution for this system would be:

• PC #1 = FTD, HMI Server, Data Server; PC #2 = Client #1; PC #3 = Client #2. Following this recommendation requires an additional PC, but the additional hardware cost is typically more than offset by increased system usability and maintainability. Servers are typically located in a secured, environmentally controlled area, clients are typically in a control room or on the plant floor.

Networking (Updated!) • A network is only as good as the hardware. RSView SE is a Client/Server software solution that relies

on having a stable and reliable network. Ethernet communications rely on a network that does not have noise, excessive collisions, or broadcast storms.



http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en

http://technet2.microsoft.com/WindowsServer/en/library/74787a10-6dff-4623-98ab-dc26f1faa6eb1033.mspx?mfr=true

http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true

• Use name-brand Network Interface Cards (e.g., 3Com, Intel) where possible. Rockwell Software has observed issues related to lesser quality - and even some motherboard integrated - NIC’s.

• Manually configure NICs and Switch ports to match each other (100 Mbps or 1000 Mbps and Full Duplex). The “Auto Negotiate” setting (typically the default) is not recommended.

• Legacy hardware like PLC5, Sidecar, and SLC5/05 operate at only 10 Mbps and Half-Duplex. Ports on a switch or repeater used with this equipment must operate at 10 Mbps and Half-Duplex.

• Consider contacting Rockwell Automation’s Network Services group. For a fee they can assist in designing, configuring, commissioning and troubleshooting networks and their components.

Hubs vs. Switches

Hubs • NOT recommended for FactoryTalk (RSView SE) applications! • Low cost, low functionality • As “dumb” modules, they do not interpret data or sort messages that pass through them. Do not posses

any fault tolerance mechanisms or traffic optimization functionality (i.e., could cause high rate of collisions and errors in network)

• Are not assigned IP or Mac addresses (they are “transparent”)

Switches • Higher cost, higher functionality • As “intelligent” modules, they interpret the data as it enters each port and redistribute it only to the

ports that need it. This results in reduced network traffic and collisions (to varying degrees). • Are available in 2 “flavors”: Unmanaged and Managed

Unmanaged Switches • NOT recommended for FactoryTalk (RSView SE) applications! • Not configurable, but route data more intelligently than hubs. They typically do not have large

buffers and there is a chance of collisions, errors, dropped packets, packet timeouts. • Are not assigned IP or Mac addresses (they are “transparent”) • NIC cards used with unmanaged switches should be set according to the switch manufacturer’s

recommendation

Managed Switches • Highest cost, highest functionality. Managed switches (commercial or industrial grade) are

recommended for FactoryTalk (RSView SE) applications. • They are configurable with extra functionality like traffic optimization, fault tolerance

mechanisms, alarms, monitoring, packet prioritizing, diagnostics, etc. • Are assigned IP addresses (they are seen as a node or station on the network) • NIC cards used with managed switches should be set to the maximum network speed and Full

Duplex (e.g., 100MB/Full Duplex).


http://www.rockwellautomation.com/services/networks/index.html

Managed Switch Features for Control Applications Required

• Full-duplex on all ports • IGMP Snooping

Recommended • VLAN • Port mirroring • Auto negotiate and manually configurable speed/duplex • Wire-speed switching fabric • “Management” features: SNMP, VLAN, Web Server

For additional information on switches please reference:

• AID 22044 - Ethernet/IP Switch Considerations • AID 24380 - Ethernet/IP, Switches, and Multicast Frames

Redundant Ethernet Cisco and Hirschmann both offer fault tolerant switches and networking software to manage redundant Ethernet solutions.

IP Addressing: Static vs. Dynamic • Static IPs should be assigned to all servers (Domain Controllers, FactoryTalk Directory, HMI, Data).

This reduces the chance of client computers not finding servers. • Dynamic Host Configuration Protocol (DHCP) can be used for clients. Reduces administration for IT. • The use of Static IPs and HOSTS files is recommended for all PCs when used in a Workgroup

configuration.

Changing Server IP Address If the computer name or IP address changes for a computer that is hosting a server (FactoryTalk Directory, HMI, Data, OPC) in a distributed SE application, all computers in the system should be rebooted. This is required to ensure that low-level communications between the computers works correctly. If the name or IP address changes for the FactoryTalk Directory server, the “Specify FactoryTalk Directory Location” utility should be run to verify proper configuration and connectivity. This should be done after the above step has been completed.

Firewalls By design, a firewall is intended to ‘block’ network traffic on one segment of a network from reaching another. This is inherently bad for a distributed system that depends on remote communications. A firewall (if necessary) should be placed ‘outside’ the control system, not ‘within’ it. The opening of ports within a firewall




http://www.cisco.com/warp/public/779/largeent/sitemap/sm_guest.html

http://portal.hirschmann.com/

may present a security concern, and an IT Security expert will need to be involved in the configuration. The following article is an excellent starting point of reference. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndcom/html/msdn_dcomfirewall.asp

Windows Firewall (XP Service Pack 2, 2003 Service Pack 1) Rockwell provides a configuration utility to aid in the modification of the Windows firewall. This utility is installed with CPR7. The Rockwell Software products need to be installed prior to running the utility. For more information, see:

• AID 30498 - Windows Firewall Configuration Utility for Windows XP Service Pack 2 • AID 29402 - TCP ports used by Rockwell products.

Microsoft components: DNS, WINS, IIS • DNS (Domain Name System) - RSView SE browses computer names and must resolve to the computer

IP addresses. DNS resolves host names to IP addresses. • WINS (Windows Internet Name Service) - Provided in Windows 2000 Server for compatibility with

older Windows operating systems like Win95 and NT. WINS resolves NetBIOS names to IP address. • IIS (Internet Information Services) - RSView SE Server uses Internet Information Services to transfer

graphic files from servers to clients. A full install of IIS contains 10 components; RSView SE only requires 4 to be installed. (Common Files, IIS Snap-in, World Wide Web Server and Personal Web Manager if using Windows 2000 Pro). Client computers do not need IIS installed, neither do RSViewSE station (stand alone).

• SE Clients use the Temporary Internet Files directory to store local copies of RSView SE Server graphic files for quicker display. This setting should be set to ‘Every visit to the page’.

Windows Support Tools Microsoft provides numerous diagnostic tools for Domain Controllers, Active Directory and networking in general that must be installed after the operating system. To install the tools, browse your operating system CD (Windows XP and Server 2003) to \Support\Tools\ and run SupTools.Msi. To get an overview of the tools available, click Start > Programs > Windows Support Tools > Support Tools Help.


http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndcom/html/msdn_dcomfirewall.asp



Boosting Server Performance (Updated!)

• It is generally recommended that once an application is rolled out into a production environment that the HMI Servers be set to 'Load and run startup components when operating system initializes'. This is accomplished with RSView Studio or the RSView Administration Console by right-clicking on the HMI Server.

• On an RSView SE server using Windows 2000 Pro, use the System tool in Control Panel to set the Performance Option’s Application Response setting to “Optimize performance for Background services” (For Windows 2000 & 2003 Server, this is the default setting). Windows XP Pro has a similar setting.

For additional information please reference Microsoft’s Description of Performance Options in Windows


http://support.microsoft.com/?kbid=259025

On an SE server using Windows 2000 or 2003 Server OS, use the Network tool in Control Panel to set the Server Optimization setting for "Maximize data throughput for network applications" (this is not the default setting).

1) 2)

3) 4)

5) Maximize data throughput for network applications This setting is best for distributed network applications, which for the most part perform their own memory caching and optimization. Rather than allocating server RAM for file caching, the RAM is available to be allocated to individual applications, as they need it. This is the setting to choose if applications such as RSViewSE or SQL server are installed. This setting may also be chosen in cases where extremely large files are routinely copied, because the cache may grow so large from these files that other system processes do not have sufficient RAM.

• Microsoft’s Maximize Data Throughput Setting for Performance


http://www.microsoft.com/technet/community/columns/insider/iisi0701.mspx


Boosting Client Performance (New!) Both clients and servers can benefit from removing unnecessary software using Control Panel > Add/Remove Programs. Additionally, network performance can be improved by removing unnecessary protocols on the network adapter. Protocols that can usually be removed are: NetBEUI and NWLink IPX/SPX (the typical RSView SE system only requires TCP/IP). These protocols are removed using Control Panel > Network Connections > Local Area Connection. Click Properties and uninstall the unnecessary protocols from the list. Dedicated clients (i.e., computers that don’t also act in any capacity as a server) typically use a workstation operating system (e.g., Windows 2000 Professional or Windows XP Professional). These clients can realize increased performance (and potentially decrease network traffic) by disabling unused services. Two examples are the Server service and the Computer Browser service (which is dependant on the Server service):

1. The Computer Browser service allows the workstation to participate in Browser Elections (the selection of a Master Browser on the network), but if a Domain Controller (or any Server OS) is on the network, the workstation OS will always loose the election. Therefore, this activity is a waste of resources. Disabling this service (or setting it Manual) will free up resources on the SE Client and has no downside. Disabling this service will not prevent you from browsing the network (provided NetBIOS over TCP/IP is enabled and there are other computers on the network with this service running).

2. The Server service basically accepts and manages remote connections. Disabling this service (or

setting it Manual) will free up resources on the SE Client while providing the added benefit of increased security for that client. However, one disadvantage of disabling the Server service is that remote management of that client is no longer available.

There are many other services you can disable to free up even more resources. However, make sure you understand the ramifications before you disable them. For example:

• Smart Card (If you don’t have a Smart Card system, you don’t need this service) • Uninterruptible Power Supply (Only needed if you have a UPS connected to the PC) • Remote Registry Service (This service allows one to remotely edit the registry. It’s a security hole that

you should close). Once again, when in doubt as to the purpose of a particular service, it is probably best to leave it alone.

Redundancy (Updated!) Redundancy requirements are unique to each application. The ideal redundant solution involves having at least two instances of everything – hardware, software, networks, and so on. In practice, this is seldom feasible or even necessary. RSView Enterprise redundancy allows creation of duplicate server information that can be used if a server fails. The desired outcome is to maximize system availability. Keep in mind that RSView Enterprise Redundancy is typically used for:

• Computer hardware failure • Software failure on one HMI/Data Server computer • Power failure on one HMI/Data Server computer


Before setting up redundancy, plan: • Which components in the system require redundancy? • What software components on PC’s require backup systems? • The network layout of the components within the system. • CPU processing load that is expected for each computer.

Software redundancy can be configured for:

• HMI Server • Data Server

Software redundancy is not the equivalent of hardware hot backup. If using (2) computers, one server should be designated as the “Primary” with the responsibility of the Primary HMI Server and Primary Data Server. The second computer designated as “Secondary” with the responsibility of the Secondary HMI Server and Secondary Data Server. A “load sharing” configuration where one server is the primary in one role and the secondary in the other role is not recommended. The FactoryTalk Directory server does not require configuration for redundancy. The FactoryTalk Directory information is cached on each computer that is participating in a distributed application. If the FactoryTalk Directory server computer is disconnected from the network or fails, each client and server in the application can continue to access the graphics (from HMI Servers) and tags (from Data Servers) in the application as long as the computer had previously accessed the FactoryTalk Directory server. However, since the FactoryTalk Directory is required to edit the application, it is recommended to place the FactoryTalk Directory on a PC with high availability. Additional Information

• RSView SE User Manual part 2 Chapter 25: Setting up redundancy • RSView SE User Manual part 2 Chapter 26: Deploying distributed applications • AID 27105 - RSView SE 3.1, 3.2 and 4.0 Server Redundancy Guidelines • AID 38160 - RSView SE 4.0 (CPR7+) Server Redundancy Guidelines • AID 28707 - Considerations for returning a restored primary HMI server into service • AID 28707 - Considerations for returning a restored primary HMI server into service • AID 35411 - Method to automatically reboot the secondary SE server after a failover and switchback • AID 27597 - Determine Active and Standby Server Status using the RSView SE Client. Note: the

‘Server Status’ graphic attached to this technote is now located in the RSView SE library files.

System Modification (Updated!)

Runtime Editing Considerations The purpose of the document in the following technote is to identify the types of runtime editing that can be performed on an RSView SE distributed application while still maintaining control of the process. Certain










runtime edits will require some form of re-initialization while other edits or deletions will not be recommended with the current release of the software. AID 32517 - Runtime Editing Considerations with RSView SE Runtime Editing capabilities were significantly improved in CPR7+. See AID 34215 - CPR7+ Runtime Editing improvements, HMI Redundancy replication, and String Spreadsheet editing.

General System Modification Procedure (Redundant & Non-Redundant) • Some tag information is loaded into RAM when the RSView SE services start. Therefore, some tag

database modifications may require: o Server restart/reboot o Client session restart o Client screen refresh

In order for the change(s) to take affect. The integration team should evaluate what modifications may be needed and have a procedure in place to allow for them once a project has been commissioned.

System Modification Procedure on Redundant Servers • Simple Display modifications which do not require new Tag creation can be copied and pasted from

one server to the other without halting the servers. The change will then take effect the next time the screen is displayed.

• Simple Macro modifications which do not require new Tag creation can be copied and pasted from one server to the other without halting the servers. The change will then take effect the next time the macro is executed.

• Simple modifications to Data Log Models, Derived Tag Files, and Event Files which do not require Tag creation can be copied and pasted from one server to the other without halting the servers. Prior to changing these files they should be stopped first, by issuing the following commands:

o DatalogOff <Data Log Model Name> o EventOff <Event file Name> o DerivedOff <Derived Tag Name>

• Once modifications have been completed and saved, then the files need to be restarted by issuing the following commands:

o DatalogOn <Data Log Model Name> o EventOn <Event file Name> o DerivedOn <Derived Tag Name>

• Type the command without the < > around the object name. • HMI Tag Deletion requires halting the server and transferring the project to the other server. All

references to tags must first be removed. This includes all reference used in Display Animation, VB code, Event File, Derived Tag File, and Data Log Model.

• Any Alarm Tag changes which require the use of the “Accept Button” in the Tag Database editor requires halting the server and transferring the project to the other server.





Communications (Updated!) RSLinx Classic (RSLC) and RSLinx Enterprise (RSLE) can both communicate with SLC/PLC/CLX controllers. However, RSLE is the preferred method of communications for RSView SE unless one of the following features of RSLC is needed.

• OPC/DDE Server to non-FactoryTalk applications (requires RSOPC Gateway) • Alias Topic Functionality • Unsolicited Messaging • Complex communication routing. Protocol changing (ex. Ethernet to DH+) • Offline browsing of PLC/SLC RSLogix files

RSLC and RSLE can also co-exist on the same computer at the same time (see the RSLE online help for more information). When designing an application, do not duplicate references to Data Servers (RSLC, RSLE and 3rd Party OPC Servers) in the application. Tags from a single Data Server may be referenced from any HMI project in any area of the application; therefore, it is recommended to place only one Data Server per Area. If a particular physical area in the plant has more than one Data Server (RSLinx for Rockwell controllers and Kepware for a 3rd party controller, for example), create logical “sub-Areas” to separate the two as illustrated below:

For more information, see AID 29663 - RSView SE Area Best Practices.



When planning communications: • Gather information about the types of controllers or devices in the plant, and the software that is

available for communicating with them. • Determine how the programmable controllers on the network will communicate with the application.

This will help plan the number of Data Server needed in the application. • Determine how the application will access data in the controllers or devices. In most instances the

values in controllers or devices can be direct referenced without the need of creating an HMI tag. For certain special instances however, the need to set up an HMI tag database may exist. HMI tags provide extended capabilities, such as:

• Triggering alarms when tag values cross a specified threshold. • Scaling or offsetting a value before sending it to a programmable controller or device. • Security

Data Server allows clients to access information in programmable controllers, devices and other Data Server that comply with the OPC-DA 2.0 specification. RSLinx Enterprise Predefined Items are internal counters and strings that are made available as data items (tags) for diagnostic purposes. These items differ from regular data items in that they access internal information contained in RSLinx Enterprise. The referenced technote includes two RSView graphics containing RSLinx Enterprise diagnostics counters. One graphic contains counters that can be used with ControlLogix family controllers and the other one contains counters that can be used with PLC-5, SLC, and MicroLogix family of controllers. These graphics will import into an RSView ME or SE project. See AID 30148 - Using RSLinx Enterprise Diagnostic Counters - Predefined items

How many tags can RSLinx poll in a given amount of time? There is no straight forward answer to this question. There are many factors involved, some of which are:

• The computer hardware that the data server (RSLinx Classic or Enterprise) is running on. The more memory and the faster the processor, the better.

• Additional CPU loading from other software running on the same computer. Even if the multiple software products are compatible to run on the same PC, you may be hurting your performance by having them fight for PC resources. Use Task Manager or Perfmon to monitor for resource hogs. Those software packages may need to be moved to another PC to improve the over all performance.

• Other software packages communicating to the controllers from the same or different PC. Batch or Recipe packages doing uploads or downloads.

• The network the data will be polled over (Ethernet, ControlNet, DH+, DH-485, Serial, Dial-up, etc.). There are physical and practical limits to how much data a network can transmit. Additional research may be needed for your specific design.

• The number of controllers the data server will need to communicate with. Just as in conversations, it is easier and more productive for you to call one person for a lot of information then it would be for




you to call fifty people for only a little bit of information each. That is one reason why a data concentrator controller may be beneficial or needed.

• The type of controllers. Some of the newer Logix brand controllers have been developed with networking optimization in mind and therefore perform better then others.

• How the controller program is written. Are the tags or data points optimized in the controller to be in consecutive blocks or are they scattered randomly throughout the controller? Are they in arrays?

• How the controller is configured. In the Logix family of controllers you have the ability to tune the communication time slice. This determines how much time is used for communication processing. You must be sure not to increase this value too much so that it does not impact on the scan time of the controllers program. Or use periodic tasks which allow blocks of communication time instead of interrupted small chunks of communication time.

RSLinx Classic vs. RSLinx Enterprise vs. 3rd Party OPC When designing an application, do not duplicate references to Data Server (RSLinx Classic, RSLinx Enterprise and 3rd Party OPC Servers) in the RSView SE application. Tags from a single data server may be referenced from any HMI project in any area of the application. Place all Servers (HMI and Data) in their own individual Areas. AID 29663 - RSView SE Area Best Practices. RSLinx Classic:

• Applications containing more then 10,000 active tags on scan may require its own dedicated host computer. This is dependent on hardware performance.

• When using Alias Topics never use “Switch on Error” when communicating to ControlLogix processors. AID 26228 - Using RSLinx Alias Topic "Switch On Error" and "Switch On Command"

• Can communicate with SLC/PLC/CLX controllers (including PLC-2, PLC-3 and PLC-5/250) • Complex communication routing. Protocol changing (ex. Ethernet to DH+) • Can server OPC data

RSLinx Enterprise:

• RSLinx Enterprise is optimized to provide the best performance for large numbers of clients (more than 10), and large number of tags (more than 10,000), even if located on the same computer as the HMI server.

• Can communicate with SLC/PLC/CLX controllers (excluding PLC-2, PLC-3 and PLC-5/250) • Can serve OPC data with the addition of RSOPC Gateway • Preferred RSView SE data server to Rockwell controllers

3rd Party OPC servers

• Applications containing more then 10,000 active tags on scan may require its own dedicated host computer. This is dependent on hardware performance.




RSLinx Classic Remote OPC Server must be selected under the "OPC Server name (ProgID):" when configuring RSLinx as an OPC Data Server in RSView SE. Regardless of where the actual copy of RSLinx.exe is running the "RSLinx Remote OPC Server" option must be selected in order to prevent problems accessing OPC Topics. To better understand what is remote vs. what is local, the Data Server should be viewed from the SE Client point of view and not the HMI Server. In most cases Data Servers will be remote from the SE Client point of view. In the rare case where an SE Client may host a Data Server, using the "RSLinx Remote OPC Server" configuration will not cause any problems.

RSOPC Gateway • RSOPC Gateway is an OPC server that enables OPC clients to connect to FactoryTalk applications that

contain RSLinx Enterprise and RSView Supervisory Edition servers. By doing so, they can access tag data within those applications.

• It is OPC Version 2.05 compatible. • RSOPC Gateway Station is for use on stand-alone, local applications. • RSOPC Gateway Distributed is for FactoryTalk network applications. • Only one RSOPC Gateway can be installed per computer. • Multiple RSOPC Gateways can point to a single FactoryTalk application. • RSOPC Gateway can only point to a single FactoryTalk application at a time. • RSOPC Gateway can communicate to as many unique tags as licensed. • 20 remote OPC clients have been formally tested and validated against RSOPC Gateway. • RSOPC Gateway v2.00, released in CPR 7, must be used with RSLinx Enterprise V4.00 and RSView

SE/ME V4.00 also released in CPR 7 • Additional information can be found in the RSLinx Enterprise Getting Results Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/gr/lnxent-gr001_-en-p.pdf

RSLinx Classic with a Logix Controller Please be aware that there are known issues when online editing or downloading to a Logix Controller, particularly when RSLinx Classic is being used as the Data Server. If a client application requests tag data, RSLinx Classic will group the tags into packets, and put these packets on scan with the controller(s). If an online edit or download causes a change to the controller’s data table for a data packet on scan, the packet may need to be taken off scan, and put back on scan for the changes to be reflected. This may be as minor as navigating off a particular HMI Display to take the tags off scan, and then navigating back to the display; however, in larger, distributed applications (particularly with alarms, event detection, data logging, etc. all enabled), it may be operationally difficult to achieve this short of rebooting the RSLinx Data Server. This would obviously affect ANY client requesting data from this instance of RSLinx Classic. Many of these issues have been addressed with RSLinx Enterprise, which was designed specifically for the Logix family of controllers, and why RSLinx Enterprise is the recommended Data Server for this platform. RSLinx Classic was originally designed for the structured data tables of the SLC and PLC product lines. The Logix platform introduced new communication and memory performance parameters that can affect RSLinx



Classic. For this reason, RSLinx Enterprise was designed to be the preferred communication server for the Logix platform. Please consult the local Rockwell account representative for a complete comparison. AID 30605 - Runtime Editing with RSLinx Classic and Logix Processors

Security You can set up security to:

• Prevent writes to specified tags from the RSView SE Client. • Prevent access to specified displays from the RSView SE Client. • Prevent access to specified commands from the RSView SE Client. • Prevent changes to the application from RSView Studio or the RSView Administration Console.

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. In addition to security settings mentioned above for individual users, DCOM and ODBC system security settings may also need to be configured for distributed configurations.

FactoryTalk Security (Updated!) FactoryTalk Security authenticates user identities and authorizes user requests to access a FactoryTalk-enabled system. These security services are fully integrated into the FactoryTalk Directory and are included as part of the FactoryTalk Automation Platform. FactoryTalk Security includes user authentication that determines who can open, create, modify, and delete application components, and on which computers the actions are allowed. You also use FactoryTalk Security to add user and group security accounts as well as Windows-linked accounts, and set up security for common actions such as tag writes, open, and delete. To open the RSView User Accounts editor or the Secured Commands editor, the user requires access to the Common/Create Children action, in addition to the Common actions, Configure Security, List Children, Read, and Write, on the area or application.

• FactoryTalk Security Technical Data http://literature.rockwellautomation.com/idc/groups/literature/documents/td/rsas-td001_-en-p.pdf

• FactoryTalk Security Product Profile http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/rsas-pp001_-en-p.pdf

• AID 30980 - FactoryTalk Security - Tips and Best Practices



http://literature.rockwellautomation.com/idc/groups/literature/documents/td/rsas-td001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/rsas-pp001_-en-p.pdf


Access to Open an Application To open an application in RSView Studio, the user must have read/write access to the sub-folder that holds the HMI projects. If, for example the security designation for RSView Studio users is Power Users, they will not necessarily have write access. To make sure that the settings for Power Users are correct, navigate to the sub-folder that holds the HMI projects; right-click; select Properties. Refer to “Default File Locations for SE Distributed Applications” earlier in this document for folder locations. In the Security tab of the Properties dialog, select Power Users from the list of groups and user names. In the Permissions box below the list, select Full Control and check the Allow check box. Additional information: AID 26251 - DCOM Security Settings for RSView SE Remote Logging AID 29103 - Virtual Private Networking (VPN) Connections for Remote Communications Across the Internet AID 29962 - Rockwell Automation Network Security for Control Systems White Paper








Windows Terminal Services RSView SE 4.0 fully supports Windows Server 2003 Terminal Services, see technical notes AID 29919 - Using RSView SE with Windows 2003 Terminal Services and AID 33116 - Using FactoryTalk Security and Terminal Server Clients with CPR7.

• Terminal Services is a standard feature built into the Windows Server family (Server, Advanced Server, and Datacenter Server) which provides remote access to servers from practically anywhere in your enterprise. It is a transparent system that runs applications and performs data processing and storage functions on the server computer to minimize the amount of information traveling across your network. While multiple sessions run on a single server, each user can only see their individual session. User's desktops are transmitted to clients for display using terminal emulation software. Similarly, the software sends print streams and command functions such as keyboard inputs and mouse clicks across the network between the client and the server.

• For a computer to be a Terminal Services client, it only requires an operating system and the Terminal Services client software. No other software (not even a web browser) is required. For this reason, these clients are known as “thin” clients.

• Since minimal software is needed on the client computer and all the processing is done on the server, client computer hardware can be scaled down to reduce cost.

Time Synchronization (Updated!) Time synchronization is critical for the proper operation of many Windows services in a distributed computing environment and highly recommended for RSView SE systems. The Windows Time service uses the Network Time Protocol (NTP) to synchronize computer clocks on the network so that an accurate clock value, or time stamp, can be assigned to network validation and resource access requests.

• In workgroup environments, configure the Windows Time server (using W32tm.exe) to synchronize all the SE computer clocks to an authoritative time server (e.g. the FactoryTalk Directory).

• In domain environments, each computer should be automatically configured for the appropriate authoritative time server the when they join the domain.

In either case, check the Event Viewer System log of each computer to verify that the time is being updated properly.

Windows Time Service Technical Reference http://technet2.microsoft.com/WindowsServer/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true

Administering the Windows Time Service http://technet2.microsoft.com/WindowsServer/en/library/ac86e77c-0be3-430a-ba0b-c2225506fc4f1033.mspx?mfr=true How to configure an authoritative time server in Windows Server 2003 http://support.microsoft.com/kb/816042






http://technet2.microsoft.com/WindowsServer/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true



http://technet2.microsoft.com/WindowsServer/en/library/ac86e77c-0be3-430a-ba0b-c2225506fc4f1033.mspx?mfr=true

http://technet2.microsoft.com/WindowsServer/en/library/ac86e77c-0be3-430a-ba0b-c2225506fc4f1033.mspx?mfr=true

http://support.microsoft.com/kb/816042

How to configure an authoritative time server in Windows XP http://support.microsoft.com/kb/314054/ How to configure an authoritative time server in Windows 2000 http://support.microsoft.com/kb/216734/

HMI Tags and Direct Referenced Tags

Tag related limits • An HMI Server supports 40,000 alarmed tags, 10,000 of them can be analog • Each graphic display can contain up to 3,000 references to expressions or tags (HMI and Direct). This

limit includes the tags contained in embedded variables.

Tag Database (HMI Tags) • Very useful when creating similar controls. Parameter files can reference directory folder structure or

tags for quick duplication of controls • Easy to do Tag Replacement (search and replace) • HMI tags must be used (that is, Direct Referenced tags can not be used) for any of the following

components in the application o Alarms o Security (can not set security to Direct Referenced tags) o Data manipulation (if the OPC Data Server does not provide: scaling, offset values, setting

minimum or maximum limits on values) • For optimum performance, do not place all the HMI tags in the root folder. It is also recommended that

you limit the number of tags in a folder to less than 1000. HMI tags contained in nested folders do not contribute to the number of tags in the root of the folder. AID 29266 - Large numbers of HMI Tags within a single Tag DB folder can cause slow object animation performance when opening screens

Direct Referenced Tags • No need to build or create a tag database since tags are directly referenced from the controller • Parameter files can be used with Direct Referenced Tags • Tag Replacement can be used with Direct Referenced Tags

Alarm Acknowledge Bit The acknowledge bit is used for telling other RSView applications or controllers that a tag has been acknowledged. When an acknowledge bit for a tag is set up, all HMI servers automatically monitor that bit at run time. When an operator acknowledges an alarm for the tag, the acknowledge bit is set. All other HMI servers then acknowledge the alarms associated with that bit. This means operators can acknowledge an alarm in one application and have it recognized in other applications (i.e. global alarm acknowledge between applications).


http://support.microsoft.com/kb/314054/

http://support.microsoft.com/kb/216734/



One acknowledge bit can be setup for each tag, one for a group of tags or one for all tags. The more acknowledge bits that are set up, the greater the system overhead. If possible group alarms to share an acknowledge bit. A burst of alarms or alarm acknowledges will induce a high amount of read/write traffic over a very short period of time. Acknowledge bits as well as Handshake bits should be accounted for when determining the total number of tags on scan.

Calculate number of tags on-scan To calculate the maximum number of tags that could possibly be on-scan from a Data Server (ex. RSLinx) add all of the following: (if a tag is used in multiple places it only counts once)

• Tags on graphics being displays (or have been displayed if displays are configured to cache and always update)

• Alarm and Alarm Acknowledge tags • Tags in Derived tag equations (only derived files running) • Tags in Event files (only event files running) • Tags in Data Logs Models (only models that are running) • Handshake tags • Tags that Macros or VBA are Reading or Writing to • Also take into consideration other applications like RSSql and RSBatch that may be using the same

Data Server

Data Log Data log is an RSView component that collects and stores tag values. Using a Data Log Model, you specify which tag values to collect, when to collect them, and where to store them. When planning data collection, design the system so only essential data is collected. Limiting data collection is important because collection activities require substantial processing power and generate significant traffic on the communication channel or network. Keep data collection requirements in mind when designing the layout of the programmable controller data tables and the tag database. Ideally, tag addresses should reference contiguous blocks of programmable controller data tables to reduce network traffic and optimize system response. In a redundant SE system it is suggested to log to a third computer as opposed to locally, in doing this there is only one location to manage the data and there is no need to merge multiple files or databases together after a failover or switchover.

Data Logging to Secondary Path RSView lets you specify a secondary or backup path to use if the primary path for file sets or the ODBC database becomes unavailable. This could happen because of network failures or because of lack of disk space on the computer where the data is being logged.


If the primary data log location becomes unavailable, RSView begins to store the data in a buffer. The buffer can hold up to 64 Kb of data. If the primary location is still unavailable when the buffer fills, or when the maximum amount of time to buffer data has elapsed, RSView switches to the secondary path. RSView checks periodically to determine whether the primary file path has become available again. If it has become available, RSView switches back automatically. If both paths are unavailable, RSView buffers the data. If the buffer fills and both paths are still unavailable, RSView empties the buffer (the data in the buffer is lost) and begins storing new data in the buffer. RSView continues checking both paths until one becomes available.

Multiple data log models At run time, up to 20 models can run simultaneously on each RSView SE Server. Use multiple data log models to:

• Store related information in separate file sets • Log groups of tags at different rates • Log groups of tags based on events

Data Log Storage Formats Logged data is stored in either an internal file set, providing faster performance for historical trends, or in an ODBC compliant database. If a file set is used, tag values are stored in proprietary format files. Trend objects can read the data to plot in a graphic display. If values are stored to an ODBC compliant database, it is highly recommended that this be a separate database server and not an SE Server. Data can be viewed in third party ODBC compliant tools such as Microsoft Excel, Seagate Crystal Reports or Rockwell Software RSBizWare Historian. If the ODBC database becomes inaccessible, RSView logs the data to backup files in proprietary format. The location of backup files is configurable.

Trending • When planning trends, consider how they will be used. For example, will the trend be used to:

o Analyze process trends o Monitor production efficiency o Archive process variables to ensure compliance with government regulations

• Based on such considerations, it can be determined: o Which tags need to be plotted on the same trend o Which tags need to be plotted from a data log model o Which tags need to be plotted against time, or against another tag

• Trends can display real-time or historical data with up to 100 pens (tags) in each trend. • Trend Templates may be used to create preconfigured trend objects for use in graphic displays.


• Trend Snapshots may be used as overlays with real-time trends. Graphic displays that contain trend objects created in previous versions of RSView Studio, need to be opened in RSView Studio 4.0 and saved to ensure that they work correctly at run time.

Database Considerations Often times RSViewSE data logging, RSSql data logging or RSHistorian reporting get blamed for being slow when it is truly the fault of the database. In the beginning the system starts up and performs well, but as the database grows the performance degrades. The larger a database gets, the longer it takes for SQL queries to execute. Report generation will also be impacted as the size of the database grows. Proper database management will be required to maintain a responsive reporting system. Server hardware will also play an important roll in the responsiveness of the database. Additional information:

• SQL-Server-Performance.Com • Microsoft SQL Server 2000 Operations Guide • Oracle DBA Information

Language Switching Language switching allows operators to view user-defined text strings in an application, in up to 20 different languages. At run time, in a distributed application, multiple RSView SE clients can switch between any of the languages the application supports. Multiple clients can also run in different languages, at the same time. AID 32713 - RSView SE Language Switching Quick ReferenceAID 32569 - Creating multiple alarms in multiple languages in RSView Studio 4.00

Global Objects A Global Object is an object that is created once and can then be reference multiple times on multiple displays in an application. When you make changes to the original (base) object, the copies (reference objects) are changed as well. AID32867 - RSView 4.00 Global Objects FAQAID32665 - RSView 4.00 Working with Global Objects

Graphic Displays Develop hierarchy of displays with each display giving more granular detail of an object, area or function. This prevents displays from being cluttered by attempting to display a large amount of information at one time. This also reduces the demands on the Data Server from having to poll and display a large amount of unnecessary data. Create templates to ensure consistency of appearance.


http://sql-server-performance.com/


http://www.dba-village.com/dba/village/dvp_base.main





Each graphic display can contain up to 3,000 references to expressions or tags (HMI and Direct). This limit includes the tags contained in embedded variables. When importing a large graphic object (*.jpg, *.bmp) to use as a background. Converting the object to wall paper will allow smoother mouse control over the object and provide a better environment for developing the graphic. It also saves memory for faster display of screen.

Importing and Exporting Graphic Display XML Files Each graphic display’s information is contained in a file called DisplayName.gfx. The Graphics Import Export Wizard in RSView Studio allows you to export this information to an XML file, or to import a graphic display XML file. The XML files can be edited to modify objects that already exist or to add new objects. You can not import or export a display that is currently open in the same instance of RSView Studio that you are attempting to import or export from. Having the display open in a second or remote instance of Studio will not cause it to fail. However if you have an older version of a display open and save it after the import has been done you will over write your imported changes. For more information about importing and exporting graphic display XML files, see Appendix E, Importing and exporting XML files, in the RSView SE User Manual Volume 2

ActiveX Components An ActiveX object is a software component that is supplied independently from RSView through products such as Microsoft® Office XP, Visual Basic®, and many other third-party applications. An ActiveX object gives you access to its features through the object’s properties, events, and methods. By embedding an ActiveX object in an RSView graphic display and then assigning properties or specifying handlers for the object’s events, the object can interact with RSView. Information is passed between an ActiveX object and RSView using RSView tags. For example, you can embed the Microsoft Forms ActiveX objects in RSView graphic displays. If you attach an RSView tag to an ActiveX object’s Value property, the object’s behavior changes as the tag’s value changes. Be aware that ActiveX versions may very based on the operating system and in turn may not work properly. For example if the Server is running Windows 2003 and the Client is Windows XP the installed ActiveX components may be different. This is only a concern if you have imbedded ActiveX components in an RSView graphics or a VBA form. AID 29730 - How to register an ActiveX control in Win32 Windows 2000/XP computer




Visual Basic for Applications

You can use Visual Basic for Applications (VBA) to customize and extend the capabilities of RSView SE. RSView graphic displays include the ability to incorporate Microsoft Visual Basic for Applications (VBA) scripts. Use the VBA integrated development environment (IDE) to create, test, and debug VBA procedures that run in response to events triggered from within RSView graphic displays.

• VB third-party access to the RSView Display Client object model, which includes the Tag and Graphic object models, is currently not supported. Access to the RSView object model is available only within the RSView SE client’s VBA.

• Limited support is available through Rockwell Automation Technical Support for customers needing assistance debugging their VBA scripts. A maximum of 20 lines of code per problem can be considered.

• The version of Visual Basic for Applications that is supported by RSView for its object model, has been updated from 6.3 to 6.4 (VBA 6.4 for RSView versions 3.2 and 4.0)

• Use of custom VBA code should be limited. Only use when a native feature of the product does not meet the necessary requirements.

• VBA is single threaded. • VBA is not recommended for continuous calculations. For continuous calculations the use of an OCX

or EXE is recommended only if derived tags are not suitable. • VBA is not compiled code.

Additional information:

• AID 30399 - Recommendations For Writing Visual Basic for Applications in RSView SE • AID 30478 - RSView SE 3.0 Client Object Model

RSView Enterprise Tools • Application Manager is software for moving, copying, renaming, backing up, and restoring

applications. • DeskLock is software that locks users in the RSView SE Client program and prevents them from

having access to the Windows desktop and using Windows system keys. • RSView SE Administration Console is software for administering RSView Supervisory Edition

applications after they have been deployed. • RSView SE Service Manager is a tool for starting and stopping HMI servers. For example, use this

tool to stop an HMI server before copying its set-up files to a redundant server. • SE Alarm Log Viewer is software for viewing the contents of alarm log file sets. • Tag Import and Export Wizard is software for importing or exporting the RSView SE Server’s tag

database.




Naming Components • RSView supports long file names. File names, including the path can be up to 200 characters long. For

example a graphic with the name “System Overview” has 15 characters in it but has 118 characters in its full name because of the directory structure “C:\Documents and Settings\All Users\Documents\RSView Enterprise\SE\HMI Projects\My Application\Gfx\System Overview.gfx”

• Names that conflict with commands and macros: To avoid problems when issuing commands and macros, do not use command names to name macros. For example, say you wanted to name a macro Display. To avoid confusion with the Display command, name the macro DisplayScreen or MyDisplay instead.

Overall Considerations • The browse button appears beside data entry fields. Type information into the field or click the browse

button to open a list containing valid entries for the field. Using the brows button will prevent typographical errors from requiring a debug later in the application development.

• During the design phase and before the development portion of the project, talk to the operators, maintenance personnel and other experts who are going to use the system. Find out what information they need to optimize plant operations to allow for efficient design and implementation of the application.

• Keep update rates only as fast as necessary for the processes like Tag Read/Write, Data Logging, Derived Tags or Events. Their update rates are important and can have a direct influence on the performance of the HMI server and clients. The update rate is also influenced by the rate that the tag in the target device changes.

• When creating graphic screens, selecting ‘Replace’ will cause the currently displayed screen to close while opening the newly requested screen. If you select ‘Overlay’ you need to be sure to manage them more closely. It is possible for multiple screens to be open one on top of the other using up memory and CPU resources unnecessarily. See the online Help for more information.


HMI startup components (services) have two options, ‘On Demand’ and ‘Load and run startup components when operating system initializes’. This setting can be accessed in Studio or the Administration Console by right mouse clicking on the HMI server icon and selecting properties. In general ‘On Demand’ is selected during development so that all the services do not startup every time the computer is started. Once the system is deployed it should be set to ‘Load and run startup components when operating system initializes’.

• When using10/100Mb Network Interface Cards (NICs) and switch ports, do not leave them at auto detect. Set them at 100Mb / Full Duplex unless communicating to older 10Mb hardware, in that case set the speed at 10Mb and not 100Mb. Leaving network ports at ‘Auto’ and the NICs at hardware defaults may degrade network throughput dramatically.

• Ghosting may be used in order to be more efficient in setting up a large system. However, this may cause an issue with communications due to duplicate serial numbers. AID 30727 - Ghosting / Imaging multiple computers with RSLinx Enterprise will cause serial number duplication problems and will require registration modification

How to determine what SE projects load when O/S initializes HMI servers in a distributed RSView SE project can be configured to launch in one of two ways:

• On demand, when a client attempts to make a connection to them, or • Load and run when the operating system initializes

This selection is made in each HMI server's "Properties". Over time, as new projects are developed and tested, it can be easy to forget which HMI servers are automatically running every time the computer starts. Since each HMI server uses memory, CPU time and Activations, this becomes an increasing burden on the computer. To determine which HMI Servers are loading automatically, open the following file: C:\Documents and Settings\All Users\Documents\RSView Enterprise\SE\HMI Projects\SLHMIServers.XLM. (default location) If it can't be found, that means that all of the HMI projects are configured to run On Demand. The first time one of the projects is configured to “Start On Boot”, the XML file will be created. Another way to force the XML to be created is to change the startup setting from "On Demand" to "Load and run startup components..." and immediately back to "On Demand", and then click Apply/Ok. The above applies to all RSViewSE versions 3.0 and above. Additional information can be found in Answer ID’s:

• AID 26334 - How to determine what SE projects load when O/S initializes, and how to prevent them from loading automatically

• AID 24896 - RSView Studio is unable to attach to an existing HMI server • AID 27207 - Renaming an RSView SE application causes it's HMI Servers to lose it's startup properties









Designing A Multi-User System When an application is run by multiple users, behavior which is appropriate in a single-user environment might not be appropriate. For example, if a graphic display that is running on several clients contains a shutdown macro that stops a derived tags file. When the display is closed on one client, the shutdown macro will stop the derived tags file. This would affect the display on the other clients, because the derived tags file resides at the server. This would be true of all server side components like Alarming, Data Logging and Derived Tags.

Languages • Do not install a local language version of RSView SE (German, French or Japanese) on an English

Operating System (Windows 2000, XP Pro or Server 2003 Standard Edition) or errors may occur. AID 31338 - Local language RSView SE 3.20 is not supported on an English OS

• RSViewSE has been tested on English versions of Windows with US settings. Should other configurations encounter issues, please report them to Technical Support.

Misc. Procedure • Before any Tags are deleted from the online ControlLogix Tag Database, they must first be removed

from RSView SE Application. This includes all reference used in Tag Database, Display Animation, VB code, Event File, Derived Tag File, and Data Log Model. This will remove tags from the scan list and prevent communication errors that can disrupt the performance of the application.

• Frequently users want to monitor the utilization and performance of the various components of an RSView SE system and be automatically alerted if a process begins to consume too many system resources. For information on how to accomplish this refer to technote AID 31196 - Monitoring RSView SE memory and CPU usage using Performance Monitor

RSView32 to RSView SE Conversions Based on RSView32 v7.0 and RSView SE v3.10 The following objects won't convert from RSView32 to RSView SE:

• VBA • Native trends • Tag monitors • Command lines embedded in graphics • External applications that depend on RSView32 to be an OPC or DDE Data Server • Alarm Summaries

Certain ActiveX controls may not function as they did in RSView32. These will need to be evaluated on a case by case basis. To migrate an RSView32 project to an RSView Enterprise distributed application, do not use the Attach option. Instead, create a new HMI server by importing the project. To do this, select 'Import a project' in the Select Operation window of the Add HMI Server Wizard. Then in the Import Project window, select RSView32 as the project type and specify the path to the RSView32 project file.






For a complete list of commands that can not be executed in RSView SE refer to Technotes:

• AID 27708 - RSView32 to RSView SE upgrade issues • RSView32 to RSView SE Migration Considerations

ControlLogix Redundancy (v13 and above) (Updated!)

Automatic IP Address Swapping During a switchover, 1756-ENBT and 1756-EWEB modules now swap their IP addresses with their partner modules in the other redundant chassis. This allows the Data Server to use the same IP address to communicate with a primary module regardless of which CLx chassis is the primary.

• Typically, you no longer need to use ControlLogix Redundancy Alias Topic Switcher software to manage the IP addresses. If your application still requires alias topics to manage IP addresses, see ControlLogix Redundancy System User Manual, publication 1756-UM523.

• In a ControlLogix redundant configuration, when the controller fails over to the secondary chassis the IP address of the ENBT is swapped with the module in the primary chassis. RSLinx Enterprise can take > 32 seconds to recognize this change. See AID 34952 - HOTFIX: RSLinx Enterprise CPR7 - ControlLogix redundancy switchover and AID 31520 - Understanding HMI Switch Overtimes when using Ethernet/IP Swapping and ControlLogix Redundancy.

• If you need bumpless communication between Data Servers and CLx controllers, use a separate ControlNet network that is dedicated to communication with those devices.

In a redundant system, use an Ethernet/IP network only for HMI/workstation communication and messaging. Do not use an Ethernet/IP network for:

• communication with I/O modules • communication between devices via produced/consumed tags

Tricks and Tweaks • AID 22007 - How to trigger a command on an SE client from an HMI server • AID 29298 - How to play an SE client wave file triggered off of an alarmed tag • AID 31307 - How to AppStart the Windows "User Account" Manager from RSView32/RSViewSE • AID 33075 - How to print a text file using VBA and Notepad • Automatic logout of FactoryTalk. AID 32566 - Studio seems unresponsive and generates: The

requested Access Check failed because the token has expired.



http://www.software.rockwell.com/download/extranet/manual/products/operate/rsviewenterpriseseries/@SellingTools/RSView32%20to%20RSView%20SE%20Project%20Migration.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um523_-en-p.pdf











Tools and Utilities • AID 30393 - Patch File Validator Utility* • AID 31196 - Monitoring RSView SE memory and CPU usage using Performance Monitor • AID 30148 - Using RSLinx Enterprise Diagnostic Counters - Predefined items • AID 30310 - RSView SE - Backup and Restore Utility for HMI Server • AID 30498 - Windows Firewall Configuration Utility for Windows XP Service Pack 2 • AID 29942 - RSView Graphic Tags Search and Replace using Graphics XML Exported Files • AID 30956 - Microsoft Network Diagnostic Tools for Ethernet • AID 20697 - Troubleshooting a Windows Network • AID 31073 - Tool for collecting Event log files

Additional Reference Links

FactoryTalk • AID 89650958 - FactoryTalk Automation Platform 1.08.00 Patch TOC • AID 124735843 - FactoryTalk Automation Platform 2.00 Patch TOC

RSView SE • RSView Supervisory Edition Install Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewse-in003_-en-p.pdf • RSView Supervisory Edition User's Guide Volume 1

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um004_-en-e.pdf • RSView Supervisory Edition User's Guide Volume 2

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewse-um005_-en-e.pdf • AID 29184 - RSView SE 3.20.00 Patch TOC • AID 32380 - RSView SE 4.00.00 Patch TOC • AID 20450 - RSView SE Operating System and Service Pack compatibility • AID 27105 - RSView SE Server Redundancy Guidelines • AID 23120 - Applying RSView SE in a 21 CFR Part 11 environment • AID 34321 - Using RSView SE with multiple monitors • AID 33103 - SE Client displays the message "You do not have security privileges to access this

application ..."

RSView ME • RSView Machine Edition Install Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewme-in003_-en-p.pdf • RSView Machine Edition User's Guide Volume 1

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewme-um004_-en-e.pdf











http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewse-in003_-en-p.pdf











http://literature.rockwellautomation.com/idc/groups/literature/documents/in/viewme-in003_-en-p.pdf


• RSView Machine Edition User's Guide Volume 2 http://literature.rockwellautomation.com/idc/groups/literature/documents/um/viewme-um005_-en-e.pdf

• AID 29187 - RSView Machine Edition 3.20.00 Patch TOC • AID 32381 - RSView Machine Edition 4.00.00 Patch TOC • AID 32590 - ME to SE Conversion revision 4.0

RSBizWare • RSBizWare Historian User's Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/hist-pp001_-en-p.pdf • RSBizWare PlantMetrics User Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/pltmt-pp001_-en-p.pdf • RSBizWare Scheduler User's Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/sched-um001_-en-p.pdf • RSBizWare RSSql User's Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/rssql-um001_-en-p.pdf • RSBizWare Batch User's Guide

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/batch-um008_-en-p.pdf • AID 24359 - Data Archiving with Historian and PlantMetrics • AID 33118 - Data Archiving with Historian and PlantMetrics - Version 7.5 and Later

Communications • AID 22199 - RSLinx Classic Service Pack/Hotfix TOC • AID 32383 - RSLinx Enterprise 4.00 Patch TOC • AID 29191 - RSLinx Enterprise 3.00 Patch TOC • AID 26464 - RSLinx Internals: OPC/DCOM timeouts when a remote client is disconnected • RSOPC Gateway information can be found in the ‘RSLinx Enterprise Getting Results Guide’


ControlLogix • AID 6408 - Logix Data Collection Application Guide • ControlLogix Redundancy System User Manual

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um523_-en-p.pdf • ControlLogix Data Collection with RSLinx

http://www.software.rockwell.com/download/comms/rslinx/clx_perf.zip • Logix 5000 Controllers Design Considerations

http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm094_-en-p.pdf • ControlLogix Redundancy System Revision 13

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1756-rn608_-en-e.pdf






http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/hist-pp001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/pp/pltmt-pp001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/sched-um001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/rssql-um001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/batch-um008_-en-p.pdf









http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um523_-en-p.pdf

http://www.software.rockwell.com/download/comms/rslinx/clx_perf.zip

http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm094_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/rn/1756-rn608_-en-e.pdf

Security • AID 29103 - Virtual Private Networking (VPN) Connections for Remote Communications Across the

Internet • AID 29962 - Rockwell Automation Network Security for Control Systems White Paper

Microsoft • Microsoft TechNet article on Domain Controllers

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.mspx • How To Register an ActiveX Control (.ocx) Manually • Maximize Data Throughput Setting for Performance • Microsoft’s Description of Performance Options in Windows • Log Parser

General • Optimizing Windows 2000 for Data Throughput • AID 20440 - Compatibility Matrix of RSI/AB software on Windows XP Pro • AID 28293 - Compatibility Matrix of RSI/AB software on Windows XP Pro Service Pack 2 • AID 27743 - RSI Products and Intel Hyper-Threading Technology • Additional Rockwell Automation online manuals

http://literature.rockwellautomation.com/idc/groups/public/documents/webassets/browse_category.hcst





http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.mspx

http://support.microsoft.com/default.aspx?scid=kb;EN-US;146219


http://support.microsoft.com/?kbid=259025

http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en

http://windows.about.com/od/customizingwindows/l/aa001008a.htm




http://literature.rockwellautomation.com/idc/groups/public/documents/webassets/browse_category.hcst