User Instructions: SE PowerFlex 525 Faceplates

2/26/2018 Rev 1.1

The " SE_PowerFlex525_Faceplate_Files " files allow you to quickly load, configure, and use preconfigured
status, control and diagnostic displays or "faceplates" for the PowerFlex 525 drives using FTView Site
Edition.

The example below shows a PowerFlex drive template object that may be added to a specific system
display. The template object can be configured to launch the on-top display or "faceplate" for the particular
PowerFlex drive it represents. The faceplate includes status, control, and diagnostic views controlled by its
own toolbar buttons

Example of a template used to launch a PowerFlex drive faceplate

1
System Compatibility
The faceplate and add-on instruction files are compatible with:
Studio5000 V24 or later
FTView Site Edition9.0 or later.

NOTE: These instructions are for PowerFlex 525 drive communicating over EtherNet/IP only.

General Setup
1) After downloading your file, the following folder will be created: “SE_PowerFlex525_Faceplate_Files”.
The sub folder with the same name will contain the PowerFlex faceplate, AOI and parameter files.
The other, called “SE_PowerFlex_Button_Templates”, will contain the templates for the PowerFlex
drives and images that can be used on your display.

Logix Configuration

1) Open existing Logix file with RSLogix5000

2) Update PowerFlex 525 Add-On Profiles

The PowerFlex 5 2 5 Add-On Profiles are independent of RSLogix5000 software releases. Update
your
PowerFlex 525 Add-On Profiles to make sure your application runs
correctly.

Add-On profiles are available for download at the RSLogix5000 Add-On Profiles website:
https://download.rockwellautomation.com/esd/download.aspx?downloadid=addonprofiles

Follow these steps to download PowerFlex Add-On profiles.

Login to the RSLogix 5000 Add-On Profiles website. The RSLogix 5000 Add-On Profiles dialog box
opens.

2
 a. Find the AOP for PowerFlex 525 and download.

b. Click the Add-On Profile icon and follow instructions.

3) Add and configure the PowerFlex modules

a. Under I/O Configuration, right click network communication module for the intended
PowerFlex drive and select “New Module”.

b. Open the Drives folder and select PowerFlex 525 Drive module and select OK.

c. Enter a distinct module name and IP Address

3
d. Select the “Change…” button and enter the following *Default DataLink Module Definitions for
Monitoring & Diagnostic Data used in PowerFlex faceplate & AOI. Click OK when complete.

e. Setting other PowerFlex parameters:

PowerFlex parameter settings are very specific to your application and should be reviewed
carefully before running your drive application. The following parameter settings must be applied
for general Ethernet/IP communications for the PowerFlex faceplates to operate correctly.

From the “Drive” tab of the PowerFlex Module Properties, open the Parameter List and set the
following parameters:

4
For PowerFiex 525 set parameters 46 & 47 to Ethernet/IP as shown:

t tll i'J
" ...
Units Internal Value Default
Name

Downol ad Upol ad ADC

41 Accel Time 1
42 Decel Time 1
43 Minimum Freq
44 M aximum Freq

Oigln TrmBik
5 O·lfN input
5 ElherNei/IP
Powonl_ '\ Speed Reference3 9 EtherNei/IP
51
52 Average kWh Cost 0 0.00

1 P 110V .50HP 53 Reset To Defalts 0 Ready/Idle

62 Digln TermBki 02 Logic In 2 25 2.Wire FWD v

525 I add+ I
<I >I

Status: Offline OK II I Cancel II Apply II Help

Filter Value:

Download Upload
t tll
ADC
L
Value Units InternalValue Default
0.00 Sec 0 10.00
0.00 Sec 0 10.00

O·lfN input 5 O·l fN input

EtherNeiiiP 5 EtherNei/IP
MOP 9 EtherNei/IP
0.00 0 0.00

1 P 1 ·ov .50HP Ready/Idle 0 Ready/Idle

Logic In 2 25 2.WireFWD v

0 PowerFei x 525 I add+ J

<I >I

Status: Ofllne OK II I Cancel II Apply II Help

5
4) Save and download your project.

