System Manual Modular Systems 7 Start-Up
HI 800 191 E Rev. 2.02 Page 57 of 114
The CRC for safeethernet is created as in
SILworX V2.36.0. This setting is required for
exchanging data with resources planned with
SILworX V2.36 or previous versions.
The CRC for safeethernet is created with the
current algorithm.
1)
First value applies to controllers, second value applies to remote I/Os.
Table 26: System Parameters of the Resource - CPU OS V7 and Higher
The following table describes the effect of Target Cycle Time Mode.
Effect on reload of processor modules
The PES maintains the target cycle time
and extends the cycle if necessary. If the
processing time of the user programs
exceeds the target cycle time, the cycle
duration is increased.
Reload is not processed if the target cycle
time is not sufficient.
At most, the duration of every fourth cycle is
increased to allow reload.
At most, the duration of every fourth cycle is
increased to allow reload.
HIMatrix maintains the target cycle time as
well as possible and also executes the
cycle as quickly as possible.
Reload is not processed if the target cycle
time is not sufficient.
Table 27: Effect of Target Cycle Time Mode
Notes on the Minimum Configuration Version Parameter:
In a new project, the latest Minimum Configuration Version is selected. Verify that this setting
is in accordance with the hardware in use, e.g., in HIMatrix standard devices, Minimum
Configuration Version must be set to SILworX V2.
In a project converted from a previous SILworX version, the value for Minimum Configuration
Version remains the value set in the previous version. This ensures that the configuration
CRC resulting from the code generation is the same as in the previous version and the
generated configuration is compatible with the operating systems in the hardware.
For this reason, the value of Minimum Configuration Version should not be changed for
converted projects.
If features only available in higher configuration versions are used in the project, SILworX
automatically generates a higher configuration version than the preset Minimum
Configuration Version. This is indicated by SILworX at the end of the code generation. The
hardware denies loading a higher configuration version than that matching its operating
system.
For help, compare the details provided by the version comparator with the module data
overview.
If a Minimum Configuration Version of SILworX V4 or higher is set for a resource, the Code
Generation Compatibility parameter must be set to SILworX V4 in every user program (see
below).