Power Xpert Administrators Guide

MN02601006E
Administrators Guide:
Power Xpert Software 2.2
PowerXpertSoftwareAdministrator'sGuide
PowerXpertSoftwareAdministrator'sGuide
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 AND
SUBJECT 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 INTERESTS
OF EATON, AND THAT NO PORTION OF THIS DOCUMENT MAY BE COPIED OR OTHERWISE REPRODUCED WITHOUT
THE PRIOR WRITTEN CONSENT OF EATON. IN THE CASE OF CONFLICTING CONTRACTUAL PROVISIONS, THIS NOTICE
SHALL 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 Corporations (Eaton)
experience and judgment and may not cover all contingencies. If further information is required, an Eaton sales office should be
consulted. Sale of the product shown in this literature is subject to the terms and conditions outlined in appropriate Eaton selling
policies 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 NOT
BECOME 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 for
any special, indirect, incidental or consequential damage or loss whatsoever, including but not limited to damage or loss of use of
equipment, plant or power system, cost of capital, loss of power, additional expenses in the use of existing power facilities, or claims
against the purchaser or user by its customers resulting from the use of the information, recommendations and descriptions con-
tained herein.
TableofContents
I. PXS Installation and Configuration ................................................................ 1
About This Manual ................................................................................ iii
Hardware and Software Requirements ..................................................... 5
Hardware Requirements ................................................................. 5
Software Requirements .................................................................. 5
Third Party Software Installed with PXS ........................................... 6
Firewall Settings ............................................................................ 7
PowerNet Device Server ........................................................ 7
Remote PowerNet Domain Server ........................................... 8
Shutdown Agent .................................................................... 8
Remote Database Support ..................................................... 8
SQL Server Considerations .................................................... 8
SQL Server Account Considerations ................................................ 8
Browser Settings ........................................................................... 8
Remote Desktop Considerations ..................................................... 9
Network Considerations ................................................................. 9
Microsoft Sharepoint ...................................................................... 9
Installation .......................................................................................... 11
Installation Scenarios ................................................................... 11
PXS Installation ........................................................................... 12
If You Have a Version 2.0 Installation of PXS... ........................ 12
Installing Under Windows Server 2008 or Windows 7 ................ 12
Installing the PXS Application ................................................ 12
Database Deployment .......................................................................... 19
About the Deployment & Validation Utility ....................................... 19
Launching the Deployment & Validation Utility ......................... 20
Initial Deployment & Validation ...................................................... 20
Windows Groups ................................................................. 20
Configure IIS ....................................................................... 21
Firewall Ports ...................................................................... 22
Database ............................................................................ 23
Summary ............................................................................ 25
Microsoft Internet Explorer Settings ........................................................ 27
Accessing the PXS Web Application from a Server .......................... 27
Security .............................................................................................. 29
Where is Security Information Stored? ............................................ 29
Read and Write Users .................................................................. 29
Read Users Group Permissions ............................................. 29
Write Users Group Permissions ............................................. 29
Creating the Users Groups Manually ...................................... 30
Local Security Settings and Web Clients ......................................... 30
Connecting Web Clients ............................................................... 31
Configuring Web Security ............................................................. 31
Configuring Secure Communication to Web Browsers ............... 31
Restricting Power Xpert Software Web Access to SSL /
HTTPS ............................................................................... 32
Modifying the Power Xpert Software Shortcuts ......................... 34
Troubleshooting ................................................................... 35
Power Xpert Reports ............................................................................ 37
Migrating PXS Databases ..................................................................... 41
Preparing for Migration ................................................................. 41
Stopping PXS ............................................................................. 41
PXR Only: Disabling the PXR SQL Server Jobs ............................... 42
Detach the PXS Databases .......................................................... 42
Moving the Database Files ........................................................... 43
Power Xpert Software Administrator's Guide
Attach the Database Files in the New SQL Server Instance ............... 43
Repointing PXS to the New SQL Server Instance ............................ 44
PXR Preparation for Restarting PXS .............................................. 44
Restarting PXS ............................................................................ 44
PXR Only: Enabling the PXR SQL Server Jobs ............................... 45
Backup and Restore ............................................................................ 47
Considerations ............................................................................ 47
Data and Configurations ............................................................... 47
Backup Foreseer ......................................................................... 48
Backup Power Xpert Software ....................................................... 48
Replacement Computer Installation ................................................ 50
Troubleshooting ........................................................................... 51
Restore Power Xpert Software ...................................................... 52
Troubleshooting ................................................................................... 55
Slow Page Loading with IIS 7.5 ..................................................... 55
Animations Don't Work in Internet Explorer ..................................... 57
I Can't Connect to a Remote SQL Server Instance ........................... 57
I Can't Deploy the Database ......................................................... 57
Remote PowerNet Database Server Appears, But No Devices Un-
der the Tree ................................................................................ 57
No Data Appears in Device Pages or User Views ............................ 58
Internet Explorer 7 Goes Into Endless Loop Attempting to Load Ac-
tive-X Controls ............................................................................ 58
If Your Users are Continually Confronted with a Login Dialog ............. 58
Tabs on Properties Dialog Boxes in Layout Manager Disappear. ........ 58
If Your Users Can't Export Alarm Information to Excel ....................... 58
Image Maps Do Not Update ......................................................... 58
Restart PXS ................................................................................ 58
Device Summary Page Won't Open, Returns Error That Foreseer
Server Isn't Running .................................................................... 59
II. Third Party Software Shipped with PXS ...................................................... 61
Installing Microsoft SQL Server Management Studio 2008 ......................... 63
III. PowerNet ............................................................................................... 65
New Device Objects ............................................................................ 67
Series NRX 520M Trip Unit .......................................................... 67
Series NRX 1150 Trip Unit ........................................................... 68
FP-6000 ..................................................................................... 72
PM3 ........................................................................................... 91
Additions to Status and Reason Codes ........................................... 94
Installing PowerNet ............................................................................ 105
PowerNet for Non-Administrative Users ................................................ 107
Adding the PowerNet User to the Required Groups ........................ 107
PowerNet Domain Server Configuration ........................................ 107
PowerNet Client Configuration ..................................................... 108
PowerNet Server with Remote SQL Server ........................................... 111
Technical Support ...................................................................... 119
iv Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com

PartI.PXSInstallationandConfiguration
AboutThisManual
This 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 or

database 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 have
administrative 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 for
Microsoft 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 discusses
how to connect to data sources within PXS, how to configure alarms, and general
system administration.
iv
HardwareandSoftwareRequirements
HardwareRequirements
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- The PXS application itself requires 190 MB of
tion disk storage.
Disk Space Required for A typical database will grow to 2 GB within a

Database year. If you have a large number of devices, re-
serve additional storage space.
Note
PXS will issue an alarm should free disk

space fall to 500 MB or less. Only the
drive on which PXS itself is stored is
monitored, so if your database files re-
side on a separate drive or server you
must make sure to monitor disk space
there.
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).
SoftwareRequirements
Supported Operating Systems:
Note
Eaton recommends that you run PXS on server operating systems and not
desktop 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
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 the
number of simultaneously connected web clients to 10. Once this limit is ex-
ceeded, PXS graphics may not render correctly or the browser may display
the message, There are too many people accessing the Web site
at 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 Standard
SQL Server 2008 Standard SP1
SQL Server 2008 Enterprise
Additional Software Components:
IIS 5.0 or higher. For Windows XP and Server 2003, you must be install this prior to
installing 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 PXS
web interface. Each user that will access PXS must have this browser. Because
PXS uses both Active-X and Silverlight technologies, other browsers (such as Fire-
fox, Safari, Chrome, and Opera) are not supported. Also, Internet Explorer 6 is
not supported. If you access PXS with IE 6 or a non-Microsoft browser (such as
Chrome or Firefox), a warning message will appear stating that some PXS func-
tionality may not be available.
ThirdPartySoftwareInstalledwithPXS
The following Microsoft software is also installed during the PXS installation.
.NET Framework 3.5 SP1
6 Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com

Firewall Settings
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 and
wish 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 Management

Studio is helpful if you wish to migrate the PXS databases from one in-
stance of SQL Server to another. See [ ]
FirewallSettings
The following ports are opened automatically on the server during PXS installation
if you are running the Microsoft firewall. If you are running a third-party fire wall, you
must open these ports manually. Also, as a general rule, ensure that there are no
conflicts 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 and
has 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 no
conflicts for these ports. These ports must not be changed from their de-
faults.
PowerNetDeviceServer
The following configuration supports communicating with a PowerNet Device Server
on 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 must
be opened manually on the PowerNet computer.
5143 - TCP
5146 - UDP
5149 - UDP
5150 - UDP
HTTPAccess
You must set the firewall to allow Web Server HTTP access. Check that this is active
before installing Power Xpert Software.
Power Xpert Software Administrator's Guide - - 7/2011 www.eaton.com 7

