Troubleshooting

FAQ and Troubleshooting Guide

Please consult the FAQ and Troubleshooting guides below before calling tech support.

FAQ

Here are some of the most frequently asked questions relevant to all our products.

How can I calculate how far my device will move for each microstep?

This depends on the "microstep resolution" setting of the controller. The default microstep resolution of Zaber products is 1/64 of a step. On the webpage for the product in question, you should see a specification for the device motion corresponding to one full revolution of the motor. You should also see a specification for then number of steps per revolution of the motor. For example, a T-LA device moves 304.8 um per revolution of the motor, and the motor has 48 steps per revolution. Therefore at the default microstep resolution of 1/64 of a step, a single microstep corresponds to 304.8/48/64 = 0.09921875 um. If you change the microstep resolution setting from the default value, you can use this method to recalculate the microstep distance.

What is the difference between resolution, accuracy, and repeatability?

Resolution is the smallest increment you can tell the device to move in. It may not move that exact distance but the position is quite repeatable.
Accuracy is how close the actual position will be to the commanded position. If the accuracy is 6 um and you tell the device to move to 22.345 mm it could go to 22.342 mm or 22.348 or anywhere in between.
Repeatability is how close the device will go to the same position if you tell it to go there several times. If the repeatability is 0.4 um and you tell the device to go to 22.3450 mm, it might go to 22.3460 mm, but it will go to that same position within 0.0004 mm, every time.

After I finish a move command from the computer, the device starts moving again on its own.

If the device is a T-Series model, the control knob might be turned. Make sure the knob is set to the middle detent position. You can feel a slight click in the middle of its rotation. Not all devices have a control knob.

Nothing happens when I turn the control knob either way.

