Guidelines for using the Configure In Runtime (CiR) / Hot Configuration in Run (HCiR) feature
The following list summarizes the guidelines that you must follow to use the CIR/HCIR feature.
Hot Configuration in Run is possible when both the master and the slave devices support this feature.
Neither Configuration in Run nor Hot Configuration in Run supports the change of parameters or settings
which are global for all slaves. This means parameters like the bus speed, the global watchdog, target token
rotation time and so on cannot be changed using HCiR.
If the slave device supports HCiR, you must consult the slave device's vendor documentation to know about
the setup that is required to support HCiR on the slave.
To use the HCiR feature, you must ensure that all slaves which support HCiR have reserved areas
configured. 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.
The Lock/Unlock features are very important for a successful configuration of HCiR. It is recommended that
you lock all your slaves before modifying the configuration to use the HCiR feature. This prevents any re-
arrangement of the "Profibus Network Configuration Tool" address management. Modifying the
configuration includes adding or deleting modules.
Keep all slaves in the Protocol Block locked all the time. Unlock them when there is no reserved memory
area planned for the device and modification in the configuration is required. After the modification, lock
By default, the addition of a reserved memory area reserves 128 bytes into the memory map of a slave.
However the length/size of the reserved area can be changed manually based on your requirement.
If it is likely that complete slaves needs to be added during runtime, these slaves needs to be either planned
as slaves (set to inactive in "Profibus Network Configuration Tool" in order to not be expected during
runtime until they are physically attached to the network), or the Target Token Rotation Time (TTRT) needs
to be tuned upwards already. Both scenarios require a careful planning by a Profibus expert.
It is a best practice to review and clear all HCiR related settings in "Profibus Network Configuration Tool"
during a plant maintenance shutdown to ensure that all requirements are in place for the next production
phase of the plant and potential HCiR requirements.
It is recommended that you do not use the Defragment feature. Though this feature does not affect the
locked slaves, it could have an impact if by chance one or more slaves are unlocked when the Defragment
button is clicked.
6 PROTOCOL BLOCK