Migrating PlantPAx Projects

from Library Version 1.x to Library Version 2.0

Migrating PlantPAx Projects from Library Version 1.x to Library Version 2.0............................................................1
HMI Update ................................................................................................................................................................2
XML Editing Procedure for Graphics Update .............................................................................................................5
Logix Update ............................................................................................................................................................ 15

HMI Update
All Graphic Symbols
Many of the Graphic Symbols have been resized and reorganized. Therefore, you will need to check all of your
displays and realign objects as needed.
Analog Input Graphic Symbols
The Analog Input Graphic symbols were moved to a new global object file (RA-BAS) P_AIn Graphics Library.
Furthermore, the graphics symbols GO_P_AInAdv and GO_P_AInDual have been deleted since the graphic
symbol GO_P_AIn now works with all P_AIn objects (including P_AInAdv, P_AInDual, and P_AInMulti).
There are two ways update the P_AIn objects in your application: 1) Use the FTView graphics editor to replace
objects one at a time or 2) export the graphics to XML files and edit the XML files to change the global object
references. Both methods are explained below.
Regardless of the method you choose, it is a good idea to back up your graphics files before you begin. You
should also document the CLX addresses each Analog Input object references.
1) Use the FTView Editor
After importing all of the new Images, Global Object Files, and Display Files; find all Broken Link Objects (they
will show up in graphics as a white box with a red X). For each broken link object that was an Analog Input,
delete the broken link object and replace it with one of the new P_AIn graphic symbols.
While this method does not require advanced technical skills, it could be time-consuming if there are a lot of
Analog Input graphic symbols in your application.
2) Edit the XML file
BEFORE importing any of the PlantPAx version 2 components, export each display that has Analog Input graphic
symbols to an XML file (note: the faceplates and help files do not need exported).
Changes using this method can be done relatively quickly; however, the developer should have experience with
importing/exporting XML files with FactoryTalk View as well as editing XML files.
The XML Editing Procedure is shown in the next major section of this document, below.
P_VSD Reverse Conveyor
The reverse conveyor Graphic Symbol was deleted from the P_VSD Graphics Library. Because direction symbols
were removed from all VSD objects, the Reverse Conveyor graphic symbol became redundant, as it was now the
same as the forward conveyor. The Reverse Conveyor graphic symbol must be replaced with the Forward
Conveyor graphic symbol. This can be done using the same methods described for the Analog Input Graphics
Symbols.

P_MotorRev Reverse Conveyor

The reverse conveyor Graphic Symbol was deleted from the P_MotorRev Graphics Library. Because direction
symbols were removed from all Reversing Motor objects, the Reverse Conveyor graphic symbol became
redundant, as it was now the same as the forward conveyor. The Reverse Conveyor graphic symbol must be
replaced with the Forward Conveyor graphic symbol. This can be done using the same methods described for
the Analog Input Graphics Symbols.
Mode Global Objects
Global objects for mode information and configuration have been moved to a new global object file (RA-BAS)
Process Mode Objects. This change will not affect your application if your application used standard Process
Library faceplates.
If you created custom faceplates using any of the following Global Objects from the file (RA-BAS) Process
Faceplate Objects, you must update your custom faceplates with the graphic symbols from (RA-BAS) Process
Mode Objects. This can be done using the same methods described for the Analog Input Graphics Symbols.

GO_ModeDisplay
GO_HMOPO_ReqModeDisplay
GO_MPO_ReqModeDisplay
GO_ModeButtons
GO_MtceModeButtons

Alarm Global Objects

Global objects for alarm information and configuration have been moved to a new global object file (RA-BAS)
Process Alarm Objects. This change will not affect your application if your application used standard Process
Library faceplates.
If you created custom faceplates using any of the following Global Objects from the file (RA-BAS) Process
Faceplate Objects, you must update your custom faceplates with the new graphic symbols from (RA-BAS)
Process Alarm Objects. This can be done using the same methods described for the Analog Input Graphics
Symbols.

GO_AlarmDisplay
GO_AlarmConfig
GO_MSI_AlarmState

Also, the Process Library faceplates now use a Reset / Acknowledge All button in place of the former Alarm
Reset button. The new Reset / Acknowledge All button can be found in the new global object file (RA-BAS)
Process Alarm Objects.

