110• Components of WAGO-I/O-PRO 32

Managing Projects

Location of the find in the Declaration (Decl) or in the Implementation (Impl) portion of a POU

Line and network number if any

The full line in the text editors

Complete text element in the graphic editors

x Message window with search result display

If you double-click the mouse on a line in the message window or press <Enter>, the editor opens with the object loaded. The line concerned in the object is marked. You can jump rapidly between display lines using the function keys <F4> and <Shift>+<F4>.

4.3.22'Project' 'Global replace'

With this command you can search for the location of a text in POUs, data types, or the objects of the global variables and replace this text by another. This is executed in the same way as with 'Project' 'Global Search' or 'Edit' 'Replace'. The libraries, however, are not offered for selection and no display in the message window is possible.

Results are displayed in the message window.

4.3.23'Project' 'Check'

Each of these functions tests the state of the most recent compilation. The project must therefore have been compiled error-free at least once, before the test can be carried out; if not, the menu items are "greyed out".

4.3.23.1Unused Variables

This function in the 'Project' 'Check' menu searches for variables that have been declared but not used in the program. They are outputted by POU name and line, e.g.: PLC_PRG (4) – var1. Variables in libraries are not examined.

Results are displayed in the message window.

4.3.23.2Overlapping memory areas

This function in the 'Project' 'Check' menu tests whether in allocation of variables via the "AT" declaration overlaps have arisen at specific memory areas. For example, an overlap occurs when allocating the variables "var1 AT %QB21: INT" and "var2 AT %QD5: DWORD" because they both use byte 21. The output then appears as follows:

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32

%QB21 is referenced by the following variables:

PLC_PRG (3): var1 AT %QB21

PLC_PRG (7): var2 AT %QD5

Results are displayed in the message window.

4.3.23.3Access conflict

This function in the 'Project' 'Check' menu searches for memory areas which are referenced in more than one task. No distinction is made here between read and write access. The output is for example:

%MB28 is referenced in the following tasks:

Task1 – PLC_PRG (6): %MB28 [read-only access]

Task2 – POU1.ACTION (1) %MB28 [write access]

Results are displayed in the message window.

4.3.23.4Multiple writes to output

This function of the 'Project' 'Check' menu searches for memory areas to which a single project gains write access at more than one place. The output then appears as follows:

%QB24 is written to at the following locations:

PLC_PRG (3): %QB24

PLC_PRG.POU1 (8): %QB24

Results are displayed in the message window.

4.3.23.5User groups

In WAGO-I/O-PRO 32 up to eight user groups with different access rights to the POUs, data types, visualizations, and resources can be set up. Access rights for single objects or all of them can be established. Only a member of a certain user group can open a project. A member of such a user group must identify himself by means of a password.

The user groups are numbered from 0 to 7, whereby the Group 0 has the administrator rights, i.e. only members of group 0 may determine passwords and access rights for all groups and/or objects.

When a new project is launched, then all passwords are initially empty. Until a password has been set for the 0 group, one enters the project automatically as a member of the 0 group.

WAGO-I/O-SYSTEM 759 WAGO-I/O-PRO 32