Manual control may be disabled. Restore factory settings with command 36 or enable manual control with command 40 (see the user's manual for details).

I send a move command and nothing happens.

It's likely that the device hasn't been homed yet. Send command 1 after you power up the device to home it.

I try to move the device but it just makes a noise and vibrates.

The load that the device is trying to push may be too high, causing the actuator to stall. You can usually achieve more thrust or torque by lowering the speed. See the manual for details.

There is no communication between the computer and my Zaber device.

1. Make sure you have the correct serial port selected. Try selecting other serial ports in the software.
2. Make sure there are no bent pins in the ends of all the data cables.
3. Make sure the power supply is working. Make sure you plug it in all the way.

My device is behaving strangely.

A setting might have been inadvertently changed. Try restoring settings to factory defaults using the method described for your series of device in the sections below.

Troubleshooting X-Series Motion Devices

The following sections contain tips for troubleshooting common problems. If the device is unable to communicate, and it is operating erratically, a manual factory reset can be performed through the following steps. Note that this will reset most settings.

1. Power Off the device
2. Push and hold the knob for the first Axis (if applicable)
3. Power On the device
4. Continue to hold the knob in until the blue LED is lit (~5 seconds), then release.

The device has been returned to its factory defaults and can be configured as per the steps in Initial Setup.

Front Panel Indicators

Green LED On

The device is powered on and is operating normally.

Green LED Flashes Slowly

The operating conditions of the device are outside of the recommended range.

This will occur when the supply voltage is either over or under the recommended range, the internal temperature has exceeded the set limit, or the driver has been disabled. Check the following:

• The input voltage is within the operational range of the device. This can be read from the device with the get system.voltage command.
• The device temperature is within range. This can be read from the device with the get system.temperature command.
• The driver is not disabled. If the driver is disabled the result of the warnings command will contain the FD flag.

Green LED Off

The device is not powered.

Check the supply connections and power adaptor for correct operation.

Red LED On or Flashing.

A critical error has occurred.

Please contact Zaber Technical Support.

Yellow LED Always Off or Flashes but No Reply.

There are communication errors.

Please see the Communication Errors section below.

Manual Control

Turning the knob either way results in no movement

The knob may have been disabled.

Check that the knob.enable (T:107) setting is correct.

Restore the default parameters through the system restore (T:36) command.

The axis won't cover the full range of travel.

The axis hasn't been homed.

Turn the knob anti-clockwise until the axis reaches the fully retracted position (closest to the motor). The axis will home and the full range of travel available.

Unexpected Behaviour

The axis doesn't respond to a move command.

The axis needs to be homed before use.

Send the home (T:1) command.

The axis is moving on its own and running against the ends of travel.

The position encoder has de-synchronized.

Reset the device by power cycling it or sending the system reset (T:0) command, then re-initialize it with the home (T:1) command.

The axis is moving very slowly. It used to move faster.

The speed settings may have been changed inadvertently.

Send a system restore (T:36) command.

The axis makes louder than normal noise during travel and is frequently slipping.

This condition happens if the thrust needed is more than the thrust available from the axis.

Check the following:

• The force on the axis is less than the maximum thrust.
• The voltage matches the specified voltage. Read the voltage using the get system.voltage command. Voltage less than the specified voltage for the device will reduce the positioner’s maximum thrust.

Test the following:

• Try a slower target velocity.
• Try a lower acceleration and deceleration.
• Clean the screw and lightly re-grease it with a grease that does not degrade plastics.

Please contact Zaber Technical Support.

The axis doesn't cover the full range of travel, or runs into the end.

A setting might have been inadvertently changed.

• home (T:1) the axis to see if this corrects the behaviour.
• Send a system restore (T:36) command.

Communication Errors

There is no communication with the device; the Yellow LED does not come on or flash.

There are several things that should be checked:

• Make sure the correct serial port is selected. Try selecting other serial ports in the software.
• Check the baud rate, hand shaking, parity, stop bit, etc. when configuring the serial communications software. The required settings are listed in the RS-232 Communications section above.
• Make sure there are no bent pins in the ends of all the data cables
• Make sure the device is powered. The Green LED should be on.
• If the computer is a laptop running on batteries, try plugging in the power. Some laptops disable the serial ports when running on batteries.
• Make sure a null modem adaptor or cable is not being used.
• Make sure the correct adaptors(if any) are being used. Refer to the pinouts in the RS-232 Communications section above.
• If the problem was encountered when trying to control the device with custom software, try using Zaber Launcher or Zaber Console (available from the Zaber website) to verify that the hardware is functioning properly.

Two or more devices both respond to commands sent to device 1.

Most devices are shipped with their device number set as 1.If you connect to the devices with Zaber Launcher, it will automatically renumber them if needed. If you aren't able to install and open Zaber Launcher, send the renumber (T:2) command in the software you are using to set all of the device numbers to different values.

The Yellow LED comes on briefly when sending a command, but the device does not move and does not reply.

Check baud rate, hand shaking, parity, stop bit, etc. are set as per the RS-232 Communications defaults.

The device numbers may not be what is expected, issue a renumber (T:2) command. Make sure that the computer does not transmit anything else while the devices renumber.

If using the Binary Protocol, check the following:

• 6 bytes are transmitted and that the device number and command are valid.
• The software does not transmit any control characters such as line feed and spaces.
• That the serial port is not configured with a termination character (it often defaults to linefeed).

If problems are encountered when using custom software, try using Zaber Launcher or Zaber Console (available from the Zaber website) to verify that the hardware works.

The device does not behave as expected when software sends it a series of commands.

If your computer's language and region settings are other than US English, your software may be sending non-ASCII characters or using commas instead of periods as decimal points. Try setting your computer's language to English and region to United States to see if it fixes the problem.

Check what is being sent out of the serial port. stackoverflow.com has a list of some tools to monitor serial ports.

In Binary mode, the device does not send replies but otherwise works.

Auto-reply might have been disabled via T:101.

Send a system restore (T:36) command.

If the problem is encountered when trying to control the device with custom software:

• Use the Zaber Console (available from the Zaber website) to verify that the hardware is functioning properly.
• Make sure that the receiving part of the code or commercial package is correct.
• Check the serial port settings are correct.
• Check connectors for bent or broken pins.

In Binary mode, the device sometimes returns fewer than 6 bytes.

This typically indicates a problem with the serial port settings. Some serial ports are set to automatically recognize and remove specific control characters such as carriage returns when they appear in the RS-232 receive buffer.

Check that the settings are correct and are not removing or replacing characters.

Slipping and Stalling

The axis makes noise but does not move.

The axis is stalling.

Try removing all external loads. If the axis now extends and retracts normally, the problem is excessive load. Try to reduce the load and ensure the load is less than the maximum thrust. A higher thrust or torque can be achieved by lowering the speed of the axis using the maxspeed (T:42) setting.

If an axis is stalling with no external load at default speed and acceleration settings then it requires servicing.

Troubleshooting A-Series Closed-Loop Motion Devices

Symptom	Check
Nothing happens when I turn the knob either way.	Manual control may have been disabled. Issue the Restore Settings (Cmd 36) command or enable the knob using Set Knob Disabled Mode (Cmd 107) with data 0.
Two or more devices both respond to commands sent to device 1.	Most devices are shipped with their device number set as 1. If you connect the devices through Zaber Console, you will be prompted to renumber them. If you aren't able to install and open Zaber Console, send the Renumber Instruction (command 2) in the software you are using to set all of the device numbers to different values.
Nothing happens when I send a move instruction.	The device needs to be "homed" first. You must issue the Home (Cmd 1) command after power up to initialize the device.
Device does not move when sending an instruction or turning the knob.	Check whether the green LED is fading in and out slowly. If so, the device is Parked. Send Set Park State (Cmd 65) with data 0 to unpark the device, or Home (Cmd 1) the device.
The device can move smoothly, but only moves for a short time then stops. Blue LED is flashing.	If the blue LED is flashing and Slip Tracking or Unexpected Position responses are received, but the device is not actually slipping or stalling, the internal encoder counter may need to be re-initialized. Reset the device by power cycling it or sending Reset (Cmd 0) command, then re-initialize it with the Home (Cmd 1) command. Ground the device and avoid operating it under statically noisy environment.
The device is moving on its own, and is running against the ends of travel.	The internal encoder counter may need to be re-initialized. Reset the device by power cycling it or sending Reset (Cmd 0) command, then re-initialize it with the Home (Cmd 1) command. Ground the device and avoid operating it under statically noisy environment.
Stall condition: The device makes noise but does not move. Blue LED is flashing.	Try removing all external loads. If the device now extends and retracts normally, the problem is excessive load. Try to reduce the load and ensure the load is less than the maximum thrust. You can achieve higher thrust or torque by lowering the speed of the device using the Set Target Speed Instruction (command 42). If a device is stalled with no external load then it requires servicing.
There is no communication between the computer and my Zaber device, the yellow light does not come on or flash.	There are several things you should check: Make sure you have the correct serial port selected. Try selecting other serial ports in the software. To ensure that your serial port is working properly, you can connect the send and receive pins of the serial adapter without connecting any devices. Use a wire to connect pins 2 and 6. Your software should echo a reply every time you send an instruction. You can view the pinout diagram here. Check the baud rate, hand shaking, parity, stop bit, etc. when configuring your serial communications software. The required settings are listed in the Control Through The RS-232 Serial Port section above. Also make sure that your serial port is not configured with a termination character (it often defaults to linefeed). Make sure there are no bent pins in the ends of all the data cables Make sure the power supply is working. The dc plug should measure 12 - 48 Vdc when it's not plugged into the device. Make sure the power plug is plugged in all the way. If your device has LEDs, the green LED should light. If your computer is a laptop running on batteries, try plugging in the power. Some laptops disable the serial ports when running on batteries. Make sure you do not have a null modem adapter or cable in the line. The serial to mini-din adapter comes in many varieties and many have different pin connections. Check the adaptor for continuity on the proper pins by consulting the adaptor pin-out diagram above. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware is functioning properly.
My device is behaving strangely. It responds to some commands as expected but not to others.	Send a Restore Settings Instruction (command 36). A setting might have been inadvertently changed. If you have a T-MCA or T-CD series stepper motor controller, note that a data value should be entered with the Restore Default Settings Instruction corresponding to the Peripheral Id of the device you are controlling. Your computer might be set to Unicode. This is common for languages that use non-Latin based characters. Go to Control Panel/Regional and Language Options/Advanced. Select a language for non-unicode programs. This should be English or another Latin based character language.
The device is moving very slowly. It used to behave differently.	The speed settings may have been changed inadvertently. Send a Restore Settings Instruction (command 36).
Green LED does not come on	Check the A/C wall plug, the voltage adaptor and its connection to the device. If the power is coming over the data cable, check the mini din connector for bent or broken pins.
Green LED flashes at 2Hz	The power supply voltage or temperature is out of range. It may either be too low or too high.
Green LED fades in and out slowly. Device does not move when sending an instruction or turning the knob.	The device is Parked. Send Set Park State (Cmd 65) with data 0 to unpark the device, or Home (Cmd 1) the device.
The yellow light comes on briefly when sending a command, but the device does not move and does not return codes.	Check baud rate, hand shaking, parity, stop bit, etc. Make sure that your software does not transmit any control characters like line feed, spaces or something else. The device numbers may not be what you think they are. Issue a renumber command, make sure that the computer does not transmit anything else while the devices renumber. Check that you transmit 6 bytes and that the device number and command are valid. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware
The red LED is on or flashing	Device has lost its settings, or an error has occurred. Please contact technical support.
The device does not send replies but otherwise works.	Auto-reply might have been disabled via Set Auto-Reply Disabled Mode (Cmd 101), try sending a Restore Settings (Cmd 36) command. If you encounter the problem when trying to control the device with your own software, try using a demo program from our website to verify that the hardware is functioning properly. Make sure that the receiving part of your code or commercial package is correct. Check baud rate, etc. Check connectors for bent or broken pins.
The device sometimes returns fewer than 6 bytes.	This problem usually indicates a problem with the settings for your serial port. Some serial ports are set to automatically recognize and remove specific control characters such as carriage returns when they appear in the RS232 receive buffer. When this happens, it appears as though the device has not sent enough bytes, but really the controlling computer has just removed some before you could read them. You will need to change the serial port settings to fix the problem.
The device makes louder than normal noise during travel and is frequently slipping.	This condition happens if the thrust needed is more than the thrust available from the device. Check that the force on the device is less than the maximum thrust. Check the voltage using the voltage command. Voltage less than the specified voltage for the device will reduce the device’s maximum thrust. Try a slower target velocity (command #42) as stepper motors produce more thrust when moving slowly. Lead screw conditions greatly affect the performance of linear motion devices. Dirt, damaged threads, no grease or too much grease will degrade performance and may contribute to a stall. A black residue appears on the lead screw after extended use. This can increase friction and reduce thrust. Clean the screw and re-grease it with a grease that does not degrade plastics. In general if you try to move a large payload or have a large static axial load (like lifting something vertically) you will have more problems. For vertical motion, the use of a counterweight, spring or rubber band can help reduce the static load and improve the performance of the device. The default value of the acceleration and target velocity are good for small to medium loads and medium speeds. For very light loads and higher speeds, or heavy loads at lower speeds, these parameters can be tuned. Trial and error is the best tuning technique.
The device has repeatability errors smaller than 4 full steps.	If you're not skipping steps, friction or loose parts may still cause some variation when returning to a position.
The device does not behave as expected when software sends it a series of commands.	It can be challenging to track down problems in a complicated script or other software. In addition to the standard techniques of debugging any software, it's also helpful to see exactly what bytes are being sent and received on the serial port. There are several tools available to display the raw data from a serial port, and stackoverflow.com has a list of some.

Troubleshooting T-Series Motion Devices

Symptom	Check
After the device finishes a move command, it starts moving again on its own.	The potentiometer knob is probably not centered. Make sure the knob is set to the middle position. You can feel a slight detent in the middle of its rotation.
Two or more devices both respond to commands sent to device 1.	Most devices are shipped with their device number set as 1. If you connect the devices through Zaber Console, you will be prompted to renumber them. If you aren't able to install and open Zaber Console, send the Renumber Instruction (command 2) in the software you are using to set all of the device numbers to different values.
Device starts turning as soon as the power is on or amber LED blinks all the time	The potentiometer is probably not centered. Turn the knob slowly until you feel the center detent.
Nothing happens when I turn the potentiometer knob either way.	Manual control may have been disabled. Issue the Restore Settings Instruction (command 36) or enable the potentiometer using the Set Device Mode Instruction (command 40).
Nothing happens when I send a move instruction.	The device needs to be "homed" first. You must issue the Home Instruction (command 1) after power up to home the device.
When I try to move the device it just makes a noise and vibrates.	There may be too much load that the device is trying to push. The actuator stalls in this situation. Try removing the load and see if the problem goes away. You can achieve higher thrust or torque by lowering the speed of the device using the Set Target Speed Instruction (command 42).
Stall condition: The device makes noise but does not move.	Try removing all external loads. If the device now extends and retracts normally, the problem is excessive load. Try to reduce the load or change step time and acceleration parameters to ensure the load is less than the maximum thrust. If a linear motion device is stalled in its fully extended position and remains stalled without any external load applied it means the lead screw has been over extended and is stuck. You can usually get the lead screw unstuck by pushing on it after issuing the home command. If a device is stalled (with no external load) in a position that is not fully extended then it requires servicing.
There is no communication between the computer and my Zaber device, the amber light does not come on or flash.	There are several things you should check: Make sure you have the correct serial port selected. Try selecting other serial ports in the software. To ensure that your serial port is working properly, you can connect the send and receive pins of the serial adaptor without connecting any devices. Use a wire to connect pins 2 and 6. Your software should echo a reply every time you send an instruction. You can view the pinout diagram here. Check the baud rate, hand shaking, parity, stop bit, etc. when configuring your serial communications software. The required settings are listed in the Control Through The RS-232 Serial Port section above. Also make sure that your serial port is not configured with a termination character (it often defaults to linefeed). Make sure there are no bent pins in the ends of all the data cables Make sure the power supply is working. Check the voltage over the DC plug to see if it measures close to the rated voltage for the supply. Make sure the power plug is plugged in all the way. If your device has LEDs, the green LED should light. If your device has a manual control knob, make sure it is centered (you should feel a detent in the center position). If your computer is a laptop running on batteries, try plugging in the power. Some laptops disable the serial ports when running on batteries. Make sure you do not have a null modem adaptor or cable in the line. The serial to mini-din adaptor comes in many varieties and many have different pin connections. Check the adaptor for continuity on the proper pins by consulting the adaptor pin-out diagram above. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware is functioning properly.
My device is behaving strangely. It responds to some commands as expected but not to others.	Send a Restore Settings Instruction (command 36). A setting might have been inadvertently changed. If you have a T-MCA or T-CD series stepper motor controller, note that a data value should be entered with the Restore Default Settings Instruction corresponding to the Peripheral Id of the device you are controlling. Your computer might be set to Unicode. This is common for languages that use non-Latin based characters. Go to Control Panel/Regional and Language Options/Advanced. Select a language for non-unicode programs. This should be English or another Latin based character language.
The device is moving very slowly. It used to behave differently.	The speed settings may have been changed inadvertently. Send a Restore Settings Instruction (command 36).
The device is not communicating or responding to computer control. The yellow LED may be blinking.	If the actuator has a manual control knob, make sure the knob is centered. Turn it back and forth until you feel a click or detent. Leave the knob at the center detent position. Then turn device off and on, and try again.
Green LED does not come on	Check the A/C wall plug, the voltage adaptor and its connection to the device. If the power is coming over the data cable, check the mini din connector for bent or broken pins. The amber light should turn off.
Green LED flashes	The power supply voltage is outside the specified range for your device. It may either be too low or too high. Some unregulated adaptors may produce voltages significantly in excess of their rated values. If the number of devices connected on a single power supply exceeds its current capability, the voltage may drop below the required minimum voltage. You may experience this problem when many motors on a single supply move together. The load may exceed the maximum current available, causing the voltage to drop too low. If you experience this problem with a single device on a single unregulated supply rated at over 300 mA, then the problem is probably that the supply voltage is too high.
Turning the potentiometer causes no motion.	You may be at the end of travel. This can happen due to missed steps even if the device does not appear to be fully extended. Turn the knob the other way. If the device makes noise but does not move you may be in a stall condition (especially if the device appears to be fully extended). See “Stall Condition” below. The amber light should blink when turning the knob, if not, try turning the power off and then on again. You may also have set the Target Velocity (command #42) so low that it doesn’t produce any visible motion. Try using command #36 to reset the device to default settings and try again.
The amber light comes on briefly when sending a command, but the device does not move and does not return codes.	Check baud rate, hand shaking, parity, stop bit, etc. Make sure that your software does not transmit any control characters like line feed, spaces or something else. The device numbers may not be what you think they are. Issue a renumber command, make sure that the computer does not transmit anything else while the devices renumber. Check that you transmit 6 bytes and that the device number and command are valid. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware
The device does not send replies but otherwise works.	If you encounter the problem when trying to control the device with your own software, try using a demo program from our website to verify that the hardware is functioning properly. Make sure that the receiving part of your code or commercial package is correct. Check baud rate, etc. Check connectors for bent or broken pins.
The device sometimes returns fewer than 6 bytes.	This problem usually indicates a problem with the settings for your serial port. Some serial ports are set to automatically recognize and remove specific control characters such as carriage returns when they appear in the RS232 receive buffer. When this happens, it appears as though the device has not sent enough bytes, but really the controlling computer has just removed some before you could read them. You will need to change the serial port settings to fix the problem.
Poor repeatability or the device does not extend or retract smoothly or makes louder than normal noise during travel.	You may be skipping steps. When skipping, the device will lose position in increments of 4 full steps (not microsteps). This condition happens if the thrust needed is more than the thrust available from the device. Check that the force on the device is less than the maximum thrust. Check the voltage using the voltage command. Voltage less than the rated or recommended voltage will reduce the device’s maximum thrust. Try a slower target velocity (command #42) as stepper motors produce more thrust when moving slowly. Lead screw conditions greatly affect the performance of linear motion devices. Dirt, damaged threads, no grease or too heavy grease will degrade performance and may contribute to a stall. A black residue appears on the lead screw after extended use. This can increase friction and reduce thrust. Clean the screw and re-grease it. In general if you try to move a large payload or have a large static axial load (like lifting something vertically) you will have more problems. For vertical motion the use of a counterweight, spring or rubber band can help reduce the static load and improve the performance of the device. The default value of the acceleration and target velocity are good for small to medium loads and medium speeds. For very light loads and higher speeds, or heavy loads at lower speeds, these parameters can be tuned. Trial and error is the best tuning technique.
The device has repeatability errors smaller than 4 full steps.	If you're not skipping steps, friction may still cause some variation when returning to a position. Depending on the exact cause, there are a couple of device modes that can reduce these errors. See the Set Device Mode command's sections on the anti-backlash and anti-sticktion routines.
A linear motion device extends and retracts smoothly but will not retract to the home (zero) position.	The device will not retract below what it believes to be the zero position. If the device has missed steps due to a previous stall condition or if the device has been set to an incorrect position, the device may incorrectly believe it is at the zero position. You can solve the problem by issuing the home command, or by turning the device on and off and manually homing it.
The device does not behave as expected when software sends it a series of commands.	It can be challenging to track down problems in a complicated script or other software. In addition to the standard techniques of debugging any software, it's also helpful to see exactly what bytes are being sent and received on the serial port. There are several tools available to display the raw data from a serial port, and stackoverflow.com has a list of some.

Troubleshooting T-JOY Devices

Symptom	Check
Green LED does not come on	Check the A/C wall plug, the 12V adapter and its connection to the device. If the power is coming over the data cable, check the mini din connector for bent or broken pins.
Green LED flashes	The power supply voltage is outside the range of 10 to 16V. It may either be too low or too high. Some unregulated 12 V adapters may produce in excess of 16 V. If the number of devices connected on a single 12 V adapter exceeds its current capability, the voltage may drop below 10 V. You may experience this problem when many motors on a single supply move together. The load may exceed the maximum current available, causing the voltage to drop. If you experience this problem with a single device on a single unregulated 12V supply rated at over 300 mA, then the problem is probably that the supply voltage is too high.
Communications do not seem to work, the amber light does not come on or flash	Make sure that you are on the correct com port. Check the baud rate, hand shaking, parity, stop bit, etc. Check the cable and adapter for bent or broken pins. Make sure you do not have a null modem adapter or cable in the line. The serial to mini-din adapter comes in many varieties and many have different pin connections. Check the adapter for continuity on the proper pins by consulting the adapter pin-out diagram below. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware is functioning properly.
The amber light comes on briefly when sending a command, but the device does not reply.	Check baud rate, hand shaking, parity, stop bit, etc. Make sure that your software does not transmit any control characters like line feed, spaces or something else. The device numbers may not be what you think they are. Issue a renumber command, make sure that the computer does not transmit anything else while the devices renumber. Check that you transmit 6 bytes and that the device number and command are valid. If you encounter the problem when trying to control the device with your own software, try using one of the demo programs from our website to verify that the hardware
The device does not send replies but otherwise works.	If you encounter the problem when trying to control the device with your own software, try using a demo program from our website to verify that the hardware is functioning properly. Make sure that the receiving part of your code or commercial package is correct. Check baud rate, etc. Check connectors for bent or broken pins.
The device sometimes returns fewer than 6 bytes.	This problem usually indicates a problem with the settings for your serial port. Some serial ports are set to automatically recognize and remove specific control characters such as carriage returns when they appear in the RS232 receive buffer. When this happens, it appears as though the device has not sent enough bytes, but really the controlling computer has just removed some before you could read them. You will need to change the serial port settings to fix the problem.
Moving the joystick causes no motion. The green LED is on, and the yellow LED blinks when I move the joystick.	The joystick may not be configured correctly to control the devices daisy-chained to it. i.e. the joystick may be trying to communicate to a device number that is different than the device numbers of the devices connected. Try the following steps: - Verify that each device in the daisy chain works individually. - Plug all the devices in a daisy-chain with the joystick being the first device next to the computer, and issue a renumber instruction. - Verify again that the computer can communicate with each device independently. - Check the device numbers associated with each axis of the joystick to see that they address the correct device in the daisy-chain. - Try moving the joystick again.
Moving the joystick causes no motion. The green LED is on, but the yellow LED stays off.	One of the following conditions could cause this symptom: -The joystick axis could have been disabled, by setting the velocity scale to 0. Solution: re-enable the joystick axis by setting the velocity scale to a non-zero value. -You may be in calibration mode. When the T-JOY is in calibration mode it does not send instructions to other devices. Solution: turn off calibration, recalibrate, or power off/on. -Calibration may be wrong. If the dead-bands and limits were reversed, it could make the joystick unresponsive. Solution: recalibrate.

Troubleshooting T-CON Devices

Symptoms	Check
Two more devices seem to both be called device 1 after power up	Most likely one or more of the actuators was sending out data during renumbering. Simply center the knob (so the actuator stops moving or sending out data by itself), and re-initialize.
The controller recognizes less devices than actually daisy chained to the controller	The controller can accept a maximum of 3 daisy-chained devices. Connecting only 3 independent devices with no more than 3 independent axis. Otherwise, make sure the knobs on the actuators are all centered, and try resetting or re-initializing the devices.
Turning the rotary knob on the controller does not do anything, and the yellow LED on the actuator is dimly lit	Make sure that the knob on the actuator itself is centered so that it is not causing the actuator to move independently of instructions from the controller.
The controller appears to freeze on any screen and does not respond to commands.	The knob on the actuator may not be centered. Try centering the knob and try again. If the controller did freeze, simply remove and reconnect power to the setup after centering the knob on the actuator.
The display position moves erratically when I turn the rotary knob on the controller.	The knob on the actuator may not be centered. Try centering the knob and try again.
When switching screen from any menu back to the control screen while an actuator knob is turned, the control screen is blank or prints garbage.	If the actuator is in the middle of sending data when the controller requests it’s position it is possible to see this problem. Stop the offending device (center the actuator’s knob), select the messed up display and turn the rotary knob on the controller. This sends a fresh command to the device and retrieves the proper position.
The actuator is currently at a position X (250), and the step size is set at Y (1000). Why can’t I make the actuator go to zero by turning the rotary knob?	Turning the rotary knob sends a “Move Relative -1000” command to the actuator. 250 – 1000 = negative, which is out of range. The actuator ignores the command. Try moving the actuator with a smaller step size like Y = 50.
The actuator is currently at a position X (282624). I can’t seem to make it go any higher.	The actuator’s internal position counter is at or near its maximum range and cannot go any higher. This is the intentional default on power-up to prevent over-extension of the actuator. Home the actuator.
The controller will freeze on the hourglass symbol or freeze on a different screen.	This is because the controller sent a command to the actuator and is waiting for a reply. It is possible the device was removed, or miscommunicated. Reset the entire setup removing and reinserting the power plug.