071652-01-8/99Subject to technical modificationspage 2 / 23
EUCHNERIdentsystemCIS3
1. Overview
This Manual describes on the whole the communication between PLC resp. CNC control and
the CIT3SX... read/write head.
The Protocol R transfer procedure serves to connect the CIT3SX1 read/write head to
PLC or NC controls.
The transfer telegrams for the commands
- Program (write) data carrier
- Read data carrier
are based on the 3964-R transfer procedure /1/
1.1. Cable- and terminal assignment
1.1.1 Read-Only Head CIT3PL...
Figure 1: Wiring diagram of the read-only head CIT3PL...
071652-01-8/99Subject to technical modificationspage 3 / 23
EUCHNERIdentsystemCIS3
K
4
3
2
1
1.1.2 Read/Write Head CIT3SX...
Figure 2: Terminal assignment read/write head CIT3SX1R1G05...
( basic unit with terminal cover open )
1.2 Connection example for read/write head CIT3SX...
24V
GND
PC oder SPS
9-pin
lemme
TxD
GND
RxD
24V
2 Receive Data
3 Transmit Data
4 Data Term Ready
5 Signal Ground
7 Request to Send
8 Clear to Send
6 Data Set Ready
Figure 3
2. Notes on installation
• Do not connect the read/write head CIT3SX... as well as the read-only head CIT3PL... if it
is still connected to the electrical power supply.
• The Read-Only head CIT3PL... should be mounted isolated, to avoid any interference’s
• When mounting the facilities make sure that the travel direction is in accordance with the
arrow direction on the active area of the reading head.
25-pin
3
2
20
7
4
5
6
071652-01-8/99Subject to technical modificationspage 4 / 23
EUCHNERIdentsystemCIS3
3. Pulse Timing Diagram for the Read-Only Head CIT3PL...
The above pulse timing diagram shows the time response of the input and output signals of
the read-only head with respect to the PLC.
As soon as a data carrier is read in, the first digit is disposed at the data outputs of the readonly head. To switch the following digits to the data outputs, you have to give a HIGH-pulse
to the Skip-input.
With every HIGH-pulse to the Skip-input, the digits are switched on.
The read-only head stores the coded information read from one data carrier until another
data carrier has been read.
The storage function offers the following advantage:
At high relative speeds between Read head and data carrier, the dwell time of a data carrier
in the read-only head’s response range may, under certain circumstances, be shorter than
the scan time of the PLC control. Owing to the storage characteristics of the Read head, the
code can nevertheless be read by the PLC in the next scan time cycle.
The additional STROBE output, when at HIGH level, indicates that a data carrier is located in
the read head’s response range.
This output is set to HIGH as soon as the Read head has been able to read 4 decimal digits.
If more than 4 digits are required, it is not possible to check with the STROBE output
whether all required digits have been read in.
If any error should occur during reading, an error message F
is given at the point in the
hex
data string. All preceding data is valid.
071652-01-8/99Subject to technical modificationspage 5 / 23
EUCHNERIdentsystemCIS3
p
4. Basic telegram structure without response telegram
Each command and any related data blocks are transferred within the telegram frame in
accordance with Procedure 3964-R from and to the read/write head (Figure 4).
With Protocol 3964-R, the relevant receiver acknowledges the received telegram by
returning an acknowledgement character (DLE). In the case of negative acknowledgement
(NAK), the entire protocol is repeated. If it is not possible to transfer the protocol error-free
after a total of six attempts, the operation is aborted.
4.1 Basic command structure
Connection set-u
Telegram data
max. 128 Bytes
(telegram core)
Connection
cleardown
Figure 4 : Basic command structure
DescriptionByte No. C O N T E N T S
ASCII
3964-R procedure start
STX
Number of telegram Bytes0
Command
identification
Header address *)301h
User data description4
User data 7
3964-R Procedure
end
5
6
to n
1
2
T or R
command
Start address
Start address
Number of data
items
DLE
ETX
BCC
Acknowledgement
of the receiver
+ -
DLE NAK
DLE NAK
*) For downward compatibility with the CIS2 identification system.
The content of the header address must always be 1 in the case
of CIS3.
071652-01-8/99Subject to technical modificationspage 6 / 23
EUCHNERIdentsystemCIS3
4.2 Special features of the 3964-R data transfer protocol /1/
The 3964-R data transfer protocol is a comparatively reliable program for electronic data
interchange between a control and a connected peripheral since data transfer is handled with
a standardised protocol.
On controls with integrated 3964-R driver (see /1/ for instance), it is not necessary for the
user to bother with the details of connection set-up and cleardown resp. data integrity.
It suffices to transfer the telegram core to the 3964-R driver via the program.
On controls without 3964-R driver or if a read/write head is connected to PC’s, the user must,
however, also program the connection set-up and cleardown and the retry attempts.
4.2.1 Basic information on data transfer procedures with protocol /1/
Numerous conventions must be agreed for a data transfer procedure: codes, operating
modes, transfer speeds and the algorithmic transfer sequence. The stipulation of the
algorithmic sequence is referred to as transfer protocol (protocol for short). A transfer
protocol generally defines the following phases of data transfer:
• Request from A to B for data interchange
• Data interchange
• End of data interchange
The transfer protocol is essentially a matter of the control. This means that it handles data
transfer independently on the basis of this protocol.
4.2.2 The 3964-R transfer protocol /1/
Unlike non-protocol-based data transfer procedures, 3964-R is a data transfer procedure
with protocol. This means that the actual data to be transferred is enclosed in specific control
characters. The 3964-R driver allows comparatively reliable data transfer by virtue of the fact
that the receiver must first signal to the transmitter that it is ready to receive (connection
set-up) and, after data interchange, must acknowledge correct reception. Data integrity is
enhanced by an additional block check character with the 3964-R transfer protocol.
The 3964-R driver interprets the following control characters:
• DLE (10
• STX (02
• NAK (15
• ETX (03
) Data Link Escape
hex
) Start of Text
hex
) Negative Acknowledgement
hex
) End of Text
hex
With the 3964-R transfer protocol, a block check character (BCC for short) is transmitted
for data integrity at the end of each data block. The block check character BCC is the evenlongitudinal parity (EXORing of all data Bytes) of a transmitted or received block.
Generation starts with the first user data Byte (first Byte of the telegram) after connection
set-up and ends after characters DLE and ETX on connection cleardown.
071652-01-8/99Subject to technical modificationspage 7 / 23
Loading...
+ 16 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.