310/641 Bosch Rexroth AG | Tightening Technology 3 608 878 300
System 350 | 3 608 878 300/2019-03
6.4.8 Send range extension (multitelegram)
When systems feature many spindles, the output range on the field bus may be too small for the results.
To allow the use of process data and to prevent using multiple KEs, the send range can be configured
according to customer requirements. To achieve this, a "virtual" send buffer can be created. This send
buffer provides all of the setting functions that have been known so far but may have a size considerably
exceeding that of the input/output area.
If the volume of process data exceeds the available input/output area, use is made of a handshake
procedure. To this end, a six-byte header is defined in the send/receipt range. This allows subdividing the
send buffer into multiple blocks and transmitting each block as a telegram. The blank receipt range
following the header can be used for the ID code as usual.
The header itself is in turn subdivided into three segments each of which has a length of two bytes.
Command
KE350 input The first input word (after the PLC input/output signals) on the KE350 is used as command (control
word). A command requests the KE350 to carry out a task.
There are the following commands:
KE350 output The first output word of the KE350 is used as command (status word). The KE350 writes information
showing the result of the command given.
There are the following commands:
The send range extension is supported from version V2.300 of the Rexroth Tightening System 350.
Table 6–57: Allocation of the header
Byte PLC to KE350 (KE receipt range) KE350 to PLC (KE send range)
0 Command (high byte control word) Command (high byte status word)
1 Command (low byte control word) Command (low byte status word)
2 Not used Telegram number (most significant byte)
Not used Telegram number (least significant byte)
Not used Telegram length (most significant byte)
Not used Telegram length (least significant byte)
Table 6–58: Commands for communication from PLC to tightening controller
Command Telegram number Number Meaning
0x0000 0x0000 0x0000 Telegram read
0x1100 0x0000 0x0000 Request telegram
0xFFFF 0x0000 0x0000 Abort current transmission
Table 6–59: Response of tightening controller to PLC
Command Telegram number Length Meaning
0x1100 0x<nnnn> 0x<dddd> <nnnn>: Telegram number
<dddd>: Telegram length in bytes without header
0xFFFF Not used Confirmation, abort current transmission
0xEEEE Not used Transmission cancel by KE
0x0000 Not used Confirmation telegram read