Built-In Instruction Graphic Symbols and Faceplates

The description and units entered as global object parameters for the Built-In instruction graphic symbols are
now passed to the faceplate. The description is displayed in the faceplate title bar and the units are displayed
on the home page.

Common Analog Edit (Numeric Data Entry Popup) and FM20.DLL

The numeric data entry popup display for the PlantPAx Library, (RA-BAS) Common-AnalogEdit.gfx, uses version
11.0.8000.0 of the Dynamic Link Library (DLL) FM20.DLL. This version of FM20.DLL is installed with FactoryTalk
View SE 6.0 if there is not a newer version already on the PC. If you have installed a recent edition of Microsoft
Office or some other application, your PC may have a newer version of this file.
If you have a newer version of the FM20.DLL file on the PC running the HMI client, you will receive a
FM20.DLL: never version used diagnostic message each time you call up the numeric data entry popup. The
popup will work correctly, and the message is a nuisance diagnostic. But if you want to avoid this message, do
the following:

Make sure each Client PC and the workstation with FactoryTalk View Studio all have the same version of
FM20.DLL. (By default it is in the C:\Windows\System32 folder.) If you need to copy the DLL from one
PC to another, be sure to COPY OVER the previous version. Do not rename or move the DLL before
copying over it.

Open the display (RA-BAS) Common-AnalogEdit in FactoryTalk View Studio. Select a graphic element
on the display (say, one button).

Place the mouse cursor over the selected graphic element, press the SHIFT key, and use an arrow key to
nudge the element one pixel. Release the SHIFT key.

Press the SHIFT key again and nudge the element back where it was. Release the SHIFT key.

Save the display file.

Modifying and saving the Common Analog Edit popup display links it to the version of FM20.DLL installed on the
PC where the change was made.
The next time you call up the data entry popup on the client, you should not receive the diagnostic message.
If you continue to have trouble with the data entry popup display, please contact Rockwell Automation
Technical Support for assistance. Remember to ask for PlantPAx support.

XML Editing Procedure for Graphics Update

1. Backup your HMI project using FTViews Application Manager.
2. If needed, update your PlantPAx version 1.x based project from FTView 5.x to FTView 6.0. See
FactoryTalk View Site Edition Installation Guide, PUBLICATION VIEWSE-IN003I-EN-E for detailed
instructions.
3. Export any display in your project to XML that contains Analog Input graphic symbols.
a. In FTViews Explorer window right click on Displays
b. Select Import and Export

c. Select Export graphic information from displays, and click Next >.

d. Select the displays to export and click Next >

e. Select the folder to export the graphic information to:

f.

Left click on the Finish button. The exporting window will open.

g. After exporting a Notepad window will open summarizing the export process.
NOTE: .bmp files will not be exported and are reported as an error. This will not affect the conversion and can
be ignored.
4. Open one of the exported XML files in a text editor (such as Wordpad.exe).
5. Search and replace the following (in the order specified):
a. Analog Input Graphic Symbols (P_AInAdv, P_AInDual, P_AIn)
Search for: (RA-BAS) Process Graphics Library.GO_P_AInAdv
Replace with: (RA-BAS) P_AIn Graphics Library.GO_P_AIn
Search for: (RA-BAS) Process Graphics Library.GO_P_AInDual
Replace with: (RA-BAS) P_AIn Graphics Library.GO_P_AIn
Search for: (RA-BAS) Process Graphics Library.GO_P_AIn
Replace with: (RA-BAS) P_AIn Graphics Library.GO_P_AIn

b. VSD Reverse Conveyor (P_VSD_ConveyorRt2Lt)

Search for: (RA-BAS) P_VSD Graphics Library.GO_P_VSD_ConveyorRt2Lt
Replace with: (RA-BAS) P_VSD Graphics Library.GO_P_VSD_ConveyorLt2Rt

c. Motor Reverse Conveyor (P_MotorRev_Conveyor_R1)

Search for: (RA-BAS) P_MotorRev Graphics Library.GO_P_MotorRev_Conveyor_R1
Replace with: (RA-BAS) P_MotorRev Graphics Library.GO_P_MotorRev_Conveyor_R

d. Mode Global Objects

