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

Lenze · PLC Designer | Migration of V2.x projects · 1.2 EN - 02/2013
23
Update of a project from V2.x to V3.x
Import of the example project into the »PLC Designer« V3.x
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
5. Recreate control configuration.
This means the following for this example:
• Insert dummy axes as virtual axes below the available node L-force Motion General Drive Pool.
• Insert CAN bus, adapt baud rate
• Insert CANopen manager
• Insert devices
• Adapt device settings (e.g. names, node number, basic configuration, mapping, PDO features).

Note!
Libraries
Device-internal and fieldbus-internal libraries are automatically available after the
import of the »PLC Designer« V2 project. No manual update of the libraries required!
Control configuration
When a V2 project is imported into V3, the control configuration gets lost. Thus, it has to
be recreated in the »PLC Designer« V3.
Logic and Motion devices
• When the system is installed, we recommend to connect the Logic and Motion devices
to separate phases!
• Separate bus phases for Logic and Motion devices are not mandatory in the »PLC
Designer« V3 (in contrast to the »PLC Designer« V2.3) .

More information on the bus-specific configuration can be found in the following
documentation:
• Controller-based Automation EtherCAT communication manual
• Controller-based Automation CANopen communication manual
• Controller-based Automation PROFIBUS communication manual