Administrator's Guide: Power Xpert Software 2.2

MN02601006E

Administrator’s Guide: Power Xpert Software 2.2

Power�Xpert�Software�Administrator's�Guide

Power�Xpert�Software�Administrator's�Guide

Publication date 7/2011

Copyright © 2011 by Eaton Corporation. All rights reserved.

Specifications contained herein are subject to change without notice.

Power Xpert is a registered trademark of Eaton Corporation.

EATON CORPORATION - CONFIDENTIAL AND PROPRIETARY NOTICE TO PERSONS RECEIVING THIS DOCUMENT AND/OR TECHNICAL INFORMATION THIS DOCUMENT, INCLUDING THE DRAWING AND INFORMATION CONTAINED THERE-ON, IS CONFIDENTIAL AND IS THE EXCLUSIVE PROPERTY OF EATON CORPORATION, AND IS MERELY ON LOAN ANDSUBJECT TO RECALL BY EATON AT ANY TIME. BY TAKING POSSESSION OF THIS DOCUMENT, THE RECIPIENT AC-KNOWLEDGES AND AGREES THAT THIS DOCUMENT CANNOT BE USED IN ANY MANNER ADVERSE TO THE INTERESTSOF EATON, AND THAT NO PORTION OF THIS DOCUMENT MAY BE COPIED OR OTHERWISE REPRODUCED WITHOUTTHE PRIOR WRITTEN CONSENT OF EATON. IN THE CASE OF CONFLICTING CONTRACTUAL PROVISIONS, THIS NOTICESHALL GOVERN THE STATUS OF THIS DOCUMENT.

DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY

The information, recommendations, descriptions and safety notations in this document are based on Eaton Corporation’s (“Eaton”)experience and judgment and may not cover all contingencies. If further information is required, an Eaton sales office should beconsulted. Sale of the product shown in this literature is subject to the terms and conditions outlined in appropriate Eaton sellingpolicies or other contractual agreement between Eaton and the purchaser. THERE ARE NO UNDERSTANDINGS, AGREEMENTS,WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE OR MER-CHANTABILITY, OTHER THAN THOSE SPECIFICALLY SET OUT IN ANY EXISTING CONTRACT BETWEEN THE PARTIES.ANY SUCH CONTRACT STATES THE ENTIRE OBLIGATION OF EATON. THE CONTENTS OF THIS DOCUMENT SHALL NOTBECOME PART OF OR MODIFY ANY CONTRACT BETWEEN THE PARTIES.

In no event will Eaton be responsible to the purchaser or user in contract, in tort (including negligence), strict liability or otherwise forany special, indirect, incidental or consequential damage or loss whatsoever, including but not limited to damage or loss of use ofequipment, plant or power system, cost of capital, loss of power, additional expenses in the use of existing power facilities, or claimsagainst the purchaser or user by its customers resulting from the use of the information, recommendations and descriptions con-tained herein.

Table�of�ContentsI. PXS Installation and Configuration ................................................................ 1

About This Manual ................................................................................ iiiHardware and Software Requirements ..................................................... 5

Hardware Requirements ................................................................. 5Software Requirements .................................................................. 5Third Party Software Installed with PXS ........................................... 6Firewall Settings ............................................................................ 7

PowerNet Device Server ........................................................ 7Remote PowerNet Domain Server ........................................... 8Shutdown Agent .................................................................... 8Remote Database Support ..................................................... 8SQL Server Considerations .................................................... 8

SQL Server Account Considerations ................................................ 8Browser Settings ........................................................................... 8Remote Desktop Considerations ..................................................... 9Network Considerations ................................................................. 9Microsoft Sharepoint ...................................................................... 9

Installation .......................................................................................... 11Installation Scenarios ................................................................... 11PXS Installation ........................................................................... 12

If You Have a Version 2.0 Installation of PXS... ........................ 12Installing Under Windows Server 2008 or Windows 7 ................ 12Installing the PXS Application ................................................ 12

Database Deployment .......................................................................... 19About the Deployment & Validation Utility ....................................... 19

Launching the Deployment & Validation Utility ......................... 20Initial Deployment & Validation ...................................................... 20

Windows Groups ................................................................. 20Configure IIS ....................................................................... 21Firewall Ports ...................................................................... 22Database ............................................................................ 23Summary ............................................................................ 25

Microsoft Internet Explorer Settings ........................................................ 27Accessing the PXS Web Application from a Server .......................... 27

Security .............................................................................................. 29Where is Security Information Stored? ............................................ 29Read and Write Users .................................................................. 29

Read Users Group Permissions ............................................. 29Write Users Group Permissions ............................................. 29Creating the Users Groups Manually ...................................... 30

Local Security Settings and Web Clients ......................................... 30Connecting Web Clients ............................................................... 31Configuring Web Security ............................................................. 31

Configuring Secure Communication to Web Browsers ............... 31Restricting Power Xpert Software Web Access to SSL /HTTPS ............................................................................... 32Modifying the Power Xpert Software Shortcuts ......................... 34Troubleshooting ................................................................... 35

Power Xpert Reports ............................................................................ 37Migrating PXS Databases ..................................................................... 41

Preparing for Migration ................................................................. 41Stopping PXS ............................................................................. 41PXR Only: Disabling the PXR SQL Server Jobs ............................... 42Detach the PXS Databases .......................................................... 42Moving the Database Files ........................................................... 43

Power Xpert Software Administrator's Guide

iv Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com

Attach the Database Files in the New SQL Server Instance ............... 43Repointing PXS to the New SQL Server Instance ............................ 44PXR Preparation for Restarting PXS .............................................. 44Restarting PXS ............................................................................ 44PXR Only: Enabling the PXR SQL Server Jobs ............................... 45

Backup and Restore ............................................................................ 47Considerations ............................................................................ 47Data and Configurations ............................................................... 47Backup Foreseer ......................................................................... 48Backup Power Xpert Software ....................................................... 48Replacement Computer Installation ................................................ 50Troubleshooting ........................................................................... 51Restore Power Xpert Software ...................................................... 52

Troubleshooting ................................................................................... 55Slow Page Loading with IIS 7.5 ..................................................... 55Animations Don't Work in Internet Explorer ..................................... 57I Can't Connect to a Remote SQL Server Instance ........................... 57I Can't Deploy the Database ......................................................... 57Remote PowerNet Database Server Appears, But No Devices Un-der the Tree ................................................................................ 57No Data Appears in Device Pages or User Views ............................ 58Internet Explorer 7 Goes Into Endless Loop Attempting to Load Ac-tive-X Controls ............................................................................ 58If Your Users are Continually Confronted with a Login Dialog ............. 58Tabs on Properties Dialog Boxes in Layout Manager Disappear. ........ 58If Your Users Can't Export Alarm Information to Excel ....................... 58Image Maps Do Not Update ......................................................... 58Restart PXS ................................................................................ 58Device Summary Page Won't Open, Returns Error That ForeseerServer Isn't Running .................................................................... 59

II. Third Party Software Shipped with PXS ...................................................... 61Installing Microsoft SQL Server Management Studio 2008 ......................... 63

III. PowerNet ............................................................................................... 65New Device Objects ............................................................................ 67

Series NRX 520M Trip Unit .......................................................... 67Series NRX 1150 Trip Unit ........................................................... 68FP-6000 ..................................................................................... 72PM3 ........................................................................................... 91Additions to Status and Reason Codes ........................................... 94

Installing PowerNet ............................................................................ 105PowerNet for Non-Administrative Users ................................................ 107

Adding the PowerNet User to the Required Groups ........................ 107PowerNet Domain Server Configuration ........................................ 107PowerNet Client Configuration ..................................................... 108

PowerNet Server with Remote SQL Server ........................................... 111Technical Support ...................................................................... 119

Part I. PXS�Installation�and�Configuration

About�This�ManualThis guide provides information concerning:

• Prerequisites for Power Xpert Software (PXS) installation.

• PXS installation.

• PXS deployment (database, security, and IIS).

• Power Xpert Reports integration.

• Troubleshooting.

While installation of PXS doesn't require that you be a system administrator ordatabase analyst, having those skills would be extremely helpful. This document as-sumes that you are familiar with Microsoft operating systems, Microsoft SQL Server,and IIS administration. The procedures outlined in this guide require that you haveadministrative privileges on both the machine and SQL Server. While step-by-step in-structions are provided for PXS related tasks, you should refer to the instructions forMicrosoft products for details about administration tasks.

At the completion of the tasks in this guide, you will be ready to connect PXS to elec-trical devices in your network. The companion PXS Core Server Guide discusseshow to connect to data sources within PXS, how to configure alarms, and generalsystem administration.

Hardware�and�Software�RequirementsHardware�Requirements

PXS requires a workstation machine with the following minimum hardware specifica-tions:

Processor 2.8 GHz, dual-core processor.

Memory 2 GB allocated for PXS (allocate 3 GB of memo-ry to a virtual machine session running PXS).

Disk Space Required for Applica-tion

The PXS application itself requires 190 MB ofdisk storage.

Disk Space Required forDatabase

A typical database will grow to 2 GB within ayear. If you have a large number of devices, re-serve additional storage space.

Note

PXS will issue an alarm should free diskspace fall to 500 MB or less. Only thedrive on which PXS itself is stored ismonitored, so if your database files re-side on a separate drive or server youmust make sure to monitor disk spacethere.

Video Resolution 1280 by 1024 pixels or higher.

Removable Media DVD RO drive.

You may wish to add the following hardware as well:

• Local printer

• Sound card (if sounds are assigned to specific alarm conditions)

• Modem (for remote alarm notification to machines not available via your network).

Software�RequirementsSupported Operating Systems:

Note

Eaton recommends that you run PXS on server operating systems and notdesktop computer operating systems.

• Windows Server 2003 R2 (Standard or Enterprise editions) 32-bit edition.

Important

You cannot install PXS on Windows 2003 Server Web Edition.

• Windows Server 2008 (Standard or Enterprise editions), 32-bit and 64-bit or Win-dows Server 2008 R2 (Standard or Enterprise editions).

Third Party Software Installed with PXS

6 Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com

• Windows Server 2008 R2 SP1 Enterprise Spanish and German editions.

• Windows 7 Professional, Ultimate, or Enterprise editions, 32-bit or 64-bit.

• Microsoft Windows XP Professional with Service Pack 3, 32-bit only.

Important

In Windows XP Professional, Internet Information Services (IIS) limits thenumber of simultaneously connected web clients to 10. Once this limit is ex-ceeded, PXS graphics may not render correctly or the browser may displaythe message, There are too many people accessing the Web siteat this time.

Note

You cannot install PowerNet on any 64-bit Windows operating system.

Supported Versions of Microsoft SQL Server:

While PXS installs Microsoft SQL Server 2008 Express edition if you have no in-stalled version of SQL Server, it can be used with the following versions of SQL Serv-er:

• SQL Server 2005 Express SP3• SQL Server 2005 Std SP3• SQL Server 2005 Enterprise SP3• SQL Server 2008 Express• SQL Server 2008 Express SP1• SQL Server 2008 Express SP2• SQL Server 2008 Express SP3• SQL Server 2008 Standard• SQL Server 2008 Standard SP1• SQL Server 2008 Standard SP2• SQL Server 2008 Standard SP3• SQL Server 2008 Enterprise• SQL Server 2008 Enterprise SP1• SQL Server 2008 Enterprise SP2• SQL Server 2008 Enterprise SP3

Additional Software Components:

• IIS 5.0 or higher. For Windows XP and Server 2003, you must be install this prior toinstalling PXS. For Windows 7 and Windows Server 2008, this is installed automat-ically.

• Microsoft Internet Explorer (IE) 7, 8, or 9. This provides browser access to the PXSweb interface. Each user that will access PXS must have this browser. BecausePXS uses both Active-X and Silverlight technologies, other browsers (such as Fire-fox, Safari, Chrome, and Opera) are not supported. Also, Internet Explorer 6 isnot supported. If you access PXS with IE 6 or a non-Microsoft browser (such asChrome or Firefox), a warning message will appear stating that some PXS func-tionality may not be available.

Third�Party�Software�Installed�with�PXSThe following Microsoft software is also installed during the PXS installation.

• .NET Framework 3.5 SP1

Firewall Settings

Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com 7

• Windows Installer 4.5• C++ Runtime Library 2008• Microsoft Data Access 2.8• SQL Server 2008 Express Edition. This is installed only if no other version of SQL

Server is resident on the computer. If you have another version of SQL Server andwish to use it for PXS, make certain that it complies with the list shown in Support-ed Versions of Microsoft SQL Server: [6].

Note

SQL Server Management Studio is not installed. SQL Server ManagementStudio is helpful if you wish to migrate the PXS databases from one in-stance of SQL Server to another. See [ ]

Firewall�Settings

The following ports are opened automatically on the server during PXS installationif you are running the Microsoft firewall. If you are running a third-party fire wall, youmust open these ports manually. Also, as a general rule, ensure that there are noconflicts with third-party applications for these ports.

• 80 - HTTP• 443 - HTTPS• 8081 - HTTP• 8988 - TCP• 8989 - TCP

PXS communicates with Foreseer on port 11000, so ensure that this port is open andhas no conflicts.

You must open the following ports on the PXS client:

• 80 - TCP• 443 - TCP• 8988 - TCP• 8989 - TCP

Note

Foreseer opens ports 81 (HTTP) and 444 (HTTPS), so ensure there are noconflicts for these ports. These ports must not be changed from their de-faults.

PowerNet�Device�Server

The following configuration supports communicating with a PowerNet Device Serveron a PC or a NetLink. if accessing a remote PowerNet, these ports are opened auto-matically on the Power Xpert Software server during installation. However, they mustbe opened manually on the PowerNet computer.

• 5143 - TCP• 5146 - UDP• 5149 - UDP• 5150 - UDP

HTTP�Access

You must set the firewall to allow Web Server HTTP access. Check that this is activebefore installing Power Xpert Software.

Remote PowerNet Domain Server


Remote�PowerNet�Domain�Server

This port must be opened manually on both the Power Xpert Software server and thePowerNet Domain Server:

• 139 - TCP

Shutdown�Agent

The Eaton Shutdown Agent requires the following ports to be opened in the firewall:UDP ports 7013 and 7014.

• 7013 - UDP

• 7014 - UDP

Remote�Database�Support

• 1433 - TCP (this is the default port for SQL Server, but it is configurable). This portmust be open on both the PXS server and the remote database server.

SQL�Server�Considerations

PXS automatically installs a copy of Microsoft SQL Server Express 2008 SP2 if noother instance of SQL Server is present on the machine. If you will be installing an-other copy of SQL Server on the PXS machine, install that before installing PXS. In-stalling another copy of SQL server after the PXS installation “masks” the Express in-stance, and unless you reconfigure Express you won't see the PXS databases. Also,it is difficult to change the SQL Server instance PXS uses after that has been initiallyset (you must migrate the databases to do this, which is covered in [ ]).

As mentioned in the installation scenarios chapter (see the section called “InstallationScenarios” [11]), there are limitations to the amount of data that SQL Server Ex-press can handle).

If you will be deploying the PXS databases to a remote SQL Server instance, thenyou must open port 1433 (TCP) on both the SQL Server and PXS servers. However,this is the default port and can be changed. Contact your IT group or server adminis-trator for information on what port is actually used. Also, ensure that SQL Browser isrunning and that the SQL Server is set to allow remote connections .

SQL�Server�Account�ConsiderationsThe account used to run the PXS service should be as follows:

• If you are using a local instance of SQL server, use a local account with system ad-ministrator privilege.

• If you are using a remote instance of SQL server, use a domain account with theSQL Server sysadmin role assigned.

To see what log-on account is being used, in the Windows Services list, right-clickthe Eaton Power Xpert Software service and select Properties. Click the Log Ontab to view the account used to log onto SQL Server.

Browser�SettingsThe following applies if you are connecting to PXS from a remote machine: if youhave a proxy server on your intranet, in the Internet Explorer preferences add the

Remote Desktop Considerations


PXS server's IP address to the Exceptions under Proxy Settings. In Internet Ex-plorer this is under Tools → Internet Options → Connections → LAN Settings → Ad-vanced.

If your PXS server is in another domain or if you don't have domains set up, you mustadd the PXS server to the Trusted Sites zone. If you don't, some of the Active-Xcontrol objects that may be part of user views pages will not load properly. In fact, thebrowser may go into an endless loop attempting to load the Active-X controls. Addingthe PXS server to the Trusted Sites zone will fix the endless loop should that occur.If IT policies prevent you from adding machines to the trusted sites list, click the Lo-cal Intranet zone and then the Sites button. Make certain that Automatically detectintranet network is not selected. If IT policies prevent access to that setting, consultwith your IT group.

Remote�Desktop�Considerations

If you are using terminal services to connect to a PXS Server, you must be connect-ed via the console session. If you don’t connect through the console session, someadministrative tools, such as the Message Manager control panel applet, won’t work.The server must also be set to access remote desktop connections to use this ap-proach.

To launch a remote desktop connection to the console session on a server, type thefollowing command at the Windows command prompt:

mstsc -v:machine_name /F -console

Where machine_name is the name of the server.

If you are installing PXS on a server via Remote Desktop, select the option to Re-member my password in Remote Desktop. Some of the prerequisites installed forPower Xpert Software require a reboot to resume the installation. Checking the op-tion to remember the password will allow the installation to access the remote direc-tory upon reboot. If you do not select this option, an error indicating that the MSI (in-stall) file cannot be found will display after the reboot. If this occurs, you must man-ually navigate back to the remote location and launch the install again to correct theproblem.

Network�Considerations

PXS requires authentication through membership in Windows user groups (coveredin the section called “Read and Write Users” [29]). Also, PXS requires that the ma-chines running PXS, SQL Server, and Power Xpert Reports all must be within thesame domain.

Microsoft�Sharepoint

PXS cannot be installed on a computer that is hosting Windows Sharepoint Serviceson the default HTTP or HTTPS ports.

InstallationInstallation�Scenarios

There are three Power Xpert Software (PXS) installation scenarios:

PXS server using Microsoft SQL Server Express as the data repository, both in-stalled on the same server. This is the easiest scenario to set up and is ideal forsmaller electrical device networks. In this scenario, the PXS installer automatically in-stalls Microsoft SQL Server Express edition on the server. You connect to SQL Serv-er Express through the deployment tool using the connection string ./SQLEXPRESS.Setting up this scenario requires only one machine and no special IT or databaseskills, although a basic understanding of Windows users, security, and firewalls is ex-tremely helpful.

SQL Server Express is limited in database size (4 GB in SQL Server Express 2005and 10 GB in SQL Server Express 2008) and can only access one CPU, so perfor-mance is limited and the database cannot scale up to accommodate a large amountof data from devices. To complete this installation, you must have administrative privi-leges for the server machine.

Note

PXS will not install SQL Server Express if any other instance of SQL Serv-er is resident on that computer. However, if you wish to install it you can findthe installation files in the Power Xpert Software\SqlExpress2008folder on the PXS distribution DVD.

PXS server using Microsoft SQL Server Standard or Enterprise edition, both in-stalled on the same server. This is a mid-range solution, and is recommendedfor larger electrical device networks. The advantage of this scenario is that SQL Serv-er Standard or Enterprise editions do not have the 4 GB limitation for database size,and therefore can scale up to handle more data than the Express edition. Also, theStandard edition can use up to four CPUs and the Enterprise edition can have unlim-ited scaling and partitioning, providing much higher performance than the Expressedition.

This scenario requires that you have previously installed either the Standard or En-terprise editions of SQL Server on the PXS server machine before installing PXS.To complete this installation, you must have administrative privileges for SQL Serveras well as administrative privileges for the server machine itself. While this scenariodoesn't require specific IT or database skills, these are extremely helpful (especiallyin troubleshooting any security, firewall, or database problems that might be specificto your IT policies or database configuration).

This scenario is also the minimum configuration if you are installing Power Xpert Re-ports PXR on the same server as PXS. If either SQL Server Standard or Enterpriseedition is installed after PXS, it's difficult to “see” PXS's local copy of SQL Server Ex-press when attempting to connect PXR to the PXS database.

PXS server Using Microsoft SQL Server Standard or Enterprise edition, withSQL Server resident on another server (or server farm). This is the most scal-able approach, and can handle larger networks. Performance is enhanced by havingSQL Server and PXS on separate machines (either real or virtual) within the sameworkgroup or domain. The database capabilities can be further scaled-up thoughhigher performance hardware and database tuning or “scaled-out” using a multi-serv-er farm. However, this approach also requires the greatest investment in both infras-tructure and IT support, as well as assistance from database analysts. It is typically

