Information, warning, and error codes
This is a current, but partial, list of error messages which the logger can produce when responding to issued commands. Each error message begins with either ERR- (for errors) or WRN- (for warnings), followed by a 3-digit decimal number, padded with leading zeroes if necessary. An (currently fictitious) example would be ERR-065.
The number allows host software to interpret the error code as desired if the rather terse messages from the logger are unsuitable for any reason.
Note that some messages may contain a variable element, represented here by a ‘<place_holder>’.
The errors have been categorized according to their very broad root cause, which will be one of the following:
Wrong usage - incorrect specification of the command or one of its parameters, or inappropriate use of a parameter value.
Change in instrument condition - an previously valid operation can no longer be performed because the state of the instrument has changed in some way.
Factory misconfiguration - the instrument’s internal settings are in an unexpected state.
Hardware failure - a problem with the instrument has prevented the command from succeeding. One possible course of action to remedy this is to apply a full hardware reset (see Tips for system integrators).
List of error and warning messages
Warning
Code | Text | Description |
|---|---|---|
WRN-305 | storage access already at selected location | The storage access command was sent to change to a state the instrument is already in. |
WRN-408 | instrument was already enabled | The current deployment has not finished; no change will be made to the instrument’s state, and all command parameters will be ignored. |
WRN-435 | instrument state is already disabled | The disable command was sent when the instrument is already disabled. |
Error
Error code | Reported description | Root cause |
|---|---|---|
ERR-101 | command parser busy | Wrong usage |
ERR-102 | invalid command '<unknown-command-name>' | Wrong usage |
ERR-104 | feature not yet implemented | Wrong usage |
ERR-105 | command prohibited while logging | Wrong usage |
ERR-107 | expected argument missing | Wrong usage |
ERR-108 | invalid argument to command: '<invalid-argument>' | Wrong usage1 |
ERR-109 | feature not available | Wrong usage |
ERR-110 | buffer full | Wrong usage/Hardware failure |
ERR-111 | command failed | Hardware failure |
ERR-114 | feature not supported by hardware | Wrong usage |
ERR-115 | syntax error '<invalid-argument>' | Wrong usage |
ERR-116 | parse error '<invalid-argument>' | Wrong usage |
ERR-117 | '<invalid-qualifier>' is not a known qualifier | Wrong usage |
ERR-118 | invalid qualifier '<invalid-qualifier>' | Wrong usage |
ERR-119 | missing qualifier | Wrong usage |
ERR-120 | '<label>' is already in use | Wrong usage |
ERR-121 | no qualified objects | Wrong usage |
ERR-122 | value '<value-entry>' is too long | Wrong usage |
ERR-123 | '<value-entry>' is a keyword and cannot be used as a value | Wrong usage |
ERR-124 | '<value-entry>' cannot be set multiple times | Wrong usage |
ERR-125 | '<parameter>' is read only | Wrong usage |
ERR-126 | arguments result in ambiguous command | Wrong usage |
ERR-127 | no value has been set | Wrong usage |
ERR-129 | no more than <max_count> entries allowed in list | Wrong usage |
ERR-302 | download tracking failed, specify all parameters | Change in instrument condition |
ERR-405 | failed to enable for logging | Hardware failure |
ERR-406 | cannot 'pause' while not logging | Wrong usage |
ERR-407 | cannot 'resume' unless paused | Wrong usage |
ERR-410 | no sampling channels active in group ‘<group-label>’ | Wrong usage |
ERR-411 | period not valid for selected mode | Wrong usage |
ERR-413 | period too short for serial streaming in schedule '<schedule_label>' | Wrong usage |
ERR-416 | wrong regimes settings | Wrong usage |
ERR-419 | calibration coefficients are missing | Factory misconfiguration |
ERR-420 | required channel is turned off | Wrong usage |
ERR-430 | empty schedule list in configuration '<configuration-label>' | Wrong usage |
ERR-431 | dataset limit of '<max-count>' reached, delete dataset(s) to make space | Wrong usage |
ERR-432 | if simulating, only one schedule allowed | Current L35 restriction, may be lifted in future |
ERR-433 | no start time specified for gating by time | Wrong usage |
ERR-434 | starttime accessible only if gating by time | Wrong usage |
ERR-436 | instrument was already enabled with different settings | Wrong usage |
ERR-437 | invalid argument ’<invalid-argument>', data storage is not available | Wrong usage |
ERR-438 | channels on sensor '<sensor-label>' split across schedules | Wrong usage |
ERR-439 | no sampling groups active in schedule '<schedule_label>' | Wrong usage |
ERR-440 | incompatible periods for schedules with common channels, '<schedule_label_a>' and '<schedule_label_b>' | Wrong usage |
ERR-441 | config '<config_label>' has too many channels/sensors for given sampling rate(s) | Wrong usage |
ERR-442 | config '<config_label>' streaming too much data for current baud rate | Wrong usage |
ERR-501 | item is not configured | Factory misconfiguration |
ERR-505 | no channels configured | Factory misconfiguration |
ERR-601 | no calibration for channel '<channel-index>' | Factory misconfiguration |
1Error ERR-108 is typically caused by the user supplying an incorrect argument to a command. However, it can also be caused by supplying a valid argument in the wrong position for those commands that require some arguments to be in a certain order. For example:
instrument power internal voltage is correct usage.
instrument power voltage internal is not.