Remote PowerNet Domain Server
RemotePowerNetDomainServer
This port must be opened manually on both the Power Xpert Software server and the
PowerNet Domain Server:
139 - TCP
ShutdownAgent
The Eaton Shutdown Agent requires the following ports to be opened in the firewall:
UDP ports 7013 and 7014.
7013 - UDP
7014 - UDP
RemoteDatabaseSupport
1433 - TCP (this is the default port for SQL Server, but it is configurable). This port
must be open on both the PXS server and the remote database server.
SQLServerConsiderations
PXS automatically installs a copy of Microsoft SQL Server Express 2008 SP2 if no
other 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 initially
set (you must migrate the databases to do this, which is covered in [ ]).
As mentioned in the installation scenarios chapter (see the section called Installation
Scenarios [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, then
you 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 is
running and that the SQL Server is set to allow remote connections .
SQLServerAccountConsiderations
The 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 the
SQL Server sysadmin role assigned.
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 the Log On
tab to view the account used to log onto SQL Server.
BrowserSettings
The following applies if you are connecting to PXS from a remote machine: if you
have 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 must
add the PXS server to the Trusted Sites zone. If you don't, some of the Active-X
control objects that may be part of user views pages will not load properly. In fact, the
browser may go into an endless loop attempting to load the Active-X controls. Adding
the 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 detect
intranet network is not selected. If IT policies prevent access to that setting, consult
with your IT group.
RemoteDesktopConsiderations
If you are using terminal services to connect to a PXS Server, you must be connect-
ed via the console session. If you dont connect through the console session, some
administrative tools, such as the Message Manager control panel applet, wont 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 the
following 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 for
Power 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 the
problem.
NetworkConsiderations
PXS requires authentication through membership in Windows user groups (covered
in 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 the
same domain.
MicrosoftSharepoint
PXS cannot be installed on a computer that is hosting Windows Sharepoint Services
on the default HTTP or HTTPS ports.

10
Installation
InstallationScenarios
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 for
smaller 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 database
skills, 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 2005
and 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 amount
of 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 find
the installation files in the Power Xpert Software\SqlExpress2008
folder 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 recommended
for 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, the
Standard edition can use up to four CPUs and the Enterprise edition can have unlim-
ited scaling and partitioning, providing much higher performance than the Express
edition.
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 Server
as well as administrative privileges for the server machine itself. While this scenario
doesn't require specific IT or database skills, these are extremely helpful (especially
in troubleshooting any security, firewall, or database problems that might be specific
to 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 Enterprise
edition 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, with
SQL Server resident on another server (or server farm). This is the most scal-
able approach, and can handle larger networks. Performance is enhanced by having
SQL Server and PXS on separate machines (either real or virtual) within the same
workgroup or domain. The database capabilities can be further scaled-up though
higher 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 Microsoft
SQL Server.
PXSInstallation
Before 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 is
missing, but this occurs later during installation. Having met the software require-
ments before starting installation ensures that you won't need to stop, install the
prerequisites, 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 the
administrator 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 called
the section called Firewall Settings [7].
Note
Depending on what Windows components are installed, during the process
you may be asked to reboot your system and restart the installation.
IfYouHaveaVersion2.0InstallationofPXS...
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 at
1-800-809-2772 or by email pqsupport@eaton.com for assistance.
InstallingUnderWindowsServer2008orWindows7
When installing on Windows Server 2008, Eaton recommends that you do this as
the 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 was
changed 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 Eaton
installation application or the setup.exe file to install PXS.
Caution
Do not install from the .msi file. This may appear to work but PXS will not func-
tion properly.
InstallingthePXSApplication
To install the application:
1. Insert the distribution DVD in the DVD R/O or R/W drive. If the drive has autorun
enabled, 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, click
Run.
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 Setup
dialog 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 are
already 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 the
machine 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 asking
permissions 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 the
terms of the license.
8. Enter the six segments of the product key, each segment in its own fields. When
the 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't
select one at this time, you can return here and install the optional components
later. 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 the
PXS 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 Start
menu and a shortcut on your desktop.

18
DatabaseDeployment
You 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] and
ensure that all prerequisites are met.
Aside from deploying the databases, the Deployment & Validation Utility also does a
number of system checks and simplifies system configuration. Through the utility you
can:
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 databases
to that SQL Server instance.
Start the required PXS services.
AbouttheDeployment&ValidationUtility
The 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 the
utility. 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 all
of 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 its
own tasks (you start and stop the various PXS services from Summary). If any of the
other indicators shows a Not Configured or Warning state, then the Summary indi-
cator will reflect this as well.
LaunchingtheDeployment&ValidationUtility
For initial Deployment & Validation, you can launch the utility directly from the last
installation dialog box. Otherwise, launch it from the Eaton Power Xpert Software
group 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 have
SQL Server sysadmin privilege.
InitialDeployment&Validation
During initial deployment, your goal is to get all indicators showing green and then
to start the services in the Summary tab. The following explains the tasks related to
each of the icons.
Important
Even if all of the status indicators are green, check the Summary tab. You must
start each of the four services before PXS is operational.
WindowsGroups
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 Eaton
Power Xpert Write Users, must be created for this purpose. Power Xpert Software
uses these groups to determine who can read and/or write data to the database. By
default, both the read and write groups are empty. For more information about these
groups, 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 to
create the groups.

Configure IIS
Figure 14. Windows Groups Task Panel
ConfigureIIS
This task verifies that you have the necessary version of IIS and that ASP.NET 2.0 is
registered with IIS and also checks for the IIS virtual directories. If the indicator icon
isn't green, click the Register ASP.NET 2.0 and IIS button.

Firewall Ports
Figure 15. Configure IIS Task Panel
FirewallPorts
This task checks if the Windows Firewall is active (listed under Status) and will open
the required ports on the Windows Firewall (click the Open Ports button). If you must
open these ports manually, refer to the section called Firewall Settings [7].
Note
The Deployment & Validation Utility uses the Windows Firewall/Internet

Connection Sharing (ICS) service to check the status of the ports. Make
sure 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 in

the section called SQL Server Account Considerations [8].
Within this panel, you can establish the instance of SQL Server that will house the
databases, set the location of the database files PXS, test the connection, and deploy
the 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 as
your_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 the
set of SQL Server instances the utility can detect and select the instance from
that list. If SQL Browser is running on a remote instance of SQL server then the
connection string should not need to specify a port number. However, if SQL
browser is not running you may need to specify the port number as part of the
connection string.

Database
Note
SQL Server Express will identify itself as (local)\SQLEXPRESS. If you
wish 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 SQL
Server instance is on the local machine, you can browse to this folder. If it's on
a 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 you
can change it here.
Note
If the user that created the instance is not the same users that's running
the Deployment utility, you may encounter errors attempting to create
the 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 will
log the various deployment steps as they are completed. This list also uses the
indicator icons, and as each step completes it should have a green icon.
Important
Once deployed, you cannot use the Deployment & Validation Utility to
change the instance that houses the PXS databases. Contact customer
support if you must migrate the PXS databases to another instance of SQL
Server.
Figure 18. Example Task Details Output

AdvancedDeployment
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 dialog
box.

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 start
each of the four services that comprise PXS with their associated Start buttons. Start
any stopped services as required using the appropriate Start button. The goal is to
have 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.

MicrosoftInternetExplorerSettings
PXS uses ActiveX controls in its web interface, and these must be installed in each of
your user's browsers. Installation of the controls is automatic when a user accesses a
PXS web page that contains one or more of the controls. However, the controls won't
install unless certain IE settings areTools made. In both versions of IE, these settings
are found in Internet Options under . To access the settings, click the Security tab
and 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 ActiveX Disable This does not affect PXS, but this
controls to run without prompt setting provides for enhanced secu-
rity.
Allow Scriptlets Prompt This does not affect PXS, but this
setting provides for enhanced secu-
rity.
Automatic prompting for ActiveX Enable
controls
Binary and script behaviors Enable
Download signed ActiveX controls Prompt
Download unsigned ActiveX controls Disabled This does not affect PXS, but this
setting provides for enhanced secu-
rity.
Initialize and script ActiveX controls Disable This does not affect PXS, but this
not marked as safe for scripting setting provides for enhanced secu-
rity.
Run ActiveX controls and plug-ins Enable
Script ActiveX controls marked safe Enable This setting does not take effect until
for scripting you restart IE.
AccessingthePXSWebApplicationfromaServer
Important
Even if you are using an account that's a member of the local Administrator's
group, domain administrators, or the built-in administrator, you must add that
account to either the Eaton Power Xpert Read Users and Eaton Power Xpert
Write Users groups. This is discussed in the section called Read and Write
Users [29].
On server operating systems, the Enhanced Security Configuration in IE can prevent

you 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 Internet
Options under Tools. To access the settings, click the Security tab and then click
the Trusted Sites zone.
If you continue to have difficulty under Windows Server 2008, you can set Internet
Enhanced 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 and
Users.
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 occur
when attempting to access the PXS Web Application (and they are properly assigned
to either the Eaton Power Xpert Read Users or Eaton Power Xpert Write Users
group), 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, click
the Security tab and then click the Local intranet zone.

Security
WhereisSecurityInformationStored?
Sensitive information, such as passwords and device addresses, are stored in the
Power Xpert Software SQL database. The connection string to the database is stored
in the registry and read/write access to that registry location is restricted in a similar
fashion to the Power Xpert Software database.
ReadandWriteUsers
The Eaton Power Xpert Read Users and Eaton Power Xpert Write Users groups
were created during initial deployment (see Figure 14, Windows Groups Task Pan-
el [21]). Each of these groups provide unique privileges on the Power Xpert Software
web page. Users in the Read group have a read-only view the system and cannot
change or edit any configurations, settings, or notifications. Users in the Write group
have all of the viewing privileges of the Read user, but can modify any and all parts of
the system. You should only assign administrators and User Views page designers to
this group.
Important
On the PXS Server machine itself, you must assign even users that are domain
administrators, local administrators, or the built-in administrative account to
one of these groups if those users will access PXS.
ReadUsersGroupPermissions
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.
WriteUsersGroupPermissions
Eaton Power Xpert Write Users have full read and write access to all parts of the
system including the User Views, Database Management, Alarm Notification, and
Layout Manager web pages. A Write user can also access the Configuration Man-
ager.
Creating the Users Groups Manually
CreatingtheUsersGroupsManually
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 users
groups 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. In
some 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 Users
group.
8. When you've finished adding groups and users, click the Close button and exit
from the Computer Management utility.
LocalSecuritySettingsandWebClients
The 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 guest
account has very limited access privilege, access to Power Xpert Software Web UI
may 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 to
Classical mode will solve the problem. Under the Classical mode, network logons
are 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.
ConnectingWebClients
Web Clients can connect to Power Xpert Software using Internet Explorer. Review
the software requirements in Hardware and Software Requirements for information
concerning specific versions of Internet Explorer that are supported.
Web Clients can access the Power Xpert Software web interface via the following
URL:
http://server_ip_address/PowerXpertSoftware
Where server_ip_address is the IP address of the machine hosting the Power
Xpert Software web server. The following section discusses setting up HTTPS ac-
cess.
ConfiguringWebSecurity
In addition to the default security precautions Power Xpert Software takes to protect
your system, you will need to examine your own security needs and further fortify
your system if desired. Power Xpert Software provides access via remote client Web
browsers. 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.
ConfiguringSecureCommunicationtoWebBrowsers
Users wishing to enable HTTPS communications in their Power Xpert Software sys-
tems should either purchase a certificate from a third-party SSL certificate provider
and/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 Xpert
Software 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 to
SSL / HTTPS
3. Expand the (local computer), then Web Sites, and then the Default Web Site
folders.
4. Right click PowerXpertSoftware and then click Properties.
5. The PowerXpertSoftware Properties window will appear. Click the Directory

Security 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 prefix
https:// should be enabled.
Note
When using an SSL certificate, the web address used to connect to Power
Xpert Software must be the same as what is specified on the certificate. For
example, 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 Xpert
Software. Be sure to make that correction when entering the address in the
browser or warnings may occur.
RestrictingPowerXpertSoftwareWebAccesstoSSL/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 to
SSL / HTTPS
To restrict communications to only SSL/HTTPS:
1. Launch the Internet Information Services (IIS) Manager, right click the Default
Web 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.
ModifyingthePowerXpertSoftwareShortcuts
The Power Xpert Software installation created shortcuts under Start->All Programs -
>Power Xpert Software. By default, the shortcuts for the Power Xpert Software Web
Application and Log Viewer point to an http:// address.
To correct the shortcuts:
1. Navigate to the following folder: C:\Program Files\Eaton Power Xpert

Software\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 is
localhost, 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 if
portions 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, found
on the Tools menu under Internet Options.
If warnings or issues still exist that didnt prior to enabling SSL communications, seek
help from your SSL Certificate Provider as a problem most likely exists with the way
the certificate was imported and applied.

36
PowerXpertReports
You 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 the
server machine running the instance of SQL Server Reporting Services used by
PXR.
PXR is currently installed and properly configured to pull data from the PXS
database.
Refer to the Power Xpert Reporting Deployment Utility Guide and the Power
Xpert Reporting Administration Utility Guide for information concerning how to
configure Power Xpert Reporting to pull data from PXS and for adding users to the
Eaton 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 PXR
reports 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 next

step.
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 Xpert
Read 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 Reporting
Services used by PXR.
2. Create one or more user groups, depending on whether all users will simply
have browse privilege or some will have elevated privileges. Add the domain
users 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 next

step.
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 that
you 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 an
alert box stating Test succeeded. If you are executing this test remotely, both
servers 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 using
reports. If the test fails, refer to the PXR documentation and ensure that PXR is prop-
erly configured to pull data from PXS.

40
MigratingPXSDatabases
You can migrate the PXS databases from one instance of SQL Server to another. If
your 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 by
PXS. 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 need
Management Studio. You can instead read through the following sections to
become familiar with the general steps involved and carry them out using SQL
Server commands.
The following procedure is based on SQL Server Management Studio 2008, and if
you are using a different version of Management Studio you may find slight varia-
tions.
PreparingforMigration
You must have administrative privileges for the server that houses PXS and for both
instances of SQL Server. If you have PXR, you'll need administrative privileges for
the 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 the
new server. If both instances of SQL Server reside on the same machine, this
step 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).
StoppingPXS
While you can stop PXS through the Windows Control Panel, the simplest way is to
do 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 Utility
from 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
PXROnly:DisablingthePXRSQLServerJobs
If you have PXR, you should disable its database tasks next. Disabling these means
that when you re-enable them, you'll pick up all of the data cached by devices as this
becomes available through PXS. Th
To disable the PXR jobs:
1. Launch SQL Server Management Studio through Start Microsoft SQL Server
yyyy.
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 the
shortcut menu.
Figure 25. The three PXR jobs.
Note
You can leave Management Studio open as you'll be completing more tasks.
DetachthePXSDatabases
Before 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 Microsoft
SQL Server yyyy.
2. In the Object Browser, expand the Databases folder. PXS related database are
Pxs, 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.
MovingtheDatabaseFiles
After the databases are detached, if the other instance of SQL Server isn't on the
same machine, you must move the database files. There are two files associated with
each database: DatabaseName.mdf, DatabaseName.ldf.
You can check the location of the files by right-clicking one of the databases in SQL
Server Management Studio and selecting Properties. Click Files in the left pane and
then 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 delete
the source files until you're sure that the everything is functioning properly in the new
instance.
AttachtheDatabaseFilesintheNewSQLServerInstance
Each 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 to
attach). 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 all
of the PXS databases are now present.

Repointing PXS to the New SQL Server Instance
RepointingPXStotheNewSQLServerInstance
Next, 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 regedit
and then click OK.
2. For Windows XP, Windows Server 2003, and Windows 7, browse to the
HKEY_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.
PXRPreparationforRestartingPXS
If you are using Windows authentication via a non-administrative account, you must
first create a local Windows users group called Eaton Power Xpert Reporting Users
on the machine housing the new SQL Server instance. This is a local users group
created 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'll
use to access PXS to that group.
Important
You will also need to add each Windows account that will access PXR reports
or the PXR Administration Utility to the Eaton Power Xpert Reporting Users
group.
Refer to the PXR
RestartingPXS
To stop PXS:
1. On the PXS Server Machine, launch the PXS Deployment Validation Utility from
Start All Programs Eaton Power Xpert Software Deployment Validation
Utility.
2. Click Summary.
3. Click the Start button for each of the PXS services. After completing this step,

PXR Only: Enabling the PXR SQL Server Jobs
Figure 27. All PXS Services Started
PXROnly:EnablingthePXRSQLServerJobs
If you have PXR, the final task is enabling the PXR jobs. This should pick up all of the
data cached by devices as this becomes available through PXS.
To enable the PXR jobs:
1. Launch SQL Server Management Studio through Start Microsoft SQL Server
yyyy.
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 the
shortcut 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 Power
Xpert Reporting Administration Utility Guide for information concerning how con-
nect PXR to the new location of the PXS databases.

46
BackupandRestore
Backing 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 customers
should 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 works
again with minimal disruption.
You take regular images of the PC with a third-party back up software. The computer
fails and you must restore to a different one.
If a replacement computer can be re-imaged directly from a backup, the solution is

simply 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 from
one computer on another with a slightly different hardware profile. Please
keep these features in mind when you choose imaging software.
You wish to move your PXS configuration and data from one computer to another, for
example, 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 a
Foreseer system that is version 4.2.x or higher. If you would like to move data from
an older Foreseer system, such as versions before 4.2.x, to versions 4.2.x and
greater, 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 repeated
on the replacement PC.
DataandConfigurations
The default installation of Power Xpert Software includes Foreseer. Therefore, users
should consider the historical data and configuration information for both of these ap-
plications during the backup and restore process. Here is whats under the hood of
each 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 and
configuration files.
BackupForeseer
When you backup your configuration, an .arq file is generated at the location you
specify.
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, it
will be created in the Restore folder in Foreseer. Click Save.
BackupPowerXpertSoftware
To backup Power Xpert Software, you will need to save the .xml files that hold your
preferences and configurations, and you will need to save the Power Xpert Software
databases.
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 Xpert
Software.
2. The UserViewNodeCollection.xml file and the

