September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
1/17
ERROR & TROUBLESHOOTINGERROR & TROUBLESHOOTING
SIEMENS
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
2/17
SIEMENS
Objectives
- Learn How to Classify Errors.
- Module Information & Diagnostic Buffer.
- Detect Error Through Stacks.
- Hardware Diagnostic Through Hardware Configuration.
- Variable Table & Cross Reference.
- Track Errors Through Blocks (Go To & Compare)
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
3/17
Categories of Errors
Errors that are detected by the PLC‘s
operating system and normally cause
the CPU to go into the Stop state.
- Module failure
- Short-circuit in signal cables
- Scan time overrun
- Programming error (accessing
a non-existent block)
Functional errors, that is, the CPU
processes the program as usual, but
thedesired function is either not
executed at all or it is executed
incorrectly.
- Process fault, Ex. wiring error
- Logical programming error (not
detected
during creation and startup)
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
4/17
x x+1x x+1
Error detected by the System:
General Rule: CPU in STOP
(such as accessing a non-existent DB)
(Diagnostic interrupt of a signal module)
Debugging Tools:
• Module Information
- Diagnostic buffer
- I STACK
- B STACK
- L STACK
• Hardware Diagnostics
Error
Functional Error:
General Rule: CPU in RUN
(process fault, such as a wire break)
(logical programming error, like a double assignment)
Debugging Tools:
• Monitor / Modify Variable
• Monitor Blocks (Block Status)
• Reference Data
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
5/17
Module Information
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
6/17
Module Information, Diagnostic
Buffer
The diagnostic buffer is is a FIFO
buffer in the CPU.
The diagnostic buffer contains all
diagnostic events in
the order in which they occurred.
The diagnostic buffer cannot be
deleted by a memory reset.
All events can be displayed on the
programming device in plain text and
in the sequence in which they occur.
Details on Event
When you select an event, the
following additional information is
supplied in the "Details on Event" box
Help on Event
When you click on the button, help on
the event selected in the list is opened.
Open Block
When you click on the button, the
block in which the interruption
occurred can be opened online
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
7/17
Interpreting Messages, Diagnostic Buffer
After the restart, the error occurred and caused entries no. 2 and 3.
Event No. 2: the CPU goes into the STOP mode because the
associated error OB (OB 121) was not loaded into the controller.
Event No. 3: the actual cause of error, FC is not loaded to the CPU
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
8/17
Opening a Block Containing an Error
For errors that were triggered by a faulty instruction in the user program, you can
open the interrupted block by clicking on the "Open Block" button.
If the STL language is selected, the cursor is positioned directly in front of the
instruction that caused the interruption. In LAD/FBD, the network causing the
interruption is displayed.
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
9/17
B Stack
The block stack (B stack) is a graphic
representation of the call hierarchy,
that is, the sequence and nesting of
the called blocks up to the point of
interruption.
The B stack also contains a listing of
all interrupt and error OBs as well as
the open DBs.
The program execution was
interrupted in the block shown at the
bottom of the list.
In the slide you can see that the
interruption occurred in the block
OB1. When a parameter-assignable
block is called several times, the
information, after which block call the
program execution was interrupted, is
relevant for troubleshooting, since the
cause of the interruption can lie in the
passing of faulty actual parameters by
the calling block.
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
10/17
I Stack
The interrupt stack (I Stack) always
refers to an execution level. Before
you can open the I Stack, the
organization block concerned must
be selected in the B Stack.
The "Point of Interruption" field
gives you information about:
• The interrupted block, with the
option of opening it directly (the
cursor is then located directly in
front of the faulty instruction),
• The priority class of the OB,
whose execution level was
interrupted,
• Open data blocks with their
numbers and sizes.
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
11/17
L Stack
The current values of the temporary
variables for blocks not ended at the
time of interruption are contained in
the L Stack.
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
12/17
Displaying the Hardware Diagnostics
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
13/17
Monitor/Modify Variables
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
14/17
Monitor Modify Update
Monitor
Update
Modified
values
Trigger point
"Beginning of Scan Cycle"
PII
PIQ
Trigger point
"End of Scan Cycle"
Trigger point
"Transition to STOP"
Cyclic
program
execution
Triggering Point for Monitor/Modify Variables
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
15/17
Overwriting Variable Using Force Variables
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
16/17
Testing & Monitoring Block Status
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
17/17
Trigger Condition For Block Monitoring
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
18/17
Display Refrance Data
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
19/17
Display Cross Refrance Data
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
20/17
Assignment Of In/Out, Bit Memory, Timers & Counters
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
21/17
Program Structure
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
22/17
Unused Symbol In Symbol Table
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
23/17
Filtering Cross Reference
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
24/17
Find In Reference Data
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
25/17
Editing Blocks Using Cross Reference
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
26/17
Go To Location From Function To Function
SIEMENS
September 28, 2018SIMATIC S7
SIEMENS LTD EGYPT
27/17
Comparing Blocks
SIEMENS

