METER TEROS 31 Soil Water Potential and Temperature sensor Installation Guide

METER TEROS 31 Soil Water Potential and Temperature sensor Installation Guide

SENSOR DESCRIPTION

The TEROS 31 Soil Water Potential and Temperature sensor is a precision tensiometer that measures water potential in the critical range (–85 kPa to +50 kPa) for water movement, critical range for plant response, and laboratory lysimeter experiments. With a ceramic diameter of only 5 mm, the TEROS 31 has all the advantages of small dimensions: little soil disturbance, selective pick-up, and fast response. Tensiometers will require periodic refilling when measurements go beyond the measuring range of the sensor.

For a more detailed description of how this sensor makes measurements, refer to the TEROS 31 User Manual.

APPLICATIONS

• Soil–water tension measurement
• Soil–water storage measurement
• Irrigation management
• Soil temperature measurement
• In-situ retention curves

ADVANTAGES

• Plug-and-play tensiometer
• Three-wire sensor interface: power, ground, and data
• Digital sensor communicates multiple measurements over a serial interface
• Low-input voltage requirements
• Low-power design supports battery-operated data loggers
• Supports SDI-12 or DDI serial communications protocols
• Modbus RTU or tensioLINK serial communications protocol supported

PURPOSE OF THIS GUIDE

METER provides the information in this integrator guide to help TEROS 31 customers establish communication between these sensors and their data acquisition equipment or field data loggers. Customers using data loggers that support SDI-12 sensor communications should consult the data logger user manual. METER sensors are fully integrated into the METER system of plug-and- play sensors, cellular-enabled data loggers, and data analysis software

COMPATIBLE FIRMWARE VERSIONS

This guide is compatible with firmware versions 1.00 or newer.

SPECIFICATIONS

MEASUREMENT SPECIFICATIONS

Water Potential

• Range –85 to +50 kPa (up to –150 kPa during boiling retardation)
• Resolution ±0.0012 kPa
• Accuracy ±0.15 kPa

Temperature

• Range –30 to +60 °C
• Resolution ±0.01 °C
• Accuracy ±0.5 °C

NOTE: If the sensor unit is not buried, measured temperature may diverge from soil temperature.

COMMUNICATION SPECIFICATIONS

Output

• DDI serial
• SDI-12 communication protocol
• TensioLINK communication protocol
• Modbus® RTU communication protocol

Data Logger Compatibility

METER ZL6 and EM60 data loggers or any data acquisition system capable of 3.6–28.0 VDC excitation and SDI-12, Modbus RTU, or tensioLINK communication.

PHYSICAL SPECIFICATIONS

Dimensions

• Width 23.5 cm (0.93 in)
• Depth 17.5 cm (0.69 in)
• Height 49.0 cm (1.93 in)

Shaft Diameter

• 5 cm (0.19 in)

Shaft Length

• 2, 5, 7, 10, 15, or 20 cm

Operating Temperature Range

• Minimum 0 °C
• Maximum 50 °C

Materials

• Ceramic Al2 O3 , bubble point 500 kPa
• Shaft PMMA
• Sensor Unit PMMA and TPE

Cable Length

• 1.5 m

Cable Diameter

• <3.0 mm (<0.12 in)

Connector Types

• 3.5-mm 4-pin stereo plug connector

Stereo Plug Connector Diameter

• 3.50 mm

Conductor Gauge

• 28 AWG drain wire

ELECTRICAL AND TIMING CHARACTERISTICS

Supply Voltage (VCC to GND)

• Minimum 3.6 V
• Typical 12.0 V
• Maximum 28.0 V

Digital Input Voltage (logic high)

• Minimum 1.6 V
• Typical 3.3 V
• Maximum 5.0 V

Digital Input Voltage (logic low)

• Minimum –0.3 V
• Typical 0.0 V
• Maximum 0.9 V

Digital Output Voltage (logic high)

• Minimum NA
• Typical 3.6 V
• Maximum NA

Power Line Slew Rate

• Minimum 1.0 V/ms
• Typical NA
• Maximum NA

Current Drain (during measurement)

• Minimum 18.0 mA

• Typical 25.0 mA

• Maximum 30.0 mA

