Configuring Siemens TIA Portal comparisons
From TIA Portal V15.1 and octoplant 101.3.0, the native comparison process for projects takes place in octoplant and does not require the TIA Portal editor. There is no autonomous fallback mechanism, however, you can add an INI entry to the AgentStation.ini
file to force the old comparison process to execute when the native comparison does not work.
If TIA Portal is installed on the same device on which the comparison or job configuration is carried out, it is possible to read out project information for selecting the PLC to be saved directly via the TIA Portal.
To do this, add the following entry to the Compare/AgentStation.ini
file:
Info
Note that this can lead to longer loading times for the comparison or job configuration.
Comparison of blocks with activated know-how protection
A binary comparison of password-protected blocks is possible. This type of comparison recognizes differences, but does not display them in detail. Note that octoplant can only decrypt password-protected blocks and display code if the user provides the know-how passwords.
Including/excluding current values in the comparison
As of TIA Portal V15.1, you have the option of including/excluding current values in the comparison.
-
Open the Comparison configuration dialog for your component.
-
In the DB compare area, activate the Compare content option.
-
If necessary, select Exclude initial/current values of variables and enter the corresponding variables.
You can define variables for inclusion or exclusion using different syntax rules.
Info
-
Do not exclude or include entire sections, variable scopes, or areas such as Static or Temp. Only actual variables (such as single variables, struct members, or array elements) can be included or excluded.
-
When specifying variable paths (such as struct members or data block references), enclose the path in quotation marks, e.g.
"Struct.Test"
.
- Variable by name:
Struct_Test
- When specified only by name, the variable is included or excluded globally, even if it matches the name of a struct member.
- Single variable:
Test
- Array element:
Array_Test[0]
orArray_Test[1]
- Entire array:
Array_Test[*]
- Struct member:
"Struct_Test.Value_1"
- The
.
indicates a path. Use quotation marks around paths to include or exclude a specific member variable.
- The
- Entire struct:
"Struct_Test.*"
- Specific variable in a specific data block:
"Data_Block_Name.Variable"
- For example:
"Test_Block_1.Struct_Test"
- This syntax also applies to arrays, structs, and struct members. For example:
"Data_Block_Name.Struct_Test.Value_1"
or"Data_Block_Name.Struct_Test.*"
- For example:
Example:
-
-
Depending on whether “SetPoint” attributes should be considered, select or clear the Consider "SetPoint" attributes checkbox.
You have the following comparison options:
- Consider "SetPoint" attributes activated: Only values with this attribute are compared, unless there are entries in the exclude/include lists. Entries in these lists take precedence over the SetPoint attribute.
- Consider "SetPoint" attributes deactivated and exclude activated (without entries): All values are compared.
- Consider "SetPoint" attributes deactivated and include activated (without entries): None of the values are compared.
When Consider "SetPoint" attributes is activated, the inclusion or exclusion of variables can also be determined by the SetPoint attribute, provided this is not already controlled by entries in the include/exclude lists.
-
Select OK to confirm.
Result behavior when using include/exclude lists
- Result list with inclusions: If an include list is configured, the job result displays only the variables explicitly listed as included. All other variables are not displayed.
- Result list with exclusions: If specific variables are excluded, the job result displays only the variables that were not excluded or omits any output for excluded variables.
Related topics