Specifications

TTroubleshooting

6 Troubleshooting

Communication with controller does not work

Communication cable is wrong or defective

⇒ Check cable. Does it work properly with another device?

For RS-232, a null-modem cable must be used.

For TCP/IP connections: Connect the controller to an Ethernet connector in

the PC using the included cross-over network cable. When connecting to a

network hub or router, it might be necessary to use a straight-through

network cable.

Communications has not been established yet

⇒ TCP/IP communication: If no DHCP server is available on the network or

if a point-to-point connection between host PC and controller is being used,

after power-on or reboot it might take a period of about 30 seconds before

communication is possible.

The interface is not configured correctly

⇒ With the RS-232 interface, check port and baud rate (depending on your

controller, the baud rate may be set via DIP switches on the front panel or

via a controller parameter). It is recommended that the host PC have a

"genuine" RS-232 interface on board. If the host PC uses a USB-to-serial

adapter instead, data loss could occur during communication, especially

when transferring large amounts of data.

⇒ With the GPIB (IEEE 488) interface, check the device address.

⇒ With the TCP/IP connection, connect the controller to a network access

point

before you power it on. Check IP address and IP mask (the settings

of the devices in the network must be compatible, e.g. the IP address of

each device must be unique). Make sure that your network administrator

has not set the network to forbid unknown devices like the E-517 to log on.

Note that if the controller is already connected to your or another host PC

via TCP/IP, a second TCP/IP session cannot be established. Presently,

only one port (50000) is available on the E-517 so that only one application

at a time can use the TCP/IP connection.