Description
2.3 Data structures of FC 45
FC 45
2-6
Function manual, Release 03/2006 , J31069-D0167-U001-A2-7618
2.3
2.3
Data structures of FC 45
The following figure shows an example of a definition of several MOBY channels with the
related MDS commands and the user data.
&DOOUHDGHU
&DOOUHDGHU
&DOOUHDGHU
&DOOUHDGHU
&KDQQHO
&KDQQHO
&KDQQHO
&KDQQHO
02%<BFRPPDQGV
6LQJOHFRPPDQGXSWR
.%FDQEH
SURFHVVHGRUFKDLQHG
FRPPDQG
8VHUBGDWD
7KHXVHU
GHILQHVWKH
VL]HDQG
GDWDW\SHV
LQKLVRZQ
GDWD
FRPPDQGB
'%BQXPEHU
FRPPDQGB
'%BDGGUHVV
'$7B'%BQXPEHU
'$7B'%BDGGUHVV
02%<B'%
8'7
8'7
3DUDPVB'%
3DUDPVB$''5
3DUDPVB'%
3DUDPVB$''5
3DUDPVB'%
3DUDPVB$''5
3DUDPVB'%
3DUDPVB$''5
&DOO)&
&DOO)&
&DOO)&
&DOO)&
Figure 2-2
Configuration scheme of FC 45
Each FC 45 call points to a separate parameter data block (Params_DB, Params_ADDR),
which is defined by a UDT 10. The variables "command_DB_number" and
"command_DB_address" are stored in the UDT 10. These variables point to the MOBY
command which is to be executed with the MDS.
UDT 20 is used to define the MOBY command. Different commands can be defined by
calling UDT 20 several times (see Section "Command chaining"). The variables
"DAT_DB_number" and "DAT_DB_address" are defined in the UDT 20. This variable
definition generates the pointer to the user data. MDS data are stored there when they are
read out. When using a write command, the user must store his data before executing the
command.