PXS Installation


the preferred scenario for larger organizations with an established use of MicrosoftSQL Server.

PXS�InstallationBefore installing PXS:

• Verify hardware and software requirements (see Hardware and Software Require-ments [5]). Be sure that your operating system complies with the requirements(including installed service packs) and that required version of Microsoft IIS is in-stalled. PXS will alert you if either the operating system isn't supported or if IIS ismissing, but this occurs later during installation. Having met the software require-ments before starting installation ensures that you won't need to stop, install theprerequisites, and then start the installation procedure again.

• Back up your system as outlined in Backup and Restore [47]

• Contact your IT department for administrator access (you must be logged-in as theadministrator to perform the installation); and obtain network settings and user ac-count privileges.

• If you have a third-party firewall, open the ports as instructed in the section calledthe section called “Firewall Settings” [7].

Note

Depending on what Windows components are installed, during the processyou may be asked to reboot your system and restart the installation.

If�You�Have�a�Version�2.0�Installation�of�PXS...

If you are upgrading from version 2.0, do not uninstall the older version of PXS be-fore upgrading. You can simply install the new version and it will upgrade your ex-isting PXS installation. If you are upgrading from version 1.2 or earlier, you must se-quentially install each version of PXS. Contact the Eaton technical services group at1-800-809-2772 or by email [email protected] for assistance.

Installing�Under�Windows�Server�2008�or�Windows�7

When installing on Windows Server 2008, Eaton recommends that you do this asthe built-in administrator for the system. The built-in administrator has greater privi-leges than users assigned to the Administrator group. In Windows 2008, the built-in administrator should be enabled by default and the password for the account waschanged during initial start-up. However, the account may be disabled on your ma-chine (although you can re-enable it).

You can be logged in as a user assigned to the group if you use the “autorun” Eatoninstallation application or the setup.exe file to install PXS.

CautionDo not install from the .msi file. This may appear to work but PXS will not func-tion properly.

Installing�the�PXS�Application

To install the application:

1. Insert the distribution DVD in the DVD R/O or R/W drive. If the drive has autorunenabled, the PXS installer will automatically launch. If not, navigate to the root di-rectory on the DVD and double-click setup.exe.

Installing the PXS Application


2. You may see a dialog box asking for permission to run the software. If so, clickRun.

Figure 1.

3. In the installer, click Next.

Figure 2. Installer Main Screen

4. On the PXS Install page, click the Install button. The MS Setup Project Setupdialog box will appear. Click the Install button to continue.

Note

You may be required to accept the terms of a license agreement for Mi-crosoft products, depending on what required software components arealready installed on the computer



Figure 3. Setup

5. The Copying required files dialog box will appear. Installing the required com-ponents can take a while and may require one or more machine restarts. If themachine restarts, you may need to launch the PXS installation again.

Figure 4. Setup

Note

You may see the following Security Warning dialog box. This is askingpermissions to install the .NET framework. Click Run to proceed.

Figure 5. Security Warning Dialog Box

6. After component installation (which may include SQL Server 2008 Express Edi-tion) is complete, the Setup Wizard appears. Click the Next button.



Figure 6. Setup Wizard

7. Scroll down to read the license agreement and then click Next to accept theterms of the license.


8. Enter the six segments of the product key, each segment in its own fields. Whenthe fields are complete, click Next (which is now enabled).




9. In the Choose Components to Install dialog box, you can select which compo-nents you'd like to install at this time (they are all selected by default). If you don'tselect one at this time, you can return here and install the optional componentslater. Normally, you'll want to leave all components selected. After selecting com-ponents, click Next.

Figure 9. Selecting PXS Components

Note

At a minimum, you must install the Core components for PXS to func-tion.

10. Click the Install button to install the PXS components.



Figure 10. Installing PXS Components

11. When installation is complete, you'll see the following dialog box. Now that thePXS components are installed, you must next deploy the PXS databases to Mi-crosoft SQL Server. Click the Deploy button to launch the Deployment & Valida-tion Utility.

Figure 11. Installation Complete Dialog Box

Note

You'll find both an Eaton Power Xpert Software entry in the Windows Startmenu and a shortcut on your desktop.

Database�DeploymentYou can either choose to deploy the PXS databases to Microsoft SQL Server Ex-press (if that was installed with PXS) or to another instance of Microsoft SQL Server.You do this through the Deployment & Validation Utility. If at a later time you must mi-grate your databases to another instance of SQL Server, see [ ].

If you are using a remote instance of SQL server, ensure that the account you are us-ing to deploy the databases is a Windows domain account and has system adminis-trator privileges. Also, refer to the section called “SQL Server Considerations” [8] andensure that all prerequisites are met.

Aside from deploying the databases, the Deployment & Validation Utility also does anumber of system checks and simplifies system configuration. Through the utility youcan:

• Create the two required PXS groups (see Security [29]).

• Register ASP.NET 2.0 with IIS.

• Open the required ports for PXS on the Windows Firewall. If you have a third-par-ty firewall, you'll need to manually open the required ports (see the section called“Firewall Settings” [7]).

• Select a SQL Server instance, test the connection, and deploy the PXS databasesto that SQL Server instance.

• Start the required PXS services.

About�the�Deployment�&�Validation�UtilityThe Deployment & Validation Utility was designed to provide a summary of the readi-ness of PXS for operation and to help you prepare PXS for use. It has a series of in-dicators along the left that also serve to switch between the various functions in theutility. Clicking an indicator icon switches to the appropriate task or the top level sum-mary.

Figure 12. Deployment & Validation Indicator/Navigation Buttons

The following figure shows the various states for each indicator. The goal is to get allof the indicators to be “green” as shown in Figure 12, “Deployment & Validation Indi-cator/Navigation Buttons” [19] and then start all four PXS services.

Figure 13. Possible Indicator States

Launching the Deployment & Validation Utility


The Summary indicator is the “sum” of the indicators above it as well as having itsown tasks (you start and stop the various PXS services from Summary). If any of theother indicators shows a Not Configured or Warning state, then the Summary indi-cator will reflect this as well.

Launching�the�Deployment�&�Validation�Utility

For initial Deployment & Validation, you can launch the utility directly from the lastinstallation dialog box. Otherwise, launch it from the Eaton Power Xpert Softwaregroup in the Windows Start menu.

Note

To run the Deployment & Validation Utility, your account must be in the lo-cal Windows Administrator group. To deploy the databases, you must haveSQL Server sysadmin privilege.

Initial�Deployment�&�Validation

During initial deployment, your goal is to get all indicators showing green and thento start the services in the Summary tab. The following explains the tasks related toeach of the icons.

Important

Even if all of the status indicators are green, check the Summary tab. You muststart each of the four services before PXS is operational.

Windows�Groups

PXS uses Windows Integrated Security to limit access to its web applications and ad-ministrative utilities. Two user groups, Eaton Power Xpert Read Users and EatonPower Xpert Write Users, must be created for this purpose. Power Xpert Softwareuses these groups to determine who can read and/or write data to the database. Bydefault, both the read and write groups are empty. For more information about thesegroups, see the section called “Read and Write Users” [29]

If the indicator icon for this task isn't green, click the Create Users Group button tocreate the groups.

Configure IIS


Figure 14. Windows Groups Task Panel

Configure�IIS

This task verifies that you have the necessary version of IIS and that ASP.NET 2.0 isregistered with IIS and also checks for the IIS virtual directories. If the indicator iconisn't green, click the Register ASP.NET 2.0 and IIS button.

Firewall Ports


Figure 15. Configure IIS Task Panel

Firewall�Ports

This task checks if the Windows Firewall is active (listed under Status) and will openthe required ports on the Windows Firewall (click the Open Ports button). If you mustopen these ports manually, refer to the section called “Firewall Settings” [7].

Note

The Deployment & Validation Utility uses the Windows Firewall/InternetConnection Sharing (ICS) service to check the status of the ports. Makesure that the service is running. The firewall itself does not need to be run-ning for PXS to function.

Database


Figure 16. Firewall Task Panel

Database

Note

Before attempting to deploy the databases, review the account information inthe section called “SQL Server Account Considerations” [8].

Within this panel, you can establish the instance of SQL Server that will house thedatabases, set the location of the database files PXS, test the connection, and deploythe databases,

To deploy the PXS database:

1. Select either Local Machine (for an instance installed on the PXS server) or Re-mote Machine.

2. Specify the Server\Instance name for the SQL Server instance, such asyour_server\SQLSERVER. If it's the local server, you can use the string (lo-cal) instead of the server name. You can click the browse button (...) to see theset of SQL Server instances the utility can detect and select the instance fromthat list. If SQL Browser is running on a remote instance of SQL server then theconnection string should not need to specify a port number. However, if SQLbrowser is not running you may need to specify the port number as part of theconnection string.

Database


Note

SQL Server Express will identify itself as (local)\SQLEXPRESS. If youwish to use SQL Server Express and it isn't listed, this may be due to in-stalling another instance of SQL Server after installing PXS. If this oc-curs, manually enter (local)\SQLEXPRESS.

3. Change the default location of the PXS database files, if desired. If the SQLServer instance is on the local machine, you can browse to this folder. If it's ona remote machine, you can enter a path that already exists on the remote ma-chine. Therefore, you must create the folder on the remote machine before youcan change it here.

Note

If the user that created the instance is not the same users that's runningthe Deployment utility, you may encounter errors attempting to createthe databases.

4. Click the Test Connection button to verify that you have specified a valid Serv-er\Instance name, that your account has administrative access to that instance,and that the specified folder for the database files exists. If all three checks pass,you'll see the following alert box.

Figure 17. Successful Connection

5. Click the Start button to deploy the PXS databases. The Task Details pane willlog the various deployment steps as they are completed. This list also uses theindicator icons, and as each step completes it should have a green icon.

ImportantOnce deployed, you cannot use the Deployment & Validation Utility tochange the instance that houses the PXS databases. Contact customersupport if you must migrate the PXS databases to another instance of SQLServer.

Figure 18. Example Task Details Output

Advanced�Deployment

If you wish to create your own deployment script or create a set of monthly databas-es, click hyperlink (at the end of Administrators can manually create the databas-es through this hyperlink). This launches the Database Creation Scripts dialogbox.

Summary


Figure 19. Database Creation Scripts Dialog Box

To make a custom deployment script:

1. Click the Copy button. This copies the entire deployment script used by the utility(shown in the scrolling pane) to the Windows clipboard.

2. Paste the script into your editor of choice. You can now create your own cus-tomizations.

To create monthly databases:

1. Select the start and end months using the date selectors.

2. Click the Create button.

Summary

After all of the other deployment tasks have been completed and the associated in-dicator icons for these tasks are green, click the Summary icon. You can now starteach of the four services that comprise PXS with their associated Start buttons. Startany stopped services as required using the appropriate Start button. The goal is tohave all four services indicating a status of Running (automatic).

Summary


Figure 20. Deployment Tasks Complete and All Services Running

The four services have the following functions:

Eaton Power Xpert Software. Main service for PXS.

Eaton Foreseer Server Service. The Foreseer data acquisition engine.

Eaton Webviews File Monitor Service. Part of the PXS graphics engine.

Eaton Message Manager Service. Notification engine for sending email alerts re-garding alarms and events.

Microsoft�Internet�Explorer�SettingsPXS uses ActiveX controls in its web interface, and these must be installed in each ofyour user's browsers. Installation of the controls is automatic when a user accesses aPXS web page that contains one or more of the controls. However, the controls won'tinstall unless certain IE settings areTools made. In both versions of IE, these settingsare found in Internet Options under . To access the settings, click the Security taband then click the Custom Level button for the zone used for connections to PXS.

The following settings are in the Active-X controls and plug-ins group:

Table 1. ActiveX Settings

Option Setting Comment

Allow previously unused ActiveXcontrols to run without prompt

Disable This does not affect PXS, but thissetting provides for enhanced secu-rity.

Allow Scriptlets Prompt This does not affect PXS, but thissetting provides for enhanced secu-rity.

Automatic prompting for ActiveXcontrols

Enable

Binary and script behaviors Enable

Download signed ActiveX controls Prompt

Download unsigned ActiveX controls Disabled This does not affect PXS, but thissetting provides for enhanced secu-rity.

Initialize and script ActiveX controlsnot marked as safe for scripting

Disable This does not affect PXS, but thissetting provides for enhanced secu-rity.

Run ActiveX controls and plug-ins Enable

Script ActiveX controls marked safefor scripting

Enable This setting does not take effect untilyou restart IE.

Accessing�the�PXS�Web�Application�from�a�Server

Important

Even if you are using an account that's a member of the local Administrator'sgroup, domain administrators, or the built-in administrator, you must add thataccount to either the Eaton Power Xpert Read Users and Eaton Power XpertWrite Users groups. This is discussed in the section called “Read and WriteUsers” [29].

On server operating systems, the Enhanced Security Configuration in IE can preventyou from accessing the PXS Web Application. The solution for this is to add both lo-calhost and about:blank to the set of Trusted Sites. This setting is found in InternetOptions under Tools. To access the settings, click the Security tab and then clickthe Trusted Sites zone.

If you continue to have difficulty under Windows Server 2008, you can set InternetEnhanced Security Configuration (IE ESC) to Off. To do this, launch the Server Man-ager through Start → Administrative Tools → Server Manager. In the Security In-formation Group, click Configure IE ESC. Select Off for both Administrators andUsers.

Accessing the PXS Web Application from a Server


Figure 21. IE ESC Turned Off

If remote clients are being challenged with log-in prompts or security errors occurwhen attempting to access the PXS Web Application (and they are properly assignedto either the Eaton Power Xpert Read Users or Eaton Power Xpert Write Usersgroup), add the PXS server machine name or IP address to the Local intranet zone.This setting is found in Internet Options under Tools. To access the settings, clickthe Security tab and then click the Local intranet zone.

SecurityWhere�is�Security�Information�Stored?

Sensitive information, such as passwords and device addresses, are stored in thePower Xpert Software SQL database. The connection string to the database is storedin the registry and read/write access to that registry location is restricted in a similarfashion to the Power Xpert Software database.

Read�and�Write�UsersThe Eaton Power Xpert Read Users and Eaton Power Xpert Write Users groupswere created during initial deployment (see Figure 14, “Windows Groups Task Pan-el” [21]). Each of these groups provide unique privileges on the Power Xpert Softwareweb page. Users in the Read group have a read-only view the system and cannotchange or edit any configurations, settings, or notifications. Users in the Write grouphave all of the viewing privileges of the Read user, but can modify any and all parts ofthe system. You should only assign administrators and User Views page designers tothis group.

Important

On the PXS Server machine itself, you must assign even users that are domainadministrators, local administrators, or the built-in administrative account toone of these groups if those users will access PXS.

Read�Users�Group�Permissions

Members of the Eaton Power Xpert Read Users group can:

• View and change the settings for trend graphs in the Trend Viewer.

• View notes, but cannot add notes on the Alarms/Events page.

Read users cannot:

• Customize the Monitor List View for any node in the tree.

• Acknowledge or close alarms on the Alarms/Events page.

• Access the Layout Manager Page to edit the templates or graphics.

• Access the Configuration Manager.

• Access any web page listed in the Configuration menu, including the User Views,Database Management, and Alarm Notification web pages.

• Export alarm information.

• Change preferences on the Alarms/Events Log page.

Write�Users�Group�Permissions

Eaton Power Xpert Write Users have full read and write access to all parts of thesystem including the User Views, Database Management, Alarm Notification, andLayout Manager web pages. A Write user can also access the Configuration Man-ager.

Creating the Users Groups Manually


Creating�the�Users�Groups�Manually

Note

You will need the SQL Server Management Studio to complete this proce-dure. For more information about installing the Management Studio, see In-stalling Microsoft SQL Server Management Studio 2008 [63].

While the Deployment & Validation Utility will create the two required PXS usersgroups for you automatically, if you choose you can create them manually.

To create the users groups:

1. From the Windows Start menu, right-click My Computer (or Computer) and se-lect Manage.

2. In the Computer Management utility, expand Local Users and Groups. Insome versions of Windows, this is under Configuration.

3. Right-click Groups and select New Group.

4. Type the following in the Group name field: Eaton Power Xpert Read Users

5. Click Add and add members as appropriate.

6. Click OK when you've finished adding users.

7. Repeat the above procedure to create the Eaton Power Xpert Write Usersgroup.

8. When you've finished adding groups and users, click the Close button and exitfrom the Computer Management utility.

Local�Security�Settings�and�Web�ClientsThe local security settings influence how clients using local accounts are authenti-cated to the server. If the setting is Guest only mode, network logons using local ac-counts are mapped to the Guest account and authenticated as such. Since the guestaccount has very limited access privilege, access to Power Xpert Software Web UImay be rejected.

Note

The mapping does not apply to network logons using domain account.Therefore, this scenario is most likely to affect the machine not residing un-der a domain.

If the setting prevents accessibility of PXS Web UI, switching Guest only mode toClassical mode will solve the problem. Under the Classical mode, network logonsare authenticated as themselves.

To switch Guest only mode to Classical mode on the server:

1. From the Windows Start menu, choose Run.

2. Type gpedit.msc and then click OK. This launches the Group Policy editor.

3. Click Computer Configuration in the tree, and then click: Windows Settings >Security Settings > Local Policies > Security Options.

4. In the security options list, double-click the Network access: Sharing and se-curity model for local accounts item. If the setting is Guest only – local users

Connecting Web Clients


authenticate as Guest, choose Classic – local users authenticate as them-selves.

5. Click OK.

6. Close the Group Policy editor.

Connecting�Web�ClientsWeb Clients can connect to Power Xpert Software using Internet Explorer. Reviewthe software requirements in Hardware and Software Requirements for informationconcerning specific versions of Internet Explorer that are supported.

Web Clients can access the Power Xpert Software web interface via the followingURL:

http://server_ip_address/PowerXpertSoftware

Where server_ip_address is the IP address of the machine hosting the PowerXpert Software web server. The following section discusses setting up HTTPS ac-cess.

Configuring�Web�SecurityIn addition to the default security precautions Power Xpert Software takes to protectyour system, you will need to examine your own security needs and further fortifyyour system if desired. Power Xpert Software provides access via remote client Webbrowsers. If Power Xpert Software will be accessed over on a network that is not iso-lated by design, enabling Secure Socket Layer (SSL) communications is recommend-ed.

Configuring�Secure�Communication�to�Web�Browsers

Users wishing to enable HTTPS communications in their Power Xpert Software sys-tems should either purchase a certificate from a third-party SSL certificate providerand/or consult their IT department in case a certificate authority exists in-house. In-structions for importing and assigning the certificate should come from the provider.

Note

Before importing and assigning an SSL certificate, exit from all Power XpertSoftware clients.

1. From the Windows Start menu, choose Run.

2. Type inetmgr and then click OK to open the Internet Information Services(IIS) Manager.

Restricting Power Xpert Software Web Access toSSL / HTTPS


3. Expand the (local computer), then Web Sites, and then the Default Web Sitefolders.

4. Right click PowerXpertSoftware and then click Properties.

5. The PowerXpertSoftware Properties window will appear. Click the DirectorySecurity tab.

6. The View Certificate... button should be enabled. If it is not enabled, please con-tact the provider of the certificate.

7. With the certificate applied, access to Power Xpert Software via the prefixhttps:// should be enabled.

Note

When using an SSL certificate, the web address used to connect to PowerXpert Software must be the same as what is specified on the certificate. Forexample, http://166.99.9.149/... and http://MachineName/...may have been interchangeable prior to enabling certificate use. However,once the SSL certificate is employed, the address prefix explicitly indicat-ed on the certificate must be what is used when connecting to Power XpertSoftware. Be sure to make that correction when entering the address in thebrowser or warnings may occur.

Restricting�Power�Xpert�Software�Web�Access�to�SSL�/�HTTPS

At this point, although secure access to Power Xpert Software has been enabled,non-secure communication (via http://) is still possible.

Restricting Power Xpert Software Web Access toSSL / HTTPS


To restrict communications to only SSL/HTTPS:

1. Launch the Internet Information Services (IIS) Manager, right click the DefaultWeb Site folder, and then click Properties.

2. On the Directory Security tab, under the Secure Communications section, se-lect Edit.

3. Locate the Require secure channel (SSL) option at the top and select it.

4. Select the Require 128-bit encryption option, and then click the OK button.

5. Exit the Default Web Site Properties window. The following dialog should ap-pear. Click the Select All button.

Modifying the Power Xpert Software Shortcuts


6. Click the OK button.

Trying to access Power Xpert Software web pages via http:// should now be un-successful and result in an error page.

Modifying�the�Power�Xpert�Software�Shortcuts

The Power Xpert Software installation created shortcuts under Start->All Programs ->Power Xpert Software. By default, the shortcuts for the Power Xpert Software WebApplication and Log Viewer point to an http:// address.

To correct the shortcuts:

1. Navigate to the following folder: C:\Program Files\Eaton Power XpertSoftware\WebUI.

2. Right click the PowerXpertSoftware Internet shortcut and click Properties.

Troubleshooting


3. Alter the URL string to be https:// instead of http://. If the domain name islocalhost, change it to match that which was designated in the certificate prefix(e.g., the machine name).

4. Click the OK button to save the URL.

Repeat these steps with the PowerXpertSoftwareLogViewer Internet Short-cut in the following folder: C:\Program Files\Eaton Power Xpert Soft-ware\LogViewer.

Troubleshooting

If certificate warnings are presented upon connecting to Power Xpert Software or ifportions of the Web Application (e.g.,user views, New Event Monitor, etc) are not op-erating as expected, try cleaning the Internet Explorer browser cache/history, foundon the Tools menu under Internet Options.

If warnings or issues still exist that didn’t prior to enabling SSL communications, seekhelp from your SSL Certificate Provider as a problem most likely exists with the waythe certificate was imported and applied.

Power�Xpert�ReportsYou can integrate Power Xpert Reports (PXR) and PXS so that PXS users can navi-gate the “reporting tree” to select reports and view these directly in a user views win-dow (using the PXS Web Application). The following procedure assumes that:

• You have administrative privilege on the PXS server machine.

• If PXR is on a separate server from PXS, you have administrative privilege on theserver machine running the instance of SQL Server Reporting Services used byPXR.

• PXR is currently installed and properly configured to pull data from the PXSdatabase.

Refer to the Power Xpert Reporting Deployment Utility Guide and the PowerXpert Reporting Administration Utility Guide for information concerning how toconfigure Power Xpert Reporting to pull data from PXS and for adding users to theEaton Power Xpert Reporting Users group.

To set access privileges for reports if PXS and PXR are on the same server:

The following procedure grants access privileges for the PXS user groups to the PXRreports themselves. This assumes that PXS and PXR reside on the same machine.

1. Launch Internet Explorer.

2. Browse to http://localhost/Reports.

3. Click Properties. If only BUILTIN\Administrators is listed, continue to the nextstep.

4. Click New Role Assignment.

5. Enter the following group: Eaton Power Xpert Write User.

6. Select a specific role (Browser is the minimum required to view reports).

7. Repeat steps 4 through 6 to create the following group: Eaton Power XpertRead User.

To set access privileges for reports if PXS and PXR are on separate servers:

The following procedure grants privileges for users to access the PXR reports them-selves. This assumes that PXS and PXR reside on separate machines .

1. Log into the server machine which houses the instance of SQL Server ReportingServices used by PXR.

2. Create one or more user groups, depending on whether all users will simplyhave browse privilege or some will have elevated privileges. Add the domainusers that will access reports to the group or groups that you created.

3. In Internet Explorer, browse to http://localhost/Reports.

4. Click Properties. If only BUILTIN\Administrators is listed, continue to the nextstep.

5. Click New Role Assignment.


6. Enter the name of the “browse” user group that you created.

7. Select a specific role (Browser is the minimum required to view reports).

8. Repeat steps 5 through 7 if you created another user group and set the privi-leges accordingly.

To add the user accounts or groups to SQL Server:

1. Through the SQL Server Management Studio, add the accounts or groups thatyou previously created as login accounts in Reporting Services.

2. Map these accounts to the Power Xpert Reporting databases.

To verify PXR integration into PXS:

1. On the PXS Server, choose Start → Eaton Power Xpert Software → Configura-tion Manager.

2. In the tree, expand Integration and select Reporting.

Figure 22. Reporting Integration

3. Click the Notification Service URL field to select it.

4. Click the expand button (...) to the right of the field. This will launch the PXS No-tification Service Information Editor.

Figure 23. Reporting Integration

5. Click the Test button. If the notification server is available, you should see analert box stating Test succeeded. If you are executing this test remotely, bothservers must be in the same domain for this to work.

6. Click OK in the alert box.

7. Click OK in the PXS Notification Service Information Editor dialog box.


The reporting button will now appear when you next launch the PXS Web Applica-tion. See the Power Xpert Reporting User's Guide for more information about usingreports. If the test fails, refer to the PXR documentation and ensure that PXR is prop-erly configured to pull data from PXS.

Migrating�PXS�DatabasesYou can migrate the PXS databases from one instance of SQL Server to another. Ifyour devices can cache data, you may be able to do this without loosing data as well.The following sections outline the procedures for the various steps in the process,and includes steps for reattaching Power Xpert Reporting as well.

Important

This procedure uses SQL Server Management Studio, which is not installed byPXS. If you wish to migrate databases, you must install SQL Server Manage-ment Studio. If you are familiar with SQL Server commands, you do not needManagement Studio. You can instead read through the following sections tobecome familiar with the general steps involved and carry them out using SQLServer commands.

The following procedure is based on SQL Server Management Studio 2008, and ifyou are using a different version of Management Studio you may find slight varia-tions.

Preparing�for�Migration

You must have administrative privileges for the server that houses PXS and for bothinstances of SQL Server. If you have PXR, you'll need administrative privileges forthe PXR server as well. During the process, you'll need to follow these general steps:

1. Stop the PXS Services.

2. Disable the PXR SQL Server jobs (required for PXR only).

3. Detach the various PXS databases.

4. Copy the various PXS database files (specified in the following sections) to thenew server. If both instances of SQL Server reside on the same machine, thisstep is not necessary.

5. Attach the PXS database files to the new SQL Server instance.

6. Change the PXS connection string to repoint PXS to the new database instance.

7. Create the PXR login credentials (required for PXR only).

8. Restart PXS.

9. Restart the PXR SQL Server Agent (required for PXR only).

Stopping�PXS

While you can stop PXS through the Windows Control Panel, the simplest way is todo stop the four PXS services through the PXS Deployment & Validation Utility.

To stop PXS:

1. On the PXS Server Machine, launch the PXS Deployment & Validation Utilityfrom Start → All Programs → Eaton Power Xpert Software → Deployment Vali-dation Utility.

PXR Only: Disabling the PXR SQL Server Jobs


2. Click Summary.

3. Click the Stop button for each of the PXS services. After completing this step,the server core status should look like the following figure.

Figure 24. All PXS Services Stopped

PXR�Only:�Disabling�the�PXR�SQL�Server�JobsIf you have PXR, you should disable its database tasks next. Disabling these meansthat when you re-enable them, you'll pick up all of the data cached by devices as thisbecomes available through PXS. Th

To disable the PXR jobs:

1. Launch SQL Server Management Studio through Start → Microsoft SQL Serveryyyy.

2. Connect to the SQL Server instance used by PXR.

3. In the Object Explorer, scroll down to the SQL Server Agent.

4. Expand Jobs.

5. Right-click each of the Power Xpert Reporting jobs and select Disable from theshortcut menu.

Figure 25. The three PXR jobs.

Note

You can leave Management Studio open as you'll be completing more tasks.

Detach�the�PXS�DatabasesBefore copying the PXS database files, you must first detach them from SQL Server.

To detach the PXS databases:

1. If not open, launch SQL Server Management Studio through Start → MicrosoftSQL Server yyyy.

2. In the Object Browser, expand the Databases folder. PXS related database arePxs, PXS_yyyy_mm and Trend_yyyy_mm.

Moving the Database Files


Figure 26. PXS Databases

3. Right-click each database and select Tasks → Detach.

Note

You can also multiselect the databases and detach them as a group.

4. In the Detach Database dialog box, click OK.

You can leave Management Studio open as you'll be completing more tasks.

Moving�the�Database�FilesAfter the databases are detached, if the other instance of SQL Server isn't on thesame machine, you must move the database files. There are two files associated witheach database: DatabaseName.mdf, DatabaseName.ldf.

You can check the location of the files by right-clicking one of the databases in SQLServer Management Studio and selecting Properties. Click Files in the left pane andthen scroll to the right under Database Files until you can see the Path value.

Copy each of the database files to the new location. It's a good practice to not deletethe source files until you're sure that the everything is functioning properly in the newinstance.

Attach�the�Database�Files�in�the�New�SQL�Server�InstanceEach of the .mdf database files must be attached to the new SQL Server instance.This is a repetitive process, as your cannot attach a group of files.

To attach database files:

1. From SQL Server Management Studio, connect to the new SQL Server instance.

2. Right-click Databases in the Object Explorer and select Attach.

3. In the Attach Databases dialog box, click the Add button (under Databases toattach). Browse to the database file and select it, then Click OK.

Repeat this step until you've selected the entire set of PXS databases.

4. After you've added each of the PXS database .mdf files, click OK.

5. Right-click Databases in the Object Explorer and select Refresh. Verify that allof the PXS databases are now present.

Repointing PXS to the New SQL Server Instance


Repointing�PXS�to�the�New�SQL�Server�InstanceNext, you'll need to change the PxsConnectionString connection string key to re-point PXS to the new SQL Server instance.

To modify the registry key:

1. Launch the Registry Editor through Start → Run. In the Open field type regeditand then click OK.

2. For Windows XP, Windows Server 2003, and Windows 7, browse to theHKEY_LOCAL_MACHINE\Software\Eaton\PowerXpertSoftware\1.0 key.

For Windows Server 2008, browse to the HKEY_LOCAL_MACHINE\Wow6432Node\Software\Eaton\PowerXpertSoftware\1.0 key.

3. Double-click the PxsConnectionString key.

4. In the Value Data field, modify the connection string value for myServerAd-dress by substituting the address of the new database instance:

Data Source=myServerAddress;Initial Catalog=Pxs;Integrated Security=True

The path to your server takes the following format:

\\ServerName\InstanceName

5. Click OK.

6. Close the Registry Editor.

PXR�Preparation�for�Restarting�PXSIf you are using Windows authentication via a non-administrative account, you mustfirst create a local Windows users group called Eaton Power Xpert Reporting Userson the machine housing the new SQL Server instance. This is a local users groupcreated by PXS specifically to provide Windows accounts with the necessary privi-leges to access the PXS databases. You must then add the Windows account you'lluse to access PXS to that group.

Important

You will also need to add each Windows account that will access PXR reportsor the PXR Administration Utility to the Eaton Power Xpert Reporting Usersgroup.

Refer to the PXR

Restarting�PXSTo stop PXS:

1. On the PXS Server Machine, launch the PXS Deployment Validation Utility fromStart → All Programs → Eaton Power Xpert Software → Deployment ValidationUtility.

2. Click Summary.

3. Click the Start button for each of the PXS services. After completing this step,the server core status should look like the following figure.

PXR Only: Enabling the PXR SQL Server Jobs


Figure 27. All PXS Services Started

PXR�Only:�Enabling�the�PXR�SQL�Server�Jobs

If you have PXR, the final task is enabling the PXR jobs. This should pick up all of thedata cached by devices as this becomes available through PXS.

To enable the PXR jobs:

1. Launch SQL Server Management Studio through Start → Microsoft SQL Serveryyyy.

2. Connect to the SQL Server instance used by PXR.

3. In the Object Explorer, scroll down to the SQL Server Agent.

4. Expand Jobs.

5. Right-click each of the Power Xpert Reporting jobs and select Enable from theshortcut menu.

Figure 28. The three PXR jobs.

Note

You can close the Management Studio open as this is the final task.

Refer to the Power Xpert Reporting Deployment Utility Guide and the PowerXpert Reporting Administration Utility Guide for information concerning how con-nect PXR to the new location of the PXS databases.

Backup�and�RestoreBacking up your data is an important preventative measure. In the event that some-thing does go wrong, you will have the ability to restore your data easily and with min-imal loss of information. What follows are some specific examples of why customersshould be concerned about this topic:

A hard drive failure occurs at some point after the installation of Power Xpert Soft-ware.

• You will need to know which files need to be backed up on a regular basis to re-store your system in the event that this happens.

• After re-installation of PXS, the files can be restored such that the system worksagain with minimal disruption.

You take regular images of the PC with a third-party back up software. The computerfails and you must restore to a different one.

• If a replacement computer can be re-imaged directly from a backup, the solution issimply to re-image.

• However, if the computer cannot be directly re-imaged from a backup, the instruc-tions that follow explain which files to extract from the image and move to the re-placement PC.

Note

Not all third-party backup/restore imaging software tools allow users to: 1.)Search through the image (data mine), or 2.) Use the image created fromone computer on another with a slightly different hardware profile. Pleasekeep these features in mind when you choose imaging software.

You wish to move your PXS configuration and data from one computer to another, forexample, moving from an outdated computer to one that is high-end with faster hard-ware, and third-party imaging software will not be employed.

Considerations

There are a few things to consider when backing up your data and restoring on an-other system:

• The Foreseer instructions should only be used when backing up and restoring aForeseer system that is version 4.2.x or higher. If you would like to move data froman older Foreseer system, such as versions before 4.2.x, to versions 4.2.x andgreater, please contact Eaton support.

• When restoring Power Xpert Software, if Secure Socket Layer (SSL) communica-tion was configured on the previous computer, this setup will need to be repeatedon the replacement PC.

Data�and�Configurations

The default installation of Power Xpert Software includes Foreseer. Therefore, usersshould consider the historical data and configuration information for both of these ap-plications during the backup and restore process. Here is what’s “under the hood” ofeach program:

Backup Foreseer


Power Xpert Software:

• Configuration Data – Stored in .xml files

• Historical & Configuration Data – SQL Server

Foreseer:

• Configuration Data – saved in a .arq file

It is suggested that you create a central folder to store all of these backup data andconfiguration files.

Backup�ForeseerWhen you backup your configuration, an .arq file is generated at the location youspecify.

To back up the configuration:

1. Open Foreseer from the Windows Start menu or from the icon tray.

2. From the Configuration menu, choose Configuration Backup....

3. Choose a folder in which you would like to store the backup .arq file. By default, itwill be created in the Restore folder in Foreseer. Click Save.


Backup�Power�Xpert�SoftwareTo backup Power Xpert Software, you will need to save the .xml files that hold yourpreferences and configurations, and you will need to save the Power Xpert Softwaredatabases.

To back up the .xml files:

1. Open the following folder appropriate folder, depending on your operating system:C:\Documents and Settings\All Users\Application Data\Eaton\Power Xpert Software or C:\Program Data\Eaton\Power XpertSoftware.

2. The UserViewNodeCollection.xml file and theDatabaseHistoricalManagement.xml file are present by default. If you con-figured the Monitor List View page or changed the Alarms and Events prefer-ences, the MonitorConfiguration.xml file and the Preferences.xml filewill also be present. Copy all of the .xml files to your backup folder.

To backup the Power Xpert databases:

1. Open Microsoft SQL Server Management Studio Express via Start ->MicrosoftSQL Server 2005-> SQL Server Management Studio Express.

Backup Power Xpert Software


2. Connect to the Power Xpert database server. By default, it is named SQLEX-PRESS, but you might have chosen a different database instance name duringthe install of Power Xpert Software.

3. Expand the Databases folder to view the Power Xpert Software databases.

Replacement Computer Installation


4. Right click one of the following database, then go to Tasks, and click Back up....

PxsPXS_year_monthTrend_year_month

5. The Back Up Database window will appear. By default, the database backup willbe stored in Microsoft SQL Server’s Backup folder. If you would like to changethis, remove the current location and click the Add button to select a differentdestination. The file must be saved locally and then it can be moved to remotestorage.

6. If all of your backup information is correct, click OK.

7. Repeat steps 4 through 6 until all of the databases are backed up.

Replacement�Computer�InstallationOn the replacement computer, copy the backup folder containing all of your data fromthe old computer. Begin by installing the prerequisites and then Power Xpert Soft-ware. At the conclusion of installation, stop the Eaton Foreseer Server Service. Forexample, you can go to Start > Administrative Tools > Services and stop the ser-vice.

After stopping the service, delete the contents of the \Program Files\EatonPower Xpert Software\Foreseer Server\Data folder or \Program Files(x86)\Eaton Power Xpert Software\Foreseer Server\Data, depend-ing on your operating system. Restart the service, and then the following dialog boxshould appear.

Important

When this appears, do not click either the Next or Cancel button. Leave thiswindow open, and follow the restore the Foreseer configuration steps. After

Troubleshooting


completing that procedure, move on to the Power Xpert Software restore pro-cedure. If you do not see this screen, see the section called “Troubleshoot-ing” [51].

To restore the Foreseer configuration:

1. Open the following folder: C:\Program Files\Eaton Power Xpert Soft-ware\Foreseer Server\Restore or C:\Program Files (x86)\EatonPower Xpert Software\Foreseer Server\Restore, depending on youroperating system.

2. Copy the backup .arq file into the folder.

3. On the Server Initial Configuration window, choose the Restore a BackupConfiguration option and click the Finish button.

4. Choose your configuration file from the Restore folder and click the Open but-ton.

5. When the restoration is finished, click OK.

Troubleshooting

If the Server Initial Configuration window did not appear, or if you did not restoreyour configuration correctly, you can:

Restore Power Xpert Software


1. Open the Services window, and stop the Eaton Foreseer Server Service.

2. Delete the entire contents of the following folder: C:\Program Files\EatonPower Xpert Software\Foreseer Server\Data\.

3. Start the Eaton Foreseer Server Service.

The Server Initial Configuration window will now appear and you can try restoringagain.

Restore�Power�Xpert�Software

To restore Power Xpert Software:

1. Open the Windows Start menu and click Run.

2. Type services.msc and click the OK button to open the Services window.

3. Stop the Eaton Power Xpert Software Service by clicking on the service nameand clicking the Stop link on the left hand side or by clicking the Stop Servicebutton on the toolbar.

4. Copy all of the .xml files into the following folder: C:\Documents and Set-tings\All Users\Application Data\Eaton\Power Xpert Software\or C:\Program Data\Eaton\Power Xpert Software, depending on youroperating system.

5. Copy all of the Power Xpert databases to the local machine. They cannot be re-stored using Microsoft SQL Server Management Studio Express from a remotelocation.

6. Open Microsoft SQL Server Management Studio Express.

7. Connect to the Power Xpert database server, named SQLEXPRESS by default.

8. Expand the Databases folder to view the Eaton Power Xpert databases. All ofthe following databases must be restored:

PxsPXS_year_monthTrend_year_month

9. Right click the first database, go to Tasks, Restore, and click Database...

10. The Restore Database window will appear. Choose the From device option andclick the ... button.

Restore Power Xpert Software


11. To select the location of the file, click the Add button.

12. Find the appropriate file in your Backup folder and click the OK button.

13. Verify the path for the file is correct and click OK.

14. On the Restore Database screen, check the Restore checkbox next to the nameof the database you are restoring. Click the OK button.

15. Repeat steps 9 through 14 for each of the backup databases.

You have now completed the steps to backup and restore Foreseer and Power XpertSoftware.

TroubleshootingYou can contact Eaton technical support at 1-800-809-2772 or send email [email protected]. A technical support representative may ask you to use thePXS Log Viewer to retrieve PXS logs and send them back to Eaton. You can accessthe Log Viewer via Start → Eaton Power Xpert Software → PXS Log Viewer.

Slow�Page�Loading�with�IIS�7.5

When the PXS web application is loaded for the first time it may take up to severalminutes for the page to display. This may also occur if the PXS web application hasnot been accessed for 20 minutes or more. You can improve the page loading per-formance by installing the Microsoft Warm-Up Extension for IIS 7.5. There are twoversions of the extension: one for 32-bit Windows 7 and another for Windows Serv-er 2008 R2 or 64-bit Windows 7. You can download this from http://www.iis.net/ex-pand/ApplicationWarmUp. You will need administrative privileges to install this exten-sion and configure PXS to work with it.

After installing the Warm-Up Extension, there are four additional steps you must com-plete. These are outlined in the following procedure:

1. Using Start → Run to launch a command prompt field, type the following com-mand and then click OK.

%SystemRoot%\system32\inetsrv\appcmd migrate config “Default Web Site/PowerXpertSoftware”

Note

The above command assumes that PowerXpertSoftware is underDefault Web Site. If not, modify the command accordingly.

2. Launch the IIS Manager.

3. Expand Default Web Site, and then select PowerXpertSoftware.

4. In the Configure section to the right, double-click Application Warm-Up.

5. Choose the Settings menu item.

6. Select Enable Application Warm-Up and then click OK

http://www.iis.net/expand/ApplicationWarmUp

http://www.iis.net/expand/ApplicationWarmUp

Slow Page Loading with IIS 7.5


Figure 29. Settings Dialog Box

7. Choose the Add Request menu.

8. In the Add Request dialog box, type start.aspx in the Enter URL relative tothe application root field and then click OK

Figure 30. Add Request Box

9. Choose the Edit User Context menu item.

10. a. In the Edit User Context dialog box, choose Set User Token for Mode andWindows for Type.

b. For User name, type an account that is a member of Eaton Power XpertRead Users, Eaton Power Xpert Write Users, or Administrators.

c. Provide the password for the account in the Password and Confirm pass-word fields.

d. Click OK.

Animations Don't Work in Internet Explorer


Figure 31. Edit User Content Dialog Box

Animations�Don't�Work�in�Internet�ExplorerInternet Explorer options can be set to block animation. To enable this feature:

1. In Internet Explorer, choose Tools → Internet Options.

2. Click the Advanced tab.

3. Under Multimedia, select Plays animations in webpages. You will need torestart Internet Explorer for this setting to take effect.

4. Click OK.

I�Can't�Connect�to�a�Remote�SQL�Server�InstanceThis is usually due to authentication problems between the account you're usingon the PXS server machine and the SQL Server machine. Here are a few things tocheck:

• PXS uses Windows authentication to connect to the SQL Server machine. Makesure that you have all of the machines on the same domain and that you have Ac-tive Directory set up.

• Make sure that your account has administrative privileges on the remote SQL Serv-er machine and that you have the appropriate database roles assigned to your ac-count.

I�Can't�Deploy�the�DatabaseProblems in database deployment are logged in the Task Details pane on theDatabase Task Panel (in the Deployment & Validation Utility).

Remote�PowerNet�Database�Server�Appears,�But�No�Devices�Under�the�TreeEnsure that the log-on account matches the log-on account expected by the Pow-erNet PC. To see what log-on account is being used, in the Windows Services list,right-click the Eaton Power Xpert Software service and select Properties. Click theLog On tab to view the account used to log onto PowerNet.

No Data Appears in Device Pages or User Views


No�Data�Appears�in�Device�Pages�or�User�ViewsIf you notice this problem while running on the PXS server machine, check the IISmanager and ensure Anonymous Access is enabled for the PXS virtual directories(webviews, support, and webadmin). If you encounter this from a client, in the In-ternet Explorer preferences add the PXS server's IP address to the Exceptions un-der Proxy Settings. This is under Tools → Internet Options → Connections → LANSettings → Advanced.

Also, make certain that port 8081 is open on the PXS server machine.

Internet�Explorer�7�Goes�Into�Endless�Loop�Attempting�to�Load�Active-X�ControlsGo to the Internet Explorer security settings (Tools > Internet Options > Securitytab), and click the Trusted Sites zone. Click the Sites button and add the machinename (preferable) or IP address of the PXS server to list of trusted sites. If IT policiesprevent you from adding machines to the trusted sites list, click the Local Intranetzone and then the Sites button. Make certain that Automatically detect intranetnetwork is not selected. If IT policies prevent access to that setting, consult with yourIT group.

If�Your�Users�are�Continually�Confronted�with�a�Login�DialogThis can occur on an intranet with a proxy server. To remedy this, in the Internet Ex-plorer preferences add the PXS server's IP address to the Exceptions under ProxySettings. This is under Tools → Internet Options → Connections → LAN Settings →Advanced.

Tabs�on�Properties�Dialog�Boxes�in�Layout�Manager�Disappear.Add about:blank to the set of Internet Explorer trusted sites.

If�Your�Users�Can't�Export�Alarm�Information�to�ExcelIf your users can't export alarm information to Microsoft Excel, grant them access asfollows:

• For remote users (not on the PXS server machine), user accounts access-ing PXS must have read/write access to the \Documents and Set-tings\machine_name\ASPNET\Local Settings\Temp folder on the PXSserver machine.

• For users on the PXS server machine, user accounts accessing PXS must haveread/write access to the \Documents and Settings\machine_name\ASPNET\Local Settings\Temp folder and the \Documents and Set-tings\user_name\Local Settings folder on the PXS server machine.

Image�Maps�Do�Not�UpdateIf image maps on user views pages do not update, make certain that the Eaton Web-views File Monitor service is running on the PXS machine.

Restart�PXSTo stop PXS:

1. On the PXS Server Machine, launch the PXS Deployment Validation Utility fromStart → All Programs → Eaton Power Xpert Software → Deployment ValidationUtility.

Device Summary Page Won't Open, Returns ErrorThat Foreseer Server Isn't Running


2. Click Summary.

3. Click the Start button for each of the PXS services. After completing this step,the server core status should look like the following figure.

Figure 32. All PXS Services Started

Device�Summary�Page�Won't�Open,�Returns�Error�That�Foreseer�Server�Isn't�Running

Occasionally, when attempting to open a device summary page or a user views page,PXS will instead return the following error:

Graphics Page cannot be opened. Please verify that the Foreseer service is running on the PXS server machine

If the Foreseer server is running and you receive this error, the likely problem is thatthe device name has exceeded 40 characters. You will need to rename the deviceat the publisher (PowerNet, the PXG, etc.) as well as delete and then recreate thematching folder on the PXS server. Contact Eaton Power Quality Technical Supportat 1-800-809-2772 or [email protected] for assistance with this task.

Part II. Third�Party�Software�Shipped�with�PXS

Installing�Microsoft�SQL�Server�ManagementStudio�2008

Both the 32 and 64-bit versions of SQL Server Express 2008 Management Studio areshipped on the PXS DVD, and reside in the \Third Party\SQL Server 2008Express Management Studio folder. If you need to install Management Studio,you can install it from the DVD.

Before you can install the SQL Server Management Studio on Windows Server 2003and XP, the Windows Power Shell must be installed. This is available from the Mi-crosoft Download Center. As of the time this manual was written, for XP systems Mi-crosoft requires that you first download and run an application that verifies you're run-ning a “genuine” copy of Windows XP before running the Power Shell installation.

Note

The Windows Power Shell is pre-installed in Windows Server 2008 and Win-dows 7.

To install Management Studio, launch either theSQLManagementStudio_x86_ENU.exe 32-bit installer or theSQLManagementStudio_x64_ENU.exe 64-bit installer. This is actually the SQLServer 2008 Express edition installer itself.

Installing the Management Studio by itself is not intuitive: you must make two impor-tant selections during the process:

• When you are presented with the choice to either perform a new installation of SQLServer or add features to an existing instance, you must choose to perform a newinstallation. You cannot add the Management Studio as a feature. Selecting thisroute will not install a second instance of SQL Server.

Figure 33. Selecting a New Installation

• When you reach the list of features to install, make certain that you select Manage-ment Tools - Basic.


Figure 34. Selecting the Management Studio

Part III. PowerNet

New�Device�ObjectsThe following are new device objects not contained in the PowerNet Documentation.

Series�NRX�520M�Trip�Unit

Table 2. Series NRX 520M Device Objects

Description NumberOf Regis-ters

DDE Tag Name DDE Type Range Units Invalid Number ScaleFactor

Status 1 STATN R# 0, 1, 2, 3, 4, 47 (See the Status Codestable in Appendix A of the PowerNetUser's Guide and Table 11, “StatusCodes” [94].)

FFFF 1

Status(String)

NA STATT M NA NA NA

Status Sec-ondary

1 STAT2N R# 0, 4, 45, 46, 48 (See the Status Codestable in Appendix A of the PowerNetUser's Guide and Table 11, “StatusCodes” [94].)

FFFF 1

Reason 1 RSONN R# 0, 1 ,2, 3, 4, 5, 6, 11, 14, 47, 121, 162,167, 230, 231, 240, 262, 263, 264,265, 297, 298, 330, 331, 423, 427, 430,459, 491, 492 (See the Reason Codestable in Appendix A of the PowerNetUser's Guide and Table 12, “ReasonCodes” [96].)

FFFF 1

Reason(String)

NA RSONT M NA NA NA

DDE DeviceAlarm