DatabaseHistoricalManagement.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 file
will 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 ->Microsoft
SQL 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 during
the 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....
Pxs
PXS_year_month
Trend_year_month
5. The Back Up Database window will appear. By default, the database backup will
be stored in Microsoft SQL Servers Backup folder. If you would like to change
this, remove the current location and click the Add button to select a different
destination. The file must be saved locally and then it can be moved to remote
storage.
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.
ReplacementComputerInstallation
On the replacement computer, copy the backup folder containing all of your data from
the old computer. Begin by installing the prerequisites and then Power Xpert Soft-
ware. At the conclusion of installation, stop the Eaton Foreseer Server Service. For
example, you can go to Start > Administrative Tools > Services and stop the ser-
vice.
After stopping the service, delete the contents of the \Program Files\Eaton
Power 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 box
should appear.
Important
When this appears, do not click either the Next or Cancel button. Leave this
window 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)\Eaton
Power Xpert Software\Foreseer Server\Restore, depending on your
operating system.
2. Copy the backup .arq file into the folder.
3. On the Server Initial Configuration window, choose the Restore a Backup

Configuration 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 restore
your 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\Eaton

Power Xpert Software\Foreseer Server\Data\.
3. Start the Eaton Foreseer Server Service.
The Server Initial Configuration window will now appear and you can try restoring
again.
RestorePowerXpertSoftware
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 name
and clicking the Stop link on the left hand side or by clicking the Stop Service
button 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 your
operating 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 remote
location.
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 of
the following databases must be restored:
Pxs
PXS_year_month
Trend_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 and
click 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 name
of 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 Xpert
Software.

54
Troubleshooting
You can contact Eaton technical support at 1-800-809-2772 or send email to
pqsupport@eaton.com. A technical support representative may ask you to use the
PXS Log Viewer to retrieve PXS logs and send them back to Eaton. You can access
the Log Viewer via Start Eaton Power Xpert Software PXS Log Viewer.
SlowPageLoadingwithIIS7.5
When the PXS web application is loaded for the first time it may take up to several
minutes for the page to display. This may also occur if the PXS web application has
not 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 two
versions 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 under

Default 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

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 to
the 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 and
Windows for Type.
b. For User name, type an account that is a member of Eaton Power Xpert
Read 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
AnimationsDon'tWorkinInternetExplorer
Internet 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 to
restart Internet Explorer for this setting to take effect.
4. Click OK.
ICan'tConnecttoaRemoteSQLServerInstance
This is usually due to authentication problems between the account you're using
on the PXS server machine and the SQL Server machine. Here are a few things to
check:
PXS uses Windows authentication to connect to the SQL Server machine. Make
sure 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.
ICan'tDeploytheDatabase
Problems in database deployment are logged in the Task Details pane on the
Database Task Panel (in the Deployment & Validation Utility).
RemotePowerNetDatabaseServerAppears,ButNoDevicesUndertheTree
Ensure 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 the
Log On tab to view the account used to log onto PowerNet.

No Data Appears in Device Pages or User Views
NoDataAppearsinDevicePagesorUserViews
If you notice this problem while running on the PXS server machine, check the IIS
manager 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 LAN
Settings Advanced.
Also, make certain that port 8081 is open on the PXS server machine.
InternetExplorer7GoesIntoEndlessLoopAttemptingtoLoadActive-XControls
Go to the Internet Explorer security settings (Tools > Internet Options > Security
tab), and click the Trusted Sites zone. Click the Sites button and add the machine
name (preferable) or IP address of the PXS server to list of trusted sites. If IT policies
prevent you from adding machines to the trusted sites list, click the Local Intranet
zone and then the Sites button. Make certain that Automatically detect intranet
network is not selected. If IT policies prevent access to that setting, consult with your
IT group.
IfYourUsersareContinuallyConfrontedwithaLoginDialog
This 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 Proxy
Settings. This is under Tools Internet Options Connections LAN Settings
Advanced.
TabsonPropertiesDialogBoxesinLayoutManagerDisappear.
Add about:blank to the set of Internet Explorer trusted sites.
IfYourUsersCan'tExportAlarmInformationtoExcel
If your users can't export alarm information to Microsoft Excel, grant them access as
follows:
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 PXS
server machine.
For users on the PXS server machine, user accounts accessing PXS must have
read/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.
ImageMapsDoNotUpdate
If 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.
RestartPXS
To stop PXS:
1. On the PXS Server Machine, launch the PXS Deployment Validation Utility from
Start All Programs Eaton Power Xpert Software Deployment Validation
Utility.

Device Summary Page Won't Open, Returns Error
That Foreseer Server Isn't Running
2. Click Summary.
3. Click the Start button for each of the PXS services. After completing this step,
Figure 32. All PXS Services Started
DeviceSummaryPageWon'tOpen,ReturnsErrorThatForeseerServerIsn'tRunning
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 that
the device name has exceeded 40 characters. You will need to rename the device
at the publisher (PowerNet, the PXG, etc.) as well as delete and then recreate the
matching folder on the PXS server. Contact Eaton Power Quality Technical Support
at 1-800-809-2772 or pqsupport@eaton.com for assistance with this task.

60
PartII.ThirdPartySoftwareShippedwithPXS
InstallingMicrosoftSQLServerManagement
Studio2008
Both the 32 and 64-bit versions of SQL Server Express 2008 Management Studio are
shipped on the PXS DVD, and reside in the \Third Party\SQL Server 2008
Express 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 2003
and 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 the

SQLManagementStudio_x86_ENU.exe 32-bit installer or the
SQLManagementStudio_x64_ENU.exe 64-bit installer. This is actually the SQL
Server 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 SQL
Server or add features to an existing instance, you must choose to perform a new
installation. You cannot add the Management Studio as a feature. Selecting this
route 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

PartIII.PowerNet
NewDeviceObjects
The following are new device objects not contained in the PowerNet Documentation.
SeriesNRX520MTripUnit
Table 2. Series NRX 520M Device Objects
Description Number DDE Tag Name DDE Type Range Units Invalid Number Scale
Of Regis- Factor
ters
Status 1 STATN R# 0, 1, 2, 3, 4, 47 (See the Status Codes FFFF 1
table in Appendix A of the PowerNet
User's Guide and Table 11, Status
Codes [94].)
Status NA STATT M NA NA NA
(String)
Status Sec- 1 STAT2N R# 0, 4, 45, 46, 48 (See the Status Codes FFFF 1
ondary table in Appendix A of the PowerNet
User's Guide and Table 11, Status
Codes [94].)
Reason 1 RSONN R# 0, 1 ,2, 3, 4, 5, 6, 11, 14, 47, 121, 162, FFFF 1
167, 230, 231, 240, 262, 263, 264,
265, 297, 298, 330, 331, 423, 427, 430,
459, 491, 492 (See the Reason Codes
table in Appendix A of the PowerNet
User's Guide and Table 12, Reason
Codes [96].)
Reason NA RSONT M NA NA NA
(String)
DDE Device NA ALARM I 0-30, 200-249 (See the Alarm Codes NA NA
Alarm table in Appendix A of the PowerNet
User's Guide.)
Comm Ver- NA COM_VERSION I 0 to 15 NA NA
sion
Product ID NA PRODUCT_ID I 44 NA NA
Division NA DIV_CODE I 32 NA NA
Code
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
SeriesNRX1150TripUnit
Table 4. NRX 1150 Device Data
Description Number DDE Tag Name DDE Type Range Units Invalid Scale
Of Mod- Number Factor
bus Reg-
isters
Status 1 STATN R# 0, 1, 2, 3, 47 (See FFFF 1
the Status Codes
table in Appendix
A of the PowerNet
User's Guide and
Table 11, Status
Codes [94].)
Status (String) N/A STATT M N/A N/A N/A
Status Secondary 1 STAT2N R# 0, 4, 45, 46, 48 FFFF 1
(See the Status
Codes table in
Appendix A of the
PowerNet User's
Guide and Ta-
ble 11, Status
Codes [94].)
Reason 1 RSONN R# 0, 1, 2, 3, 4, 5, FFFF 1
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, 413
418. 419, 423,
427, 429, 451,
452, 454, 457,
458, 459, 460,
478, 486, 488
(See the Reason
Codes table in
Appendix A of the
PowerNet User's
Guide and Ta-
ble 12, Reason
Codes [96].)
Reason (String) N/A RSONT M N/A N/A N/A
DDE Device Alarm N/A ALARM I 0-30, 200-249 N/A N/A
(See the Alarm
Codes table in
Appendix A of the
PowerNet User's
Guide.)
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
a
Event Count 1 EVENTCOUNT R# 0 to 65535 FFFF 1
Frequency 1 FREQ R#.# 45 to 65 Hz FFFF 10
Phase A Current 1 IA R# 0 to 65535 A FFFF 1
(RMS)

bus Reg-
isters
Phase B Current 1 IB R# 0 to 65535 A FFFF 1
(RMS)
Phase C Current 1 IC R# 0 to 65535 A FFFF 1
(RMS)
Ground Current 1 IG R# 0 to 65535 A FFFF 1
(RMS)
Neutral Current 1 IN R# 0 to 65535 A FFFF 1
(RMS)
Phase A Demand 1 IADEMAND R# 0 to 65535 A FFFF 1
Current
Phase A Peak De- 1 IAPEAK R# 0 to 65535 A FFFF 1
mand Current
Phase B Demand 1 IBDEMAND R# 0 to 65535 A FFFF 1
Current
Phase B Peak De- 1 IBPEAK R# 0 to 65535 A FFFF 1
mand Current
Phase C Demand 1 ICDEMAND R# 0 to 65535 A FFFF 1
Current
Phase C Peak De- 1 ICPEAK R# 0 to 65535 A FFFF 1
mand Current
Number of Instanta- 1 INST_SDT_FAULTS I 0 to 65535 FFFF 1
neous/Short Delay
Faults
Number of Long 1 LDT_GFT_FAULTS I 0 to 65535 FFFF 1
Delay/Ground
Faults
Maximum Phase A 1 MAX_IA R# 0 to 65535 A FFFF 1
Current (RMS)
Maximum Phase B 1 MAX_IB R# 0 to 65535 A FFFF 1
Current (RMS)
Maximum Phase C 1 MAX_IC R# 0 to 65535 A FFFF 1
Current (RMS)
Maximum Ground 1 MAX_IG R# 0 to 65535 A FFFF 1
Current (RMS)
Maximum Neutral 1 MAX_IN R# 0 to 65535 A FFFF 1
Current (RMS)
Maximum Apparent 1 MAX_SYSTEM_PF_APP R#.## +/- 1.00 7FFF 100
Power Factor
Maximum Trip Unit 1 MAX_TEMP R# -273 to 330 C FFFF 1
Temperature
Minimum Phase A 1 MIN_IA R# 0 to 65535 A FFFF 1
Current (RMS)
Minimum Phase B 1 MIN_IB R# 0 to 65535 A FFFF 1
Current (RMS)
Minimum Phase C 1 MIN_IC R# 0 to 65535 A FFFF 1
Current (RMS)
Minimum Ground 1 MIN_IG R# 0 to 65535 A FFFF 1
Current (RMS)
Minimum Neutral 1 MIN_IN R# 0 to 65535 A FFFF 1
Current (RMS)
Minimum Apparent 1 MIN_SYSTEM_PF_APP R#.## +/- 1.00 7FFF 100
Power Factor
Per Phase Current 1 PER_PHASE_I_DEMAND_WINDOW R# 0 to 65535 min FFFF 1
Demand Window
Power Factor (Ap- 1 PFAPP R#.## +/- 1.00 7FFF 100
parent)
Forward Real Ener- 2 POSENERGY R# +/- 999999999000 Wh FFFFFFFF 1
gy (Watthours)

bus Reg-
isters
Power Demand 1 POWER_DEMAND_WINDOW R# 0 to 65535 min FFFF 1
Window
Raw Status 2 RAW_STATUS I N/A FFFFFFFF 1
Reverse Real Ener- 2 NEGENERGY R# 0 to Wh FFFFFFFF 1
gy (Watthours) 999999999000
System Real Power 2 SYS_DEMAND_WATTS R# 0 to 2147483646 W 7FFFFFFF 1
Demand (Watts)
System Negative 2 SYS_NEG_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1
Peak Demand
Watts (calculated)
System Positive 2 SYS_POS_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1
Peak Demand
Watts (calculated)
Time of System N/A SYS_NEG_PEAK_DEMAND_WATTS_TIME TIME N/A N/A N/A
Negative Peak De-
mand Watts
Time of System N/A SYS_POS_PEAK_DEMAND_WATTS_TIME TIME N/A N/A N/A
Positive Peak De-
mand Watts
Time of Last Rest N/A SYS_TIME_LAST_RESET_DEMAND_WATTS TIME N/A N/A N/A
of System Demand
Watts (calculated)
Time of Last Reset N/A TIME_1_PHASE_DEMAND_I_RESET TIME N/A N/A N/A
of Phase Demand
Currents
Time of Last Reset N/A TIME_LAST_MM_PF_APP_RESET TIME N/A N/A N/A
of Min/Max Power
Factor
Time of Maximum N/A TIME_MAX_SYSTEM_PF_APP TIME N/A N/A N/A
Power Factor
Time of Minimum N/A TIME_MIN_SYSTEM_PF_APP TIME N/A N/A N/A
Power Factor
Time of Last Event N/A TIME_OF_LAST_OPERATION TIME N/A N/A N/A
(Breaker Open)
Time of Last Reset N/A TIME_OF_LAST_POWER_RESET TIME N/A N/A N/A
of Power Demand
Time of Phase A N/A TIME_OF_PEAK_IA TIME N/A N/A N/A
Peak Demand Cur-
rent
Time of Phase B N/A TIME_OF_PEAK_IB TIME N/A N/A N/A
Peak Demand Cur-
rent
Time of Phase C N/A TIME_OF_PEAK_IC TIME N/A N/A N/A
Peak Demand Cur-
rent
Time of Peak Ap- N/A TIME_OF_PEAK_VA TIME N/A N/A N/A
parent Power De-
mand
Time of Peak Reac- N/A TIME_OF_PEAK_VARS TIME N/A N/A N/A
tive Power Demand
Time of Peak Real N/A TIME_OF_PEAK_WATTS TIME N/A N/A N/A
Power Demand
Percent THD 1 THDIA R# 0 to 65535 % FFFF 1
Phase A Current
Percent THD 1 THDIB R# 0 to 65535 % FFFF 1
Phase B Current
Percent THD 1 THDIC R# 0 to 65535 % FFFF 1
Phase C Current
Percent THD Neu- 1 THDIN R# 0 to 65535 % FFFF 1
tral Current

