Differences: Predecessor product to current product
When you migrate logi.CAD/32 projects/objects to Neuron Power Engineer projects/objects, you will notice that the resulting Neuron Power Engineer projects/objects differ from the logi.CAD/32 projects/objects in some aspects. The main reason for the differences is that:
-
Neuron Power Engineer is based on the standard IEC 61131-3, edition 3.0 (= IEC-standard).
-
logi.CAD/32 is based on the standard IEC 61131-3, edition 2.0 but there have been deviations from it.
Neuron tries to provide a complete list regarding the differences of the logi.CAD/32 compared to Neuron Power Engineer. However, be aware that this list does not claim to be comprehensive. Please inform Neuron when you become aware of additional differences so that this list is modified/enhanced accordingly. |
The following tables inform in which aspects Neuron Power Engineer differs from its its predecessor logi.CAD/32. The aspects are grouped as Neuron sees fit.
In this article: |
---|
Explanation for tables
The columns of the tables have the following meaning:
-
Title specifies the appropriate aspect as known from logi.CAD/32.
-
Migration points out how the migration handles the aspect. Mind that the aspect is adjusted so that it matches the implementation in Neuron Power Engineer.
Migration can be done by the migration wizard or a command line interface for migration (identified as "headless tool" in the following description). Some of the migration results can be changed by configuring a file in JSON format (= JSON file) for the migration wizard or by specifying appropriate parameters when invoking the headless tool. See the documentation "Administrator's Manual" for information about the configuration possibilities for the migration wizard and the invocation of the headless tool and its parameters.
The icons used in this column have the following meaning:The aspect will be migrated.
The aspect will be migrated. But Neuron advises you to check the results in Neuron Power Engineer. If they are not to your liking, you might have to adjust them in Neuron Power Engineer.
The aspect will be migrated. But Neuron Power Engineer will report some problems after the migration of this aspect. Check the results in Neuron Power Engineer and fix the reported problems.
The aspect will not be migrated.
If this aspect is not supported in Neuron Power Engineer, the results in Neuron Power Engineer will not contain this aspect. Otherwise the columns to the right inform what can be done or how the aspect is realized in Neuron Power Engineer. -
LC32 informs about details of the aspect how it is realized for logi.CAD/32. Just the different parts are mentioned.
-
NPE informs about details of the aspect how it is realized for Neuron Power Engineer. Just the different parts are mentioned.
Basics
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
If you are interested in a different replacing method, it is possible to specify a replacement list and/or the simpler algorithm (instead of the default one). This is possible for the migration wizard (by changing a JSON file) as well as the headless tool (by specifying the appropriate parameter). Only in case of inputs (also |
Non-IEC-conform identifiers are allowed. At special locations (e.g. at the declaration location), such identifiers might have been embedded in: |
Only IEC-conform identifiers are allowed. Example: |
|
reserved keywords |
Identifiers that are reserved keywords are automatically replaced as follows:
|
Such identifiers are allowed. |
Such identifiers might not be allowed – depending on the context See the Neuron Power Engineer product user documentation for information on reserved keywords in Neuron Power Engineer product – search for "Reserved keywords in ST". |
names of system blocks as names for user-defined blocks in the logic (ST and FBD) |
The names of system blocks are automatically replaced, if they are used as
Example: The user-defined block If you are interested in a different replacing method, specify a replacement list and/or the simpler algorithm (instead of the default one). This is possible for the migration wizard (by changing a JSON file) as well as the headless tool (by specifying the appropriate parameter). |
Names of system blocks are allowed as names for user-defined blocks. |
Names of system blocks are not allowed as names for user-defined blocks. |
names of system blocks as names for variables or structuring elements in the logic (ST and FBD) |
Names of system blocks are allowed as names for variables or structuring elements. Example: variable |
|
|
Case of letters in identifiers |
Case sensitive identifiers for local variables become unique identifiers. Neuron Power Engineer will report errors for other case sensitive identifiers, i.e. for for inputs, outputs, global/external variables or blocks. |
case sensitivity of identifiers |
case insensitivity of identifiers |
Objects in Project Management
Errors and omissions when migrating objects
|
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
project |
Blanks in the project name are deleted. |
Blanks in the project name are allowed. |
Only a project name without blanks is allowed. |
libraries |
|
Libraries are realized ... |
... as folders. |
POU(ST); |
|
POU(ST) are realized ... |
... as ST-objects. |
program types(ST) |
|
|
ST-objects containing one program |
function block types(ST) |
|
|
ST-objects containing one function block |
functions(ST)
|
|
|
ST-objects containing one function |
for default migration when using the migration wizard It is not possible to change this migration result (by changing a JSON file). |
The function(ST) becomes... |
... |
|
for default migration when using the headless tool (without parameter |
The function(ST) becomes...
|
... a function (ST). |
|
data types |
|
Data types are realized ... |
... as ST-objects containing one data type. |
POU(FBD); |
|
POU(FBD) are realized ... |
... as FBD-objects. |
program types(FBD) |
|
|
FBD programs |
function block types(FBD) |
|
|
FBD function blocks |
functions(FBD)
|
|
|
FBD functions |
for default migration when using the migration wizard It is not possible to change this migration result (by changing a JSON file). |
The function(FBD) becomes... |
... |
|
for default migration when using the headless tool (without parameter |
The function(FBD) becomes... |
.... a function(FBD). |
|
POU(LD); |
|
|
not supported |
program types(LD) |
|
|
not supported |
function block types(LD) |
|
|
not supported |
functions(LD) |
|
|
not supported |
configurations |
|
Configurations are realized ... |
... as items within a PLC-object. |
resources |
|
Resources are realized ... |
... as items within a PLC-object. |
program instances |
|
Program instances are realized ... |
... as items within a PLC-object. |
type instances |
Type instances are migrated to program types and program instances. |
A type instance becomes ... |
|
task |
Tasks are migrated with an exception. |
Tasks are realized ... |
... as items within a PLC-object. |
global variables in configurations |
|
Configuration-global variables are realized ... |
... as global variables in a global-object (located in a folder with the name of the configuration). The configuration in the PLC-object contains a reference to these global variables. |
global variables in resources |
|
Resource-global variables are realized ... |
... as global variables in a global-object (located in a folder with the name of the resource). The resource in the PLC-object contains a reference to these global variables. |
documents-objects |
|
|
not supported |
structuring folders |
|
Structuring folders are realized ... |
... as folders. |
links |
|
|
Create a linked resource in Neuron Power Engineer. |
non logi.CAD/32 objects |
|
Such objects must be copied from the logi.CAD/32 project ... |
... into the Neuron Power Engineer project. |
vendor libraries with vendor function blocks and/or |
Only the interface of vendor function blocks and vendor functions is migrated. Regarding the sorting of variables: Use POU-unique names (when possible, project- and POU-unique) for all C-identifiers that are available in a global namespace. Details on the reason for this can be found in the Neuron Power Engineer user documentation, under "The dos and don'ts when working, When creating blocks with C-code". |
The required C-code must be integrated ... |
... into the application in Neuron Power Engineer. |
definitions entered by an OEM in the tab Master Data for vendor function blocks and/or vendor functions |
– if the project/objects are migrated when using the headless tool and the corresponding OEM-parameter This migration result is also possible when using the migration wizard (by changing a JSON file). Contact Neuron for more information. |
The definitions become ... |
... so-called instance parameter items. |
signal data base |
|
|
not supported |
properties |
|
The values might be a comma-separated list. These values become ... |
... the according settings for namespaces. |
Contact Neuron, if you are interested in details on how to specify the mentioned logi.CAD/32 properties. |
Supported elementary data types
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lower limit: |
lower limit: |
|
|
upper limit: |
upper limit: |
|
|
lower limit: |
lower limit: |
|
String literals not conform to the IEC-standard are migrated. This affects e.g. string literals with double quotes or with special characters. |
String literals (constants) with double quotes are migrated ... |
... to string literals with single quotes. |
for default migration when using the migration wizard: Strings without a size become strings with a length of Strings with a size always keep their length – no matter if the parameter |
|
|
|
for default migration when using the headless tool (without parameter Strings with a size always keep their length – no matter if the parameter |
|
|
Variable declarations for ST and FBD
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
variables in programs |
– as specified in this table |
|
|
variables in function blocks |
– as specified in this table |
|
|
variables in functions |
The storing behavior changes. Observe that it is possible to migrate LC32 functions so that they become NPE function blocks. As a consequence, the storing behavior does not change for the included variables (see "Objects in Project Management", items "functions(ST)" and functions(FBD) for details). |
Variables in functions have storing behavior. |
Variables in functions do not have storing behavior. |
variables |
|
|
|
|
Regarding the sorting of variables: |
|
|
|
|
|
|
|
|
|
|
|
Regarding the sorting of variables: |
|
|
|
Initial values for Regarding the sorting of variables: |
Initial values for |
Initial values for |
variables |
|
|
|
derived variables |
|
|
|
subrange variables |
The variable is migrated but the subrange is lost. |
The subrange becomes... |
a comment. |
array variables |
|
|
|
enumeration variables |
Neuron Power Engineer will report errors for such variables. |
|
not supported |
variables |
|
|
|
|
A variable with attribute |
|
|
|
A variable with attribute |
The attribute is lost or highlighted as faulty for |
because |
|
A |
The |
an in-out variable ( |
visualize |
|
|
not supported |
parameter |
|
|
not supported |
the following pieces of information for variables |
|
|
|
long name |
The long name is automatically enclosed by single quotes: |
Single quotes |
by double quotes |
comment |
The comment is automatically enclosed by single quotes: |
Single quotes |
by double quotes |
technical units |
|
|
not supported |
scaling |
|
|
not supported |
alternate names for in-/outputs |
Alternate names are only migrated in case of the active LC32 setting Alternate I/O-names. There is a special behavior, if no alternate name for an input (also |
|
|
physical address |
Physical addresses for outputs are migrated to hardware addresses for outputs conform to the IEC-standard. Invalid physical addresses are removed. |
Example: |
|
additional information e.g. for variables (specified by an OEM) |
|
The definitions become... |
... initial values of the so-called instance parameter.Ask your system integrator for details on the instance parameters. |
Data type declarations
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
declarations |
|
|
|
derived data types |
|
|
|
subrange data types |
The data type is migrated but the subrange is lost. |
The subrange becomes... |
a comment. |
array data types |
|
|
|
enumeration data types |
Neuron Power Engineer will report errors for such data types. |
|
not supported |
structured data types |
Regarding the sorting of variables:
|
|
Regarding the sorting of variables: |
the following pieces of information for structure elements |
|
|
|
long name |
The long name is automatically enclosed by single quotes: |
Single quotes |
by double quotes |
comment |
The comment is automatically enclosed by single quotes: |
Single quotes |
by double quotes |
scaling |
|
|
not supported |
layout for data types: color, line type |
|
|
The default layout is used. |
Elements for function block diagram
If the POU(FBD) in logi.CAD/32 contains faulty FBD-elements, those FBD-elements are still faulty in Neuron Power Engineer.
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
empty value fields |
|
|
not supported |
value fields with content and the following pieces of information |
|
|
|
position, size |
|
|
|
text (variable or literal) in value field |
|
String literals (constants) with double quotes are migrated ... |
... to string literals with single quotes. |
inverted, connected in-/outputs |
|
Inverted in-/outputs are called ... |
... negated in-/outputs. |
inverted, unconnected in-/outputs |
|
|
not supported |
layout: color, font |
|
|
The default layout is used. |
flipped value fields |
Re-position such value fields in order to correct the line connections. |
Flipped value fields become ... |
... normal values fields but the original line connections are kept. |
call of function block or functions with the following pieces of information |
|
|
|
position, size |
|
|
|
name of function block or function |
|
|
|
in-/outputs: name and position |
|
|
|
|
The left columns contain only the differences.
|
The different behavior, when
|
The different behavior, when
See the Neuron Power Engineer user documentation for information on the behavior in Neuron Power Engineer – search for "Execution control: EN, ENO". |
inverted, connected in-/outputs |
|
Inverted in-/outputs are called ... |
... negated in-/outputs. |
inverted, unconnected in-/outputs |
|
|
supported but such inputs are causing a warning |
layout: color, font |
|
|
The default layout is used. |
displayed instance name |
|
|
|
displayed priority |
|
|
not supported |
flag for inline |
|
|
not supported |
flag for retain |
|
|
not supported |
instance data |
Some lists and/or a format string might become normal text. |
The list Wildcards for data items within the list are supported in logi.CAD/32. |
... the appertaining dynamic text for the instance data: Wildcards for the instance data elements are not supported in Neuron Power Engineer. |
comment fields with the following pieces of information |
|
|
|
position, size |
|
|
|
text in comment field |
|
|
|
graphics in comment field |
|
|
not supported |
layout: color, font |
|
|
The default layout is used. |
comment fields attached to empty value fields |
|
|
not supported |
comment fields attached to other elements in FBD |
Some format strings might become normal text. |
Attached comment fields become ... |
... attached comment fields. |
connector fields with the following pieces of information |
|
Connector breaks are called ... |
... connectors. |
position, size |
|
|
|
text in connector field |
|
The text (name) for the connector is adjusted ... |
... so that the name is unique. |
layout: color, font |
|
|
The default layout is used. |
flipped connector fields |
Re-position such connector fields in order to correct the line connections. |
Flipped connector fields become ... |
... normal connector fields but the original line connections are kept. |
invisible connector fields (= mini connector fields) |
|
Invisible connector fields become ... |
... normal connector fields. |
lines connected to FBD-elements, connecting an input with an output |
|
|
|
lines connected to FBD-elements, connecting an input with a different input |
Such lines are migrated but they are highlighted as faulty in Neuron Power Engineer. |
It is possible to create a line and its starting or ending point are different inputs. |
It is not possible to create such lines. |
open lines |
|
It is possible to create a line and its starting or ending point is not connected to any element. |
It is not possible to create such lines. |
line connections with the following pieces of information |
|
|
|
routes of lines |
|
|
|
fixed nodes for lines |
|
Nodes for lines are called ... |
... connection points. |
layout: color, font |
|
|
The default layout is used. |
OLT-fields in function blocks or programs |
|
|
|
OLT-fields for value fields with content |
|
|
|
OLT-fields for empty value fields |
|
|
not supported |
OLT-fields for function block instances |
|
|
|
OLT-fields for function calls |
|
|
not supported |
OLT-fields for in-/outputs of function block instances |
|
|
|
OLT-fields for inputs of function calls |
|
|
not supported |
OLT-fields for outputs of function calls |
|
|
|
unconnected OLT-fields |
|
|
not supported |
OLT-fields in functions |
|
|
not supported |
OLE-objects |
|
|
not supported |
feedback loops |
Feedback loops are not touched. |
A feedback loop caused after a function call is allowed. |
A feedback loop caused after a function call is only allowed, if a value field or a function block call follows the function call. Depending on the configuration of Neuron Power Engineer, feedback loops for functions without a variable in between are highlighted as error or warning. |
execution order of networks, if all network inputs are part of explicit feedback loops within the network |
A different execution order might result. This different execution order of networks might influence the behavior at the end of the task cycle. |
If all inputs of the network are part of explicit feedback loops within the network or an input is used as output by another network, the network cannot be evaluated at first. |
If all inputs of the network are part of feedback loops within the network, the network can be evaluated. |
execution order of networks, if a variable is used as array index for statements |
A different execution order might result. |
In the default variant, logi.CAD/32 distinguishes where the array variable is used for the statement:
Note: There is a processing variant for logi.CAD/32 that is identical to the Neuron Power Engineer behavior. |
Neuron Power Engineer always waits for the evaluation of the variable which is used as array index – no matter where the array variable is used for the statement. |
execution order within networks |
A different execution order might result, if:
|
|
Note: Different rules are applied, if you have used the start option |
the following pieces of information for FBD-elements |
|
|
|
hyperlinks |
|
|
not supported |
properties |
|
|
not supported |
shapes |
|
|
not supported |
the following pieces of information for the drawing field |
|
|
|
size |
|
Example: The page size "DIN A3" in logi.CAD/32 becomes... |
page size "DIN A4" in Neuron Power Engineer. |
layout: value field area |
|
|
|
other layout: connector field area, grid, color, DXF-forms in background |
|
|
The default layout is used. |
the following pieces of information for the sheets |
|
|
|
page number, short name |
|
|
not supported |
long name |
|
The long name becomes... |
the page name. |
information on creation, changes |
|
|
not supported |
information on labeling system: ULS, PPLS, page ID |
|
|
not supported |
Sequential function chart (SFC)
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
steps and initial steps |
|
|
|
transitions |
Transitions with an inverted input for the transition condition but without a connected value field differ in their behavior. |
Such transitions are never enabled. |
Such transitions are not supported in Neuron Power Engineer. An error message will report this error. |
action blocks |
|
The comment of an action block... |
... is not supported in Neuron Power Engineer. |
connecting one step to one transition and vice versa |
Check the messages of the logi.CAD/32 tool |
|
|
other connections for step sequences: connecting one step to several transitions (alternative branch) connecting several transitions to one step (alternative junction) connecting one transition to several steps (parallel branch) connecting several steps to one transition (parallel junction) |
|
Lines of these connections are ... |
... displayed with another line style. |
execution order of SFC networks and SFC elements |
The execution order of SFC differs. |
The execution order of SFC differs ... See the logi.CAD/32 online-help for information on the behavior in logi.CAD/32. |
... from the evaluation of SFC elements. See the Neuron Power Engineer user documentation for information on the behavior in Neuron Power Engineer. |
Ladder diagram
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
LD (ladder diagram) |
If you migrate ladder diagrams anyway, it is likely that the results in Neuron Power Engineer will differ from your expectations. |
Ladder diagrams in logi.CAD/32 are differently realized ... |
... than in Neuron Power Engineer. |
System function blocks or functions
See "Differences: System blocks in predecessor product to current product".
Graphical interfaces for user-defined function blocks or functions
Title |
Migration |
LC32 |
NPE |
---|---|---|---|
displayed text: name |
|
|
|
displayed text: alternative text |
|
|
|
size |
|
|
|
extendable |
|
|
|
in-/outputs |
|
|
|
position of in-/outputs |
|
|
|
layout: background color |
|
|
|
other layout options, such as font |
|
|
The default options for the layout are used, when a new call is set. |
the following pieces of information |
|
|
|
setting whether a specific in-/output is to be inverted |
|
|
not supported |
setting whether instance name is to be displayed |
|
|
|
setting whether to generate INLINE-code |
|
|
not supported |
setting whether |
|
|
not supported |
setting Alternate I/O-names (= whether alternate names for in-/outputs are to be displayed) |
The behavior is slightly different. |
The alternate names are used for the visual display, only if the LC32 setting is checked. |
The alternate names are automatically used for the visual display. |
setting for priority |
|
|
not supported |
the following elements in the interface |
|
|
|
attribute input fields |
|
|
not supported |
comment fields containing the format string |
|
Such comment fields become ... |
... the instance name displayed within the interface. |
other comment fields |
|
Format strings in comment fields, such as |
... normal text (such as the type name). |
layout of comment fields |
|
The layout of comment fields is migrated... |
as far as NPE supports the respective layout option. |
value fields for an input, if the input is not connected |
|
The value field incl. its content ... |
... is migrated. Reason: The content of the value field (e.g. a literal) is used as value for the input. |
value fields for an input, if the input is connected |
|
Only the value field ... |
... is migrated. |
graphics |
|
|
not supported |