Controller will not respond to host PC
Symptoms
All or some commands from the user's PC are not executed by the controller. See also the ‘Cannot start a move/scan‘ sections below.
Possible causes, tests, cures
If only some commands are ignored:
Check that the UCC2 is enabled for the type of commands you are sending. If you are sending scanning commands and the controller has
not been licensed for scanning, then the commands will not be accepted.
Some commands are not executed by the controller if it is preoccupied with a previous command. See the programmer's guide for
information on individual commands and their handling. The controller state number ﴾from the status bytes in the reply to the ‘position
and status' command) will indicate whether it is able to execute that command at that time.
Other commands are ignored if inappropriate for the current circumstances, e.g. asking for a peripheral's data when none is available.
If all commands are ignored:
Send the ‘resync controller' command ﴾#351﴿. If this restores normal operation, the controller was in a locked state due to some internal
malfunction. A possible cause is an incorrectly constructed command from the host PC to the controller. If the system is fully
commissioned and is being controlled by proven user front-end software, consult the Renishaw support services. If the front-end software
is not fully proven in service, the faulty command must be found.
Send the reboot controller command ﴾#335﴿. If the front panel LEDs are now extinguished, except the ‘power on' and flashing error,
download the controller program and reinitialise the controller.
Power down the controller, wait at least 10 seconds and then power up again. Download the controller program and re-initialise the
controller. If this restores normal operation the controller was in a locked state due to some internal malfunction. Proceed as described
above.
Check that the Ethernet cable between the host PC and the controller is in place and undamaged. Reconnect or replace as necessary.
If none of the above tests succeed in solving the problem then it is possible that there is a problem with the communication link between the
host PC and the controller. Section 3 describes the IP configuration in detail but in the following sections there some additional checks
outlined that you can make.
Seeing the IP address of a UCC2
Follow the procedure in
"Configuration of IP addresses"
, but once you have seen the IP address of the device click on the ‘Exit' button.
Checking the IP address of the UCC2 with ping
You can check the IP address of a UCC2 either by running the IP configuration software, as described in
"Configuration of IP addresses"
you can use the command-line utility ping. Ping tests connectivity, so as long as your UCC2 has an IP address and is either waiting for a
download or the downloadable is running, you can check that you have a connection to it by pinging it. This is done as follows:
1. Use ipconfig to ensure that your network adapter is not in the “Media disconnected” state:
UCC2 and UCC2-2 installation guide
www.renishaw.com
Issued 07 2021
53
