Plant changes in RUN - CiR
11.4 Re-configuring I/O modules and ports in IO devices
CPU 410 Process Automation/CPU 410 SMART
164
System Manual, 05/2017, A5E31622160-AC
OB calls in re-configuration
Once the CPU has run the tests described in "Behavior of the CPU after download of the
configuration in RUN", it starts OB 83 with the event W#16#335A. This means that as of now
the input or output data of the I/O modules in question may no longer be correct. You may no
longer call any SFCs that trigger new jobs for sending data records to the I/O modules
involved, otherwise a conflict could occur between the data records sent by the system and
those sent by the user.
Once the CPU has completed OB 83, it sends the parameter data records with each I/O
module involved receiving the total number of data records (regardless of how many data
records are affected by your change).
Another OB 83 start follows (start event W#16#325A if sending was successful or
W#16#395B if it was not). No other priority class is interrupted by this processing of OB 83.
11.4.4
Reconfiguration Procedure
11.4.4.1
Using a Previously Unused Channel
Procedure
1.
Change the hardware configuration and download it to the CPU.
2.
Save your project.
3.
Make the change to the wiring.
4.
Change the user program and download it to the CPU.
11.4.4.2
Reconfiguring an already used channel.
Introduction
The procedure depends on whether or not changes to the user program and the associated
hardware are necessary due to the re-configuration. The individual cases are described
below.
Procedure without change
The user program need not be changed as a result of re-configuration. This is the case, for
example, when you change an alarm limit or when you disable the diagnostic interrupt.
●
Change the hardware configuration and download it to the CPU.