Lenze PLC Designer Migration PLC Designer (R2-x)-PLC Designer (R3-x) - Manual (Page 11)

Lenze · PLC Designer | Migration of V2.x projects · 1.2 EN - 02/2013
11
General information
Preparing PLC projects in the »PLC Designer« V2.x
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
5 General information
This chapter describes the alterations necessary for importing the projects created in the »PLC Desi-
gner« V2.x into the version V3.0.
5.1 Preparing PLC projects in the »PLC Designer« V2.x
Preconditions/requirements
In order to be able to import a PLC project from the »PLC Designer« V2.x to V3.x, the following pre-
conditions are required:
Libraries used in the project...
• must not have any references to external files
• must be able to be compiled.
 Convert libraries ( 21)
Precondition Information/example Remedy
It must be possible to compile the
project in the »PLC Designer« version
2.3 without any errors.
When an error-free »PLC Designer«
V2.x project is compiled, many war-
ning signals are displayed in the »PLC
Designer« V3.
These are implicit conversions where
information can get lost. (for in-
stance a sign reversal)
The warning signals must be evalua-
ted individually.
The initialisation of variables with
constants is checked more carefully
in the »PLC Designer« V3.x:
• Example: byte_var : BYTE :=
word_constant;
if V2.x no er-
ror is in the »PLC Designer« V2.x -
an error message is generated du-
ring the import to V3.
Correcting in the V2 project: Observe
correct type data.
In the »PLC Designer« V3.x, cases are
checked against the switch variable:
• CASE USINT OF INT is not che-
cked in the »PLC Designer« V2.x -
during the import into V3 an error
message is generated.
Correcting in the V2 project: Observe
correct type data in a case instruc-
tion.