![LI-COR li-6262 Instruction Manual Download Page 87](http://html.mh-extra.com/html/li-cor/li-6262/li-6262_instruction-manual_1906652087.webp)
Section 6
Interfacing
6-7
Solving Communication Problems
A few common communication problems and possible causes are given
below:
PROBLEM
WHAT TO CHECK
Nothing happens
Wrong cable. Connections tight? Handshake?
All characters are wrong
Baud rate set wrong.
Some characters are wrong Data bits, stop bits, or parity wrong.
The most common problem in RS-232C communications is the use of the
wrong cable. If you have communication problems that cannot be resolved,
you may wish to purchase an RS-232C indicator card (Model #9960-031).
This card indicates which lines in the cable are being used and generally
indicates where the problem is.
If the output buffer (512 bytes) becomes full, the message "Too much Data
or Baud Rate too low" will be displayed. This can happen at lower baud
rates, or if the handshaking (XON/XOFF or DTR) is preventing the data
from being sent.
6.3 Analog Output
Analyzer output can be recorded by connecting a logging device to the
terminal strip on the back of the analyzer. Both linear outputs (scaled over
any range and in any units) and non-linear outputs are available.
Measuring Linear Analyzer Output
The LI-6262 has two D/A Converters (DAC's), which can be used to convert
calculated quantities (your choice of channels 22-27, 32-38, or 42) to an
analog signal (-5V to +5V, -100mV to +100mV, or 4mA to 20mA ranges).
The voltage and current ranges are selected by choosing the appropriate
terminals on the back panel terminal strip.
DAC #1 is configured using FCT 05 (or FCTS 81-83), and DAC #2 is
configured using FCT 06 (or FCTS 84-86).
A DAC is configured by specifying the source channel (e.g. 22, 23, etc.)
which will drive the analog signal, the source channel value which