Page Mode
CAN-CBM-DP
Software Manual Rev. 2.0
57
READ_CONFIG_DB
Data block for defining the Rx-identifiers.
(DB95)
In the PLC-source code included in the product package, the
READ-
CONFIG-DB
has been realized as data block DB95.
In
READ-CONFIG-DB
6 bytes are required for each Rx-identifier to be
written:
Address
Bytes 0...3
Byte 4
Byte 5
Explanation
0
Rx-Identifier 1
form 1
length 1
definition of Rx-Id 1
6
Rx-Identifier 2
form 2
length 2
definition of Rx-Id 2
12
Rx-Identifier 3
form 3
length 3
definition of Rx-Id 3
:
:
:
:
:
n
6
endconfig
-
-
marking the end of the
DB or the Rx-
configuration
Table 6.5.3:
Structure of the
READ-CONFIG-DB
Rx-Identifier x
Here the value of the Rx-identifier has to be specified.
CAN-CBM-DP order-no. C.2844.03: 0 ... 2047
CAN-CBM-DP order-no. C.2844.05: 0 ... 536870911
form x
In parameter
form
you choose, whether the input data is to
be converted from Intel format of the CAN network to the
Motorola format of the PLC or not. Byte
form
has already
been described in detail on page 29.
length x
This byte specifies the number of data bytes which are to
be received by this Rx-identifier.
endconfig
The PLC has to be told whether another data block is
required for the definition of the Rx-identifiers and when
the Rx-definition will be finished.
- If another data block is required, the hexadecimal value
‘DDDDDDDD’ has to be specified as last Rx-identifier
definition. FB2 will then continue with the handling of
the following DB.
- If the last Rx-identifier has been defined, this is
indicated to the FB2 by specifying the hexadecimal
value ‘EEEEEEEE’. FB2 will then continue with the
transmission of user data.
The length of the data blocks differs. The required length can be
determined from the number of Rx-identifiers required plus the four bytes
for the end flag.
