PowerFlex 7000

DataAnalyzer

User Reference Manual

Revision 1.2

(FRN .006B)

Prepared by:

Wayne Davis
Power Products Development
Control Team
 Table of Contents

INTRODUCTION ........................................................................................................................................ 3

SCOPE........................................................................................................................................................... 3

DETAILED OPERATION .......................................................................................................................... 4

SETUP .......................................................................................................................................................... 4
VIEW ........................................................................................................................................................... 5
Event History .......................................................................................................................................... 5
Alarm Queue........................................................................................................................................... 6
Control Data........................................................................................................................................... 7
Trend Capture ........................................................................................................................................ 8
Parameters ............................................................................................................................................. 9
Variables ................................................................................................................................................ 9
Revision Levels ..................................................................................................................................... 10
MARKS & SEARCHING............................................................................................................................... 11
ANALYZE .................................................................................................................................................. 13
MERGE ...................................................................................................................................................... 14
UPLOADING DATA VIA HYPERTERMINAL .................................................................................................. 16

2
Introduction
Various reports are available within the drive such as Alarm Queues, Customizable Trending,
Parameter and Variables, Event logs and Fixed Control Data Capture during fault conditions.
This tool is used to view and analyze all of this data within a single software tool referred to as the
Data Analyzer.

This tool along with the various data reports and logs is collectively being referred to as the “Black
Box Data” within development

Scope
The Data Analyzer and some of the data logs which it uses are primarily a tool for use by
development. It is also useful for advanced users within product support.

The tool is NOT for customer use and at this time should be considered a beta release, as it is
still undergoing changes as time permits and additional features are developed.

The tool requires the .NET Framework (available from Microsoft if not already loaded onto your
computer) in order to operate.

The files which the analyzer software uses to view the data must be uploaded using either:

a) via an RS232 connection using traditional methods such as HyperTerminal.

b) via the PFNetServer from within this program (preferred) or via File Explorer to a directory.

3
Detailed Operation
The program (DataAnalyzer.exe) is started by clicking on the filename. There are no command
line parameters associated with this program. The following Figure 1 shows the opening screen
and available menu options:

Figure 1

Setup

The Setup Menu must then be opened and “Filenames” selected. This will bring up the dialog
shown in Figure 2.

From this dialog, the user specifies the filenames of the individual data reports that the program
can analyze as well as the location of the data. It is recommended that the default filenames and
local path be used as any changes to the setup cannot be saved from one session of the program
to the next.

All data must be uploaded from the drive (refer to Uploading Data) and stored in a common
directory. This common directory is specified by the “Local Path”.

All data files with the exception of the “Control Data” are Comma Separated Variables (.CSV)
formatted files. These types of files can be directly read by Excel if desired. The “Control Data”
file is a binary file and can only be viewed using this program. The “Database” is a copy of the
appropriate database in Excel format and its use is optional as it does provide some additional
information when analyzing the reports.

The database by default is contained in the common directory. By selecting the Browse button, it
is possible to supply a database from any location accessible by the computer.

If a PFNetServer module is in used, the “Direct Connect IP” is used to define the IP address of
the PFNetServer add-on board of the drive. This is a future enhancement which will allow direct
connection to the drive. With the use of the PFNetServer, pressing the “Upload Data” button will
upload all of the reports from the drive, using the defined names and store them in the common
directory.

Once you have all the data defined, you are now ready to analyze the ‘Black Box’ data collected
from the drive. Press OK.

4
 Figure 2

View

The view menu allows the individual data files to be viewed. Although most of these files can be
viewed as an ASCII file or within Excel, some files (ie. the Event History) contain encoded data in
order to conserve memory within the drive and can only be easily decoded using this program.

Event History
The following Figure 3 shows a typical Event History window.

Each event that is captured within the drive is time stamped. Some of the events have
supplementary data associated with the event. Selecting the event as shown in the
example will decode the supplementary data and display it in the right hand pane of the
dialog.

As different events are selected, the supplementary data changes. In particular for the
Drive Faulted event (reference Figure 4), the dialog provides a means to correlate this
event to the data captured within the “Control Data”. Pressing the “Details” button will
search for captured data that correlates to this fault (if it is available) and opens the
corresponding view for that data. It will also open the Alarm Queue window and mark the
associated fault with an Orange banner mark both in the Alarm Queue and the Event
Log. (Refer to Marks and Searching later in this document).

5
 Note that only a single view window of each type can be open at once. Ie. You cannot
have two Alarm Queue views open at once.

Figure 3 - Event History

Figure 4 – Drive Faulted Event

Alarm Queue
A typical Alarm Queue view is shown in Figure 5. The Alarm Queue displayed here,
differs from the Queues displayed on the drive terminal in that this queue cannot be
cleared and is much larger. It is an accumulation of all alarms (faults and warnings) that
have occurred within the drive.

6
 Figure 5

Control Data
The Control Data view in Figure 6 shows the data that was captured in the drive during
the last number of triggered conditions. The number of buffers and the dimensions of
these buffers is a function of the drive software to which this software will adapt based on
the given information within the binary file.

Figure 6

7
 It should be noted that the Control Data is not necessarily triggered on only a Fault within
the drive. Its trigger conditions can be any event that Development decides is necessary
to capture data on.

