Home Home Applications Products Products Support Support Downloads Downloads Company Company
Applications

WinTES/PC2000 Troubleshooting

From the WinTES start up screen, selecting Diagnose (or Install) will bring up the WinTesCheck screen. If you were to select "PRN1", for example, from the drop down menu at the top, Win TES Check would try to find and test a camera connected to the parallel printer port #1. The result when no camera was connected would be as shown in the figure below. Anyone who downloads the demo software can do this much, because no camera or interface is required!

As each item in the list is being checked, the box to right of the text will be blinking. When each test is completed, the box will be filled in green if the test was passed. In the above figure, the Available Memory and Processor Speed were found to be acceptable for use. Had this test been run on a 286, this would likely have not been the case. This much of the test can be usefully applied by prospective customers to see if their computer will be adequate for use with the PC2000.

If the test was failed, it will be filled in red and generally subsequent tests will not be attempted. Thus, as in the above figure, the bottom four boxes are black indicating that those tests have NOT been performed. In addition, the failed "red" test will generally have an explanation or suggestion printed to the right of the box.  For a failure in the last step, "Initialization", a failure code will be displayed to the right of the red box.

WinTES Check
Some representative or common failure displays are:
Cables being securely connected and fully seated are one of the more common problems. If the interface board or cable from the computer printer port to the /e interface module is faulty, the failure will generally occur in the "Camera Interface" step as illustrated above. Problems diagnosed as Cable connections to the camera (from the computer or /e module) will show up in the "Interface Communications" step or any of the following steps. A connection or cable problem can cause a wide range of symptoms. If you have a potential cable problem, please check the possibility of a connector assembly recall applicable to your camera.
Failure codes (displayed to the right of the red box on the bottom line, "Initialization"):

If something is blocking the left/right mirror motion, or if the "home" micro switch has failed because, for example, its lever got bent or snagged from being improperly packaged for transport, then WinTEScheck will fail on the last test with a failure code 4 that indicates that the PAN motion was not working properly.

If something is totally blocking the mirror's up/down flapping motion, the "Mirror motion" test will fail and the passage "Is there something in the camera cavity?" will be displayed to the right of the red box for that test.

If something is partially blocking or impeding the mirror's up/down flapping motion, the "Mirror Motion" test may succeed, but the "Initialization" test will still fail. Several error codes are possible in this case depending on the exact point at which the initialization process determined it could not achieve satisfactory mirror motion. The code 255, if it appears, indicates a time-out by the computer while waiting for the interface to find a solution to the mirror motion control algorithm. A code of 32 means that the index or reference for the mirror's motion was not found and indicates a fairly severe disruption of the mirror's ability to flap correctly. Code 16 indicates the mirror could not move far enough to have full motion. Codes 8, 24 and 40 can indicate a specific reason that the solution to the mirror motion control algorithm fails, although in practice the timeout 255 code is more likely to occur first.

If the foam strip packing material that is to be placed behind the mirror is not remove, the error code most likely to occur is 16.

If the calibration parameters become corrupted, "Initialization" will fail with an error code 128 displayed to the right of the red box on the bottom line.

Other codes and symptoms are constantly being added to this list. If you are trying to trouble shoot, be sure to check the most recent version of this page.

Maintenance Mode

If you contact Compix for trouble shooting assistance, you may be asked to use the maintenance mode of Win TES Check. If so, you will be instructed on how to enter the maintenance mode from the TES Check window illustrated above. If that happens, be sure the mouse cursor is inside the TES Check window when you press the instructed keys. When you enter the maintenance mode, you will see a window like the one illustrated below.

CAUTION: From the maintenance mode, you can corrupt or destroy the camera calibration data and can even create combinations of parameters which could be harmful to the camera. Therefore, the use of this mode should not be attempted except in conjunction with active guidance and coordination with Compix personnel.

Maintainence Mode
NOTE: Older versions of WinTEScheck may have a maintenance mode window as shown below in which the buttons' functions have been moved to the drop down list of the newer version.
Old look fo maintainence mode
Compix is a registered trademark of Compix Incorporated. Copyright © 2010 Compix Incorporated. All rights reserved.