Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Serial busy protocols<br />
In these protocols, the printer uses DTR (pin 20) and REV-CH (pin<br />
11) to signal to the computer when it is able to accept data. These<br />
pins go on when the printer is ready to accept data. In the l-byte<br />
mode, they go off after each character is received. In the l-block<br />
mode, they go off only as the printer buffer approaches capacity.<br />
In both cases, they stay off if the buffer is too full to accept more data.<br />
XONIXOFF protocol<br />
This protocol uses the ASCII characters DC1 and DC3 (sometimes<br />
called XON and XOFF, respectively) to communicate with the corn- -<br />
puter. When the printer buffer approachescapacity, the printer sends<br />
a DC3 on TXD (pin 2) to tell the computer that it must stop sending --<br />
data. When the printer is able to receive more data, it sends a DC1<br />
on the TXD pin. The computer can then send more data until the - --<br />
printer sends another DC3.<br />
ACK protocol<br />
-<br />
In the ACK protocol, the printer sends an ACK (ASCII 6) signal on<br />
the TXD pin each time it is prepared to receive a byte of data.<br />
• THE IEEE-488 INTERFACE<br />
You may also use the IEEE-488 interface to connect printer to your<br />
computer. This 8-bit parallel interface uses a TTL-compatible logic<br />
level, and is capable of transferring characters at rates of up to 1<br />
megabyte per second. Its transfer system is governed by a three-wire<br />
handshaking protocol, illustrated in Figure H-4.<br />
NRFD<br />
(LIstenerI<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
Data Walt<br />
------DataProcessing<br />
Data Invalid<br />
-<br />
DAV<br />
(Talker)<br />
I<br />
I<br />
--- --_- ------Data”a,,,,<br />
I<br />
NDAC<br />
lLlrtenerl<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I<br />
I !<br />
-------- DataReceptionComplete<br />
Data not yet recewed or<br />
currenfly bemg received<br />
Figure H-4. Data transfer timing chart for the IEEE-488 interface.<br />
_<br />
134