-6
Proceed as follows:
Close “Parameterize FM 357-2” and “S7 Hardware Configuration”.
Open example project “zEn16_01_FM357-2_BF_EX” in the SIMATIC Manager by selecting
File
Open...
Projects
.
Select the S7 directory “EXAMPLES” in this project. This directory contains:
a “Symbols” file, a “Sources” directory and a “Blocks” directory.
Select the “Symbols” file and copy it to your project under
SIMATIC 300-Station
CPUxxx
S7
Program
.
Open the “Sources” directory and copy the STL sources “example3”, “ob_example” and “userdb” to
the “Sources” directory of your project. Open the “Blocks” directory and copy all blocks to the “Blocks”
directory of your project.
Open the copied STL source “ob_example” in your project (“Sources” directory)..
When calling FC 1 in the OB 100, enter the FM 357-2 module address under FMLADDR (in the exam-
ple: 256). Change the call “CALL EXAMPLE1” in OB 1 to “CALL EXAMPLE3”.
Select menu commands
File
Save
and
File
Compile
to generate organization blocks (OB 1,
OB 82, OB 100) from the STL source.
Close the Editor.
Go to the Blocks directory in the SIMATIC Manager by selecting
SIMATIC 300-Station
CPUxxx
S7 Program
Blocks
. Load all S7 blocks (and system data) stored under Blocks to the CPU (CPU in
the STOP state) by selecting menu commands
Target system
Load
.
Switch your CPU to the RUN-P state.
“JOG” mode is preset when the FM 357-2 has powered up successfully.
Select
SIMATIC 300-Station
CPUxxx
S7 Program
Blocks
in your project and start the
“Control and Monitor Variables” tool (required for monitoring/controlling the axis) via the menu
Target
System
Monitor/Control Variables
.
Enter the following markers in the “Operand” column:
DB115.dbx11.0 (CTR_EN_AX3 – Controller enable axis 3)
DB115.dbx11.1 (START – Start of CPU axis 3)
DB115.dbx11.5 (ERR – Error CPU axis 3)
DB115.dbx11.6 (INPOS – CPU axis 3 position reached)
DB115.dbx11.7 (ACTIV – CPU axis active)
DB115.dbb10 (ERR_NO – in the case of an error, error number of the CPU axis)
Establish the connection to the CPU via the menu
Target System
Establish Connection to
Di-
rectly Connected CPU
.
By selecting commands
Variables
View
, you can now monitor these operands cyclically.
The operands are updated once for monitoring when you select commands
Variables
Update Sta-
tus Values
.
In order to start the third axis, enter the value “2#1” in the line of the marker DB115.dbx11.0 under the
column “Control Value”. The controller enable signal of the axis is thus set. Then enter the value “2#1”
in the line DB115.dbx11.1 in order to start the CPU axis 3.
Set the marker cyclically by selecting menu commands
Variables
Control
or
set the marker once by selecting menu commands
Variables
Activate Control Values
.
The bit “ACTIV”=TRUE indicates that the axis is being positioned. When the position has been
reached (“INPOS”=TRUE) without any error, positioning is terminated through resetting of the control
signal “Start” = FALSE. If an error occurred during positioning (“ERR” = TRUE), this error is stored
intermediately in the byte “ERR_NO” for evaluation.
Note:
After the start, the axis traverses a relative (incremental) path of 300 mm with a velocity of 0.5 m/min.
The output messages “INPOS”, “ACTIV” and “ERR” indicate the various axis positions in relation with
axis positioning of the 3
rd
axis. If an error occurs during the execution (ERR = TRUE), the data byte
“ERR_NO” (DB115.dbb10) must be evaluated (see Section 6.5.1, Axis control of CPU).
– 6 –
