007 Protocol; Protocol Sequence - Balluff BIS U-6127-081-1 4-06-ST36 Betriebsanleitung

BIS U-6127-081-1_4-06-ST36
Processor unit
8

007 protocol

For communication of the processor unit with the
controlling system, the Balluff 007 protocol can be
selected, which is transmitted via an Ethernet TCP/IP
connection. The protocol is byte-oriented and uses little
overhead, since complete, error-free and sequence-correct
data transmission is ensured by the Ethernet transmission
channel.
The procedure for creating or opening a TCP/IP
socket connection depends on the system used
(PC, controller, etc.) and the programming
language used (for guidance, see chapter 7, for
details, see the documentation of the controlling
system or the selected programming language).
8.1

Protocol sequence

The protocol is based on synchronous commands, which
are structured according to the Request – Response
principle. Accordingly, the controller receives a
corresponding response to each correct request, which
may contain data or a status message. The sequence as
described in this chapter must be followed. Inputs that
deviate from this are ignored or not acknowledged by the
processor unit. After a command has been completely
processed or aborted, the processor unit automatically
returns to the basic status.
The only exception, which deviates from the
Request – Response principle used, is the asyn-
chronous message Tag comes or Tag goes,
which is sent to the controller without a previous
request. This function must be activated via the
parameter AsyncOperation (see AsyncOpera-
tion in chapter 7.3 on page 55).
Single-stage commands are executed according to the
principle B – R
aSic State equeSt
Application
Command
Data/Status
Fig. 8-1: Single-stage commands
www.balluff.com
– R – B :
eSponSe aSic State
Processor unit
Ground
state
Ground
state
Multi-stage commands are executed according to the
principle B
– R
aSic State equeSt
a /d – R
cknowledgment ata eSponSe
Application
Command
Status
Acknowledgment/Data
Status
Acknowledgment/Data
Status
Fig. 8-2: Multi-stage commands
Multi-stage commands can be aborted by the controller
using the Abort command (command identifier 'Q') after
each response received. The processor unit then returns to
the basic state and waits for an input.
– R –
eSponSe
– ... – B :
aSic State
Processor unit
Ground
state
Ground
state
english 89