Fluke NetDAQ 2645A - Manual (Page 278)

2640A/2645A NetDAQ
Users Manual
I-16
Network drivers typically use PC soft interrupts to communicate with the protocol
software. If you’re using two network cards, and as a result, two drivers, you must
select two different soft interrupt levels for the drivers. For example, Packet
drivers (used with Trumpet) usually use soft interrupt level 60 (hex). If two packet
drivers are resident, one can use 60, but the other must use something else (like
61). Usually, this must be communicated to the driver (via a command line switch
or configuration file) and to the level of protocol software that is communicating
with the driver (winpkt in the case of Trumpet).
So, you usually have to include a command line switch on both the driver load line
and on some other load line (like the winpkt line) to identify the soft interrupt and
these much match each other. Packet drivers may use soft interrupts in the range
60 - 7F (hex).
Troubleshooting Information I-15.
This section presents some information about what to do if you cannot
successfully communicate between your PC and NetDAQ instruments.
1. Mouse stops working when using a Parallel-to-LAN adapter (PLA).
This is usually due to a bus mouse using the same IRQ as the PLA's parallel
port. Move the bus mouse to a different IRQ.
2. Bind fails during PC boot.
Check that the information in the driver section of the protocol.ini file
associated with the NDIS driver, matches the setup of the Ethernet adapter.
Check for misspelled words in the protocol.ini file (NDIS driver). Make
sure that the BINDINGS= line in the [NETMANAGE] section contains the
name of the correct driver section.
Check that the soft interrupt specified for use by the network interface driver
is the same as specified for use by the protocol software. Make sure that this
interrupt is not being used by another software package (i.e. another hardware
driver).
3. Network software loads and binds properly, but NetDAQ Logger cannot
communicate with the instrument.
Use the communication configuration dialog and the instrument front panel
interface to check that the Base Channel Number (BCN), IP address, Socket
Port Number, and Instrument Type are all correct for each instrument.
If General Networking mode is selected, check that the subnet of the PC is the
same as the subnet of each instrument (see “IP Addresses and Segmented
Networks” in this appendix). If the subnets are not the same, check the router
connecting the subnets to make sure it can route IP packets. Also check the