6 PROTOCOL BLOCK
6.7 About modifying the field network configuration during runtime
Starting 410.2, Configure In Runtime (CiR) / Hot Configuration in Run (HCiR) is supported in PGM. This
feature enables you to modify some of the slave device configuration without causing a break in the V0 process
data delivery to other slave devices. When you modify the configuration during runtime, the corresponding
device is r-econfigured, which means that the field device is re-initialized.
CIR in PGM is supported for slaves that retain their process data in same addresses in old and new version of
the network configuration.
Modifying slave device configuration can be any of the following:
Modifying the device configuration or parameters.
Adding or removing a module that can be added or removed.
Modifying any of the PGM master parameters such as baud rate, station address, and so on. In this scenario,
all field devices are reconfigured.
The following figure displays a sample Bus Parameters page.
While configuring the slaves in "Profibus Network Configuration Tool", it is recommended that you add reserved
input and/or output memory area to the slaves and lock the slaves (ensure that you lock the inputs and outputs
separately). This helps you to add modules without unlocking the slaves. The length of the reserved area gets
adjusted automatically with the memory area of the module on insertion of a module. This way the Target Token
Rotation Time (TTRT) is maintained and as a result the change can be loaded to the PGM without causing process
data delivery interruptions to unchanged slaves in the network. As long as the modified slave supports the Hot
Configuration in Run feature, even its own inputs and outputs are automatically frozen during the re-configuration
and a bump-less restart after the re-configuration is executed.