Omega Engineering OMB-DBK-34A, User Manual

Page: 77 / 250

Troubleshooting 5
Electrostatic Discharge (ESD), Handling Notice …… 5-1
Troubleshooting Checklist …… 5-1
Frequently Asked Questions …… 5-3
Customer Assistance …… 5-7
Please read through this chapter before calling for help. Many customers have solved problems without
factory assistance.
Reference Note :
A list of API error codes appears in the Programmer’s Manual included on your CD-ROM. Note
that API does not apply to LogBook.
Electrostatic Discharge (ESD), Handling Notice
The discharge of static electricity can damage some electronic components. Semiconductor
devices are especially susceptible to ESD damage. You should always handle components
carefully, and you should never touch connector pins or circuit components unless you are
following ESD guidelines in an appropriate ESD controlled area. Such guidelines include the use
of properly grounded mats and wrist straps, ESD bags and cartons, and related procedures.
Troubleshooting Checklist
For most problems, proceed through the following checklist. When applicable, be sure to follow ESD
prevention guidelines to avoid damaging components.
1. Power. Check power and fuses to all affected units.
2. If the System Parameters Need Reset. Cycle the power “off” then back “on.” This will often reset
system parameters to the correct values.
3. Signal. Check signal lines and connectors. Connectors must be free of corrosion. All lines should
be undamaged and free of sharp bends and twists. Signal paths should avoid potential sources of
noise such as high voltage and electromagnetic interference.
4. Self-Test. Run system diagnostic tests to confirm the LogBook or Daq device is properly connected
to the PC.
5. Software. Try to acquire data with the DaqView windows application if you are using a Daq device
or LogView windows application if you are using a LogBook. If you are unable to acquire data in
either DaqView or LogView and another program, a hardware problem is likely. If you can obtain
readings by enabling the input reading column, but cannot log data to disk, an interrupt problem is
indicated.
6. Interrupt. Make sure the interrupt selected matches the interrupt used by the parallel port [for
LogBooks and DaqBooks] or the interrupt selected by the hardware switches [on the DaqBoard].
The program MSD.EXE (comes with DOS 6.0 and later) reports the interrupt usage of the computer.
In some cases, an interrupt conflict may arise due to a Windows printer driver stealing the interrupt.
For such a problem, you must edit the SYSTEM.INI file and remove lines loading the printer
drivers. In other cases, the hardware is incapable of accepting interrupts through the parallel port.
7. Parallel port. Make sure the parallel port selected is the same as the port to which the LogBook or
DaqBook is connected. Also, make sure the correct protocol is selected. For Daq device users, Daq
device configuration or DaqTest.exe will verify this. Also see
Parallel Port Troubleshooting Tips .
DBK Option Cards and Modules
967094
Troubleshooting Tips 5-1