Pulse

SCADA/HMI
P-CIM to Pulse Migration

JANUARY 2013

Copyright
The information in this document is subject to change without prior notice and does
not represent a commitment on the part of AFCON Control and Automation LTD.,
AFCON Software and Electronics Division.
No part of this document may be used or reproduced in any manner whatsoever
without written permission from AFCON Control and Automation LTD., AFCON
Software and Electronics Division.
The software described in this document is furnished under a license agreement or
a non-disclosure agreement.
The software may be used or copied only in accordance with the terms of the
agreement. It is against the law to copy this software on any other medium for any
purpose other than the purchaser's personal use.
Copyright 2012 AFCON Control and Automation LTD., AFCON Software and
Electronics Division.
All rights reserved.

Pulse logos are registered trademarks of AFCON Control and Automation LTD.,
AFCON Software and Electronics Division.
Windows is a registered trademark of Microsoft Corporation in the United States
and other countries.

Disclaimer
ANTLR Notification and License Agreement (Legal Commitment)
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Project Migration
In Pulse, you can work in projects that were created and stored in any version of P-CIM
7.70 and higher. The migration process includes the following topics:

Migrating a P-CIM 7.70 (and Higher) Project to a Pulse Project

The Project Migration Wizard

Important Notes
If your P-CIM project includes dBASE (dbf) data, perform the following steps before
starting to back up the project in P-CIM.
1

Make sure that the following files are located in the P-CIM projects Dailylog folder
(if not, copy and paste them there):
ALARMDAT.DBF, ALARMDAT.MDX, ALARMMAP.DBF, ALARMMAP.MDX,
ALARMCMD.DBF (in some cases), pfwaldef.ini

In the pfwaldef.ini file, go to the [AlarmWinDBF] sections

DbfCollectionPathName parameter and remove the path value (you can do this
in the INI File Editor).

Cells from P-CIM do not retain their cell definitions after the migration. Instead, the
cells objects are converted independently with their individual properties.

Graphic text objects from P-CIM do not retain their Background properties after the
migration.

Graphic path objects may become misshaped during the migration.

Migrated projects and display names may not be larger than eight characters.

When migrating a P-CIM 7.70 project to Pulse, the project name and the display names
cannot be longer than eight characters. After the project has been restored to Pulse
format, you can assign or modify project and display names with more than eight
characters.

P-CIM Cell is not migrated to Pulse as a single unit.

Cells from P-CIM do not retain their cell definitions after the migration to Pulse. Instead,
the cells objects are converted independently with their individual properties.

To migrate from P-CIM to Pulse on 64 bit operating systems, see Migrating a P-CIM
Application to Pulse on 64 bit Operating Systems on page 87.

The drivers used in the project should be updated to the latest available version after
migrating from P-CIM to Pulse.
After migrating from P-CIM to Pulse, it is highly recommended to update the drivers
used in the project.
Check for the latest available version of the drivers from the AFCON DVD or from the
AFCON website.

Pulse 2.0 User Guide

Migrating a P-CIM 7.70 (and Higher) Project to a Pulse Project

Before starting the migration process, you must back up the P-CIM project.
1

With P-CIM running, open the P-CIM Setup and click Backup Project.

Select the project and the target backup folder and then click Create Backup.

After completing the Backup operation, shut down P-CIM.

From the AFCON Pulse group menu, point to Pulse Setup and then click Project. After
the Project Setup opens, close the window (this changes the active AFCON application
on the computer to Pulse).

To restore the backed up file to Pulse, browse to the backup folder created in step 2
and click setup.exe.

The following message states the P-CIM product source version (7.70 and higher) and
the Pulse product target version (8.00 and higher). Click Yes to continue.

A message may ask if you want to set the restored project as the default project in
Pulse. If you do, click Yes. Otherwise, click No.

If the project is already existing in the Pulse target version, select whether to replace
the existing project or to restore the project as a new one in Pulse.
The restore process finishes.