Search for: (RA-BAS) Process Faceplate Objects.GO_ModeButtons
Replace with: (RA-BAS) Process Mode Objects.GO_ModeButtons
Search for: (RA-BAS) Process Faceplate Objects.GO_MtceModeButtons
Replace with: (RA-BAS) Process Mode Objects.GO_MtceModeButtons
Search for: (RA-BAS) Process Faceplate Objects.GO_ModeDisplay
Replace with: (RA-BAS) Process Mode Objects.GO_ModeDisplay
Search for: (RA-BAS) Process Faceplate Objects.GO_HMOPO_ReqModeDisplay
Replace with: (RA-BAS) Process Mode Objects.GO_HMOPO_ReqModeDisplay
Search for: (RA-BAS) Process Faceplate Objects.GO_MPO_ReqModeDisplay
Replace with: (RA-BAS) Process Mode Objects.GO_MPO_ReqModeDisplay

e. Alarm Global Objects

Search for: (RA-BAS) Process Faceplate Objects.GO_AlarmDisplay
Replace with: (RA-BAS) Process Alarm Objects.GO_AlarmDisplay
Search for: (RA-BAS) Process Faceplate Objects.GO_AlarmConfig
Replace with: (RA-BAS) Process Alarm Objects.GO_AlarmConfig
Search for: (RA-BAS) Process Faceplate Objects.GO_MSI_AlarmState
Replace with: (RA-BAS) Process Alarm Objects.GO_MSI_AlarmState

6. Save the XML file.

7. Repeat steps 3, 4, and 5 with the remaining XML files.
8. Add new Images into project
a. In FTViews Explorer window right click Images
b. Select Add Component Into Application

c. Browse to downloaded updates Images folder. (Usually \Graphics\FTView

SE\ProcessLibrary\Images.)
d. Select all image files:
i. Left clicking on the first file,
ii. Scroll to the last file,
iii. Hold the shift key,
iv. Left click the last file.
v. Select Open
NOTE: Some files may already exist. If asked to over-write existing files, select Yes to All.

e. Allow all files to be added.

9. Add new Global Objects into project
a. In FTViews Explorer window right click Global Objects
b. Select Add Component Into Application

c. Browse to downloaded updates Global Object folder. (Usually \Graphics\FTView

SE\ProcessLibrary\Global Objects.)
d. Select all Global Objects files:
i. Left clicking on the first file,
ii. Scroll to the last file,
iii. Hold the shift key,
iv. Left click the last file.
v. Select Open

NOTE: Some files may already exist. If asked to over-write existing files, select Yes to All.

e. Allow all files to be added.

10. Add new Displays into project
a. In FTViews Explorer window right click Displays
b. Select Add Component Into Application

c. Browse to downloaded updates Displaysfolder. (Usually \Graphics\FTView

SE\ProcessLibrary\GFX.)
d. Select all Display files that will be used in your application:
i. Left clicking on the first file,
ii. Scroll to the last file,
iii. Hold the shift key,
iv. Left click the last file.
v. Select Open

NOTE: Some files may already exist. If asked to over-write existing files, select Yes to All.

e. Allow all files to be added.

11. Import edited XML files into project
a. After having backed up your project in Step 1 above, delete the .gfx files you exported in Step 3
above.
i. In FTViews Explorer window, right click on the first display that was exported.
ii. Select Delete from the menu.

iii. Repeat Steps 11.a.i and 11.a.ii for each of the remaining displays exported in Step 1
above.
b. In FTViews Explorer window right click on Displays
c. Select Import and Export

d. Select Import graphic information from displays, and click Next.

e. Select No, and click Next >.

f.

Select the type of file to import: Multiple displays batch import file.

g. Select the multiple display batch import file.

NOTE: This file was created by the export. It is located in the folder you chose during the export procedure from
Step 3.e above. It is named: BatchImport_XYZ.xml where XYZ is the name of your project.

h. Select Create new object on the display and click Finish.

i.

The importing window will open.

12. Review imported displays to determine that graphic objects have been correctly referenced.

Logix Update
Back Up Your Project before Updating
Before starting the update procedure, go online with your controller and upload a copy of the application,
including current tag values, and save this copy in a safe place.

Version 18 or Later of RSLogix 5000 Required

