Professional Documents
Culture Documents
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.
GO_ModeDisplay
GO_HMOPO_ReqModeDisplay
GO_MPO_ReqModeDisplay
GO_ModeButtons
GO_MtceModeButtons
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.
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.
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.
c. Select Export graphic information from displays, and click Next >.
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
NOTE: Some files may already exist. If asked to over-write existing files, select Yes to All.
NOTE: Some files may already exist. If asked to over-write existing files, select Yes to All.
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
f.
Select the type of file to import: Multiple displays batch import file.
i.
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.
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.
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.
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.
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.
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.