Campbell LoggerNet, Instruction Manual

Page: 536 / 580

Appendix E. Log Files
TABLE E-1. Transaction Log Messages
User Response to
Code Message Text Message Parameters Message Meaning Message
8 Security
database read
failed
When the server
started up it could not
read the security
settings file. This is a normal
message on server
startup if security has
not been set up. If
security should be set
the file needs to be
removed and security
re-configured.
9 Modem default
database read
failed
When the server
started up it could not
read the default
modem file
wmodem.ini. This file should exist in
the working directory
on the server computer
(c:\campbellsci
\loggernet\sys\bin).
May indicate a
permissions or
configuration problem
on the computer.
10 Modem custom
database read
failed
When the server
started up it could not
read the user
customized modem
settings file
wmodem.cust. If the user has not set
up custom modem
configurations, this file
will not exist.
11 Clock check
started
A clock check has
been initiated. This
clock check is not
sent out to the station
until the transaction
is sent.
12 Clock set Device time before set;
Server time; The device clock has
been set.
13 Clock checked Datalogger time The datalogger clock
has been checked.
14 Clock check
failed
Reason code:
3. Communication failure
4. Invalid datalogger
security clearance
5. Invalid transaction
number specified (already
in use)
6. Communications are
disabled for this device
7. The transaction was
aborted by client request
8. The device is busy with
another transaction The clock check/set
failed for the reason
specified in the
reason code. Check the connections
of the communication
path to the datalogger,
make sure the
datalogger is connected
and has power, check
the security setting in
the datalogger and in
Setup, check that
communications are
enabled in Setup for all
the devices in the path.
E-4