5) Correlate the online drive.

1. In the treeview under I/O Configuration, right-click on the drive profile (for this example “PowerFlex 525-
EENET PowerFlex_52X_Drive”) and select Properties.

2. Select the Drive tab to begin the correlation process.

After the drive configuration data has been verified, the Drive tab will display a request to synchronize the
configuration with the drive. Click Accept.
If the Differences Found Screen appears—which is typical, click Download. This will download the project
settings from the controller to the drive. If Upload is clicked, the drive settings are uploaded to the
controller.

3. The Drive tab displays the current status of the drive.

6
When the drive download completes successfully, the drive status indicates “Connected”, highlighted in
green.

4. Click OK to close the Module Properties window for the drive.

6) Import the PowerFlex AOI file for the drive you are using, (i.e. PFlex_525_AOI file).

a. In the System tree, right click on Add-On Instructions and select “Import Add_on Instruction”.
The Import Add-on Instruction dialog appears.

7
b. Browse to the “SE_PowerFlex_Faceplate Files” folder and select the AOI.

c. Click Import button to complete import operation.

Note: If you create multiple PowerFlex Module Definitions for the same type of drive (i.e. PF 70) with
unique datalink definitions, you will also have to create unique AOIs with unique names for those modules
as well.

7) Reassign the Input and Output parameter Data Types in the AOI for your configured drive. a. In the
project file Explorer window, expand the Add-On Instructions folder.

8
b. Select the appropriate PowerFlex AOI file you are using and double-click Parameters and Local Tags.

c. Scroll to and select the Inp_PowerFlex_525 AOI tag and click next to the data type field .The
Select Data Type dialog box opens.

d. Browse to the Input Data Type that matches the PowerFlex Module Data Type that was
created when you configured the drive in Step 3.

It should have a name similar to the drive you configured, for example, AB:PowerFlex525_xxxxxxx:I:x.

IMPORTANT: If multiple changes to your PowerFlex Module definitions were made and saved, there will
be multiple Data Types listed for a particular type of drive, so be careful to match the Data Type you select
within the AOI file to the Data Type of the intended PowerFlex Module definition.

e. Click OK.

The Data Type field updates. This example shows a PowerFlex 525 input tag’s data type.

9
f. Select the Out_PowerFlex_525 AOI tag and click next to the data type field.
The Select Data Type dialog box opens.

g. Browse to the output data type that matches the PowerFlex Module Data Type that was created when
you configured the drive in Step 3.

h. It should have a name similar to the drive you configured, for example, AB:PowerFlex525_xxxxxxx:O:x.

Click OK.

10
The Data Type field updates. This example shows a PowerFlex 525 output tag’s data type.

j. Close Parameter and Local Tags when completed.

8) Drop the PowerFlex AOIs into your application Program Routines.

a. Open the intended program routine, create a rung, and the select the Add-On instruction tab. b. Select
the PowerFlex Add-On instruction (i.e. PFlex 525).

c. Assign a PowerFlex Data Type tag to the main AOI tag with the same name of the module you want to
control and monitor. (In this example "PF525"). Then right click the tag and Add PF525 tag with the
"PFlex_525_AOI Data Type as shown.
d. Select the module Input and Output Tags for the

12
AOI you previously configured. Be sure to save your application file, after additions are made.

e. Create a new tag “Fault_Msg” with data type Message.

f. Click message configuration icon next to Fault_Msg tag. The Message Configuration box opens.

13
g. Configuration of “Fault_Msg” instruction.

Select:

Service Type: Get Attribute Single

Class : 97, Instance : 4, Attribute :1

h. Create a new tag for destination, click on “New Tag” and name as “Fault_Code”
14
Click on datatype and select DINT. Click ok.

The message configuration settings for Fault_Msg should look like below.

j. Click on the communication tab and browse to the scanner with communication to PowerFlex 525 Drive .
Click OK.

15
h. Enter the Inp_Scaled_Speed_At_60Hz , the AOI will scale the drive input and output speed values
based on the value entered.

*Add the below rungs in the main routine along with the PF525_Faceplate_AOI or import the main
rotine.L5X