bus Reg-
isters
Apparent Power 2 VA R# 0 to 2147450880 VA 7FFFFFFF 1
(VA)
Voltage A-B 2 VAB R# 0 to 2147450880 V FFFFFFFF 1
Apparent Power 2 VADEMAND R# 0 to 2147450880 VA 7FFFFFFF 1
Demand (VA)
Apparent Energy 2 VAHRS R# 0 to VAh FFFFFFFF 1
(VAhours) 999999999000
Peak Apparent 2 VAPEAK R# 0 to 2147450880 VA 7FFFFFFF 1
Power Demand
(VA)
Voltage A-N 2 VAN R# 0 to 2147450880 V FFFFFFFF 1
Reactive Power 2 VARS R# +/- 1073709057 var 7FFFFFFF 1
(vars)
Reactive Power 2 VARSDEMAND R# +/- 1073709057 var 7FFFFFFF 1
Demand (vars)
Peak Reactive 2 VARSPEAK R# +/- 1073709057 var 7FFFFFFF 1
Power Demand
(vars)
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- 2 WATTSDEMAND R# +/- 1073709057 W 7FFFFFFF 1
mand (Watts)
Peak Real Power 2 WATTSPEAK R# +/- 1073709057 W 7FFFFFFF 1
Demand (Watts)
a
The 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- # Of DDE Tag Name DDE Range Units Invalid Number Scale Factor
tion Reg- Type
isters
Status 1 STATN R# 0, 1, 2, 3, 4, 5, 6, 7, 9, 10, 21, 22, FFFF 1
47 (See the Status Codes table
in Appendix A of the PowerNet
User's Guide and Table 11, Sta-
tus Codes [94].)
Status NA STATT M NA NA NA
(String)
Status Sec- 1 STAT2N R# 0, 1, 2, 3, 4, 5, 6 (See the Status FFFF 1
ondary Codes table in Appendix A of the
PowerNet User's Guide and Ta-
ble 11, Status Codes [94].)
Reason 1 RSONN R# 0 - 6, 20, 21, 26, 27, 34, 39, 43, FFFF 1
72, 73, 82, 85, 103, 117, 119,
168, 171, 223, 235, 239, 273,
296, 326, 332, 400 - 432, 472,
473, 482 (See the Reason Codes
table in Appendix A of the Power-
Net User's Guide and Table 12,
Reason Codes [96].)
Reason NA RSONT M NA NA NA
(String)
DDE Device NA ALARM I 0-30, 200-249 (See the Alarm NA NA
Alarm Codes table in Appendix A of the
PowerNet User's Guide.)
Comm Ver- NA COM_VERSION I 0 to 15 NA NA
sion
Division NA DIV_CODE I 4 NA NA
Code
Device NA TYPEN I 99 NA NA
Type
27-A1 Aux 1 AUX_27_A1_UV_OP R# 0,1 FFFF 1
Vx Under
Volt Flag
27-A2 Aux 1 AUX_27_A2_UV_OP I 0,1 FFFF 1
Vx Under
Volt Flag
27-M1 Main 1 MAIN_27_M1_UV_OP I 0,1 FFFF 1
Vp Under
Volt Flag
27-M2 Main 1 MAIN_27_M2_UV_OP I 0,1 FFFF 1
Vp Under
Volt Flag
32-1 Power 1 POWER_32_1_OPERATION_ I 0,1 FFFF 1
Operation FLAG
Flag
Operation FLAG
Flag
Operation FLAG
Flag
46-1 Cur- 1 MISC_46_1_CU_OP I 0,1 FFFF 1
rent Unbal
Op Flag
46-2 Cur- 1 MISC_46_2_CU_OP I 0,1 FFFF 1
rent Unbal
Op Flag

FP-6000
tion Reg- Type
isters
47-1 Volt- 1 MISC_47_1_VU_OP I 0,1 FFFF 1
age Unbal-
ance Op
Flag
47-2 Volt- 1 MISC_47_2_VU_OP I 0,1 FFFF 1
age Unbal-
ance Op
Flag
49- RTD #1 1 IEEE_49_RTD_1_ALARM_1_ I 0,1 FFFF 1
Alarm 1 FLAG
Alarm 2 FLAG
49- RTD #1 1 IEEE_49_RTD_1_OPERATE_ I 0,1 FFFF 1
Operate FLAG
49- RTD 1 IEEE_49_RTD_10_ALARM_1_ I 0,1 FFFF 1
#10 Alarm 1 FLAG
#10 Alarm 2 FLAG
49- RTD 1 IEEE_49_RTD_10_OPERATE_ I 0,1 FFFF 1
#10 Oper- FLAG
ate
#11 Alarm 1 FLAG
#11 Alarm 2 FLAG
49- RTD 1 IEEE_49_RTD_11_OPERATE_ I 0,1 FFFF 1
#11 Oper- FLAG
ate
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG

FP-6000
tion Reg- Type
isters
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
Alarm 1 FLAG
Alarm 2 FLAG
Operate FLAG
49- RTD 1 IEEE_49_RTD_GROUP_1_ I 0,1 FFFF 1
Group #1 OPERATE_FLAG
Operate
49- RTD 1 IEEE_49_RTD_GROUP_2_ I 0,1 FFFF 1
Group #2 OPERATE_FLAG
Operate
49- Ther- 1 IEEE_49_THERMAL_MODEL_ I 0,1 FFFF 1
mal Model ALARM_1_FLAG
Alarm 1
49- Ther- 1 IEEE_49_THERMAL_MODEL_ I 0,1 FFFF 1
mal Model ALARM_2_FLAG
Alarm 2
49- Thermal 1 IEEE_49_THERMAL_MODEL_ I 0,1 FFFF 1
Model Op- OPERATE_FLAG
erate
50P-1 1 IOC_50P_1_PHASE_OP I 0,1 FFFF 1
Phase IOC
Operation
Flag
Phase IOC
Operation
Flag
Phase IOC
Operation
Flag
50R-1 Ir 1 IOC_50R_1_IR_OP I 0,1 FFFF 1
IOC Opera-
tion Flag
IOC Opera-
tion Flag
IOC Opera-
tion Flag
50X-1 Ix 1 IOC_50X_1_IX_OP I 0,1 FFFF 1
IOC Opera-
tion Flag
IOC Opera-
tion Flag
IOC Opera-
tion Flag

FP-6000
tion Reg- Type
isters
51P Phase 1 TOC_51P_PHASE_OP I 0,1 FFFF 1
TOC Oper-
ation Flag
51P2 Phase 1 PHASE_TOC_51P2_ I 0,1 FFFF 1
TOC Oper- OPERATION_FLAG
ation Flag
51R Ir TOC 1 TOC_51R_IR_OP I 0,1 FFFF 1
Operation
Flag
51X Ix TOC 1 TOC_51X_IX_OP I 0,1 FFFF 1
Operation
Flag
55A App 1 APP_55A_PWR_FACT_OP I 0,1 FFFF 1
Pwr Factor
Op Flag
55D Displ 1 DISP_55D_PWR_FACT_OP I 0,1 FFFF 1
Pwr Factor
Op Flag
59-A1 Aux 1 AUX_59_A1_OV_OP I 0,1 FFFF 1
Vx Over
Volt Flag
59-A2 Aux 1 AUX_59_A2_OV_OP I 0,1 FFFF 1
Vx Over
Volt Flag
59-M1 Main 1 MAIN_59_M1_OV_OP I 0,1 FFFF 1
Vp Over
Volt Flag
59-M2 Main 1 MAIN_59_M2_OV_OP I 0,1 FFFF 1
Vp Over
Volt Flag
59N-1 1 RESIDUAL_VOLTAGE_59N_ I 0,1 FFFF 1
Residual 1_OPER_FLAG
Voltage Op-
eration Flag
59N-2 1 RESIDUAL_VOLTAGE_59N_ I 0,1 FFFF 1
Residual 2_OPER_FLAG
Voltage Op-
eration Flag
79- Auto- 1 AUTO_RECLOSER_STATUS R# 0, 1, 2, 3, 4, 5 FFFF 1
matic Re-
closer Sta- 0=unknown, 1=off,
tus 2=ready, 3=run,
4=lockout, 5=blocked
79- Fail 1 IEEE_79_FAIL_FLAG I 0,1 FFFF 1
79- Reclose NA IEEE_79_SHOT_1_FLAG I 0,1 NA NA
Shot #1
Shot #2
Shot #3
Shot #4
79- Voltage NA IEEE_79_VOLTAGE_BLOCK_ I 0,1 NA NA
Block Trip TRIP_FLAG
79- Voltage NA IEEE_79_VOLTAGE_BLOCK_ I 0,1 NA NA
Block Pick- PICKUP_FLAG
up
Reclose NA IEEE_79_RECLOSE_BLOCK_ I 0,1 NA NA
Block FLAG
81O-1 1 MISC_81O_1_OF_OP I 0,1 FFFF 1
Overfre-
quency Op
Flag

FP-6000
tion Reg- Type
isters
81O-2 1 MISC_81O_2_OF_OP I 0,1 FFFF 1
Overfre-
quency Op
Flag
81U-1 Un- 1 MISC_81U_1_UF_OP I 0,1 FFFF 1
derfrequen-
cy Op Flag
81U-2 Un- 1 MISC_81U_2_UF_OP I 0,1 FFFF 1
derfrequen-
cy Op Flag
Accumulat- 1 ACC_INT_CURRENT_ALARM I 0,1 FFFF 1
ed Interrupt-
ed Current
Alarm Flag
Alarm 1 ALARM_OUTPUT I 0,1 FFFF 1
Alarm LED 1 ALARM_LED I 0,1 FFFF 1
Flag
Breaker An- 1 IEEE_BREAKER_ANTI_ I 0,1 FFFF 1
ti-Pumping PUMPING_FLAG
Breaker Fail 1 BREAKER_FAIL_OP I 0,1 FFFF 1
Op Flag
Breaker 2 BH_ACCUM_INT_IA R# 0 to 4,294,967,293 A FFFFFFFFFF 1
History Ac-
cumulated
Interrupted
IA
Breaker 2 BH_ACCUM_INT_IB R# 0 to 4,294,967,293 A FFFFFFFFFF 1
History Ac-
cumulated
Interrupted
IB
Breaker 2 BH_ACCUM_INT_IC R# 0 to 4,294,967,293 A FFFFFFFFFF 1
History Ac-
cumulated
Interrupted
IC
Breaker 1 BH_NUM_BREAKER_OPS R# 0 to 65,533 FFFF 1
History
Number of
Breaker Op-
erations
Breaker Op- 1 BREAKER_OPS_ALARM I 0,1 FFFF 1
erations
Alarm Flag
Breaker Po- 1 BREAKER_POSITION R# 0, 1, 2 FFFF 1
sition
0=unknown, 1=open,
2=closed.
Breaker 1 BREAKER_STATE_ALARM I 0,1 FFFF 1
State Alarm
Flag
Break- 1 BREAKER_STATE_ I 0,1 FFFF 1
er State CHANGE_OF_STATE
Change of
State Flag
Break- 1 BREAKER_STATE_CLOSED I 0,1 FFFF 1
er State
Closed Flag
Breaker 1 BREAKER_STATE_FAILURE I 0,1 FFFF 1
State Fail
Flag
Breaker 1 BREAKER_STATE_LOCKOUT I 0,1 FFFF 1
State Lock-
out Flag

FP-6000
tion Reg- Type
isters
Breaker 1 BREAKER_STATE_OPEN I 0,1 FFFF 1
State Open
Flag
Breaker 1 SLOW_BREAKER_CLOSE_ I 0,1 FFFF 1
State Time TIME
Alarm Flag
CIN_Flags_Word
1 CIN_FLAGS_WORD I 0 to 65535 FFFF 1
(NA for
DDE/OPC)
Comm Log- 1 COMM_LOGIC_STATE I 0 to 255 FFFF 1
ic State
Contact In- 1 CIN1 I 0,1 FFFF 1
put 1 Flag
put 2 Flag
put 3 Flag
put 4 Flag
put 5 Flag
put 6 Flag
put 7 Flag
put 8 Flag
Current De- 1 CURRENT_DMD_ALARM I 0,1 FFFF 1
mand Alarm
Flag
Current 1 CURRENT_THD_ALARM I 0,1 FFFF 1
THD Alarm
Flag
Frequency 1 FREQ R#.## 10.00 to 99.99 Hz FFFF 100
Frequency 1 FREQUENCY_TRIPS R# 0 to 65,533 FFFF 1
Trips
Ground Trip 1 GROUND_TRIP_LED I 0,1 FFFF 1
LED Flag
I(Fourth CT) 2 FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
I(Fourth CT) 2 FOURTH_CT_CURRENT_ R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Magnitude MAGNITUDE
I(Fourth CT) 1 FOURTH_CT_CURRENT_ R#.## -327.65 to +327.65 7FFF 100
Phase PHASE
I(Negative 2 NEGATIVE_SEQUENCE_ R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Sequence) CURRENT_MAGNITUDE
Magnitude
I(Negative 1 NEGATIVE_SEQUENCE_ R#.## -327.65 to +327.65 7FFF 100
Sequence) CURRENT_PHASE
Phase
I(Positive 2 POSITIVE_SEQUENCE_ R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Sequence) CURRENT_MAGNITUDE
Magnitude
I(Positive 1 POSITIVE_SEQUENCE_ R#.## -327.65 to +327.65 7FFF 100
Sequence) CURRENT_PHASE
Phase
I(R) 2 IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
I(Residual) 2 RESIDUAL_CURRENT_ MAG- R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Magnitude NITUDE
I(Residual) 1 RESIDUAL_CURRENT_PHASE R#.## -327.65 to +327.65 7FFF 100
Phase

FP-6000
tion Reg- Type
isters
I(Zero Se- 2 ZERO_SEQUENCE_CURRENT_ R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
quence) MAGNITUDE
Magnitude
I(Zero Se- 1 ZERO_SEQUENCE_CURRENT_ R#.## -327.65 to +327.65 7FFF 100
quence) PHASE
Phase
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- 2 IAPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
mand
Ia Magni- 2 IA_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
tude
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- 2 IBPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
mand
Ib Magni- 2 IB_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
tude
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- 2 ICPEAK R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
mand
Ic Magni- 2 IC_MAGNITUDE R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
tude
Ic Phase 1 IC_PHASE R#.## -327.65 to +327.65 7FFF 100
LED Indica- 1 LED_INDICATOR_1_FLAG I 0,1 FFFF 1
tor #1
tor #2
tor #3
tor #4
tor #5
tor #6
tor #7
tor #8
Logic Gate 1 LOGIC_GATE1_OUTPUT_ I 0,1 FFFF 1
1 FLAG
2 FLAG
3 FLAG
4 FLAG
5 FLAG
6 FLAG

FP-6000
tion Reg- Type
isters
LOP Alarm 1 LOP_ALARM_FLAG I 0,1 FFFF 1
Flag
LOP Block 1 LOP_BLOCK_FLAG I 0,1 FFFF 1
Flag
LOP Flag 1 LOP_FLAG I 0,1 FFFF 1
Max Appar- 2 MAX_VA R# 0 to 4,294,967,293 VA 7FFFFFFF 1
ent Power
(VA)
Max Fre- 1 MAX_FREQUENCY R#.## 0 to 655.33 Hz FFFF 100
quency
Max 2 MAX_FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
I(Fourth CT)
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 2 MAX_IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
(Residual)
Max Reac- 2 MAX_REACTIVE_POWER R# 0 to 4,294,967,293 VAr 7FFFFFFF 1
tive Power
(VAr)
Max Re- 2 MAX_REAL_POWER R# 0 to 4,294,967,293 W 7FFFFFFF 1
al Power
(Watts)
Max Sys- 1 MAX_SYSTEM_PF_APP R#.## -1.00 to +1.00 7FFF 100
tem PF
(App)
Max Sys- 1 MAX_SYSTEM_PF_DISP R#.## -1.00 to +1.00 7FFF 100
tem PF
(Disp)
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- 2 MIN_VA R# 0 to 4,294,967,293 VA FFFFFFFFFF 1
ent Power
(VA)
Min Fre- 1 MIN_FREQUENCY R#.## 0 - 65.533 Hz FFFF 100
quency
Min I(Fourth 2 MIN_FOURTH_CT_CURRENT R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
CT)
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 2 MIN_IR R#.## 0 to 42,949,672.93 A FFFFFFFFFF 100
(Residual)
Min Reac- 2 MIN_REACTIVE_POWER R# 0 to 4,294,967,293 VAr 7FFFFFFF 1
tive Power
(VAr)
Min Re- 2 MIN_REAL_POWER R# 0 to 4,294,967,293 W 7FFFFFFF 1
al Power
(Watts)
Min System 1 MIN_SYSTEM_PF_APP R#.## -1.00 to +1.00 7FFF 100
PF (App)
Min System 1 MIN_SYSTEM_PF_DISP R#.## -1.00 to +1.00 7FFF 100
PF (Disp)

FP-6000
tion Reg- Type
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
Number 1 NUM_IOC_TRIPS R# 0 to 65,533 FFFF 1
IOC Trips
Number of 1 NUM_THERMAL_TRIPS R# 0 to 65,533 FFFF 1
Thermal
Trips
Number of 1 NUM_VAR_TRIPS R# 0 to 65,533 FFFF 1
VAr Trips
Number 1 NUM_OPERATING_HOURS R# 0 to 65,533 FFFF 1
Operating
Hours
Number 1 NUM_TIMES_POWERED_UP R# 0 to 65,533 FFFF 1
Times Pow-
ered Up
Number 1 NUM_TOC_TRIPS R# 0 to 65,533 FFFF 1
TOC Trips
Number 1 NUM_UNBAL_TRIPS R# 0 to 65,533 FFFF 1
Unbalance
Trips
Number 1 NUM_VOLT_TRIPS R# 0 to 65,533 FFFF 1
Volt Trips
Number of NA INCOMPLETE_SLAVE_ AC- R# 0 to 65,533 NA NA
Incomplete TIONS
Slave Ac-
tions
Per Phase 1 PER_PHASE_I_DEMAND_ R# 0 to 255 min FFFF 1
Current De- WINDOW
mand Win-
dow
Percent 1 PERCENT_CURRENT_ UNBAL- R# 0 to 65,533 % FFFF 1
Current Un- ANCE
balance
Percent 1 THDIA R# 0 to 65,533 % FFFF 1
THD Ia
Percent 1 THDIB R# 0 to 65,533 % FFFF 1
THD Ib
Percent 1 THDIC R# 0 to 65,533 % FFFF 1
THD Ic
Percent 1 THDVAB R# 0 to 65,533 % FFFF 1
THD Vab
Percent 1 THDVAN R# 0 to 65,533 % FFFF 1
THD Van
Percent 1 THDVBC R# 0 to 65,533 % FFFF 1
THD Vbc
Percent 1 THDVBN R# 0 to 65,533 % FFFF 1
THD Vbn
Percent 1 THDVCA R# 0 to 65,533 % FFFF 1
THD Vca
Percent 1 THDVCN R# 0 to 65,533 % FFFF 1
THD Vcn
Percent 1 PERCENT_VOLTAGE_ UNBAL- R# 0 to 65,533 % FFFF 1
Voltage Un- ANCE
balance

FP-6000
tion Reg- Type
isters
PF Appar- 1 PFAPP R#.## -1.00 to +1.00 7FFF 100
ent
PF Dis- 1 PFDISP R#.## -1.00 to +1.00 7FFF 100
placement
Phase Trip 1 PHASE_TRIP_LED I 0,1 FFFF 1
LED Flag
Pickup LED 1 PICKUP_LED I 0,1 FFFF 1
Flag
PLC 79- 1 PLC_79_BLOCKED_FLAG I 0,1 FFFF 1
Reclose
Blocked
PLC 79- 1 PLC_79_LOCKOUT_FLAG I 0,1 FFFF 1
Reclose
Lockout
PLC 79- NA PLC_79_INITIATE_FLAG I 0,1 NA NA
Reclose Ini-
tiate
Power De- 1 POWER_DEMAND_WINDOW R# 0 to 65,533 min FFFF 1
mand Win-
dow
Raw Status 2 RAW_STATUS I NA FFFFFFFFFF 1
Relay 3 1 RELAY3_OUTPUT I 0,1 FFFF 1
Relay 1 RELAY_HEALTHY I 0,1 FFFF 1
Healthy
Vahours 2 VAHRS (VAHRS = R# 0 to 4.294967293E+12 VA FFFFFFFFFF 1
(Apparent VAHRS_BASE x 10 SYSENR-
Energy) GYBASE)
VAhours 2 VAHRS_BASE FFFFFFFFFF 1
Base
VA (Appar- 2 VA R# -17,280,000k to VA 7FFFFFFF 1
ent Power) +17,280,000k
VA (Appar- 1 VA_PWR_ALARM I 0,1 FFFF 1
ent Power)
Alarm Flag
VA (Appar- 1 VA_PWR_DMD_ALARM I 0,1 FFFF 1
ent Power)
Demand
Alarm Flag
VA (Appar- 2 VADEMAND R# 0 to 16,674k VA FFFFFFFFFF 1
ent Power)
Demand
VA (Appar- 2 VAPEAK R# 0 to 18,634k VA FFFFFFFFFF 1
ent Power)
Demand
Peak
Reactive 1 VAR_PWR_ALARM I 0,1 FFFF 1
Power (VAr)
Alarm Flag
Reactive 1 VAR_PWR_DMD_ALARM I 0,1 FFFF 1
Power (VAr)
Demand
Alarm Flag
Reactive 2 VARS R# -17,280,000k to VAr 7FFFFFFF 1
Power (VAr) +17,280,000k
Reactive 2 VARSDEMAND R# 0 to 4,294,967,293 VAr FFFFFFFFFF 1
Power De-
mand (VAr)
Reactive 2 VARSPEAK R# 0 to 4,294,967,293 VAr FFFFFFFFFF 1
Power De-

FP-6000
tion Reg- Type
isters
mand (VAr)
Peak
VArhours 2 NEGVARHRS_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1
(Negative )
Base
VArhours 2 NEGVARHRS (NEGVARHRS = R# 0 to 4.294967293E+12 VArh FFFFFFFFFF 1
(Lagging / NEGVARHRS_BASE x 10 SY-
Negative SENRGYBASE)
Reactive
Energy )
VArhours 2 NETVARHRS (NETVARHRS = R# -2,147,483,645,000 to VArh 7FFFFFFF 1
(Net Reac- NETVARHRS_BASE x 10 SY- 2,147,483,645,000
tive Energy) SENRGYBASE)
Net 2 NETVARHRS_BASE R# -2,147,483,645,000 to 7FFFFFFF 1
VArhours 2,147,483,645,000
Base
VArhours 2 POSVARHRS (POSVARHRS = R# 0 to 4.294967293E+12 VArh FFFFFFFFFF 1
(Leading / POSVARHRS_BASE x 10 SY-
Positive Re- SENRGYBASE)
active Ener-
gy)
VArhours 2 POSVARHRS_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1
(Positive)
Base
Real Power 2 WATTS R# -17,280,000k to W 7FFFFFFF 1
(Watts) +17,280,000k
Real Pow- 2 WATTSDEMAND R# -32,767k to 32,767k W 7FFFFFFF 1
er Demand
(Watts)
Real Pow- 2 WATTSPEAK R# 0 to 18,634k W FFFFFFFFFF 1
er Demand
(Watts)
Peak
Real Pow- 1 WATT_PWR_ALARM I 0,1 FFFF 1
er (Watts)
Alarm Flag
Real Power 1 WATT_PWR_DMD_ALARM I 0,1 FFFF 1
(Watts) De-
mand Alarm
Flag
Energy 1 SYSENRGYEXP R# 0 to 255 (i.e. 3 = Kilo, 6 FFFF 1
Units = Mega)
Positive En- 2 POSENERGY_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1
ergy Base
Positive Re- 2 POSENERGY (POSENERGY = R# 0 to 4.294967293E+12 Wh FFFFFFFFFF 1
al Energy POSENERGY_BASE x 10 SY-
(Forward SENRGYBASE)
Watthours)
Negative 2 NEGENERGY_BASE R# 0 to 4,294,967,293 FFFFFFFFFF 1
Energy
Base
Negative 2 NEGENERGY (NEGENERGY = R# 0 to 4.294967293E+12 Wh FFFFFFFFFF 1
Real Ener- NEGENERGY_BASE x 10 SY-
gy (Reverse SENRGYBASE)
Watthours)
Net Real 2 NETENERGY (NETENERGY R# -2,147,483,645,000 to Wh 7FFFFFFF 1
Energy (Net = NETENERGY_BASE x 10 2,147,483,645,000
Watthours) NETENRGYBASE)
Net 2 NETENERGY_BASE R# -2,147,483,645,000 to 7FFFFFFF 1
Watthours 2,147,483,645,000
Base
RTD Num- 1 RTD_1_TEMPERATURE R# 0 to 255 C FFFF 1
ber1 Tem-
perature