Current Drain (while asleep)

• Minimum 0.03 mA
• Typical 0.05 mA
• Maximum 0.09 mA

Power Up Time (DDI serial)

• Minimum 125 ms
• Typical 130 ms
• Maximum 150 ms

Power Up Time (SDI-12)

• Minimum 125 ms
• Typical 130 ms
• Maximum 150 ms

Power Up Time (SDI-12, DDI disabled)

• Minimum 125 ms
• Typical 130 ms
• Maximum 150 ms

Measurement Duration

• Minimum 60 ms
• Typical 65 ms
• Maximum 70 ms

COMPLIANCE

• Manufactured under ISO 9001:2015
• EM ISO/IEC 17050:2010 (CE Mark)

EQUIVALENT CIRCUIT AND CONNECTION TYPES

Refer to Figure 2 and Figure 3 to connect the TEROS 31 to a data logger. Figure 2 provides a low-impedance variant of the recommended SDI-12 specification.

Figure 2 Equivalent circuit diagram

PIGTAIL CABLE

STEREO CABLE

Figure 3 Connection types

PRECAUTIONS

METER sensors are built to the highest standards, but misuse, improper protection, or improper installation may damage the sensor and possibly void the warranty. Before integrating sensors into a sensor network, follow the recommended installation instructions and implement safeguards to protect the sensor from damaging interference.

SURGE CONDITIONS

Sensors have built-in circuitry that protects them against common surge conditions. Installations in lightning-prone areas, however, require special precautions, especially when sensors are connected to a well-grounded third- party logger.

Read the application note Lightning surge and grounding practices on the METER website for more information.

POWER AND GROUNDING

Ensure there is sufficient power to simultaneously support the maximum sensor current drain for all the sensors on the bus. The sensor protection circuitry may be insufficient if the data logger is improperly powered or grounded. Refer to the data logger installation instructions. Improper grounding may affect the sensor output as well as sensor performance.

Read the application note Lightning surge and grounding practices on the METER website for more information.

CABLES

Improperly protected cables can lead to severed cables or disconnected sensors. Cabling issues can be caused by many factors, including rodent damage, driving over sensor cables, tripping over the cable, not leaving enough cable slack during installation, or poor sensor wiring connections. To relieve strain on the connections and prevent loose cabling from being inadvertently snagged, gather and secure the cable travelling between the TEROS 31 and the data acquisition device to the mounting mast in one or more places. Install cables in conduit or plastic cladding when near the ground to avoid rodent damage. Tie excess cable to the data logger mast to ensure cable weight does not cause sensor to unplug.

SENSOR COMMUNICATIONS

METER digital sensors feature a serial interface with shared receive and transmit signals for communicating sensor measurements on the data wire (Figure 3). The sensor supports four different protocols: SDI-12 and DDI serial one-wire, as well as tensioLINK and Modbus over RS-485 two-wire. The sensor automatically detects the interface and protocol which is being used. Each protocol has implementation advantages and challenges. Please contact Customer Support if the protocol choice for the desired application is not obvious.

SDI-12 INTRODUCTION

SDI-12 is a standards-based protocol for interfacing sensors to data loggers and data acquisition equipment.

Multiple sensors with unique addresses can share a common 3-wire bus (power, ground, and data). Two-way communication between the sensor and logger is possible by sharing the data line for transmit and receive as defined by the standard. Sensor measurements are triggered by protocol command. The SDI-12 protocol requires a unique alphanumeric sensor address for each sensor on the bus so that a data logger can send commands to and receive readings from specific sensors. Download the SDI-12 Specification v1.3 to learn more about the SDI-12 protocol.

DDI SERIAL INTRODUCTION

The DDI serial protocol is the method used by the METER data loggers for collecting data from the sensor. This protocol uses the data line configured to transmit data from the sensor to the receiver only (simplex). Typically, the receive side is a microprocessor UART or a general-purpose I/O pin using a bitbang method to receive data. Sensor measurements are triggered by applying power to the sensor.

TENSIOLINK RS485 INTRODUCTION

