Error Messages Reference
Overview
This document describes the error messages that you may find in the
WxService system log, and provides suggestions for fixing the problem.
The values in curly braces are placeholders for replaceable parameters.
They will be replaced with actual values in the system log.
- SEVERE log entries usually indicate that the system or a sensor
cannot continue.
- WARNING log entries usually indicate a problem if it persists,
but sporadic warnings are usually not serious.
- INFO log entries and below (even if they use the error messages
below) are purely informational.
Invalid administrator key
User attempted to configure the server without setting the correct
administrator key. See
Configuration Quick Reference
for instructions on how to configure authentication.
Counter reset to {0}
The precipitation sensor counter should always count up. This error
indicates that the current value is less than the previous value. This
may happen if the sensor loses power and the backup battery is dead.
Device not found: Address = {0}, file = {1}, family = {2}
A search for a 1-Wire device with the specified address, device file
or device family failed. This may happen if the device address or the
device file are in error, or the device is not connected, or if there
is interference on the 1-Wire bus. The barometer task uses the device
file name to identify the 1-Wire switches inside the AAG Pressure
Sensor.
Device not found: Address = {0}, family = {1}
A search for a 1-Wire device with the specified address or device
family failed. This may happen if the device address is in error, or
the device is not connected, or if there is interference on the 1-Wire
bus. All device tasks use the device family or device address to locate
devices on the 1-Wire bus.
Abnormal operation completion status
The barometer task logs this error if the pressure sensor does not
report the expected value at the end of a command. If this error
persists, it indicates a device malfunction, or persistent interference
on the 1-Wire bus.
Data conversion timeout
The barometer task logs this error if the A/D conversion does not
complete within the expected time. If this error persists, it indicates
a device malfunction, or persistent interference on the 1-Wire bus.
Could not connect to any host in the rotation list
The APRS formatter logs this error if it cannot connect to any of the
hosts in the host rotation aprs.formatter.address
configuration setting. If this error persists, and check your network
and Internet connection. If they're working properly, check
CWOP News for server issues.
Timing tolerance error: {0} = {1, number}
The anemometer task logs this error when the time between samples
exceeds plus or minus 20% of the
anemometer.task.sampling.interval
configuration setting.
This may occur if the computer becomes extremely busy, and cannot read
the device at the specified intervals, or if the system clock changes
abruptly (syncs with a network time server, or user sets the system
clock). See the "Enable Incremental Time Sync" entry on my
Tech Notes
page.
Access tolerance error: {0} = {1, number}
The anemometer task logs this error when the time to access the
anemometer spin counter exceeds 250 milliseconds. This may occur if
the computer becomes extremely busy while attempting to access the
device.
Undefined pattern
The wind vane task logs this error when the A/D converters return
values that it cannot resolve into a directional heading. This occurs
if the wind vane changes direction rapidly while the device is being
read. This is not usually a serious error unless happens more than a
few times a day. Gusty winds can aggravate the problem.
Data value error: {0} = {1, number}
Various sensor tasks log this error if a value is outside the expected
range. The error format will be description = value
to explain the error. If this error persists for a given device, it might
be out of calibration, or the device might be malfunctioning.
Data value error: {0} = {1, number}, {2} = {3, number}
Various sensor tasks log this error if a value is outside the expected
range. The error format will be description = value,
description = value to explain the error. If this
error persists for a given device, it might be out of calibration, or
the device might be malfunctioning.
1-Wire errors, no data, data validation and CRC errors
These errors indicate problems with the 1-Wire bus. This usually
indicates interference on the 1-Wire bus, or wiring problems. Refer to
the Dallas tech note
Guidelines for Reliable 1-Wire Networks for detailed troubleshooting tips.