Filter
Top Products
Chapter 6 539
Programming Fundamentals
Using the LAN to Control the Instrument
Programming Fundamentals
Either a hardware problem or a software problem can prevent the
instrument's remote file server from communicating over the LAN. The
following common problems may be encountered:
Communications Not Established If you have just installed and
configured the LAN interface and you have never been able to access
the instrument via ftp or telnet, go directly to “Pinging the
Instrument from a Computer or Workstation” on page 6-542.
If you have previously been able to access the instrument via ftp or
telnet and now cannot do so, check the following:
o Has any hardware been added or moved on your network? This
includes adding or removing any workstations or peripherals, or
changing any cabling.
o Have software applications been added to the network?
o Has the functionality been turned off from the front panel? Press
System, Config I/O, SCPI LAN.
o Have any configuration files been modified? Pressing
System,
Restore Sys Defaults
restores the original factory defaults and you
will have to re-set the instrument IP address and host name.
o Is the upper- and lower-case character usage in your host name
consistent?
o Have any of the following files been deleted or overwritten?
UNIX:
—/etc/hosts
— /etc/inetd.conf
— /etc/services
PCs:
— dependent network files
If you know or suspect that something has changed on your network,
consult with your network administrator.
Timeout Errors Timeout errors such as “Device Timeout,” “File
Timeout,” and “Operation Timeout,” are symptoms of one or both of
the following problems:
— The currently configured timeout limits are too short compared to
the time it takes the LAN to complete some operations. This
problem may occur during periods of increased LAN traffic.
— The LAN connection has failed, or fails occasionally.
To increase your timeout period, refer to your computer
documentation for instructions. Contact your LAN administrator if