Instruction manual

SECTION 5. NETADMIN
5-6
5.2 NETWORK HEALTH
FIGURE 5-3. Main NetAdmin Screen Showing Network Health
When a description is made active, the com-
munications module (DLSMGR) will attempt to
establish communication with each new station in
the network. The NetAdmin main screen (see
Figure 5-3), will show each station entered in the
description. The stations will be black until com-
munication is attempted. A green color indicates
successful communication, blue indicates a
warning occurred, and red indicates a fault.
If a station is blue or red, there will also be
warning or fault message generated. These
messages can be viewed by selecting
STATUS/ WARNING/FAULT from the VIEW
submenu. See Section 5.5 on SWF messages.
The net description should also be checked to
ensure the affected station was entered
correctly. Check the path, dialing strings, and
switch settings. Repeat the "make active"
procedure if any corrections are made.
A flashing indicator (the Memory Low Indicator)
will give warning when less than 2 megabytes of
virtual memory is available. OS/2 attempts to free
memory by swapping block to the hard disk. Low
virtual memory can indicate that hard disk space
is low. This may also be a sign that too many
programs are being run concurrently. Long term
operation with insufficient memory or hard disk
space is not reliable. The indicator appears in the
bottom right corner of the Communication and
Data Collection box.
The PAUSE NETWORK COMMUNICATION allows
pausing communication to all nodes in the network.
The pause time is increased by dragging the "slider"
control to the right. The box below the control indi-
cates how much longer the communication will be
paused. When DLSMGR is started, it will pause
before starting communication with the datalogger
network. This allows NetAdmin to be started and
the paused time increased before communication
begins. This is only important when preventing
communication is necessary.
5.3 CLOCK SET/CHECK
For most applications it is important to keep the
datalogger's clocks synchronized with each other
and the computer. However when manually setting
the clocks or when scheduling unattended clock
sets, it is important to consider three consequences
of changing the datalogger's clocks.
First, make sure the computer clock is set correctly
as it is used as the reference time. Many
computers have inaccurate clocks.
Second, consider when the datalogger's clock is
changed. If the dataloggers are collecting data,
setting the clock may cause the datalogger to
miss or cause an extra output interval if the
clock is changed when the datalogger is near
an output interval. For example, if the
datalogger clock says it is 12:01 and the
datalogger has just stored hourly data