Filter
Top Products
CyberResearch
®
PC Accessories GFC 1716A
CyberResearch, Inc. 29
25 Business Park Drive P: (203) 483-8815; F: (203) 483-9024
Branford, CT USA www.cyberresearch.com
Product Service
Diagnosis and Debug
CyberResearch, Inc. maintains technical support lines staffed by experienced
Applications Engineers and Technicians. There is no charge to call and we will
return your call promptly if it is received while our lines are busy. Most problems
encountered with data acquisition products can be solved over the phone. Signal
connections and programming are the two most common sources of difficulty.
CyberResearch support personnel can help you solve these problems, especially
if you are prepared for the call.
To ensure your call’s overall success and expediency:
1) Have the phone close to the PC so you can conveniently and quickly take
action that the Applications Engineer might suggest.
2) Be prepared to open your PC, remove boards, report back-switch or
jumper settings, and possibly change settings before reinstalling the
modules.
3) Have a volt meter handy to take measurements of the signals you are
trying to measure as well as the signals on the board, module, or power
supply.
4) Isolate problem areas that are not working as you expected.
5) Have the source code to the program you are having trouble with available
so that preceding and prerequisite modes can be referenced and
discussed.
6) Have the manual at hand. Also have the product’s utility disks and any
other relevant disks nearby so programs and version numbers can be
checked.
Preparation will facilitate the diagnosis procedure, save you time, and avoid
repeated calls. Here are a few preliminary actions you can take before you call
which may solve some of the more common problems:
1) Check the PC-bus power and any power supply signals.
2) Check the voltage level of the signal between SIGNAL HIGH and SIGNAL
LOW, or SIGNAL+ and SIGNAL– . It CANNOT exceed the full scale range
of the board.
3) Check the other boards in your PC or modules on the network for address
and interrupt conflicts.
4) Refer to the example programs as a baseline for comparing code.