Product Registration | Knowledge Base | Software Downloads | Support Documents

Knowledge Base

Search Keywords | Search Text | Index by Description | Index by Tip ID

What To Do When The ComProbe Is Not Responding or Stops Responding

PROBLEM DESCRIPTION

FTS sometimes finds the ComProbe on startup or when the Test button is pressed on the Hardware Settings window, but then later displays the message "Test Device Not Responding" or "ComProbe not responding, but was before. This could be due to a loss of power. Cycle power on the ComProbe and then restart program."

SOLUTION

1. Try a different parallel port mode.

Many PC parallel ports can operate in one of several modes. These usually have names like bi-directional, ECP, and EPP mode. There may also be uni-directional, normal or other modes, depending on the PC. The parallel port mode can usually be changed in the system BIOS or system setup. Some PCs also have parallel port setup utilities that are accessed from the Start button in Windows. Check for a utility in Windows first, and then try changing the mode from the BIOS. See your operating manual for help on getting into the BIOS. You may need to change the mode both in Windows and the BIOS.

You may need to try several modes before finding one that works with the ComProbe.

2. Adjust the ComProbe delay values.

FTS must adhere to the timing requirements of the ComProbe in order to communicate with it. The timing requirements are expressed in three delay values called Long Delay, Short Delay and Nibble Delay. FTS profiles your computer to determine the best delay values and uses these by default. However, FTS does not always get the delay values exactly right, and it may be necessary to adjust them to get the best performance.

The delay values are changed from the Hardware Settings window. To open the Hardware Settings window, start FTS, and choose Hardware Settings from the File menu on the Control window.

The delays determined by FTS are located in the Computed column. To adjust the delays, click the radio button labeled User. This should activate the User column, allowing you to change the values. Set the values in the User column to match the values in the Computed column. The computed delay values will often be zero for the Short and Nibble Delays, and a number for the Long Delay.

The first adjustment to try is to increase the value of the Long Delay by five. Leave the Short and Nibble Delays at their computed values. Close the Hardware Settings window, exit FTS, and restart FTS. FTS will use the values you entered in the User column when it restarts to communicate with the ComProbe.

If increasing the Long Delay by one does not solve the problem, try increasing first the Long and then the Short Delay. If the problem still exists after adjusting both these delays, increase the Nibble Delay. There is no hard and fast rule on how much to adjust the delay values or what values to use for a particular PC. Start by adjusting each delay value by one until a set of delays is found which works well.

3. Test the power supply.

Disconnect the ComProbe from the PC. Check that the ComProbe is connected to either the power supply or a fresh 9 volt battery and turned on. The green power indicator should light steadily and not flicker. If the power light is out or flickers, you may have a bad power supply or battery, or a bad ComProbe. If using the power supply, check that the connection between the ComProbe and the power supply jack is tight, and that the power to the ComProbe is not being interrupted from a loose jack.

Troubleshooting ComProbe Problems under Win2K and Windows ….pdf