The tensioLINK RS485 protocol is a robust bus connection to connect multiple devices to one bus. It is capable of using very long cable distances under harsh environments. tensioLINK is a proprietary protocol that communicates over the RS485 interface and is used to read data and configure features of the device. It is fast and reliable. METER provides a PC-USB serial interface to communicate directly with the sensor and read data. Please contact Customer Support for more information.

MODBUS RTU RS485 INTRODUCTION

The Modbus RTU RS485 protocol is a very common protocol used by PLCs or data loggers to communicate with devices. For more information about the implementation of Modbus RTU in the TEROS 31, please contact Customer Support.

INTERFACING THE SENSOR TO A COMPUTER

The serial signals and protocols supported by the sensor require some type of interface hardware to be compatible with the serial port found on most computers (or USB-to-serial adapters). There are several SDI-12 interface adapters available in the marketplace; however, METER has not tested any of these interfaces and cannot make a recommendation as to which adapters work with METER sensors. METER data loggers and the ZSC handheld device can operate as a computer-to-sensor interface for making on-demand sensor measurements.

TEROS 31 can also be configured and measured via tensioLINK using METER software tensioVIEW. To connect a TEROS 31 to a computer a tensioLINK USB converter and a suitable adapter cable is necessary. For more information, please contact Customer Support.

METER SDI-12 IMPLEMENTATION

METER sensors use a low-impedance variant of the SDI-12 standard sensor circuit (Figure 2). During the power-up time, sensors output some sensor diagnostic information and should not be communicated with until the power-up time has passed. After the power up time, the sensors are fully compatible with all commands listed in the SDI-12 Specification v1.3 except for the continuous measurement commands (aR0–aR9 and aRC0–aRC9). M, R, and C command implementations are found on pages 7–8. The aR3 and aR4 commands are used by METER systems and as a result uses a space delimiter, instead of a sign delimiter as required by the SDI-12 standard.

Out of the factory, all METER sensors start with SDI-12 address 0 and print out the DDI serial startup string during the power-up time. This can be interpreted by non-METER SDI-12 sensors as a pseudo-break condition followed by a random series of bits.

The TEROS 31 will omit the DDI serial startup string when the SDI-12 address is nonzero. Changing the address to a nonzero address is recommended for this reason.

SENSOR BUS CONSIDERATIONS

SDI-12 sensor buses require regular checking, sensor upkeep, and sensor troubleshooting. If one sensor goes down, that may take down the whole bus even if the remaining sensors are functioning normally. Power cycling the SDI-12 bus when a sensor is failing is acceptable, but METER does not recommend scheduling power cycling events on an SDI-12 bus more than once or twice per day. Many factors influence the effectiveness of the bus configuration. Visit metergroup.com for articles and virtual seminars containing more information.

SDI-12 CONFIGURATION

Table 1 lists the SDI-12 communication configuration

Baud Rate

| 1,200
---|---
Start Bits|

1

Data Bits

| 7 (LSB first)
Parity Bits|

1 (even)

Stop Bits

| 1
Logic|

Inverted (active low)

Table 1 SDI-12 communication configuration

SDI-12 TIMING

All SDI-12 commands and responses must adhere to the format in Figure 4 on the data line. Both the command and response are preceded by an address and terminated by a carriage return and line feed combination () and follow the timing shown in Figure 5.

Figure 4 Example SDI-12 transmission of the character 1 (0x31)

Figure 5 Example data logger and sensor communication

COMMON SDI-12 COMMANDS

This section includes tables of common SDI-12 commands that are often used in an SDI-12 system and the corresponding responses from METER sensors.

IDENTIFICATION COMMAND (aI!)

The Identification command can be used to obtain a variety of detailed information about the connected sensor. An example of the command and response is shown in Example 1, where the command is in bold and the response follows the command.

Example 1 1I!113METER␣␣␣TER31␣T31-00001

Parameter

| Fixed Character Length| Description
---|---|---
1I!| 3|

Data logger command.
Request to the sensor for information from sensor address 1.

1

| 1| Sensor address.
Prepended on all responses, this indicates which sensor on the bus is returning the following information.
13| 2|

Indicates that the target sensor supports SDI-12 Specification v1.3.

METER␣␣␣

| 8| Vendor identification string.
(METER and three spaces ␣␣␣ for all METER sensors)
TER31␣| 6|