NA ALARM I 0-30, 200-249 (See the Alarm Codestable in Appendix A of the PowerNetUser's Guide.)

NA NA

Comm Ver-sion

NA COM_VERSION I 0 to 15 NA NA

Product ID NA PRODUCT_ID I 44 NA NA

DivisionCode

NA DIV_CODE I 32 NA NA

Device Type NA TYPEN I 100 NA NA

Ia (RMS) 2 IA R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib (RMS) 2 IB R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ic (RMS) 2 IC R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ig (RMS) 2 IG R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

In (RMS) 2 IN R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Table 3. Series NRX 520M Controls

Description Tag name DDE Type Modbus Value Direct

Close Device CLOSE_DEVICE I 0x601 X

Open Device OPEN_DEVICE I 0x600 X

Reset Power Up RESET_POWER_UP I 0x63B X

Reset Slave Stats RESET_SLAVE_STATS I 0x63C X

Reset Trip RESET_UNIT I 0x603 X

Reset Power-up Indicator RESET_POWER_UP I 0x833 X

Enable Maintenance Mode ENABLE_MAINTENANCE_MODE I X

Disable Maintenance Mode DISABLE_MAINTENANCE_MODE I X

Series NRX 1150 Trip Unit


Series�NRX�1150�Trip�Unit

Table 4. NRX 1150 Device Data

Description NumberOf Mod-bus Reg-isters

DDE Tag Name DDE Type Range Units InvalidNumber

ScaleFactor

Status 1 STATN R# 0, 1, 2, 3, 47 (Seethe Status Codestable in AppendixA of the PowerNetUser's Guide andTable 11, “StatusCodes” [94].)

FFFF 1

Status (String) N/A STATT M N/A N/A N/A

Status Secondary 1 STAT2N R# 0, 4, 45, 46, 48(See the StatusCodes table inAppendix A of thePowerNet User'sGuide and Ta-ble 11, “StatusCodes” [94].)

FFFF 1

Reason 1 RSONN R# 0, 1, 2, 3, 4, 5,6, 14, 18, 19,20, 21, 33, 47,85, 103, 105,119, 142, 167,230, 235, 236,239, 242, 259,262, 263, 264,265, 298, 330,331, 401, 410,411, 412, 413418. 419, 423,427, 429, 451,452, 454, 457,458, 459, 460,478, 486, 488(See the ReasonCodes table inAppendix A of thePowerNet User'sGuide and Ta-ble 12, “ReasonCodes” [96].)

FFFF 1

Reason (String) N/A RSONT M N/A N/A N/A

DDE Device Alarm N/A ALARM I 0-30, 200-249(See the AlarmCodes table inAppendix A of thePowerNet User'sGuide.)

N/A N/A

Comm Version N/A COM_VERSION I 0 to 15 N/A N/A

Product ID N/A PRODUCT_ID I 46 N/A N/A

Division Code N/A DIV_CODE I 32 N/A N/A

Device Type N/A TYPEN I 103 N/A N/A

Crest Factor IA 1 CFIA R#.# 0 to 6553.5 FFFF 10

Crest Factor IB 1 CFIB R#.# 0 to 6553.5 FFFF 10

Crest Factor IC 1 CFIC R#.# 0 to 6553.5 FFFF 10

Crest Factor IN 1 CFIN R#.# 0 to 6553.5 FFFF 10

Event Counta 1 EVENTCOUNT R# 0 to 65535 FFFF 1

Frequency 1 FREQ R#.# 45 to 65 Hz FFFF 10

Phase A Current(RMS)

1 IA R# 0 to 65535 A FFFF 1





ScaleFactor

Phase B Current(RMS)

1 IB R# 0 to 65535 A FFFF 1

Phase C Current(RMS)

1 IC R# 0 to 65535 A FFFF 1

Ground Current(RMS)

1 IG R# 0 to 65535 A FFFF 1

Neutral Current(RMS)

1 IN R# 0 to 65535 A FFFF 1

Phase A DemandCurrent

1 IADEMAND R# 0 to 65535 A FFFF 1

Phase A Peak De-mand Current

1 IAPEAK R# 0 to 65535 A FFFF 1

Phase B DemandCurrent

1 IBDEMAND R# 0 to 65535 A FFFF 1

Phase B Peak De-mand Current

1 IBPEAK R# 0 to 65535 A FFFF 1

Phase C DemandCurrent

1 ICDEMAND R# 0 to 65535 A FFFF 1

Phase C Peak De-mand Current

1 ICPEAK R# 0 to 65535 A FFFF 1

Number of Instanta-neous/Short DelayFaults

1 INST_SDT_FAULTS I 0 to 65535 FFFF 1

Number of LongDelay/GroundFaults

1 LDT_GFT_FAULTS I 0 to 65535 FFFF 1

Maximum Phase ACurrent (RMS)

1 MAX_IA R# 0 to 65535 A FFFF 1

Maximum Phase BCurrent (RMS)

1 MAX_IB R# 0 to 65535 A FFFF 1

Maximum Phase CCurrent (RMS)

1 MAX_IC R# 0 to 65535 A FFFF 1

Maximum GroundCurrent (RMS)

1 MAX_IG R# 0 to 65535 A FFFF 1

Maximum NeutralCurrent (RMS)

1 MAX_IN R# 0 to 65535 A FFFF 1

Maximum ApparentPower Factor

1 MAX_SYSTEM_PF_APP R#.## +/- 1.00 7FFF 100

Maximum Trip UnitTemperature

1 MAX_TEMP R# -273 to 330 °C FFFF 1

Minimum Phase ACurrent (RMS)

1 MIN_IA R# 0 to 65535 A FFFF 1

Minimum Phase BCurrent (RMS)

1 MIN_IB R# 0 to 65535 A FFFF 1

Minimum Phase CCurrent (RMS)

1 MIN_IC R# 0 to 65535 A FFFF 1

Minimum GroundCurrent (RMS)

1 MIN_IG R# 0 to 65535 A FFFF 1

Minimum NeutralCurrent (RMS)

1 MIN_IN R# 0 to 65535 A FFFF 1

Minimum ApparentPower Factor

1 MIN_SYSTEM_PF_APP R#.## +/- 1.00 7FFF 100

Per Phase CurrentDemand Window

1 PER_PHASE_I_DEMAND_WINDOW R# 0 to 65535 min FFFF 1

Power Factor (Ap-parent)

1 PFAPP R#.## +/- 1.00 7FFF 100

Forward Real Ener-gy (Watthours)

2 POSENERGY R# +/- 999999999000 Wh FFFFFFFF 1





ScaleFactor

Power DemandWindow

1 POWER_DEMAND_WINDOW R# 0 to 65535 min FFFF 1

Raw Status 2 RAW_STATUS I N/A FFFFFFFF 1

Reverse Real Ener-gy (Watthours)

2 NEGENERGY R# 0 to999999999000

Wh FFFFFFFF 1

System Real PowerDemand (Watts)

2 SYS_DEMAND_WATTS R# 0 to 2147483646 W 7FFFFFFF 1

System NegativePeak DemandWatts (calculated)

2 SYS_NEG_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1

System PositivePeak DemandWatts (calculated)

2 SYS_POS_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1

Time of SystemNegative Peak De-mand Watts

N/A SYS_NEG_PEAK_DEMAND_WATTS_TIME TIME N/A N/A N/A

Time of SystemPositive Peak De-mand Watts

N/A SYS_POS_PEAK_DEMAND_WATTS_TIME TIME N/A N/A N/A

Time of Last Restof System DemandWatts (calculated)

N/A SYS_TIME_LAST_RESET_DEMAND_WATTS TIME N/A N/A N/A

Time of Last Resetof Phase DemandCurrents

N/A TIME_1_PHASE_DEMAND_I_RESET TIME N/A N/A N/A

Time of Last Resetof Min/Max PowerFactor

N/A TIME_LAST_MM_PF_APP_RESET TIME N/A N/A N/A

Time of MaximumPower Factor

N/A TIME_MAX_SYSTEM_PF_APP TIME N/A N/A N/A

Time of MinimumPower Factor

N/A TIME_MIN_SYSTEM_PF_APP TIME N/A N/A N/A

Time of Last Event(Breaker Open)

N/A TIME_OF_LAST_OPERATION TIME N/A N/A N/A

Time of Last Resetof Power Demand

N/A TIME_OF_LAST_POWER_RESET TIME N/A N/A N/A

Time of Phase APeak Demand Cur-rent

N/A TIME_OF_PEAK_IA TIME N/A N/A N/A

Time of Phase BPeak Demand Cur-rent

N/A TIME_OF_PEAK_IB TIME N/A N/A N/A

Time of Phase CPeak Demand Cur-rent

N/A TIME_OF_PEAK_IC TIME N/A N/A N/A

Time of Peak Ap-parent Power De-mand

N/A TIME_OF_PEAK_VA TIME N/A N/A N/A

Time of Peak Reac-tive Power Demand

N/A TIME_OF_PEAK_VARS TIME N/A N/A N/A

Time of Peak RealPower Demand

N/A TIME_OF_PEAK_WATTS TIME N/A N/A N/A

Percent THDPhase A Current

1 THDIA R# 0 to 65535 % FFFF 1

Percent THDPhase B Current

1 THDIB R# 0 to 65535 % FFFF 1

Percent THDPhase C Current

1 THDIC R# 0 to 65535 % FFFF 1

Percent THD Neu-tral Current

1 THDIN R# 0 to 65535 % FFFF 1





ScaleFactor

Apparent Power(VA)

2 VA R# 0 to 2147450880 VA 7FFFFFFF 1

Voltage A-B 2 VAB R# 0 to 2147450880 V FFFFFFFF 1

Apparent PowerDemand (VA)

2 VADEMAND R# 0 to 2147450880 VA 7FFFFFFF 1

Apparent Energy(VAhours)

2 VAHRS R# 0 to999999999000

VAh FFFFFFFF 1

Peak ApparentPower Demand(VA)

2 VAPEAK R# 0 to 2147450880 VA 7FFFFFFF 1

Voltage A-N 2 VAN R# 0 to 2147450880 V FFFFFFFF 1

Reactive Power(vars)

2 VARS R# +/- 1073709057 var 7FFFFFFF 1

Reactive PowerDemand (vars)

2 VARSDEMAND R# +/- 1073709057 var 7FFFFFFF 1

Peak ReactivePower Demand(vars)

2 VARSPEAK R# +/- 1073709057 var 7FFFFFFF 1

Voltage B-C 2 VBC R# 0 to 2147450880 V FFFFFFFF 1

Voltage B-N 2 VBN R# 0 to 2147450880 V FFFFFFFF 1

Voltage C-A 2 VCA R# 0 to 2147450880 V FFFFFFFF 1

Voltage C-N 2 VCN R# 0 to 2147450880 V FFFFFFFF 1

Voltage G-N 2 VGN R# 0 to 2147450880 V FFFFFFFF 1

Real Power (Watts) 2 WATTS R# +/- 1073709057 W 7FFFFFFF 1

Real Power De-mand (Watts)

2 WATTSDEMAND R# +/- 1073709057 W 7FFFFFFF 1

Peak Real PowerDemand (Watts)

2 WATTSPEAK R# +/- 1073709057 W 7FFFFFFF 1

aThe Event Count attribute is the breaker operations count: the count increments each time the position of the breaker poles changes(i.e., from open to closed or closed to open).

Table 5. Series NRX 1150 Controls

Description Tag name DDE Type Modbus Value Direct

Close Breaker CLOSE_DEVICE I 601 X

Open Breaker OPEN_DEVICE I 600 X

Enable Maintenance Mode ENABLE_MAINTENANCE_MODE I 637 X

Disable Maintenance Mode DISABLE_MAINTENANCE_MODE I 638 X

Reset Current Demand RESET_DEMAND_I I 609 X

Reset Power Demand Window RESET_DEMAND_WATTS_WND I 607 X

Reset Power Demand RESET_DMD_WATTS I 602 X

Reset All Min/Max Values RESET_ALL_MIN_MAX I 61F X

Reset Min/Max Currents RESET_MIN_MAX_I I 620 X

Reset Min/Max Power Factor RESET_MIN_MAX_PF_APP I 624 X

Reset Min/Max L-LVoltages RESET_MIN_MAX_LL_VOLTS I 621 X

Reset Min/Max L-N Voltages RESET_MIN_MAX_LN_VOLTS I 622 X

Reset Min/Max Power RESET_MIN_MAX_POWER I 625 X

Reset Health Statistics RESET_HEALTH_STATISTICS I 636 X

Reset Power Up Indicator RESET_POWER_UP I 833 X

Reset INCOM Statistics RESET_SLAVE_STATS I 649 X

Reset Unit RESET_UNIT I 603 X

FP-6000


FP-6000

Table 6. FP-6000 Device Objects

Descrip-tion

# OfReg-isters

DDE Tag Name DDEType

Range Units Invalid Number Scale Factor

Status 1 STATN R# 0, 1, 2, 3, 4, 5, 6, 7, 9, 10, 21, 22,47 (See the Status Codes tablein Appendix A of the PowerNetUser's Guide and Table 11, “Sta-tus Codes” [94].)

FFFF 1

Status(String)

NA STATT M NA NA NA

Status Sec-ondary

1 STAT2N R# 0, 1, 2, 3, 4, 5, 6 (See the StatusCodes table in Appendix A of thePowerNet User's Guide and Ta-ble 11, “Status Codes” [94].)

FFFF 1

Reason 1 RSONN R# 0 - 6, 20, 21, 26, 27, 34, 39, 43,72, 73, 82, 85, 103, 117, 119,168, 171, 223, 235, 239, 273,296, 326, 332, 400 - 432, 472,473, 482 (See the Reason Codestable in Appendix A of the Power-Net User's Guide and Table 12,“Reason Codes” [96].)

FFFF 1

Reason(String)

NA RSONT M NA NA NA

DDE DeviceAlarm

NA ALARM I 0-30, 200-249 (See the AlarmCodes table in Appendix A of thePowerNet User's Guide.)

NA NA

Comm Ver-sion

NA COM_VERSION I 0 to 15 NA NA


DivisionCode

NA DIV_CODE I 4 NA NA

DeviceType

NA TYPEN I 99 NA NA

27-A1 AuxVx UnderVolt Flag

1 AUX_27_A1_UV_OP R# 0,1 FFFF 1

27-A2 AuxVx UnderVolt Flag

1 AUX_27_A2_UV_OP I 0,1 FFFF 1

27-M1 MainVp UnderVolt Flag

1 MAIN_27_M1_UV_OP I 0,1 FFFF 1

27-M2 MainVp UnderVolt Flag

1 MAIN_27_M2_UV_OP I 0,1 FFFF 1

32-1 PowerOperationFlag

1 POWER_32_1_OPERATION_FLAG

I 0,1 FFFF 1



I 0,1 FFFF 1



I 0,1 FFFF 1

46-1 Cur-rent UnbalOp Flag

1 MISC_46_1_CU_OP I 0,1 FFFF 1

46-2 Cur-rent UnbalOp Flag

1 MISC_46_2_CU_OP I 0,1 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



47-1 Volt-age Unbal-ance OpFlag

1 MISC_47_1_VU_OP I 0,1 FFFF 1

47-2 Volt-age Unbal-ance OpFlag

1 MISC_47_2_VU_OP I 0,1 FFFF 1

49- RTD #1Alarm 1

1 IEEE_49_RTD_1_ALARM_1_FLAG

I 0,1 FFFF 1

49- RTD #1Alarm 2


I 0,1 FFFF 1

49- RTD #1Operate

1 IEEE_49_RTD_1_OPERATE_FLAG

I 0,1 FFFF 1

49- RTD#10 Alarm 1


I 0,1 FFFF 1

49- RTD#10 Alarm 2


I 0,1 FFFF 1

49- RTD#10 Oper-ate


I 0,1 FFFF 1

49- RTD#11 Alarm 1


I 0,1 FFFF 1

49- RTD#11 Alarm 2


I 0,1 FFFF 1

49- RTD#11 Oper-ate


I 0,1 FFFF 1

49- RTD #2Alarm 1


I 0,1 FFFF 1

49- RTD #2Alarm 2


I 0,1 FFFF 1

49- RTD #2Operate


I 0,1 FFFF 1

49- RTD #3Alarm 1


I 0,1 FFFF 1

49- RTD #3Alarm 2


I 0,1 FFFF 1

49- RTD #3Operate


I 0,1 FFFF 1

49- RTD #4Alarm 1


I 0,1 FFFF 1

49- RTD #4Alarm 2


I 0,1 FFFF 1

49- RTD #4Operate


I 0,1 FFFF 1

49- RTD #5Alarm 1


I 0,1 FFFF 1

49- RTD #5Alarm 2


I 0,1 FFFF 1

49- RTD #5Operate


I 0,1 FFFF 1

49- RTD #6Alarm 1


I 0,1 FFFF 1

49- RTD #6Alarm 2


I 0,1 FFFF 1

49- RTD #6Operate


I 0,1 FFFF 1

49- RTD #7Alarm 1


I 0,1 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



49- RTD #7Alarm 2


I 0,1 FFFF 1

49- RTD #7Operate


I 0,1 FFFF 1

49- RTD #8Alarm 1


I 0,1 FFFF 1

49- RTD #8Alarm 2


I 0,1 FFFF 1

49- RTD #8Operate


I 0,1 FFFF 1

49- RTD #9Alarm 1


I 0,1 FFFF 1

49- RTD #9Alarm 2


I 0,1 FFFF 1

49- RTD #9Operate


I 0,1 FFFF 1

49- RTDGroup #1Operate

1 IEEE_49_RTD_GROUP_1_OPERATE_FLAG

I 0,1 FFFF 1

49- RTDGroup #2Operate

1 IEEE_49_RTD_GROUP_2_OPERATE_FLAG

I 0,1 FFFF 1

49- Ther-mal ModelAlarm 1

1 IEEE_49_THERMAL_MODEL_ALARM_1_FLAG

I 0,1 FFFF 1

49- Ther-mal ModelAlarm 2

1 IEEE_49_THERMAL_MODEL_ALARM_2_FLAG

I 0,1 FFFF 1

49- ThermalModel Op-erate

1 IEEE_49_THERMAL_MODEL_OPERATE_FLAG

I 0,1 FFFF 1

50P-1Phase IOCOperationFlag

1 IOC_50P_1_PHASE_OP I 0,1 FFFF 1





50R-1 IrIOC Opera-tion Flag

1 IOC_50R_1_IR_OP I 0,1 FFFF 1





50X-1 IxIOC Opera-tion Flag

1 IOC_50X_1_IX_OP I 0,1 FFFF 1





FP-6000


Descrip-tion

# OfReg-isters



51P PhaseTOC Oper-ation Flag

1 TOC_51P_PHASE_OP I 0,1 FFFF 1

51P2 PhaseTOC Oper-ation Flag

1 PHASE_TOC_51P2_OPERATION_FLAG

I 0,1 FFFF 1

51R Ir TOCOperationFlag

1 TOC_51R_IR_OP I 0,1 FFFF 1

51X Ix TOCOperationFlag

1 TOC_51X_IX_OP I 0,1 FFFF 1

55A AppPwr FactorOp Flag

1 APP_55A_PWR_FACT_OP I 0,1 FFFF 1

55D DisplPwr FactorOp Flag

1 DISP_55D_PWR_FACT_OP I 0,1 FFFF 1

59-A1 AuxVx OverVolt Flag

1 AUX_59_A1_OV_OP I 0,1 FFFF 1

59-A2 AuxVx OverVolt Flag

1 AUX_59_A2_OV_OP I 0,1 FFFF 1

59-M1 MainVp OverVolt Flag

1 MAIN_59_M1_OV_OP I 0,1 FFFF 1

59-M2 MainVp OverVolt Flag

1 MAIN_59_M2_OV_OP I 0,1 FFFF 1

59N-1ResidualVoltage Op-eration Flag

1 RESIDUAL_VOLTAGE_59N_1_OPER_FLAG

I 0,1 FFFF 1

59N-2ResidualVoltage Op-eration Flag

1 RESIDUAL_VOLTAGE_59N_2_OPER_FLAG

I 0,1 FFFF 1

79- Auto-matic Re-closer Sta-tus

1 AUTO_RECLOSER_STATUS R# 0, 1, 2, 3, 4, 5

0=unknown, 1=off,2=ready, 3=run,4=lockout, 5=blocked

FFFF 1

79- Fail 1 IEEE_79_FAIL_FLAG I 0,1 FFFF 1

79- RecloseShot #1

NA IEEE_79_SHOT_1_FLAG I 0,1 NA NA

79- RecloseShot #2


79- RecloseShot #3


79- RecloseShot #4


79- VoltageBlock Trip

NA IEEE_79_VOLTAGE_BLOCK_TRIP_FLAG

I 0,1 NA NA

79- VoltageBlock Pick-up

NA IEEE_79_VOLTAGE_BLOCK_PICKUP_FLAG

I 0,1 NA NA

RecloseBlock

NA IEEE_79_RECLOSE_BLOCK_FLAG

I 0,1 NA NA

81O-1Overfre-quency OpFlag

1 MISC_81O_1_OF_OP I 0,1 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



81O-2Overfre-quency OpFlag

1 MISC_81O_2_OF_OP I 0,1 FFFF 1

81U-1 Un-derfrequen-cy Op Flag

1 MISC_81U_1_UF_OP I 0,1 FFFF 1

81U-2 Un-derfrequen-cy Op Flag

1 MISC_81U_2_UF_OP I 0,1 FFFF 1

Accumulat-ed Interrupt-ed CurrentAlarm Flag

1 ACC_INT_CURRENT_ALARM I 0,1 FFFF 1

Alarm 1 ALARM_OUTPUT I 0,1 FFFF 1

Alarm LEDFlag

1 ALARM_LED I 0,1 FFFF 1

Breaker An-ti-Pumping

1 IEEE_BREAKER_ANTI_PUMPING_FLAG

I 0,1 FFFF 1

Breaker FailOp Flag

1 BREAKER_FAIL_OP I 0,1 FFFF 1

BreakerHistory Ac-cumulatedInterruptedIA

2 BH_ACCUM_INT_IA R# 0 to 4,294,967,293 A FFFFFFFFFF 1

BreakerHistory Ac-cumulatedInterruptedIB

2 BH_ACCUM_INT_IB R# 0 to 4,294,967,293 A FFFFFFFFFF 1

BreakerHistory Ac-cumulatedInterruptedIC

2 BH_ACCUM_INT_IC R# 0 to 4,294,967,293 A FFFFFFFFFF 1

BreakerHistoryNumber ofBreaker Op-erations

1 BH_NUM_BREAKER_OPS R# 0 to 65,533 FFFF 1

Breaker Op-erationsAlarm Flag

1 BREAKER_OPS_ALARM I 0,1 FFFF 1

Breaker Po-sition

1 BREAKER_POSITION R# 0, 1, 2

0=unknown, 1=open,2=closed.

FFFF 1

BreakerState AlarmFlag

1 BREAKER_STATE_ALARM I 0,1 FFFF 1

Break-er StateChange ofState Flag

1 BREAKER_STATE_CHANGE_OF_STATE

I 0,1 FFFF 1

Break-er StateClosed Flag

1 BREAKER_STATE_CLOSED I 0,1 FFFF 1

BreakerState FailFlag

1 BREAKER_STATE_FAILURE I 0,1 FFFF 1

BreakerState Lock-out Flag

1 BREAKER_STATE_LOCKOUT I 0,1 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



BreakerState OpenFlag

1 BREAKER_STATE_OPEN I 0,1 FFFF 1

BreakerState TimeAlarm Flag

1 SLOW_BREAKER_CLOSE_TIME

I 0,1 FFFF 1

CIN_Flags_Word(NA forDDE/OPC)

1 CIN_FLAGS_WORD I 0 to 65535 FFFF 1

Comm Log-ic State

1 COMM_LOGIC_STATE I 0 to 255 FFFF 1

Contact In-put 1 Flag

1 CIN1 I 0,1 FFFF 1


1 CIN2 I 0,1 FFFF 1


1 CIN3 I 0,1 FFFF 1


1 CIN4 I 0,1 FFFF 1


1 CIN5 I 0,1 FFFF 1


1 CIN6 I 0,1 FFFF 1


1 CIN7 I 0,1 FFFF 1


1 CIN8 I 0,1 FFFF 1

Current De-mand AlarmFlag

1 CURRENT_DMD_ALARM I 0,1 FFFF 1

CurrentTHD AlarmFlag

1 CURRENT_THD_ALARM I 0,1 FFFF 1

Frequency 1 FREQ R#.## 10.00 to 99.99 Hz FFFF 100

FrequencyTrips

1 FREQUENCY_TRIPS R# 0 to 65,533 FFFF 1

Ground TripLED Flag

1 GROUND_TRIP_LED I 0,1 FFFF 1

I(Fourth CT) 2 FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(Fourth CT)Magnitude

2 FOURTH_CT_CURRENT_MAGNITUDE

R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(Fourth CT)Phase

1 FOURTH_CT_CURRENT_PHASE

R#.## -327.65 to +327.65 ° 7FFF 100

I(NegativeSequence)Magnitude

2 NEGATIVE_SEQUENCE_CURRENT_MAGNITUDE

R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(NegativeSequence)Phase

1 NEGATIVE_SEQUENCE_CURRENT_PHASE

R#.## -327.65 to +327.65 ° 7FFF 100

I(PositiveSequence)Magnitude

2 POSITIVE_SEQUENCE_CURRENT_MAGNITUDE

R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(PositiveSequence)Phase

1 POSITIVE_SEQUENCE_CURRENT_PHASE

R#.## -327.65 to +327.65 ° 7FFF 100

I(R) 2 IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(Residual)Magnitude

2 RESIDUAL_CURRENT_ MAG-NITUDE

R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(Residual)Phase

1 RESIDUAL_CURRENT_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

FP-6000


Descrip-tion

# OfReg-isters



I(Zero Se-quence)Magnitude

2 ZERO_SEQUENCE_CURRENT_MAGNITUDE

R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

I(Zero Se-quence)Phase

1 ZERO_SEQUENCE_CURRENT_PHASE

R#.## -327.65 to +327.65 ° 7FFF 100

Ia 2 IA R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ia Demand 2 IADEMAND R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ia Peak De-mand

2 IAPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ia Magni-tude

2 IA_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ia Phase 1 IA_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

Iavg 2 IAVG R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib 2 IB R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib Demand 2 IBDEMAND R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib Peak De-mand

2 IBPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib Magni-tude

2 IB_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ib Phase 1 IB_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

Ic 2 IC R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ic Demand 2 ICDEMAND R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ic Peak De-mand

2 ICPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ic Magni-tude

2 IC_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Ic Phase 1 IC_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

LED Indica-tor #1

1 LED_INDICATOR_1_FLAG I 0,1 FFFF 1

LED Indica-tor #2


LED Indica-tor #3


LED Indica-tor #4


LED Indica-tor #5


LED Indica-tor #6


LED Indica-tor #7


LED Indica-tor #8


Logic Gate1

1 LOGIC_GATE1_OUTPUT_FLAG

I 0,1 FFFF 1

Logic Gate2


I 0,1 FFFF 1

Logic Gate3


I 0,1 FFFF 1

Logic Gate4


I 0,1 FFFF 1

Logic Gate5


I 0,1 FFFF 1

Logic Gate6


I 0,1 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



LOP AlarmFlag

1 LOP_ALARM_FLAG I 0,1 FFFF 1

LOP BlockFlag

1 LOP_BLOCK_FLAG I 0,1 FFFF 1

LOP Flag 1 LOP_FLAG I 0,1 FFFF 1

Max Appar-ent Power(VA)

2 MAX_VA R# 0 to 4,294,967,293 VA 7FFFFFFF 1

Max Fre-quency

1 MAX_FREQUENCY R#.## 0 to 655.33 Hz FFFF 100

MaxI(Fourth CT)

2 MAX_FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Max Ia 2 MAX_IA R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Max Ib 2 MAX_IB R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Max Ic 2 MAX_IC R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Max Ir(Residual)

2 MAX_IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Max Reac-tive Power(VAr)

2 MAX_REACTIVE_POWER R# 0 to 4,294,967,293 VAr 7FFFFFFF 1

Max Re-al Power(Watts)

2 MAX_REAL_POWER R# 0 to 4,294,967,293 W 7FFFFFFF 1

Max Sys-tem PF(App)

1 MAX_SYSTEM_PF_APP R#.## -1.00 to +1.00 7FFF 100

Max Sys-tem PF(Disp)

1 MAX_SYSTEM_PF_DISP R#.## -1.00 to +1.00 7FFF 100

Max Vab 2 MAX_PHA_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Max Van 2 MAX_PHA_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

Max Vbc 2 MAX_PHB_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Max Vbn 2 MAX_PHB_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

Max Vca 2 MAX_PHC_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Max Vcn 2 MAX_PHC_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Appar-ent Power(VA)

2 MIN_VA R# 0 to 4,294,967,293 VA FFFFFFFFFF 1

Min Fre-quency

1 MIN_FREQUENCY R#.## 0 - 65.533 Hz FFFF 100

Min I(FourthCT)

2 MIN_FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Min Ia 2 MIN_IA R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Min Ib 2 MIN_IB R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Min Ic 2 MIN_IC R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Min Ir(Residual)

2 MIN_IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100

Min Reac-tive Power(VAr)

2 MIN_REACTIVE_POWER R# 0 to 4,294,967,293 VAr 7FFFFFFF 1

Min Re-al Power(Watts)

2 MIN_REAL_POWER R# 0 to 4,294,967,293 W 7FFFFFFF 1

Min SystemPF (App)

1 MIN_SYSTEM_PF_APP R#.## -1.00 to +1.00 7FFF 100

Min SystemPF (Disp)

1 MIN_SYSTEM_PF_DISP R#.## -1.00 to +1.00 7FFF 100

FP-6000


Descrip-tion

# OfReg-isters



Min Vab 2 MIN_PHA_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Van 2 MIN_PHA_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Vbc 2 MIN_PHB_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Vbn 2 MIN_PHB_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Vca 2 MIN_PHC_LLV R# 0 to 1,200,000 V FFFFFFFFFF 1

Min Vcn 2 MIN_PHC_LNV R# 0 to 1,200,000 V FFFFFFFFFF 1

NumberIOC Trips

1 NUM_IOC_TRIPS R# 0 to 65,533 FFFF 1

Number ofThermalTrips

1 NUM_THERMAL_TRIPS R# 0 to 65,533 FFFF 1

Number ofVAr Trips

1 NUM_VAR_TRIPS R# 0 to 65,533 FFFF 1

NumberOperatingHours

1 NUM_OPERATING_HOURS R# 0 to 65,533 FFFF 1

NumberTimes Pow-ered Up

1 NUM_TIMES_POWERED_UP R# 0 to 65,533 FFFF 1

NumberTOC Trips

1 NUM_TOC_TRIPS R# 0 to 65,533 FFFF 1

NumberUnbalanceTrips

1 NUM_UNBAL_TRIPS R# 0 to 65,533 FFFF 1

NumberVolt Trips

1 NUM_VOLT_TRIPS R# 0 to 65,533 FFFF 1

Number ofIncompleteSlave Ac-tions

NA INCOMPLETE_SLAVE_ AC-TIONS

R# 0 to 65,533 NA NA

Per PhaseCurrent De-mand Win-dow

1 PER_PHASE_I_DEMAND_WINDOW

R# 0 to 255 min FFFF 1

PercentCurrent Un-balance

1 PERCENT_CURRENT_ UNBAL-ANCE

R# 0 to 65,533 % FFFF 1

PercentTHD Ia

1 THDIA R# 0 to 65,533 % FFFF 1

PercentTHD Ib

1 THDIB R# 0 to 65,533 % FFFF 1

PercentTHD Ic

1 THDIC R# 0 to 65,533 % FFFF 1

PercentTHD Vab

1 THDVAB R# 0 to 65,533 % FFFF 1

PercentTHD Van

1 THDVAN R# 0 to 65,533 % FFFF 1

PercentTHD Vbc

1 THDVBC R# 0 to 65,533 % FFFF 1

PercentTHD Vbn

1 THDVBN R# 0 to 65,533 % FFFF 1

PercentTHD Vca

1 THDVCA R# 0 to 65,533 % FFFF 1

PercentTHD Vcn

1 THDVCN R# 0 to 65,533 % FFFF 1

PercentVoltage Un-balance

1 PERCENT_VOLTAGE_ UNBAL-ANCE

R# 0 to 65,533 % FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



PF Appar-ent

1 PFAPP R#.## -1.00 to +1.00 7FFF 100

PF Dis-placement

1 PFDISP R#.## -1.00 to +1.00 7FFF 100

Phase TripLED Flag

1 PHASE_TRIP_LED I 0,1 FFFF 1

Pickup LEDFlag

1 PICKUP_LED I 0,1 FFFF 1

PLC 79-RecloseBlocked

1 PLC_79_BLOCKED_FLAG I 0,1 FFFF 1

PLC 79-RecloseLockout

1 PLC_79_LOCKOUT_FLAG I 0,1 FFFF 1

PLC 79-Reclose Ini-tiate

NA PLC_79_INITIATE_FLAG I 0,1 NA NA

Power De-mand Win-dow

1 POWER_DEMAND_WINDOW R# 0 to 65,533 min FFFF 1

Raw Status 2 RAW_STATUS I NA FFFFFFFFFF 1

Relay 3 1 RELAY3_OUTPUT I 0,1 FFFF 1



RelayHealthy

1 RELAY_HEALTHY I 0,1 FFFF 1

Vahours(ApparentEnergy)

2 VAHRS (VAHRS =VAHRS_BASE x 10 SYSENR-GYBASE)

R# 0 to 4.294967293E+12 VA FFFFFFFFFF 1

VAhoursBase

2 VAHRS_BASE FFFFFFFFFF 1

VA (Appar-ent Power)

2 VA R# -17,280,000k to+17,280,000k

VA 7FFFFFFF 1

VA (Appar-ent Power)Alarm Flag

1 VA_PWR_ALARM I 0,1 FFFF 1

VA (Appar-ent Power)DemandAlarm Flag

1 VA_PWR_DMD_ALARM I 0,1 FFFF 1

VA (Appar-ent Power)Demand

2 VADEMAND R# 0 to 16,674k VA FFFFFFFFFF 1

VA (Appar-ent Power)DemandPeak

2 VAPEAK R# 0 to 18,634k VA FFFFFFFFFF 1

ReactivePower (VAr)Alarm Flag

1 VAR_PWR_ALARM I 0,1 FFFF 1

ReactivePower (VAr)DemandAlarm Flag

1 VAR_PWR_DMD_ALARM I 0,1 FFFF 1

ReactivePower (VAr)

2 VARS R# -17,280,000k to+17,280,000k

VAr 7FFFFFFF 1

ReactivePower De-mand (VAr)

2 VARSDEMAND R# 0 to 4,294,967,293 VAr FFFFFFFFFF 1

ReactivePower De-

2 VARSPEAK R# 0 to 4,294,967,293 VAr FFFFFFFFFF 1

FP-6000


Descrip-tion

# OfReg-isters



mand (VAr)Peak

VArhours(Negative )Base

2 NEGVARHRS_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1

VArhours(Lagging /Negative ReactiveEnergy )

2 NEGVARHRS (NEGVARHRS =NEGVARHRS_BASE x 10 SY-SENRGYBASE)

R# 0 to 4.294967293E+12 VArh FFFFFFFFFF 1

VArhours(Net Reac-tive Energy)

2 NETVARHRS (NETVARHRS =NETVARHRS_BASE x 10 SY-SENRGYBASE)

R# -2,147,483,645,000 to2,147,483,645,000

VArh 7FFFFFFF 1

NetVArhoursBase

2 NETVARHRS_BASE R# -2,147,483,645,000 to2,147,483,645,000

7FFFFFFF 1

VArhours(Leading /Positive Re-active Ener-gy)

2 POSVARHRS (POSVARHRS =POSVARHRS_BASE x 10 SY-SENRGYBASE)

R# 0 to 4.294967293E+12 VArh FFFFFFFFFF 1

VArhours(Positive)Base

2 POSVARHRS_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1

Real Power(Watts)

2 WATTS R# -17,280,000k to+17,280,000k

W 7FFFFFFF 1

Real Pow-er Demand(Watts)

2 WATTSDEMAND R# -32,767k to 32,767k W 7FFFFFFF 1

Real Pow-er Demand(Watts)Peak

2 WATTSPEAK R# 0 to 18,634k W FFFFFFFFFF 1

Real Pow-er (Watts)Alarm Flag

1 WATT_PWR_ALARM I 0,1 FFFF 1

Real Power(Watts) De-mand AlarmFlag

1 WATT_PWR_DMD_ALARM I 0,1 FFFF 1

EnergyUnits

1 SYSENRGYEXP R# 0 to 255 (i.e. 3 = Kilo, 6= Mega)

FFFF 1

Positive En-ergy Base

2 POSENERGY_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1

Positive Re-al Energy(ForwardWatthours)

2 POSENERGY (POSENERGY =POSENERGY_BASE x 10 SY-SENRGYBASE)

R# 0 to 4.294967293E+12 Wh FFFFFFFFFF 1

NegativeEnergyBase

2 NEGENERGY_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1

NegativeReal Ener-gy (ReverseWatthours)

2 NEGENERGY (NEGENERGY =NEGENERGY_BASE x 10 SY-SENRGYBASE)

R# 0 to 4.294967293E+12 Wh FFFFFFFFFF 1

Net RealEnergy (NetWatthours)

2 NETENERGY (NETENERGY= NETENERGY_BASE x 10NETENRGYBASE)

R# -2,147,483,645,000 to2,147,483,645,000

Wh 7FFFFFFF 1

NetWatthoursBase

2 NETENERGY_BASE R# -2,147,483,645,000 to2,147,483,645,000

7FFFFFFF 1

RTD Num-ber1 Tem-perature

1 RTD_1_TEMPERATURE R# 0 to 255 °C FFFF 1

FP-6000


Descrip-tion

# OfReg-isters























RTD Num-ber1 MaxTempera-ture

1 MAX_TEMPERATURE_RTD_1 R#.# 0 to 255.0 deg. C 7FFF 10















RTD Num-ber9 Max


FP-6000


Descrip-tion

# OfReg-isters



Tempera-ture





SystemNegativePeak RealPower De-mand

2 SYS_NEG_PEAK_DEMAND_WATTS

R# -2,147,483,645 to 0 W FFFFFFFFFF 1

Time ofSystemNegativePeak De-mand

NA SYS_NEG_PEAK_DEMAND_WATTS_TIME

TIME NA 0 NA

SystemPositivePeak RealPower De-mand

2 SYS_POS_PEAK_DEMAND_WATTS

R# 0 to 4,294,967,293 W FFFFFFFFFF 1

Time ofSystemPositivePeak De-mand

NA SYS_POS_PEAK_DEMAND_WATTS_TIME

TIME NA 0 NA

System Re-al PowerDemand(Watts)

2 SYS_DEMAND_WATTS R# -2,147,483,645 to+2,147,483,645

W 7FFFFFFF 1

Time ofLast Resetof SystemDemand

NA SYS_TIME_LAST_RESET_DEMAND_WATTS

TIME NA 0 NA

Time ofBreakerHistory LogTime Reset

NA BH_LOG_DATE_RESET TIME NA 0 NA

Time of To-tal HistoryLog TimeReset

NA TH_LOG_DATE_RESET TIME NA 0 NA

Time ofMax Appar-ent Power(VA)

NA TIME_MAX_VA TIME NA 0 NA

Time of MinApparentPower (VA)

NA TIME_MIN_VA TIME NA 0 NA

Time ofMax Reac-tive Power(VAr)

NA TIME_MAX_REACTIVE_POWER TIME NA 0 NA

Time of MinReactivePower (VAr)

NA TIME_MIN_REACTIVE_POWER TIME NA 0 NA

Time ofMax Re-al Power(Watts)

NA TIME_MAX_REAL_POWER TIME NA 0 NA

FP-6000


Descrip-tion

# OfReg-isters



Time of MinReal Power(Watts)

NA TIME_MIN_REAL_POWER TIME NA 0 NA

Time ofLast Reset(Min MaxPower)

NA TIME_LAST_MM_POWER_ RE-SET

TIME NA 0 NA

Timeof MaxI(Residual)

NA TIME_MAX_IR TIME NA 0 NA

Time of MinI(Residual)

NA TIME_MIN_IR TIME NA 0 NA

Timeof MaxI(Fourth CT)

NA TIME_MAX_FOURTH_CT_CURRENT

TIME NA 0 NA

Time of MinI(Fourth CT)

NA TIME_MIN_FOURTH_CT_ CUR-RENT

TIME NA 0 NA

Time ofMax Ia

NA TIME_MAX_IA TIME NA 0 NA

Time of MinIa

NA TIME_MIN_IA TIME NA 0 NA

Time ofMax Ib

NA TIME_MAX_IB TIME NA 0 NA

Time of MinIb

NA TIME_MIN_IB TIME NA 0 NA

Time ofMax Ic

NA TIME_MAX_IC TIME NA 0 NA

Time of MinIc

NA TIME_MIN_IC TIME NA 0 NA

Time ofPeak Ia

NA TIME_OF_PEAK_IA TIME NA 0 NA

Time ofPeak Ib

NA TIME_OF_PEAK_IB TIME NA 0 NA

Time ofPeak Ic

NA TIME_OF_PEAK_IC TIME NA 0 NA

Time ofLast Reset(Min MaxCurrent)

NA TIME_LAST_MM_I_RESET TIME NA 0 NA

Time of 1Phase De-mand Cur-rent Reset

NA TIME_1_PHASE_DEMAND_I_RESET

TIME NA 0 NA

Time ofLast 1Phase Cur-rent De-mand Win-dow

NA TIME_LAST_1_PHASE_I_ DE-MAND

TIME NA 0 NA

Time ofMax Van

NA TIME_MAX_PHA_LNV TIME NA 0 NA

Time of MinVan

NA TIME_MIN_PHA_LNV TIME NA 0 NA

Time ofMax Vbn

NA TIME_MAX_PHB_LNV TIME NA 0 NA

Time of MinVbn

NA TIME_MIN_PHB_LNV TIME NA 0 NA

Time ofMax Vcn

NA TIME_MAX_PHC_LNV TIME NA 0 NA

Time of MinVcn

NA TIME_MIN_PHC_LNV TIME NA 0 NA

FP-6000


Descrip-tion

# OfReg-isters



Time ofMax Vab

NA TIME_MAX_PHA_LLV TIME NA 0 NA

Time of MinVab

NA TIME_MIN_PHA_LLV TIME NA 0 NA

Time ofMax Vbc

NA TIME_MAX_PHB_LLV TIME NA 0 NA

Time of MinVbc

NA TIME_MIN_PHB_LLV TIME NA 0 NA

Time ofMax Vca

NA TIME_MAX_PHC_LLV TIME NA 0 NA

Time of MinVca

NA TIME_MIN_PHC_LLV TIME NA 0 NA

Time ofLast Reset(Min Max L-N V)

NA TIME_LAST_MM_LNV_RESET TIME NA 0 NA

Last Reset(Min Max L-L V)

NA TIME_LAST_MM_LLV_RESET TIME NA 0 NA

Time ofMax Fre-quency

NA TIME_MAX_FREQUENCY TIME NA 0 NA

Time of MinFrequency

NA TIME_MIN_FREQUENCY TIME NA 0 NA

Time ofMax Sys-tem PF(App)

NA TIME_MAX_SYSTEM_PF_APP TIME NA 0 NA

Time of MinSystem PF(App)

NA TIME_MIN_SYSTEM_PF_APP TIME NA 0 NA

Time ofLast Reset(Min MaxApp PF)

NA TIME_LAST_MM_APP_PF_ RE-SET

TIME NA 0 NA

Time ofMax Sys-tem PF(Disp)

NA TIME_MAX_SYSTEM_PF_DISP TIME NA 0 NA

Time of MinSystem PF(Disp)

NA TIME_MIN_SYSTEM_PF_DISP TIME NA 0 NA

Time ofLast Reset(Min MaxDisp PF)

NA TIME_LAST_MM_DISP_PF_RESET

TIME NA 0 NA

Time ofPeak RealPower De-mand

NA TIME_OF_PEAK_WATTS TIME NA 0 NA

Time ofPeak Ap-parent Pow-er Demand

NA TIME_OF_PEAK_VA TIME NA 0 NA

Time ofPeak Reac-tive PowerDemand

NA TIME_OF_PEAK_VARS TIME NA 0 NA

Time ofPower Re-set

NA TIME_OF_LAST_POWER_ RE-SET

TIME NA 0 NA

Time ofLast Pow-

NA TIME_OF_LAST_POWER_DEMAND_WINDOW

TIME NA 0 NA

FP-6000


Descrip-tion

# OfReg-isters



er DemandWindow

Time of En-ergy Reset

NA TIME_OF_ENERGY_RESET TIME NA 0 NA

Time of Re-set of MaxRTD Tem-peratures

NA TIME_OF_RESET_FOR_MAX_RTD

TIME NA 0 NA

THD IaMagnitude

2 THD_IA_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100

THD IbMagnitude

2 THD_IB_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100

THD IcMagnitude

2 THD_IC_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100

THD VabMagnitude

2 THD_VAB_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

THD VanMagnitude

2 THD_VAN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

THD VbcMagnitude

2 THD_VBC_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

THD VbnMagnitude

2 THD_VBN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

THD VcaMagnitude

2 THD_VCA_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

THD VcnMagnitude

2 THD_VCN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10

Timer Gate1

1 LOGIC_TIMER1_OUTPUT_FLAG

I 0,1 FFFF 1

Timer Gate2


I 0,1 FFFF 1

Timer Gate3


I 0,1 FFFF 1

Timer Gate4


I 0,1 FFFF 1

Timer Gate5


I 0,1 FFFF 1

Timer Gate6


I 0,1 FFFF 1

Total Histo-ry Accumu-lated Inter-rupted IA

2 TH_ACCUM_INT_IA R# 0 to 4,294,967,293 A FFFFFFFFFF 1

Total Histo-ry Accumu-lated Inter-rupted IB

2 TH_ACCUM_INT_IB R# 0 to 4,294,967,293 A FFFFFFFFFF 1

Total Histo-ry Accumu-lated Inter-rupted IC

2 TH_ACCUM_INT_IC R# 0 to 4,294,967,293 A FFFFFFFFFF 1

Total Histo-ry Numberof BreakerOperations

1 TH_NUM_BREAKER_OPS R# 0 to 65,533 FFFF 1

Total His-tory Num-ber of Pow-er Trips

1 POWER_TRIPS R# 0 to 65,533 FFFF 1

Total Num-ber of Trips

1 TOTAL_NUM_OF_TRIPS R# 0 to 65,533 FFFF 1

FP-6000


Descrip-tion

# OfReg-isters



TRIP1 Mon-itor ActiveFlag

1 TRIP1_MON_ACT I 0,1 FFFF 1

TRIP1 Mon-itor AlarmFlag

1 TRIP1_MON_ALM I 0,1 FFFF 1

TRIP1 Out-put Flag

1 TRIP1_OUT I 0,1 FFFF 1

TRIP2 Mon-itor ActiveFlag

1 TRIP2_MON_ACT I 0,1 FFFF 1

TRIP2 Mon-itor AlarmFlag

1 TRIP2_MON_ALM I 0,1 FFFF 1

TRIP2 Out-put Flag

1 TRIP2_OUT I 0,1 FFFF 1

TrippingDisarmedFlag

1 TRIP_DISARMED I 0,1 FFFF 1

V(Auxiliary) 2 AUXILIARY_VOLTAGE R# 0 to 1,200,000 V FFFFFFFFFF 1

V(Auxiliary)Magnitude

2 AUXILIARY_VOLTAGE_ MAG-NITUDE

R# 0 to 1,200,000 V FFFFFFFFFF 1

V(Auxiliary)Phase

1 AUXILIARY_VOLTAGE_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100

V(L-G) Av-erage

2 VLGAVG R# 0 to 1,200,000 V FFFFFFFFFF 1

V(L-L) Aver-age

2 VLLAVG R# 0 to 1,200,000 V FFFFFFFFFF 1

V(L-N) Av-erage

2 VLNAVG R# 0 to 1,200,000 V FFFFFFFFFF 1

V(NegativeSequence)Magnitude

2 NEGATIVE_SEQUENCE_VOLTAGE_MAGNITUDE


V(NegativeSequence)Phase

1 NEGATIVE_SEQUENCE_VOLTAGE_PHASE

R#.## -327.65 to +327.65 deg. 7FFF 100

V(PositiveSequence)Magnitude

2 POSITIVE_SEQUENCE_VOLTAGE_MAGNITUDE


V(PositiveSequence)Phase

1 POSITIVE_SEQUENCE_VOLTAGE_PHASE

R#.## -327.65 to +327.65 deg. 7FFF 100

V(Zero Se-quence)Magnitude

2 ZERO_SEQUENCE_VOLTAGE_MAGNITUDE


V(Zero Se-quence)Phase

1 ZERO_SEQUENCE_VOLTAGE_PHASE

R#.## -327.65 to +327.65 deg. 7FFF 100

Vab 2 VAB R# 0 to 1,200,000 V FFFFFFFFFF 1

Vab Magni-tude

2 VAB_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Vab Phase 1 VAB_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

Vag 2 VAG R# 0 to 1,200,000 V FFFFFFFFFF 1

Van 2 VAN R# 0 to 1,200,000 V FFFFFFFFFF 1

Van Magni-tude

2 VAN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Van Phase 1 VAN_PHASE R#.## -327.65 to +327.65 ° 7FFF 100

Vbc 2 VBC R# 0 to 1,200,000 V FFFFFFFFFF 1

FP-6000


Descrip-tion

# OfReg-isters



Vbc Magni-tude

2 VBC_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Vbc Phase 1 VBC_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100

Vbg 2 VBG R# 0 to 1,200,000 V FFFFFFFFFF 1

Vbn 2 VBN R# 0 to 1,200,000 V FFFFFFFFFF 1

Vbn Magni-tude

2 VBN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Vbn Phase 1 VBN_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100

Vca 2 VCA R# 0 to 1,200,000 V FFFFFFFFFF 1

Vca Magni-tude

2 VCA_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Vca Phase 1 VCA_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100

Vcg 2 VCG R# 0 to 1,200,000 V FFFFFFFFFF 1

Vcn 2 VCN R# 0 to 1,200,000 V FFFFFFFFFF 1

Vcn Magni-tude

2 VCN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1

Vcn Phase 1 VCN_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100

VoltageTHD AlarmFlag

1 VOLTAGE_THD_ALARM I 0,1 FFFF 1

Zone Inter-lock GndOp Flag

1 ZONE_INT_GROUND_OP I 0,1 FFFF 1

Zone Inter-lock OutputFlag

1 ZONE_INT_OUPUT I 0,1 FFFF 1

Zone Inter-lock PhaseOp Flag

1 ZONE_INT_PHASE_OP I 0,1 FFFF 1

Zone Inter-lock InputFlag

NA ZONE_INTERLOCK_INPUT_FLAG

I 0,1 NA NA

Zone Inter-lock GroundPickup Flag

NA ZONE_INTERLOCK_GROUND_PICKUP_FLAG

I 0,1 NA NA

Zone Inter-lock PhasePickup Flag

NA ZONE_INTERLOCK_PHASE_PICKUP_FLAG

I 0,1 NA NA

Table 7. FP-6000 Device Controls

Description Tag name DDE Type ModbusValue

Direct

Activate Relay 1 ACTIVATE_RELAY_1 I 63B X

Activate Relay 2 ACTIVATE_RELAY_2 I 63C X

Activate Relay 3 ACTIVATE_RELAY_3 I 64D X

Activate Relay 4 ACTIVATE_RELAY_4 I 64E X

Activate Relay 5 ACTIVATE_RELAY_5 I 83A X

Activate Relay 6 ACTIVATE_RELAY_6 I 83B X

Activate Zone Interlock Out-put

ACTIVATE_RELAY_8 I 83D X

Close Breaker CLOSE_DEVICE I 601 X

Comm Logic State 1 COMM_LOGIC_1 I 846 X



FP-6000



Direct


Comm Logic State Off COMM_LOGIC_OFF I 845 X

Deactivate Relay 1 DEACTIVATE_RELAY_1 I 63D X

Deactivate Relay 2 DEACTIVATE_RELAY_2 I 63E X

Deactivate Relay 3 DEACTIVATE_RELAY_3 I 64F X

Deactivate Relay 4 DEACTIVATE_RELAY_4 I 650 X

Deactivate Relay 5 DEACTIVATE_RELAY_5 I 83E X

Deactivate Relay 6 DEACTIVATE_RELAY_6 I 83F X

Deactivate Zone InterlockOutput

DEACTIVATE_RELAY_8 I 841 X

Open Breaker OPEN_DEVICE I 600 X

Reset Alarm RESET_ALARM I 656 X

Reset All Min Max RESET_ALL_MIN_MAX I 61F X

Reset All RTD Max Values RESET_ALL_SENSORS_MIN_MAX_VALUES I 880 X

Reset Auto Recloser Lock-out

RESET_AUTO_RECLOSER_LOCKOUT I 87F X

Reset Demand Watts Wnd RESET_DEMAND_WATTS_WND I 607 X

Reset Energy RESET_ENERGY I 606 X

Reset Logic Latch 1 RESET_LOGIC_LATCH_1 I 866 X

Reset Logic Latch 2 RESET_LOGIC_LATCH_2 I 867 X

Reset Min Max Current RESET_MIN_MAX_I I 620 X

Reset Min Max L-L Voltage RESET_MIN_MAX_LL_VOLTS I 621 X

Reset Min Max L-N Voltage RESET_MIN_MAX_LN_VOLTS I 622 X

Reset Min Max PF App RESET_MIN_MAX_PF_APP I 624 X

Reset Min Max PF Disp RESET_MIN_MAX_PF_DSP I 623 X

Reset Min Max Power RESET_MIN_MAX_POWER I 625 X

Reset Peak Demand Current RESET_DEMAND_I I 609 X

Reset Peak Demand Watts RESET_DMD_WATTS I 602 X

Reset RTD #1 Max Value RESET_SENSOR_1_MIN_MAX_VALUES I 881 X

Reset RTD #10 Max Value RESET_SENSOR_10_MIN_MAX_VALUES I 88A X

Reset RTD #11 Max Value RESET_SENSOR_11_MIN_MAX_VALUES I 88B X









Reset Sensor #13 Min/MaxValue

RESET_SENSOR_13_MIN_MAX_VALUES I 88D X


RESET_SENSOR_14_MIN_MAX_VALUES I 88E X


RESET_SENSOR_15_MIN_MAX_VALUES I 88F X


RESET_SENSOR_16_MIN_MAX_VALUES I 890 X

Reset Slave Stats RESET_SLAVE_STATS I 649 X

Reset System Demand RESET_SYSTEM_DEMAND I 658 X

Reset Trip RESET_UNIT I 603 X

PM3



Direct

Select Active Group 1 ACTIVE_SET_GROUP_1 I 855 X




PM3Table 8. PM3 Device Objects

Description # of ModbusRegisters


Range Units InvalidNumber

ScaleFactor

Status 1 STATN R# 0, 4, 38 (See the Sta-tus Codes table in Ap-pendix A of the Power-Net User's Guide.)

FFFF 1

Status (String) NA STATT M NA NA NA

Status Secondary 1 STAT2N R# 0, 45, 46, (See theStatus Codes tablein Appendix A of thePowerNet User'sGuide and in the sec-tion called “Additionsto Status and ReasonCodes” [94] in thisGuide.)

FFFF 1

Reason 1 RSONN R# 0, 1, 2, 3, 4, 5, 6, 18,47, 339, 340 (See theReason Codes ta-ble in Appendix A ofthe PowerNet User'sGuide and in the sec-tion called “Additionsto Status and ReasonCodes” [94] in thisGuide.)

FFFF 1

Reason (String) NA RSONT M NA NA NA

DDE DeviceAlarm

NA ALARM I 0-30, 200-249 (Seethe Alarm Codes ta-ble in Appendix A ofthe PowerNet User'sGuide and in the sec-tion called “Additionsto Status and ReasonCodes” [94] in thisGuide.)

NA NA

Comm Version NA COM_VERSION I 0 to 15 NA NA


Division Code NA DIV_CODE I 35 NA NA


Ia (RMS) 1 IA R#.# 0 to 630 A FFFF 10

Ib (RMS) 1 IB R#.# 0 to 630 A FFFF 10

Ic (RMS) 1 IC R#.# 0 to 630 A FFFF 10

Iavg (RMS) 1 IAVG R#.# 0 to 630 A FFFF 10

Frequency 1 FREQ R#.# 45 to 65 Hz FFFF 10

Reverse Real En-ergy (Watthours)

2 NEGENERGY R# 0 to 999999999000 Wh FFFFFFFF 1

Reverse EnergyBuffer

2 NEGENERGY_BASE R# 0 to 4294967295 FFFFFFFF 1

Lagging ReactiveEnergy (Varhours)

2 NEGVARHRS R# +/- 999999999000 varh FFFFFFFF 1

Lagging VarhoursBuffer

2 NEGVARHRS_BASE R# 0 to 4294967295 FFFFFFFF 1

PM3





ScaleFactor

Net Real Energy(Watthours)

2 NETENERGY R# +/- 999999999000 Wh 7FFFFFFF 1

Net WatthoursBuffer

2 NETENERGY_BASE R# +/- 2147483647 7FFFFFFF 1

Net Reactive En-ergy (Varhours)

2 NETVARHRS R# +/- 999999999000 varh 7FFFFFFF 1

Net VarhoursBuffer

2 NETVARHRS_BASE R# +/- 2147483647 7FFFFFFF 1

PF Apparent 1 PFAPP R#.## +/- 1.00 7FFF 100

PF App Phase A 1 PFAPPA R#.## +/- 1.00 7FFF 100

PF App Phase B 1 PFAPPB R#.## +/- 1.00 7FFF 100

PF App Phase C 1 PFAPPC R#.## +/- 1.00 7FFF 100

Forward Real En-ergy (Watthours)

2 POSENERGY R# +/- 999999999000 Wh FFFFFFFF 1

Forward EnergyBuffer

2 POSENERGY_BASE R# 0 to 4294967295 FFFFFFFF 1

Leading ReactiveEnergy (Varhours)

2 POSVARHRS R# +/- 999999999000 varh FFFFFFFF 1

Leading VarhoursBuffer

2 POSVARHRS_BASE R# 0 to 4294967295 FFFFFFFF 1

Raw Status 2 RAW_STATUS I NA FFFFFFFF 1

System RealPower Demand(Watts)

2 SYS_DEMAND_WATTS R# 0 to 2147483646 W 7FFFFFFF 1

System NegativePeak Real PowerDemand

2 SYS_NEG_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1

System PositivePeak Real PowerDemand

2 SYS_POS_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1

Energy Units 1 SYSENRGYEXP R# 0 to 65534 FFFF 1

Apparent Power(VA)

2 VA R# 0 to 2147450880 VA 7FFFFFFF 1

Vab 1 VAB R#.# 0 to 600 V FFFF 10

Apparent Energy(VAhours)

2 VAHRS R# 0 to 999999999000 VAh FFFFFFFF 1

VAhours Buffer 2 VAHRS_BASE R# 0 to 4294967295 FFFFFFFF 1

Apparent Power(VA) Phase A

2 VAMPA R# 0 to 2147450880 VA FFFFFFFF 1

Apparent Power(VA) Phase B

2 VAMPB R# 0 to 2147450880 VA FFFFFFFF 1

Apparent Power(VA) Phase C

2 VAMPC R# 0 to 2147450880 VA FFFFFFFF 1

Van 1 VAN R#.# 0 to 600 V FFFF 10

Reactive Power(Vars)

2 VARS R# +/- 1073709057 var 7FFFFFFF 1

Reactive Power(Vars) Phase A

2 VARSA R# +/- 1073709057 var 7FFFFFFF 1

Reactive Power(Vars) Phase B

2 VARSB R# +/- 1073709057 var 7FFFFFFF 1

Reactive Power(Vars) Phase C

2 VARSC R# +/- 1073709057 var 7FFFFFFF 1

Vbc 1 VBC R#.# 0 to 600 V FFFF 10

Vbn 1 VBN R#.# 0 to 600 V FFFF 10

Vca 1 VCA R#.# 0 to 600 V FFFF 10

Vcn 1 VCN R#.# 0 to 600 V FFFF 10

V(L-L) Average 1 VLLAVG R#.# 0 to 600 V FFFF 10

PM3





ScaleFactor

V(L-N) Average 1 VLNAVG R#.# 0 to 600 V FFFF 10

Real Power(Watts)

2 WATTS R# +/- 1073709057 W 7FFFFFFF 1

Real Power(Watts) Phase A

2 WATTSA R# +/- 1073709057 W 7FFFFFFF 1

Real Power(Watts) Phase B

2 WATTSB R# +/- 1073709057 W 7FFFFFFF 1

Real Power(Watts) Phase C

2 WATTSC R# +/- 1073709057 W 7FFFFFFF 1

Table 9. PM3 controls

Description Tag name DDE Type Modbus Value (hexideci-mal)

Direct BIM / BIMII

Reset Power Up RESET_POWER_UP I 833 X

Reset Slave Stats RESET_SLAVE_STATS I 649 X

Reset System DemandWatts

RESET_SYSTEM_DEMAND I 658 X

Table 10. PM3 Breaker Device Objects


Tag Name DDE Type Range Invalid Number Scale Fac-tor

Status 1 STATN R# 0, 1, 2, 3 (See the Status Codestable in Appendix A of the Power-Net User's Guide and in the sec-tion called “Additions to Statusand Reason Codes” [94] in thisGuide.)

FFFF 1

Status (String) NA STATT M NA NA NA

Status Secondary 1 STAT2N R# 0, 45 (See the Status Codes ta-ble in Appendix A of the Power-Net User's Guide and in the sec-tion called “Additions to Statusand Reason Codes” [94] in thisGuide.)

FFFF 1

Reason 1 RSONN R# 0, 1, 2, 3, 4, 5, 6, 341, 480 (See theReason Codes table in Appendix Aof the PowerNet User's Guide andin the section called “Additions toStatus and Reason Codes” [94]in this Guide.)

FFFF 1

Reason (String) NA RSONT M NA NA NA

DDE DeviceAlarm

NA ALARM I 0-30, 200-249 (See the AlarmCodes table in Appendix A of thePowerNet User's Guide and in thesection called “Additions to Statusand Reason Codes” [94] in thisGuide.)

NA NA

Comm Version NA COM_VERSION I 0 to 15 NA NA


Division Code NA DIV_CODE I 32 NA NA


Raw Status 2 RAW_STATUS I NA FFFFFFFF 1

Breaker Position 1 BREAKER_POSITION I 0, 1, 2 (See the Status Codes ta-ble in Appendix A of the Power-Net User's Guide and in the sec-tion called “Additions to Statusand Reason Codes” [94] in thisGuide.)

FFFF

Additions to Status and Reason Codes


Additions�to�Status�and�Reason�CodesAppendix A of the PowerNet documentation provides an incomplete set of statuscodes and reason codes. The following tables, in addition to the tables in Appendix A,provide a complete set of codes.

Table 11. Status Codes

Short Description Long Description Meaning Status Reason Code

n/a n/a The device state is "not ap-plicable" or "not meaning-ful" at this time.

45

POWERED UP Powered Up The device was powereddown and has subsequent-ly been re-powered.

46

PICKED UP Picked Up A protective element withinthe device has picked up.

47

TEST Test The device is in a teststate.

48

DISABLED Disabled The device is in a disabledstate.

49

DISARMED Disarmed The device is in a disarmedstate.

50

FAILED Failed The controlled device failedto operate.

51

PH A TRIP Phase A Trip The device is in a trip statedue to a protective elementthat has operated due toelectrical Phase A.

52

PH B TRIP Phase B Trip The device is in a trip statedue to a protective elementthat has operated due toelectrical Phase B.

53

PH C TRIP Phase C Trip The device is in a trip statedue to a protective elementthat has operated due toelectrical Phase C.

54

NEUT TRIP Neutral Trip The device is in a trip statedue to a protective elementthat has operated due tothe electrical Neutral.

55

GRND TRIP Ground/Earth Trip The device is in a trip statedue to a protective elementthat has operated due tothe electrical Ground/Earth.

56

PH A ALM Phase A Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phase A.

57

PH B ALM Phase B Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phase B.

58

PH C ALM Phase C Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phase C.

59

NEUT ALM Neutral Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to the electrical Neu-tral.

60

GROUND Ground/Earth The device is in an alarmstate due to a protectiveelement that has operat-ed due to the electricalGround/Earth.

61




PH AB ALM Phase AB Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phases A& B.

62

PH BC ALM Phase BC Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phases B& C.

63

PH CA ALM Phase CA Alarm The device is in an alarmstate due to a protective el-ement that has operateddue to electrical Phases C& A.

64

GOOD SRC On Good Source The device is on a goodelectrical source.

65

OVERLOAD Overload The device is in an over-load state due to a pro-tective element that hassensed an electrical over-load condition.

66

FIXEDINST Fixed Instantaneous The device state is due toa fixed instantaneous over-current condition.

67

HIGHINST High Instantaneous The device state is due toa high instantaneous over-current condition.

68

… … … …

UNDEFINED (225) Undefined Status Code(225)

The device status code isundefined (Code = 225)

225



Table 12. Reason Codes


DISARM Disarmed The device state is dis-armed.

226

STOPPED Stopped The device state isstopped.

227

RESET Reset The device state is reset. 228

POWERUP Powered Up The device was powereddown and has subsequent-ly been powered up.

229

MCRTRIP Making Current Release The device state is due tomaking current release op-eration

230

HIGH INST High Instantaneous The device state is due tothe high instantaneous cur-rent.

231

STPMISMAT Setpoint Mismatch The device has detected asetpoint mismatch.

232

STPTRAN Setpoint Transfer Error The device has detected asetpoint transfer error.

233

ACCBUS Accessory Bus The reason for the devicestate is due to an input onthe accessory bus.

234

THD Total Harmonic Distortion The device state is due toelectrical total harmonicdistortion.

235

PWRFACT Power Factor The device state is due topower factor

236

KWDMD Demand kW The device state is due toreal power (kW) demand.

237

KVADMD Demand kVA The device state is due toapparent power (kVA) de-mand.

238

OP COUNT Operations Count The device state is due tothe device operation count.

239

HIST Historical Data The device state is dueto a previous operation orcondition (i.e. historical)

240

ERROR Error The device has detectedan error.

241

WATDOG WatchDog The reason for the devicestate is due to a watchdogtimer error.

242

CBEMA CBEMA The device state is due toa ITIC/CBEMA event.

243

HGHSPEED High Speed The device state is due toa high speed condition.

244

SETCHG Settings Saved The device settings havebeen saved.

245

EMR_OVRD Emergency Override The device state is due toan emergency override op-eration.

246

RESERVED Reserved (247) The reason code is re-served (Code = 247)

247

… … …

RESERVED Reserved (255) The reason code is re-served (Code = 255)

255

FTSOP Fail to Sync On Phase The device state is due toa failure to synchronize onphase.

256




FTSOF Fail to Sync On Frequency The device state is due toa failure to synchronize onfrequency

257

FTSOV Fail to Sync On Voltage The device state is due toa failure to synchronize onvoltage

258

INST Instantaneous The device state is due tothe instantaneous overcur-rent protection element.

259

LONG DELAY Inverse Time Long Delay The device state is due tothe inverse long delay timeovercurrent protection ele-ment.

260

NEUTRAL Inverse Time Neutral The device state is due tothe inverse time neutralovercurrent protection ele-ment.

261

LONG DELAY Long Delay The device state is due tothe long delay time over-current protection element.

262

SHORTDELAY Short Delay The device state is due tothe short delay time over-current protection element.

263

GND FAULT Ground Fault The device state is due tothe ground fault protectionelement.

264

EARTHFAULT Earth Fault The device state is due tothe earth fault protection el-ement.

265

ENGINETST Engine Test The device state is due toan engine test.

266

EMERINHBT Emergency Inhibit The device state is due toan emergency inhibit oper-ation.

267

MNTRMODE Monitor Mode The device state is duemonitor mode.

268

ABORT Abort The device state is due anaborted operation.

269

INACTCHAN Inactive Channel(s) The device state is due aninactive channel

270

CKSUMFAIL Checksum Test Failed The device checksum testhas failed.

271

FAILSAFE Failsafe The device state is due afailsafe condition

272

POWER Power The device state is due anelectrial power protectionelement.

273

CURR THD Current THD The device state is due anelectrial current THD pro-tection element.

274

VOLT THD Voltage THD The device state is due anelectrial voltage THD pro-tection element.

275

PICKUP Pickup The device state is due apickup of an electrial pro-tection element.

276

TRIP Trip The device state is due atrip issued by electrial pro-tection element.

277

CONTACT IN Contact Input The device state is due acontact input.

278

SYSTEM System The device state is due asystem operation.

279




CONTROL Control The device state is due acontrol

280

PHASE OC Phase Overcurrent The device state is due tothe phase overcurrent pro-tection element.

281

GRND OC Ground Overcurent The device state is due tothe ground overcurrent pro-tection element.

282

INST OC Instantaneous Overcurrent The device state is due tothe instantaneous over-current protection element(50).

283

INVTIME OC Inverse Time Overcurrent The device state is due tothe inverse time overcur-rent protection element(51).

284

ALARM Alarm The device state is due analarm.

285

VOLTAGE Voltage The device state is due anelectrial voltage protectionelement.

286

FREQ Frequency The device state is due anelectrial frequency protec-tion element.

287

OPEN BKR Open Breaker Open circuit breaker. 288

CLOSE BKR Close Breaker Close circuit breaker. 289

BKR CLOSED Breaker Closed The device has detected aclosed circuit breaker.

290

BKR ALARM Breaker Alarm The device state is due acircuit breaker alarm.

291

CONFIG Configuration The device state is due toconfiguration.

292

SCALING Scaling The device state is due toscaling.

293

WIRING Wiring The device state is due towiring.

294

MAINT Maintenance Mode The device is in mainte-nance mode.

295

AR FAILURE Automatic Recloser Failure The automatic recloser hasfailed.

296

FIXEDINST Fixed Instantaneous The device state is due afixed instantaneous opera-tion.

297

HIGHINST High Instantaneous The device state is due ahigh instantaneous opera-tion.

298

299 Reserved (299) The reason code is re-served (Code = 299)

299

EXTERNAL External event The device state is due toan external event.

300

PH IOC 50P: Instantaneous PhaseOvercurrent

The device state is due tothe instantaneous phaseovercurrent protection ele-ment (50P).

301

IG IOC 50G: InstantaneousGround Overcurrent

The device state is due tothe instantaneous groundovercurrent protection ele-ment (50G).

302

IN IOC 50N: Instantaneous NeutralOvercurrent

The device state is due tothe instantaneous neutralovercurrent protection ele-ment (50N).

303




IR IOC 50R: Instantaneous Resid-ual Overcurrent

The device state is due tothe instantaneous residualovercurrent protection ele-ment (50R).

304

PH TOC 51P: Inverse Time PhaseOvercurrent

The device state is dueto the inverse time phaseovercurrent protection ele-ment (51P).

305

IG TOC 51G: Inverse Time GroundOvercurrent

The device state is due tothe inverse time groundovercurrent protection ele-ment (51G).

306

IN TOC 51N: Inverse Time NeutralOvercurrent

The device state is due tothe inverse time neutralovercurrent protection ele-ment (51N).

307

IR TOC 51R: Inverse Time Residu-al Overcurrent

The device state is due tothe inverse time residualovercurrent protection ele-ment (51R).

308

OV 59: Overvoltage The device state is due tothe overvoltage protectionelement (59).

309

UV 27: Undervoltage The device state is due tothe undervoltage protectionelement (27).

310

AUX OV 59A: Auxiliary Overvoltage The device state is due tothe auxiliary overvoltageprotection element (59A).

311

AUX UV 27A: Auxiliary Undervolt-age

The device state is due tothe auxiliary undervoltageprotection element (27A).

312

UFREQ 81U: Underfrequency The device state is due tothe underfrequency protec-tion element (81U).

313

OFREQ 81O: Overfrequency The device state is due tothe overfrequency protec-tion element (81O).

314

I UNBAL 46: Current Unbalance The device state is due tothe overfrequency protec-tion element (81O).

315

V UNBAL 47: Voltage Unbalance The device state is due tothe voltage unbalance pro-tection element (47).

316

APP PF 55A: Apparent Power Fac-tor

The device state is due tothe apparent power factorprotection element (55A).

317

DISP PF 55D: Disp Power Factor The device state is due tothe displacement powerfactor protection element(55D).

318

LOW BATT Low Battery: Save all logdata

The device state is due tolow battery (save all log da-ta).

319

50X 50X: Instantaneous AuxOvercurrent

The device state is due tothe instantaneous auxilliaryovercurrent protection ele-ment (50X).

320

51X 51X: Inverse Time Auxil-liary Overcurrent

The device state is due tothe inverse time auxilliaryovercurrent protection ele-ment (51X).

321

ZONEINTPIC Zone Interlock Pickup The device state is due tozone interlock pickup.

322




ACCINTCUR Accumulated Interrupt Cur-rent

The device state is due tothe accumulated interruptcurrent protection element.

323

51P2 51P2: Inverse Time PhaseOvercurrent

The device state is dueto the inverse time phaseovercurrent secondary pro-tection element (51P2).

324

59NG 59NG: Neutral-GroundOvervoltage

The device state is due tothe neutral-to-ground over-voltage protection element(59NG).

325

LOP Loss Of Potential The device state is due tothe loss of potential.

326

POWER PU 32: Power Pickup The device state is due topickup of the power protec-tion element (32).

327

59N 59N: Neutral Overvoltage The device state is dueto the neutral overvoltageprotection element (59N).

328

POWER TRIP 32: Overpower/Underpow-er

The device state is due toa trip issued by the powerprotection element (32).

329

MAINT Maintenance Mode The device state is due tomaintenance mode.

330

BKR MECH Breaker Mechanism Fail-ure

The device has detected acircuit breaker mechanismfailure

331

AR LOCKOUT 79: Automatic RecloserLockout

The automatic recloser isin lockout.

332

THERMAL Thermal Trip The device state is due toa trip issued by a thermalprotection element.

333

THERMAL Thermal Alarm The device state is due toan alarm issued by a ther-mal protection element.

334

GROUP VAR Group VAr Trip The device state is due toa trip issued by the groupVAr protection element.

335

HACCINTCUR Hourly Accumulated Inter-rupt Current

The device state is due tohourly accumulated inter-rupt current

336

WEAR ALARM Breaker Wear Alarm The circuit breaker wearalarm is active

337

LOCKOUT Breaker Wear Lockout The circuit breaker islocked out due to exces-sive wear

338

ENGSTORE Metered Energy StorageError

Metered Energy StorageError

339

MEASURE Meter Measurement Fail-ure

Meter Measurement Fail-ure

340

AUX Auxiliary Contact(s) Auxiliary Contact(s) 341

… … … …

398 Reserved (398) The reason code is re-served (Code = 398)

398

RES OUT RG Reason Code Out ofRange

The reason code is out ofrange

399

EXTERNAL External Condition #1 External Condition #1 400

PH IOC Instantaneous Phase Over-current

Instantaneous Phase Over-current

401

IG IOC Instantaneous GroundOvercurrent

Instantaneous GroundOvercurrent

402




IN IOC Instantaneous NeutralOvercurrent

Instantaneous NeutralOvercurrent

403

IR IOC Instantaneous ResidualOvercurrent

Instantaneous ResidualOvercurrent

404

PH TOC Inverse Time Phase Over-current

Inverse Time Phase Over-current

405

IG TOC Inverse Time Ground Over-current

Inverse Time Ground Over-current

406

IN TOC Inverse Time Neutral Over-current

Inverse Time Neutral Over-current

407

IR TOC Inverse Time ResidualOvercurrent

Inverse Time ResidualOvercurrent

408

AUX OV Auxiliary Overvoltage Auxiliary Overvoltage 409

AUX UV Auxiliary Undervoltage Auxiliary Undervoltage 410

I UNBAL Current Unbalance Current Unbalance 411

V UNBAL Voltage Unbalance Voltage Unbalance 412

APP PF Apparent Power Factor Apparent Power Factor 413

DISP PF Disp Power Factor Disp Power Factor 414

WATT Watts Watts 415

VA VA VA 416

Var VAr VAr 417

WATT DMD Power Demand Power Demand 418

VA DEMAND VA Demand VA Demand 419

Var DEMAND VAr Demand VAr Demand 420

CURR DMD Current Demand Current Demand 421

CNT MAINT Contact Maintenance Contact Maintenance 422

COMM Control via Communica-tions

Control via Communica-tions

423

CONT DISAG Contact Disagreement Contact Disagreement 424

BKR FAIL Breaker Failure Breaker Failure 425

OP TIMEOUT Operation Time Exceeded Operation Time Exceeded 426

COIL SUPER Coil Supervision Coil Supervision 427

LOGIC Programmable Logic Programmable Logic 428

DIAGWARN1 Diagnostic Warning #1 Diagnostic Warning #1 429

DIAGFAIL1 Diagnostic Failure #1 Diagnostic Failure #1 430

LOW BATT Low Battery Low Battery 431

MULTIPLE Multiple Causes Multiple Causes 432






















LONG DELAY Long Delay Phase Over-current

Long Delay Phase Over-current

451

SHORT DELA Short Delay Phase Over-current

Short Delay Phase Over-current

452

FINST #1 Fixed Instantaneous PhaseOvercurrent #1

Fixed Instantaneous PhaseOvercurrent #1

453

REV POW Reverse Power Reverse Power 454



455

REV PHASE Reverse Phase Reverse Phase 456

I NEAR PU Phase Current Near Pickup Phase Current Near Pickup 457



458

OVERTEMP Over-temperature Over-temperature 459

LD NEUTRAL Long Delay Neutral Over-current

Long Delay Neutral Over-current

460

EXTERNAL 2 External Condition #2 External Condition #2 461


GND FAULT Ground Fault (Instanta-neous or Delay)

Ground Fault (Instanta-neous or Delay)

463

EARTH Earth Fault (Instantaneousor Delay)

Earth Fault (Instantaneousor Delay)

464







MULT EXT Multiple External Condi-tions

Multiple External Condi-tions

471

MOTOR BNG Motor Bearing Tempera-ture

Motor Bearing Tempera-ture

472

LOAD BNG Load Bearing Temperature Load Bearing Temperature 473

GND DELAY Time Delayed GroundOvercurrent

Time Delayed GroundOvercurrent

474

VOLT SAG Voltage Sag Voltage Sag 475

VOLT SWELL Voltage Swell Voltage Swell 476

INTERLOCK Safety Interlock Safety Interlock 477

RTC Real-Time Clock Real-Time Clock 478

TRIP BLOCK Trip Blocked Trip Blocked 479

NONE Cause N/A (none) Cause N/A (none) 480

TRANSIENT Voltage Transient Voltage Transient 481

RTD RTD RTD 482

FREQOUTBND Frequency Out of Bounds Frequency Out-of-Bounds 483

CK AUX SW Check Auxillary Switch Check Auxillary Switch 484

MISMATCH Sensor Mismatch Sensor Mismatch 485

PHASEROT Phase Rotation Phase Rotation 486

DIAGFAILPU Diagnostic Failure on Pow-er Up

Diagnostic Failure on Pow-er Up

487




NONVOLMEM Non-Volatile Memory Non-Volatile Memory 488

TIMEDLYWV Time Delayed watt-var Time Delayed Watt-VAr 489

OCWATTVAR Overcurrent watt-var Overcurrent Watt-VAr 490

DISCONPOS Disconnect Position The device has sensed adisconnect position condi-tion.

491

SHNTRPPRB Shunt Trip Problem The device has sensed ashunt trip problem.

492

WARN UNIT Warning: Replace Unit The device has sensed anincipient failure. The unitshould be replaced.

493

FAIL UNIT Failure: Replace Unit The device has sensed afailure. The unit must bereplaced.

494

Installing�PowerNetImportant

When upgrading PowerNet to version 3.40, use the PNUPDATE key ONLY. Ifyou wish to add a new feature, run the installation again and enter the appropri-ate key then.

You must manually assign the account running PowerNet (normally, BUILTIN\Administors group) to the sysadmin role in the instance of SQL Server hous-ing the PowerNet database.

When installing a PowerNet system on either Windows 7 or Windows Server2008, after installation completes you will need to reboot twice. This is in addi-tion to the reboot during the PowerNet installation.

The PowerNet installation file, setup.exe, can be found in the PowerNet folder of thePXS installation DVD. Follow the installation instructions in the PowerNet documenta-tion. Documentation can be found in the following folders on the DVD:

• Manuals can be found in PowerNet\PowerNet\PowerNet_PDF

• Help files may be found in PowerNet\PowerNet\PowerNet_Help

• Application notes may be found in PowerNet\App_Notes. Two of the applica-tion notes, which were updated for this release, are also presented as the followingchapters.

Also, refer to the PXS Release Notes for additional PowerNet specific information.

PowerNet�for�Non-Administrative�UsersWhile PowerNet must be installed by an administrative user, it is possible to run Pow-erNet through an account that's a member of the Power User's group. The followingsections cover how to set up PowerNet to run with such an account.

Adding�the�PowerNet�User�to�the�Required�Groups

To create the users groups:

1. From the Windows Start menu, right-click My Computer (or Computer) and se-lect Manage.

2. In the Computer Management utility, expand Local Users and Groups. Insome versions of Windows, this is under Configuration.

3. Right-click Groups and select Power Users.

4. Right-click Power Users and select Add to Group.

5. Click Add and add the account.

6. Click OK.

7. Repeat the above procedure to add the user to the PowerNetPowerUser andPowerNetUser groups.

8. Right-click Users and select Properties.

9. Select the user in the Members list.

10. Click Remove.

11. Click OK.

PowerNet�Domain�Server�Configuration

Note

The following procedures are for Windows Server 2008. If you are using adifferent version of Windows, the locations and steps might be slightly differ-ent.

To set the PowerNet folder permissions:

1. Navigate to the Eaton Power Xpert Software folder and right-click the Pow-erNet folder. Select Properties.

2. Under Group or user names, click the Add button.

3. Click the Advanced button.

4. In the Select users or Groups dialog box, click the Find Now button.

5. Select the user from the Search results list, then click the OK button.


PowerNet Client Configuration


7. In the Permissions for PowerNet dialog box, select Allow for Full control.

Figure 35. Selecting Full Control for an Account

8. Click the Apply button.

9. Click the Sharing tab.

10. Click the Advanced Sharing button.

11. Select Share this folder.

12. Make sure Everyone is selected.

13. Select Allow under Full Control.

14. Click the OK button and then again on the Advanced Sharing dialog box.

15. Click the General tab.

16. Clear the Read-only selection.

17. Click the Close button.

18. In the Confirm Attribute Changes dialog box, click the OK button to apply theunset read-only change.

PowerNet�Client�ConfigurationTo set the PowerNet folder permissions:

1. Navigate to the Eaton Power Xpert Software folder and right-click the Pow-erNet folder. Select Properties.

PowerNet Client Configuration


2. Under Group or user names, click the Add button.

3. Click the Advanced button.

4. In the Select users or Groups dialog box, click the Find Now button.

5. Select the user from the Search results list, then click the OK button.


7. In the Permissions for PowerNet dialog box, select Allow for Full control.

8. Click the Apply button.

9. Click the Sharing tab.

10. Click the Advanced Sharing button.

11. Select Share this folder.

12. Make sure Everyone is selected.

13. Select Allow under Full Control.

14. Click the OK button and then again on the Advanced Sharing dialog box.

15. Click the General tab.

16. Clear the Read-only selection.

17. Click the Close button.

18. In the Confirm Attribute Changes dialog box, click the OK button to apply theunset read-only change.

PowerNet�Server�with�Remote�SQL�ServerThe PowerNet Database Server usually runs on the same PC as the SQL Serverdatabase. However, there are instances where you may need these two applicationsto run on separate machines. This following explains how to set up such an arrange-ment.

Prerequisites:

• SQL Server has already been installed on the PC.

• If using SQL Server 2005 or SQL Server 2008, SQL Backward Compatibility mustbe installed on the PC. The installation file (SQLServer2005_BC.msi) for this isavailable in the PowerNet\SQLBC folder on the PXS DVD.

• SQL Management Studio must be installed. This is covered in Installing MicrosoftSQL Server Management Studio 2008 [63].

• The Windows Firewall should be turned off. Also, on Windows Server 2008, theAdvanced Firewall (under Administrative Tools) must be turned off.

• On Windows Server 2008 in the Network and Sharing Center, the Network Dis-covery and File Sharing options must be turned on.

• On Windows Server 2008, User Account Control (UAC) must be turned off.

To Set Up the PowerNet Databases on a Remote PC

1. Log on as an Administrator. You must have privileges to create Windows UserGroups, as well as create databases, tables, etc.

2. Create the following files:

NGSWINST.INI This must be located in the WINNT or Windows folder. Thecontents must have a path pointing to a folder where the Pow-erNet SQL Server database files and transaction log files areto be located. If this folder does not already exist, you mustcreate it. The historical PowerNet Microsoft Access databas-es must be located in this folder if you wish to import previoushistorical data into the SQL Server database. For example:

[DomainShare] _PNetDb=drive:\PowerNet\Database

DBSVRNAME.INI This must be located in the _PNetDb folder. The contentsmust include the following where myservername is the SQLServer Server instance that you want to use. For example:

[MSDE]SQLServerName=myservername

3. Setup Windows sharing for the folder in which the PowerNet SQL Serverdatabases will be located. Set the share name to _PNetDb.

4. Copy the Microsoft Access databases to the _PNetDb folder if you want to importa previous PowerNet system into the new SQL Server databases.

5. Copy the contents of the PowerNet\EBILLData folder located on the PXS DVDinto a working folder on the remote PC.


6. Launch a Windows command prompt window and navigate to the working folder.Run CreateEBillDatabase.exe to create the engbill32 database using thefollowing syntax:

CreateEBillDatabase.exe servername engbill32 datadirectory

Where:

servername is the name of the SQL Server instance.

datadirectory is the path to the SQL Server database files and transactionlog files folder. This is the path that you previously specifiedin the NGSWINST.INI file.

7. While in the working folder, from the command line runConvertEBillDatabase.exe to create engbill32 tables and/or import oldengbill32 Access data into the SQL Server database. You can use the follow-ing syntax:

ConvertEBillDatabase.exe n

Where n is either:

0 to create engbill32 tables.

1 to create the engbill32 tables and import the previous Access engbill32data into the new SQL Server database.

8. You'll next use ProjectDTSPowerNetDBCreate.exe to create the remain-ing historical databases. If you're using SQL Server 2005 or SQL Server2008, this program requires SQL Backward Compatibility. Before you can runProjectDTSPowerNetDBCreate.exe you must copy the following files from thePowerNet\PowerNet\Config folder on the PXS DVD to a working folder onthe remote PC.• ProjectDTSPowerNetDBCreate.exe• COMCTL32.DLL• MSCOMCTL.OCX• RICHTX32.OCX• COMDLG32.OCX

Also, copy the following file from the PowerNet folder on the PXS DVD to thesame working folder on the remote PC:

• SQLDMO.DLL

9. The three ActiveX controls (.ocx files) must be registered using regsvr32.exe.From a Windows command prompt, use the following syntax withregsvr32.exe:

regsvr32.exe ocxfile

Where:

ocxfile is the name of the .ocx file.

10. Run ProjectDTSPowerNetDBCreate.exe to set up the PowerNet historicaldatabases:


a. Select the SQL Server instance from the Available Servers drop-down list.If the SQL Server Instance does not appear in the list, type the path to the in-stance in the box.

b. Select the Create Databases check box to create the englog32, alarm,tsevent, sysevent, trending, and waveform databases. This selectionwill also create two Windows Users Groups, PowerNetUser and PowerNet-PowerUser, that have security access to the PowerNet databases.

c. Select the Transfer Current Database Data check box to import previousPowerNet data from the Access databases into the SQL Server databases.

d. The Database Path edit box should display the path where the PowerNetSQL Server database files and transaction log files will reside and wherethe historical PowerNet databases are located. This path is read from theNGSWINST.INI file.

e. Click the Build Databases button.

Note

If ProjectDTSPowerNetDBCreate.exe fails to create thedatabases when the server name is (local), replace (local) with theSQL Server instance in the Available Servers box.

11. ProjectDTSPowerNetDBCreate.exe created two Windows Users Groups,PowerNetUser and PowerNetPowerUser, on the remote PC. You must assignusers to one or the other of these groups to allow access to the PowerNet SQLServer databases. The following explains the privileges of the two groups:

PowerNetUser For users who only need read access to PowerNet his-torical databases.

PowerNetPowerUser For users who need Read/Write access to the PowerNethistorical databases. E-Bill users should belong to thisgroup.

12. Copy the following files from the PowerNet folder on the PXS DVD into a work-ing folder on the remote PC:

• All batch files (*.bat)

• All SQL script files (*.sql)

• UpdateEbillDatabase.exe

13. From a Windows command prompt, run the UpdateEbillDatabase.exe pro-gram to update the engbill32 database. This program is located in the workingfolder. For example:

UpdateEbillDatabase.exe

14. From a Windows command prompt, run the following PowerNet database updatebatch files to update the historical databases. These batch files and their corre-sponding SQL script files are located in the working folder.

PowerNet_Database_3_32.bat servernameAutoClose.bat servernamePowerNet_Database_3_34.bat servernamePowerNet_Database_3_40.bat servername


Where servername is the name of the SQL Server instance.

15. If the SQL Browser Service is not running, start the SQL Browser Service fromthe Services Control Panel (Start → Administrative Tools → Services). TheStartup Type must be set to Automatic.

16. The SQL Server authentication should be set to Windows Authentication mode.

17. For SQL Server 2005 using the SQL Server Surface Area Configuration tool, setthe Database Remote Connections to Local and remote connections usingTCP/IP only.

For SQL Server 2008 using SQL Management Studio:

a. Right click the Server Instance and select the Facets menu item.


b. Select Server Configuration in the Facet drop down list. Set Remote Ac-cess Enabled to True. Press OK to save and exit.


For SQL Server 2008 using SQL Server Configuration Manager:

a. Select Protocols for MSSQLSERVER under SQL Server Network Configu-ration and set TCP/IP to Enabled.


b. Select Client Protocols under SQL Native Client 10.0 Configuration andset TCP/IP to Enabled.

18. For SQL Server 2005 and SQL Server 2008 run Local Security Policy from theControl Panel under Administrative Tools. Select Security Options under Lo-cal Policies. Set Network access: Sharing and security models for local ac-counts to Classic - local users authenticate as themselves.


19. Reboot the machine.

Setting up the PowerNet Domain Server:

1. Install PowerNet and select Domain Server. During the installation, choose touse a remote SQL Server when prompted. Select the appropriate remote SQLServer instance with the PowerNet databases from the list of available SQL Serv-er instances.

Note

If the appropriate SQL Server instance is not listed, press Back and se-lect to use a Local instance.

2. Once the installation is complete, if a Local instance was selected, change theSQLServerName to the remote SQL Server instance in the DBSVRNAME.INI file(this resides in the PowerNet Database folder). Also, run the ODBC Data SourceAdministrator from Administrative Tools and change the following ODBC DSNsto use the remote SQL Server instance:• E-BILL32• E-LOG32• NGSW_ALARM

Technical Support


• NGSW_SYSEVENT• NGSW_TSEVENT• NGSW_WAVEFORM• TRENDING

3. Run Services from Administrative Tools.

4. Stop the PowerNet Database Server service.

5. Highlight PowerNet Database Server in the Services window and display itsProperties window. (Right-click and select Properties.)

6. Click the Log On tab in the Properties window. Select This account under Logon as and type a user account and password that will enable Database Serveraccess to the remote PC. Click OK to save and exit.

7. Start the PowerNet Database Server service.

Technical�Support

For technical support on this topic or PowerNet in general, contact Eaton PowerQuality Technical Support at 1-800-809-2772 or [email protected].

Administrator's Guide: Power Xpert Software 2.2

Documents

Transcript of Administrator's Guide: Power Xpert Software 2.2