MOBY Commands
4-31
FC 56
J31069-D0155-U001-A0-7618
4.2.18
MOVE
Parameterizing the command in Command_DB
Table 4-27
UDT 50 “MOBY FH CMD” – MOVE
Address
Name
Starting
Value
Commentary
0.0
+0.0
UID
DW#16#0
Not used
+4.0
command
’M’
MDS command: M = MOVE
+5.0
sub_command_1
B#16#0
Not used
+6.0
sub_command_2
B#16#0
Not used
+7.0
sub_command_3
B#16#0
Not used
+8.0
Filename
’xxxxxxxx’
Not used
+16.0
length
L#1
Not used
+20.0
address_MDS
W#16#0
Not used
+22.0
DAT_DB_number
48
Data DB. The data of the MOVE command are
written to this DB.
+24.0
DAT_DB_address
0
Address of the beginning of the user data in
the data DB
+26.0
QUEUE_DB_number
48
Not used
+28.0
QUEUE_DB_address
0
Not used
=30.0
Acknowledgment data in the MOVE command
Starting with address DAT_DB_address, data block DAT_DB_number contains the
requested data. The length of the data generated by the MOVE command
depends on the formatting of the MDS and is returned in the “length” parameter in
UDT 50. The “length” parameter returned here must be used again as the
parameter for a later LOAD command.
The maximum expected data length occurs with a 32-kB MDS (i.e., 1335 bytes).
Attention
The delivered data may not be changed by the user after the MOVE command is
executed. The resulting data of the MOVE command are transferred back to the
SLG, as necessary, with the LOAD command.
Summary of Contents for MOBY FC 56
Page 12: ...Introduction 1 6 FC 56 J31069 D0155 U001 A0 7618 ...
Page 63: ...5 1 FC 56 J31069 D0155 U001 A0 7618 Sample Applications 5 ...
Page 80: ...Sample Applications 5 18 FC 56 J31069 D0155 U001 A0 7618 ...
Page 90: ...Entry Exit Check of an MDS in an SLG Field 6 10 FC 56 J31069 D0155 U001 A0 7618 ...
Page 94: ...System Configuration 7 4 FC 56 J31069 D0155 U001 A0 7618 ...
Page 100: ...Commissioning Guidelines 8 6 FC 56 J31069 D0155 U001 A0 7618 ...
Page 101: ...9 1 FC 56 J31069 D0155 U001 A0 7618 Error Messages and Trouble Shooting 9 ...
Page 152: ...Programming MOBY ASM on PROFIBUS DP V1 B 30 FC 56 J31069 D0155 U001 A0 7618 ...