Laser beta lasermike LS8000-3 - Manual (Page 206)

LaserSpeed 8000-3 Instruction Handbook
Appendix E: Troubleshooting Guide
Part No. 93463 / Drawing No. 0921-01561 Page 206 of 221 Revision A (Sep 2007)
If using RS-232 over a long
cable, the baud rate may
too high.
Switch to RS-422 for
communications.
are typing while pins 2 and 3 are
connected. If no characters appear
on the screen, the cable or computer
serial port may be faulty.
See the
Automatic Baud Rate Detection
section to reset the baud rate to a lower
rate, or connect a shorter cable.
RS-422 uses differential signals that have
much better noise immunity than RS-232.
USB to RS-422 converters are
commercially available.
The gauge is communicating, but I
can't see what I'm typing in
HyperTerminal. Terminal Settings The gauge does not echo the characters
you are typing, so you must configure
your terminal program to echo. Turn on
the "Echo typed characters locally"
setting in HyperTerminal. Adjust terminal
settings to match the following:
Time scale in LaserTrak looks
wrong LaserTrak is missing data
points. The X axis in LaserTrak is drawn based
on the gauge's User Update Rate setting.
If the gauge is configured to output data
very fast, but baud rate is such that there
is not enough time to send each reading,
some readings will be dropped. To
correct this problem:
1. Change the User Update Rate to
output data less often
--- or---
2. Switch to a faster baud rate.
LaserTrak detects gauge on the
wrong com port. Computer has virtual serial
ports or a modem.
1. If using LaserTrak 4:
Disable the virtual
User Software sometimes creates virtual
com ports that LaserTrak searches for a
LaserSpeed gauge.
1. Cancel the "Find LaserSpeed
Gauges" screen if it appears when