HI 800 317 AEA Conversion ELOP II V3.5 -> V4.

1 (0611)

Conversion of Projects
from ELOP II V3.5 to ELOP II V4.1

1 Overview
This document describes the conversion of an unchanged project. Modifications of
the project must be made in accordance with the safety manual (HI 800 013).

The consequences for safe operation depend on the application. The

operating company must check the code of the converted project
with the appropriate authorities!

The new version ELOP II V4.1 makes it possible to open ELOP II V3.5 projects and
convert them into the V4.1 format.

Note The conversion of a project from ELOP II V3.5 to ELOP II V4.1 is not
reversible!
Before archive your project in ELOP II V3.5.

1.1 Conversion of a Project only for “Online-Test” of ELOP II V4.1

The user may only convert a project from ELOP II V3.5 to ELOP II V4.1 without the
proceeding described in this document, if the converted code will not be loaded into
the H41q/H51q PES.
After the conversion of the project to ELOP II V4.1 the user can monitor the
H41q/H51q PES using the "Online-test" in ELOP II V4.1.
This conversion has no effect to the function of the H41q/H51q PES.

It is strongly recommended to avoid loading this converted version

into the H41q/H51q controller without the measures described in this
document.

1.2 Rules for the conversion

Upwards compatible only.
Projects can be converted without restriction.
Online test with converted projects is possible.
Reload with converted projects is possible.
Codeversion will change after the code generation in ELOP II V4.1, if the
ELOP II V3.5 project contains sequential function charts (SFC) or array vari-
ables.

All rights reserved. The technology is subject to changes without notice: 1/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

1.3 Consider the Rules when Converting from V3.0 to V3.5

If you want to convert projects created using an ELOP II version V3.0, you must first
convert the V3.0 project to ELOP II V3.5.
Please refer to the manual HI 800 106 "Instructions for conversion of user programs
from ELOP II-NT V 3.0 to ELOP II V3.5" for further information on conversion.

1.4 Changes in ELOP II V4.1

The following table provides an overview of the changes and effects that have to be
considered during the conversion of a project from ELOP II V3.5 to ELOP II V4.1.

Change Remarks
Standard function The function blocks that already existed in ELOP II V3.5
blocks from ELOP II will not cause any changes in the code.
V3.5
New The new function blocks did not exist in ELOP II V3.5.
Function blocks Therefore they cannot occur in those projects and will not
CTD_ANY_NUM, cause any changes in the code after the conversion to
CTU_ANY_NUM, ELOP II V4.1.
CTUD_ANY_NUM
Sequential function The order of creation of elements in sequential function
chart (SFC) charts (SFC) has been corrected.

Variable Type Array
Effect:
As a result the code version will change, if the V3.5 pro-
ject contains SFC elements.
This change does not have any effect on the functionality.
The processing sequence of the POUs (Logic) connected
to array variables has been corrected.

Effect:
As a result the code version will change, if array variables
are used in the V3.5 project.
This change may have effects on the functionality.
Warnings if using If feedback loops are used in the user program, then
feedback loops these are displayed in ELOP II V4.1 in the dialog "Error
in ELOP II V3.5 messages" of the code generator and saved in the file
"Program.ERR".

Effect:
The feedback loops in projects created with ELOP II V3.5
will not cause any changes in the code after the conver-
sion to ELOP II V4.1.

In ELOP II V3.5 this message was displayed in the "Error-

State Viewer”.
Please refer to the ELOP II Online help "Evaluation of
Feedback Loops” for further information about feedback
Loops.

All rights reserved. The technology is subject to changes without notice: 2/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

2 Conversion of a Project from V3.5 to V4.1

2.1 Preparing the Project for Conversion in ELOP II V3.5

Follow the steps to prepare the ELOP II V3.5 project for the conversion:

Open the project that should be converted in ELOP II V3.5.

Before activating the C code comparator in the resource properties, a generated
C code of each resource must be present. Generate code now, if no code for
these resources was generated.

Perform the following steps for each resource in your project:

Open the context menu of the resource and select Properties.
Select the tap Code generator.
Activate the following settings:
Start target code comparator
The target code comparator compares two target codes that are gener-
ated one after the other by the C compiler (GCC). This method prevents
errors caused by a non-safe PC.

Generate code image (for comparator)

Start code comparator
The C code comparator identifies modifications in the user program. As
resource for code image (C code (old)) select the same resource in the
same project.

Apply the settings with the button “Apply”.

Open the context menu of the Resource and select Code Generator
If the option “Create reloadable code” is set in the register "Code genera-
tor", then the reloadable code must be created for this resource as de-
scribed in the chapter 4. This may take place also afterwards after the con-
version on V4.1.

