Control FPWIN GR/GR7 files (*.fpx) can be imported via . All PLC types are supported.
Program blocks
Program block encryption is not supported. All program blocks must be decrypted before importing. Encryption is only available for FP7 projects.
Unconverted program blocks or networks are not supported.
Comments
I/O comments, block comments, and remark comments can only be imported in one language (type 1). Comments in other languages (type 2 and type 3) will be discarded.
Instructions
Instructions for direct output (OT, WO) are not supported. Use the Control FPWIN Pro7 instruction FP_DIRECT_OUTPUT instead.
The total number of labels must be smaller than 65537.
The total number of subroutines must not exceed 65537.
The instructions STARTPG, STOPPG, GPB, PUSHIX, and POPIX are not supported. Because these instructions are FP7 instruction, only the import ofFP7 projects is affected.
ECALL, EFCALL, LCWT, and LCRD instructions may not be supported depending on the memory area used by the operand. An error occurs if Control FPWIN Pro7 requires a different memory area than the one used in Control FPWIN GR/GR7.
Configuration
In Control FPWIN GR/GR7, it is possible to protect FP7 projects with a password. In Control FPWIN Pro7, this is not possible. You can only protect the project when it has been downloaded to a PLC and you have set a password manually for the PLC afterwards. When importing a password-protected project, you will be asked to enter the administrator password.
Program blocks
Program blocks to be imported are handled depending on the option or property applied:
Program blocks set to Detarget This PB for Conversion: The program block is imported as an empty POU and is deactivated in the task list.
Program blocks set to Detarget This PB for Execution: The program block is imported as a POU, but is deactivated in the task list.
Program blocks with the property Set this PB to standby mode: The program block is imported as a POU, but is deactivated in the task list.
The original program block name may not be kept because different rules may apply in Control FPWIN Pro7 with regards to program block names and POU names.
Program blocks to be executed once after switching to RUN mode (initial execution type) are imported as functions (FUN). At the same time, an additional POU is generated to call the function.
Addresses
Address names are adapted to Control FPWIN Pro7 names, e.g. the timer set value register TS is imported as TSV.
Local addresses are not supported. All local addresses will be converted to global addresses.
Instructions
Control FPWIN Pro7 instructions do not contain an arithmetic data type. To keep the original arithmetic data type, add a special prefix to the address:
Prefix |
Data type |
Example |
Comment |
---|---|---|---|
D |
32-bit data |
DDT0 |
|
U |
Unsigned 16-bit data |
UDT0 |
This is prepended only if really needed. |
UD |
Unsigned 32-bit data |
UDDT0 |
This is prepended only if really needed. |
R |
32-bit real number |
RDT0 |
|
LR |
64-bit real number |
LRDT0 |
A subroutine surrounded by SBL and RET instructions is imported as a POU of type FUN. All CALL instructions are replaced by calling a POU of type FUN.
An interrupt surrounded by INTPG and IRET instructions is imported as a POU of type PRG. The POU will be assigned to the corresponding interrupt task.
LBL (label) numbers are re-assigned starting from zero.
Pulse instructions such as pMV.SS are imported as a non-pulse instruction combined with a DFI instruction.
Configuration
In data recording and operation recording, UTF-8 encoding is used for strings instead of the code page defined by the actual Windows installation. As a result, an error may occur during import if the data length is increased because the UTF-8 encoding works differently than the code page with which the original string was encoded.
CPU project comment
CPU project comments are stored in the comment field of the object PLC in the navigator.