Sensor model string.
This string is specific to the sensor type. For the TEROS 31, the string is TER31.

100

| 3| Sensor version.
This number divided by 100 is the METER sensor version (e.g., 100 is version 1.00).
T31-00001| ≤13, variable|

Sensor serial number.
This is a variable length field. It may be omitted for older sensors.

CHANGE ADDRESS COMMAND (aAB!)
The Change Address command is used to change the sensor address to a new address. All other commands support the wildcard character as the target sensor address except for this command. All METER sensors have a default address of 0 (zero) out of the factory. Supported addresses are alphanumeric (i.e., a–z, A–Z, and
0–9). An example output from a METER sensor is shown in Example 2, where the command is in bold and the response follows the command.

Example 2 1A0!0

Request to the sensor to change its address from 1 to a new address of 0.
0| 1| New sensor address.
For all subsequent commands, this new address will be used by the target sensor.

ADDRESS QUERY COMMAND (?!)

While disconnected from a bus, the Address Query command can be used to determine which sensors are currently being communicated with. Sending this command over a bus will cause a bus contention where all the sensors will respond simultaneously and corrupt the data line. This command is helpful when trying to isolate a failed sensor. Example 3 shows an example of the command and response, where the command is in bold and the response follows the command. The question mark (?) is a wildcard character that can be used in place of the address with any command except the Change Address command.

Example 3 ?!0

Request for a response from any sensor listening on the data line.
0| 1| Sensor address.
Returns the sensor address to the currently connected sensor.

COMMAND IMPLEMENTATION

The following tables list the relevant Measurement (M), Continuous (R), and Concurrent (C) commands and subsequent Data (D) commands, when necessary

MEASUREMENT COMMANDS IMPLEMENTATION
Measurement (M) commands are sent to a single sensor on the SDI-12 bus and require that subsequent Data (D) commands are sent to that sensor to retrieve the sensor output data before initiating communication with another sensor on the bus.

Please refer to Table 2 and for an explanation of the command sequence and to Table 7 for an explanation of response parameters.

Table 2 aM! command sequence

This command reports average, accumulated, or maximum values.

NOTE: The measurement and corresponding data commands are intended to be used back to back. After a measurement command is processed by the sensor, a service request a is sent from the sensor signaling the measurement is ready. Either wait until ttt seconds have passed or wait until the service request is received before sending the data commands. See the SDI-12 Specifications v1.3 document for more information.

CONCURRENT MEASUREMENT COMMANDS IMPLEMENTATION
Concurrent Measurement (C) commands are typically used with sensors connected to a bus. C commands for this sensor deviate from the standard C command implementation. First, send the C command, wait the specified amount of time detailed in the C command response, and then use D commands to read its response prior to communicating with another sensor.

Please refer to Table 3 for an explanation of the command sequence and to Table 7 for an explanation of response parameters.

Table 3 aC! measurement command sequence

This command reports instantaneous values.

CONTINUOUS MEASUREMENT COMMANDS IMPLEMENTATION
Continuous Measurement (R) commands trigger a sensor measurement and return the data automatically after the readings are completed without needing to send a D command.

The aR4! command must be used at intervals of 2 s or greater for the response to be returned within 15.0 ms as defined in the SDI-12 standard.

aR0!, aR3!, and aR4! return more characters in their responses than the 75-character limitation called out in the SDI-12 Specification v1.3. It is recommended to use a buffer that can store at least 116 characters.

Please refer to Table 4 through Table 6 for an explanation of the command sequence and see Table 7 for an explanation of response parameters.

Table 4 aR0! measurement command sequence

This command reports average, accumulated, or maximum values.

NOTE: This command does not adhere to the SDI-12 response timing. See METER SDI-12 Implementation for more information.

Table 5 aR3! measurement command sequence

This command reports average, accumulated, or maximum values.

aR3!| a±±+
---|---

NOTE: This command does not adhere to the SDI-12 response format or timing. See METER SDI-12 Implementation for more information.

Table 6 aR4! measurement command sequence

This command reports average, accumulated, or maximum values.

aR4!| a±±+
---|---