FP-6000
tion Reg- Type
isters
ber2 Tem-
perature
ber3 Tem-
perature
ber4 Tem-
perature
ber5 Tem-
perature
ber6 Tem-
perature
ber7 Tem-
perature
ber8 Tem-
perature
ber9 Tem-
perature
ber10 Tem-
perature
ber11 Tem-
perature
RTD Num- 1 MAX_TEMPERATURE_RTD_1 R#.# 0 to 255.0 deg. C 7FFF 10
ber1 Max
Tempera-
ture
ber2 Max
Tempera-
ture
ber3 Max
Tempera-
ture
ber4 Max
Tempera-
ture
ber5 Max
Tempera-
ture
ber6 Max
Tempera-
ture
ber7 Max
Tempera-
ture
ber8 Max
Tempera-
ture
ber9 Max

FP-6000
tion Reg- Type
isters
Tempera-
ture
ber10 Max
Tempera-
ture
ber11 Max
Tempera-
ture
System 2 SYS_NEG_PEAK_DEMAND_ R# -2,147,483,645 to 0 W FFFFFFFFFF 1
Negative WATTS
Peak Real
Power De-
mand
Time of NA SYS_NEG_PEAK_DEMAND_ TIME NA 0 NA
System WATTS_TIME
Negative
Peak De-
mand
System 2 SYS_POS_PEAK_DEMAND_ R# 0 to 4,294,967,293 W FFFFFFFFFF 1
Positive WATTS
Peak Real
Power De-
mand
Time of NA SYS_POS_PEAK_DEMAND_ TIME NA 0 NA
System WATTS_TIME
Positive
Peak De-
mand
System Re- 2 SYS_DEMAND_WATTS R# -2,147,483,645 to W 7FFFFFFF 1
al Power +2,147,483,645
Demand
(Watts)
Time of NA SYS_TIME_LAST_RESET_ TIME NA 0 NA
Last Reset DEMAND_WATTS
of System
Demand
Time of NA BH_LOG_DATE_RESET TIME NA 0 NA
Breaker
History Log
Time Reset
Time of To- NA TH_LOG_DATE_RESET TIME NA 0 NA
tal History
Log Time
Reset
Time of NA TIME_MAX_VA TIME NA 0 NA
Max Appar-
ent Power
(VA)
Time of Min NA TIME_MIN_VA TIME NA 0 NA
Apparent
Power (VA)
Time of NA TIME_MAX_REACTIVE_POWER TIME NA 0 NA
Max Reac-
tive Power
(VAr)
Time of Min NA TIME_MIN_REACTIVE_POWER TIME NA 0 NA
Reactive
Power (VAr)
Time of NA TIME_MAX_REAL_POWER TIME NA 0 NA
Max Re-
al Power
(Watts)