More Related Content

PPT
Function Block & Organization Block
PPT
PPT
Declaration Table
PPT
plc introduction
PPT
Analogue Module
PPT
Math operation
PPT
S7 bas-16
Function Block & Organization Block
Declaration Table
plc introduction
Analogue Module
Math operation
S7 bas-16

What's hot (20)

PPTX
Tia portal v14_en
PPT
Data Block
PPTX
Industrial automation
PDF
Presentatie Festo
PDF
Presentatie Phoenix Contact
PPTX
Industrial Automation
PPTX
Programmable Logic Controllers
PDF
1 sinamics components
PDF
PPTX
PPT on INDUSTRIAL AUTOMATION, PLC, SCADA
PPTX
MCC & Smart (intelligent) MCC وحدات
PDF
Allen Bradley- Micrologix PLC Instructions
PPTX
ppt on PLC
PDF
Simens plc training. simatic working-with-step-7
PPT
S7 400 h
DOCX
Plc seminar abu
PPTX
Basics of Automation, PLC and SCADA
PDF
Corporate presentation Prima Automation
PPTX
Use of plc in industrial automation
Tia portal v14_en
Data Block
Industrial automation
Presentatie Festo
Presentatie Phoenix Contact
Industrial Automation
Programmable Logic Controllers
1 sinamics components
PPT on INDUSTRIAL AUTOMATION, PLC, SCADA
MCC & Smart (intelligent) MCC وحدات
Allen Bradley- Micrologix PLC Instructions
ppt on PLC
Simens plc training. simatic working-with-step-7
S7 400 h
Plc seminar abu
Basics of Automation, PLC and SCADA
Corporate presentation Prima Automation
Use of plc in industrial automation
Ad

Similar to ERROR (20)

