Cryo-con Model 24C
Appendix C: Troubleshooting Guide
Symptom
Condition
Can’t talk to IEEE-488
interface.
Possible causes:
1.
Ensure that the GPIB port is selected. Press the
System
key
and scroll down to the RIO-Port: field.
2.
Ensure that the EOI handshake is set. Please review the
GPIB Configuration
section.
3.
Check that the controller’s address matches the host
computer’s assignment. Press the
System
key and scroll
down to the RIO-Address: field.
Debugging tip: Cryo-con utility software can be used to talk to the
controller over the IEEE-488 port using the terminal mode. All
command and response strings are displayed. Since the software
provides the proper interface setup, it is a good way to establish initial
connection.
Intermittent lockup on the
IEEE-488 interface.
Possible causes:
1.
Bus cables too long or too many loads on a single bus.
2.
Don’t send reset commands before each query. This was
common in early IEEE-488 systems.
3.
Ground loops: Some equipment manufacturers improperly
connect the IEEE-488 Shield Ground wire to their circuit
board ground. This can cause ground loops with equipment
that is properly connected. Debug by disconnecting
instruments from the bus.
4.
Use of unshielded bus cables.
Symptom
Condition
Can’t talk to the LAN
interface.
Possible causes:
1.
A Category 5 crossover patch cable is being used where a
Category 5 patch cable should be used, or visa-versa.
2.
The TCP settings between the monitor and the PC are
incompatible. Review the network configuration section.
3.
PC Client software not configured to use TCP Data Socket
5000.
Debugging tip: Cryo-con utility software can be used to talk to the
monitor over the LAN Data Socket port using the terminal mode. All
command and response strings are displayed. Since the software
provides the proper interface setup, it is a good way to establish initial
connection.
155