FP-6000
tion Reg- Type
isters
Time of Min NA TIME_MIN_REAL_POWER TIME NA 0 NA
Real Power
(Watts)
Time of NA TIME_LAST_MM_POWER_ RE- TIME NA 0 NA
Last Reset SET
(Min Max
Power)
Time NA TIME_MAX_IR TIME NA 0 NA
of Max
I(Residual)
Time of Min NA TIME_MIN_IR TIME NA 0 NA
I(Residual)
Time NA TIME_MAX_FOURTH_CT_ TIME NA 0 NA
of Max CURRENT
I(Fourth CT)
Time of Min NA TIME_MIN_FOURTH_CT_ CUR- TIME NA 0 NA
I(Fourth CT) RENT
Time of NA TIME_MAX_IA TIME NA 0 NA
Max Ia
Time of Min NA TIME_MIN_IA TIME NA 0 NA
Ia
Time of NA TIME_MAX_IB TIME NA 0 NA
Max Ib
Time of Min NA TIME_MIN_IB TIME NA 0 NA
Ib
Time of NA TIME_MAX_IC TIME NA 0 NA
Max Ic
Time of Min NA TIME_MIN_IC TIME NA 0 NA
Ic
Time of NA TIME_OF_PEAK_IA TIME NA 0 NA
Peak Ia
Time of NA TIME_OF_PEAK_IB TIME NA 0 NA
Peak Ib
Time of NA TIME_OF_PEAK_IC TIME NA 0 NA
Peak Ic
Time of NA TIME_LAST_MM_I_RESET TIME NA 0 NA
Last Reset
(Min Max
Current)
Time of 1 NA TIME_1_PHASE_DEMAND_I_ TIME NA 0 NA
Phase De- RESET
mand Cur-
rent Reset
Time of NA TIME_LAST_1_PHASE_I_ DE- TIME NA 0 NA
Last 1 MAND
Phase Cur-
rent De-
mand Win-
dow
Time of NA TIME_MAX_PHA_LNV TIME NA 0 NA
Max Van
Time of Min NA TIME_MIN_PHA_LNV TIME NA 0 NA
Van
Time of NA TIME_MAX_PHB_LNV TIME NA 0 NA
Max Vbn
Time of Min NA TIME_MIN_PHB_LNV TIME NA 0 NA
Vbn
Time of NA TIME_MAX_PHC_LNV TIME NA 0 NA
Max Vcn
Time of Min NA TIME_MIN_PHC_LNV TIME NA 0 NA
Vcn

FP-6000
tion Reg- Type
isters
Time of NA TIME_MAX_PHA_LLV TIME NA 0 NA
Max Vab
Time of Min NA TIME_MIN_PHA_LLV TIME NA 0 NA
Vab
Time of NA TIME_MAX_PHB_LLV TIME NA 0 NA
Max Vbc
Time of Min NA TIME_MIN_PHB_LLV TIME NA 0 NA
Vbc
Time of NA TIME_MAX_PHC_LLV TIME NA 0 NA
Max Vca
Time of Min NA TIME_MIN_PHC_LLV TIME NA 0 NA
Vca
Time of NA TIME_LAST_MM_LNV_RESET TIME NA 0 NA
Last Reset
(Min Max L-
N V)
Last Reset NA TIME_LAST_MM_LLV_RESET TIME NA 0 NA
(Min Max L-
L V)
Time of NA TIME_MAX_FREQUENCY TIME NA 0 NA
Max Fre-
quency
Time of Min NA TIME_MIN_FREQUENCY TIME NA 0 NA
Frequency
Time of NA TIME_MAX_SYSTEM_PF_APP TIME NA 0 NA
Max Sys-
tem PF
(App)
Time of Min NA TIME_MIN_SYSTEM_PF_APP TIME NA 0 NA
System PF
(App)
Time of NA TIME_LAST_MM_APP_PF_ RE- TIME NA 0 NA
Last Reset SET
(Min Max
App PF)
Time of NA TIME_MAX_SYSTEM_PF_DISP TIME NA 0 NA
Max Sys-
tem PF
(Disp)
Time of Min NA TIME_MIN_SYSTEM_PF_DISP TIME NA 0 NA
System PF
(Disp)
Time of NA TIME_LAST_MM_DISP_PF_ TIME NA 0 NA
Last Reset RESET
(Min Max
Disp PF)
Time of NA TIME_OF_PEAK_WATTS TIME NA 0 NA
Peak Real
Power De-
mand
Time of NA TIME_OF_PEAK_VA TIME NA 0 NA
Peak Ap-
parent Pow-
er Demand
Time of NA TIME_OF_PEAK_VARS TIME NA 0 NA
Peak Reac-
tive Power
Demand
Time of NA TIME_OF_LAST_POWER_ RE- TIME NA 0 NA
Power Re- SET
set
Time of NA TIME_OF_LAST_POWER_ TIME NA 0 NA
Last Pow- DEMAND_WINDOW

FP-6000
tion Reg- Type
isters
er Demand
Window
Time of En- NA TIME_OF_ENERGY_RESET TIME NA 0 NA
ergy Reset
Time of Re- NA TIME_OF_RESET_FOR_MAX_ TIME NA 0 NA
set of Max RTD
RTD Tem-
peratures
THD Ia 2 THD_IA_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Magnitude
THD Ib 2 THD_IB_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Magnitude
THD Ic 2 THD_IC_MAGNITUDE R.## 0 to 42,949,672.93 A FFFFFFFFFF 100
Magnitude
THD Vab 2 THD_VAB_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
THD Van 2 THD_VAN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
THD Vbc 2 THD_VBC_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
THD Vbn 2 THD_VBN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
THD Vca 2 THD_VCA_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
THD Vcn 2 THD_VCN_MAGNITUDE R.## 0 to 42,949,672.93 V FFFFFFFFFF 10
Magnitude
Timer Gate 1 LOGIC_TIMER1_OUTPUT_ I 0,1 FFFF 1
1 FLAG
2 FLAG
3 FLAG
4 FLAG
5 FLAG
6 FLAG
Total Histo- 2 TH_ACCUM_INT_IA R# 0 to 4,294,967,293 A FFFFFFFFFF 1
ry Accumu-
lated Inter-
rupted IA
Total Histo- 2 TH_ACCUM_INT_IB R# 0 to 4,294,967,293 A FFFFFFFFFF 1
ry Accumu-
lated Inter-
rupted IB
Total Histo- 2 TH_ACCUM_INT_IC R# 0 to 4,294,967,293 A FFFFFFFFFF 1
ry Accumu-
lated Inter-
rupted IC
Total Histo- 1 TH_NUM_BREAKER_OPS R# 0 to 65,533 FFFF 1
ry Number
of Breaker
Operations
Total His- 1 POWER_TRIPS R# 0 to 65,533 FFFF 1
tory Num-
ber of Pow-
er Trips
Total Num- 1 TOTAL_NUM_OF_TRIPS R# 0 to 65,533 FFFF 1
ber of Trips

FP-6000
tion Reg- Type
isters
TRIP1 Mon- 1 TRIP1_MON_ACT I 0,1 FFFF 1
itor Active
Flag
TRIP1 Mon- 1 TRIP1_MON_ALM I 0,1 FFFF 1
itor Alarm
Flag
TRIP1 Out- 1 TRIP1_OUT I 0,1 FFFF 1
put Flag
TRIP2 Mon- 1 TRIP2_MON_ACT I 0,1 FFFF 1
itor Active
Flag
TRIP2 Mon- 1 TRIP2_MON_ALM I 0,1 FFFF 1
itor Alarm
Flag
TRIP2 Out- 1 TRIP2_OUT I 0,1 FFFF 1
put Flag
Tripping 1 TRIP_DISARMED I 0,1 FFFF 1
Disarmed
Flag
V(Auxiliary) 2 AUXILIARY_VOLTAGE R# 0 to 1,200,000 V FFFFFFFFFF 1
V(Auxiliary) 2 AUXILIARY_VOLTAGE_ MAG- R# 0 to 1,200,000 V FFFFFFFFFF 1
Magnitude NITUDE
V(Auxiliary) 1 AUXILIARY_VOLTAGE_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100
Phase
V(L-G) Av- 2 VLGAVG R# 0 to 1,200,000 V FFFFFFFFFF 1
erage
V(L-L) Aver- 2 VLLAVG R# 0 to 1,200,000 V FFFFFFFFFF 1
age
V(L-N) Av- 2 VLNAVG R# 0 to 1,200,000 V FFFFFFFFFF 1
erage
V(Negative 2 NEGATIVE_SEQUENCE_ R# 0 to 1,200,000 V FFFFFFFFFF 1
Sequence) VOLTAGE_MAGNITUDE
Magnitude
V(Negative 1 NEGATIVE_SEQUENCE_ R#.## -327.65 to +327.65 deg. 7FFF 100
Sequence) VOLTAGE_PHASE
Phase
V(Positive 2 POSITIVE_SEQUENCE_ R# 0 to 1,200,000 V FFFFFFFFFF 1
Sequence) VOLTAGE_MAGNITUDE
Magnitude
V(Positive 1 POSITIVE_SEQUENCE_ R#.## -327.65 to +327.65 deg. 7FFF 100
Sequence) VOLTAGE_PHASE
Phase
V(Zero Se- 2 ZERO_SEQUENCE_ R# 0 to 1,200,000 V FFFFFFFFFF 1
quence) VOLTAGE_MAGNITUDE
Magnitude
V(Zero Se- 1 ZERO_SEQUENCE_ R#.## -327.65 to +327.65 deg. 7FFF 100
quence) VOLTAGE_PHASE
Phase
Vab 2 VAB R# 0 to 1,200,000 V FFFFFFFFFF 1
Vab Magni- 2 VAB_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
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- 2 VAN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
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
tion Reg- Type
isters
Vbc Magni- 2 VBC_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
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- 2 VBN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
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- 2 VCA_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
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- 2 VCN_MAGNITUDE R# 0 to 1,200,000 V FFFFFFFFFF 1
tude
Vcn Phase 1 VCN_PHASE R#.## -327.65 to +327.65 deg. 7FFF 100
Voltage 1 VOLTAGE_THD_ALARM I 0,1 FFFF 1
THD Alarm
Flag
Zone Inter- 1 ZONE_INT_GROUND_OP I 0,1 FFFF 1
lock Gnd
Op Flag
Zone Inter- 1 ZONE_INT_OUPUT I 0,1 FFFF 1
lock Output
Flag
Zone Inter- 1 ZONE_INT_PHASE_OP I 0,1 FFFF 1
lock Phase
Op Flag
Zone Inter- NA ZONE_INTERLOCK_INPUT_ I 0,1 NA NA
lock Input FLAG
Flag
Zone Inter- NA ZONE_INTERLOCK_GROUND_ I 0,1 NA NA
lock Ground PICKUP_FLAG
Pickup Flag
Zone Inter- NA ZONE_INTERLOCK_PHASE_ I 0,1 NA NA
lock Phase PICKUP_FLAG
Pickup Flag
Table 7. FP-6000 Device Controls

Description Tag name DDE Type Modbus Direct
Value
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- ACTIVATE_RELAY_8 I 83D X
put
Close Breaker CLOSE_DEVICE I 601 X
Comm Logic State 1 COMM_LOGIC_1 I 846 X

FP-6000

Value
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 Interlock DEACTIVATE_RELAY_8 I 841 X
Output
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- RESET_AUTO_RECLOSER_LOCKOUT I 87F X
out
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/Max RESET_SENSOR_13_MIN_MAX_VALUES I 88D X
Value
Reset Sensor #14 Min/Max RESET_SENSOR_14_MIN_MAX_VALUES I 88E X
Value
Reset Sensor #15 Min/Max RESET_SENSOR_15_MIN_MAX_VALUES I 88F X
Value
Reset Sensor #16 Min/Max RESET_SENSOR_16_MIN_MAX_VALUES I 890 X
Value
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

