Keithley KPCI-3101 Series, User Manual

Page: 120 / 146

C-10 Systematic Problem Isolation KPCI-3101 — KPCI-3104 Series User’s Manual
14. You arrived at this step from step 2, after successfully starting the Analog I/O Panel. Select
your next action based on the criteria given in the following alternatives:
• If you are performing Scheme B independently as an installation check, then Driver-
LINX and your KPCI-3101–4 board are installed correctly. Return to
Section 3 and finish
installing your data acquisition system.
•
If you performed Scheme B as part of the systematic problem isolation procedure AND
arrived at this point after reconfiguring the board or reinstalling DriverLINX and the
board, then go to “
Problem isolation Scheme G: verification of problem solution .”
• If you performed Scheme B as part of the systematic problem isolation procedure AND
arrived at this point without performing any remedial efforts, then your problem must lie
elsewhere. Go to “
Problem isolation Scheme C: application software ” and check for
application software issues.
Problem isolation Scheme C: application software
In Scheme C, you check for bugs in custom application software, assuming that you can access
the source code. Alternatively, you check for compatibility and installation issues in commercial
application software. In Scheme A, you temporarily installed a KPCI-3101–4 board that is
known to be good in place of a KPCI-3101–4 board that you removed from the computer. This
substitution, still in place, eliminates possible board I/O problems during Scheme C. You now
perform I/O tests using your application software. You debug custom code, if necessary, and
recheck.
NOTE
This is not a stand-alone procedure. Use it only when it is called for by
another procedure.
Follow these instructions as you perform Scheme C:
1. Perform the procedure outlined in the “ Analog input hardware test ,” found later in this
appendix.
2. Based on the results of the Analog input software test, do one of the following:
•
If your software appears not to be working properly with your analog inputs, skip to
step 8.
• If your software appears to be working properly AND your board does not have analog
outputs, skip to step 5.
•
If your software appears to be working properly AND your board has analog outputs,
continue with step 3.
3. Perform the procedure outlined in the “ Analog output hardware test ” found later in this
appendix.
4. Based on the results of the Analog output software test, do one of the following:
• If your software appears not to be working properly with your analog outputs, skip to
step 8.
•
If your software appears to be working properly with your analog outputs, continue with
step 5.
5. Perform the procedure outlined in the “ General-purpose digital I/O hardware test ” found
later in this appendix.