Measurement Computing WaveBook rev.5.3 - Manual (Page 113)

WaveBook User’s Manual – IO version 979194 Troubleshooting 7-5
Table 1, No communication with the PC, (continued)
Possible Causes Details and Possible Solutions
Another
application is
communicating
with WaveBook.
WaveBooks are limited to communicating via one software application at a time. Thus, if an
application such as LabVIEW, DASYLab or a custom API currently has communication established
with the WaveBook, WaveView will not be able to communicate with the device. In the case of
DASYLab, simply having a worksheet open that references a particular unit, will not allow any other
application [such as WaveView] to open communications with that unit. In custom API programs
communications to multiple units may be established, e.g., WaveBooks on multiple parallel ports. In
such cases, only the current program may establish communications with these devices.
A WBK30 has
been removed.
If a WBK30 memory option has been removed and the three associated bypass jumpers have not been
installed inside the WaveBook (on header J101), communications to the PC will not occur.
WaveBook/516E users will need to contact the factory in regard to WBK30 issues. Users of other
WaveBook models should refer to the WBK30 section of the WBK Options User’s Manual
(p/n 489-0902).
2. IRQ test fails. The IRQ test did not pass in the Daq Configuration Utility.
Possible Causes Details and Possible Solutions
There is a
shared
interrupt.
WaveBook drivers do not allow sharing of interrupts; thus the IRQ test failure was likely caused by the
interrupt [which is assigned to the LPT port] being assigned elsewhere. In the case of parallel port
communications, ensure that the parallel port has exclusive assignment of the interrupt used.
Windows/2000’s
Device Manager
is not set to use
interrupts.
Windows/2000 allows the user to select whether or not to use assigned interrupts for a particular
device. The IRQ test failure could be due to the Device Manager being set not to use interrupts. Make
sure that the Device Manager is selected to the “Use any assigned interrupt” option.
3. ECP and / or EPP protocol problem. WaveBook is not working with ECP or EPP protocols.
Possible Causes Details and Possible Solutions
The driver is not
supportive of
ECP protocol.
The driver version may not support the ECP protocol. Review the read.me file for your current
installation to ensure that ECP compatibility is featured. Note that the latest drivers can be
downloaded from the IOtech website, free of charge.
The EPP type is
not compatible
with WaveBook.
Although the WaveBook may have EPP capability, because the EPP protocol is a diversely interpreted
it is possible that the PC’s EPP type and version is not compatible with that of the WaveBook. Note
that ECP is a more highly defined protocol; and for this reason ECP should be used in cases where
EPP does not appear to be compatible
The WaveBook
is not ECP
compatible.
If the WaveBook was manufactured prior to June of 2000 it is likely to be incompatible with the ECP
protocol. This incompatibility issue can be resolved via an upgrade. Contact the factory for additional
information.
Also refer to table 15, Parallel Port Problems.