16
Fault_Code is the tag which was created in the Message output instruction. Move the Fault Code into the
“Last_Fault_code” tag of AOI.
To fetch the device status GSV instruction is used. Select:
Class Name : Module
Instance Name : Select the drive

Attribute Name: Entry Status

Dest. :Create a new tag Comm_Status with data type DINT.

17
After configuring GSV instruction it should look as below:

Comm_Status is moved to AOI .

18
9) Logic integration into your specific Logix application.

a. View Add-On Defined tags and Example Logix Code for integration into your specific Logix application.
i. Expand the Add-On Definition folder in the System tree and then expand your PowerFlex
Drive AOI. You can view Parameters and Local Tags to integrate into your application for Program control
of the PowerFlex Drives (i.e. Cmd_xxxxProg and Set_xxxxProg tags).

b. Important AOI Program and Operator Control transfer considerations:

The first three rungs of each AOI handle the transfer of control from the Logix program (Program Control)
to the faceplate (Operator Control). The two Operator Control rungs are shown below. It is important to
understand how these rungs operate so your desired program to operator and operator to program control
transfers are achieved.

19
For example the rungs shown above, enable the Operator Control of the intended PowerFlex Drive.
Command requests (Cmd) can be initiated from either the Logix Programs (ProgOperReq) or
FTViewME/SE PowerFlex Faceplate (OperOperReq).

A specific drive example:

To enable Operator Control for a drive associated with "Motor_1" AOI instance, a rung could be added to
the Logix MainRoutine with specific input conditions driving an output instruction with the tag name
"Motor_1.Cmd_ProgOperReq". Likewise, a pushbutton within an FTView ME/SE Faceplate could be
added with a value tag name of "#1.Cmd_OperOperReq" with the
#1 parameter for that faceplate display associated with "Motor_1" tag.
A “Motor_1.Cmd_ProgToOperPermissive” must also be included in the Logix Program to control whether
Program to Operator Control transfer requests are allowed or acted upon. A tag value of 1 permits the
associated control transfer requests. A value of 0 prevents the associated control transfer requests.

ATTENTION:
If an Xxxx.Cmd_ProgToOperPermissive tag is set to 1, the associated AOI is programmed to allow
a transfer from Program Control to Operator Control regardless of the current direction, speed, or
active status of the PowerFlex Drive. In addition, the AOI is programmed to transfer the current
Program Speed value "Xxxx.Set_SpeedProg" to the associated Operator Speed tag,
"Xxxx.Set_SpeedOper", creating a "bumpless" transfer
when a transfer from Program Control to Operator Control is executed. Therefore, if the PowerFlex
Drive is running at the time of a Program to Operator Control transition, the PowerFlex Drive will
continue to run at the most recent commanded Program Speed. If a different Program to Operator
Control transition is desired, then the status of the PowerFlex Drive and the Operator command
requests must be monitored and the appropriate Program commands must be issued before the
Xxxx.Cmd_ProgToOperPermissive is allowed. Therefore, it is very important that the status of the
PowerFlex Drive is monitored and appropriate Program commands, for the specific application, are
issued before the Xxxx.Cmd_ProgToOperPermissive tag is set, to insure a safe Program to
Operator Control transfer.

20
ATTENTION:
If an Xxxx.Cmd_OperToProgramPermissive tag is set to 1, the associated AOI is programmed to
allow a transfer from Operator Control to Program Control regardless of
the current direction, speed, or active status of the PowerFlex Drive. In addition, there is no logic
within the AOI that sets the “Set_SpeedProg” upon transfer to Program mode, so the PowerFlex
drive will assume the last commanded “Set_SpeedProg” speed value unless logic is programmed
outside of the AOI to set it to a different value. Therefore, it is very important that the status of the
PowerFlex Drive is monitored and appropriate Program commands, for the specific application, are
issued before the Xxxx.Cmd_OperToProgramPermissive tag is set, to insure a safe Operator to
Program Control transfer.

