1 2 3 4 5 6 7 8 9 10 11 A B C FM 353 Stepper Drive Positioning Simatic
1 2 3 4 5 6 7 8 9 10 11 A B C FM 353 Stepper Drive Positioning Simatic
Product Overview
1
FM 353 Wiring
4
Stepper Drive Positioning
Module Defining Parameters
5
Programming the Technological
Functions
6
Manual
Starting up
7
Human-machine Interface
8
Description of Functions
9
Troubleshooting
11
Appendices
Technical Specifications
A
List of Abbreviations
C
Index
6ES7 353-1AH01-8BG0
09/2011 Edition
Safety Information
This Manual contains information which you should carefully observe to ensure your own personal
safety and the prevention of damage to the system. This information is highlighted by a warning
triangle and presented in one of the following ways depending on the degree of risk involved:
Danger
! indicates that death or severe personal injury damage will result if proper precautions are not taken.
Warning
! indicates that death or severe personal injury damage can result if proper precautions are not taken.
Caution
! indicates that minor personal injury can result if proper precautions are not taken.
Caution
without warning sign means that material damage can occur if the appropriate precautions are not taken.
Attention
means that an undesired result or a condition may occur if the appropriate note is not observed.
If more than one level of hazard can occur, the warning note of the correspondingly highest level is used in
all cases. If a warning note with a warning triangle warns of personal injury, an additional warning of
material damage can be included in the same warning note.
Qualified personnel
The unit may only be started up and operated by qualified personnel. Qualified personnel
as referred to in the safety guidelines in this document are those who are authorized to start up, earth
and label units, systems and circuits in accordance with relevant safety standards.
Proper use
Please note the following:
Warning
! The unit may be used only for the applications described in the catalog or the technical description,
and only in combination with the equipment, components and devices of other manufacturers as far
as this is recommended or permitted by Siemens.
It is assumed that this product be transported, stored and installed as intended and maintained and
operated with care to ensure that the product functions correctly and safely.
Trademarks
All names marked with the copyright notice R are registered trademarks of SIEMENS AG.
Other names in this publication might be trademarks whose use by a third party for his own purposes
may violate the rights of the registered holder.
Information
This manual contains all information about the FM 353 module:
S Hardware and functions
S Parameterization
S Human-machine interface
S S7 blocks
S Safe design
User requirements
The present manual describes the hardware and functions of the FM 353
To set up, program and start up a SIMATIC S7-300 with the FM 353, you will need
a knowledge of:
S The SIMATIC S7
Installation manual S7-400/M7–400 Programmable Controller, Hardware and
Installation
S Your programming device (PG)
S How to perform programming with STEP 7
S How to configure an operator panel interface.
FM 353 users
The structure and presentation of the information in the manual are oriented to the
intended uses of the FM 353, and the user ’s own activity.
It distinguishes among the following:
S Installation and wiring
These activities include installation and wiring of the FM 353.
S Parameterizing and Programming
These activities include parameterizing and programming the FM 353.
S Troubleshooting and diagnostics
These activities include detecting and correcting faults and errors
– in the hardware setup of the module and its components
– and in the programming, handling and control of module functions.
S Operation
These users operate the FM 353. The operator accordingly deals only with the
control of positioning tasks.
Technical support
If you have any technical question, please do no hesitate to contact our hotline:
Note
The country–specific telephone numbers for technical consultation can be found
on the Internet at: http://www.siemens.com/automation/service&support
Further support
We are offering courses to help you familiarize yourself with the operation of the
SIMATIC S7 programmable controller system.
Please contact your regional or the central training center in D-90027 Nürnberg,
Germany under tel. +49 911-89 53 202.
J
11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.1 Error classes and module responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11.2 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
11.2.1 Fault indication by LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
11.2.2 Diagnostic interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
11.2.3 Error messages in checkback signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
11.2.4 Message in data block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
11.2.5 Viewing the diagnostic buffer (PG/PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
11.3 Error lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
11.3.1 Diagnostic interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
11.3.2 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
A Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
B User Data Block (AW-DB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
C List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Multi-rack configurations
A SIMATIC S7-300 CPU may run up to four racks with as many as eight bus sta-
tions each (see Figure 1-1).
OP PG
MPI
Operator panel Programming device
Backplane Rack 3
bus
IM SM SM SM FM SM SM SM
dig./anal. dig./anal. dig./anal. dig./anal. dig./anal. dig./anal.
24 V
Rack 2
IM SM SM SM FM SM SM SM
dig./anal. dig./anal. dig./anal. dig./anal. dig./anal. dig./anal.
24 V
stepper drive
Rack 1
IM SM SM SM FM 353 SM SM SM
dig./anal. dig./anal. dig./anal. dig./anal. dig./anal. dig./anal.
24 V
Rack 0 Distributed I/Os,
L2-DP with IM interface
module
PS 24 V SIMATIC IM SM SM SM FM 353
2/5/10 A S7-300 CPU dig./anal. dig./anal. dig./anal.
System overview
A complete positioning controller using the FM 353 consists of a variety of individ-
ual components, which are shown in Figure 1-2.
Configuration package
DIN rail
SIMATIC S7-300
PS
CPU
IM SM SM
FM 353
SM SM
Power section
e.g.
FM STEPDRIVE
e.g. touch probe
MPI connection
The FM can service up to 3 MPI nodes (PCs, programming devices or OPs) simul-
taneously.
Components
The most important components and their functions are listed in Table 1-1.
Component Function
DIN rail ... the module mounting rack for the S7-300.
FM 353 ... the positioning module. It is controlled by the S7-300 CPU.
CPU ... executes the user program; powers the S7-300 backplane
bus at 5 V; and communicates with the programming device
and the operator panel via the MPI interface.
Power supply (PS) ... converts line voltage (120/230 V AC) to 24 V DC operating
voltage to power the S7-300.
Signal modules (SM) ... adapts various process-signal levels to the S7-300
Interface module (IM) ... connects the individual cells of an S7-300 with
one another (applies to multi-rack configuration; see Figure
1-1).
Programming device (PG) ... configures, parameterizes, programs and tests the S7-300
and the FM 353.
Operator panel (OP) ... the interface to the machine. It serves for operation and
monitoring. It is not an absolute prerequisite for operation of
an FM 353.
Power section ... actuates the motor.
Motor ... drives the axis.
Configuration package ... A CD-ROM containing:
S An FC block package
S MD DBs (for start-up of stepper motor)
S The parameterization tool ”Parameterize FM 353”
S A preconfigured operator interface for the COROS series
OP 07 and OP 17
S A manual in PDF format
S Getting Started in PDF format
CPU FM 353
Human-machine
interface
Creation of the
user program Parameterization, e.g.:
testing and diag- S Machine data
nostics
S Increments
OP
S Tool offset data
S Traversing programs
S Status messages
PG (STEP 7)
DIN rail
STEP.CONTR.X2
SF Front connector
1
Status and DC5V
2
3 I0
error displays DIAG 4 I1
5 I2
6 I3
7
8
9 RM
1 0
1
Display for digital I/O
1 Q0
Drive port X2 1 2 Q1 modules
1 3 Q2
1 4 Q3
1 5
1 6
1 7
1 8
1 9
2 0
I/O port X1
Ports
A description of the ports is provided in Table 1-2.
Ports Description
Bus connector – Back connector to continue the S7 LAN from module to module
SIMATIC port
Drive port 15-pin male sub-D connector (X2) to connect the drive unit
I/O port 20-pin male front connector (X1) to connect the load power
supply and for digital input and output wiring
LED indicators
Twelve LEDs are arranged on the front panel of the FM 353. Table 1-3 describes
these LEDs and what they mean.
LED Significance
SF (red) - This LED indicates an error condition in the FM 353.
Group error (see Troubleshooting, Chapter 11)
5 V DC (green) - This LED indicates that the hardware is ready for operation.
Logic power supply is
ON
DIAG (yellow) - This LED indicates various diagnostic states
Diagnostics (see Troubleshooting, Chapter 11)
I0 – I3 (green) - These LEDs indicate which input is ON.
Digital inputs
Q0 – Q3 (green) - These LEDs indicate which output is ON.
Digital outputs
RM (green) - This LED indicates that the input is activated.
Input, controller mes- (see Section 4.4)
sage
SIEMENS
Product status
Marks and approvals
Order number Module identifier
Summary
The FM 353 module performs the following functions:
S Mode control
S Determining position
S Stepper motor control
S Digital inputs and outputs
S Settings and functions that do not depend on operating mode
S Software limit switches
S Process interrupts
S Block sequence control
S Diagnostics and troubleshooting
S Data storage on the FM 353
Mode control
The operating mode is specified to the FM 353 by way of the user program.
The FM 353 has the following modes available:
S Jogging
S Open-loop control
S Reference point approach
S Incremental mode, relative
S MDI-Manual Data Input)
S Automatic
S Automatic single block
Determining position
The control frequency pulses emitted by the FM 353 are added internally to form a
position actual value.
Digital inputs/outputs
Four digital inputs and four outputs can be used as specified by the user.
You might connect:
S Reference-point switches
S Switches for external starting
S Touch probes
S Position reached, Stop (“PEH”)
S Forward/backward rotation
The switching function is assigned to a given I/O number by way of the machine
data.
Process interrupts
Process interrupts are triggered by such events as:
S Position reached
S Length measurement completed
S On-the-fly block change
S Inprocess measurement
Process interrupts are selected by way of machine data.
s
Dx
Position A Position B
Power grid
EMERG. STOP CPU
FM 353
Drive port
Safety de-
vice Power section
Parameterize PG
Movement
Motor M
Mechanical transmis-
sion elements
Safety device
“Parameterize FM 353”
FM 353
The FM 353 generates the following for the power section:
S Control frequency
S Direction signal
S Special control signals
Power section
The power section processes the control signals and supplies power to the motor.
Motor
The motor is connected, either directly or by way of mechanical transmission ele-
ments, to the machine component to be moved.
Peripherals
All other additional equipment is covered by the term peripherals.
Peripherals mainly include:
S Limit switches to limit the positioning range (safety devices).
S A programming device (PG) and the “Parameterize FM 353” parameterization
software.
J
Overview
The FM 353 is intended for installation as an I/O module in the SIMATIC S7-300
programmable logic controller.
Mechanical set-up
The options for the mechanical set-up and its configuration are described in the
manual S7-300 Programmable Controller; Hardware and Installation.
Below, we give only a few supplementary pointers.
Installation position
The module should preferably be installed horizontally.
In vertical installations, please observe the ambient temperature restrictions
(max. 40 °C).
Rules
No particular protective measures (EGB Guidelines) are necessary for the installa-
tion of the FM 353.
Warning
! Install the FM 353 only after all power to the S7-300 has been turned OFF.
Tools required
A 4.5 mm (.18 inch) screwdriver.
Procedure
To install the FM 353:
1. The FM 353 comes with a bus connector. Plug this into the bus plug of the
module to the left of the FM 353. (The bus plug is on the back; you may have to
loosen the module already in place.)
If further modules are to be mounted to the right, plug the bus connector of the
next module into the right backplane bus connector on the FM 353.
If the FM 353 is the last module in the rack, do not connect this bus connector .
2. Hook the FM 353 onto the rail and swing it down into position.
3. Screw the FM 353 down (torque approx. 80-110 Nm).
4. After the modules have been mounted, you can also assign each of them a slot
number. Slot labels for this purpose are enclosed with the CPU.
The numbering scheme and how to plug in the slot labels are described in the
installation manual S7-300 Programmable Controller, Hardware and Installation,
for the numbering scheme to follow and how to apply the slot labels.
Note
The slot determines the initial address of each module. To find out how to allocate
the module start address, please refer to the installation manual S7-300 Program-
mable Controller, Hardware and Installation, Order No.: 6ES7 030-0AA01-8AA0.
The FM 353 is addressed in the same way as an analog module.
Rules
No particular protective measures (EGB Guidelines) are necessary for the removal
of the FM 353.
Warning
! Remove the FM 353 only after all power to the S7-300 has been turned OFF.
Tools required
A 4.5 mm (.18 inch) screwdriver.
Procedure
To remove the FM 353:
1. Open the front doors. If necessary, remove the labeling strips.
2. Detach the power-supply connections from the terminal block.
3. Detach the sub-D plug from the drive unit.
4. Release the protective device on the front connector and unplug it.
5. Loosen the fastening screws and swing the module up and out.
Overview
If a defective FM 353 has to be replaced, and no programming device/PC is avail-
able for parameterization, or the module is to be replaced while the system is
switched on, please note the following start-up requirements (CPU, FM):
S An SDB w 1 000 should be generated in order to complete the startup (for stor-
ing the parameter data); see Section 5.5.
S In the user program:
– Interrupt communication with the FM 353 before removing the old FM, and
resume communication after installing the new FM.
– If data/parameters are modified during operation and stored retentively on
the FM, please follow the instructions in Section 9.3.1.
Replacing an FM 353
To replace a parameterized but defective FM 353:
1. Replace the FM 353 when the system is switched off (CPU, FM)
Yes
Reparameterization of FM
FM 353 parameter- → PG/PC required
ized automatically
FM 353 ready
Fig. 3-1 Replacing the FM 353 with the system switched off
Safety rules
In order to ensure the safe operation of your plant, you should introduce the follow-
ing additional measures, and adjust them appropriately to your system’s condi-
tions:
S An EMERGENCY STOP concept meeting appropriate safety regulations (e.g.
European standards EN 60204, EN 418 and associated standards).
S Additional measures for limiting the end position of axes
(e.g. hardware limit switches).
S Equipment and measures for protecting the motors and power electronics in
accordance with the installation guidelines for FM STEPDRIVE/SIMOSTEP.
We also recommend you carry out a risk analysis in accordance with basic safety
requirements / Appendix 1 of the EC machine directive, in order to identify sources
of danger affecting the complete system.
Further references
Please refer also to the following chapters in the manual S7-300 Programmable
Controller, Hardware and Installation:
S Lightning protection and overvoltage protection: Chapter 4.2
S Guidelines for handling of electrostatic sensitive devices (ESDs): Appendix B.
S Configuring the electrical installation: Chapter 4.
For further information about EMC guidelines, we recommend the description in:
Equipment for Machine Tools, EMC guidelines for WS/WF equipment, Order No.:
6ZB5 440-0QX01-0BA1.
Summary
Figure 4-1 shows how the individual components of the positioning controller with
FM 353 are linked together.
OP PG
Front connector
SIEMENS
SIMATIC S7-300
External 24 V
power supply CPU FM 353
MPI connecting cable
Note
The device is designed for operation with safety extra–low voltage (SELV). This
means that only safety extra–low voltages (SELV) complying with
IEC950/EN60950/VDE0805 may be connected to the power supply terminals.
The power unit for supplying the device must comply with NEC Class 2 as de-
scribed by the National Electrical Code(r) (ANSI/NFPA 70).
The power of all connected power units in total must correspond to a limited power
source (LPS).
Connecting cables
Table 4-1 lists the connecting cables for a positioning controller with the FM 353.
Front connector
You need a 20-pin screw-type front connector for wiring the digital I/Os. It must be
ordered separately.
Order No.: 6ES7 392-1AJ00-0AA0
see Catalog ST 70, Order No. E86060-K4670-A101-AV
see Catalog NC 60.1, Order No. E86060-K4460-A101-AV
Connector position
Figure 4-2 shows the installation position and identification of the plug on the mod-
ule.
STEP.CONTR. X2
1
9
15
8
FM 353
Connector pinout
Connector identifier: X2 STEP.CONTR.X2
Connector type: 15-pin sub-D plug connector
Signal names
PULSE, PULSE_NC Lock signal, true and negated
DIR, DIR_N Direction signal, true and negated
ENABLE, ENABLE_N Enable signal, true and negated
PWM/BOOST, PWM_N/BOOST_N Current control, true and negated
READY1_N Ready message
GND Signal ground
Signal type
O Output
I Input
Note
The active level of each signal can be defined in MD37 (see Section 5.3.1, 9.7).
Check the technical documentation for your drive device regarding assignment of
signal levels to direction of rotation.
Output signals
Clock, directional and enable signals are provided. In addition, an additional signal
can be parameterized for current generation.
S PULSE
The clock pulses control the motor. The motor executes one increment in re-
sponse to each rising pulse edge.
This means that the number of pulses which are output determines the angle of
rotation, i.e. the distance to be traversed.
The pulse frequency determines the speed of rotation, i.e. the traversing speed.
S DIRECTION
The signal levels which are output determine the direction of rotation of the mo-
tor.
Signal ON: “Rotation to left”
Signal OFF: “Rotation to right”
S ENABLE
The FM 353 activates this signal anytime the cyclical control operating mode is
detected.
Signal ON: Power activation is enabled
Signal OFF: Depending on power section, one or more of the
responses mentioned may occur:
– Disable pulse input
– Switch off power to motor
– Reset ring counter
– Erase error messages
S PWM / BOOST
This signal is for purposes of altering the motor current.
In the “PWM” function, a pulse width modulated signal is output which can be
used to adjust the motor current between 0 and 100%.
The “BOOST” function can be used to amplify the motor current:
Signal ON: Motor current increases
Signal OFF: Motor current normal
The use of this signal must be defined in the machine data (see MD37, Section
5.3.1, 9.7.2).
Note
In the case of asymmetrical transmission satisfactory functioning cannot be guar-
anteed because of the various non-standardized input circuits of the drive units.
Especially the lead length and the limit frequency depend on the properties of the
input circuit and the lead used. Furthermore, the reference potential GND must be
floating in order to prevent electrical interference.
+
RL
VOD
–
VOL VOH
GND
RL =
GND
RL =
GND
VOL
RL
VOH
GND GND
Input signal
READY1_N
This input is non-isolated and works with a 5V level. A floating output (switching
contact or optical coupler) may be connected. The FM 353 interprets this input as
a Ready message from the power section.
An alternative connection option is available by way of peripherals connector X1
(see Section 4.4).
Its use is defined in machine data (see MD37, Section 5.3.1, 9.7.2).
GND
l v 35 m 5V
2k
GND
l v 35 m 5V
2k
GND
Note
Use only shielded twisted pairs for lines. The shielding must be connected to the
metallic or metallized connector jacket on the controller side. To protect the analog
setpoint signal against low-frequency interference, we recommend that you not
ground the shielding on the drive-unit side.
The cable set supplied as an accessory offers excellent immunity against interfer-
ence.
e.g. FM STEPDRIVE
Front connector
Four digital inputs/outputs and one message signal from the power section may be
connected to the 20-pin front connector X1 with its single-wire terminal.
Location of connector
Figure 4-6 shows the front connector in position to be wired, and the labeling on
the inside of the front door.
Locking device
1
2
3 3
4 4
5 5
6 6
7
8 9
9
10
1 0
X1
1 1 11
1 2 12
1 3 13
1 4 14
1 5
1 6
1 7
1 8 19
1 9
2 0 20 L+
M
Connector pinout
Connector identifier: X1
Connector type: 20-pin S7 front connector for single-wire terminal
Signal names
DI1 – 4 Digital input 1 – 4
DQ1 – 4 Digital output 1 – 4
RM_P Positive input for controller message
RM_N Negative input for controller message
L+, M 24 V load power supply / ground
Signal type
Q Output
I Input
VI Voltage input
Note
The “controller message” input is configured as an isolated optical coupler input.
This allows both a current-sourcing and a current-sinking output of the power sec-
tion to be connected. For details about wiring see Section 4.5.
Actuation, current-sourcing
FM 353 Power section
X1
9 RM_P
RM_N
10
L+
19
M
20
Actuation, current-sinking
X1
9 RM_P
RM_N
10
L+
19
20 M
Fig. 4-7 Actuation of the input controller message, power supply from the
control
Actuation, current-sourcing
FM 353 Power section
X1 P24
9 RM_P
RM_N
10
M
19 L+
20 M
Actuation, current-sinking
X1
RM_P
9 P24
RM_N
10
19 L+
20 M
M
Fig. 4-8 Actuation of the input controller message, power supply from the
drive unit
Note
Make sure that the cable length between the digital outputs and the load does not
exceed a permissible max. length of 30 m.
Note
Note the SIMATIC setup guidelines. In particular, the M terminal (reference poten-
tial) must be connected with the chassis ground of the programmable controller
(M terminal on the terminal block of the S7-300 CPU).
see manual S7-300 Programmable Controller, Hardware and Installation.
Danger
! The 24 V load power supply should be a functional extra-low voltage with safe
isolation to EN60204-1, Section 6.4, PELV (with M grounding).
Note
Make sure that the interconnecting cable between power supply and load power
supply connection L+ and appropriate reference potential M does not exceed a
max. permissible length of 10 m.
SF ENCODER X3
1
2
DC5V 3
3 I0
DIAG 4 4
I1
5 I2 5
6 6
I3
7
8 9
9 RM 10
1 0
X1
1 1 Q0 11
1 2 Q1 12
1 3 Q2 13
1 4 Q3 14
1 5
1 6
1 7
1 8 AC
1 9 19 19
+
2 0 20 – 20 L+
DC24V M
FM 353
Labeling on inside of front door
Digital
outputs Shielding terminal element
Digital
inputs
e.g. touch
probe
Connecting cables
Flexible conductor, cross-sectional area 0.25...1.5 mm 2
Ferrules are not necessary.
You can use ferrules without insulating collars per DIN 46228, Shape A, long con-
figuration.
You can connect two lines measuring 0.25 – 0.75 mm 2 in a single ferrule.
Note
To provide optimum immunity to interference, shielded cables should be used to
connect touch probes or sensors.
Tools required
A 3.5 mm (.13 inches) screwdriver or power screwdriver.
Shielded cables
When using shielded cables, the following additional steps are necessary:
1. After leading the cable into the cabinet, connect the cable shielding with a
grounded shielding bus (strip the insulation from the cable itself).
For this you can use the shielding terminal element mounted on the DIN rail; it
will accept up to eight shielding terminals.
see manual S7-300 Programmable Controller, Hardware and Installation.
2. Connect the shielded line to the module, but do not connect the shielding there.
Overview
This chapter gives you an overview of how to define the parameters of the FM 353
with the “Parameterize FM 353” tool.
Rack parameterization -
Parameter-
Group selection -
ization forms
Activate interrupts
(basic parameters)
Configuration: Generate system data
Setup.exe
Module parameterization
Prerequisites
One of the following operating systems must be installed on the programming de-
vice (PG/PC):
S “MS Windows XP Professional SP2 or SP3“
S “MS Windows Server 2003 R2 SP2 standard edition as workstation computer“
S ”MS Windows 7 32 Bit Ultimate, Professional or Enterprise”
S ”MS Windows 7 64 Bit Ultimate, Professional or Enterprise”
You need the STEP 7 program (from V5.5 + HF4).
For online operation, make sure that your programming device (PG) / PC is
connected to the S7-300 CPU (see Figure 4-1). For distributed use of the FM, a
connection from the PG / PC must be established to the L2 DP network.
Installation
The entire software (parameterization tool, function blocks and preconfigured user
interface for OPs) is stored on CD ROM.
Install the software as follows:
1. Insert the CD ROM in the CD ROM drive of your PG/PC.
2. Run file Setup.exe on the CD ROM.
3. Follow the instructions displayed by the installation routine step for step.
Result: The software is installed in the following directories:
– “Parameterize FM 353” parameterization tool: [STEP7 directory]\S7FSTEP
– Technology functions:
[STEP7 directory]\S7LIBS\FMSTSV_L (library name: “FMSTSV_L”)
– Technology functions:
[STEP7 directory]\S7LIBS\FM353_354 (library name: “FM353_354”)
– User interface for OPs:
[STEP7 directory]\EXAMPLES\FM353\zDt13_02_FM353_OP_EX
– Sample applications for blocks of the FMSTSV_L library:
[STEP7 directory]\EXAMPLES\zDt13_02
STEP7 project name: zDt13_02_FM353_EX
– Sample applications for blocks of the FM353_354 library:
[STEP7 directory]\EXAMPLES\zDt13_03
STEP7 project name: zDt13_03_FM353_EX
– MD DBs (for commissioning of the stepper drive):
[STEP7 directory]\EXAMPLES\FM353\MD
Prerequisites
You have installed the software on your programming device/PC, as described in
Section 5.1.
Configuration
Before you can configure your system, you must create a project in which to save
the parameters. You will find further information on how to configure modules in
your user manual Standard Software for S7 and M7, STEP 7. The description be-
low outlines only the most important steps.
1. Start the SIMATIC Manager and open your project.
2. Insert a SIMATIC 300 station in the menu Insert > Station.
3. Select the SIMATIC 300 station. Call up the S7 hardware configuration from
the menu Edit > Open Object.
4. Select a rack.
5. Select the FM 353 positioning module with the correct order number from the
module catalog, and insert it in the hardware table as appropriate for your con-
figuration.
6. Double-click a module to configure it.
The Properties dialog box appears.
7. By clicking on the tabs in this FM 353 window (General, Addresses and Basic
Parameters), you can
– Assign a name
– Change the address of the FM as well as any input parameters for the
POS_INIT block (see Section 6.3.2)
– Configure the interrupts (diagnostic interrupt, process interrupt).
Note:
Further operation of the FM 353 is not possible with the CPU in the ST OP state.
Click the Parameters button to call up the screen for setting the parameters.
You can return to this display at any point during parameterization by selecting the
menu View > Overview.
The FM 353 module for stepper drive-controlled positioning is parameterized by
way of parameter DBs that reside in memory on the module. Here a key function is
performed by the “Machine data” data block (DB-MD), since it is always needed,
regardless of what technological function the module performs. All other parameter
DBs are only needed as a function of the technology involved.
You can now set the parameters of your module. This chapter gives you an over-
view of the parameters that can be set.
You can use the mouse to change the size of the window for entering the parame-
ter data and the size of the overview display.
Proceed as follows:
1. Position the mouse pointer on the top border of the window, so that it changes
into an arrow.
2. Press the left mouse button, and drag the pointer downwards by moving the
mouse.
3. Release the mouse button.
4. Position the mouse pointer on the bar with the name of the window.
5. Press the left mouse button, and drag the pointer upwards by moving the
mouse. When you have moved the window to the correct position, release the
mouse button.
When you have configured your project, you can call up the Properties screen in
S7 Configuration by selecting the module and activating the menu command Edit
> Object Properties.
Integrated help
The parameterization user interface has an integrated help system to support you
when you set the parameters of the positioning module. To call up the integrated
help:
S Select the menu command Help > Help Topics... or
S press the F1 key or
S select the symbol and then move to the element or window you want infor-
mation about and press the left mouse button.
Detailed data block structures and parameterization data for the individual types of
data blocks can be found in the following sections.
DB structure
Table 5-3 gives you an overview of the structure of the “machine data” data block
(DB-MD).
Entering values
In “Parameterize FM 353” select the menu File > New > Machine Data to call up
the following display.
Note
The measurement system (MD7) must match the measurement system specified
in the other DBs.
The measurement system raster (MSR) is the smallest distance unit in the active
system of measurement.
If at some point you have failed to take this precaution:
1. Delete all data blocks (which do not match the measurement system) or clear
the memory of the FM 353 completely.
2. Modify the other data blocks on the PG.
3. Reload the data blocks to the FM 353.
Dependencies
With certain combinations of machine data, restrictions in the value range arise for
non-processing of the machine data.
These dependencies are verified on acceptance of the MD DB or individual ma-
chine data, and an error message is output in the event of a violation. Some
checks are performed on the basis of internally calculated reference variables.
These reference variables and the dependency checks are described in the tables
below.
Reference variables generated internally from MD:
Generation of travel per motor revolution UMWEG
MWFAKTOR VFBABS
<1 109 / MWFAKTOR
w1 109
Verification:
MD9 check
Permissible measured value factor range: 2–14 < MWFAKTOR < 214
MD28 check
MD29 check
MD34 check
Permissible:
BYTE0(MD34) ≠ BYTE1(MD34) ≠ BYTE2(MD34) ≠ BYTE3(MD34)
MD35 check
Permissible:
BYTE0(MD35)&0x7F ≠ BYTE1(MD35)&0x7F ≠ BYTE2(MD35)&0x7F ≠
BYTE3(MD35)&0x7F
MD38 check
MD38 Permissible increment number per current-sourcing cycle
0
≠0 MD38 ≥ 4
MD40 check
Permissible frequency: MD39 ≤ MD40 ≤ MD41
MD41 check
Permissible frequency: MD41 ≤ VMAX/MWFAKTOR/60
VMAX = 500 000 000 MSR/min see Section 10.1
MD42 check
Permissible acceleration: MD41 / 200 ≤ MD42 ≤ MD392
MD43 check
MD43 Permissible acceleration
0 0
≠0 MD41 / 200 ≤ MD43 ≤ MD392
MD44 check
MD44 Permissible acceleration
0 0
≠0 MD41 / 200 ≤ MD44 ≤ MD392
MD45 check
MD45 Permissible acceleration
0 0
≠0 MD41 / 200 ≤ MD45 ≤ MD392
P1 P2
Max. frequency
tover aover
P3 P4
10 kHz/s
1 kHz/s
df/dt 10 20 40 100 Hz/s
5.3.2 Increments
DB structure
Table 5-5 gives you a general view of the structure of the “Increments” data block
(DB-SM).
Input of values
Values are input in the increments menu of the “Parameterize FM 353” parameter-
ization tool.
DB structure
Table 5-6 gives you a general view of the structure of the “tool offset data” data
block (DB-WK).
Input of values
Values are input in the tool offset data menu of the “Parameterize FM 353” para-
meterization tool.
If the additive wear value is changed online, the FM calculates the new wear pa-
rameter as an absolute value and the additive tool wear is reset to 0.
DB structure
Table 5-7 gives you a general view of the structure of the “traversing programs”
data block (DB-NC).
Overview
The FM 353 stores its parameter data internally.
In order to ensure that the parameter data are available if a fault develops on the
FM 353 and no programming device/PC is at hand, the data can be stored in a
system data block (SDB w 1 000). The CPU transfers the data stored in SDB w
1 000 to the FM 353 on each new start. If the FM 353 has no machine data or the
internal time stamp (time of creation) is invalid, the data are transferred from SDB
w 1 000 to the FM 353 and saved there.
The time stamp is renewed every time a DB (parameter data) is opened and when
a file is imported. If the contents of the DB are modified (for instance the machine
data), a new time stamp is also generated when the DB is saved or loaded.
You must ensure that the parameter data in
SDB w 1 000 always match the parameter data on the FM 353 when start-up
is complete.
Note
If parameter data are modified again in the FM following creation of SDB w 1 000,
they are overwritten when the CPU is restarted (see “Time stamp”, above).
SDB w 1 000 should therefore not be created until start-up is finished!
If you need to modify the data subsequently, you should generate SDB w 1 000
again and load it into the CPU. You can delete the previous SDB before you load
the new one, however the new SDB automatically overwrites the old one when it is
generated. The old SDB and the new SDB do not have to be allocated the same
number.
No
Overwrite this SDB?
Yes Abort
No
Delete SDB? Close the window
Yes
If the configuration is loaded from HW-CONFIG, this SDB is not loaded into the
CPU.
General remarks
The purpose of the function description of the blocks and of the interface is to illus-
trate the communication between the CPU and the FM 353 in the SIMATIC S7 pro-
grammable controller. The programmable blocks and the AW-DB (which is the in-
terface to the FM 353) make it possible for you to write your user program to suit
your particular application.
S7-300
CPU FM 353
P bus Control/check-
Standard function
back signals
blocks, user program
System data
and user DB
K bus Data blocks
MPI
Online
Offline
PG
(STEP 7)
Standard The standard function
User
function blocks and the user DB
DB
blocks are loaded into the CPU.
Setup.exe
Prerequisites
The following prerequisites must be fulfilled for the development of your user pro-
gram if you want to control the FM 353:
S You must have installed the software on the PG/PC as per Section 5.1.
The block libraries containing the basic functions are stored in the following
directories by default:
– Blocks of the “FMSTSV_L” library:
[STEP7 directory]\S7LIBS\FMSTSV_L
– Blocks of the “FM353_354” library:
[STEP7 directory]\S7LIBS\FM353_354
S The link from PG/PC to the S7 CPU must be established (see Figure 4-1).
S You must have already created your project for the SIMATIC S7 (see “FM 353,
First Steps”).
Overview
In this chapter you will find information on the following:
S Communication between the CPU and the FM 353, Section 6.1.1, p. 6-4
S Structure of a user program, Section 6.1.2, p. 6-5
S Distributed use of OB 86, Section 6.1.3, p. 6-6
S Embedding an OP, Section 6.1.4, p. 6-6
S Procedure for creating a user program, Section 6.1.5, p. 6-7
CPU FM 353
OB 40 OB 82
(process 4 bytes of OB start information Diagnostic and
(diagnostics)
interrupt) process inter-
POS_DIAG rupt information
4 bytes of OB
start information OB 1
Fig. 6-2 Overview diagram for linking the FM 353 into the user program
The diagram below provides an overview of the structure of the user program
(AWP).
Note
GET/PUT functions (SFC 72/73) from/to the FM are not guaranteed to work prop-
erly, that is to say, these functions are not supported, since they are not required.
Parameter initialization data can be modified via the “Modify parameters/data” sig-
nal (user DB, DBX39.3).
If system operation must be maintained with an FM 353 despite a faulty link be-
tween CPU and distributed I/Os (DP), OB 86 is to be linked into the user program.
In OB 86, provisions (e.g. set flag and evaluate in OB) must be made to prevent
OB 1 communication with the FM 353 in case of a failure. To enable synchroniza-
tion of the user program and the FM, the POS_INIT block (corresponding to exe-
cution in OB 100) is to be linked on re-establishing the link. Additionally, OB 122
(I/O access error) must be loaded in the CPU.
6.1.4 Embedding an OP
Part of the AW-DB, namely the “Data field for operator control/monitoring”
(DBB496 to DBB515), is used to store signals/data for an OP as per the preconfi-
gured operator interface. In order to initiate actions, the relevant signals/data have
to be transferred to the interface (relevant area in the AW-DB) via the user pro-
gram (see Section 6.7, example 4).
Note
Observe the relevant safety measures if you want to move the axis.
Overview
This chapter contains information on the following:
S Overview of the “FMSTSV_L” block library, Section 6.3.1, p. 6-9
S POS_INIT (FC 0) – Initializing the user DB, Section 6.3.2, p. 6-10
S POS_CTRL (FC 1) – Data exchange, Section 6.3.3, p. 6-12
S POS_DIAG (FC 2) – Reading diagnostic alarm data, Section 6.3.4, p. 6-22
S POS_MSRM (FC 3) – Reading measurement values, Sections 6.3.5, p. 6-25
S Interface, user data blocks (AW-DB), Section 6.3.6, p. 6-26
You can use the blocks of the “FMSTSV_L” block library as follows:
S Central configuration of the FM
S Distributed configuration of the FM via PROFIBUS DP
The table below provides an overview of the functions (FC), data blocks (DB) and
organization blocks (OB) required for communication and control of the FM 353.
Table 6-1 Standard function blocks of the “FMSTSV_L” library (overview)
1) – The block number is a default setting, block number can be changed in the SIMATIC Manager
– Symbol table entries can be changed in conjunction with symbolic programming only
Note
The symbolic block identifier is used from here on.
Function
Use the POS_INIT block to initialize specific areas of your AW-DB.
Call options
The POS_INIT block must be called once in the start-up OB 100 and in OB 86 for
”distributed configuration”.
Parameters
The Table below lists the parameters for this block.
Function description
The POS_INIT block carries out the following actions:
1. Entry of addressing values in user DB AW-DB, If parameter LADDR ≠ 0
Module address
2. Deletion of the following structures in user DB AW-DB:
– Control signals
– Checkback signals
– Initiate, Ready and Error signals for the job requests
– Single functions and single commands and their Ready and Error signals
3. If the input parameter LADDR = 0, no address is entered in the user DB. It is
assumed that the addressing values (module address) have been entered
manually via ”Parameterize FM 353” (button ”Enter Mod-Adr in user DB” in
main display).
Error evaluation
An error is signalled by the binary result BR = 0 or by RET_VAL < 0.
Possible errors are:
S Unknown channel number CH_NO and DB no. = 0 as input parameters; the
AW-DB is not initialized.
S If no AW-DB is found, the CPU goes to STOP; view the CPU’s diagnostic
buffer.
RET_VAL Error
–1 Unknown channel number
–2 DB number = 0
Function
The POS_CTRL block is the basic block for controlling the FM 353.
With the POS_CTRL block, you can:
S process read and write requests
S control the operatign modes (control and checkback signals)
The POS_CTRL block performs the following actions:
1. Synchronization with the module (only then is the exchange of signals/data pos-
sible).
2. Reading of the checkback signals. The values/signals read by the POS_CTRL
block are stored in the user data block AW-DB.
3. Transfer of the control signals from user data block AW-DB to the FM 353.
4. Carrying out of Write requests from user data block AW-DB, which includes the
transfer of associated data from AW-DB and setting of the job status for the
Write. Before the function is activated, all data required for the execution of the
intended functions must be entered in AW-DB.
5. Carrying out of Read requests from user data block AW-DB, which includes
transfer of the associated data to AW-DB and setting of the Read job status.
6. Automatic transfer of all single functions from user data block AW-DB to the
FM 353 when one or more than one setting has been changed and setting of
the Write job status (Set or Reset).
7. Automatic transfer of all single commands from user data block AW-DB to the
FM 353 and setting of the Write job status. The single commands are reset fol-
lowing the transfer.
8. Automatic reading of the error number when an operator input error, traversing
error or data error has occurred. The error number is entered in user data block
AW-DB (DBB90 to DBB97) and the Read job status set.
Call options
POS_CTRL must be called cyclically (once in the OB 1 cycle, for instance) for
each channel. Before calling the function, enter all data/signals required to execute
the intended functions in user data block AW-DB.
Parameters
The Table below lists the parameters for this block.
Return values
The function returns the following values:
RET_VAL BR Description
1 1 At least 1 job/transfer in progress
0 1 No job/transfer in progress, no error
<0 0 Error:
S Data error (AW-DB, DBX22.4)
S Communication error (AW-DB, DBW66)
Function description
The function works together with an AW-DB user data block. The DB number is
passed to the function in the DB_NO parameter when the block is called.
S Start-up
POS_CTRL acknowledges start-up of the module. During this time, the
“RET_VAL” parameter and the “Write/Read job in progress” signals (AW-DB,
DBX68.0 and DBX68.2) are TRUE.
S Control and checkback signals
When POS_CTRL is called, the checkback signals are read from the FM 353
immediately (via direct access). Since the control signals and job requests are
processed after these signals have been read, the checkback signals reflect the
status of the module before the block was called. The control signals are also
written to the FM 353 using direct access.
Depending on the chosen mode, the control signals “Start, “Negative direction”
and “Positive direction” (AW-DB, DBX15.0, 15.2 and 15.3) are reset once
start-up has actually taken place (edge formation of the signals for the FM).
For information on the generation of the checkback signals “Process” (AW-DB,
DBX13.6) and “Position” (AW-DB, DBX13.7), see “Mode control”.
S Job requests
Data interchange with the module that goes beyond control and checkback sig-
nals is handled using job requests. Simultaneously pending Write or Read re-
quests, however, can only be executed in succession, whereby one Read and
one Write request are processed in one call.
To issue a request, set the relevant initiation signal in user data block AW-DB
(DBB38 to DBB43). In the case of Write requests, you must also make the ap-
propriate data available.
The request is serviced when POS_CTRL is called. When the FM is used
centralized, a Read request is performed during the call. A Write request re-
quires at least three calls (or OB cycles) due to the acknowledgements required
from the module. The time interval between the calls should exceed the length
of one FM cycle.
When a request has been serviced, the Initiate signal is removed (does not ap-
ply to single functions).
The next job request is not determined or executed until the next block call has
been made.
For each job request, there is a Ready signal (AW-DB, DBX44.0 to 53.7) and
an Error signal (AW-DB, DBX54.0 to 63.7) in addition to the Initiate signal.
You should reset the Ready and Error signals for a job request following evalua-
tion or prior to issuing the request.
S Order in which job requests are serviced/priority
You may submit several job requests simultaneously, even together with Write
requests for single commands and single functions.
As soon as a Write request is detected (also on a signal change in the case of
single functions), it is serviced immediately upon completion of the transfer cur-
rently in progress, if any. Be sure that signals for single commands are not set
cyclically, as this could prevent other job requests from being serviced (priority).
Order/priority of Write requests:
1. Write single commands
2. Write single functions
3. Write requests.
The Write requests are serviced in the order of the Initiate signals,
which is stipulated in user data block AW-DB (from DBX38.0 to 39.7).
Order/priority of Read requests:
1. Read error code, operator/traverse errors or data errors
2. Read requests
The Read requests are serviced in the order of the Initiate signals,
which is stipulated in user data block AW-DB (from DBX42.0 to 43.6).
Jobs in
Initiate Ready Error
RET_VAL Progress
Job Request Status Signals Signals Signals
(integer) (DBX68.0
(DBB34...43) (DBB44...53) (DBB54...63)
DBX68.2)
1. Job in progress 1 1 1 – –
2. Job terminated without 0 – – 1 –
error
3. Write job terminated with –1 – – 1 1
error in this job
4. Write job aborted or not –1 – – – 1
executed
5. Read job aborted –2 – – – 1
6. Write and Read aborted –3 – – – 1
or not executed (in the
case of simultaneous job
requests)
– Irrelevant for error evaluation
Processing status
Signal Description
Write not possible = TRUE; Write request cannot be serviced in this cycle because:
(AW-DB, DBX68.1) S The axis is not initialized
S Test mode is enabled
S No operating mode is active
S The selected operating mode has not yet been set
In these cases, you can leave the Write request pending or you can cancel it.
The POS_CTRL block resets the signal when all of the above-listed condi-
tions are fulfilled.
Read not possible = TRUE; Read request cannot be serviced at this time because:
(AW-DB, DBX68.3) S The axis is not initialized
S No mode has been selected
S Test mode is enabled
In these cases, you can leave the Read request pending or you can cancel
it. The POS_CTRL block resets the signal when all of the above-listed condi-
tions are fulfilled.
Reset status/error With this signal you can reset all Ready and Error signals prior to processing
(AW-DB, DBX69.1) of the pending job requests. The signal itself is then reset by the block.
Error evaluation
Communication errors or data interpretation errors on the FM are flagged in the
Binary Result (BR = 0) and by RET_VAL < 0; see job request status.
Possible errors are:
S Data transfer error (communication is not completed) during a transfer with SFC
58/59 “WR_REC / RD_REC”. The error code is made available in user data
block AW-DB, DBW66 (RET_VAL value of these internal SFCs) (job states 4, 5
and 6, see Table 6-2, see also Error List, Section 6.8).
S Data transferred with Write are checked for data errors by the module and inter-
preted. If a data error occurs, the checkback signal “Data error” (AW-DB,
DBX22.4) is set to TRUE in user data block AW-DB (message: “Write job ter-
minated with error”). The error number, read out via an internal job request, is
entered in user data block AW-DB, DBB94 and 95 (job status 3, Table 6-2).
You will find more information on data errors in the parameter initialization tool
under the menu command Debug > Error Evaluation and in Chapter 11.
Performance in the event of an error during the servicing of a Write request (does
not apply to single functions and commands):
S The Initiate signal is removed for the errored request and the Error signal (AW-
DB, DBX54.0 to 63.7) and Ready signal (AW-DB, DBX44.0 to 53.7) are set (job
request status, point 3, Table 6-2).
S The Initiate signal is also removed for all pending Write requests and the Error
signal set (job request status, point 4, Table 6-2).
S Any pending Read requests are serviced. The error code (AW-DB, DBW66) for
each request is re-set if another error occurs.
Performance in the event of an error during the servicing of a Read request:
S The Initiate signal is removed for the errored Read and the Error signal set (job
request status, point 5, Table 6-2).
S Any pending Read requests are serviced. The error code (AW-DB, DBW66) for
each request is re-set if another error occurs.
Performance in the event of an error during servicing of single functions and
commands:
S The Write request is not serviced in its entirety, and the Error signal is set (job
request status, point 4, Table 6-2).
S The function set/reset which led to initiation of the Write request is not acti-
vated.
The checkback signals “Process in progress” and “Position reached. Stop” are not
reported back to the user program until the FM has detected and processed the
Start signal (v 2 FM cycles).
When calling the POS_CTRL block and the relevant control/checkback signals,
the subsequent signals are generated so that starting of the procedure can be de-
tected earlier than would otherwise be the case.
Signal Description
Execution started = TRUE When a mode/movement is started with the relevant
(AW-DB, DBX13.6) control signals or when the status for “Process in
progress” (AW-DB, DBX23.1) = 1
when the block is called/
“Execution started”
started
“Process in progress” when the FM starts tra-
versing movement
Position = FALSE When status signal “Position reached. Stop.” (AW-DB,
(AW-DB, DBX13.7) DBX25.7) = 0 is returned or when a mode is started
with the relevant control signals.
when the block is called/
“Position”
started
“Position reached. Stop” when FM starts traversing
movement
Single functions and single commands are also requred to control the FM 353.
All single commands and single functions that are active when the POS_CTRL
block is called are transferred. The single commands are cancelled following trans-
fer, even in the event of an error.
The functions which can be activated in the FM using single settings or single com-
mands are listed below.
In the event of a fatal error, the FM 353 generates a diagnostic interrupt (OB 82
must be embedded in the user program and the interrupt parameterization of the
FM 353 must be activated) and provides the relevant information to the local data
area. For information on diagnostic interrupts, see Section 6.5.
For further information on external channel errors (operating errors), please call the
POS_DIAG block.
Call options
POS_DIAG can be called in interrupt OB 82 or in OB 1.
Parameters
The Table below lists the parameters for the POS_DIAG block.
Function description
The function works together with an AW-DB user data block. When the function is
called, the AW-DB is forwarded with a DB_NO parameter.
Reading of the diagnostic data is started by setting the IN_DIAG parameter to
TRUE. The block resets the parameter when the request has been serviced.
The IN_DIAG parameter remains set while the request is being serviced. Transfer
of the data is terminated when the parameter is reset (IN_DIAG = F ALSE).
Error evaluation
Errors are flagged in the Binary Result (BR = 0) and by RET_VAL < 0.
Possible errors are as follows:
Data transfer error during transfers with SFC 51 “RDSYSST”. The error is made
available in the user DB AW-DB, DBW96 (see Error List, Section 6.8).
Diagnostic data
The prerequisite for the generation of a diagnostic interrupt is activation of the in-
terrupt with the aid of the appropriate parameters (see Section 5.2).
If the user program does not contain an OB 82, the CPU goes to ST OP.
The Table below contains the diagnostic information for the FM 353.
COMM_FAULT AW-DB
WTCH_DOG_FLT
INT_PS_FLT Byte.Bit: 78.0...7
EPROM_FLT
RAM_FLT
HW_INTR_FLT
Function
Use the POS_MSRM block to read the measured values from the AW-DB user
data block.
For information on process interrupts, please see Section 6.5.
For information on measured values 9.3.10.
Note
The measured values can also be read by means of POS_CTRL (Read request).
If more than one Read request is pending, this request will be processed in the
relevant order.
If the POS_MSRM block is called, the measured values are obtained irrespective
of any other Read requests currently present.
Call options
POS_MSRM can be called in OB 40 (only when FM is used centralized) if the pro-
cess interrupt was triggered (see Section 5.2), or in OB 1. POS_MSRM must not
be called in both OBs at the same time.
Parameters
The Table below lists the parameters for the POS_MSRM block.
Function description
The function works together with an AW-DB user data block. When the function is
called, the DB number is forwarded in the DB_NO parameter.
Reading of the measured value is started by setting the IN_MSR parameter to
TRUE. When the function has executed, the block resets the parameter.
The IN_MSR parameter remains set while the function is executing. Transfer of the
data is terminated is complete when the parameter is reset (IN_MSR = FALSE).
Error evaluation
Errors are flagged in the Binary Result (BR = 0) and by RET_VAL < 0.
Possible errors are as follows:
Data transfer errors during transfers with SFC 59 “RD_REC”. The error is made
available in the user data block AW-DB, DBW98 (see Error List, Section 6.8).
You can use the blocks of the “FM353_354” block library as follows:
S centralized configuration of the FM
S distributed configuration of the FM via PROFIBUS DP
Note
The blocks of the “FM353_354” block library requires the following firmware
version on the CPU:
S CPU modules with MMC with firmware V2.0 and higher
S CPU318 with firmware V3.0 and higher
The table below provides an overview of the functions (FC), function blocks (FB),
data blocks (DB) and organization blocks (OB) required for communication and
control of the FM 353.
Table 6-6 Standard function blocks of the “FM353_354” block library (overview)
1) – The block number is a default setting, block number can be changed in the SIMATIC Manager
– Symbol table entries can only be changed in conjunction with symbolic programming
Note
The symbolic block identifier is used from here on.
Block description
See Section 6.3.2.
Function
The POS_CTRL block is the basic block for controlling the FM 353.
With the POS_CTRL block, you can:
S process read and write requests
S control the operating modes (control and checkback signals)
The POS_CTRL block performs the following actions:
1. Synchronization with the module (only then is the exchange of signals/data pos-
sible).
2. Reading of the checkback signals. The values/signals read by the POS_CTRL
block are stored in the user data block AW-DB.
3. Transfer of the control signals from user data block AW-DB to the FM 353.
4. Carrying out of Write requests from user data block AW-DB, which includes the
transfer of associated data from AW-DB and setting of the job status for the
Write. Before the function is activated, all data required for the execution of the
intended functions must be entered in AW-DB.
5. Carrying out of Read requests from user data block AW-DB, which includes
transfer of the associated data to AW-DB and setting of the Read job status.
6. Automatic transfer of all single functions from user data block AW-DB to the
FM 353 when one or more than one setting has been changed and setting of
the Write job status (Set or Reset).
7. Automatic transfer of all single commands from user data block AW-DB to the
FM 353 and setting of the Write job status. The single commands are reset fol-
lowing the transfer.
8. Automatic reading of the error number when an operator input error, traversing
error or data error has occurred. The error number is entered in user data block
AW-DB (DBB90 to DBB97) and the Read job status set.
Call options
The POS_CTRL block requires an instance data block (DB) when called. The DB
IFFM_ICTRL (DB1) is part of the “FM353_354” library and at the same time inclu-
des the user interface. For more information, please refer to Section 6.4.6.
You must call the POS_CTRL block cyclically (e.g. once in the OB 1 cycle). Before
you call the function, enter all data/signals in the user DB (AW-DB) which are re-
quired to execute the intended functions.
The block does not have multiple-instance capability.
Parameters
The POS_CTRL block possesses neither input, nor output parameters.
Return values
The POS_CTRL block delivers the following return values in the RETVAL instance
variable:
RET_VAL BR Description
1 1 At least 1 job/transfer in progress
0 1 No job/transfer in progress, no error
<0 0 Error:
S Data error (AW-DB, DBX22.4)
S Communication error (AW-DB, DBW66)
Function description
The block operates with an AW-DB user data block. The DB number is determined
when calling the FB using a transferred instance DB.
S Start-up
POS_CTRL acknowledges start-up of the module. During this time, the
RETVAL parameter and the “Write/Read job in progress” signals (AW-DB,
DBX68.0 and DBX68.2) are TRUE.
S Control and checkback signals
When POS_CTRL is called, the checkback signals are read from the FM 353
immediately (via direct access). Since the control signals and job requests are
processed after these signals have been read, the checkback signals reflect the
status of the module before the block was called. The control signals are also
written to the FM 353 using direct access.
Depending on the chosen mode, the control signals “Start, “Negative direction”
and “Positive direction” (AW-DB, DBX15.0, 15.2 and 15.3) are reset once
start-up has actually taken place (edge formation of the signals for the FM).
For information on the generation of the checkback signals “Process” (AW-DB,
DBX13.6) and “Position” (AW-DB, DBX13.7), see “Mode control”.
S Job requests
Data interchange with the module that goes beyond control and checkback sig-
nals is handled using job requests. Simultaneously pending Write or Read re-
quests, however, can only be executed in succession, whereby one Read and
one Write request are processed in one call.
To issue a request, set the relevant initiation signal in user data block AW-DB
(DBB38 to DBB43). In the case of Write requests, you must also make the ap-
propriate data available.
The request is serviced when POS_CTRL is called. When the FM is used
centralized, a Read request is performed during the call. A Write request re-
quires at least three calls (or OB cycles) due to the acknowledgements required
from the module. The time interval between the calls should exceed the length
of one FM cycle.
When a request has been serviced, the Initiate signal is removed (does not ap-
ply to single functions).
The next job request is not determined or executed until the next block call has
been made.
For each job request, there is a Ready signal (AW-DB, DBX44.0 to 53.7) and
an Error signal (AW-DB, DBX54.0 to 63.7) in addition to the Initiate signal.
You should reset the Ready and Error signals for a job request following evalua-
tion or prior to issuing the request.
S Order in which job requests are serviced/priority
You may submit several job requests simultaneously, even together with Write
requests for single commands and single functions.
RETVAL Jobs in
Initiate Ready Error
instance progress
Job request status signals signals signals
variable (DBX68.0
(DBB34...43) (DBB44...53) (DBB54...63)
(integer) DBX68.2)
1. Job in progress 1 1 1 – –
2. Job completed without 0 – – 1 –
errors
3. Write job completed with –1 – – 1 1
errors in this job
4. Write job aborted or not –1 – – – 1
executed
5. Read job aborted –2 – – – 1
6. Write and Read aborted –3 – – – 1
or not executed (in case
of simultaneous job re-
quests)
– Irrelevant for error evaluation
Processing status
Signal Description
Write not possible = TRUE; Write request cannot be processed in this cycle because:
(AW-DB, DBX68.1) S The axis is not initialized
S Test mode is enabled
S No operating mode is active
S The selected operating mode has not yet been set
In these cases, you can leave the Write request pending or you can cancel it.
The POS_CTRL block resets the signal when all of the above-listed condi-
tions are fulfilled.
Read not possible = TRUE; Read request cannot be serviced at this time because:
(AW-DB, DBX68.3) S The axis is not initialized
S No mode has been selected
S Test mode is enabled
In these cases, you can leave the Read request pending or you can cancel
it. The POS_CTRL block resets the signal when all of the above-listed condi-
tions are fulfilled.
Reset status/error With this signal you can reset all Ready and Error signals prior to processing
(AW-DB, DBX69.1) of the pending job requests. The signal itself is then reset by the block.
Error evaluation
Communication errors or data interpretation errors on the FM are flagged in the
Binary Result (BR = 0) and by instance variable RETVAL < 0; see job request sta-
tus.
Possible errors are:
S Data transfer error (communication is not completed) during a transfer with SFC
58/59 “RDREC / WRREC”. The error code is made available in user data block
AW-DB, DBW66 (RET_VAL value of these internal SFBs) (job states 4, 5 and
6, see Table 6-7, see also Error List, Section 6.8).
S Data transferred with Write are checked for data errors by the module and inter-
preted. If a data error occurs, the checkback signal “Data error” (AW-DB,
DBX22.4) is set to TRUE in user data block AW-DB (message: “Write job ter-
minated with error”). The error number, read out via an internal job request, is
entered in user data block AW-DB, DBB94 and 95 (job status 3, Table 6-7).
You will find more information on data errors in the parameter initialization tool
under the menu command Debug > Error Evaluation and in Chapter 11.
Performance in the event of an error during the servicing of a Write request (does
not apply to single functions and commands):
S The Initiate signal is removed for the errored request and the Error signal (AW-
DB, DBX54.0 to 63.7) and Ready signal (AW-DB, DBX44.0 to 53.7) are set (job
request status, point 3, Table 6-7).
S The Initiate signal is also removed for all pending Write requests and the Error
signal set (job request status, point 4, Table 6-7).
S Any pending Read requests are serviced. The error code (AW-DB, DBW66) for
each request is re-set if another error occurs.
Performance in the event of an error during the servicing of a Read request:
S The Initiate signal is removed for the errored Read and the Error signal set (job
request status, point 5, Table 6-7).
S Any pending Read requests are serviced. The error code (AW-DB, DBW66) for
each request is re-set if another error occurs.
Performance in the event of an error during servicing of single functions and
commands:
S The Write request is not serviced in its entirety, and the Error signal is set (job
request status, point 4, Table 6-7).
S The function set/reset which led to initiation of the Write request is not acti-
vated.
The checkback signals “Process in progress” and “Position reached. Stop” are not
reported back to the user program until the FM has detected and processed the
Start signal (v 2 FM cycles).
When calling the POS_CTRL block and the relevant control/checkback signals,
the subsequent signals are generated so that starting of the procedure can be de-
tected earlier than would otherwise be the case.
Signal Description
Execution started = TRUE When a mode/movement is started with the relevant
(AW-DB, DBX13.6) control signals or when the status for “Process in
progress” (AW-DB, DBX23.1) = 1
when the block is called/
“Execution started”
started
“Process in progress” when the FM starts tra-
versing movement
Position = FALSE When status signal “Position reached. Stop.” (AW-DB,
(AW-DB, DBX13.7) DBX25.7) = 0 is returned or when a mode is started
with the relevant control signals.
when the block is called/
“Position”
started
“Position reached. Stop” when FM starts traversing
movement
Furthermore, various settings and commands are required to control the FM 353.
In all cases, those commands and settings are transferred which are activated at
the time when the POS_CTRL block is called. The commands are canceled after
the transfer, also in case of error.
The functions which can be activated in the FM using single settings or single com-
mands are listed below.
6.4.4 The POS_ DIAG (FC 2) block – Read diagnostic interrupt data
Block description
See Section 6.3.4.
Function
Use the POS_MSRM block to read the measured values into the AW-DB user data
block.
For information on process interrupts, please see Section 6.5.
For information on measured values, see Section 9.3.10.
Note
The measured values can also be read by means of POS_CTRL (Read request).
If more than one Read request is present, this request is processed in the relevant
order.
If the POS_MSRM block is called, the measured values are obtained irrespective
of any other Read requests currently present.
Call options
The POS_MSRM block requires an instance DB when called.
The DB “IMSRM” (DB 3) is part of the “FM353_354” library.
POS_MSRM can be called in OB 40 (only when the FM is operated in the central
configuration) if the process interrupt has been activated (see Section 5.2), or in
OB 1. It is not possible to call POS_MSRM in both OBs simultaneously.
The block does not have multiple-instance capability.
Parameters
The Table below lists the parameters for the POS_MSRM block.
Function description
The function works together with an AW-DB user data block. When the function is
called, the DB number is forwarded in the DB_NO parameter.
Reading of the measured value is started by setting the IN_MSR parameter to
TRUE. When the function has executed, the block resets the parameter.
The IN_MSR parameter remains set while the function is executing. Transfer of the
data is terminated is complete when the parameter is reset (IN_MSR = FALSE).
Error evaluation
Errors are flagged in the Binary Result (BR = 0) and by RETVAL < 0.
Possible errors are as follows:
Data transfer errors during transfers with SFB 52 “RDREC”. The error is made
available in the user data block AW-DB, DBW98 (see Error List, Section 6.8).
User DB 1 is the user data block in the default condition of the function blocks; it’ s
symbolic name is IFFM_ICTRL. This DB consists of the user data interface and
the instance data of the POS_CTRL block (FB 1).
The user can access the signals and/or data on the interface using absolute or
symbolic addresses if reference is made via the symbol table of the project.
When calling POS_CTRL, the interface is transferred as an instance. With the
other standard function blocks, the interface is assigned to the appropriate
channel/axis using the DB_NO input parameter.
Note
If the POS_CTRL block is called for several channels/axes, a new instance DB of
the POS_CTRL block is to created for each individual channel/axis. To assign the
datza to the relevant channel/axis, this instance is always to be transferred when
calling the block.
The module address is part of the user data block (AW-DB). It is entered either by
the POS_INIT block or manually via ”Parameterize FM 353“ using the ”Enter mo-
dule address in the user data block“ in the overview diagram. The user data block
(AW-DB) must exist.
6.5 Interrupts
Interrupt processing
The FM 353 can generate process interrupts and diagnostic interrupts. You can
process these interrupts only in an interrupt OB (OB 40 or OB 82). If an interrupt is
generated without the associated OB having been loaded, the CPU goes to STOP
(refer to the manual entitled Programming with STEP 7).
Interrupt servicing is enabled in the following stages:
1. General Interrupt Enable for the entire module:
– Select the module in the hardware configuration.
– Enable diagnostic and/or process interrupts with Edit > Object Properties >
Basic Parameters (also see Figure 5.2).
– Select the OB number for the process with Edit > Object Properties > Ad-
dresses.
– Save and compile the hardware configuration.
– Load the hardware configuration into the CPU.
2. Enable the events for the process interrupt in the machine data.
Overview
The Table below describes the structure of the user data block.
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
General addresses
DBW0 Module address (data type INT)
DBW2
to Reserved
DBB12
Execution
DBB13 Position
started
Control signals
Acknowl- Switch to
edge opera- P bus
DBB14
tor/travers- Start-up
ing error
Acknowl-
Drive Read-in Positive Negative
DBB15 Block skip edge M Stop Start
enable enable direction direction
function
DBB16 Operating mode
DBB17 Operating mode parameters
DBB18 Override
DBB19
to Reserved
DBB21
Checkback signals
Operator/ Switch to
Channel
DBB22 Data error traversing P bus com-
initialized
error pleted
Wait for
Reverse Dwell in Machining Start
DBB23 external
prog. scan progress in progress enable
enable
DBB24 Active operating mode
On-the-fly
Position End of Channel
setting of Servo ena- Positive Negative
DBB25 reached. measure- synchroni-
actual value ble status travel travel
Stop. ment zed
completed
DBB26 M function number
M function
DBB27 modifica-
tion
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Actual position
DBD28
(with firmware version V3.7.6 and higher in conjunction with the blocks of the “FM353_354” library
DBW32 Reserved
Initiation signals
Initiation signals for single settings (switches); transfer through Write request when change occurs
Parking Rotation In-process Controller
DBB34 Simulation
axis monitoring measuring enable
Software
Enable Length
limit posi- Retrigger
DBB35 input dis- measure-
tions dis- ref. point
abled ment
abled
Initiation signals for single commands; transfer through Write request when change occurs
(signals are reset following transfer)
DBB36 Reserved
Rescind Automatic Automatic Delete
Activate
DBB37 setting of Restart block block ad- residual
MD
actual value return vance distance
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Ready signals
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Error signals
DBW66 Error code (communications error) of the last job request/transfer (data type: INT)
Read re- Write re-
Read job Write job
DBB68 quest not quest not
active active
possible possible
Reset
DBB69
status/error
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Channel er-
DBB77
ror vector
Operating
DBB78
error
DBB79
to Reserved
DBB85
Error code after error message “Operating error”
(is read if ’operating error’ is set after calling the POS_DIAG block)
DBB86 Error number (DS 164) – Detail event class
DBB87 Error number (DS 164) – Detail event number
DBB88
to Reserved
DBB89
Error code following flagging of “Operator/traversing error”
DBB90 Error number (DS 162) – Detail event class
DBB91 Error number (DS 162) – Detail event number
DBB92
to Reserved
DBB93
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Error code following flagging of “Data error”
DBB94 Error number (DS163) – Detail event class
DBB95 Error number (DS163) – Detail event number
Error code for the POS_DIAG block (return code SFC 51)
DBW96
(Data type: INT)
Error code for the POS_MSRM block (return code SFC 59)
DBW98
(Data type: INT)
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
MDI block
DBB176
to Reserved
DBB177
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
DBB227 G function no. of group 2
DBB228
to Reserved
DBB229
DBD230 Value for position/dwell (data type DINT)
DBD234 Value for speed (data type DINT)
DBB238 M function no. of group 1
DBB239 M function no. of group 2
DBB240 M function no. of group 3
DBB241 Reserved
Program selection
DBB242 Program number
DBB243 Block number
DBB244 Direction of processing
DBB245 Reserved
Request for application data
DBB246 Application data 1
DBB247 Application data 2
DBB248 Application data 3
DBB249 Application data 4
Teach-in
DBB250 Program number
DBB251 Block number
DBB252
to Reserved
DBB309
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Active NC block
DBB342 Program number
DBB343 Block number
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Application data
DBD382 Application data 1 (data type: DINT)
DBD386 Application data 2 (data type: DINT)
DBD390 Application data 3 (data type: DINT)
DBD394 Application data 4 (data type: DINT)
Actual value block change
DBD398 Data type DINT
Service data
DBD402 Frequency output value (data type DINT)
DBD406 Pulse output counter (data type DINT)
DBD410 Reserved
DBD414 Reserved
DBD418 Difference between setpoint and actual position (data type DINT)
DBD422 Reserved
DBD426 Switch adjustment (data type DINT)
DBD430 Reserved
Additional production data
DBB434 Override
DBB435 NC traversing program no.
DBB436 NC block no.
DBB437 UP call counter
DBB438 Active G90/91
DBB439 Active G60/64
DBB440 Active G43/44
DBB441 Active D number
DBB442 Speed limit
Accelera- Frequency Start/stop
tion/decel- value for frequency
DBB443 eration accelera- limited
value lim- tion limited
ited
DBB444
to Reserved
DBB445
Parameter/data
DBB446 DB type (MD, incremental dimension or traversing program)
DBB447 Number
DBB448 Quantity
DBB449 Request
AW-DB FM 353
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
DBB450
Array, structure/data type according to data, to be read as per bytes 1 to 4 of this structure
to
(e.g. a program record or max. 5 MD items)
DBB469
DBB470
to Reserved
DBB485
Measured values
Measured values as per POS_MSRM call
DBD486 Initial value or in-process measured value (data type DINT)
DBD490 Final value (data type DINT)
DBD494 Measured length value
Note
For the symbolic signal designations, please refer to the “FMSTSV_L” library, UDT
1 block, or to the “FM353_354” library, DB 1 (IFFM_CTRL).
Overview
This chapter provides information on the following:
S Basic example for setting the operating mode
S Example 1: Moving axes in “JOG mode” and “Approach to reference point
mode”
S Example 2: Traversing an MD block
S Example 3: “Automatic” mode with program selection
S Example 4: Technology example for embedding OPs
General remarks
The installation of the FM 353 configuration package includes the following sample
projects:
S “zDt13_02_FM353_EX” ([STEP7 directory]\EXAMPLES\zDt13_02)
for application examples for the “FMSTSV_L” block library
S “zDt13_03_FM353_EX” ([STEP7 directory]\EXAMPLES\zDt13_03)
for application examples for the “FM353_354” block library
The relevant technological functions (POS_CTRL, POS_DIAG, POS_INIT) are
called in the OB 1, OB 82 and OB 100 blocks. DB 100 (DBEX) contains the
relevant user signals/user data for all application examples.
Each example is programmed as a block (e.g., example 1 = FC 101, etc.). In The
basic example (FC 100) is always necessary for the examples 1 to 3; it sets the
relevant modes and copies the data between DB 1 and DB 100.
The examples 1 to 3 are interdependent. They are technologically simple examples
which you can expand to suit your particular needs. To be able to use the functions
provided by the examples 1 to 3, call the relevant examples in OB 1 analogous to
example 1.
OB 1 contains an example after the call of POS_CTRL how the evaluation of the
reported errors of the POS_CTRL could be programmed. You can expand this
error evaluation accordingly if you want.
Example 4 requires the OB_example4 source file specified in the source folder to
be compiled. Since this is an application example for use of an OP, only example 4
should be called in OB 1, as not to overwrite data.
Note
In the examples, the axes do not traverse in simulation mode!
Because “DBEX” is a retentive DB, it is initialized in the start/restart routine (OB
100). If this is not required, simply delete the initialization section of OB 100 (net-
work “DBEX Initialization”).
Example 1
Open the example project. The block used for this example is FC 101.
The signals are in “DBEX”. The signals relevant for Example 1 only are in structure
“EX1”.
The Drive Enable and the Controller Enable for the axis are set in “DBEX” (OB
100: DRV_EN = TRUE, SERVO_EN = TRUE) and are transferred to the interface
(AW_DB) in Example 1.
In order for the example to function, you must first set either “Jog” mode (mode
code 01) or “Reference point approach” mode (mode code 03) in byte MODE_IN of
the “DBEX”. The respective mode checkback signal is flagged in byte
MODE_OUT.
The traversing movements are shown in bits “GO_M” = TRUE (traverse -axis 1) or
“GO_P” = TRUE (traverse + axis 1).
“Jog” mode active:
Once a mode has become active, the Write request “VLEV_EN” (AW-DB, transfer
speed level 1, 2) is executed once. If you want to transfer it again, you must either
reset the “VLEV_D” bit (status/checkback signal from the request) or set the
“JOBRESET” (reset status/error) in DB_FM.
If you set bit “DIR_M” (minus direction) or bit “DIR_P” (plus direction) to TRUE in
“DBEX”, the axis is moved in either a negative or positive direction.
“Reference point approach” mode active:
When you set the “START” bit to TRUE, the axis is moved in a negative or positive
direction (depending on the machine data initialization) until the reference point is
located. If the reference point approach was successful, the axis is synchronized
(SYNC=TRUE).
If an operator or traverse error occurred, this is flagged by bit “OT_ERR” = TRUE.
An error can be acknowledged by setting bit “OT_ERR_A” to TRUE.
Note:
Variable table 1, which contains all the relevant signals for monitoring and control-
ling Example 1 (“control and monitor variable” tool), is located in the “Blocks” direc-
tory.
Example 2
Open the example project. The block used for this example is FC 102.
The signals are in “DBEX”. The signals relevant for Example 2 only are in structure
“EX2”.
The Drive Enable and the Controller Enable for the axis are set in “DBEX” (OB
100: DRV_EN = TRUE, SERVO_EN = TRUE), and are transferred to the interface
(AW-DB) in Example 2.
In order for the example to function, you must set the “MDI” mode. Enter “MDI”
mode (mode code 06) in the MODE_IN byte of “DBEX”. The relevant mode check-
back signal is flagged in byte MODE_OUT.
Once the mode has been successfully set, a default MDI block is automatically
transferred to the module (MDI network) when Write request “MDI_EN” has been
set in “AW-DB” (transfer MDI block). This block can be changed in dependence on
the system and the request. If it is to be retransferred, you either have to reset the
“MDI_D” bit in “AW-DB” (status/checkback signal for request) or set bit “JOBRE-
SET” (reset status/error).
Set the “START” bit in “DBEX” to TRUE in the “EX2” structure. The activated MDI
block is started on the condition that the axis is synchronized and has a Start En-
able. Then the “START” bit is reset. The MDI block cannot be restarted until the
start enable is again available.
The block can be stopped by setting the “STOP” bit.
Only when the “STOP” bit has been reset to FALSE (and the “START” bit to
TRUE) is a restart possible.
If an operator error or traversing error occurs, it is flagged by the “OT_ERR” bit
(the bit is set to TRUE). The error can be acknowledged by setting the
“OT_ERR_A” bit to TRUE.
Note:
Variable table 2, which contains all the relevant signals for monitoring and control-
ling Example 2 (“control and monitor variable” tool), is located in the “Blocks” direc-
tory.
Example 3
Open the example project. The block used for this example is FC 103.
The signals are in “DBEX”. The signals relevant for Example 3 only are in structure
“EX3”.
The program to be selected in the Example has the program number “10”. This
program number is entered in Example 3.
The Read Enable, the Drive Enable, and the Controller Enable for the axis are set
in “DBEX” (OB 100: READ_EN = TRUE, DRV_EN=TRUE, SERVO_EN=TRUE),
and are transferred to the interface (AW-DB) in Example 3.
Prerequisite for successful program selection is the availability of that program in
the FM.
In order for the example to function, you must set “Auto” mode. Set the “AUT O”
mode (mode code 08) in byte MODE_IN of “DBEX”. The relevant mode checkback
signal is flagged in byte MODE-OUT.
Following successful mode selection, the program with the number “10” is auto-
matically selected by setting Write request “PROGS_EN” in “AW-DB”.
Set the “START” bit in “DBEX” to TRUE in structure “EX3”. The selected program
is started, assuming that the axis is synchronized and has a Start Enable. Then the
“START” bit will be reset.
The program can be stopped by setting the “STOP” bit. It can be restarted by re-
setting the “STOP” bit to FALSE (and the “START” bit to TRUE).
If an operator error or traversing error occurs, it is flagged in the “OT_ERR” bit (the
bit is then TRUE). The error can be acknowledged by setting bit “OT_ERR_A” to
TRUE.
Note:
Variable table 3, which contains all the relevant signals for monitoring and control-
ling Example 3 (“control and monitor variable” tool), is located in the “Blocks” di-
rectory.
Example 4
Open the example project. The block used for this example is FC 104.
Note: If you call the example 4 in OB 1, then please do not call the examples 1 to
3 at the same time; otherwise, data would be overwritten.
In this example, the HMI interface signals for the data range from DBB 498 through
DBB 515 are transferred to the interface area for the control signals, e.g. the
modes (see Section 8.2).
You can trigger write and read jobs by assigning the data fields to be transferred
the appropriate parameters and data.
For example, if you select the machine data screen PIC_763, you can write an MD
using the ”set” softkey (SK) and read an MD using the ”read” softkey (SK).
Once you have selected the mode screen PIC_75 on the operator panel and
selected the appropriate mode SK, the selected mode will be accepted into the
control signals of the interface, and the appropriate mode will be set.
If you select the diagnostic screen PIC_77, you can acknowledge an error by
pressing the ”Quit” SK or acknowledge a diagnostic alarm by pressing the ”Res”
SK.
In this way, all interface signals which can be activated by the OP are requested.
You can assign default values to all data fields and transmit trigger pulses for the
jobs to be executed.
Memory allocation
The Table below provides an overview of the memory allocation for the blocks and
the user data block (AW-DB). All values are rounded.
Table 6-13 Memory requirements for the blocks and user data block
Table 6-14 Memory mapping of the blocks and of the user data block AW-DB,
“FM353_354” library
No. Block Block in bytes MC7 code in bytes Local data in bytes
Loading buffer
0 POS_INIT 250 142 4
1 POS_CTRL 4,966 3,198 34
2 POS_DIAG 310 186 46
3 POS_MSRM 380 242 32
4 AW-DB 2,012 576 –
Processing times for the blocks taking the following example system
The specified times are rounded.
Structure: CPU 315-2DP, FM 353 in the simulation mode
User cycle time: approx. 5 ms
FM cycle: 2 ms
Several cycles are required to read or write data via the relevant requests.
Overview
This Chapter introduces you to the user interface for testing and start-up, and pro-
vides check lists for starting up the positioning module. The checklists will help
you:
S Check all steps until the module is running.
S Prevent malfunctions of the module once it is in operation.
You are guided through start-up of the machine axes.
Installation information
You can find information about how to install your module:
S In Chapter 3 of this manual
S In the manual S7-300 Programmable Controller, Hardware and Installation
Wiring information
You can find information about how to wire your module:
S In Chapter 4 of this manual
S In the manual S7-300 Programmable Controller, Hardware and Installation
Checklist
The checklist below will help you check important steps in the installation and para-
meterization of the FM 353 positioning module.
Parameterization information
You can find information about parameterization:
S In Chapter 5 of this manual
S In the on-line help in “Parameterize FM 353”
Overview
The following overview display appears in the “Parameterize FM 353” tool:
You can return to this display at any point during parameterization by selecting the
menu View > Overview.
As it is written to the FM 353, the DB-MD is checked for the input limits of the indi-
vidual values and their interdependencies. It is then stored only if all values are
allowed. Otherwise data error messages are displayed by way of the MPI. A defec-
tive DB will not be retained when the power is turned off.
Checklist
Despite the “acceptance” testing just mentioned, the ultimate responsibility for the
accuracy of all machine data lies with the module user. So it is highly advisable to
perform startup using the following checklist.
Note
The measurement system (MD7) must match the measurement system specified
in the other DBs.
The measurement system raster (MSR) is the smallest distance unit in the active
system of measurement.
If at some point you have failed to take this precaution:
1. Delete all data blocks (which do not match the measurement system) or clear
the memory of the FM 353 completely.
2. Modify the other data blocks on the PG.
3. Reload the data blocks to the FM 353.
Initial contents of MD
The table below shows you what initial contents are recommended or required for
the E machine data at startup of the machine axis.
Enter the machine data in the tab windows or in table format in accordance with
the following table.
1 – Error field
2 – Status field (e.g. actual values, checkback signals)
3 – Field for mode-specific inputs
4 – Field for input of values/settings/commands and start/stop for movement
The abbreviations for the checkback signals are described in Table 9-2.
Note
S Select a mode
S Turn simulation on (if you want an operating case)
S Servo enable
S Drive enable
S Override 1 – 100%
You can operate the “R+” and “R-” buttons in the “jogging” mode as follows:
1. Select “R+” or “R-” with the mouse
2. Press the space bar
You can operate “Start” and “Stop” with the mouse, or with the space bar if you
have already selected the button.
The digital outputs are not set in the “Stop” status of the CPU.
When you call up the following button, you will get dialog windows:
S set actual value
S set actual value on-the-fly
S set reference point
S zero offset
Warning
! If you move the axis directly (without simulation), for safety’s sake make sure you
can switch off the hardware if a hazard arises.
Note
If you use the start-up user interface to operate the FM 353 when the CPU is in
“STOP”, and then switch the CPU to “RUN” and then immediately switch to the
start-up interface in your user program by means of the [TFB] (TEST_EN) signals
(e.g. if example application 3 is included in the user program), please note the fol-
lowing:
You must select the mode again from the start-up interface, or close the
start-up interface and call it up again.
The following display appears when you select Test > Service data:
The following display appears when you select Test > Trace:
Checklist
When starting up the machine axis, it is important to perform the following steps in
the indicated sequence. Steps 1 to 5 are always necessary; the rest are optional,
depending on your own application.
Note
In order for an axis to start, the start enable checkback signal must have been set.
If there is no start enable, this may be because:
S “Drive enable” is not set
S “Stop” is set
S “Operation in progress” is active
Overview
The checkback signal PARA notifies you that a DB-MD has been retained. This
machine data is automatically activated at power-up. The module’s positioning
functions are ready to operate.
If no DB-MD is present as yet on the FM 353 when the control is switched on, the
module can only communicate by way of the MPI interface. The control signals are
not processed by the FM 353. Once an error-free DB-MD has been transferred,
the machine data is automatically activated, PARA is set and the control signals
are processed.
If the FM 353 is working with activated machine data, you can transfer a new data
block or individual parameters in modified form to the module and, if the entire
DB-MD is error-free, put the new or modified data into effect by means of the ”Acti-
vate machine data” function provided that an operating mode is active (parameter-
izing tool ”Start-up display”).
The following approaches are possible:
S If only E data has been modified in the machine data record since the last ac-
tivation, the equipment is activated with module status “Operation in progress”
= 0, without interrupting the servo cycle. “SYN” is retained.
S If K data has also been modified in the machine data record since the last ac-
tivation, activation takes place with module status “Operation in progress” = 0
by way of a cold restart of the servo, just as occurs for a power-up of the mod-
ule. The instantaneous actual position is still displayed, but encoder pulses from
incremental encoders might go unrecorded. “SYN” is reset.
S If the machine data record contains erroneous data at activation time, the func-
tion is rejected, with the “Machine data cannot be activated” error message (see
Table 11-5, Class 2, No. 21).
Overview
Basically, the stepper motor is a highly dynamic drive motor which is capable of
following setpoint assignments more or less free of following error. It is also capa-
ble of handling the transition between idle time and movement (and back) by way
of the start/stop frequency at an extremely high rate of acceleration. This presup-
poses however, that the available motor torque at any given movement status,
matches as a minimum, the torque necessary for executing the movement. In the
following discussion, it is assumed that you are familiar with the necessary torque
values for your particular application from the having conducted configuration of
the drive. If necessary, refer to the formula or tabular material (e.g. Positec/Berger
Lahr: [title translated: “Formulas + Computations for optimal stepper motor adjust-
ment” [TN: available in English? If so, what is exact English title?] provided by the
stepper drive manufacturers.
You can obtain optimal configuration of the speed profile for traversing movement
when the speed-timing diagram, as shown in Figure 9-7, is well-defined.
You can determine the parameters for the speed profile, as shown in the following
parameterization example, from the operating characteristic curves of the stepper
motor you have in use. When doing this, please be sure to always allow a torque
reserve of approx. 20%.
Procedure
Determining the available or necessary torque:
MMotor = MLoad + MAccelerations
Determining the present moments of inertia:
JLoad = Jexternal_rotational + Jexternal_translational
Jtotal = JMotor + JLoad
Assumed values from the parameterization example:
MMotor = 5 Nm
MLoad = 0,6 Nm (assumption: constant at all rpms)
JMotor = 4 kgcm2
JLoad = 3 kgcm2
MD13 = 500 increments per revolution
fmax = 10 kHz
Further definitions, e.g.:
acceleration values = deceleration values
M0
5
Maximum permissible
Torque drop from PWM
operating moment
3.4
( )
3 M1
Mb1 Start/Stop
SS (J = 0)
1.8
M2
Mb2
0.6
MLoad
0
n [1/min]
[kgcm2]
3
JLoad
0
12 120 1 200 n [1/min]
When you evaluate this example characteristic in accordance with the algorithm in
Figure 7-7, you determine the following machine data:
MD39 = 100 Hz Start/stop frequency
MD40 = 3 000 Hz Frequency value feg
MD42 = 218 000 Hz/s Acceleration 1 (f feg)
MD43 = 109 000 Hz/s Acceleration 2 (f > feg)
MD44 = 0 Deceleration 1 = acceleration 1
MD45 = 0 Deceleration 1 = acceleration 2
No Yes
Equate acceleration element for all Should values for acceleration and delay be
f – fmax: Mb1 = Mb2 identical within the range f > feg ?
Yes No
Should values for acceleration and delay be
identical within the range f < feg?
Notes
Notes regarding special boundary conditions:
S It is evident from the above example that the acceleration moment within the
lower speed range is approximately twice the value of the same value at maxi-
mum speed. This results in optimally-timed positioning cycles. Of course, the
acceleration switchover is freely selectable in accordance within certain techno-
logical criteria. In this case the result is the value of the available motor torque
M1 or Mb1 according to the characteristic.
S In case your stepper drive features the “Current control through boost” function,
you can count on the elevated curve for determining the acceleration moment.
Any advantage from increased acceleration capability is realized from the mo-
ment curve only within the lower rpm range of the motor
(e.g. Mb1 = 3.4 Nm – 0.6 Nm = 2.8 Nm, M b2 unchanged).
The following adjustments should be made:
– electrical connection
– MD37 (activation of the function)
– MD48/49 (for monitoring of boost duration, see Section 7.3.6)
S In case your stepper drive features the “Current control through PWM” function,
you can reduce the power loss converted in the motor, thereby reducing motor
heating. This is possible because the acceleration moment is not needed. It is
accomplished by reducing the motor current for idle and for constant travel
phases proportional to the load moment. An advantage of reduced heating dur-
ing constant travel becomes evident from the moment curve, particularly within
the lower rpm range of the motor.
The following adjustments should be made:
– electrical connection
– MD37 (activation of the function)
– MD50 = (MLoad (fmax ) : M Motor (fmax ))100% (e.g. 60%)
– MD51 = (MLoad (f = 0): M Motor (f = 0)) 100% (e.g. 12%)
Overview
Use the following flow charts to verify the drive actuation and that the machine
data determined so far are correct. Since the FM 353 positions the stepper motor
axis without using encoders (i.e., from control engineering standpoint, pure, direct
control; see Fig. 7-10), special attention must be placed on evaluating the travers-
ing movement. An initial test should be conducted to verify that the stepper motor
will traverse as a matter of course in response to actuation by the FM 353. A se-
cond test should be conducted to verify positioning accuracy. (Always activate MD
changes using “Activate MD”!)
Note
Always activate MD changes using “Activate machine data”!
Caution
! Prior to triggering any traversing movements, check to make sure there is clear-
ance for axis movement in the desired direction of travel!
Basic startup
Use the following flow chart to verify the drive actuation.
Starting the axis
Start the axis with the “space bar” after preselecting the direction via R+ or R–.
The “Windows properties” allow for successive execution of the command (re-
peated starting/stopping of the axis) when the “space bar” is depressed in quick
succession.
Parameterize
Load MD-DB to FM 353
(K data according to axis configuration)
(enter E data according to Table 7-2 or Section 7.3.2)
Select BA = jogging
Speed level 1
OVER = 100%
Set
Activate machine data
Set
Speed level 1 = vss
Speed level 2 = vmax
Set
Servo enable = ON
Start axis
Plus or minus direction
(execute several times)
Travel test using Start/Stop frequency
(make sure travel area is clear!)
No
Axis movement completed?
Yes
No No
Direction correct? Stepper drive active?
(Motor torque present?)
Yes Yes
Check drive
Check MD: Check MD: Check MD:
MD37.9 (inverted) MD 39, MD 37.17, MD 37.0 (RFG)
MD 37.19 MD 37.16 to MD 37.19
Select
BA = jogging
Speed level 1
Start axis
Plus or minus direction Travel at
(execute several times) fmax
(make sure travel area is clear!)
No
Axis movement completed?
(including correct braking?)
Check MD:
MD 42 to MD 45
Yes MD 37.16 to MD 37.19
Positioning
Use the following flow chart to check axis travel to a target position.
Set
Speed level 1 = 0.5Vmax
Speed level 2 = 0.5Vmax
Set
Set reference point with value 0
Set
Servo enable = ON
Start axis
Plus or minus direction
(make sure travel area is clear!)
External measurement device options
include:
Check position actual value using ex- S Laser measurement device
ternal measurement device S Linear scale with position indicator
S Dial gauge
S Measurement scale featured on axis
No
Direction OK?
Yes
No
Amount OK?
Yes
No
Additional testing desired?
Yes
Select
OVER = 1--200 %
Overview
The motor axis driven by the FM 353 is driven by pure, direct control. It features
the following structure:
Motor and
FM 353 Drive Phase current control Machine
PULSE Iph
Set Direction Current-sourcing Current
position pattern counter regulator M
Stepper mo-
tor control
Target
speed PWM/
BOOST
Select
BA = jogging
Speed level 2
OVER = various values
Set
Speed level 1 = 0.1Vmax
Speed level 2 = 0.5Vmax
Set
Servo enable = ON
Start axis
Plus or minus direction
(make sure travel area is clear!)
Uniformity of movement
Evaluation of axis behavior Tendency to vibration
Positioning time
Additional testing desired?
Yes
No
END
Fig. 7-11 Test movements for optimizing the stepper motor control system
Axis
To ensure distinct reproducibility of reference recordings, it is necessary for the
synchronizing zero pulse (SYNI) formed by an external zero pulse or by the “cur-
rent-sourcing pattern zero” signal (see Section 9.7.2) to be a distinct distance away
from the reference-point switch (RPS). At low reducing velocities, we recommend
a distance of between 10% and 90% of the distance of one stepper motor revolu-
tion, or the distance of one current-sourcing pattern cycle. For high reducing veloci-
ties, we recommend 30% to 60%. Check this value in the servicing data report
(switch alignment value), and if you find nonconformity to the required value range,
make a corresponding adjustment in the relative position allocation between the
zero pulse encoder or the stepper motor, and the reference-point switch.
Example: Positive search direction
SYNI
RPS
Zero pulse
MD11, 12
Set the referencing velocity to the highest value compatible with your require-
ments. It is important for it to be possible to brake to the reducing speed along the
entire length of the reference-point switch (RPS). If this is not the case, an addi-
tional repositioning to the RPS occurs before the search phase begins. Compare
the cycle of the executed traversing movements with Section 9.2.3 and optimize
the referencing speed (MD28).
Then readjust the reference-point coordinates-proper by entering the necessary
reference-point shift in the machine data. After the machine data is activated, the
new reference-point shift takes effect with the next reference point approach.
Overview
Once optimization of stepper motor control is completed, activate the stepper mo-
tor diagnostics as needed.
Boost
The boost signal is monitored in terms of its active time. This is in order to protect
the drive motor against overheating.
Refer to the stepper motor drive documentation for information regarding maximum
absolute and relative boost duration. Enter this information into machine data
MD48 and MD49, provided for that purpose.
When boost function is parameterized, the FM 353 triggers the errors “Boost dura-
tion absolute” or “Boost duration relative” in the event that time for the active
phase(s) of the Boost signal is exceeded.
Once parameterization is completed, check the diagnostics function for efficacy
using a suitable test program with which particularly large proportions of accelera-
tion and braking phases occur during execution.
Rotation monitoring
Activation is accomplished by way of the “Rotation monitoring” single-setting func-
tion (refer to Section 9.7.3 for functional description of rotation monitoring).
If the rotation monitoring function is programmed, the FM 353 will trigger the “Rota-
tion monitoring” error in the event that the stepper motor is unable to follow the
movement specified.
Check the efficacy of the diagnostics function. This is accomplished by electrically
separating the cyclic zero pulse encoder or the power section of the stepper motor
and executing a test movement in any operating mode.
Note
If you change the reference point coordinates, you must redefine the positioning
values of the software limit switches.
If you do not need the software limit switches, the input limits –10 9 and 109 [MSR]
must be entered in MD21/MD22 (for default values, see Table 5-4).
Backlash compensation
Due to play in the mechanical transmission elements, position deviation of the ma-
chine component to be positioned (e.g. lathe slide) may occur when a stepper mo-
tor is used for positioning. Normally, some travel distance “turns up missing” follow-
ing a direction reversal. This backlash can be ascertained as an average at
different axis positions. This can then be entered in the machine data set.
You can use the following flow chart to determine backlash and activate backlash
compensation.
Also please refer to the information on “backlash compensation” presented in Sec-
tion 9.7!
Parameterize
MD 31 – Set direction reference of
backlash
Set
Activate machine data
Set
Velocity level 1 = 0.1 vmax
Velocity level 2 = 0.5 vmax
Set
Servo enable = ON
Select
BA = relative incremental
Increment = 3 DB increments, value 3 = e.g. 100 MSR
OVER = 10%
Start axis
Direction per MD31
Please note:
Determine backlash value:
Backlash = increment - measured dist. Repeat of test produces negative backlash val-
ues in cases of overcompensation
Positioning operations for short travels programmed in conjunction with the para-
meterization of relatively high accelerations (MD42...MD45) are performed within a
few FM cycles.
In previous software versions, positioning times can occur which do not comply
with the times calculated, but are considerably higher (depending on the path
length programmed). When reducing the distance to be traversed, e.g. by a path
corresponding to one step of the stepper motor, the following effect can occur: The
positioning time is not reduced or remains unchanged, but the positioning can last
longer by several FM cycles.
The possibility of mispositioning should not be excluded in conjunction with the
causes for this behavior, even though such error messages had not been reported
by now.
In the present software version, the functioning principle of the FM 353 can be
switched to the “Optimized motion profile” mode.
MD56 Optimized motion profile (see Table 5-4)
Note
MD56 is zero (”0”) by default. Thus, the default motion profile is activated; the
functioning principle is the same as in the previous software versions.
No value monitoring with output of error messages is provided when entering
MD56. In case of an illegal or invalid value assignment, the default motion com-
mand is activated.
Summary
In this chapter you’ll find an overview of the operator-control and monitoring capa-
bilities offered by the FM 353.
For operator control and monitoring of the FM 353, a control panel can be con-
nected to the CPU via the MPI interface (see Figure 1-2).
The FM can service no more than three nodes simultaneously.
The module uses the SIMATIC interface (backplane bus) to communicate with the
control panel.
Overview
This Section describes a preconfigured user interface, which you will need to
change according to your project (e. g. FM addresses, DB no.), for the following
COROS equipment (operator panels):
S OP 07
S OP 17
The tool to be used for this is the “ProTool/Lite” configuring tool. You can use it to
modify, add or delete graphics.
The user interface is addressed to user DB No.1 in the CPU (target system 1, ad-
dress = 2) and to the DB-SS of the FM 353 (target system 2, address = 3).
The text field “FM user name” represented in the images can be renamed to a text
of your choice.
You can print out the entire configuration using “ProTool/Lite”. This provides you
with detailed graphics descriptions.
You will find the preconfigured user interfaces op07_353.pdb and op17_353.pdb
in the following directory:
[STEP7 directory]\EXAMPLES\FM353\zEn13_02_FM353_OP_EX
DB-SS
This data block for status messages (DB 1000) contains the control/checkback
signals, as well as the system data of the FM 353. The data of the DB-SS can only
be read.
Monitoring
The data for monitoring can be read and displayed directly in the DB-SS as well as
in the corresponding parameterized DBs of the FM 353.
The advantage of reading directly from the FM is that the values/signals do not
have to be read via the user program first.
Operator control
For operator control, the data and signals (including memory bits and values) are
written to the user DB of the user program.
User program
User data bock AW-DB is the interface for the OP.
When control signals, single functions and single commands are set in the user
data block via the OP, they are immediately transferred to the FM by the
POS_CTRL block.
The signals written in “Operator Control and Monitoring” (requests to transfer the
data with Write as per Table 8-3) must be evaluated accordingly by the user pro-
gram (taking into account any user-specific interlocks) before setting the Write or
Read requests.
PIC72
PIC71 PIC74
Switch readjustment
User name act. mode in ref.: Free for user
x +1000000.000 mm Fre. output val.
x-Diff 1000000.000 SK for OP mode
<< MD Eins User
Teach BA-E Auto Eist Offl Onl Trans
Diff. betw. act. and set-
point pos.:
Pulse outp. counter: PIC73
PIC712 PIC714 MD Eins User > >
Operator/travel errors
Error class
PIC713 Error no.
<< Acknowledg Res >>
PIC722 PIC723 PIC724 Data error
MD no. status set Error class
Servo enable x Error no.
Value Free for user
Restart Axis << Message >>
Read Set active >> Operating error
status set Error class
SW limit switch off x Error no.
park. axis x << Res >>
PIC711 < < Diagnostic interrupts
Teach In Byte 0: Byte 2:
Pr. no. Block Byte 3: Byte 8:
X +1000000.000 mm << Res >>
PIC712
set
F level 1
F level 2
Selection stage
Control SMR MDI
PIC713 PIC714
PIC7132 PIC7141
% N Zero point offset
Direction Value
Total 1000000.000
SAvor SArü set ZPO set
Figure 8-2 describes the functions of the global function keys for the user interface
of the OP 07.
ESC key You can use this key to call up the previous screen of the higher
levels.
>> << Soft keys You can use these keys to call up the next inset screen within the
same screen (same screen number).
K1 Function key You can use this key to skip from any point in the menu tree to the
actual value display main screen (PIC71).
K6 Function key You can use this key to skip from any point in the menu tree to the
diagnostic main screen (PIC73).
Note
The screens of the user interface (see Figure 8-2 and description of each screen,
Table 8-1) contain display fields and input/output fields. These fields contain values
of configured variables.
S The display fields are addressed to the DB-SS (“Control 2,” DB1000) and are
read directly from the FM 353.
S The input/output fields are addressed to the user DB No.: 1 (Control 1-CPU).
– Transmission of these values occurs from the OP 07 to the CPU into the
user DB. These values (if needed) must be transmitted to the FM 353 by
the user program.
– If certain values or control signals can be written only under the right condi-
tions (e.g. if axis is necessary on HOLD or selection of a certain operating
mode), then the user program must ensure, by analyzing the response sig-
nals, that these conditions are met.
Table 8-1 below describes the individual screens of the user interface.
Main screen
PIC7 K1 K2 K3 K4 K5 K6 Global function keys
F1 F2 F3 F4 F5 F6 F7 F8
User-specific screens
Diagnostics,
PIC77
error message
SK1 SK2
Group signal Alarms
PIC Z_MESS_EVENT PIC772
Startup PIC76
SK1 SK3
Startup settings Machine data
PIC761 PIC763
SK1
MDI block on the fly PIC741
PIC73
Auto. main screen
SK7
Part progr.1) Overview
SK1 SK2 SK4 SK5 (P-sel)
Current block Foll. block Program selection Teach In
PIC736
PIC731 PIC732 PIC734 PIC735
SK8
Part progr.1) Edit
PIC72 (P-ed)
Parameters
PIC737
Figure 8-3 describes the functions of the global function keys for the user interface
of the OP 17.
ESC key You can use this key to call up the previous screen of the higher
level (the table of contents in the main screen).
K1 Function key You can use this key to jump from any point on the menu tree to the
main screen (PIC7).
K2 Function key You can use this key to jump from any point on the menu tree to the
diagnostics error message screen (PIC77).
K3 Function key You can use this key to jump from any point on the menu tree to the
operating mode selection screen (PIC75).
Note
The screens of the user interface (see Figure 8-3 and description of the individual
screens) contain display fields and input/output fields. These fields contain values
of configured variables.
S The display fields are addressed to the DB-SS (“Control 2,” DB1000) and are
read directly from the FM 353.
S The input/output fields are addressed to user DB No.: 1 (control 1-CPU).
– Transmission of these values occurs from the OP 17 to the CPU into the
user DB. These values (if needed) must be transmitted to the FM 353 by
the user program.
– If certain values or control signals can be written only under the right condi-
tions (e.g. if axis is necessary on HOLD or selection of a certain operating
mode), then the user program must ensure, by analyzing the response sig-
nals, that these conditions are met.
The pending errors are displayed in the errors line. More detailed error information
is provided on the screens “Diagnostics, Troubleshooting” and “Interrupt mes-
sages.”
FM 353
The illustrations shown below (Fig. 8-5 to Fig. 8-19) provide you with the screen
content of the configured screens.
FM 353
This screen is displayed to you after the OP 17 is enabled. The FM353 values are
display values. The soft keys (F1 - F8) are used to request the continuation
screens. The first and last soft keys (User) are kept free for the user to insert his/
her own screens (e.g. including additional FMs).
FM 353
Frq.–Stufe1 Hz
Frq.–Stufe2 Hz
Tipp Steu Refpk SMR MDI AutoE Autom
Fig. 8-6 Operating mode selection, PIC75
This screen permits you to enter the operating mode, velocity levels or control lev-
els or the incremental value.
FM 353
set
Fig. 8-7 Teach In PIC735
This illustration displays the actual value for you. You can enter the values for
Teach In.
FM 353
MDIfl set
Fig. 8-8 MDI block entry PIC74
The fields identified by an X are text fields and can be toggled back and forth be-
tween “X” and “ ”. You can enter the values of the MDI block.
FM 353
MDI set
Fig. 8-9 MDI block on the fly PIC741
Handling of the MDI block on the fly corresponds to that of the MDI block.
FM 353
FM 353
FM 353
folgSA
Fig. 8-12 Current block PIC731
FM 353
aktSA
Fig. 8-13 Continuation block PIC732
FM 353
The sum of the offsets and the actual value display are display fields.
FM 353
Frequency output value Hz
Switch readjustment in ref.:
Diff. betw. act. and setpoint pos.:
Pulse output counter
Einst MD
Fig. 8-15 Startup PIC76
FM 353
FM 353
FM 353
This screen displays the FM 353 errors. The fields are display fields.
FM 353
This screen displays the FM 353 errors. The fields are display fields.
Overview
The Table below tells you which Write requests must be submitted by the user pro-
gram and which signals are written directly to the FM.
Variable
User DB Description User DB
type
DBB17 BYTE Velocity or frequency level 1, 2 [BP] –
BOOL Single functions Internal
DBX34.0 Servo enable Write re-
DBX34.6 Parking axis quest
DBX35.6 Disable software limit monitoring
BOOL Single commands Internal
DBX37.0 Activate machine data Write re-
DBX37.1 Delete distance-to-go quest
DBX37.2 Automatic block advance
DBX37.3 Automatic block return
DBX37.5 Restart
DBX37.6 Undo set actual value
DBD140 DINT Zero offset DBX39.1
DBD144 DINT Set actual value DBX38.7
DBD156 DWORD Setpoint for incremental dimension DBX38.2
DBD160 DWORD Speed level 1 DBX38.0
DBD164 DWORD Speed level 2
DBD168 DWORD Frequency level 1 DBX38.1
DBD172 DWORD Frequency level 2
DBB176 STRUCT MD block DBX38.3
to
DBB195
DBB222 STRUCT MD block on-the-fly DBX38.4
to
DBB241
DBB242 BYTE Program selection – program number DBX39.5
DBB243 BYTE Program selection – block number
DBB244 BYTE Program selection – direction
DBB250 BYTE Teach In – program number DBX39.7
DBB251 BYTE Teach In – block number
DBW500 WORD MD No. –
DBD502 DINT/ MD value –
relev. MD
DBB506 BYTE SM No. –
Overview
The following table lists the parameters/data that can be read out during operation.
1) A variable in the S7 protocol is addressed by the DB No. and, depending on data format, by the DBB, DBW
and DBD No. (offset in DB), as well.
1) A variable in the S7 protocol is addressed by the DB No. and, depending on data format, by the DBB, DBW
and DBD No. (offset in DB), as well.
1) A variable in the S7 protocol is addressed by the DB No. and, depending on data format, by the DBB, DBW
and DBD No. (offset in DB), as well.
The control and checkback signals in Table 8-4 can be the following signals:
Bit 7 6 5 4 3 2 1 0
Byte
Control signals:
24 BFQ/ TFB
FSQ
25 AF SA EFG QMF R+ R– STP ST
26 BA
27 BP
28 OVERR
29
Checkback signals:
30 PARA DF BF/FS TFGS
31 PBR T-L WFG BL SFG
32 BAR
33 PEH FIWS SRFG FR+ FR– ME SYN
34 MNR
35 AMF
The following table describes the control and checkback signals in German and En-
glish.
Overview
This chapter describes the functions of the FM 353.
You can activate these functions via the user program by calling the appropriate
standard function blocks or technology functions.
Overview
The POS_CTRL block transfers the control signals from the user DB to the module
and transfers the checkback signals from the module to the user DB.
Bit 7 6 5 4 3 2 1 0
Byte
Control signals:
14 BFQ/ TFB
FSQ
15 AF SA EFG QMF R+ R– STP ST
16 BA
17 BP
18 OVERR
19
Checkback signals:
22 PARA DF BF/FS TFGS
23 PBR T-L WFG BL SFG
24 BAR
25 PEH FIWS SRFG FR+ FR– ME SYN
26 MNR
27 AMF
28
29
ACT_POS 1)
30
31
1) With FM firmware version V3.7.6 in conjunction with the blocks of the “FM353_354” library.
Overview
The axis is operated and controlled by means of control signals.
Table 9-1 describes the control signals and their functions.
Table 9-1 Control signals
Symbol
Name Function
English German
TEST_EN TFB Sw./over Interrupts communication with the user program, and switches over
P-bus the P bus interface for operation with the start-up user interface.
interface
OT_ERR_A BFQ/ Ack- ... resets an error message. Before acknowledging the error, correct
FSQ nowl. its cause.
opera-
tor/
travel
error
START ST Start ... starts movement in “Automatic”, “MDI” and “Reference-point ap-
proach” modes.
STOP STP Stop ... interrupts movement or processing of the program
... cancels reference point approach.
DIR_M R– Direc- ... moves axis in negative direction.
tion mi- S In Jogging and Control modes, moves axis in negative direction
nus (level-dependent).
S Starts movement in negative direction in Incremental relative and
Reference-point approach modes.
S Specifies direction of movement for rotary axes in MDI and Auto-
matic modes.
DIR_P R+ Direc- ... moves axis in positive direction.
tion plus S In Jogging and Control modes, moves axis in positive direction
(level-dependent).
S Starts movement in positive direction in Incremental relative and
Reference-point approach modes.
S Specifies direction of movement for rotary axes in MDI and Auto-
matic modes.
ACK_MF QMF Ac- ... only “acknowledge-driven” during M function output (seemachine
knowl- data list in Table 5-4, MD32).
edge M ... acknowledges receipt of M function. Program sequence can be
function continued.
READ_EN EFG Read-in ... prevents read-in (processing) of the next block
enable ... has effect only in Automatic mode.
The read-in enable is required in order to read in the next traversing
block during program execution.
SKIP_BLK SA Skip ... skips identified blocks in the program
block ... has effect only in Automatic mode.
Symbol
Name Function
English German
DRV_EN AF Drive ... enables movement.
enable When the signal is reset, a deceleration of the movement takes
place.
If MD 37.15 = 0, program execution or the movement is aborted and
the distance to go deleted.
If MD 37.15 = 1, the following applies (machining resumed after
emergency stop):
S Rapid deceleration of the movement.
S On axis standstill FR+ or FR– = 0; BL = 1
the drive remains activated and Servo Enable active
S If an error occurs in this state (e.g. the user starts the movement
without a Start Enable, etc.), the relevant error response is initi-
ated, e.g. the distance to go is deleted; BL = 0 (a new path must
be specified).
MODE_IN BA Operat- Operating mode (see Section 9.2) Code
ing Jogging 01
mode Open-loop control 02
Reference point approach 03
Incremental relative 04
MDI 06
Automatic 08
Automatic single block 09
MODE_ BP Mode ... selects speed levels in Jogging mode
TYPE parame- ... selects frequency levels in Control mode
ter
... selects increment in Incremental relative mode (value 1 – 100 or
254).
OVERRIDE OVERR Override ... affects response of traversing movement. Range: 0-255%
... override has no effect in Control mode
S Velocity override
Range: 0-255%
Speed adjusted by percentage
Example: Override doubled from 100% to 200%
v
200 %
vact
100 %
vprog
t
– speed v is doubled
–
acceleration and deceleration values are not affected
vprog Override
vact =
100
The positioning time is not cut in half.
Symbol
Name Function
English German
OVERRIDE OVERR Override S Time override
If you parameterize the “time override” function in MD37, there
are two ranges:
– range 100-255%: speed override operates as described
above
– range 0-100%: time override operative
Speed, acceleration and deceleration are changed in such a way
that the time necessary for the traversing movement is directly
correlated with the override value.
50 % vact
fss
t
– speed v is cut in half
– acceleration and deceleration are quartered
– Cut override in Start/Stop frequency
vprog Override a Override2 t 100
vact = aact = tact =
100 1002 Override
Positioning time is doubled.
Taking the override into account as a time override presupposes
the following additional condition:
If a traversing movement consists of multiple positioning blocks
with block change on-the-fly (the axis does not stop between
blocks), changing the override value affects only the speed.
Acceleration and deceleration are additionally affected only after
the axis comes to a stop (e.g., reversal of direction).
Note:
Time override has effect only in the MDI and Automatic modes.
Note
For further functions, settings and commands concerning open-loop control, see
Section 9.3.2 and Section 9.3.3.
Overview
The checkback signals indicate the processing status of the axis and report it to
the user program.
Table 9-2 describes the checkback signals and their functions.
Symbol
English Ger- Significance Function
man
TST_STAT TFGS Sw./over P Communication with the user program is not possible, since the
bus interface P bus interface has been switched over for operation with the
complete start-up tool.
OT_ERR BF/FS Operator/ ... signaled to the user if an operator-control error or travel error is
travel errors pending (e.g., unallowed control signal has been set, (R+) and
(R–) set simultaneously) An error message causes the move-
ment to be canceled.
See Section 11
DATA_ERR DF Data error ... is reported to the user when a data error occurs.
see Section 11
PARA PARA Parameterize ... module parameterized. All machine data applicable for control
of an axis are present on the module.
ST_ENBLD SFG Start enable ... signals that the FM 353 is ready for positioning and output.
S “Start enable” is set:
– if no static stop or error is pending and the drive enable is
pending
– if the mode setting and mode checkback match (after
mode change)
– if no axis functions (including M output, dwell time) are
active, or after functions have been completed
– for further processing of a function interrupted with unpro-
grammed stop
– in Automatic mode, after program has been selected (one
program active) and after M0, M2, M30, or at end of block
with Automatic single-block
S “Start enable” is deleted:
– if a function has been started and is active, or
– if a start condition is active (stat.)
– if there is an error and an unprogrammed stop
S Without Enable Start, none of the functions that can be oper-
ated with Travel Plus, Travel Minus and Start can be exe-
cuted.
Symbol
English Ger- Significance Function
man
WORKING BL Processing ... indicates that a function has been started with Start or Travel
in progress Plus/Minus, and is active.
S “Processing in progress” is set with:
– “Jogging”, “Control” mode during the movement up to
standstill after cancelation of R+, R–
– Reference-point approach mode, during approach until
reference point is reached
– MDI, Incremental relative mode, during the positioning
process or while functions of the MDI block are being
processed
– Automatic mode, during processing of a traversing pro-
gram until the end of the program.
S “Processing in progress” is deleted:
– by errors and restarts
– by mode changes.
– after axis standstill
WAIT_EI WFG Wait for ex- ... takes effect only if a digital input has been parameterized by
ternal enable means of MD34 (see Section 9.8.1).
Set: if the enable input has not yet been set or has been reset
when a movement has been activated.
DT_RUN T-L Dwell time ... only active in Automatic and MDI mode.
in progress As soon as a traversing block with a dwell time has been pro-
cessed, (T-L) is output during the programmed time period.
PR_BACK PBR Program ... is set after a Start in Automatic mode if a program is being
processing processed in reverse.
in reverse
MODE_OUT BAR Active mode The selected mode is not fed back until it is internally active. For
a mode change, for example, a movement must be stopped be-
fore another mode can become active (does not apply to switch-
ing between Automatic and Automatic single-block modes).
SYNC SYN Synchronism ... module is synchronized (see Section 9.6.1)
Required for axis motion in modes:
S Incremental Relative
S MDI
S Automatic
MSR_DONE ME End mea- ... signals an executed measurement (see Section 9.3.10)
surement
Symbol
English Ger- Significance Function
man
GO_P FR+ Travel plus ... means the axis is traveling in the direction of increasing actual
values or in the direction of frequency output “+” in Control mode
GO_M FR– Go_minus ... means the axis is traveling in the direction of decreasing ac-
tual values or in the direction of frequency output “–” in Control
mode.
S As soon as an active traversing movement is pending, the
messages (FR+) or (FR–) are output depending on the tra-
versing direction. They can only be pending as alternatives.
S “Travel Plus” or “Travel Minus” is actuated at the start of the
acceleration phase and remains active until the axis comes
to a standstill or the POS_ROD target area has been
reached.
ST_SERVO SRFG Servo enable S Feedback of servo enable status after single function has
status been activated
S See also Section 9.3.2 ”Servo enable”
S See also Section 11.1, error reaction ”Everything OFF”
FVAL_ FIWS Set actual ... set Actual value on-the-fly is executed.
DONE value on-the- The signal is reset when “Set actual value on-the-fly” is activated
fly complete (see Section 9.3.6).
NUM_MF MNR M function M command 0 – 99
number
STR_MF AMF Change M ... is indicated simultaneously with the M function number.
function S If M functions are programmed in a traversing block, their
output is signaled by setting “Change M function.”
S “Change M function” remains pending until:
– the specified time has expired, for time-controlled M func-
tions
– the user has acknowledged, for acknowledgment-con-
trolled M functions.
Symbol
English Ger- Significance Function
man
POS_RCD PEH Position S When the preset target position is reached correctly, (PEH) is
reached, actuated, and remains in effect until the next axis movement.
Stop (“PEH”) S (PEH) is actuated only in the following modes and cases:
– Reference-point approach: If the reference point has
been reached in full (including reference-point shift).
– MDI, Incremental relative: If the preset position has been
reached.
– Automatic: If a traversing block has been positioned in full
and the axis remains motionless until the next traversing
movement.
S It is not set if no synchronization is available yet.
ACT_POS ACT_ Actual posi- The firmware version V3.7.6 of the FM 353 positioning module in
POS tion conjunction with the blocks of the “FM353_354” block library pro-
vides direct access to the actual value. This is stored in the
checkback signals during the module cycle (2 ms) and read by
the POS_CTRL block. In addition, as previously, the actual value
is included as a DINT variable in the basic operating data read
request.
Overview
Before data/settings can be transferred to the FM 353, an operating mode must be
active (e.g. “Jogging” mode = 1 and MODE = 1). That means that communication
with the FM 353 has been initiated and the FM 353 has access to valid machine
data.
Error condition:
S Reported via BF/FS – acknowledgement with BFQ/FSQ
S Reported via DF – acknowledgement with next correct data transfer
S Reported via diagnostic interrupt – acknowledgement with “Restart”
(user DB, DBX37.5)
Module control
The following table lists the control signals used to start a movement.
Prerequisite: Drive enable [AF] = 1, Stop [STP] = 0,
Start enable [SFG] = 1
Switching edge
(e.g. R+, R–, Start,
according to mode)
Processing in progress
Enable start
The following table lists the control signals used to interrupt/terminate a movement.
Overview
The following operating modes are implemented on the FM 353:
S Jogging (ER) Code 01
S Open-loop control (STE) Code 02
S Reference point approach (REF) Code 03
S Incremental relative (SMR) Code 04
S MDI (Manual Data Input) Code 06
S Automatic (A) Code 08
S Automatic single block (AE) Code 09
Changing modes
Changing modes triggers an internal stop.
If a mode change is attempted while a traversing movement is in progress, the
modes are not switched until the axis comes to a stop. The mode checkback is
performed after the movement in the old mode is completed.
This does not apply to changes between Automatic and Automatic Single-Block
mode.
9.2.1 Jogging
Overview
In Jogging mode, axis traversing movements are specified by way of the direction
keys (R+ or R–) and by speed.
Velocity
Before the axis can be moved, speeds (velocities) 1 and 2 must first be transferred
to the FM 353 (user DB, DBX38.0).
You can choose between two mutually independent velocities (level 1 and level 2)
with the mode parameter (BP).
The velocity can also be controlled using the override, and can be changed during
the movement.
Note
Please see also Section 9.1.3!
Control actions
Preconditions:
S The FM 353 has been initialized.
S The mode has been selected and acknowledged.
S Drive Enable [AF] = 1 (control signal in user DB, DBX15.7)
S Stop [STP] = 0 (control signal in user DB, DBX15.1)
S Servo Enable (RF) = 1 (user DB, DBX34.0)
S Speed levels have been transferred.
Overview
In the “Control” mode, a frequency with selectable magnitude is specified and then
used to perform a controlled movement. The direction of movement is determined
by way of direction keys (R+ or R–).
The actual value of the axis is updated at the same time.
Note
A closed-loop controller, which may have been activated by a servo enable, is in-
terrupted while the frequency is being output. After the Jogging signals R+ or R–
have died off, servo control is referred to the new actual value, and reinstated after
the axis comes to a stop, if the servo controller enable is still active when the axis
stops.
Frequency values
The frequency is specified in the user DB, DBX38.1.
You can choose between two mutually independent frequency levels (level 1 and
level 2) with the mode parameter (BP).
Note
Please see also Section 9.1.3!
Control actions
The control and checkback signals are handled in the same way as in “Jogging”
mode.
Overview
In Reference-point approach mode, the direction keys (R+ or R–) or Start are used
to position the axis to a point (reference-point coordinate MD16) specified in the
machine data.
The axis is thus synchronized (see Section 9.6.1).
The override is set at 100% for the reducing speed.
An active zero offset or Set actual value is reset.
Machine data
The following table lists the machine data that is of significance for reference-point
approach:
Sequence of motions
Triggering of move-
Type of reference- (reference point offset = 0)
ment, direction for
point approach VA – referencing velocity
synchronization (R)
VR – reducing velocity
1st situation
Current-sourcing VA VR
pattern zero or
zero pulse exter-
nal, to right of – +
RPS
RPS Ref. pt.
2nd situation
VA V
Current-sourcing
pattern zero or R
zero pulse exter-
nal, to left of RPS – +
RPS
3rd situation
R+ (“edge-con- RPS centered VA
trolled”) or Start (no zero pulse V
necessary) R
– +
RPS
4th situation
VA
RPS edge
(no zero pulse V
necessary) R
– +
RPS
1st situation equals R+ 2nd situation
see above mirrored
2nd situation equals R+ 1st situation mir-
see above rored
3rd situation equals R+ 3rd situation
R– (“edge-con- RPS centered mirrored
trolled”) or Start (no zero pulse
necessary)
4th situation equals R+ 4th situation
RPS centered mirrored
(no zero pulse
necessary)
When crossing the RPS, a signal length of Δt w 2@FM cycle must be assured!
The following table shows you the exact location of the synchronization point on
the current-sourcing pattern zero or zero pulse external.
RPS
RPS NIX
Center
The value for the reference-point shift (MD27) is traveled after the synchronization
point is reached.
Note
Please see also Section 9.1.3!
Control actions
Preconditions:
S The FM 353 has been initialized.
S The mode has been selected and acknowledged.
S Drive Enable [AF] is = 1 (control signal in the user DB, DBX15.7)
S Stop [STP] = 0 (control signal in the user DB, DBX15.1)
S Servo Enable (RF) is = 1 (user DB, DBX34.0)
Table 9-4 Control actions for “Reference point approach” mode (examples)
Table 9-4 Control actions for “Reference point approach” mode (examples), continued
Overview
In the Incremental Relative mode it is possible to execute single positionings over
relative distances using user-definable increments.
The traversing movement is triggered with the direction keys (R+ and R–).
Position setting
Note
Please see also Section 9.1.3!
Control actions
Prerequisites:
S The FM 353 has been initialized.
S The mode has been selected and acknowledged.
S The Drive Enable [AF] = 1 (control signal in the user DB, DBX15.7)
S Stop [STP] = 0 (control signal in the user DB, DBX15.1)
S The Servo Enable (RF) = 1 (user DB, DBX34.0)
S Speed levels have been transferred.
S The axis is synchronized.
e.g. Travel plus [FR+] When the defined position has been reached, the axis
Processing in progress enables [PEH]; [SFG] and checkback signals [FR+]
[BL] and [BL] are reset.
Position reached, stop
[PEH]
Table 9-5 Control actions for “Incremental relative” mode (examples), continued
Overview
In the MDI mode it is possible to execute single positionings by way of traversing
blocks. These traversing blocks are provided by the user program.
The MDI block and MD block on-the-fly have an identical block structure.
MDI block
The structure of the MDI block is identical to that of the traversing blocks (see
Chapter 10 resp. Section 9.3.12) except that it has neither a program number nor a
block number.
The user program passes the “MDI block” (user DB, DBX38.3) to the FM 353, and
the block can then be executed. The block can be executed repeatedly, since it is
stored internally. The feedrate is override-dependent.
The MDI block remains in effect until it is overwritten with a new MDI block. A new
block can be transmitted while another block is being processed.
Block structure
The following table shows the block structure of the MDI block.
X/t Position/dwell time programmed (fills in value 1)
G1 – G2 G function group 1 – 2
M1 – M3 M function group 1 – 3
F Speed programmed (fills in value 2)
Note:
When the assignment bit (byte 2 and byte 3) is not set, the associated values must
be deleted.
Note
Please see also Section 9.1.3!
Control actions
Prerequisites:
S The FM 353 has been initialized.
S The mode has been selected and acknowledged.
S Drive Enable [AF] is = 1 (control signal in user DB, DBX15.7)
S Stop [STP] is = 0 (control signal in user DB, DBX15.1)
S Servo Enable (RF) is = 1 (user DB, DBX34.0)
S Axis is synchronized.
e.g. Travel plus [FR+] When the defined position has been reached, the axis
enables [PEH]; [SFG] and checkback signals [FR+]
Processing in progr. [BL]
and [BL] are reset.
Position reached, stop
[PEH]
9.2.6 Automatic
Overview
In the Automatic mode (following-block mode), the FM 353 processes traversing
programs autonomously. These programs are created with “Parameterize FM 353”
(see Chapter 5, 5.3.4) and stored as a data block. The traversing programs contain
information about movement sequences and outputs (see Chapter 10).
Program selection
Programs are selected (user DB, DBX39.5) by way of the user program, by speci-
fying a program number and an optional block number, as well as the direction of
machining. A program can be selected only when other programs have been inter-
rupted or terminated or at the start of a program.
A selected program remains active until it is inactivated by selecting program num-
ber = 0, or overwritten by selecting another program.
If modifications are made to a preselected program, including the subprogram, pre-
selection of the program is canceled. You must then select the program again. A
modification can be made to a program when BL = 0 (start of program/end of pro-
gram) and on Stop.
User DB allocation
Forward processing
The program processes the block numbers in ascending order.
Processing begins at Start, with the first block (specified block number = 0).
If processing is to begin at some other point of the traversing program, specify the
desired block number.
Processing will take place by searching forward to this block, then processing for-
ward until the program end command is recognized.
Backward processing
The program processes the block numbers in descending order.
Processing begins at Start, with the last block (specified block number = 0).
If processing is to begin at some other point of the traversing program, specify the
desired block number. Processing will take place by searching back to this block,
then processing in reverse until the program beginning is recognized.
Note
If reverse processing is to execute the same sequence of movements as the for-
ward movement, the effects of the corresponding commands must be taken into
account in the programming. For example:
S M outputs should be written separately in a block;
note M output (MD32) and G60/G64.
S Note change between G60/G64 and G90/G91.
S Note start and end of tool offsets.
S M18 is not executed.
S M02 and M30 at the end of the program are not processed.
Block advance
The program is prepared up to the end point of the target block; the tool offset, M
commands and dwell times are output; and the traversing movements are sup-
pressed.
When processing traversing programs with a forward block search, there are a
number of special cases:
S The external forward block search (G50) is not executed.
S Continuous travel with functions to set (G88, 89) or delete (G87) an actual
value on-the-fly is not executed.
S The blocks under G50, G87, G88, G89 (in the processing direction) should con-
tain a path in absolute coordinates.
Block return
Similar to block advance
Control actions
Prerequisites:
S The FM 353 has been inititalized.
S The mode has been selected and acknowledged.
S Drive Enable [AF] is = 1 (control signal in user DB, DBX15.7)
S Stop [STP] is = 0 (control signal in user DB, DBX15.1)
S Servo Enable (RF) is = 1 (user DB, DBX34.0)
S Axis is synchronized.
Control action 6, cancelation of the read-in enable during program execution (special situationl)
Control signal: If [EFG] is canceled during program execution, the
Read-in enable [EFG] current block is processed up to the end, and program
execution is then suspended.
Checkback signals:
[FR+] and [FR–] are reset.
Travel plus [FR+] or Travel
minus [FR–] [PEH] is actuated.
Position reached, stop
[PEH]
Control action 7, resume program execution after read-in enable (special situation)
Control signal: The program resumes on [EFG].
Read-in enable [EFG]
Checkback signals:
Travel plus [FR+] or Travel [FR+] and [FR–] are reset.
minus [FR–] [PEH] is reset.
Position reached, stop
[PEH]
Control action 8, stop during positioning with new start signal for resumed positioning
(special situation)
Control signals: Interrupt with Stop
Stop [STP] [FR+] is cleared when the axis comes to a standstill,
Start [ST] and [SFG] is enabled (if Stop is not active). [PEH] re-
mains cleared, since the defined position has not yet
Checkback signals:
been reached.
Position reached, stop
Start clears [SFG] and enables [FR+] again.
[PEH]
[BL] remains enabled.
Travel plus [FR+]
Before the axis comes to a standstill, it is possible to
Start enable [SFG]
define a new direction “through start”.
Processing in progress
[BL]
Control action 9, end of program reached
Checkback signals: The end of the program is indicated by the enabling of
Travel plus [FR+] or [PEH], output of M2, M30 and resetting of [BL].
Travel minus [FR–]
Processing in progr. [BL]
Position reached, stop
[PEH]
M function number [MNR]
Start enable [SFG]
Overview
Functions, same as “Automatic” mode
Whereas in “Automatic” mode the FM 353 automatically starts processing the next
block after completing a given block, in “Automatic single-block” mode the axis
waits for a new Start signal after processing each block that contains a traversing
path, dwell time or M command (except for blocks with G50, G88 or G89).
You can change between Automatic single-block and Automatic mode at any time,
without stopping the movement or interrupting the output.
Overview
This chapter describes settings and functions that apply in multiple modes, and
that are likewise necessary in order to control and operate the FM 353, and data of
the FM available for checkback messages.
S Change parameters/data (Write request in user DB, DBX39.3), page 9-38
S Single functions (user DB, DBB34 and 35), page 9-42
S Single functions (user DB, DBB36 and 37), page 9-44
S Zero offset (Write request in the user DB, DBX39.1), page 9-46
S Set actual value (Write request in the user DB, DBX38.7), page 9-48
S Set actual value on-the-fly (Write request in the user DB, DBX39.0), page 9-49
S Request application data (Write request in the user DB, DBX39.6), page 9-50
S Teach in (Write request in the user DB, DBX39.7), page 9-51
S Set reference point (Write request in the user DB, DBX38.6), page 9-51
S Measured values, page 9-52
S Basic operating data (Read request in the user DB, DBX42.0), page 9-55
S Active NC block (Read request in the user DB, DBX42.1),
next NC block (Read request in the user DB, DBX42.2), page 9-56
S Application data (Read request in the user DB, DBX43.6), page 9-57
S Actual value block change (Read request in the user DB, DBX42.3), page 9-57
S Servicing data (Read request in the user DB, DBX42.4), page 9-57
S Additional operating data (Read request in the user DB, DBX43.5), page 9-58
S Parameters/data (Read request in the user DB, DBX43.3), page 9-58
Overview
You can use this function to modify parameters and data in the FM 353 data blocks
or to define parameters and data which can then be read out with a Read request
(user DB, DBX43.3) (see Section 9.3.17).
Addr. in Data
Symbol Description
user DB format
196 Byte DB type type 1 = MD 2 = SM 3 = TO 4 = NC (travers-
ing program)
197 Byte Number Info 1 MD No. SM No. (1 – TO No. Progr. No.
(5 – 45) 100) (1 – 20) (1 – 199)
198 Byte Number Info 2 Number of Number of 0 = Tool offset Block No.
MDs, con- SMs, con- complete (1 – 255)
secutive secutive 1 = Tool length
(1 – 5) (1 – 5) only
2 = Wear value
abs. only
3 = Wear value
add. only
199 Byte Job 1 = Read job parameters
2 = Write parameters
4 = Write parameters and save retentively1)
200 – de- Data S MD: Data format of machine data see Table 5-4 or
219 pends field S SM: Data format of increments see Table 5-5 (DWORD) or
on type
S WK: Data format of tool offset see Table 5-6 (DINT) or
S NC: Block format see Section 9.3.12 ”Active NC block”
Example 1
The software limit switches (MD21, MD22) for the axis are to be set to the values
100 mm and 50,000 mm. These values are to remain in effect only until the unit is
shut down.
DB type =1
Data number = 21
Number of data =2
Job type =2
Data array
Byte 200 –203 = 100,000 (MD21, data format DINT)
Byte 204 – 207 = 50,000,000 (MD22, data format DINT)
Bytes from 208 on =0
For activation of the machine data, see Section 9.3.3
Notes
Please note the following when changing the parameter data:
S Machine data
Machine data can always be modified. Once you have modified the machine
data, the machine data have to be reactivated (for single command, see Sec-
tion 9.3.3).
S Increments
Modifications can be made in all operating modes (even in “Incremental rela-
tive” mode) during movement. The modifications of the increments must always
be complete before a new movement is started in “Incremental relative” mode.
If this is not the case, the error message “incremental dimensions do not exist”
is output Cl. 2/No. 13.
S Tool offset data
Modifications can be made in all operating modes and during movement. If
modifications are made during starting or at block transitions when the tool
compensation is active (internal access to offset values), the error message
“tool offset value does not exist” is output Cl.3/No.35.
S Traversing programs
– Programs which are not selected can always be modified.
– If modifications are made to a preselected program, including the subpro-
gram, preselection of the program is canceled. You must then select the pro-
gram again. A modification can be made to a program when BL = 0 (start of
program/end of program) and on Stop.
Delete block: Specify the program no. and the block no. in the “data field”.
The other data/bits must not be assigned.
Insert block: The block number does not exist in the selected program.
The contents should be entered in accordance with
the “block format”.
Modify block: The block with the corresponding block number is
overwritten with the contents in accordance with “block format”.
Example 2
Procedure for changing the actual value and the velocity in block 10 of traversing
program 1.
1. Submit job request to read the block. Enter the following values in the user DB:
DB type = 4
Number = 1
Number of data = 10
Job type = 1
Data array = 0
2. Set Write request (user DB, DBX39.3).
3. Following termination of the Write request (one cycle later), read out the block
by setting the Read request (user DB, DBX43.3).
4. Save the data read out from DBB 446 to 469 of the user DB in DBB196 to 219.
5. Enter the actual value in data array DBB208 to 211 in the user DB (data type
DINT).
6. Enter the velocity in DBB212 to 215 of the user DB (data type DINT).
7. Enter a 4 in DBB199 of the user DB (request) (retentive storing of the block).
8. Set Write request (user DB, DBX39.3).
Block sizes:
DB machine data 284 bytes
DB increments 468 bytes
DB tool offset data 308 bytes
DB traversing programs 108 + (20 x no. of traversing blocks) bytes
Example:
Assuming a service life of 10 years and 24-hour operation, a typical limit = 10 6.
Note
SDB w 1 000 (system data block, created for module replacement), contains pa-
rameter data which were valid at the time of start-up. If data/parameters are modi-
fied during operation and stored retentively on the FM, these data are not con-
tained in SDB w 1 000. These modifications are lost when the module is replaced,
and should be traceable in the user program.
Overview
You can use this function to transfer single settings to the FM 353 and activate the
corresponding functions. These settings are:
S Length measurement
S Inprocess measurement
S Retrigger reference point
S Switch off enable input
S Switch off software end position monitoring
S Servo enable
S Rotation monitoring
S Parking axis
S Simulation
Start Target
– RPS +
Zero pulse Zero pulse for
synchronization
Rotation monitoring
Rotation monitoring is performed in all operating modes. It is automatically inter-
rupted as the synchronization mark is passed in “Reference point approach” mode
and in “Retrigger reference point” function.
The “rotation monitoring” function is described in Section 9.7.3.
Servo enable
You can use this function to:
S Activate the control function “Positioning”
S Switch the signal through to the drive as indicated in MD37
Parking axis
You can use this function to achieve the following:
S Pending error messages are deleted and no new ones are triggered (including
diagnostic interrupts)
S Digital outputs are inactive
The setting can be switched on or off if “Processing in progress” = 0.
Simulation
You can use this function to:
S Test function sequences without the drive and measuring system.
A drive, if any connected, must be switched off.
S Evaluate all digital inputs (Caution, if you are going to simulate sequences that
use such signals, they should be connected to the inputs of the FM 353 - e.g.
for Reference-Point Approach).
S The servo simulates a controlled system; “Controller Ready” is not necessary.
S The setting can be switched on or off if “Processing in progress” = 0.
S All internal function sequences behave as in normal operation.
When the function is deactivated, the axis is reset internally (see Restart,
Section 9.3.3).
Overview
You can use this function to transfer single commands to the FM 353. These com-
mands are:
S Activate machine data
S Delete residual distance
S Automatic block search in reverse
S Automatic block advance
S Restart
S Remove setting actual value
Restart
You can use this command to reset the axis.
S Pulse output is interrupted.
S The instantaneous processing status is canceled, and synchronization in incre-
mental encoders is deleted.
S Active compensation values are deleted.
S An acknowledge signal is issued for all errors.
Actual posi-
tion = 100
Zero offset by –50
(shift of reference
point)
–50
Actual position
= 150
– Zero point
Rotary axis
The following restriction applies to a rotary axis:
Zero offset < Rotary-axis range. The actual value is normalized.
Example:
9.3.5 Set actual value (Write request in the user DB, DBX38.7)
Overview
You can use this function to assign a new value to the current actual value.
Actual position
Set actual
= 100
value to 150
9.3.6 Set actual value on-the-fly (Write request in the user DB,
DBX39.0)
Overview
You can use this function to assign a new value to the actual value by means of an
external event.
Overview
A selection of up to four display data items whose values can be read out with
“read application data” (see Section 9.3.13).
Code table:
Code Significance
0 No parameter request
1 Actual position
2 Actual speed
3 Residual distance
4 Set position
5 Total current coordinate shift
6 Rotational speed
16 Frequency output value
17 Pulse output counter (0...216–1) [pulse]
20 Difference between target and actual position [MSR]
22 Switch adjustment in “Reference point approach” mode
Overview
In a program block selected with the program number and block number, the cur-
rent actual position is entered as a position setpoint (Caution: This is an absolute
position).
The Teach-in facility is possible only in the following modes:
S Jogging
S Incremental Relative
S MDI
and while the axis is not in motion.
The program and the appropriate program block must be present on the FM 353
(see Parameterization, Chapter 5).
9.3.9 Set reference point (Write request in the user DB, DBX38.6)
Overview
You can use this function to synchronize the axis without reference point approach.
Function
With Set Reference Point, a position value at the instantaneous position of the
axis, indicated as a parameter, is accepted as an actual value.
”Set reference point” is not possible during machining ([BL] = 1) and will only come
into effect after machining ([BL] = 0).
This function is not effective in “Automatic” mode (mode 08) or in “Automatic
Single block” mode (mode 09).
Prerequisites
The following prerequisites must be fulfilled to execute the “Measuring” function:
1. Connect a bounce-free switching-signal encoder (sensing probe) to a digital
output of the FM 353.
2. Parameterize “Measurement” for this input in MD34.
Function description
Measurement functions can be executed in all modes. An executed measurement
is signaled by the checkback signal “ME” and optionally also by a process inter-
rupt.
Inprocess measurement
The present actual position is captured at each rising edge of the touch probe. At
the same time, the axis movement is interrupted (servo-controlled braking).
Inprocess measurement On
Measurement input
Process interrupt
S1
S1 – execution of measurement
Length measurement
The current actual position value is acquired at both the rising and the subsequent
falling edge of the sensing probe. In addition, the distance (absolute value) actually
traversed between the two edges is determined.
Length measurement On
Measurement input
Process interrupt
Measurement taking place
Error messages
The following table lists the errors that can occur in the execution of the Measure-
ment function.
Error Significance
Travel er- The “Digital input not parameterized” error is signaled when a measurement function is
rors selected without a digital input having been parameterized (see Troubleshooting, Table
11-7, Class 3 No. 30).
Operator The “Measurement function undefined” error is signaled when both measuring functions
contr. errors are selected (see Troubleshooting, Table 11-6, Class 2 No. 16).
Measuring An erroneous length measurement is indicated by signaling back the length “–1.” Possible
error causes include:
S Resynchronization in the Reference-Point Approach mode while a measurement is in
progress
S Execution of the Set Reference Point function while a measurement is in progress
S Direction of travel at the falling edge is opposite to the direction of travel of the previous
rising edge
No. Value 0 Value “–1” All other posi- All other nega-
tive values tive values
1 the Length Measurement and Inprocess Actual position for rising touch-probe edge in Inpro-
Measurement functions are inactive cess Measurement and Length Measurement func-
tions
2 S the Length Measurement and Inprocess Actual position for falling touch-probe edge in
Measurement functions are inactive Length Measurement function
S always with the Inprocess Measurement
function
3 S the Length Measurement and Inprocess Erroneous Measured Nonexistent
Measurement functions are inactive length mea- length
S always with the Inprocess Measurement surement
function
S measured length 0 is actually possible,
because touch probe has been con-
nected while axis is stationary
9.3.11 Basic operating data (Read request in the user DB, DBX42.0)
Overview
The following display data are basic operating data:
S Actual position [MSR]
S Actual speed [MSR/min]
S Distance-to-go [MSR]
S Set position [MSR]
S Total of active coordinate shifts for tool offset, zero offset [MSR]
S Rotational speed (rotary axis only) [rpm]
9.3.12 Active NC block (Read request in the user DB, DBX42.1), next
NC block (Read request in the user DB, DBX42.2)
Active NC block
... are display data in “Automatic” mode
/ Skipped block
L Subprogram callup (fills in UP number)
P Number of runs for subprogram (fills in UP number of runs)
X/t Position/dwell time programmed (fills in value 1)
G1-G3 G function group 1-3
D Tool offset value number
M1-M3 M function group 1-3
F Speed programmed (fills in value 2)
Next NC block
as described in “active NC block”
Overview
The values requested with “Request application data” (user DB, DBX39.6, see
Section 9.3.7) are returned by the FM 353 when the user submits the Read re-
quest (user DB, DBX43.6).
9.3.14 Actual value block change (Read request in the user DB,
DBX42.3)
Overview
The “actual value block change” function is described in Section 10.1, G50, G88,
G89.
Overview
The following display data of the measuring circuit are servicing data:
S Frequency output value [Hz]
S Pulse output counter (0...2 16-1) [pulse]
S Difference between target and actual position [MSR]
S Switch alignment in BA “Reference point approach” [MSR]
Overview
The following display data are additional operating data:
S Override [%]
S NC traversing program No.
S NC block No.
S UP callup counter
S G90/91 active, see Section 10.1
S G60/64 active, see Section 10.1
S G43/44 active, see Section 10.1
S D No. active, see Section 10.1
S Status messages 1 (data type: BOOL):
Velocity limitation to maximum frequency MD41
S Status messages 2 (data type: BOOL):
When the acceleration or time override is programmed, a displayed limitation of
the active limitation occurs in the event that the working range of the frequency
generator of the FM 353 is violated (compare the diagram “Working range, fre-
quency generator” Figure 5-5):
– Start/Stop frequency is limited (MD39)
– Frequency value for acceleration switchover limited (MD40)
– Acceleration/delay value is limited (MD42 – MD45)
Overview
This request is used to read the parameters and data modified by means of the
“Change parameters/data” function (Write request in the user DB, DBX39.3, see
Section 9.3.1).
Overview
At the start of parameterization, you must fill in the basic machine data item sys-
tem of measurement (MD7). This item governs the input of values.
Examples
The sample values in the table below illustrate the relation between the system of
measurement and internal values:
Note
The measurement system (MD7) must match the measurement system specified
in the other DBs.
The measurement system raster (MSR) is the smallest distance unit in the active
system of measurement.
If at some point you have failed to take this precaution:
1. Delete all data blocks (which do not match the measurement system) or clear
the memory of the FM 353 completely.
2. Modify the other data blocks on the PG.
3. Reload the data blocks to the FM 353.
Overview
You can select the axis type with machine data item MD8. Choose either of the
following types:
S Linear axis
S Rotary axis
Linear axis
A linear axis moves between two range limits (traversing range min –10 9, max
109). The range limits may be bounded by software limit switches (MD21, MD22)
to form the “working range.”
Linear axes have a limited traversing range. The limits are imposed by the:
S Resolution of the numerical scale
S The range covered by an absolute encoder.
Movement
M G
Motor Encoder
Rotary axis
With rotary axes, the actual value is reset to “0” after one revolution. Rotary axes
thus have an infinite traversing range.
0
9 999
5 000
Before you start a movement in “MDI” and “Automatic” modes, you can define a
fixed direction of rotation with R+ or R–.
Rotary axes are subject to certain restrictions in the choice of gear ratio, as shown
in Figure 9-5. These restrictions arise from the need to reproduce the actual posi-
tion accurately over several revolutions when referencing with one periodic zero
pulse per motor revolution (type of reference point approach < 4). See also “De-
pendencies”, Section 5.3.1).
SRA = nSSZ
n = 1, 2, 3
Examples:
Overview
The FM 353 operates without encoders.
The position resolution of the axis is determined by the traversing distance of one
motor increment.
The control frequency pulses emitted by the FM 353 are added internally to form a
position value.
Function parameters
The following table shows you how to adapt a stepper motor to the FM 353.
Overview
When stepper motors are used, there is an unknown offset between the internal
position value and the mechanical position of the axis after the FM is switched on.
To establish the position reference, the value internal to the FM must be synchro-
nized with the real position value of the axis. Synchronization is performed by tak-
ing over a position value at a known point of the axis.
Reference point
is a fixed point on the axis. It is:
S The target coordinate in the Reference-Point Approach mode
S Removed from the synchronization point by the amount of the reference-point
shift, in axes with incremental encoders.
Synchronization point
is a defined point on the traversing path of the axis. It is defined by the mechanical
position of a reference-point switch or in association with a cyclic zero mark of an
incremental encoder.
Synchronization
Creating the position reference between the internal FM position value and me-
chanical position of the axis.
Current-sourcing pattern
zero or zero pulse external
Axis direction +
RPS
With reference to the synchronization point, the reference point can be located on
the side of the lower or the higher position actual values. In the “reference point
approach” operating mode the machine axis additionally traverses this distance,
during its last phase of motion, once the synchronization point has been found.
Consequently, the axis halts the motion, in each instance, exactly on the reference
point.
Example
RV +
RV –
Overview
Actuation of the stepper drive for controlling the movement sequence takes place
by way of the signals “Pulse” (frequency) and “Direction”. These signals are gener-
ated by a frequency generator in each operating mode of the FM 353. The pulse
width is a constant 50% of the period of the maximum frequency parameterized.
The diagram 9-6 gives you an overview of the function units and the machine data
acting upon them.
Direction
s
Interpolator Backlash f generation
Setpoint compensation
value s f Pulse
v t
t
Stepper mo-
Phase current Boost/PWM
MD21 MD22 tor control
control
active/inactive high/low
Backlash compensation
Mechanical drive elements generally have a certain amount of backlash (play).
MD30 provides compensation of mechanical reversal backlash. With each reversal
of direction, the mechanical backlash runs through before any axis movement
takes place. This results in positioning errors.
– +
Spindle
A backlash figure entered in the MD30 is calculated, with correction, by the stepper
motor control as a factor of the current traversing direction of the axis. The result
is an approximate compensation of backlash during positioning.
In MD31, the “backlash-free” traversing direction of the axis is identified. When
MD31 = 0, that direction is considered to be “backlash-free” which corresponds to
the direction of the axis movement at the time synchronization is begun. This cor-
responds to the following correspondence, as a factor of MD18:
MD18 = 0,2,4,8: Plus direction is backlash-free
MD18 = 1, 3, 5, 9: minus-direction backlash-free
Function parameters
The following table shows you which parameters to use in matching frequency
generation to the selected stepper drive.
Frequency profile
In controlling speed, special importance is attached to the drive-specific require-
ments regarding the shape of the frequency/time function. Based on this, a discon-
tinuous traversing movement is initiated or stopped below the Start/Stop frequency.
For higher traversing velocities, a ramp-shaped control cycle, which builds on the
Start/Stop frequency, takes place within two velocity ranges with acceleration val-
ues of different parameterization capability .
The following illustrations provide you with examples of frequency profiles for se-
lected traversing movements.
Maximum speed frequency profile
f
fmax
feg
ab2
av2
fss
ab1 av1
t
f
fmax
f2
feg
f1
f3
fss
t
N1 N2 N3
f1 – Frequency in set N1/Override value 1
f2 – Frequency in set N2/Override value 2
f3 – Frequency in set N3/Override value 3
Stop
f
fmax
feg
fss
t
tvk tst
N1 N2
Overview
As a minimum, actuation of the stepper drive for controlling the movement se-
quence takes place by way of the signals “Pulse” and “Direction”. By way of these
signals for specifying distance beyond the stepper drive, the FM 353 optionally pro-
cesses additional signals from different drive ports.
MD Designation Value/Meaning
37 Special control signals
37.8 Pulse output inverted 0: Pulse high active Output signal
1: Pulse low active
37.9 Direction output inverted 0: low sign. = direction + Output signal
1: low sign. = direction –
MD Designation Value/Meaning
37 Special control signals
37.0 Controller enable active 0: Signal not used Output signal
1: Signal used
37.2 Controller ready active 0: Signal not connected Input signal
1: Signal is connected
37.3 Controller ready inverted 0: Controller ready high active
1: Controller ready low active
37.4 Controller ready input 0: at Front panel connector X1 (RM)
selection 1: at D Sub connector X2
(Ready1_N)
In all operating modes except Control mode, the “servo enable” signal is required
for the duration of every traversing movement, irrespective of the parameter defini-
tions. If the servo enable is not detected or is deactivated during the movement,
the “servo enable missing” message is triggered (see Table 11-5, Class 3/No. 61).
In all operating modes except Control mode, the “servo ready” signal is required for
the duration of every traversing movement when the parameter is active (MD37.2).
If the servo ready is not detected or is deactivated during the movement, the
“servo not ready” message is triggered (see Table 11-5, Class 3/No. 62).
The following table shows you the available machine data for parameterizing the
function.
MD Designation Value/Meaning
37 Special control signals
37.16 Boost active 0:Boost function not used Output signal
1:Boost function used
37.17 Boost inverted 0:Boost signal high active
1:Boost signal low active
37.18 PWM active 0:PWM function not used
1:PWM function used
37.19 PWM inverted 0:PWM pulse high active
1:PWM pulse low active
48 Boost duration absolute 1 – 1,000,000 ms
49 Boost duration relative 1 – 100%
50 Phase current travel Pulse duty factor [%]
51 Phase current idle
Function, PWM:
The signal is generated as a 20 kHz frequency.
Boost function:
The signal is monitored with reference to the maximum absolute and relative active
phase.
Effect: PWM
The motor phase current can be changed between 0 % and 100 %. Current modifi-
cation is possible at zero speed and during continuous travel. On acceleration/de-
celeration, the current is always 100 % (max).
fpulse
PWM
IPWM
100 %
MD50
MD51
Effect: Boost
During acceleration/deceleration, the activated boost signal triggers a current in-
crease on the drive unit. The amount of the increase is set on the drive unit. At
zero speed and during continuous travel, the current is always 100 %.
fpulse
t
IBoost
100 %
Note
When using this signal, the signal “Controller ready” can be processed only by way
of the D Sub connector X2 (Signal Ready1_N)!
The following table shows you the available machine data for parameterizing the
function.
MD Designation Value/Meaning
37 Special control signals
37.24 Current-sourcing pattern zero active 0:Current-sourcing pattern Input signal
zero not used
1:Current-sourcing pattern
zero used
37.25 Current-sourcing pattern zero in- 0:Current-sourcing pattern
verted zero high active
1:Current-sourcing pattern
zero low active
37.26 Zero pulse external active 0:Zero pulse external not
used
1:Zero pulse external
used
37.27 Zero pulse external inverted 0:Zero pulse external high
active
1:Zero pulse external low
active
38 No. of increments/current-sourcing 0...4001)
pattern cycle2)
Prerequisites
The following prerequisites must be met for the “Rotation monitoring” function:
1. External zero pulse (NIX) which is generated cyclically, precisely once per mo-
tor revolution
Condition:
At the maximum speed of the stepper motor, a signal length of Δt w 2@FM
cycle must be assured for the external zero pulse!
2. Connection to the “Servo message” input of the FM 353’s front panel connector.
3. Parameterization of the external zero pulse (MD37.26)
4. Use of the current-sourcing pattern zero signal is not allowed!
Error message
The following errors are reported:
S Error “Digital input not parameterized” (see Troubleshooting, Table 11-5,
Kl. 3/Nr. 30)
Selecting function without parameterization for NIX
S “Rotation monitoring” error (see Troubleshooting, Table 11-5, Cl. 3/No. 66)
– Motor turns too slowly (during acceleration/travel)
– Motor turns too fast (during acceleration/travel)
– External zero pulse failed
– Incorrect number of increments per motor revolution parameterized (MD13)
Function description
The external zero pulse is used as described below to monitor the motor rotation
as specified in controlled operation (see Figure 9-10)
S The first NIX received synchronizes rotation monitoring.
S The first NIX must arrive within the period elapsing during two stepper motor
rotations + 45°. Otherwise, the ”Rotation monitoring” error message will be trig-
gered.
S With every further NIX received, the system verifies whether the current pulse
output of the stepper motor is within a window n 360° "45°. The error “Rota-
tion monitoring” is triggered by the occurrence of NIX edges which are outside
the allowed window.
S With every FM cycle the system verifies whether the pulse output is outside a
window " (360° + 45°) since receipt of the last NIX. Positioning outside this
allowable window also triggers the “Rotation monitoring” error.
S Stepper motor rotation without a specified setpoint value likewise triggers a
“Rotation monitoring” error in response to the NIX edges caused by the un-
wanted rotation. This occurs whenever the previous setpoint position falls within
the range outside the allowable window for the NIX edges. No error is triggered
if the previous setpoint position is within the admissible window as there is no
way of distinguishing between oscillation on a NIX edge position on account of
a fault or full motor rotation.
S Rotation monitoring is automatically discontinued whenever the synchronization
mark is passed over in the “Reference point approach” operating mode, and the
function “Retrigger reference point approach” is executed.
X
–45°
B
NIX
A
+45°
Fig. 9-10 Allowable range relative position for the external pulse
Overview
Four digital inputs and four digital outputs of the FM 353 can be used specifically to
a given application.
The conventions and parameterization for this purpose are defined in the machine
data MD34 to MD36.
The signals are processed in the FM cycle.
The signal status of the digital inputs and outputs can be recognized by readback
(user DB, DBX43.4).
Function parameters
Table 9-9 shows you the functions assigned to each input/output.
Level adjustment
External start
The control signals of the axis include the start signal which triggers a positioning
operation in “Reference point approach”, “MDI” and “Automatic” modes. A logical
OR is established with the “External Start” digital input and the control signal (ST).
External start is connected to digital input I1.
Example
ST 1
w1 3
Control signal (Start)
Digital “External start” input 2
1
2
Enable input
Setting the enable input is a prerequisite for positioning, movement or output of an
axis, if this is parameterized with MD34. A reset stops the movement (external
movement enable).
S In the Jogging and Control modes, the movement of the axis proceeds as long
as the AND link continues between the control signal (R+/R–) and the enable
input.
Example
R+ or R– 1
& 3
Positioning
2
Enable
1
2
Reference point switch for reference point approach See Section 9.2.3
Direct output
Outputs Q0...Q3 (D_OUT1...D_OUT4), which are defined in MD35 as “direct out-
put”, can be used directly by the user program (user DB, DBX39.4) and can also
be controlled by the FM 353.
Since the same memory is used in the user DB for W rite request (user DB,
DBX39.4) and Read request (user DB, DBX43.4), the jobs cannot be used simulta-
neously in the cycle.
Note
The outputs are subject to deactivation on module errors of error classes with the
response “Everything Off”.
Overview
To limit the working range, entries in the machine data (MD21 and MD22) specify
the start and stop limit switches. These limit switches are active at synchronization
of the axis.
If the limit switches are not needed, values lying outside the possible working
range should be entered in the machine data (MD21 and M22), or monitoring
should be switched off via the user program.
Warning
! The software limit switches do not replace the hardware limit switches for EMER-
GENCY STOP responses.
Rotary axis
The end position of MDstart may be greater than MD stop.
When traveling into the working range (e.g. end position was previously switched
off), the shortest path is always chosen.
If both default values are parameterized the software limit switches are inactive.
Overview
Process interrupts are interrupts that quickly signal states in the current process to
the user program.
The appropriate setting in the machine data (MD5) specifies which signals are to
be quickly communicated to the user program.
Process-interrupt generation
The process interrupt is generated by way of machine data item MD5:
MD Designation Significance
5 Process-interrupt genera- 0 = Position reached
tion (data type - bit field) 1 = Length measurement completed
3 = Change block on-the-fly
4 = Inprocess measurement
Overview
To execute the desired operations of the machine axis (sequence, position, etc.) in
“Automatic” mode, the FM 353 needs certain information. This information is pro-
grammed with “Parameterize FM 353” (traversing program creation) in the form of
a traversing program, based in principle on DIN 66025.
Traversing programs
Each traversing program is stored under a program number.
A traversing program consists of not more than 100 traversing blocks.
The program number and traversing blocks are converted to an internal format
(see Section 9.3.12), are stored in the appropriate data block, and are transferred
to the module. where they are administered.
The possible number of programs depends on the amount of memory available
(max. 16 Kbytes) and on the length of the individual programs.
Program length in bytes: 108 + (20 x no. of traversing blocks)
Program name
Any program can be assigned a name (optional).
The program name may have up to 18 characters, and is saved with the program.
Program number
Programs may be numbered from % 1 to % 199.
Traversing block
A traversing block contains all the data required to perform a machining step.
Program structure
A program consists of several blocks. Each block number occurs only once, and
numbers are arranged in ascending order.
A sample program structure follows:
/ N G1 G2 G3 X/t F M1 M2 M3 D L P
Block structure
The following Figure gives you an overview of the structure of traversing blocks.
/ N G1 G2 G3 X/t F M1 M2 M3 D L P
Skip block /
Program blocks which are not to be executed every time the program runs can be
identified as skippable blocks by an oblique “/ ”. When the program is being pro-
cessed, the “Skip block” control signal can be used to decide whether skippable
blocks are to be skipped. The last block may not be skipped.
Block number N
The program is executed in ascending order of block numbers (1 to 255) or in de-
scending order if executed in reverse.
G function group 1 – 3
In each traversing block only one G function may be entered from each G function
group.
The following figure shows an example.
/ N G1 G2 G3 X/t F M1 M2 M3 D
G functions
Table 10-1 lists the possible G functions and the individual G function groups.
1) These G functions take effect only on a block-by-block basis. The other G functions remain
active until canceled explicitly.
G30, G90 and G64 are the initial settings after the start of the program.
Dwell G04
A traversing block with dwell can only contain M functions and the time parameter
apart from this G function.
The following applies for dwell time:
Odd input values are rounded upward. Dwell times take effect only on a block-by-
block basis.
If no value is input for G04 in the block, the lower input limit applies.
/ N G1 G2 G3 X/t F M1 M2 M3 D
10 50 10 000 1 000
20 12 000 1 300
F
N10 N20
1 300
1 000
ÍÍ
E 10 000 12 000
E – digital input
ÍÍ X
/ N G1 G2 G3 X/t F M1 M2 M3 D
V
N10 N15 N20 N25
t
Reversal of direc-
I tion
Í t
I
N10 N15 N25
X System of measure-
0 50 100 150 200 250 300 350 400 ment normal
N20
System of X
measurement
0 50 100 150 200 250 300 350 400
shifted
I – digital input
Note
The G functions G87, G88 and G89 take effect only on a block-by-block basis and
must be reselected if necessary.
/ N G1 G2 G3 X/t F M1 M2 M3 D
90 20 100
Programmed Actual position
position
0 10 20 30 40 50 mm
Note
To ensure precise reproduction of the program, the first block should contain refer-
ence-measure programming.
/ N G1 G2 G3 X/t F M1 M2 M3 D
91 –30 100
0 10 20 30 40 50 mm
Option 1 Option 2
Set position 0_ Actual position Set position 0_ Actual position
315_ 45_ 315_ 45_
/ N G1 G2 G3 X/t F M1 M2 M3 D
10 90 315 100
Option 1:
With G90, the axis autonomously always takes the shortest path to reach the
set position of 45_, going via 0_ to 315_.
Option 2:
The control signals (R+) or (R–) force the respective direction of the axis - in
this example 45_ via 180_ to 315_. (R+) or (R–) must already be pending when
positioning is activated (START).
Note
The direction (R+) or (R–) must be specified sufficiently in advance. A traversing
direction cannot be forced on a traversing block that is already active, or on the
traversing blocks (up to 4) that have already been calculated in advance in G64
operation.
Operation with option 1 or option 2 is at the user ’s discretion.
É É ÉÉ
É Tool zero
DVadd DV
DVabs
DL
Position X
Positions may be input with a negative or positive sign. The plus sign on positive
values may be omitted.
Speed F
The input speed is calculated against the override. If the speed value is numeri-
cally greater than the maximum allowed speed, it is limited to the magnitude of the
machine data item. Speeds are modal and need to be re-input only when changed.
M functions
Up to three M functions can be programmed in one traversing block, with any as-
signment of M1, M2 and M3. The output sequence of the M functions is always
M1³M2³M3 (for information about output see Section 9.1).
The following figure shows an example.
/ N G1 G2 G3 X/t F M1 M2 M3 D
M0, M2, M18 and M30 are always output at the end of the traversing movement.
M0, M2, M18 and M30 are mutually exclusive within a single block.
Subprogram call P, L
A block with a subprogram call (P is the “number of runs”, L is the “program num-
ber”) cannot contain any further information.
A maximum of 19 subroutines can be called up in one program. Nesting is not
possible.
Forward processing
As a rule, programs are processed by ascending block number.
Reverse processing
If programs are processed in reverse, the effects of commands must be taken into
account in the programming:
S Commands are modal (G90, G91, G60, G64, G30 – G39)
S Active tool offset (G43, G44, D0 – D20)
S Change of coordinate systems via G87, G88, G89.
For these reasons, a distinction can be made between forward processing and re-
verse processing, in terms of both geometry and block transition response.
Overview
This chapter describes the influence of certain commands on block transitions.
ÉÉÉÉÉ
ÉÉÉÉÉ
ÉÉÉÉÉ t
(“long block”)
ÉÉ
ÉÉ ÉÉ
ÉÉ
ÉÉ ÉÉ
ÉÉ
ÉÉÉÉ Ni Ni+1
t
(“short block”)
M
Target range
ÉÉÉÉÉÉ
ÉÉ ÉÉ
ÉÉ
ÉÉÉÉÉÉ t
/ N G1 G2 G3 X/t F M1 M2 M3 D
5 90 64 10 000 100 00
10 20 000
15 30 000 200 00
20 40 000 150 00
25 64 30 000 100 00
V
N5 N10 N15 N20 N25
3
4
1 2
To be able to approach a position correctly, the axis must calculate the point of de-
celeration. The relevant parameters for this calculation are the residual traversing
distance, the deceleration value and the current traversing speed.
The point of deceleration is also the earliest possible time for a block change.
V 1 V 2 V 3
t t t
M
M M
1 – Since the M output is completed at the point of deceleration, a block change takes
place on-the-fly.
2 – The M output is not yet complete at the point of deceleration. The axis begins to brake.
At the end of the M output, the axis returns to speed (transition on-the-fly from
deceleration ramp to acceleration ramp).
3 – Axis comes to a complete standstill and waits for the end of M output.
/ N G1 G2 G3 X/t F M1 M2 M3 D
5 90 10 000 100 00 10
10 20 000 20
15 30 000 30 40
20 60 40 000 97
V
N5 N10 N15 N20
1 2 3 4
X
10 000 20 000 30 000 40 000
M No.
10 20 30 40 97
Overview
The FM 353 provides diagnostics for the following:
S I/Os
S Module processes
This chapter “Troubleshooting” describes the different types of errors, their cause,
effect and elimination.
Error localization
The FM 353 distinguishes according to the following criteria:
S Errors which trigger a diagnostic interrupt in the CPU, and
S Errors which the module reports by way of checkback messages.
In the event of diagnostic interrupt, STATUS LEDs light up in addition.
CPU FM 353
Diag-
RAM nostic External
inter- channel
OB 82 rupt errors
call SFC 52
Diagn.
Write diagn. interrupt information “Binary” diagn.
buffer of External
the CPU POS_DIAG Callup in interrupt infor- errors
user pro- P Bus mation
gram
Other error mes- Internal
OB 1
sage errors
POS_CTRL SSL
. Other er-
. Diagn.
. backup rors, op-
User DB error his- erator
tory control
DB-SS
K Bus errors
MPI
OP
Overview
The FM 353 contains monitoring circuits which are active during startup or during
continuous operation. Errors occurring during those times are reported to the sys-
tem and to the user program.
The table below lists the error classes and their meaning.
Error response
Each error message triggers an appropriate response.
Error Significance
response
Everything S Stop movement by way of voltage ramp (MD44/MD45)
OFF S Disable digital outputs
S Deactivate controller enable
S SYN is cleared after the error has been acknowledged with Restart
S No new travel jobs possible
Feed STOP S Stop movement
S Travel job is canceled and terminated.
S No new travel jobs possible
Warning S Message only
S Movement and control of axes not affected
Introduction
The following approaches to error localization are available for the FM 353:
S Error display by LEDs
S Error messages to the system and to the user program
SF
DC 5V
DIAG
Overview
Internal errors, external errors and external channel errors are indicated to an inter-
rupt-capable system by means of diagnostic interrupts (see diagnostic interrupt
data in Tables 11-4, 11-5 and Section 6.3.4). This presupposes that the diagnostic
interrupt message was activated at the time of configuration (see Chapter 5). If the
system is not interrupt-capable, the diagnostic interrupt information must be read
out cyclically with POS_DIAG.
External channel errors Byte-.Bit-No. 0.2, 0.3 LED “SF” and “DIAG”
Group error byte 8
Diagnostic interrupt
Message to the CPU (precondition: interrupt message activated Message in the Entry in diag-
(see Section 5.2) “troubleshooting” nostic buffer
display of “Para-
No OB 82 OB 82 OB 1 meterize FM353”
exists ! CPU Menu: Test >
switches to Enters the Enters the Calls Troubleshooting
STOP diagnostic in- diagnostic in- POS_DIAG
formation in the formation in
diagnostic the user DB
buffer of the starting at ad-
CPU (4 bytes) dress 70 and
and calls SFC calls
52 POS_DIAG
Interrupt acknowledgement
If processing is to continue after a diagnostic interrupt, the diagnostic interrupt has
to be acknowledged with a restart (user DB, DBX37.5) when the error has been
remedied.
Internal errors cannot be acknowledged. External errors are self-acknowledging.
Overview
Operator/travel errors [BF/FS] and data errors/machine data errors/traversing pro-
gram errors [DF], are communicated to the user by way of checkback signals (call
of the POS_CTRL block) and operating errors by means of diagnostic interrupts
(see Section 6.3.4). The error-specification is stored in the form of an error number
(see error list in Table 11-6...11-8).
Error acknowledgement
Set/clear control signal [BFQ/FSQ]
or
on message [DF] ! write a new write job
Note
Invalid data are not accepted. The original data are retained.
Overview
Please note the following for direct access to DBs (e.g. using an OP).
If data errors/machine data errors/traversing program errors are detected when the
parameters are written to the data block (e.g. in the parameterization tool), an error
message is stored in the data block. The error-specification is stored in the form of
an error number in the corresponding data block (see error list in Table 11-8). The
error message occurs each time the data block is written to until the cause has
been eliminated.
It is recommended to scan the error message after every write operation.
Overview
The last five error messages are stored in the diagnostic buffer.
There are two ways of proceeding:
1. In the S7 SIMATIC Manager select the menu File > Open > Accessible
Nodes.
2. In the Accessible Nodes window, select the MPI address of your module.
3. You can view the diagnostic buffer in the menu Target system > Module
status
or
1. Open your project in the S7 SIMATIC Manager.
2. Select the menu View > Online.
3. In the dialog box, select the FM 353 and the associated program.
4. You can view the diagnostic buffer in the menu Target system > Module
status
Note
In the following tables, please note:
The module response described under “Effect” refers to the error-specific module
response. The error response described in Table 11-2 occurs in addition.
Overview
The diagnostic interrupts are listed according to error class in Tables 11-4, 11-5.
Overview
The errors are listed in Tables 11-6...11-8 according to error class.
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-8 General data errors, machine data errors, traversing program errors, continued
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
UL/CSA certifications
The following certifications are on record for the FM 353:
UL Recognition Mark
Underwriters Laboratories (UL) in compliance with
UL Standard 508, File E 164110
CSA Certification Mark
Canadian Standard Association (CSA) in compliance with
Standard C 22.2 No. 142
FM approval
The FM approval is on record for the FM 353:
FM certification in accordance with Factory Mutual Approval Standard Class Num-
ber 3611, Class I, Division 2, Group A, B, C, D.
Warning
! Potential for personal injury and property damage.
In areas where there is a risk of explosion, personal injury and property damage
may occur if you disconnect plugs while the S7-300 is in operation.
In areas where there is a risk of explosion, always cut off power to the S7-300 be-
fore disconnecting plugs.
Warning
! WARNING - NEVER DISCONNECT WHILE CIRCUIT IS LIVE
UNLESS LOCATION IS KNOWN TO BE NONHAZARDOUS
CE marking
Our products are in compliance with the EU Guideline 89/336/EEC “Electromag-
netic Compatibility” and the harmonized European standards (EN) which it embo-
dies.
The EC Declaration of Conformity in accordance with Article 10 of the EU Guide-
line referenced above can be found on the Internet at:
http://support.automation.siemens.com/WW/view/de/15257461
Application
SIMATIC products are designed for application in an industrial environment.
Connected load
Technical data: Connected load
FM cycle
2 ms
Drive port
Technical data on drive port:
Digital inputs
Technical data for digital inputs:
Digital outputs
Technical data for digital outputs:
Number of outputs 4
Supply voltage 24 V DC
(allowable range: 20.4 – 28.8 V)
Electrical isolation No
Output voltage S 0 signal: Residual current max. 2 mA
S 1 signal: (Power supply –3 V)
Output current on signal “1”
S at ambient temperature of
40_C
– Rated value 0.5 A (total current 2 A)
– Permissible value range 5 mA...0.6 A (over power supply range)
– Lamp load max. 5 W
S at ambient temperature of
60_C
– Rated value 0.1 A (total current 0.4 A)
– Permissible value range 5 mA...0.12 A (over power supply)
Output delay S 0 → 1 signal: type 300 μs
S 1 → 0 signal: type 300 μs
Short circuit Yes
Switching rate S Resistive load: max. 100 Hz
S Inductive load: max. 0.25 Hz
Adresse
Variable Data type Comment
absolut
General addresses
0 MOD_ADR INT Module address
2...13.5 Reserved
13.6 MODE_BUSY BOOL Execution started
13.7 POS_REACHED BOOL Position
Control signals
14.0 Reserved
14.1 TEST_EN BOOL Switch to P bus Start-up
14.2 Reserved
14.3 OT_ERR_A BOOL Acknowledge operator/traversing error
14.4...14.7 Reserved
15.0 START BOOL Start
15.1 STOP BOOL Stop
15.2 DIR_M BOOL Negative direction
15.3 DIR_P BOOL Positive direction
15.4 ACK_MF BOOL Acknowledge M function
15.5 READ_EN BOOL Read-in enable
15.6 SKIP_BLK BOOL Block skip
15.7 DRV_EN BOOL Drive enable
16 MODE_IN BYTE Operating mode
17 MODE_ TYPE BYTE Operating mode parameters
18 OVERRIDE BYTE Override
19...21 Reserved
Checkback signals
22.0 Reserved
22.1 TST_STAT BOOL Switch to P bus completed
22.2 Reserved
22.3 OT_ERR BOOL Operator/traversing error
Adresse
Variable Data type Comment
absolut
22.4 DATA_ERR BOOL Data error
22.5...22.6 Reserved
22.7 PARA BOOL Channel parameterizell
23.0 ST_ENBLD BOOL Start enable
23.1 WORKING BOOL Machining in progress
23.2 WAIT_EI BOOL Wait for external enable
23.3...23.4 Reserved
23.5 DT_RUN BOOL Dwell in progress
23.6 PR_BACK BOOL Reverse prog. scan
23.7 Reserved
24 MODE_OUT BYTE Active operating mode
25.0 SYNC BOOL Channel synchronized
25.1 MSR_DONE BOOL End of measurement
25.2 GO_M BOOL Negative travel
25.3 GO_P BOOL Positive travel
25.4 ST_SERVO BOOL Servo enable status
25.5 FVAL_DONE BOOL On-the-fly setting of actual value completed
25.6 Reserved
25.7 POS_RCD BOOL Position reached. Stop.
26 NUM_MF BYTE M function number
27.0...27.3 Reserved
27.4 STR_MF BOOL M function strobe signal
27.5...33 Reserved
28...31 ACT_POS DINT Actual position
32...33 Reserved
Initiation signals for single settings
34.0 SERVO_EN BOOL Controller enable
34.1 GAUG_FLY BOOL On-the-fly measuring
34.2...34.4 Reserved
34.5 TRAV_MON BOOL Rotation monitoring
34.6 PARK_AX BOOL Parking axis
34.7 SIM_ON BOOL Simulation on
35.0...35.1 Reserved
35.2 MSR_EN BOOL Length measurement
35.3 REF_TRIG BOOL Retrigger reference point
35.4 DI_OFF BOOL Enable input disabled
Adresse
Variable Data type Comment
absolut
35.5 Reserved
35.6 SSW_DIS BOOL Software limit positions disabled
35.7 Reserved
Initiation signals for single commands
36 Reserved
37.0 MD_EN BOOL Activate MD
37.1 DELDIST_EN BOOL Delete residual distance
37.2 SEARCH_F BOOL Automatic block advance
37.3 SEARCH_B BOOL Automatic block return
37.4 Reserved
37.5 RESET_AX BOOL Restart
37.6 AVALREM_EN BOOL Rescind setting of actual value
37.7 Reserved
Initiation signals for Write requests
38.0 VLEV_EN BOOL Speed levels 1, 2
38.1 CLEV_EN BOOL Frequency levels 1, 2
38.2 TRG254_EN BOOL Setpoint for incremental dimension
38.3 MDI_EN BOOL MDI block
38.4 MDIFLY_EN BOOL On-the-fly MDI block
38.5 Reserved
38.6 REFPT_EN BOOL Set reference point
38.7 AVAL_EN BOOL Set actual value
39.0 FVAL_EN BOOL On-the-fly setting of actual value
39.1 ZOFF_EN BOOL Zero offset
39.2 Reserved
39.3 PARCH_EN BOOL Modify parameters/data
39.4 DIGO_EN BOOL Digital outputs
39.5 PROGS_EN BOOL Program selection
39.6 REQAPP_EN BOOL Request application data
39.7 TEACHIN_EN BOOL Teach-in
40...41 Reserved
Initiation signals for Read requests
42.0 OPDAT_EN BOOL Basic operating data
42.1 ACT_BL_EN BOOL Active NC block
42.2 NXT_BL_EN BOOL Next NC block
42.3 BLEXT_EN BOOL Actual value block change
Adresse
Variable Data type Comment
absolut
42.4 SERVDAT_EN BOOL Service data
42.5 OC_ERR_EN BOOL Operating error no.
42.6...43.2 Reserved
43.3 PARRD_EN BOOL Parameter/data
43.4 DIGIO_EN BOOL Dig. inputs/outputs
43.5 OPDAT1_EN BOOL Additional operating data
43.6 APPDAT_EN BOOL Application data
43.7 MSRRD_EN BOOL Read measured values
Ready signals (for Initiation signals, single settings)
44.0 SERVO_D BOOL Controller enable
44.1 GAUG_FLY_D BOOL On-the-fly measuring
44.2...44.4 Reserved
44.5 TRAV_MON_D BOOL Rotation monitoring
44.6 PARK_AX_D BOOL Parking axis
44.7 SIM_ON_D BOOL Simulation on
45.0...45.1 Reserved
45.2 MSR_D BOOL Length measurement
45.3 REF_TRIG_D BOOL Retrigger reference point
45.4 DI_OFF_D BOOL Enable input disabled
45.5 Reserved
45.6 SSW_DIS_D BOOL Software limit positions disabled
45.7 Reserved
Ready signals (for Initiation signals, single commands)
46 Reserved
47.0 MD_D BOOL Activate MD
47.1 DELDIST_D BOOL Delete residual distance
47.2 SEARCH_F_D BOOL Automatic block advance
47.3 SEARCH_B_D BOOL Automatic block return
47.4 Reserved
47.5 RESET_AX_D BOOL Restart
47.6 AVALREM_D BOOL Rescind setting of actual value
47.7 Reserved
Ready signals (for Initiation signals for Write requests)
48.0 VLEV_D BOOL Speed levels 1, 2
48.1 CLEV_D BOOL Frequency levels 1, 2
48.2 TRG254_D BOOL Setpoint for incremental dimension
Adresse
Variable Data type Comment
absolut
48.3 MDI_D BOOL MDI block
48.4 MDIFLY_D BOOL On-the-fly MDI block
48.5 Reserved
48.6 REFPT_D BOOL Set reference point
48.7 AVAL_D BOOL Set actual value
49.0 FVAL_D BOOL On-the-fly setting of actual value
49.1 ZOFF_D BOOL Zero offset
49.2 Reserved
49.3 PARCH_D BOOL Modify parameters/data
49.4 DIGO_D BOOL Digital outputs
49.5 PROGS_D BOOL Program selection
49.6 REQAPP_D BOOL Request application data
49.7 TEACHIN_D BOOL Teach-in
50...51 Reserved
Ready signals (for Initiation signals for Read requests)
52.0 OPDAT_D BOOL Basic operating data
52.1 ACT_BL_D BOOL Active NC block
52.2 NXT_BL_D BOOL Next NC block
52.3 BLEXT_D BOOL Actual value block change
52.4 SERVDAT_D BOOL Service data
52.5 OC_ERR_D BOOL Operating error read
52.6 OT_ERR_D BOOL Operator/traversing error read
52.7 DA_ERR_D BOOL Data error read
53.0...53.2 Reserved
53.3 PARRD_D BOOL Parameter/data
53.4 DIGIO_D BOOL Dig. inputs/outputs
53.5 OPDAT1_D BOOL Additional operating data
53.6 APPDAT_D BOOL Application data
53.7 MSRRD_D BOOL Read measured values
Error signals (for Initiation signals, single settings)
54.0 SERVO_ERR BOOL Controller enable
54.1 GAUG_FLY_ERR BOOL On-the-fly measuring
54.2...54.4 Reserved
54.5 TRAV_MON_ERR BOOL Rotation monitoring
54.6 PARK_AX_ERR BOOL Parking axis
54.7 SIM_ON_ERR BOOL Simulation on
Adresse
Variable Data type Comment
absolut
55.0...55.1 Reserved
55.2 MSR_ERR BOOL Length measurement
55.3 REF_TRIG_ERR BOOL Retrigger reference point
55.4 DI_OFF_ERR BOOL Enable input disabled
55.5 Reserved
55.6 SSW_DIS_ERR BOOL Software limit positions disabled
55.7 Reserved
Error signals (for Initiation signals, single commands)
56 Reserved
57.0 MD_ERR BOOL Activate MD
57.1 DELDIST_ERR BOOL Delete residual distance
57.2 SEARCH_F_ERR BOOL Automatic block advance
57.3 SEARCH_B_ERR BOOL Automatic block return
57.4 Reserved
57.5 RESET_AX_ERR BOOL Restart
57.6 AVALREM_ERR BOOL Rescind setting of actual value
57.7 Reserved
Error signals (for Initiation signals for Write requests)
58.0 VLEV_ERR BOOL Speed levels 1, 2
58.1 CLEV_ERR BOOL Frequency levels 1, 2
58.2 TRG254_ERR BOOL Setpoint for incremental dimension
58.3 MDI_ERR BOOL MDI block
58.4 MDIFLY_ERR BOOL On-the-fly MDI block
58.5 Reserved
58.6 REFPT_ERR BOOL Set reference point
58.7 AVAL_ERR BOOL Set actual value
59.0 FVAL_ERR BOOL On-the-fly setting of actual value
59.1 ZOFF_ERR BOOL Zero offset
59.2 Reserved
59.3 PARCH_ERR BOOL Modify parameters/data
59.4 DIGO_ERR BOOL Digital outputs
59.5 PROGS_ERR BOOL Program selection
59.6 REQAPP_ERR BOOL Request application data
59.7 TEACHIN_ERR BOOL Teach-in
60...61 Reserved
Error signals (for Initiation signals for Read requests)
Adresse
Variable Data type Comment
absolut
62.0 OPDAT_ERR BOOL Basic operating data
62.1 ACT_BL_ERR BOOL Active NC block
62.2 NXT_BL_ERR BOOL Next NC block
62.3 BLEXT_ERR BOOL Actual value block change
62.4 SERVDAT_ERR BOOL Service data
62.5 OC_ERR_ERR BOOL Operating error read
62.6 OT_ERR_ERR BOOL Operator/traversing error read
62.7 DA_ERR_ERR BOOL Data error read
63.0...63.2 Reserved
63.3 PARRD_ERR BOOL Parameter/data
63.4 DIGIO_ERR BOOL Dig. inputs/outputs
63.5 OPDAT1_ERR BOOL Additional operating data
63.6 APPDAT_ERR BOOL Application data
63.7 MSRRD_ERR BOOL Read measured values
64...65 Reserved
Error messages/status signals from POS_CTRL
66 JOB_ERR INT Error code SFC 58/59 (POS_CTRL)
68.0 JOBBUSY_WR BOOL Write job active
68.1 IMPO_WR BOOL Write request not possible
68.2 JOBBUSY_RD BOOL Read job active
68.3 IMPO_RD BOOL Read request not possible
68.4...69.0 Reserved
69.1 JOBRESET BOOL Reset status/error
69.2...69.7 Reserved
Diagnostic interrupt data (POS_DIAG)
70.0 MDL_DEFECT BOOL Module/group errors (coming and going)
70.1 INT_FAULT BOOL Internal error/hardware error (group error DBB72,
73)
70.2 EXT_FAULT BOOL External error
70.3 PNT_INFO BOOL External channel error (group error bytes 78)
70.4...70.5 Reserved
70.6 NO_CONFIG BOOL Module not initialized
70.7 Reserved
71 MDL_TYPE BYTE Module type class for FM 453 = 08H / Channel in-
formation available
72.0 Reserved
Adresse
Variable Data type Comment
absolut
72.1 COMM_FAULT BOOL Communication error (K bus)
72.2 Reserved
72.3 WTCH_DOG_FLT BOOL Response from watchdog timer
72.4 INT_PS_FLT BOOL Internal supply voltage to the module failed (NMI)
72.5...73.1 Reserved
73.2 EPROM_FLT BOOL FEPROM error
73.3 RAM_FLT BOOL RAM error
73.4...73.5 Reserved
73.6 HW_INTR_FLT BOOL Process interrupt lost
73.7 Reserved
74 POS_ID BYTE FM pos. ID (74H)
75 LEN_INFO BYTE Length of the diagnostic information (16)
76 CHEN_NO BYTE Number of channels (1)
77.0 CH_ERR_VE1 BOOL Channel error vector
77.1...78.6 Reserved
78.7 OC_ERR_EN1 BOOL Operating error for channel
79..85 Reserved
86 OC_ERR_NO BYTE Error number (DS 164) – Detail event class
87 OC_REE_CL BYTE Error number (DS 164) – Detail event number
88...89 Reserved
90 OT_ERR_NO BYTE Error number (DS 162) – Detail event class
91 OT_ERR_CL BYTE Error number (DS 162) – Detail event number
92...93 Reserved
94 DA_ERR_NO BYTE Error number (DS163) – Detail event class
95 DA_ERR_CL BYTE Error number (DS163) – Detail event number
96 DIAG_ERR INT Error code for POS_DIAG (return code SFC 51)
98 MSRM_ERR INT Error code for POS_MSRM
(return code SFC 59/SFB42)
100 ARRAY Internal, Reserved
[100 ..139]
BYTE
Adresse
Variable Data type Comment
absolut
Data for the requests
140 ZOFF DINT Zero offset
144 AVAL DINT Set actual value
148 FVAL DINT On-the-fly setting of actual value
152 REFPT DINT Set reference point
156 TRG254 DWORD Setpoint for incremental dimension
160 VLEVEL_1 DWORD Speed level 1
164 VLEVEL_2 DWORD Speed level 2
168 CLEVEL_1 DWORD Frequency level 1
172 CLEVEL_2 DWORD Frequency level 2
MDI block
176 MDIB STRUCT MDI block
+ 0...+1 Reserved
+ 2.0 G_1_EN BOOL G function group 1
+ 2.1 G_2_EN BOOL G function group 2
+ 2.2...+ 2.3 Reserved
+ 2.4 X_T_EN BOOL Position/ dwell
+ 2.5...+ 2.7 Reserved
+ 3.0 V_EN BOOL Speed
+ 3.1 M_1_EN BOOL M function group 1
+ 3.2 M_2_EN BOOL M function group 2
+ 3.3 M_3_EN BOOL M function group 3
+ 3.4...+ 3.7 Reserved
+4 G_1_VAL BYTE G function no. of group 1
+5 G_2_VAL BYTE G function no. of group 2
+ 6...+ 7 Reserved
+8 X_T_VAL DINT Value for position/dwell
+ 12 V_VAL DINT Value for speed
+ 16 M_1_VAL BYTE M function no. of group 1
+ 17 M_2_VAL BYTE M function no. of group 2
+ 18 M_3_VAL BYTE M function no. of group 3
+ 19 Reserved
END_STRUCT
Modify parameter/data
196 PAR_CHAN STRUCT Modify parameter/data
+0 TYP BYTE DB type
Adresse
Variable Data type Comment
absolut
+1 NUMB BYTE Number
+2 COUN BYTE Quantity
+3 JOB BYTE Request
+4 DATA ARRAY Data array, structure/data type of Write data as per
[200 ..219] bytes 1 to 4 of this structure
BYTE
END_STRUCT
Digital inputs/outputs (for read and write)
220.0 D_IN0 BOOL Digital input 0
220.1 D_IN1 BOOL Digital input 1
220.2 D_IN2 BOOL Digital input 2
220.3 D_IN3 BOOL Digital input 3
220.4...7 Reserved
221.0 D_OUT0 BOOL Digital output 0
221.1 D_OUT1 BOOL Digital output 1
221.2 D_OUT2 BOOL Digital output 2
221.3 D_OUT3 BOOL Digital output 3
221.4...7 Reserved
On-the-fly MDI block
222 MDI_F STRUCT On-the-fly MDI block
+ 0...+ 1 Reserved
+ 2.0 G_1_EN BOOL G function group 1
+ 2.1 G_2_EN BOOL G function group 2
+ 2.2...+ 2.3 Reserved
+ 2.4 X_T_EN BOOL Position/dwell
+ 2.5...+ 2.7 Reserved
+ 3.0 V_EN BOOL Speed
+ 3.1 M_1_EN BOOL M function group 1
+ 3.2 M_2_EN BOOL M function group 2
+ 3.3 M_3_EN BOOL M function group 3
+ 3.4...+ 3.7 Reserved
+4 G_1_VAL BYTE G function no. of group 1
+5 G_2_VAL BYTE G function no. of group 2
+ 6...+ 7 Reserved
+8 X_T_VAL DINT Value for position/dwell
+ 12 V_VAL DINT Value for speed
Adresse
Variable Data type Comment
absolut
+ 16 M_1_VAL BYTE M function no. of group 1
+ 17 M_2_VAL BYTE M function no. of group 2
+ 18 M_3_VAL BYTE M function no. of group 3
+ 19 Reserved
END_STRUCT
Program selection
242 PROG_NO BYTE Program number
243 BLCK_NO BYTE Block number
244 PROG_DIR BYTE Direction of processing
245 Reserved
Request for application data
246 CODE_AP1 BYTE Application data 1
247 CODE_AP2 BYTE Application data 2
248 CODE_AP3 BYTE Application data 3
249 CODE_AP4 BYTE Application data 4
Teach-in
250 TEA_PROG_NO BYTE Program number
251 TEA_BLCK_NO BYTE Block number
252 FELD2_INTERN ARRAY Internal, Reserved
[252...309]
BYTE
Basic operating data
310 ACT_VAL DINT Actual position
314 SPEED DWORD Actual speed
318 REM_DIST DINT Residual distance
322 SET_POS DINT Setpoint position
326 SUM_OFST DINT Sum of active coordinate offset, tool offset, zero
offset
330 TRAV_SPE DWORD Rotational speed
334...338 Reserved
Active NC block
342 ACT_BL STRUCT Active NC block
+0 PROG_NO BYTE Program number
+1 BLCK_NO BYTE Block number
+ 2.0 G_1_EN BOOL G function group 1
+ 2.1 G_2_EN BOOL G function group 2
+ 2.2 G_3_EN BOOL G function group 3
Adresse
Variable Data type Comment
absolut
+ 2.3 Reserved
+ 2.4 X_T_EN BOOL Position/dwell
+ 2.5 SR_L_EN BOOL No. of UP calls
+ 2.6 SR_N_EN BOOL UP call
+ 2.7 SKIP_EN BOOL Block skip
+ 3.0 V_EN BOOL Speed
+ 3.1 M_1_EN BOOL M function group 1
+ 3.2 M_2_EN BOOL M function group 2
+ 3.3 M_3_EN BOOL M function group 3
+ 3.4 TO_EN BOOL Tool offset
+ 3.5...+ 3.7 Reserved
+4 G_1_VAL BYTE G function no. of group 1
+5 G_2_VAL BYTE G function no. of group 2
+6 G_3_VAL BYTE G function no. of group 3
+7 Reserved
+8 X_T_VAL DINT Value for position/dwell
+ 12 V_VAL DINT Value for speed
+ 16 M_1_VAL BYTE M function no. of group 1
+ 17 M_2_VAL BYTE M function no. of group 2
+ 18 M_3_VAL BYTE M function no. of group 3
+ 19 TO_VAL BYTE Tool offset no.
END_STRUCT
Next NC block
362 NXT_BL STRUCT Next NC block
+0 PROG_NO BYTE Program number
+1 BLCK_NO BYTE Block number
+ 2.0 G_1_EN BOOL G function group 1
+ 2.1 G_2_EN BOOL G function group 2
+ 2.2 G_3_EN BOOL G function group 3
+ 2.3 Reserved
+ 2.4 X_T_EN BOOL Position/dwell
+ 2.5 SR_L_EN BOOL No. of UP calls
+ 2.6 SR_N_EN BOOL UP call
+ 2.7 SKIP_EN BOOL Block skip
+ 3.0 V_EN BOOL Speed
+ 3.1 M_1_EN BOOL M function group 1
Adresse
Variable Data type Comment
absolut
+ 3.2 M_2_EN BOOL M function group 2
+ 3.3 M_3_EN BOOL M function group 3
+ 3.4 TO_EN BOOL Tool offset
+ 3.5...+ 3.7 Reserved
+4 G_1_VAL BYTE G function no. of group 1
+5 G_2_VAL BYTE G function no. of group 2
+6 G_3_VAL BYTE G function no. of group 3
+7 Reserved
+8 X_T_VAL DINT Value for position/dwel
+ 12 V_VAL DINT Value for speed
+ 16 M_1_VAL BYTE M function no. of group 1
+ 17 M_2_VAL BYTE M function no. of group 2
+ 18 M_3_VAL BYTE M function no. of group 3
+ 19 TO_VAL BYTE Tool offset no.
END_STRUCT
Application data
382 APP1 DINT Application data 1
386 APP2 DINT Application data 2
390 APP3 DINT Application data 3
394 APP4 DINT Application data 4
Actual value block change
398 BLCK_EXT DINT Actual value block change
Service data
402 OUT_VAL DINT frequency output value
406 ENC_VAL DINT pulse output counter
410...414 Reserved
418 FOLL_ERR DINT Difference between setpoint and actual position
422 Reserved
426 OSC_ERR DINT Setpoint overshoot value/switch adjustment
430 Reserved
Additional operating data
434 OVERRIDE1 BYTE Override
435 PROG_NO1 BYTE NC traversing program no.
436 BLCK_NO1 BYTE NC block no.
437 LOOP_NO1 BYTE UP call counter
438 G90_91 BYTE Active G90/91
Adresse
Variable Data type Comment
absolut
439 G60_64 BYTE Active G60/64
440 G43_44 BYTE Active G43/44
441 TO_NO BYTE Active D number
442.0 Reserved
442.1 LIM_SP BOOL Speed limit
442.2... Reserved
442.7
443.0 LIM_FR BOOL Start/stop frequency limited
443.1 LIM_FV BOOL Frequency value for acceleration limited
443.2 Reserved
443.3 LIM_FS BOOL Acceleration/deceleration value limited
443.4... Reserved
445
Parameter/data
446 PAR_RD STRUCT Parameter/data
+0 TYP BYTE DB type
+1 NUMB BYTE Number
+2 COUN BYTE Quantity
+3 JOB BYTE Request
+4 DATA1 ARRAY Array, structure/data type according to data, to be
[450 ..469] read as per bytes 1 to 4 of this structure
BYTE
END_STRUCT
Adresse
Variable Data type Comment
absolut
+ 0.5 BITC_5 BOOL Incremental dimension transferred
+ 0.6 BITC_6 BOOL Speed levels transferred
+ 0.7 BITC_7 BOOL Frequency levels transferred
+ 1.0 BITC_8 BOOL MDI block transferred on-the-fly
+ 1.1 BITC_9 BOOL Set actual value transferred
+ 1.2 BITC_10 BOOL Zero offset transferred
+ 1.3...+ 1.4 Reserved
+ 1.5 BITC_13 BOOL Diagnostic interrupt
+ 1.6 BITC_14 BOOL Data error
+ 1.7 BITC_15 BOOL Operator/traversing error
+2 MD_NO WORD MD number
+4 MD_VALUE DINT MD value
+8 INC_NO BYTE Incremental dimension number
+9 Reserved
+ 10 PICT_NO WORD Display number
+ 12 KEY_CODE WORD Keyboard code
+ 14...+15 Reserved
+ 16.0 BITA_0 BOOL Open-loop control mode
+ 16.1 BITA_1 BOOL Approach to reference point
+ 16.2 BITA_2 BOOL Incremental mode (relative)
+ 16.3 BITA_3 BOOL MDI
+ 16.4 BITA_4 BOOL Auto/single block mode
+ 16.5 BITA_5 BOOL Auto mode
+ 16.6 BITA_6 BOOL Jog mode
+ 16.7... Reserved
+17.5
+ 17.6 BITA_14 BOOL Acknowledge error
+ 17.7 BITA_15 BOOL Acknowledge diagnostic interrupt
END_STRUCT
FC Function
FEPROM Flash EPROM: Read/Write memory
FM Function module
HEX Hexadecimal
HMI Device for operating and monitoring of a process
I Input parameter
IM Interface module (SIMATIC S7)
I/Q Throughput parameter (initialization parameter)
LAD Ladder program
LED Light Emitting Diode
MDI Manual Data Input
MLFB Machine-readable order designation
MPI Multi Point Interface
MSR Measurement system raster
NMI Non-Maskable Interrupt
OB Organization block
OP Operator panel
PG Programming device
PLC Programmable controller
PS Power Supply (SIMATIC S7)
PWM Pulse width modulation
Q Output parameter
RFG Controller enable
RPS Reference point switch
S7-300 PLC of medium performance range
SDB System data block
SFC System Function Call (integrated fucntions)
SM Signal module (SIMATIC S7, e.g. input/output module)
SSI Synchronous Serial Interface
STEP 7 Programming device software for SIMATIC S7
STL Statement list
SZL System status list
TF Technology function
UP User program
J
F M
FM approval, A-2
M functions, 10-14
FM cycle, 9-53, 9-75, 9-76, 9-77, 9-78, A-3
machine data, 5-9
frequency generation, 9-69
activation, 7-13, 9-45
working range of frequency generator, 5-19
dependencies, 5-16
frequency levels, 9-18
input limits, 7-3
front connector, 1-7, 4-12
interdependencies, 7-3
connecting cables, 4-18
machine data list, 5-11
Wiring up the front connector, 4-18
MDI (Manual Data Input), 9-10, 9-27 POS_CTRL (FC 1) – data exchange, 6-12
measured values, 9-52 POS_DIAG (FC 2) – read diagnostic interrupt
inprocess measurement, 9-52 data, 6-22, 6-41
length measurement, 9-53 POS_INIT (FC 0) – Initialization, 6-10, 6-30
measurement, 9-52 POS_MSRM (FB 3) – read measured values,
mode parameter, 9-18 6-41
mode parameter , 9-15, 9-24 POS_MSRM (FC 3) – read measured values,
module replacement, 5-8 6-25
MPI connection, 1-4 position resolution, 9-63
positioning, 2-1, 7-20
assessment criteria, 7-21
N open–loop control, 2-2
status messages, 9-58
next NC-block, 9-56
process interrupts, 9-81
processing in progress, 9-7
Processing read and write requests, 6-12,
O 6-14, 6-30, 6-32
OP 07 menu tree, 8-5, 8-10 Processing Read requests, 6-18, 6-37
Open–loop control, 9-10 Processing Write requests, 6-17, 6-36
open–loop control, 2-2, 9-18 Program selection, block advance, 9-33
Operating control mode, 6-18, 6-37 program selection, 9-31
operating modes, 9-14 block return, 9-33
automatic, 9-31 Programming the technological functions, 6-1
automatic single block, 9-36 Communication between the CPU and the
incremental relative, 9-24 FM 353, 6-4
Jogging, 9-15 Fundamentals, 6-4
MDI, 9-27 Interface, user data blocks, 6-26, 6-42
open–loop control, 9-18 Sample applications, 6-57
reference point approach, 9-19 Structure of a user program, 6-5
operator control and monitoring, 8-1, 8-3 Symbolic programming, 6-27, 6-43
data blocks, 8-1 Testing the user program, 6-6
user data, 8-1 Writing the user program, 6-7
operator/travel errors, 11-3 Putting into operation, with the parameteriza-
optimization (machine axis), 7-21 tion tool, 6-8
dynamic response, 7-21
Optimized motion profile, 7-28
Override, 9-4 R
override
read data
acceleration-override, 10-11
active NC-block, 9-56
time-override, 9-5
actual value-block change, 9-57
velocity-override, 9-4
additional operating data, 9-58
application data, 9-57
basic operating data, 9-55
P next NC-block, 9-56
parameterization, 5-1, 5-25 parameters/data, 9-58
parameters/data, 9-58 servicing data, 9-57
parking axis, 9-44 read–in enable, 9-3
ports reference point, 9-64
drive -port, 1-8 Reference point approach, 9-10
drive-port, 1-7 reference point approach, 9-19
I/O port, 1-7, 1-8 reducing velocity, 7-24
SIMATIC bus connector-port, 1-7, 1-8 referencing velocity, 7-24
POS_CTRL (FB 1) – data exchange, 6-30 reference point coordinates, 7-24, 7-26