10-94
Handling, Diagnostic and Service Functions
MPH-02, MPB-02, MPD-02
DOK-INDRV*-MP*-02VRS**-FK01-EN-P
Structure of the Useful Data Header
Note:
The structure of the useful data header depends on the
direction of transmission. The useful data headers described
below are only valid for the services 0x80 … 0x8F.
In the structure of the useful data header we distinguish between
command telegram and reaction telegram.
Command Telegram
The command telegram is the telegram the master (drive) sends to the
slave (master
→
slave).
tel. header
control
byte
device
address
param.
type
parameter no.
useful data header
useful data
1byte
1byte
1byte
1byte
1byte
Ta0001f1.fh7
Fig. 10-55: Structure of the useful data header in the command telegram
In the command telegram the useful data header describes the kind of
request.
The control byte indicates the parameter element (data, name, ...) that is
to be read or written. In addition, the control byte indicates whether other
telegrams (sequential telegrams) are required for reading or writing.
In this byte the device address set at the address switches has to be
entered.
The parameter number has the format defined in the specification for
SERCOS interface. In order to be able to address control parameters, a
byte for characterizing the parameter type precedes the address.
bit 0:
reserved
bit 2:
reserved
bits 3-5: element
000: channel not active
001: IDN
010: name
011: attribute
100: unit
101: min. input value
110: max. input value
111: operating data
bit 1:
reserved
bit 6:
reserved
bit 7:
reserved
Fig. 10-56:
Structure of the control byte
Significance of the Useful Data
Header
Control Byte
Device Address
Parameter Type and Number
Courtesy
of
CMA/Flodyne/Hydradyne
▪
Motion
Control
▪
Hydraulic
▪
Pneumatic
▪
Electrical
▪
Mechanical
▪
(800)
426-5480
▪
www.cmafh.com