Each buffer is time stamped. This can be correlated to other events and alarms. The
FRN value defines the firmware for which this capture applies. The Export feature is
used to open the data within an Excel spreadsheet (given that the version of Excel is
available on the PC). Excel is to be used for the purpose of plotting the captured data
and more flexible analyzes of the captured data. By default only the current Buffer is
exported. Selecting the “Export all Buffers” will open a sheet for each buffer within Excel.

Selecting a row and then selecting a column header will give detailed information about
that data point if the database is available to provide the detailed information typical of
that shown in Figure 7. Note that the control data can capture internal variables that are
not defined in the database. Additional information for these variables are not available.

Figure 7 – Detailed Control Data

Trend Capture
The view typical of Figure 8 shows the data which was captured by the normal trending
feature of the drive. If the drive has the Extended trending enabled, this view will show
the complete 1000 sample data, whereas the terminal is only capable of showing 100
samples around the trigger point.

8
 Figure 8 – Trend View

Parameters
The Parameters View typical of Figure 9 shows all of the parameters, ie. those that can
be written to in order to configure the drive operation.

Figure 9 – Parameters View

The data can be sorted by “Group”, “ID Code” or “Name”. To select, the data, click on
the column header you wish to sort by.

Variables
The Variables View in Figure 10 shows the runtime variables as they were at the time
the file was uploaded.

9
 Figure 10 – Variables View

The data can be sorted by “Group”, “ID Code” or “Name”. To select, the data, click on
the column header you wish to sort by.

Revision Levels

The Revision Levels view shown in Figure 11 gives the revision details of all major
firmware components within the drive.

Figure 11 – Revision Levels

10
Marks & Searching

All of the Views and Dialogs which display data have the capability of “Marking” a row of data to
make it visibly easier to locate. A mark menu is accessible by using the Right Click of the Mouse.

Place the mouse on the row you wish to mark, click the right mouse button and select from the
menu shown in Figure 12.

Figure 12

a) ‘Mark’ – places a Yellow banner on the selected row.

b) “UnMark’ – removes any marking banner (of any colour) from the selected row.

c) “UnMark All’ – removes all marking banners from the view.

In addition to “Marking”, some of the views have the capability of searching for data within the
current view. The “Search” menu, if available is also part of the right mouse click menu as shown
in Figure 13.

Figure 13

The search feature is context sensitive depending on the column you have the mouse on when
you select the Search menu. For example, if you have the mouse on the Date or Time column,
the search will be for a given Time stamp. If the mouse is on the Event or Alarm data columns,
the search will be for the respective Event or Alarm.

When search is selected, a dialog box typical of Figure 14 is shown, giving the Search item based
on the current cell contents. The user is free to change the text as required. Pressing Enter will
perform the search.

For Alarms, note that in the shown example, the search will be for Fault Codes 269. If “W269”
had been entered the search would be for a warning 269. Searching for “269” will look for either.

11
Figure 14 – Typical Search Dialog

Once an initial Search has been performed, ‘Search Next’ will find the next item from the mouse
position, towards the end of the list, wrapping around if necessary.

The ‘Search Next’ feature can also be applied to another view. For example if searching for a
time on the event view, ‘Search Next’ can be used to search for the same time on the Alarm
Queue view.

‘Search Highlight’ will mark all rows within the view with a Green banner, if they match the given
search criteria. The marking can be removed with ‘UnMark’ or ‘UnMark All’.

12
Analyze

The Analyze feature is accessed under the File menu. It is an initial attempt at automating some
of the analysis of the captured data. The analysis starts with the Event view.

Selecting an event such as the Drive Faulted event will bring up additional information about that
event. Selecting details for the event will attempt to find the captured control data associated with
this fault event.

Selecting a row number and then clicking on the column header, ie. InvControlFlag will give
detailed information about the selected value, such as shown below. This information is only
available if a valid database file has been provided during the setup phase, and only for data that
is accessible from the database. Values which are internal to the drive only, cannot be decoded
by this firmware as there is no reference to them within the database.

13
The Close selection from the File menu, closes all analyzer windows which are currently open.
This must be done prior to opening the same windows with the View menu selection.

Merge

A Merge function combines the Event Log and Alarm Queue together based on the time stamp as
shown in Figure 15. Use the File-Print selection from the menu to print this merged document.

Figure 15 - Merge

14
The “Marks and Searching” features apply to the Merge window.

The Close selection from the File menu, closes all Merge windows which are currently open. This
must be done prior to opening the same windows with the View menu selection.

15
Uploading Data via Hyperterminal

The data which will be used by this program must be uploaded from the drive and placed into a
common directory. This is accomplished by using HyperTerminal connected to the “Data Port” of
the DPM. (Refer to …….. for detailed instructions on the use of this port).

Once connected, the following screen will be shown.

Figure 16

When uploading data from the drive, the data will be in the specified format as indicated by the
suggested file extension (ie. .csv or .bin). It is recommended that you use these extension names
to avoid confusion.

As well, the suggested names for the files are as shown in the following table. You are however
free to use whatever name you wish, but you will have to add these names to the “Filenames-
Setup” in order to use them within the program.

Analyzer Upload Recommended

DataFile Option # Filename

Event Log 1 events.csv

Alarms 2 alarms.csv

ETrend 3 trend.csv

Control Data 4 control.bin

Parameters 5 parameters.csv

16
 Variables 6 variables.csv

Revisions 7 revlevels.csv

Option 8 data is not required.

17