Response Telegram - Pepperl+Fuchs SmartRunner Detector Manual

SmartRunner Detector
Operation
5.1.2

Response Telegram

The response telegram may contain 6 to 9 bytes, depending on the content. The first byte
contains the address of the responding reader and status information. The X position of the
reader is transmitted in bytes 2 to 5, starting with the MSB. Depending on the controller
request, information such as speed and the Y position is transmitted in the subsequent bytes.
These bytes are omitted if a corresponding request is not sent. The last byte is used to detect
faults during the data transfer.
Status (is alive)
The status always returns 0x55 if the sensor is ready for operation.
Byte
1
Result Data
Result Data provides the measurement status and result as a response.
Byte
Byte 1 -
Status
Byte 2 -
Result
Byte 3 -
Counter
Byte 4 -
Checksum
Legend
Status
Result
Counter
Software Trigger
After sending the sequence for the software trigger, the sensor triggers an image capture. No
response telegram is generated to the command.
Teach-In
After sending the sequence for the teach-in, the sensor begins the teach-in routine. No
response telegram is generated to the command.
8 7 6
PAR R/W R.4
Parity 0 1
Bit 8 Bit 7 Bit 6
Parity 0 -
Parity 0 0
Parity 0 C06
Parity 0 xor
Addr Device address
Event Event occurred, currently read as 0
WRN Unused
No Pos. Is always read as 0
ERR System error or evaluation error
R0 Faulty background line
R1 Object detected
R3 Unused
R4 Unused
R5 Unused
Increments for each evaluation, is restarted at 0x3F
5 4 3
R.3 R.2 R.1
0 1 0
Bit 5 Bit 4 Bit 3
Addr 1 Addr 0 Event
R5 R4 R3
C05 C04 C03
xor xor xor
2 1 0
R.0 A.1 A.0
1 0 1
Bit 2 Bit 1 Bit 0
WRN No Pos. ERR
R2 R1 R0
C02 C01 C00
xor xor xor
25