Table of Contents
Advertisement
Description of Functions
MDI block on-the-fly
The MDI block currently being processed is canceled when the user program out-
puts an "MDI block on-the-fly" (user DB, DBX38.4).
Transfer of "MDI block on-the-fly" interrupts the active "MDI block". The new block
is executed immediately without "Start".
The MDI block on-the-fly is not saved in the FM 353.
With software version 3.6 of the FM 353 and higher, the error "Data cannot be
accepted at the time of transfer" (Class 4/No.1) is signaled when "MDI block flying"
is provided and [BL] has already been reset or [PEH] =1.
Block structure
The following table shows the block structure of the MDI block.
X/t
G1 − G2
M1 − M3
F
Example
0
0
Bits 0, 1, 4 set
Bit 0 set
90
30
0
0
100,000
5,000
0
0
0
0
1) Traversing block with absolute dimensions (G90), an end position of 100,000 DSG as
per MD7, and a speed of 5,000 DSG/min.
Note:
When the assignment bit (byte 2 and byte 3) is not set, the associated values must
be deleted.
9-28
Position/dwell time programmed (fills in value 1)
G function group 1 − 2
M function group 1 − 3
Speed programmed (fills in value 2)
1)
Byte
Data format
0
1
2
3
4
5
6
7
8
12
16
17
18
19
7
6
5
Byte
Byte
8 x bits
0
0
0
8 x bits
0
0
0
Byte
Byte
Byte
Byte
DINT
32-Bit-value 1
DINT
32-Bit-value 2
Byte
Byte
Byte
Byte
FM 353 Stepper Drive Positioning Module
Bit
4
3
2
1
0
0
0
X/t
0
0
G2 G1
0
M3 M2 M1
F
G function 1
G function 2
0
0
M function 1
M function 2
M function 3
0
6ES7 353-1AH01-8BG0
Hide quick links:
Advertisement
Table of Contents