After you have finished the work on all resources select Project -> Close in the
menu to close the project.
Close ELOP II V3.5.

All rights reserved. The technology is subject to changes without notice: 3/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

2.2 Converting the Project from V3.5 to V4.1

Follow the steps to open and to convert your prepared ELOP II V3.5 project into a
V4.1 project:

Start ELOP II V4.1

Open the project that you have prepared in chapter 2.1.
Confirm the popup dialog with the button „OK“

In the menu bar select Tools->Error State Viewer and check whether the con-
version was successfully completed.

2.3 Comparing the Code Versions

Perform the following steps for each resource in your project:

Select a resource and start the code generator.

During the code generation, the code comparator window opens up and shows
the result of the code comparator.
In the dialog window “Code comparator” check if the Code version (hex.) has
changed.

If the code version has changed, an analysis of the change is re-

quired.

All rights reserved. The technology is subject to changes without notice: 4/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

2.3.1 Information about the code version

Whenever a user program is compiled, a code version is generated. The code ver-
sion is calculated by using a CRC32 polynomial. According to the statements of the
probability theory, the probability that a change of the application program generates
the same code version, is equal to the probability, that exactly one of 232 cases oc-
curs. This probability is equal to 2-32, what corresponds to approximately
2,328 ·10-10.
This probability is so low, that such an error does not need to be considered for the
creation of the code version of an application program and can be excluded.

2.3.2 The code version has not changed

If the code version did not change, then the code of the user program did no change
during the conversion.
Therefore you can use the code in ELOP II V4.1 without further examinations.

2.3.3 The code version has changed

Changes of a POU are displayed in the tab “POU” of the dialog window “Code com-
parator” and in the file „H5Cvgl.TXT“.
C: Change of the C code
D: Change of the data

2.3.3.1 Required test procedure

All changes shown in the code comparator must be tested.

To ensure the safe function of the generated code, each change has
to be completely tested. This means every place in the program (in-
stance and function blocks) where a POU with a changed code ver-
sion is used must be tested.

The test can also be carried out in a separate test system. This makes it possible to
test the changed code independently from the production system. After you have
successfully tested all changes, you can download the code with the reload func-
tionality into the system.

All rights reserved. The technology is subject to changes without notice: 5/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

3 Conversion aborted
If there are broken connectors, in an ELOP II V3.5 project then the conversion is
aborted. In order to convert the project nevertheless on V4.1, follow the following
steps:

Prepare the ELOP II V3.5 project for conversion to ELOP II V4.1 accordant to
the instructions in section 2.1.
Open the „ELOP II Control Center“.
Open the „Command Prompt“.
Enter the following command into the command prompt
LCConvVer –f –r –d –x [Path\Project] >Info.txt.
The option "- x" repairs critical errors during the conversion (e.g. broken Connec-
tors). Please refer to the ELOP II Control Center
Documentation->Tools Documentation for more information on the conversion
tool "LCConvVer".

If the ELOP II V3.5 project was successfully converted to ELOP II V4.1, the following
message appears in the command prompt:
"Information: LOE050: Conversion has been completed successfully"

To check the fixed errors follow the following steps:

Open the file „Info.txt“ and search for error messages.
In the file Info.txt the messages (error, status etc.) are stored, that are produced
during the conversion to ELOP II V4.1.

It is required to check all functions in the application program where

errors were repaired (e.g. broken connectors).

Compare the code versions and check the changes, as described in chapter 2.3.

All rights reserved. The technology is subject to changes without notice: 6/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl
HI 800 317 AEA Conversion ELOP II V3.5 -> V4.1 (0611)

4 Creating Reloadable Code

Problem: After changing the application program, a new code is generated and
loaded. If the code generator is started again – without any modifications, the sys-
tem is creating a new code version (modified CRC).

Note To ensure that the code version (CV) will not change after a program
modification and another reload, we recommend to generate and load
the code always twice.
After this, the code may be created as often as required (e.g. after
restoring it from an archive) without changing the code version.
See also chapter “Reload” in the operating system manual of the
H41q/H51q (HI 800 105)!

5 Support
If you experience problems or questions about the conversion, please contact the
HIMA Support.

Hotline +49 (0) 6202 709-255/ -258

or
Telefonisch : +49 (0) 6202 709-0
FAX : +49 (0) 6202 709-107
E-mail : info@hima.com

All rights reserved. The technology is subject to changes without notice: 7/7
HIMA Paul Hildebrandt GmbH + Co KG, Postfach 1261, D-68777 Bruehl