MOBY Commands
4-27
FC 56
J31069-D0155-U001-A0-7618
4.2.14
GET
Parameterizing the command in Command_DB
Table 4-22
UDT 50 “MOBY FH CMD” – GET
Address
Name
Starting
Value
Commentary
0.0
+0.0
UID
DW#16#0
Not used
+4.0
command
’P’
Command: P = GET. Fetch UIDs of all MDSs
located in the field.
+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 status data 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 GET command
The user data contained in the acknowledgment of the GET command are written
to the address parameterized in the command. The acknowledgment data are
stored in the structure shown below.
Table 4-23
UDT 200 “MOBY UID4”
Address
Name
Type
Commentary
0.0
STRUCT
+0.0
Reserved
BYTE
+1.0
Number_MDS
BYTE
Number of MDSs located in the field. This is
also the number of valid UID entries in the
ARRAY which follows.
+2.0
UID
ARRAY [1..12]
MDS number (unique identifier)
*4.0
DWORD
=50.0
END_STRUCT
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 ...