![ESD CAN-CBM-DP Скачать руководство пользователя страница 33](http://html.mh-extra.com/html/esd/can-cbm-dp/can-cbm-dp_software-manual_2426392033.webp)
Configuration via SIMATIC Manager
CAN-CBM-DP
Software Manual Rev. 2.0
29
5.2 Description of Input Window ‘
Properties - DP Slave
’
- In field
I/O-Type
‘input’ or ‘output’ has to be selected, depending on the data direction desired.
Other properties are not permissible.
- In field
Address
the PLC-I/O address is entered as a
decimal value
.
- By means of fields
Length
and
Unit
the number of data bytes is specified.
- The entry in field
Consistent for
shows whether the data is to be transmitted as individual unit
(bytes, words, etc.) or as complete package (1-8 bytes or 16 bytes in Communication Window)
during a PLC cycle. This function is only to be set to ‘whole length’ if required, because the
transmission as ‘unit’ is faster.
Note:
If the data is to be transmitted consistently for the entire length, you have to specify this here
and
you have to use SFC14 and SFC15 (refer to Step7-PLC Manual).
- In field
Comment
the CAN identifier and then the control byte
form
, each divided by commas, are
transmitted in the first two bytes. The data format for all properties is
hexadecimal
(!).
Note:
The CAN-CBM-DP-module with the order no. C.2844.05 can handle 29-Bit-CAN-identifiers.
A 29-bit identifier requires
four
bytes and bit 29 must be set to ‘1’ (counted 0...31 bits), in order
to enable the module to distinguish between 11-bit and 29-bit identifiers.
If ‘input’ has been selected in the
I/O-Type
field, the CAN identifier entered there is regarded as
an Rx-identifier by the PLC. If ‘output’ has been selected in the
I/O-Type
, the CAN identifier
entered here is a Tx-identifier.
Attention:
No Rx-identifier must be assigned twice!
Example: If the
same
Rx-identifier has unpermissibly been selected on PLC-address 50 and
address 51, no new Rx-data would be received on address 50 after the Rx-identifier has
been assigned. The data received last remained unchanged.
This Rx-identifier rule is also valid for the Rx-identifier activated via the Communication Window.
The control byte
form
is used to convert the user data from Motorola format (high byte first) into
Intel format (low byte first).