NetDAQ Users Manual
Table Of Contents
- 2640A/2645A NetDAQ Users Manual
- 1. Overview
- 2. Preparing for Operation
- Introduction
- Instrument Preparation
- Unpacking and Inspecting the Instrument
- Positioning and Rack Mounting
- Connecting to a Power Source and Grounding
- Universal Input Module Connections
- Digital I/O Connections
- Alarm/Trigger I/O Connections
- External Trigger Wiring for a Group Instrument
- Controls and Indicators
- Front Panel Operating Procedures
- Power-On Options
- Displaying a Monitor Channel
- Displaying the Digital I/O Status
- Displaying the Totalizer Status
- Reviewing and Setting the Base Channel Number
- Reviewing and Setting the Line Frequency
- Reviewing and Setting the Network Type
- Reviewing and Setting the General Network Socket Port
- Reviewing and Setting the General Network IP Address
- Reviewing and Setting the Subnet Mask and Default Gateway
- Viewing the Instrument Ethernet Address
- Host Computer and Network Preparation
- Testing and Troubleshooting
- 3. Configuring NetDAQ Logger for Windows
- Introduction
- Configuring Network Communications
- Configuring the Current Setup
- Setup Files
- Configuring an Instrument
- Configuring Channels
- Configuring Mx+B Scaling From a File
- Entering an Instrument's Description
- Copying a Channels Configuration
- Default Configuration Settings
- Using Configuration Lockout
- Saving an Instrument's Configuration as a Text File
- Configuring the netdaq.ini File
- 4. Operating NetDAQ Logger for
- 5. Using Trend Link for Fluke
- Introduction
- Getting the Right Look for Your Trend Link Chart
- 6. Maintenance
- Introduction
- Self-Test Diagnostics and Error Codes
- Cleaning
- Fuse Replacement
- Performance Test
- Configuring the Performance Test Setup
- Initializing the Performance Test Setup
- Accuracy Performance Tests
- Volts DC Accuracy Test (2640A)
- Volts DC Accuracy Test (2645A)
- Volts AC Accuracy Test
- Frequency Accuracy Test
- Analog Channel Integrity Test
- Computed Channel Integrity Test
- Thermocouple Temperature Accuracy Test
- Open Thermocouple Response Test
- 2-Wire Resistance Accuracy Test (2640A)
- 2-Wire Resistance Accuracy Test (2645A)
- 4-Wire Resistance Accuracy Test (2640A)
- 4-Wire Resistance Accuracy Test (2645A)
- RTD Temperature Accuracy Test (Resistance) (2640A)
- RTD Temperature Accuracy Test (Resistance) (2645A)
- RTD Temperature Accuracy Test (DIN/IEC 751 RTD)
- Digital Input/Output Tests
- Totalizer Tests
- Master Alarm Output Test
- Trigger Input Test
- Trigger Output Test
- Calibration
- Variations in the Display
- Service
- Replacement Parts
- Appendices
- A. Specifications
- Introduction
- 2640A/2645A Combined Specifications
- 2640A Specifications
- 2640A DC Voltage Measurement Specifications
- 2640A AC Voltage Measurement Specifications
- 2640A 4-Wire Resistance Measurement Specifications
- 2640A 2-Wire Resistance Measurement Specifications
- 2640A RTD's 4-Wire, per ITS-1990 Measurement Specifications
- 2640A RTD's 2-Wire per ITS-1990 Measurement Specifications
- 2640A Thermocouple per ITS-1990 Measurement Specifications
- 2640A Frequency Measurement Specifications
- 2645A Specifications
- 2645A DC Voltage Measurement Specifications
- 2645A AC Voltage Measurement Specifications
- 2645A 4-Wire Resistance Measurement Specifications
- 2645A 2-Wire Resistance Measurement Specifications
- 2645A 4-Wire RTD per ITS-1990 Measurement Specifications
- 2645A Thermocouple per ITS-1990 Measurement Specifications
- 2645A Frequency Measurement Specifications
- B. Noise, Shielding, and Crosstalk Considerations
- C. True-RMS Measurements
- D. RTD Linearization
- E. Computed Channel Equations
- F. Data File Format
- G. Dynamic Data Exchange (DDE)
- H. Ethernet Cabling
- I. Network Considerations
- J. Error Messages & Exception Conditions
- K. Fluke Service Centers
- A. Specifications
- Index
- Instrument Parameter Record (Isolated Network)
- Instrument Parameter Record (General Network)
- General Network Parameter Record
- Host Computer General Network Parameter Record
2640A/2645A NetDAQ
Users Manual
I-10
Packet drivers support only one protocol at a time. As a result, only one package
of protocol software can use a packet driver at any one time.
Packet drivers are usually loaded by executing a *.com or an *.exe file in the
autoexec.bat. This loads a terminate and stay resident (TSR) program during
the DOS boot process. The setup of the packet driver is usually done by including
command line switches on the driver load line. There must be at least one switch
that assigns the soft interrupt used to communicate with the protocol stack. Other
switches may be required to set the IRQ, port address, and other parameters.
For example, the 3Com EtherLink packet driver is loaded by executing the line
3c5x9pd.com 0x60, where the 0x60 sets the soft interrupt to number 60
(hex). This driver needs no other parameters because it reads the other information
from flash memory on the interface board. On the other hand, the Cabletron
adapter packet driver reads setup information from a file named e21pd.cfg.
Since each driver is different, the NetDAQ Logger installation program has packet
driver information built-in for only the Ethernet drivers we sell. If other hardware
is used, you must enter the proper information in the Trumpet setup window
during the installation process or edit the autoexec.bat file directly.
Both ODI and NDIS are multi-protocol, packet driver standards. They both allow
operation of more than one set of protocol software "over" the driver at the same
time. Use of this feature will be discussed in the protocol section below.
The ODI standard was defined by Novell for use with the netware line of
networking software. It supports the native IPX/SPX protocol of netware and
other protocols, such as TCP/IP.
NDIS was defined by 3COM and Microsoft for use with the LANManager
networking software. It has since become commonly used by other network
operating systems. It also supports multiple protocols, including IPX/SPX and
TCP/IP.
ODI and NDIS drivers are usually loaded by being included in a DEVICE= line in
the config.sys file. This line loads a DOS-level driver. There are a few
implementations of the NDIS driver as a Windows VxD level driver. The NDIS
driver used with the Windows for Workgroups version of MS Windows is a
Windows VxD.
The setup information for NDIS drivers is contained in a file called
protocol.ini that must be in the same directory from which the driver is
loaded. This file contains sections describing the driver characteristics and the
protocols that may be operating over the driver. For example, a driver
characteristic section might look like this:
[EtherLinkII]
DRIVERNAME=ELNKII$
INTERRUPT=5
TRANCEIVER=INTERNAL
IOADDRESS=0x300