PPT
10731617.ppt
PPT
Ch7 v70 scl_en
PPTX
Webinar on Functional Safety Analysis using Model-based System Analysis
PDF
Comparison list for Siemens S7-300, S7-400, S7-1200, S7-1500 Reference Manual
PPTX
Siemens_PLC_Debugging_Troubleshooting.pptx
PPTX
What is the Siemens Open Library, and How it Decreased Development Time for E...
PPT
Top Ten Siemens S7 Tips and Tricks
PDF
Siemens s7 300-400-working with step 7 v5.1
PDF
s7_1500_compare_table_en_mnemo.pdf
PDF
Siemens s7 300-400-working with step 7 v5.0
PDF
Safety Verification and Software aspects of Automotive SoC
PPTX
Top Ten Programming Mistakes by People New to Siemens
PDF
Diagnostic_TIA_Environment_EN.pdf materials
PDF
TechRef_RelFdetsie.pdf
PDF
Trouble Shooting PC
PDF
Software-supported testing - SENTRON 3WA air circuit breakers .pdf
PPT
DSP/Bios
PPT
Function Block.ppt
DOCX
Simatic manager siemens S7 guide
10731617.ppt
Ch7 v70 scl_en
Webinar on Functional Safety Analysis using Model-based System Analysis
Comparison list for Siemens S7-300, S7-400, S7-1200, S7-1500 Reference Manual
Siemens_PLC_Debugging_Troubleshooting.pptx
What is the Siemens Open Library, and How it Decreased Development Time for E...
Top Ten Siemens S7 Tips and Tricks
Siemens s7 300-400-working with step 7 v5.1
s7_1500_compare_table_en_mnemo.pdf
Siemens s7 300-400-working with step 7 v5.0
Safety Verification and Software aspects of Automotive SoC
Top Ten Programming Mistakes by People New to Siemens
Diagnostic_TIA_Environment_EN.pdf materials
TechRef_RelFdetsie.pdf
Trouble Shooting PC
Software-supported testing - SENTRON 3WA air circuit breakers .pdf
DSP/Bios
Function Block.ppt
Simatic manager siemens S7 guide
Ad

More from Mahmoud Hussein (20)

PPTX
07 modelling.electric.motors
PPTX
Dc dc converter
PPTX
08 pid.controller
PPTX
06 control.systems
PPTX
05 tuning.pid.controllers
PPTX
02 physical.system.modelling mechanical.systems.
PPTX
03 dynamic.system.
PPTX
Lecture 02 laplace transformation
PPTX
PPTX
Model based design-Hardware in loop-software in loop
PPTX
Ac drive basics
PPTX
Velocity kinematics
PPT
MPI Communication
PPTX
Industrial communication
PPTX
Computer vision
PPTX
Neural network
PPTX
Fuzzy logic
PPTX
Dh parameter application
PPTX
Lectue five
07 modelling.electric.motors
Dc dc converter
08 pid.controller
06 control.systems
05 tuning.pid.controllers
02 physical.system.modelling mechanical.systems.
03 dynamic.system.
Lecture 02 laplace transformation
Model based design-Hardware in loop-software in loop
Ac drive basics
Velocity kinematics
MPI Communication
Industrial communication
Computer vision
Neural network
Fuzzy logic
Dh parameter application
Lectue five

Recently uploaded (20)

PPTX
ASME PCC-02 TRAINING -DESKTOP-NLE5HNP.pptx
PDF
Unit1 - AIML Chapter 1 concept and ethics
PDF
Computer System Architecture 3rd Edition-M Morris Mano.pdf
PDF
Design Guidelines and solutions for Plastics parts
PPTX
Petroleum Refining & Petrochemicals.pptx
PDF
Computer organization and architecuture Digital Notes....pdf
PDF
August 2025 - Top 10 Read Articles in Network Security & Its Applications
PPTX
Feature types and data preprocessing steps
PPTX
Information Storage and Retrieval Techniques Unit III
PPTX
CN_Unite_1 AI&DS ENGGERING SPPU PUNE UNIVERSITY
PPTX
mechattonicsand iotwith sensor and actuator
PDF
null (2) bgfbg bfgb bfgb fbfg bfbgf b.pdf
PDF
LOW POWER CLASS AB SI POWER AMPLIFIER FOR WIRELESS MEDICAL SENSOR NETWORK
PPTX
Chemical Technological Processes, Feasibility Study and Chemical Process Indu...
PDF
distributed database system" (DDBS) is often used to refer to both the distri...
PPTX
ai_satellite_crop_management_20250815030350.pptx
PPTX
Principal presentation for NAAC (1).pptx
PPTX
Module 8- Technological and Communication Skills.pptx
PDF
UEFA_Carbon_Footprint_Calculator_Methology_2.0.pdf
PPTX
Management Information system : MIS-e-Business Systems.pptx
ASME PCC-02 TRAINING -DESKTOP-NLE5HNP.pptx
Unit1 - AIML Chapter 1 concept and ethics
Computer System Architecture 3rd Edition-M Morris Mano.pdf
Design Guidelines and solutions for Plastics parts
Petroleum Refining & Petrochemicals.pptx
Computer organization and architecuture Digital Notes....pdf
August 2025 - Top 10 Read Articles in Network Security & Its Applications
Feature types and data preprocessing steps
Information Storage and Retrieval Techniques Unit III
CN_Unite_1 AI&DS ENGGERING SPPU PUNE UNIVERSITY
mechattonicsand iotwith sensor and actuator
null (2) bgfbg bfgb bfgb fbfg bfbgf b.pdf
LOW POWER CLASS AB SI POWER AMPLIFIER FOR WIRELESS MEDICAL SENSOR NETWORK
Chemical Technological Processes, Feasibility Study and Chemical Process Indu...
distributed database system" (DDBS) is often used to refer to both the distri...
ai_satellite_crop_management_20250815030350.pptx
Principal presentation for NAAC (1).pptx
Module 8- Technological and Communication Skills.pptx
UEFA_Carbon_Footprint_Calculator_Methology_2.0.pdf
Management Information system : MIS-e-Business Systems.pptx

