Specifications

107
5.12.7 Event log file
This file is always named HISTORY.DOC. Note that this is a human readable text file that does
not contain messages. In order to trace buoy behaviour during testing or deployment several
events are logged. Table 5.12.2 gives a list of all possible events. In case you experience any
buoy problems and you intend to contact Datawell Service please include this log file in your
email or keep it at hand when calling.
Table 5.12.2. Alphabetical list of possible events logged and their meaning.
Event string WR-
SG
DWR-
MkIII
DWR-
G
Meaning
Buoy started x x x buoy started by power-up reset
Clock set x x x system clock set by GPS receiver
GPS fix timed out x x GPS position receiver unable to find a
position fix within preset time
GPS wave data
recovered
x real-time data stream recovered after large
gap
GPS wave receiver
timed out
x GPS wave receiver did not respond within
preset time; buoy will be reset
Large gap in GPS wave
data
x large gap encountered in real-time data
stream; GPS wave receiver error or
washing over waves
Logger restarted after
repetitive errors
x x x repetitive logger errors caused logger
restart; does not affect other buoy functions
Logger started x x x logger started either by power-up reset or
console command
Logger stopped x x x logger stopped
ORBCOMM position
found
x x x Orbcomm module found new Doppler
position for internal use only
ORBCOMM user
command processed
x x x Orbcomm module received new timing
interval or Hs-threshold
Unknown event x x x this event is unknown
VRU communication
timed out
x x ADC module did not respond within preset
time; buoy will be reset
Argos communication
timed out
x x x Argos PTT did not react
Argos module is restarted