Value
Select Active Group 1 ACTIVE_SET_GROUP_1 I 855 X
PM3
Table 8. PM3 Device Objects
Description # of Modbus DDE Tag Name DDE Range Units Invalid Scale
Registers Type Number Factor
Status 1 STATN R# 0, 4, 38 (See the Sta- FFFF 1
tus Codes table in Ap-
pendix A of the Power-
Net User's Guide.)
Status (String) NA STATT M NA NA NA
Status Secondary 1 STAT2N R# 0, 45, 46, (See the FFFF 1
Status Codes table
in Appendix A of the
PowerNet User's
Guide and in the sec-
tion called Additions
to Status and Reason
Codes [94] in this
Guide.)
Reason 1 RSONN R# 0, 1, 2, 3, 4, 5, 6, 18, FFFF 1
47, 339, 340 (See the
Reason Codes ta-
ble in Appendix A of
the PowerNet User's
Codes [94] in this
Guide.)
Reason (String) NA RSONT M NA NA NA
DDE Device NA ALARM I 0-30, 200-249 (See NA NA
Alarm the Alarm Codes ta-
ble in Appendix A of
the PowerNet User's
Codes [94] in this
Guide.)
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- 2 NEGENERGY R# 0 to 999999999000 Wh FFFFFFFF 1
ergy (Watthours)
Reverse Energy 2 NEGENERGY_BASE R# 0 to 4294967295 FFFFFFFF 1
Buffer
Lagging Reactive 2 NEGVARHRS R# +/- 999999999000 varh FFFFFFFF 1
Energy (Varhours)
Lagging Varhours 2 NEGVARHRS_BASE R# 0 to 4294967295 FFFFFFFF 1
Buffer

PM3
Net Real Energy 2 NETENERGY R# +/- 999999999000 Wh 7FFFFFFF 1
(Watthours)
Net Watthours 2 NETENERGY_BASE R# +/- 2147483647 7FFFFFFF 1
Buffer
Net Reactive En- 2 NETVARHRS R# +/- 999999999000 varh 7FFFFFFF 1
ergy (Varhours)
Net Varhours 2 NETVARHRS_BASE R# +/- 2147483647 7FFFFFFF 1
Buffer
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- 2 POSENERGY R# +/- 999999999000 Wh FFFFFFFF 1
ergy (Watthours)
Forward Energy 2 POSENERGY_BASE R# 0 to 4294967295 FFFFFFFF 1
Buffer
Leading Reactive 2 POSVARHRS R# +/- 999999999000 varh FFFFFFFF 1
Energy (Varhours)
Leading Varhours 2 POSVARHRS_BASE R# 0 to 4294967295 FFFFFFFF 1
Buffer
Raw Status 2 RAW_STATUS I NA FFFFFFFF 1
System Real 2 SYS_DEMAND_WATTS R# 0 to 2147483646 W 7FFFFFFF 1
Power Demand
(Watts)
System Negative 2 SYS_NEG_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1
Peak Real Power
Demand
System Positive 2 SYS_POS_PEAK_DEMAND_WATTS R# 0 to 4294967295 W FFFFFFFF 1
Peak Real Power
Demand
Energy Units 1 SYSENRGYEXP R# 0 to 65534 FFFF 1
Apparent Power 2 VA R# 0 to 2147450880 VA 7FFFFFFF 1
(VA)
Vab 1 VAB R#.# 0 to 600 V FFFF 10
Apparent Energy 2 VAHRS R# 0 to 999999999000 VAh FFFFFFFF 1
(VAhours)
VAhours Buffer 2 VAHRS_BASE R# 0 to 4294967295 FFFFFFFF 1
Apparent Power 2 VAMPA R# 0 to 2147450880 VA FFFFFFFF 1
(VA) Phase A
Apparent Power 2 VAMPB R# 0 to 2147450880 VA FFFFFFFF 1
(VA) Phase B
Apparent Power 2 VAMPC R# 0 to 2147450880 VA FFFFFFFF 1
(VA) Phase C
Van 1 VAN R#.# 0 to 600 V FFFF 10
Reactive Power 2 VARS R# +/- 1073709057 var 7FFFFFFF 1
(Vars)
Reactive Power 2 VARSA R# +/- 1073709057 var 7FFFFFFF 1
(Vars) Phase A
Reactive Power 2 VARSB R# +/- 1073709057 var 7FFFFFFF 1
(Vars) Phase B
Reactive Power 2 VARSC R# +/- 1073709057 var 7FFFFFFF 1
(Vars) Phase C
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
V(L-N) Average 1 VLNAVG R#.# 0 to 600 V FFFF 10
Real Power 2 WATTS R# +/- 1073709057 W 7FFFFFFF 1
(Watts)
Real Power 2 WATTSA R# +/- 1073709057 W 7FFFFFFF 1
(Watts) Phase A
Real Power 2 WATTSB R# +/- 1073709057 W 7FFFFFFF 1
(Watts) Phase B
Real Power 2 WATTSC R# +/- 1073709057 W 7FFFFFFF 1
(Watts) Phase C
Table 9. PM3 controls

Description Tag name DDE Type Modbus Value (hexideci- Direct BIM / BIMII
mal)
Reset Power Up RESET_POWER_UP I 833 X
Reset Slave Stats RESET_SLAVE_STATS I 649 X
Reset System Demand RESET_SYSTEM_DEMAND I 658 X
Watts
Table 10. PM3 Breaker Device Objects

Description # of Modbus Tag Name DDE Type Range Invalid Number Scale Fac-
Registers tor
Status 1 STATN R# 0, 1, 2, 3 (See the Status Codes FFFF 1
table in Appendix A of the Power-
Net User's Guide and in the sec-
tion called Additions to Status
and Reason Codes [94] in this
Guide.)
Status (String) NA STATT M NA NA NA
Status Secondary 1 STAT2N R# 0, 45 (See the Status Codes ta- FFFF 1
ble in Appendix A of the Power-
Guide.)
Reason 1 RSONN R# 0, 1, 2, 3, 4, 5, 6, 341, 480 (See the FFFF 1
Reason Codes table in Appendix A
of the PowerNet User's Guide and
in the section called Additions to
Status and Reason Codes [94]
in this Guide.)
Reason (String) NA RSONT M NA NA NA
DDE Device NA ALARM I 0-30, 200-249 (See the Alarm NA NA
Alarm Codes table in Appendix A of the
PowerNet User's Guide and in the
section called Additions to Status
Guide.)
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- FFFF
ble in Appendix A of the Power-
Guide.)

Additions to Status and Reason Codes
AdditionstoStatusandReasonCodes
Appendix A of the PowerNet documentation provides an incomplete set of status
codes 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- 45
plicable" or "not meaning-
ful" at this time.
POWERED UP Powered Up The device was powered 46
down and has subsequent-
ly been re-powered.
PICKED UP Picked Up A protective element within 47
the device has picked up.
TEST Test The device is in a test 48
state.
DISABLED Disabled The device is in a disabled 49
state.
DISARMED Disarmed The device is in a disarmed 50
state.
FAILED Failed The controlled device failed 51
to operate.
PH A TRIP Phase A Trip The device is in a trip state 52
due to a protective element
that has operated due to
electrical Phase A.
PH B TRIP Phase B Trip The device is in a trip state 53
electrical Phase B.
PH C TRIP Phase C Trip The device is in a trip state 54
electrical Phase C.
NEUT TRIP Neutral Trip The device is in a trip state 55
the electrical Neutral.
GRND TRIP Ground/Earth Trip The device is in a trip state 56
the electrical Ground/Earth.
PH A ALM Phase A Alarm The device is in an alarm 57
state due to a protective el-
ement that has operated
due to electrical Phase A.
PH B ALM Phase B Alarm The device is in an alarm 58
due to electrical Phase B.
PH C ALM Phase C Alarm The device is in an alarm 59
due to electrical Phase C.
NEUT ALM Neutral Alarm The device is in an alarm 60
due to the electrical Neu-
tral.
GROUND Ground/Earth The device is in an alarm 61
state due to a protective
element that has operat-
ed due to the electrical
Ground/Earth.


PH AB ALM Phase AB Alarm The device is in an alarm 62
due to electrical Phases A
& B.
PH BC ALM Phase BC Alarm The device is in an alarm 63
due to electrical Phases B
& C.
PH CA ALM Phase CA Alarm The device is in an alarm 64
due to electrical Phases C
& A.
GOOD SRC On Good Source The device is on a good 65
electrical source.
OVERLOAD Overload The device is in an over- 66
load state due to a pro-
tective element that has
sensed an electrical over-
load condition.
FIXEDINST Fixed Instantaneous The device state is due to 67
a fixed instantaneous over-
current condition.
HIGHINST High Instantaneous The device state is due to 68
a high instantaneous over-
current condition.

UNDEFINED (225) Undefined Status Code The device status code is 225
(225) undefined (Code = 225)

Table 12. Reason Codes

DISARM Disarmed The device state is dis- 226
armed.
STOPPED Stopped The device state is 227
stopped.
RESET Reset The device state is reset. 228
POWERUP Powered Up The device was powered 229
down and has subsequent-
ly been powered up.
MCRTRIP Making Current Release The device state is due to 230
making current release op-
eration
HIGH INST High Instantaneous The device state is due to 231
the high instantaneous cur-
rent.
STPMISMAT Setpoint Mismatch The device has detected a 232
setpoint mismatch.
STPTRAN Setpoint Transfer Error The device has detected a 233
setpoint transfer error.
ACCBUS Accessory Bus The reason for the device 234
state is due to an input on
the accessory bus.
THD Total Harmonic Distortion The device state is due to 235
electrical total harmonic
distortion.
PWRFACT Power Factor The device state is due to 236
power factor
KWDMD Demand kW The device state is due to 237
real power (kW) demand.
KVADMD Demand kVA The device state is due to 238
apparent power (kVA) de-
mand.
OP COUNT Operations Count The device state is due to 239
the device operation count.
HIST Historical Data The device state is due 240
to a previous operation or
condition (i.e. historical)
ERROR Error The device has detected 241
an error.
WATDOG WatchDog The reason for the device 242
state is due to a watchdog
timer error.
CBEMA CBEMA The device state is due to 243
a ITIC/CBEMA event.
HGHSPEED High Speed The device state is due to 244
a high speed condition.
SETCHG Settings Saved The device settings have 245
been saved.
EMR_OVRD Emergency Override The device state is due to 246
an emergency override op-
eration.
RESERVED Reserved (247) The reason code is re- 247
served (Code = 247)

RESERVED Reserved (255) The reason code is re- 255
served (Code = 255)
FTSOP Fail to Sync On Phase The device state is due to 256
a failure to synchronize on
phase.


FTSOF Fail to Sync On Frequency The device state is due to 257
frequency
FTSOV Fail to Sync On Voltage The device state is due to 258
voltage
INST Instantaneous The device state is due to 259
the instantaneous overcur-
rent protection element.
LONG DELAY Inverse Time Long Delay The device state is due to 260
the inverse long delay time
overcurrent protection ele-
ment.
NEUTRAL Inverse Time Neutral The device state is due to 261
the inverse time neutral
ment.
LONG DELAY Long Delay The device state is due to 262
the long delay time over-
current protection element.
SHORTDELAY Short Delay The device state is due to 263
the short delay time over-
GND FAULT Ground Fault The device state is due to 264
the ground fault protection
element.
EARTHFAULT Earth Fault The device state is due to 265
the earth fault protection el-
ement.
ENGINETST Engine Test The device state is due to 266
an engine test.
EMERINHBT Emergency Inhibit The device state is due to 267
an emergency inhibit oper-
ation.
MNTRMODE Monitor Mode The device state is due 268
monitor mode.
ABORT Abort The device state is due an 269
aborted operation.
INACTCHAN Inactive Channel(s) The device state is due an 270
inactive channel
CKSUMFAIL Checksum Test Failed The device checksum test 271
has failed.
FAILSAFE Failsafe The device state is due a 272
failsafe condition
POWER Power The device state is due an 273
electrial power protection
element.
CURR THD Current THD The device state is due an 274
electrial current THD pro-
tection element.
VOLT THD Voltage THD The device state is due an 275
electrial voltage THD pro-
tection element.
PICKUP Pickup The device state is due a 276
pickup of an electrial pro-
tection element.
TRIP Trip The device state is due a 277
trip issued by electrial pro-
tection element.
CONTACT IN Contact Input The device state is due a 278
contact input.
SYSTEM System The device state is due a 279
system operation.


CONTROL Control The device state is due a 280
control
PHASE OC Phase Overcurrent The device state is due to 281
the phase overcurrent pro-
tection element.
GRND OC Ground Overcurent The device state is due to 282
the ground overcurrent pro-
tection element.
INST OC Instantaneous Overcurrent The device state is due to 283
the instantaneous over-
current protection element
(50).
INVTIME OC Inverse Time Overcurrent The device state is due to 284
the inverse time overcur-
rent protection element
(51).
ALARM Alarm The device state is due an 285
alarm.
VOLTAGE Voltage The device state is due an 286
electrial voltage protection
element.
FREQ Frequency The device state is due an 287
electrial frequency protec-
tion element.
OPEN BKR Open Breaker Open circuit breaker. 288
CLOSE BKR Close Breaker Close circuit breaker. 289
BKR CLOSED Breaker Closed The device has detected a 290
closed circuit breaker.
BKR ALARM Breaker Alarm The device state is due a 291
circuit breaker alarm.
CONFIG Configuration The device state is due to 292
configuration.
SCALING Scaling The device state is due to 293
scaling.
WIRING Wiring The device state is due to 294
wiring.
MAINT Maintenance Mode The device is in mainte- 295
nance mode.
AR FAILURE Automatic Recloser Failure The automatic recloser has 296
failed.
FIXEDINST Fixed Instantaneous The device state is due a 297
fixed instantaneous opera-
tion.
HIGHINST High Instantaneous The device state is due a 298
high instantaneous opera-
tion.
299 Reserved (299) The reason code is re- 299
served (Code = 299)
EXTERNAL External event The device state is due to 300
an external event.
PH IOC 50P: Instantaneous Phase The device state is due to 301
Overcurrent the instantaneous phase
ment (50P).
IG IOC 50G: Instantaneous The device state is due to 302
Ground Overcurrent the instantaneous ground
ment (50G).
IN IOC 50N: Instantaneous Neutral The device state is due to 303
Overcurrent the instantaneous neutral
ment (50N).