ERROR

  • 1. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 1/17 ERROR & TROUBLESHOOTINGERROR & TROUBLESHOOTING SIEMENS SIEMENS
  • 2. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 2/17 SIEMENS Objectives - Learn How to Classify Errors. - Module Information & Diagnostic Buffer. - Detect Error Through Stacks. - Hardware Diagnostic Through Hardware Configuration. - Variable Table & Cross Reference. - Track Errors Through Blocks (Go To & Compare)
  • 3. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 3/17 Categories of Errors Errors that are detected by the PLC‘s operating system and normally cause the CPU to go into the Stop state. - Module failure - Short-circuit in signal cables - Scan time overrun - Programming error (accessing a non-existent block) Functional errors, that is, the CPU processes the program as usual, but thedesired function is either not executed at all or it is executed incorrectly. - Process fault, Ex. wiring error - Logical programming error (not detected during creation and startup) SIEMENS
  • 4. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 4/17 x x+1x x+1 Error detected by the System: General Rule: CPU in STOP (such as accessing a non-existent DB) (Diagnostic interrupt of a signal module) Debugging Tools: • Module Information - Diagnostic buffer - I STACK - B STACK - L STACK • Hardware Diagnostics Error Functional Error: General Rule: CPU in RUN (process fault, such as a wire break) (logical programming error, like a double assignment) Debugging Tools: • Monitor / Modify Variable • Monitor Blocks (Block Status) • Reference Data SIEMENS
  • 5. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 5/17 Module Information SIEMENS
  • 6. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 6/17 Module Information, Diagnostic Buffer The diagnostic buffer is is a FIFO buffer in the CPU. The diagnostic buffer contains all diagnostic events in the order in which they occurred. The diagnostic buffer cannot be deleted by a memory reset. All events can be displayed on the programming device in plain text and in the sequence in which they occur. Details on Event When you select an event, the following additional information is supplied in the "Details on Event" box Help on Event When you click on the button, help on the event selected in the list is opened. Open Block When you click on the button, the block in which the interruption occurred can be opened online SIEMENS
  • 7. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 7/17 Interpreting Messages, Diagnostic Buffer After the restart, the error occurred and caused entries no. 2 and 3. Event No. 2: the CPU goes into the STOP mode because the associated error OB (OB 121) was not loaded into the controller. Event No. 3: the actual cause of error, FC is not loaded to the CPU SIEMENS
  • 8. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 8/17 Opening a Block Containing an Error For errors that were triggered by a faulty instruction in the user program, you can open the interrupted block by clicking on the "Open Block" button. If the STL language is selected, the cursor is positioned directly in front of the instruction that caused the interruption. In LAD/FBD, the network causing the interruption is displayed. SIEMENS
  • 9. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 9/17 B Stack The block stack (B stack) is a graphic representation of the call hierarchy, that is, the sequence and nesting of the called blocks up to the point of interruption. The B stack also contains a listing of all interrupt and error OBs as well as the open DBs. The program execution was interrupted in the block shown at the bottom of the list. In the slide you can see that the interruption occurred in the block OB1. When a parameter-assignable block is called several times, the information, after which block call the program execution was interrupted, is relevant for troubleshooting, since the cause of the interruption can lie in the passing of faulty actual parameters by the calling block. SIEMENS
  • 10. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 10/17 I Stack The interrupt stack (I Stack) always refers to an execution level. Before you can open the I Stack, the organization block concerned must be selected in the B Stack. The "Point of Interruption" field gives you information about: • The interrupted block, with the option of opening it directly (the cursor is then located directly in front of the faulty instruction), • The priority class of the OB, whose execution level was interrupted, • Open data blocks with their numbers and sizes. SIEMENS
  • 11. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 11/17 L Stack The current values of the temporary variables for blocks not ended at the time of interruption are contained in the L Stack. SIEMENS
  • 12. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 12/17 Displaying the Hardware Diagnostics SIEMENS
  • 13. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 13/17 Monitor/Modify Variables SIEMENS
  • 14. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 14/17 Monitor Modify Update Monitor Update Modified values Trigger point "Beginning of Scan Cycle" PII PIQ Trigger point "End of Scan Cycle" Trigger point "Transition to STOP" Cyclic program execution Triggering Point for Monitor/Modify Variables SIEMENS
  • 15. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 15/17 Overwriting Variable Using Force Variables SIEMENS
  • 16. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 16/17 Testing & Monitoring Block Status SIEMENS
  • 17. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 17/17 Trigger Condition For Block Monitoring SIEMENS
  • 18. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 18/17 Display Refrance Data SIEMENS
  • 19. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 19/17 Display Cross Refrance Data SIEMENS
  • 20. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 20/17 Assignment Of In/Out, Bit Memory, Timers & Counters SIEMENS
  • 21. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 21/17 Program Structure SIEMENS
  • 22. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 22/17 Unused Symbol In Symbol Table SIEMENS
  • 23. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 23/17 Filtering Cross Reference SIEMENS
  • 24. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 24/17 Find In Reference Data SIEMENS
  • 25. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 25/17 Editing Blocks Using Cross Reference SIEMENS
  • 26. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 26/17 Go To Location From Function To Function SIEMENS
  • 27. September 28, 2018SIMATIC S7 SIEMENS LTD EGYPT 27/17 Comparing Blocks SIEMENS

