Differences Between Forcing and Modifying Variables Page 1 of 1

Differences Between Forcing and Modifying Variables

The following table summarizes the differences between forcing and modifying:

Feature / Function Forcing with Forcing with Modify

S7-400 (incl. S7-300 (without
CPU 318-2DP) CPU 318-2DP)
Bit memory (M) yes  yes
Timers and counters (T, C)   yes
Data blocks (DB)   yes
Peripheral inputs (PIB, PIW, PID) yes  
Peripheral outputs (PQB, PQW, PQD) yes  yes
Inputs and outputs (I, Q) yes yes yes
User program can overwrite the  yes yes
modify/force values
Replacing the force value effective yes yes 
without interruption
The variables retain their values when yes yes 
the application is exited
The variables retain their values after the yes yes 
connection to the CPU is broken
Addressing errors permitted:   The last becomes
e.g. IW1 modify/force value: 1 effective
IW1 modify/force value: 0
Setting triggers Always trigger always trigger once or every cycle
immediately immediately
Function only affects variable in visible Affects all force affects all force yes
area of active window values values

Note
 With "Enable Peripheral Outputs," the force values for forced peripheral
outputs become effective on the corresponding output modules; the modify
values for peripheral outputs, however, do not.
 With forcing, the variable always has the forced value. This value is read
during each read access to the user program. All forms of write access are
ineffective.
 With permanent modifying, read access to the program is effective and
remains so until the next trigger point.

mk:@MSITStore:E:\Arquivos%20de%20programas\Siemens\Step7\S7bin\s7bashdB.ch... 9/5/2009