GroupStates()
Instance type | Instance Name |
---|---|
Master |
|
Slaves |
|
State diagram:
Process description:
- A group always remains in the
Idle
state until a grouping command is issued. - It does not matter whether this is requested by the machine data, the PLC program or the HMI.
- As soon as a grouping command is received, the group in the
ConfigMd
state starts to configure the internal FB_MdTempGrouping instances according to the grouping. - The
ConfigXy
andReadTuningXy
states are then loaded file by file from the target system and compared with the set grouping. - Special case program start: The last grouping used is loaded here when the program is started.
- Once the grouping has been found on the target system, the system begins to load the stored parameters of this group configuration into the runtime memory.
- If the option
EnableConfigConfirmation
is activated, the group waits with this process until a response is triggered by FB_TemperatureHmi.Groups(x).ConfigConfirm
or.ConfigReject
. - If no grouping data is found on the target system, the grouping set at the beginning is created and saved as a new configuration with a new
ConfigID
. - If automatic tuning is activated by FB_TemperatureHmi.Groups(x)
.DoTune
, the group is in tuning mode (within theTuningXy
states). If a regrouping is requested in this state, the tuning process is aborted.
Special case: Grouping by machine data Loading the machine data for the first time after starting the program is a special case: In the higher-level machine data of the FB_Temperature, the |
Default parameterization All default parameters should be set in the
|
Requirements
Development environment | Target platform | PLC libraries to include |
---|---|---|
TwinCAT >= v3.1.4024.54 (recommended) | PC or CX (x64, x86) | Tc3_PlasticBaseApplication (>= v3.12.7.0) |