ATTENTION:
If The PowerFlex Drive is started in Operator Mode and the FTView ME /SE PowerFlex Faceplate is
closed while the PowerFlex Drive is running, the PowerFlex Drive will continue running at the
current Set_SpeedOper tag value. Therefore, it is very important to understand how this operation
affects the specific application and appropriate actions and safeguards are implemented.

ATTENTION:
There is no logic within the AOI that controls the minimum or maximum PowerFlex Commanded
Speed values sent to the specific drive. Therefore, it is very important to understand the
limitations of the motor connected to the specific drive and set the appropriate PowerFlex Drive
parameters and add additional Program logic if necessary.

21
FTView SE Configuration

1) Open your existing FTView SE application that you wish to add the PowerFlex 525 faceplates to.

2) Add the “PowerFlex_525_Faceplate.gfx” to your display.

a. Right-click on Displays, and select 'Add Component into Application'.

b. Browse to the SE_PowerFlex_Faceplate_Files folder and select the faceplate GFX file.

3) Add the faceplate parameter file your FTViewSE application.

a. Right-click on Parameters, and select 'Add component to application'.
b. Browse to the SE_PowerFlex_Faceplate_Files folder and select the PF_Parameter.par file and click
Open button. (Typically you would rename the parameter with a name that associates it with the intended
drive you wish to monitor and control.)

c. Now open the parameter that you just added and edit the parameter “tagname” to match your
application. The parameter “tagname” needs to include the RSLinx Enterprise “Device
21
Shortcut” name of your systems controller and the “Module Name” of the intended PowerFlex
Drive you wish to monitor and control.

Double-click on the faceplate parameter file, and edit the “Device Shortcut” name to match the Logix
controller that was previously configured in your RSLinx Enterprise Communication Setup, ie. CLX.

ii. Enter the desired “Module Name” of the PowerFlex drive you desire to monitor and control, ie. PF525,
which you previously configured in step 3b in the Logix Configuration section. Close and save changes.

4) Create the display navigation to open the PowerFlex Faceplate at runtime. (To use the PowerFlex
button templates, skip to pg 25, Configuration Steps for using the PowerFlex Button Templates.)
22
a. On a desired graphic display, create a button object over the graphic object that represents the
motor/drive you intend to monitor and control.
b. Double-click on the button object to display its properties and configure the Action tab. Click on the
browse (i.e. ellipses, ) button beside the Press Action field to launch the Command Wizard.
c. Select the Display command and click Next.

d. Use the browse buttons, drop down menus and the Parameter File checkbox to select the appropriate
area, display and parameter file name and click Finish.

e. The Display command syntax has now been configured and inserted into the Press Action field.

23
f. Configure the “Up Appearance” tag so that the Back style is transparent and any other remaining
properties if desired. Click OK.

24
Configuration Steps for using Pre-Created Goto Buttons

If you desire a hardware system view as shown below, a PowerFlex Drive object configured as a Goto
button that can launch individual PowerFlex faceplates, follow these instructions.

1) Add the PowerFlex bitmap images into your FTView application by right clicking onto the Image folder
in the system tree and choosing “Add Component into Application.”

2) Browse to your “SE_PowerFlex_Button_Templates” folder that was created in step 1 when you
unzipped the SE_PowerFlex_Faceplate_Files.zip file. Select the Bitmap image and click Open.

25
3) Next, add the PowerFlex Goto Displays files into your FTView Application by right clicking on the
Display folder in the system tree and by selecting “Add Component into Application.”

4) Browse to your “SE_PowerFlex_GotoButtons” folder and select the “Goto_PowerFlex.gfx” file. Click
Open. Verify the “Goto_PowerFlex” display appears under Displays in your system tree.

5) Double Click on the “Goto_PowerFlex” display

On the “General” tab, assign the PowerFlex Faceplate and parameter file to associate the button to.
a. Select the browse button along side of the Display field and assign the PowerFlex Faceplate display.

26
b.

Select the browse button along side of the Parameter file field and assign the PowerFlex parameter file.
Be sure to click the OK button of the Goto Display Button Properties dialog to save your configuration.

27
c. Under label select the Powerflex image .Click on OK.

6) Now, you can save and create a runtime file to test your display.

28