Editor's Notes

  • #4: Monitoring Functions Diagnosis is important in the operating phase of a system or machine. Diagnosis usually occurs when a problem (disturbance) leads to standstill or to the incorrect functioning of the system or machine. Due to the costs associated with downtimes or faulty functions, the associated cause of the disturbance has to be found quickly and then eliminated.
  • #6: Module Information The Module Information function reads the most important data from the directly connected module. You will find additional information in the individual tabs: General: Among other things, the module description, hardware and firmware versions Diagnostic Buffer: It contains all diagnostic events in the order they occurred. All events are listed in plain text and in the order they occurred in the display. Memory: Size and usage of the EPROM load memory, RAM load memory and the work memory. Scan Cycle Time: Displays the monitoring time selected, the shortest, the longest and the current cycle time Time System: Displays the real-time clock and the integrated run-time meter Performance Data: Displays the integrated system blocks and the available organization blocks as well as address areas (I,Q,M,T,C,L) Communication: Displays the performance data of the communication interfaces and the connection overview Stacks: Information on the contents of the I Stack, B Stack and L Stack. For this, the CPU must be in the STOP state or have reached a breakpoint.
  • #7: Diagnostic Buffer The diagnostic buffer is is a FIFO buffer in the CPU‘s battery-backed memory area. The diagnostic buffer contains all diagnostic events in the order in which they occurred. The diagnostic buffer cannot be deleted by a memory reset. All events can be displayed on the programming device in plain text and in the sequence in which they occur.
  • #9: Opening a Block For so-called synchronous errors, that is, for errors that were triggered by a faulty instruction in the user program, you can open the interrupted block by clicking on the "Open Block" button. If the STL language is selected, the cursor is positioned directly in front of the instruction that caused the interruption. In LAD/FBD, the network causing the interruption is displayed.
  • #11: The contents of all relevant registers at the time of the interruption are displayed in the I Stack screen: •AccumulatorsYou can select the numbers format for displaying the accumulator contents in the "Display Format" list. •Address RegisterYou can select the numbers format for displaying the address register contents in the "Display Format" list. •Status WordBits 0 to 7 of the status word are displayed. They are identified with abbreviations according to their meaning.
  • #13: Diagnosing Hardware The function opens the station that can be accessed online and gives you information about the status or operating mode of the modules. You can see that there is diagnostic information for a module when you see the diagnostic symbols that indicate the status of the associated module or the operating mode of the CPU. When you double-click the symbol, a screen with further information pops up. In the example shown, the analog input module (slot 7) has triggered a diagnostic interrupt. As a result, the CPU has gone into the STOP mode. Both modules have been given symbols accordingly. By double-clicking the CPU, you would see the diagnostic buffer. By double-clicking the analog module, you would be given the relevant diagnostic data. In the example, the external auxiliary voltage (supply voltage) of the analog module has failed.
  • #14: Monitor/Modify Variables The Variable Address Table (VAT) is used to view (monitor) and change (modify) a CPU memory area‘s address value in a defined format. The "Monitor/Modify Variables" function is started from the SIMATIC Manager or from the LAD/STL/FBD Editor. • Address: absolute address of the variable. • Symbol: symbolic name of the variable • Symbol comment: comment on the variable displayed • Display format: a data format you can choose per mouse click (such as binary or decimal), in which the contents of the variable is displayed • Status value: value of the variable in the selected status format • Modify value: value to be assigned to the variable To check the input and output wiring (regardless of the user program), you can also call the Monitor/Modify Variables tool (VAT) directly from the HWConfig tool
  • #15: Trigger Point You can establish the trigger points for Monitoring and Modifying using Variable -> Set Trigger... or by using the icon shown here on the left. The "Trigger Point for Monitoring" specifies when the values of the variables being monitored on the screen are to be updated. The "Trigger Point for Modifying" specifies when the given modify values are to be assigned to the variables being modified.
  • #16: Function With Force, you can overwrite variables with any values you like, independent of the user program. You can open only one Force Values window for a CPU. With the S7-300™, you can only force the process image inputs and outputs; with the S7-400™ you can also force bit memories and peripherals. Notes • You can only cancel a force job by selecting the Variable -> Stop Forcing menu option • You cannot undo "Forcing" with the Edit -> Undo menu option. • You cannot cancel the force job by closing the Force Values window or by exiting the "Monitor/Modify Variables" application.
  • #20: Area of Use The Cross References (list) gives you information about how which addresses are used in which blocks. Thus, you can find out, for example, where in the entire user program a memory bit is (double) assigned. You open the cross references with View -> Cross References or by clicking the icon you see here on the left.
  • #24: Filtering Cross References You can also use the Filter function to display individual addresses or address areas separately. You access the Filter reference data dialog through the View menu. The entries in the Filter Dialog have the following meaning: •…with NumberThe filter area specifies the address area to be displayed. You can also specify several partial areas. The filter area entry "10-50; 70; 100-130" means that the address 70 and the address area from 10 to 50 and from 100 to 130 is to be displayed.