Now, continue the Migration process by running the Migration Wizard (see The Project
Migration Wizard below.

Migrating a P-CIM Application to Pulse on 64 bit Operating Systems

A migration failure occurs when a P-CIM application migrates to Pulse on 64 bit
operating systems.

To migrate a P-CIM application to Pulse on 64 bit operating systems

1 First migrate the P-CIM application on a 32 bit operating system.
2 Backup the project in Pulse.
3 Restore the project in Pulse on a 64 bit operating system.

Pulse 2.0 User Guide

The Project Migration Wizard

The Project Migration Wizard guides you through the process of migrating a P-CIM v7.70
(or higher) project into a Pulse project.
NOTE

A project that was saved in Pulse format cannot be opened in P-CIM.

To migrate a P-CIM project to Pulse format

1

In the AFCON Pulse Program Groups Tools folder, double-click the Project
Migration Wizard icon to open the Project Migration Wizard.

NOTE

At any time, click Migrate to start the migration process at that point, without
further configuration.

Click Next to start configuring the migration.

To preserve the projects P-CIM files, save the backed up project before performing the
conversion to Pulse. Enter a location to save the backed-up files. If you select No, the
Migration utility creates project files in Pulse format but discards the backed-up P-CIM
files. Click Next to continue.

Pulse 2.0 User Guide

Select displays and configuration items to remain in the project as it migrates. By

default, all items are selected. Click Next to continue.

Review the summary of the pending migration process. To change something, click
Previous to return to previous pages. Click Migrate to continue.

Pulse 2.0 User Guide

The Wizard displays the progress of the migration.

When the migration is complete, a report appears in the Wizard. The report shows if the
items converted successfully into a Pulse project, and if errors occurred.

Pulse 2.0 User Guide

Perform the following options, if your migration process requires. Then, click Finish to
close the Migration Wizard.
Start All Services

During the migration process, some of the Pulse services

started, but not all of them. Select this option to start the rest
of all Pulse services and start the Pulse Server automatically.
If you do not select this option (default), you must start the
Pulse Server using the AFCON Pulse Startup command.

Export to HTML

Pulse 2.0 User Guide

Generate the Migration report to HTML format, which enables

you to view and print it from Internet Explorer.

Project Migration Error and Warning Codes

The following table lists the migration error codes with their descriptions.
Table 1: Error Codes

Description

Error
Code

The ActiveX property element [SymbolName] is missing its properties.

-1

The ActiveX property element [SymbolName] has an exception message.

-2

LoadAlarmClassActionData exception message

-3

UpdateAlarmClassDBTable exception message

-4

ConvertCommandsToWorkflows exception message

-5

ConvertActionToWorkflow exception message

-6

The display conversion StartUpAction failed.

-7

The display conversion ShutdownAction failed.

-8

DisplayConverter.Convert exception message

-9

An exception message about the conversion of Trend groups to resource

failure

-10

An exception message about the Trend Group parsing failure

-11

An exception message about the conversion of Trend group display failure

-12

An exception message about the conversion of the group file [filePath] to

the resource key [keyName] value [groupValue] failure

-13

An exception message about the conversion failure of display groups

-14

An exception message about the failure to create the default resource for
a display

-15

The list box item has the wrong number of parameters

-16

ConvertToSelectionBox exception message

-17

CreateSelectionBoxDisplay exception message

-18

The conversion of the workstation startup action failed.

-19

The conversion of the workstation shutDownAction failed.

-20

The conversion of the workstation idleAction failed.

-21

The duplicate AutoAction [keyName] was removed.

-22

WorkStationTriggerConverter.Convert exception message

-23

ActiveX could not be loaded.

-24

The TrendPropertyConverter failed to save the curve file.

-25

The TrendPropertyConverter has an invalid TrendPen P-CIM item.

-26

Pulse 2.0 User Guide

Description

Error
Code

The TrendPropertyConverter has an invalid AxisX P-CIM item.

-27

The Element [ElementName] @ contains \ in the expression or in

aliases. A parsing failure is possible.
Use \\ or GetAlias() to overcome the error.

-28

The DBFTagConvertor.ConvertDataSheetTag ElementName failed to

create a new DBF user DSN.

-29

The DBFTagConvertor.ConvertDataSheetTag ElementName has an invalid

topic format or an invalid number of parameters.

-30

The DBFTagConvertor.ConvertDataSheetTag ElementName has a query

range with invalid DBF range functions.

-31

The DBFTagConvertor.ConvertDataSheetTag ElementName failed to

create a new DBF user DSN.

-32

The DBFTagConvertor.ConvertDataSheetTag ElementName failed to save

the new Datasheet Tag item.

-33

DBFTagConvertor.ConvertDataSheetTag ElementName [ElementName]

exception message

-34

The INITagConvertor.ConvertDataSheetTag ElementName has an invalid

topic format or an invalid number of parameters.

-35

The INITagConvertor.ConvertDataSheetTag ElementName failed to save

the new Datasheet Tag item.

-36

The ODBCTagConvertor.ConvertDataSheetTag ElementName has an

invalid topic format or an invalid number of parameters.

-37

The ODBCTagConvertor.ConvertDataSheetTag ElementName has an

external SQL query file not in INI format that cannot be converted.

-38

The ODBCTagConvertor.ConvertDataSheetTag ElementName failed to

save the new Datasheet Tag item.

-39

ODBCTagConvertor.ConvertDataSheetTag ElementName [ElementName]

exception message

-40

The TXTTagConvertor.ConvertDataSheetTag ElementName has an invalid

topic format or an invalid number of parameters.

-41

The TXTTagConvertor.ConvertDataSheetTag ElementName failed to save

the new Datasheet Tag item.

-42

TXTTagConvertor.ConvertDataSheetTag ElementName [ElementName]

exception message

-43

The Save action failed. The user did not allow to override the existing
display on the server.

-44

The server is not running. The migration process was aborted.

-45

The Save operation failed; the operation was cancelled by the user.

-46

The Save operation failed; reading the UPD file failed.

-47

DisplayMigration.ConvertDisplay exception message

-48

Pulse 2.0 User Guide

Description

Error
Code

The Save [saveResult] ToString() failed.

-49

Converting of {0} failed [result] exception message

-50

AddExtendedPropertyToElement [type.Name] exception message

-51

Invalid UPD file

-52

OldDisplay.Parse exception message

-53

ReadAnimation exception message

-54

The conversion from [oldDisplayVersion] version to Version 7.5 timeout

[messOut] expired.

-55

The conversion of the display in compact mode to Version 7.5 failed with
code.

-56

The conversion from [oldDisplayVersion] version to Version 7.5 failed with

code.

-57

The [Environment.NewLine] allFile files could not be moved.

-58

The database conversion process failed.

-59

The Pulse services failed to start. The migration process cannot be

initialized.

-60

The alarm class actions in the database failed to migrate.

-61

The conversion of alarm conditions to workflows failed.

-62

MigrationEngineProccess exception message

-62

The ActiveX [ObjName] static properties were not converted.

-63

The DBFTagConvertor.ConvertDataSheetTag ElementName - {0} DBF file

path is invalid.

-64

An AlarmConverter.ConvertAlarm ElementName [ElementName]

exception message

-65

UpdateProjectLocalization exception message

-66

The DBFTagConvertor.ConvertDataSheetTag ElementName

[ElementName] query range has invalid DBF range functions.

-67

Pulse 2.0 User Guide

The following table lists the migration warning codes with their descriptions.
Table 2: Warning Codes

Description

Warning
Code

The object [oldObject.GetName] contains both slider and position

animations. The definitions of the Slider and/or Position offsets may need
manual corrections.

The object named [objectName] Flip or Rotate properties will not be

migrated properly.

The object named [objectName] Flip properties will not be migrated

properly.

The INITagConvertor.ConvertDataSheetTag ElementName -{0} dynamic

parameters ({1}) were added to DisplayOpenAction.

The DisplayMigration.ConvertDisplay old display name [displayName] will

be converted to [newDisplayName].

The Color Animation Digital Alarm Property of the Object

[newObjectName] was converted to a Digital value.
For the Color Animation Alarm type, the item must be a Database Block.

The AlarmConverter.ConvertAlarm ElementName [ElementName] has an

invalid item format.

The display [newDisplay.DisplayName] with a Single Border frame type

is migrated to Border Style None.

The display [newDisplay.DisplayName] with frame type Double Border is

migrated to Border Style None.

The TrendPropertyConverter [trend.GetType().ToString()]

[trendProperty.SymbolName] has an invalid BatchProperty P-CIM item.

10

The Group composite cannot be in a negative location and be larger than

the display.

11

xxx was renamed due to an illegal or duplicate name.

12

The AlarmConverter.ConvertAlarm ElementName [ElementName] could

not find the new branch index by old branch levels.

13

The ODBCTagConvertor.ConvertDataSheetTag ElementName

[ElementName] dynamic parameters [dynamicActions] were added to
DisplayOpenAction.

14

P-CIM AutoActions were converted to Server AutoActions. Go to the

Server AutoActions Manager and go to Operator Personalization
AutoAction and remove irrelevant actions.

15

The Object [symbolID] with line ends might need slight repositioning.

16

The TXTTagConvertor.ConvertDataSheetTag ElementName

[ElementName] dynamic parameters [dynamicActions] were added to
DisplayOpenAction.

17

Pulse 2.0 User Guide

10

Description

Warning
Code

The element with Symbol ID [ElementName] Login Null Null was

converted to Login null null.

18

The element with Symbol ID [ElementName] @ with the internal path

C:\PCIM32 was converted to alias &PcimPath&. Verify that the complete
path is correct.

19

The background color of the label named '{0}' was lost during conversion.

20

The Path object [newPath.Name] might need a slight repositioning.

21

The Pie object [newPie.Name] might need a slight repositioning.

22

The Extended properties Height Slider property will override the Height
Position property.

23

The EndDot line cap type is not supported by the Pulse graphical engine
and will be converted to RoundAnchor.

24

The EndOpenDelta line cap type is not supported by the Pulse graphical
engine and will be converted to SquareAnchor.

25

The EndDelta line cap type is not supported by the Pulse graphical engine
and will be converted to SquareAnchor.

26

The EndTick line cap type is not supported by the Pulse graphical engine
and will be converted to SquareAnchor.

27

The Cell {0} definitions were removed. The Cell content was saved and
embedded in a display as objects.

28

The DBFTagConvertor.ConvertDataSheetTag element name

[ElementName] dynamic parameters [dynamicActions] were added to
DisplayOpenAction.

29

The EndArrowStop line cap type is not supported by the Pulse graphical
engine and will be converted to ArrowAnchor.

30

The EndSquareDot line cap type is not supported by the Pulse graphical
engine and will be converted to SquareAnchor.

31

The EndSquare line cap type is not supported by the Pulse graphical
engine and will be converted to SquareAnchor.

32

The [oldObject.GetName] object contains both slider and position

animations. The definitions of the Slider and/or Position offsets may need
manual corrections.

33

The element with Symbol ID [ElementName] |!$login was converted to

GDisplay|Pcim!Username.

34

The Advised item Gdisplay|Pcim!RecipeBusy is dismissed.

35

The Advised item Gdisplay|Pcim!ToolBar and the Pulse Action toolbar

[toolbar-name] are not supported.

36

The Advised item Gdisplay|Pcim!StatusF4 is not supported.

37

The Advised item Gdisplay|Pcim!ReportBusy is dismissed.

38

The Extended properties WidthSliderProperty will override the

WidthPositionProperty.

39

Pulse 2.0 User Guide

11

Description
The object [oldObject.GetName] Orientation Animation pivot location
cannot be properly migrated and it requires manual correction.

Pulse 2.0 User Guide

Warning
Code
40

12