×
Siemens Industry Online Support
Siemens AG
Entry type: FAQ Entry ID: 21671563, Entry date: 10/20/2014
(13)
Rate

How do you monitor a block with the desired call environment in STEP 7?

  • Entry
  • Associated product(s)

Instructions
When a block is called multiple times, there is a way of monitoring the block at a specific call. Proceed as follows to monitor a block with the desired call environment.

Preparation

  1. Load your project into the CPU and open the desired block.
  2. In the "Test" menu you select the command "Mode..." and in the "Mode" dialog you enable the "Test mode" option.
  3. Confirm with "OK".
  4. In the "Test" menu you select the "Call Environment..." command. If a message appears asking you whether you want to generate the reference data, acknowledge this with "Yes".
  5. STEP 7 provides the following four ways of defining the trigger conditions as described below.
Call-up path from cross-references
In the "Call Environment of the Block" dialog you get a display of the call-up paths of the current block determined by the Reference Data function.

The following instructions start with Step 6. Steps 1 to 5 were described in this entry under Preparation.

  1. Enable the "Call-up Path" function and select the "From Cross-References" tab.
  2. Click the check box in front of the the displayed blocks to select the desired call-up path.
  3. Disable the "Call-up Path" function if you want to clear the call-up path conditions.


Fig. 01

Manual call-up path
Here you can select the call-up path of the current block manually and also specify call-up paths that cannot be displayed in the "From Cross-References" tab, because when called, the block number is generated dynamically only during runtime.

The following instructions start with Step 6. Steps 1 to 5 were described in this entry under Preparation.

  1. Enable the "Call-up Path" function and select the "Manual" tab.
  2. In the right field you mark the required blocks and then click on "Add" to add them to the call-up path. If you want to delete blocks from the call-up path, mark them in the left field and click "Delete".
  3. Disable the "Call-up Path" function if you want to clear the call-up path conditions.


Fig. 02

Open data blocks
Here the call environment is defined by specifying one or two data blocks. Status recording is triggered when the block to be tested has been called with the data blocks specified. 

The following instructions start with Step 6. Steps 1 to 5 were described in this entry under Preparation.

  1. Enable the "Open Data Blocks" option.
  2. Specify the number of the global DB in the bottom left field and/or the number of the instance DB in the bottom right field.
  3. Disable the "Open Data Blocks" option if the data block condition is to be cleared.


Fig. 03

Monitoring with call-up path from the calling block
The program status of a called block can be displayed directly from its call-up. In this way you can monitor a block instance also when the block to be monitored is called multiple times from the same block.

The following instructions start with Step 6. Steps 1 to 5 were described in this entry under Preparation.

  1. Open the calling block and in the "Test" menu you select the "Mode..." command.
  2. Select "Test Mode" and close the dialog with OK.
  3. Transfer and load the block once again into the CPU.
  4. Right-click the call-up instruction and in the pop-up menu that opens you select the "Called Blocks > Monitor with Call-up Path" command.


Fig. 04

The called block is then opened. The call-up with address as criterion is entered in the trigger conditions of the block and the status for this instance of the block is enabled. Any existing trigger conditions for data blocks are retained unchanged and have to be manually disabled if no longer desired.

Notes on operating modes

  • Test mode
     All the test functions can be used without restriction. Great increases in the CPU cycle time might occur, because, for example, the status of statements in programmed cycles is determined each cycle.
  • Process mode 
    The Program Status test function is limited in order to ensure the least possible load on the cycle time. Therefore, no call-up conditions are permitted, for example. The status display of a programmed cycle is interrupted at the return point. The test function "HALT" and step-by-step program run cannot be executed.

If the operating mode has been defined when assigning the CPU parameters in the Hardware Configuration (not relevant for S7-400 and CPU 318-2), you only have to change the operating mode in the CPU properties of the Hardware Configuration. 


Fig. 05

Note
The functionality described is unlimited with S7-400, with S7-300 only from release 10/2000 onwards.

Note on S7-1200
For S7-1200, monitoring with desired call-up environment is not possible with STEP 7 V5.x. For this you need STEP 7 (TIA Portal) V13 onwards. This functionality is only supported with the S7-1200 CPU modules from firmware V4.0 onwards.

Creation Environment
The screens in this FAQ response were created with STEP 7 V5.5 + SP2.

Security information
In order to protect technical infrastructures, systems, machines and networks against cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art IT security concept. Siemens’ products and solutions constitute one element of such a concept. For more information about cyber security, please visit
https://www.siemens.com/cybersecurity#Ouraspiration.