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-6
strips off the Frame information around the packet. So, unless you’re doing low-
level analysis of network traffic, you never need to deal with Frame information.
For any protocol, the Packet consists of a destination address, a source address,
some protocol type information, a message length field, and error detection
information.
The TCP/IP protocol adds additional fields to the packet for message sequence
determination and application port ID. The sequence number allows multi-packet
messages to be assembled into the correct order. The port ID specifies which
application running on a system is sending or receiving the message. Support of
port IDs allow multi-tasking within a computer system, with messages being sent
and received from the individual task.
In the TCP/IP protocol, error detection is supported by adding a checksum of the
data in the packet to the end of each packet. Using this checksum, the receiving
system can detect a bad packet and request a re-transmit (using the source
address).
Each Host (device attached to the network wiring) in an Ethernet network has a
unique address that is assigned by the interface hardware vendor. Each vendor is
assigned a block of addresses and it is required that each device produced have a
unique Ethernet address. Users of the TCP/IP protocol very rarely need to know or
deal with the Ethernet address.
When TCP/IP is used, each host is also assigned a unique IP address, but this
address is assigned by the user when the TCP/IP protocol software is initialized.
In contrast to the Ethernet address, IP addresses have a structure that can be used
by Network Management to facilitate breaking the network into segments
(subnets) that make better use of the available data communication capacity
(bandwidth). Use of IP addressing and the network segmentation scheme is
described in “IP Addresses and Segmented Networks” in this appendix.
The relationship between a host's Ethernet address and its IP address is established
by the TCP/IP protocol software. No user interaction is needed to establish this
relationship. However, some network management systems require that the
Ethernet address of each network host be kept in a data base. So, it is sometimes
necessary to communicate the Ethernet addresses of all devices on the network to
the Network Administrator.
IP Addresses and Segmented Networks I-8.
If all networks consisted of a few computers and other devices attached to each
other locally, use of IP addressing and network segmentation schemes would not
be necessary. However, networks have evolved past simple work groups into
campus-wide, inter-campus, and even international interconnect schemes. This
makes it necessary to divide the network into subnets.










