Sensor & Device Metadata (error codes)
The ZENTRA System can collect, transmit, and display sensor metadata. Most metadata represent conditions that likely cannot be resolved without intervention. Metadata comes in two frequencies. One is…
The ZENTRA System can collect, transmit, and display sensor metadata. Most metadata represent conditions that likely cannot be resolved without intervention. Metadata comes in two frequencies. One is "slow moving" and the other is "fast moving."
Slow Moving Metadata
The data logger sends slow moving metadata when:
- A data logger reboot occurs (the TEST button on the board is pressed).
- A change in sensor type is set by the user or auto detected by the data logger.
- Auto sends once per day just after midnight local time.
As a result of the slower moving nature of this metadata, it may be stale soon after it arrives. Stale metadata will clear after the next midnight local time communication if the issue has been resolved. Pressing the physical TEST button will also clear stale metadata if you are servicing the unit onsite.
Slow moving metadata is currently available via the v4 API but not the v5 API.
AutoPump Low Battery
Indicates that the battery in the AutoPump is low and should be charged or swapped out.
AutoPump Frozen
Indicates that the pump could not run due to freezing conditions. This is a non-damaging event and will clear once the weather warms up.
AutoPump In-Line
Indicates the presence of an AutoPump accessory used with the HYDROS 21 + G3 Drain Gauge.
Backup Temperature
Indicates that the primary temperature sensor is broken and that a backup temperature source such as the ATMOS 41 RH sensor temperature is in use.
Curated Rainfall Degraded
Indicates that the volume between the drop counter and the tipping spoon differs by more than 0.68mm (about 0.03 in).
Degraded Output
Indicates when a digital sensor detects corruption in a secondary calibration. The specific calibration that is corrupted will be ambiguous when there is more than one secondary calibration associated with the instrument.
Firmware Corrupt
Indicates when a digital sensor detects corruption in its firmware. This can be cleared by loading new sensor firmware code. Firmware - METER Group
Freeze Damage
Indicates the sensor experienced temperatures low enough to freeze water contained in the sensor, causing physical damage to the sensor. This metadata cannot be cleared once triggered.
GPS Failure
Indicates the onboard GPS/GNSS hardware is not working or is unable to get a location fix.
Offline
Indicates that the sensor is unplugged from the data logger port.
Orientation Error
Indicates when a sensor orientation is problematic. Set when a tensiometer installation orientation does not allow in situ refilling, or when a weather sensor tilt angle is too large, greater than +/- 2° from zero.
Pyranometer Calibration
Indicates when the current calibration for the pyranometer is no longer adequate. The ATMOS 51 uses the location provided by its onboard GNSS and the Clear Sky model of available solar radiation to determine a “local calibration”. The pyranometer should be swapped out or sent in for recalibration.
Refill Required
Indicates when the tensiometer has detected a cavitation and now requires a refill to remove an air bubble.
Fast Moving Metadata
The data logger sends "fast moving" metadata with every measurement value. This metadata is available in table exports and from the v4 and v5 APIs.
65528 Sensor calibration problem
The sensor is reporting a problem with its calibration values or a critical setting. This could be from a broken sensor or corrupted firmware.
65529 Excitation under-voltage error
The sensor is reporting that the excitation voltage is too low to reliably make a measurement.
- This could be because the data logger is low on power. Install new batteries and check the PCB board for corrosion.
65530 Sensor is reporting a temporary lack of data
The sensor is reporting that it temporarily cannot make the measurement; the measurement value will return when the state returns to normal.
- e.g., the ATMOS 41 detects an error when the sonic transducers are covered by water. The measurement value will return when the water covering the transducer clears.
65531 Sensor type not supported
The sensor type is not supported/recognized by the data logger; this could be because the logger firmware version is older/out of date. Update the logger firmware to the latest version.
- Check the firmware version to see if it is up-to-date available.
65532 Sensor communication error
There is communication between the sensor and the data logger, but this communication is corrupted. This could be from a broken sensor or a sensor with corrupted firmware.
- This could indicate the sensor is unplugged from the port, or the cable has been damaged. A field visit would be required. Check for damage to the cable.
- Using the "SCAN" function on your ZENTRA Utility (via laptop or phone), check if you receive any response from the sensor. If you do not, try plugging the sensor into another port. If no response, contact support.environment@metergroup.com with the Sensor specifics, Logger ID number, and any data showing the error.
65533 Sensor is reporting an error
There is no communication between the sensor and the data logger; this could be from an unplugged or broken sensor.
- This could indicate the sensor is unplugged from the port, or the cable has been damaged. A field visit would be required. Check for damage to the cable.
65533 Sensor is reporting an error
There is no communication between the sensor and the data logger; this could be from an unplugged or broken sensor.
- This could indicate the sensor is unplugged from the port, or the cable has been damaged. A field visit would be required. Check for damage to the cable.
65534 No response from sensor
The sensor and data logger are not communicating with each other; this could be due to an unplugged or broken sensor.
- This could indicate the sensor is unplugged from the port, or the cable has been damaged. A field visit would be required. Check for damage to the cable.
- Using the "SCAN" function on your ZENTRA Utility (via laptop or phone), check if you receive any response from the sensor. If you do not, try plugging the sensor into another port. If no response, contact support.environment@metergroup.com with the Sensor specifics, Logger ID number, and any data showing the error.
65535 Erased flash memory
Contact support.environemnt@metergroup.com with your logger ID number.
65536 Sensor value outside the expected range
The values are unexpected; this could be from a misconfigured port, corrupted firmware, or broken sensor.
- Check your sensors' valid range in the sensor specifications.
- If your sensor is Analog (ex, TEROS 10, VP4), make sure the port configuration is correct for your sensor
- Check the sensor physically and make sure it is properly plugged in, has no nicks or cramps on the cable (rodent damage)
- Use Case: Water potentials below -2,000 kPa exceed the detection limits of the TEROS 21 Gen1. When water potential is below -2,000 kPa, the TEROS 21 will report an error code (-9990), and an error message will appear (Sensor value is temporarily out of range).
65537 Invalid Value
The sensor is reporting that a processed value became NaN (not a number) or infinite.
65538 Alpha value too low
The sensor is reporting that alpha for NDVI is < 0.79 or > 2.0; for PRI < 0.02
65539 Radiance value(s) too low
The sensor is reporting that the measured value is too low to calculate the index. This could be because the radiance values are freq_1 < 0.0001 and freq_2 < 0.001.
65540 Calculation exceeds limits
An input value to the computation exceeds the acceptable limit of the model.
- Example 1: NDVI or PRI exceeds the limit (e.g., < -1 or > 1;
- Example 2: VPD is < 0 or > 10000.
65541 Calculation error
The sensor is reporting an unexpected process error for the calculated value.
65542 Value exceeds limits of the model
The values are unexpected; the values are too extreme to be considered reasonable; this could be from a misconfigured port, corrupted firmware, or broken sensor. This error code only appears on Em50 data loggers.
How did we do?