IR IOC 50R: Instantaneous Resid- The device state is due to 304
ual Overcurrent the instantaneous residual
ment (50R).
PH TOC 51P: Inverse Time Phase The device state is due 305
Overcurrent to the inverse time phase
ment (51P).
IG TOC 51G: Inverse Time Ground The device state is due to 306
Overcurrent the inverse time ground
ment (51G).
IN TOC 51N: Inverse Time Neutral The device state is due to 307
Overcurrent the inverse time neutral
ment (51N).
IR TOC 51R: Inverse Time Residu- The device state is due to 308
al Overcurrent the inverse time residual
ment (51R).
OV 59: Overvoltage The device state is due to 309
the overvoltage protection
element (59).
UV 27: Undervoltage The device state is due to 310
the undervoltage protection
element (27).
AUX OV 59A: Auxiliary Overvoltage The device state is due to 311
the auxiliary overvoltage
protection element (59A).
AUX UV 27A: Auxiliary Undervolt- The device state is due to 312
age the auxiliary undervoltage
UFREQ 81U: Underfrequency The device state is due to 313
the underfrequency protec-
tion element (81U).
OFREQ 81O: Overfrequency The device state is due to 314
the overfrequency protec-
tion element (81O).
I UNBAL 46: Current Unbalance The device state is due to 315
the overfrequency protec-
tion element (81O).
V UNBAL 47: Voltage Unbalance The device state is due to 316
the voltage unbalance pro-
tection element (47).
APP PF 55A: Apparent Power Fac- The device state is due to 317
tor the apparent power factor
DISP PF 55D: Disp Power Factor The device state is due to 318
the displacement power
factor protection element
(55D).
LOW BATT Low Battery: Save all log The device state is due to 319
data low battery (save all log da-
ta).
50X 50X: Instantaneous Aux The device state is due to 320
Overcurrent the instantaneous auxilliary
ment (50X).
51X 51X: Inverse Time Auxil- The device state is due to 321
liary Overcurrent the inverse time auxilliary
ment (51X).
ZONEINTPIC Zone Interlock Pickup The device state is due to 322
zone interlock pickup.


ACCINTCUR Accumulated Interrupt Cur- The device state is due to 323
rent the accumulated interrupt
51P2 51P2: Inverse Time Phase The device state is due 324
Overcurrent to the inverse time phase
overcurrent secondary pro-
tection element (51P2).
59NG 59NG: Neutral-Ground The device state is due to 325
Overvoltage the neutral-to-ground over-
voltage protection element
(59NG).
LOP Loss Of Potential The device state is due to 326
the loss of potential.
POWER PU 32: Power Pickup The device state is due to 327
pickup of the power protec-
tion element (32).
59N 59N: Neutral Overvoltage The device state is due 328
to the neutral overvoltage
protection element (59N).
POWER TRIP 32: Overpower/Underpow- The device state is due to 329
er a trip issued by the power
protection element (32).
MAINT Maintenance Mode The device state is due to 330
maintenance mode.
BKR MECH Breaker Mechanism Fail- The device has detected a 331
ure circuit breaker mechanism
failure
AR LOCKOUT 79: Automatic Recloser The automatic recloser is 332
Lockout in lockout.
THERMAL Thermal Trip The device state is due to 333
a trip issued by a thermal
protection element.
THERMAL Thermal Alarm The device state is due to 334
an alarm issued by a ther-
mal protection element.
GROUP VAR Group VAr Trip The device state is due to 335
a trip issued by the group
VAr protection element.
HACCINTCUR Hourly Accumulated Inter- The device state is due to 336
rupt Current hourly accumulated inter-
rupt current
WEAR ALARM Breaker Wear Alarm The circuit breaker wear 337
alarm is active
LOCKOUT Breaker Wear Lockout The circuit breaker is 338
locked out due to exces-
sive wear
ENGSTORE Metered Energy Storage Metered Energy Storage 339
Error Error
MEASURE Meter Measurement Fail- Meter Measurement Fail- 340
ure ure
AUX Auxiliary Contact(s) Auxiliary Contact(s) 341

398 Reserved (398) The reason code is re- 398
served (Code = 398)
RES OUT RG Reason Code Out of The reason code is out of 399
Range range
EXTERNAL External Condition #1 External Condition #1 400
PH IOC Instantaneous Phase Over- Instantaneous Phase Over- 401
current current
IG IOC Instantaneous Ground Instantaneous Ground 402
Overcurrent Overcurrent


IN IOC Instantaneous Neutral Instantaneous Neutral 403
IR IOC Instantaneous Residual Instantaneous Residual 404
PH TOC Inverse Time Phase Over- Inverse Time Phase Over- 405
current current
IG TOC Inverse Time Ground Over- Inverse Time Ground Over- 406
current current
IN TOC Inverse Time Neutral Over- Inverse Time Neutral Over- 407
current current
IR TOC Inverse Time Residual Inverse Time Residual 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- Control via Communica- 423
tions tions
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- Long Delay Phase Over- 451
current current
SHORT DELA Short Delay Phase Over- Short Delay Phase Over- 452
current current
FINST #1 Fixed Instantaneous Phase Fixed Instantaneous Phase 453
Overcurrent #1 Overcurrent #1
REV POW Reverse Power Reverse Power 454
REV PHASE Reverse Phase Reverse Phase 456
I NEAR PU Phase Current Near Pickup Phase Current Near Pickup 457
OVERTEMP Over-temperature Over-temperature 459
LD NEUTRAL Long Delay Neutral Over- Long Delay Neutral Over- 460
current current
EXTERNAL 2 External Condition #2 External Condition #2 461
GND FAULT Ground Fault (Instanta- Ground Fault (Instanta- 463
neous or Delay) neous or Delay)
EARTH Earth Fault (Instantaneous Earth Fault (Instantaneous 464
or Delay) or Delay)
MULT EXT Multiple External Condi- Multiple External Condi- 471
tions tions
MOTOR BNG Motor Bearing Tempera- Motor Bearing Tempera- 472
ture ture
LOAD BNG Load Bearing Temperature Load Bearing Temperature 473
GND DELAY Time Delayed Ground Time Delayed Ground 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- Diagnostic Failure on Pow- 487
er Up er Up


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 a 491
disconnect position condi-
tion.
SHNTRPPRB Shunt Trip Problem The device has sensed a 492
shunt trip problem.
WARN UNIT Warning: Replace Unit The device has sensed an 493
incipient failure. The unit
should be replaced.
FAIL UNIT Failure: Replace Unit The device has sensed a 494
failure. The unit must be
replaced.

104
InstallingPowerNet
Important
When upgrading PowerNet to version 3.40, use the PNUPDATE key ONLY. If
you 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 Server

2008, 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 the
PXS 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 following
chapters.
Also, refer to the PXS Release Notes for additional PowerNet specific information.
106
PowerNetforNon-AdministrativeUsers
While 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 following
sections cover how to set up PowerNet to run with such an account.
AddingthePowerNetUsertotheRequiredGroups
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. In

some 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 and
PowerNetUser groups.
8. Right-click Users and select Properties.
9. Select the user in the Members list.
10. Click Remove.
11. Click OK.
PowerNetDomainServerConfiguration
Note
The following procedures are for Windows Server 2008. If you are using a
different 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 the
unset read-only change.
PowerNetClientConfiguration
To 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 the
unset read-only change.

110
PowerNetServerwithRemoteSQLServer
The PowerNet Database Server usually runs on the same PC as the SQL Server
database. However, there are instances where you may need these two applications
to 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 must
be installed on the PC. The installation file (SQLServer2005_BC.msi) for this is
available in the PowerNet\SQLBC folder on the PXS DVD.
SQL Management Studio must be installed. This is covered in Installing Microsoft

SQL Server Management Studio 2008 [63].
The Windows Firewall should be turned off. Also, on Windows Server 2008, the
Advanced 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 User

Groups, as well as create databases, tables, etc.
2. Create the following files:
NGSWINST.INI This must be located in the WINNT or Windows folder. The

contents must have a path pointing to a folder where the Pow-
erNet SQL Server database files and transaction log files are
to be located. If this folder does not already exist, you must
create it. The historical PowerNet Microsoft Access databas-
es must be located in this folder if you wish to import previous
historical data into the SQL Server database. For example:
[DomainShare]
_PNetDb=drive:\PowerNet\Database
DBSVRNAME.INI This must be located in the _PNetDb folder. The contents

must include the following where myservername is the SQL
Server Server instance that you want to use. For example:
[MSDE]
SQLServerName=myservername
3. Setup Windows sharing for the folder in which the PowerNet SQL Server
databases will be located. Set the share name to _PNetDb.
4. Copy the Microsoft Access databases to the _PNetDb folder if you want to import
a previous PowerNet system into the new SQL Server databases.
5. Copy the contents of the PowerNet\EBILLData folder located on the PXS DVD
into 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 the
following 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 transaction
log files folder. This is the path that you previously specified
in the NGSWINST.INI file.
7. While in the working folder, from the command line run

ConvertEBillDatabase.exe to create engbill32 tables and/or import old
engbill32 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 engbill32
data 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 Server
2008, this program requires SQL Backward Compatibility. Before you can run
ProjectDTSPowerNetDBCreate.exe you must copy the following files from the
PowerNet\PowerNet\Config folder on the PXS DVD to a working folder on
the 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 the
same 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 with
regsvr32.exe:
regsvr32.exe
ocxfile
Where:
ocxfile is the name of the .ocx file.
10. Run ProjectDTSPowerNetDBCreate.exe to set up the PowerNet historical

databases:

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 selection
will 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 previous
PowerNet data from the Access databases into the SQL Server databases.
d. The Database Path edit box should display the path where the PowerNet
SQL Server database files and transaction log files will reside and where
the historical PowerNet databases are located. This path is read from the
NGSWINST.INI file.
e. Click the Build Databases button.
Note
If ProjectDTSPowerNetDBCreate.exe fails to create the

databases when the server name is (local), replace (local) with the
SQL Server instance in the Available Servers box.
11. ProjectDTSPowerNetDBCreate.exe created two Windows Users Groups,

PowerNetUser and PowerNetPowerUser, on the remote PC. You must assign
users to one or the other of these groups to allow access to the PowerNet SQL
Server 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 PowerNet

historical databases. E-Bill users should belong to this
group.
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 working
folder. For example:
UpdateEbillDatabase.exe
14. From a Windows command prompt, run the following PowerNet database update
batch 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 servername
AutoClose.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 from
the Services Control Panel (Start Administrative Tools Services). The
Startup 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, set
the Database Remote Connections to Local and remote connections using
TCP/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 and
set TCP/IP to Enabled.
18. For SQL Server 2005 and SQL Server 2008 run Local Security Policy from the
Control 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 to
use a remote SQL Server when prompted. Select the appropriate remote SQL
Server 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 the
SQLServerName to the remote SQL Server instance in the DBSVRNAME.INI file
(this resides in the PowerNet Database folder). Also, run the ODBC Data Source
Administrator from Administrative Tools and change the following ODBC DSNs
to 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 its
Properties window. (Right-click and select Properties.)
6. Click the Log On tab in the Properties window. Select This account under Log
on as and type a user account and password that will enable Database Server
access to the remote PC. Click OK to save and exit.
7. Start the PowerNet Database Server service.
TechnicalSupport
For technical support on this topic or PowerNet in general, contact Eaton Power
Quality Technical Support at 1-800-809-2772 or pqsupport@eaton.com.

120

Power Xpert Administrators Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Power Xpert Administrators Guide

Caricato da

Copyright:

Formati disponibili

MN02601006E

Specifications contained herein are subject to change without notice.

Power Xpert is a registered trademark of Eaton Corporation.

DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY

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

Prerequisites for Power Xpert Software (PXS) installation.

PXS deployment (database, security, and IIS).

Power Xpert Reports integration.

While installation of PXS doesn't require that you be a system administrator or

Processor 2.8 GHz, dual-core processor.

Memory 2 GB allocated for PXS (allocate 3 GB of memo-

Disk Space Required for A typical database will grow to 2 GB within a

PXS will issue an alarm should free disk

Video Resolution 1280 by 1024 pixels or higher.

Removable Media DVD RO drive.

You may wish to add the following hardware as well:

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

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

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.

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

Supported Versions of Microsoft SQL Server:

SQL Server 2005 Express SP3

Additional Software Components:

.NET Framework 3.5 SP1

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

Windows Installer 4.5

SQL Server Management Studio is not installed. SQL Server Management

You must open the following ports on the PXS client:

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

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

Where machine_name is the name of the server.

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

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

3. In the installer, click Next.

Figure 2. Installer Main Screen

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

Figure 5. Security Warning Dialog Box

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

Figure 6. Setup Wizard

Figure 7. Setup Wizard

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

Figure 8. Setup Wizard

Figure 9. Selecting PXS Components

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

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

Figure 10. Installing PXS Components

Figure 11. Installation Complete Dialog Box

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

Figure 12. Deployment & Validation Indicator/Navigation Buttons

Figure 13. Possible Indicator States

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

Figure 14. Windows Groups Task Panel

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

Figure 15. Configure IIS Task Panel

The Deployment & Validation Utility uses the Windows Firewall/Internet

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

Figure 16. Firewall Task Panel

Before attempting to deploy the databases, review the account information in

To deploy the PXS database:

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

Figure 17. Successful Connection

Figure 18. Example Task Details Output