Table of Contents
Advertisement
5-8
Troubleshooting
18. Based on the results of step 17, do one of the following:
• If you can write and read all I/O bits to and from the OK board, skip to step 21.
• If you cannot write and read all I/O bits to and from the OK board, there may be data
acquisition program errors or defective slot contacts corresponding to I/O bits; continue
with step 19.
19. You have arrived at this step because you cannot write and read all I/O bits to and from the
OK board. You may have already tried some data acquisition program source-code debug-
ging. Do one of the following:
• If either of the following statements are true, then continue with step 20.
– You have arrived at step 19 before debugging the source code.
– You have arrived at step 19 after debugging the source code once, but you have not
yet tried to find more code bugs after two or more I/O test failures.
• If both of the following statements are true, then the cause of your problem may be out-
side the scope of these diagnostics. Read the instructions in
contact Keithley for help in isolating the cause of your problem:
– You have arrived again at step 19 after having debugged the source code at least once
and after having failed the I/O bit tests at least a second time.
– You have tried to find more code bugs after two or more I/O test failures and cannot
find any more bugs.
20. Thoroughly check if all data acquisition program source-code lines are OK. Check the pro-
gram documentation and/or use a debugger to look for programming errors that may be caus-
ing the problem.
• If programming errors are found, do the following:
a. Debug and fix all known data acquisition program errors.
b. Repeat steps 17 and 18.
• If no programming errors are found after thorough debugging, then the cause of your
problem may be outside the scope of these diagnostics. Read the instructions in
"Technical
support," and then contact Keithley for help in isolating the cause of your
problem.
21. If you can write and read all I/O bits to and from the OK board, do the following:
• If you have arrived at step 21 after program corrections have been made, and you can
now write and read all I/O bits to and from the OK board, then the problem has appar-
ently been resolved. Skip to step 27.
• If you have arrived at step 21 without making data acquisition program corrections and
can write and read all I/O bits to and from the OK board, then faulty external I/O connec-
tions may have caused your problem. Continue with step 22.
22. Check for external wiring faults as follows:
a. Into the OK KPCI-PIO32IOA or KPCI-PDISO8A board, plug back one of the STP-36
accessories (or an in-house-wired 36-pin mating connector) that is wired to external cir-
cuits. You unplugged one or more of these in step 1.
b. Check each external I/O connection, one at a time, for short circuits and open circuits and
immediately correct any faults as you find them.
c. If KPCI-PIO32IOA and KPCI-PDISO8A boards were installed in more than one PCI
slot, repeat steps 22a and 22b until all external circuits have been checked and all faults
have been corrected.
23. Based on the results of step 22, do the following:
• If any external I/O connection faults were found and corrected, assume that your prob-
lems were caused by the faulty connections. Skip to step 27.
• If all external I/O connections were found to be normal, then, by process of elimination,
the KPCI-PIO32IOA or KPCI-PDISO8A board(s) originally installed in the computer is
likely the cause of the problem. Continue with step 24.
KPCI-PIO32IOA and KPCI-PDISO8A User's Manual
"Technical
support," and then
Advertisement
Table of Contents
