Troubleshooting
6 Troubleshooting
NOTE
The controller must be power-cycled to read in new DIP switch settings.
Power-cycling will return internal parameters to their power-up values.
Problem (1):
When the Mercury™ is powered up, both front-panel LEDs stay dark
(normally upper LED lights green).
Solution: Make sure that:
Switch #8 on the front panel is in lower position (firmware
update OFF)
Power supply with suitable voltage is connected and operating
properly
Problem (2):
Axis starts to move before you send any move commands.
Possible cause: The autostart macro is active.
Solution: Erase the autostart macro
Joystick is connected but not calibrated. See Section 4 on p. 27
for details
Joystick was activated but no joystick is connected. Disable
joystick
Problem (3):
When the PI host software starts, no communication with the
Mercury™ can be established.
Error message "No controller found" or “Could not connect...”.
Solution: Make sure that:
COM port is not being used by another program
Baud rate setting correct (for 9600 baud: SW 5&6:ON)
Upper LED lights green? If not, see problem (1)
Firmware has current version level
For RS-232 connection: C-815.32 null-modem cable is being
used
Either RS-232 or USB cable is connected, but not both
www.pi.ws C-863 MS173E Release 1.2.7 Page 30
To Next Page
Loading...