NOTE: This command does not adhere to the SDI-12 response format or timing. See METER SDI-12 Implementation for more information.

PARAMETERS

Table 7 lists the parameters, unit measurement, and a description of the parameters returned in command responses for TEROS 31.

Table 7 Parameter Descriptions

2. ttt| s| Maximum time measurement will take (fixed width of 3) | —| Tab character | —| Carriage return character | —| Line feed character | —| ASCII character denoting the sensor type For TEROS 31, the character is ; | —| METER serial checksum | —| METER 6-bit CRC

DDI SERIAL COMMUNICATION

The DDI serial communications protocol is ideal for systems that have dedicated serial signaling lines for each sensor or use a multiplexer to handle multiple sensors. The serial communications are compatible with many TTL serial implementations that support active-high logic levels using 0–3.6 V signal levels. When the sensor
is first powered, it automatically makes measurements of the integrated transducers then outputs a response over the data line. Systems using this protocol control the sensor excitation to initiate data transfers from the sensor. This protocol is subject to change as METER improves and expands the line of digital sensors and data loggers.

The TEROS 31 will omit the DDI serial startup string when the SDI-12 address is nonzero.

NOTE: Out of the factory, all METER sensors start with SDI-12 address 0 and print out the startup string when power cycled.

DDI SERIAL TIMING

Table 8 lists the DDI serial communication configuration

Table 8 DDI serial communication configuration

Baud Rate

| 1,200
---|---
Start Bits|

1

Data Bits

| 8 (LSB first)
Parity Bits|

0 (none)

Stop Bits

| 1
Logic|

Standard (active high)

At power up, the sensor will pull the data line high within 100 ms to indicate that the sensor is taking a reading (Figure 6). When the reading is complete, the sensor begins sending the serial signal out the data line adhering to the format shown in Figure 7. Once the data is transmitted, the sensor goes into SDI-12 communication
mode. To get another serial signal, the sensor must be power cycled.

NOTE: Sometimes the signaling from the sensor can confuse typical microprocessor UARTs. The sensor holds the data line low while taking measurements. The sensor raises the line high to signal the logger that it will send a measurement. Then the sensor may take some additional measurements before starting to clock out the first data byte starting with a typical start bit (low). Once the first start bit is sent, typical serial timing is valid; however, the signal transitions  before this point are not serial signaling and may be misinterpreted by the UART.

Figure 6 Data line DDI serial timing

Figure 7 Example DDI serial transmission of the character 9 (0x39)

DDI SERIAL RESPONSE

Table 9 details the DDI serial response.

Table 9 DDI serial response

COMMAND    RESPONSE

NA|

NOTE: There is no actual command. The response is returned automatically upon power up.

DDI SERIAL CHECKSUM

These checksums are used in the continuous commands R3 and R4 as well as the DDI serial response. The legacy checksum is computed from the start of the transmission to the sensor identification character, excluding the sensor address.

Example input is 0]M and the resulting checksum output is x.

The more robust CRC6 utilizes the CRC-6-CDMA2000-A polynomial with the value 48 added to the results to make this a printable character and is computed from the start of the transmission to the legacy checksum character, excluding the sensor address.

CRC6 checksum example input is 1.222 23.4 92.81{/6 and the resulting checksum output is x.

CUSTOMER SUPPORT

NORTH AMERICA
Customer service representatives are available for questions, problems, or feedback Monday through Friday, 7:00 am to 5:00 pm Pacific time.

Email: support.environment@metergroup.com
sales.environment@metergroup.com
Phone: +1.509.332.5600
Fax: +1.509.332.5158
Website: metergroup.com

EUROPE
Customer service representatives are available for questions, problems, or feedback Monday through Friday, 8:00 to 17:00 Central European time.

Email: support.europe@metergroup.com
sales.europe@metergroup.com
Phone: +49 89 12 66 52 0
Fax: +49 89 12 66 52 20
Website: metergroup.de

If contacting METER by email, please include the following information:

• Name
• Address
• Phone number
• Email address
• Instrument serial number
• Description of problem

NOTE: For products purchased through a distributor, please contact the distributor directly for assistance.

REVISION HISTORY

The following table lists document revisions

References

• METER Group
• METER Group

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>