Recommendations
(Original Document)
About us
At a Glance
When converting PL7 applications, certain cases have been identified in which manual solutions are required. These are described in this appendix.
CAUTION
UNEXPECTED APPLICATION BEHAVIOR - INCOMPLETE CONVERSION
If you are using control loops parametered using PL7 variables (%MW, %MF...) in the FEF file to be converted, you must enter them again using Control Expert.
Failure to follow these instructions can result in injury or equipment damage.
What to do when the conversion fails
The following table shows the procedure when the conversion fails just after opening the FEF file.
If
Then
an error message appears
consult the report file to obtain additional information.
in the report file, the error concerns an unknown hardware configuration
Then
  • open the STX file using version ≥4.3 of PL7,
  • modify the processor version,
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
in the report file, the error concerns the name of a character string longer than 32 characters
Then
  • using PL7, modify the name of the variable to lower the size to under 32 characters,
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
in the report file, the error concerns a name conflict between variables, sections, etc.
Then
  • using PL7, modify the names or symbols concerned,
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
the FEF file was created with a version of PL7 previous to 4.0
Then
the FEF file was created with a 4.0, 4.1 or 4.2 version of PL7
Then
the processor is not level 3
Then
in the FEF file, built-in control loops are used, set using PL7 variables (%MF, for example)
Then
  • using PL7, modify the loops concerned,
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
you have modified the configuration of a TSX SCY 21601 module just before exporting the FEF file
Then
  • using PL7, save the stx file before exporting the application (this allows you to save all last-minute modifications),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
What to do when the import fails
The following table describes the procedure when the import phase fails (this phase is launched automatically after the conversion phase).
If
Then
the hardware configuration of the FEF file has ATV 16 controllers on a Fipio bus
Then
  • using PL7 remove the ATV 16 controllers from the Fipio bus (ATV 16 no longer recognized by Control Expert),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
the hardware configuration of the FEF file has CCX 17 controllers on a Fipio bus
Then
  • using PL7 remove the CCX 17 controllers from the Fipio bus (CCX 17 no longer recognized by Control Expert),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
the hardware configuration of the FEF file has SIMULATION devices on a Fipio bus
Then
  • using PL7 remove the SIMULATION devices from the Fipio bus (SIMULATION no longer recognized by Control Expert),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
the hardware configuration of the FEF file has a TSX P57 2823 or TSX P57 4823 processor
Then
  • using PL7 replace the processor with one that is recognized by Control Expert, then modify the configuration to obtain equivalent functionalities (for example, use a TSX P57 253 processor and ETY module to replace a TSX P57 2823),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
the PL7 application to convert has a TSX SPY 400 simulation module or TSX ISPY 100 weighing module
Then
  • using PL7, delete all the parts concerning these (configuration, sections, etc.),
  • export the PL7 application to obtain a new FEF file,
  • restart the conversion, opening the FEF file with Control Expert.
an indexed variable is used as an activation condition
using Control Expert, write the missing condition without using indexed variables.
A simulation module is used in the PL7 Pro configuration during import
Always remove the simulation module from the PL7 Pro configuration from the rack and when used with FIP I/O bus.
What to do when the generation of the project fails
The following table describes the procedure when the Control Expert generation phase fails.
If, in the generation report, one of the following cases appears
Then
a section written in ST language has a truncated line
Then
  • using Control Expert, correct the faulty line return generated during editing (the ST editor does not authorize lines of over 300 characters),
  • generate the project again.
an error occurs on a macro step bit
Then
  • using Control Expert, check that the macro step is declared (using PL7 it is possible to use a macro step bit without it being declared),
  • if this is the case, correct the program accordingly.
  • generate the project again.
an error on input or output-type objects (%Q1.2.48:16 for example) is generated
Then
  • check that these objects are configured using PL7,
  • if this is not the case, correct the program accordingly.
  • generate the project again.
an error on FIPIO objects (%IW\2.80\0.0.0.3 for example) is generated
Then
  • check that these objects are configured using PL7,
  • if this is not the case, correct the program accordingly.
  • generate the project again,
  • if you are using ADM 390 10 modules, it is no longer possible to use FIPIO objects under Control Expert.
an error in the system word tables is generated
Then
  • create a table of integers with 4 elements,
  • assign each element one by one.
  • generate the project again.
an error occurs on a table-type DFB output
a table-type DFB output is no longer accessible outside the DFB. To access it, you must use the variable connected to the corresponding output pin. For further information see on DFBs, conversion precautions
an error on the DINT-type variables recognized as INT by Control Expert
Then
  • modify the program to make the types compatible,
  • example: SD52, the solution consists of creating a DINT-type SD52 object by writing SD52:=INT_AS_DINT(%SW52,%SW53);.
  • generate the project again.
an error occurs on the %I or %IW assigned in the program
modify the program to delete these assignments. Assignment on inputs is no longer accepted by Control Expert.
an error occurs on a vertical comparison block located in the first column of the editor
using the Copy/Paste function, modify the program to move this block by one column.
an error occurs in an SFC. An error message indicates that alternative divergences or parallel convergences must be followed respectively by a transition or a step
modify the SFC following the indications of the output window.
an error indicates that the maximum number of configured steps is insufficient
increase the maximum number of steps as indicated in the output window (use the command Tools → Project settings → Language extensions). The calculation of the maximum number of steps using Control Expert includes macro-steps.
an error indicates an incompatibility between the different types of an assignment (probably a multi-assignment using PL7)
Modify the program to remove these incompatibilities.
an error occurs on a multi-assignment in an LD operate block
modify the program by writing as many blocks as there are assignments.
NOTE: In IL language, some conversions generate errors when analysing the project, see Boolean Instructions page.