Release 2.0 of the PlantPAx Library requires Version 18 or later of RSLogix 5000 Software and controller
firmware. If your controller project was developed in Version 16 or 17 of RSLogix 5000 software, you will need
to migrate forward to Version 18 or later before importing the PlantPAx Library 2.0 Add-On Instructions.

You will need to flash the controller to this same firmware Major Revision before you can download the updated
project to it. You can use the ControlFlash tool, or RSLogix 5000 will prompt you and flash the controller when
you attempt to download the project.

Update P_Alarm and P_Mode First

When importing library 2.0 Add-On Instructions into an existing 1.x application, import the P_Alarm and
P_Mode instructions first.
Many of the other Add-On Instructions use P_Alarm and/or P_Mode instances within them. In addition, the
Add-On Instructions for PlantPAx Library 2.0 are signed. The signature of a device instruction, such as P_Motor,
depends on the signed version of P_Alarm and P_Mode used within. When importing a device instruction,
P_Alarm and P_Mode can be pulled in as well, but that is not the default import behavior. If you import a device
instruction like P_Motor without also importing P_Alarm and P_Mode (or not having already imported them),
the signature will break and default values for new parameters will not be populated.
To avoid problems with missing values for new parameters, always import the updated P_Alarm 2.0 and
P_Mode 2.0 Add-On Instructions first; then import the rest of the PlantPAx Library 2.0 instructions.

Inf_Type Local Tag

A new Local Tag used in PlantPAx Library 2.0 Add-On Instructions is called Inf_Type it is a Local string Tag in
each instruction, and its value in every instruction instance must be set to the name of the instruction. So every
instance of P_AIn must have the Inf_Type Local Tag set to P_AIn.
This Local Tag is used for navigation. For example, the Analog Input Graphic Symbols use this Local Tag to know
which Faceplate display to open when clicked.
This Local Tag has the correct value stored automatically when each Version 2.0 instruction is imported, so long
as the instruction signature is not broken.
If you click on an analog input Graphic Symbol and get a display not found message, it is likely that the
Inf_Type value was not set (see above on updating P_Alarm and P_Mode first) and is empty (null string). There
are two ways to recover:
1) Go back to your backup copy of the RSLogix 5000 Project and do the import again, making sure to import
P_Alarm and P_Mode before importing any other Add-On Instructions. See the instructions above.
2) Open each PlantPAx Library instruction instance and type in the correct value of Inf_Type.

In RSLogix 5000 Software, open the application.

Open the routine containing the instruction instance you want to check and navigate to the instruction
instance.

Right-click on the instruction name (not the backing tag name) and select Open Instruction Logic.

Rung 0 of the instruction definition opens, with the data context set to the instruction instance (not the
definition). Rung 0 contains STRING instructions (that are jumped over, not executed) that display the
STRING data for the instance.

If the value of Inf_Type is missing or incorrect, double-click on the value to bring up the STRING entry
popup and enter the name of the instruction into the STRING.

L_CPU (Controller CPU Utilization) Instruction

The recommended procedure for handling the L_CPU instruction in an RSLogix 5000 project when upgrading to
PlantPAx Library 2.0 is as follows:

If you have not already done so, save the project and make a backup copy of the project file (.ACD).

Find the L_CPU instruction instance. One way to do this is to right-click on the L_CPU Add-On
Instruction in the Controller Organizer and select Cross Reference. Double-click on the instance in the
Cross Reference to go to the rung containing the instance.

Make note of the Controller slot number and the Task to be monitored in the MOV and GSV in the upper
branch of this rung.

Delete the rung.

In the Controller Organizer, double-click Controller Tags. Using the Tag Edit window, delete the
backing tag for the L_CPU instruction. This should be a Controller Tag named L_CPU.

In the Controller Organizer, delete the L_CPU Add-On Instruction definition.

o

If the Delete option is not enabled when you right-click on the L_CPU Add-On Instruction, not all
instances and backing tags have been deleted.

Import the new L_CPU_18, L_CPU_19 or L_CPU_20 Rung (as appropriate for your controller firmware
revision), making sure to create new or overwrite (not use existing) all the components, including
the Add-On Instruction definition, plus any data types, MSG backing tags and data tags.

Be sure to configure the controller slot number (in the MOV) and the Task to monitor (in the GSV, if not THIS)
on the upper branch of the rung before switching the controller to RUN.