EUCHNER CIS3(A) - Manual (Page 11)

EUCHNER Identsystem CIS3
071652-01-8/99 Subject to technical modifications page 11 / 23
Byte
No. Description
ASCII
C O N T E N T S
HEX
Decimal
0 Number of telegram Bytes 7
1
2 Command
identification R
F 52
46 82
70
3 Read/write head address * 01 01
4
5 Padding data 00
00 00
00
6 Error number Error No. **
Figure 6: Response telegram "Write data carrier" (telegram core)
*) For downward compatibility with the CIS2 identification system.
The content of the header address must always be 1 in the case of CIS3.
**) Error number f = 00: No error
02: Data carrier not in active area
03: Read operation aborted
05: Write operation aborted, move data carrier
out of active area
5.2 Read operation
Command telegram (telegram core, PLC → CIT3SX , see also Figure 7):
TL (read/write head address) (start address) (number of Bytes user data)
Response telegram (telegram core, CIT3SX → PLC, see also Figure 8 or Figure 9):
There are two different possible responses for this command
1. RL (read/write head address) (start address) (number of Bytes user data) (user data)
or
2. RF (read/write head address) (0.0)(error No.)
The response telegram RL (see also Figure 8) means error-free reception of the data.
If it is not possible to read a data carrier, an RF response telegram is received
(see also Figure 9). The error number then indicates the cause of the error.
Content or possible value range
Byte
No. Description
ASCII
C O N T E N T S
HEX
Decimal
0 Number of telegram Bytes 7
1
2 Command
identification T
L 54
4C 84
76
3 Read/write head address *) 01 01
4
5 Start address of
user data 00
0 ... Fh 00
0 ... 15
6
Number of Bytes of
user data
1 ... 10h 1 ... 16
Figure 7: Command telegram "Read data carrier" (telegram core)