Filter
Top Products
Reference, Installation, and Operations Manual Troubleshooting comm., mech., and elec.
3-9000-743 Rev S June 2013
Communications troubleshooting 313
A
Appendix D Troubleshooting comm., mech.,
and elec.
D.1 Communications troubleshooting
Q1. Why won't the CPU board LINK LED come on when connecting to the Mark III meter via the Ethernet?
A1. The LINK light indicates good electric connectivity between two LAN ports. It also indicates proper polarity in
the Ethernet connection.
W
HEN CONNECTING DIRECTLY: Check to ensure that the Ultrasonic cable (P/N 2-3-3400-079) "cross-over" type
cable is properly connected.
W
HEN USING A HUB: When using a hub between the Mark III meter and the PC, a straight-through patch cable is
required between the Mark III and the hub and a straight-through patch cable is required between the hub
and the PC. Do not connect either the Mark III or PC to the hub UPLINK port. Most hubs do not allow use of
the port immediately next to the hub UPLINK port when the UPLINK port is used to connect the hub to a LAN.
Ensure the Mark III and PC are not plugged in to a hub non-usable UPLINK port.
Verify that the Mark III meter is powered up by checking that CPU board LED 1 is on (either solid red or green).
If the LED is not on, check power to the meter. If the LED is on, check the Ethernet cable connections.
Q2. My CPU board LINK LED is on but I can't communicate with the meter using Ethernet. What's wrong?
A2. If you are connecting for the first time, refer to Section 5.3.2 for instructions on initial communication (via
Ethernet) setup.
If you are using the Daniel MeterLink program, ensure that the optional Ethernet connection is enabled.
Ensure that the Mark III meter's DHCP server is enabled (CPU board switch S2-2 CLOSED). Verify that the PC
has received an IP address from the meter as follows:
• bring up DOS prompt window (Start->Run->(type)cmd)
• in the DOS prompt window, type ipconfig.
You should then see something like:
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection 1:
Connection-specific DNS Suffix:
IP Address: 192.168.135.35 (note: the last .35 can be up to .44)
Subnet Mask: 255.255.255.0
Default Gateway: