VXM Controller Troubleshooting Guide

First – always read the Users Manual.

Whenever you have an issue with the VXM Controller controlling the motor(s), check to be sure the system is configured correctly. The VXM needs to be set-up to recognize the specific motor and axis it is controlling. Install and run COSMOS™ Configurator Software to program the VXM to properly operate the connected motors.

If the VXM does not appear to be controlling the motors properly, run diagnostics. First run the Serial Port Diagnostics. This will indicate whether or not you are communicating with the VXM Controller. If you are not communicating with the Controller, the system may not be configured correctly or you may have an issue with the communications port. Check both.

If the Serial Port Diagnostics runs correctly, but you still have issues, then run the COSMOS Systems Diagnostics. This can help you and Velmex Support, should you contact us, determine what the issue is and how to resolve it.

VXM™ Stepper Motor Controller

Issues with Equipment

Symptom	Possible Cause
Power (Green LED) light does not come on.	Power supply not connected or AC cord not attached. Power switch not on. Circuit breaker tripped (white center protruding from breaker.)
Motor makes noise but is not moving (Stalled).	VXM not configured for Motor, speed too high, broken wiring, or jammed mechanism/motor.
Motor is not making any noise and is not moving (no power to motor).	Limit switches not connected or set for wrong type switches.
Circuit breaker trips when power applied to VXM.	Voltage >28 volts or polarity reversed.
Circuit breaker trips while running motor for a short time.	Wrong motor selected. Shorted wiring.
Circuit breaker trips while running motor for a long time	Wrong motor setting. Shorted wiring. Controller overheating from lack of ventilation or ambient temperature too high.
Controller is too hot to touch. (It is normal for Controller and Motor do get very warm when running continuously.)	Wrong motor setting. Lack of ventilation or ambient temperature too high. NOTE: Motor should always be mounted for heat conduction.
Motor runs erratically (at lowest speeds goes either direction, and has low torque at mid speeds).	Broken wire to motor or broken connector pin.
Motor always goes opposite direction.	Directions were inverted with the "setDM" command. Refer to the "getDM" and "setDM" command.
VXM resets itself and sends "EB" to the host.	A motor 3 or 4 command was sent to the VXM when there is not a second VXM connected to the VXM bus.
VXM continuously resets itself (flashes power light slowly) and sends "EB"s to the host.	A master VXM attempts communication with a slave that is off.
Power (Green LED) light flashes rapidly and continuously on power-up	Run, Stop, or a Jog input is pulled low. The VXM does not allow button Jog inputs to be activated at power up. (release button/input to recover.)
On-Line light flashing continuously (yellow LED).	RS-232 overrun error, host sent commands while VXM was busy sending requested data (power off/on to recover.)
Power and On-Line light flash rapidly and VXM sends "EM" to the host.	Program memory is full (send "K" to recover.)
Power and On-Line light flash rapidly and VXM sends "EL" to the host.	More than 10 nested Loop commands encountered per run (send "K" to recover.)
Power and On-Line light flash rapidly and VXM sends "EJ" to the host.	More than 4 nested "JMx"s encountered per run (send "K" to recover.)
Power and On-Line light flash rapidly and VXM sends "EC" to the host.	When "U9x" missing or motor not the same when continuous indexing (send "K" to recover.)

Sound Indicators

The following are some sound bytes to help troubleshoot motor and controller operation.

Description	Sound
The sound of a normal operating stepper motor:
The sound of an overloaded motor:
The sound of a motor when acceleration is set too high:
The sound of a motor when the speed is set too high:
The sound of a motor with a broken wire: