METER ES-2 INTEGRATOR SENSOR User Guide

ES-2 INTEGRATOR GUIDE

SENSOR DESCRIPTION

The ES-2 sensor is an accurate tool for monitoring electrical conductivity and temperature in a pipe or tank. The ES-2 measures temperature using an onboard thermistor and electrical conductivity using a stainless steel electrode array. The integrated 4-probe electrical conductivity transducer accurately senses EC up to 120 dS/m. The electronic circuitry is encapsulated in a marine-grade epoxy to protect the sensor in corrosive environments.

For a more detailed description of how this sensor makes measurements, refer to the ES-2 User Manual.

APPLICATIONS

• Tank monitoring
• Pipe monitoring
• Salt management

ADVANTAGES

• Three-wire sensor interface: power, ground, and data
• Digital sensor communicates multiple measurements over a serial interface
• Robust thermistor for accurate temperature measurements
• Low-input voltage requirements
• Low-power design supports battery-operated data loggers
• Robust epoxy encapsulation resists corrosive environments
• Supports SDI-12 or DDI serial communications protocols
• Modern design optimized for low-cost sensing

Figure 1 ES-2 sensor

PURPOSE OF THIS GUIDE

METER provides the information in this integrator guide to help ES-2 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 3.89 or newer.

METER Group, Inc. USA
2365 NE Hopkins Court, Pullman, WA 99163
T +1.509.332.2756 F +1.509.332.5158
E info@metergroup.com W metergroup.com

SPECIFICATIONS

MEASUREMENT SPECIFICATIONS

Temperature

Range| -40 to 60 °C
Resolution| 0.1 °C
Accuracy| ±1 °C
Bulk EC
Range| 0–120 dS/m
Resolution| 0.001 dS/m
Accuracy| ±0.01 dS/m or ±10% (whichever is greater)

COMMUNICATION SPECIFICATIONS

Output

DDI serial or
SDI-12 communication protocol
Data Logger Compatibility
METER ZL6 data loggers and any data acquisition system capable of 3.6- to 15-VDC power and serial or SDI-12 communication

PHYSICAL SPECIFICATIONS

Dimensions

Length| 10.9 cm (4.3 in)
Diameter| 2.4 cm (0.95 in)
Thread| 1/2-in National Pipe Thread
Operating Temperature Range
Minimum| –40 °C
Maximum| 60 °C
NOTE:  Sensors may be used at higher temperatures under certain conditions; contact Customer Support for assistance.
In-Line Pipe Connector Type
1-in Tee socket pipe fitting
Cable Length
5 m (standard)
75 m (maximum custom cable length)NOTE:  Contact Customer Support if a nonstandard cable length is needed.
Connector Types
3.5-mm stereo plug connector or stripped and tinned wires

ELECTRICAL AND TIMING CHARACTERISTICS

Supply Voltage (VCC to GND)

Minimum| 3.6 V
Typical| NA
Maximum| 15.0 V
Digital Input Voltage (logic high)
Minimum| 2.8 V
Typical| 3.6 V
Maximum| 5.0 V
Digital Input Voltage (logic low)
Minimum| -0.3 V
Typical| 0.0 V
Maximum| 0.8 V
Digital Output Voltage (logic high)
Minimum| NA
Typical| 3.6 V
Maximum| NA
Power Up Time (SDI-12)
Minimum| 100 ms
Typical| 200 ms
Maximum| 250 ms
Power Up Time (SDI-12, DDI disabled)
Minimum| NA
Typical| 125 ms
Maximum| NA
Power Line Slew Rate
Minimum| 1.0 V/ms
Typical| NA
Maximum| NA
Current Drain (during measurement)
Minimum| 20 mA
Typical| 20 mA
Maximum| 28 mA
Current Drain (while asleep)
Minimum| NA
Typical| 0.03 mA
Maximum| NA
Power Up Time (DDI serial)
Minimum| NA
Typical| NA
Maximum| 100 ms
Measurement Duration
Minimum| NA
Typical| 25 ms
Maximum| 50 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 ES-2 to a data logger. Figure 2 provides a low-impedance variant of the recommended SDI-12 specification.

Figure 2 Equivalent circuit diagram

PIGTAIL CABLE

1 Power (brown)
2 Ground (bare)
3 Digital communication (orange)

STEREO CABLE

1 Ground
2 Digital communication
3 Power

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 ATMOS 41 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 two different protocols: SDI-12 and DDI serial. 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.

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 ProCheck hand-held device can operate as a computer-to-sensor interface for making on-demand sensor measurements. 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 (aR3 and aRC3). M, R, and C command implementations are found on page 7. The aR3 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 ES-2 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.

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)

*Maximum time is dependent upon the amount of data returned for the command sent.

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!113DECAGON␣ES-2␣␣389631800001

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.
DECAGON␣| 8| Vendor identification string.
(DECAGON and one space␣ )
ES-2␣␣| 6| Sensor model string.
This string is specific to the sensor type.
For the ES-2, the string is ES-2.
389| 3| Sensor version.
This number divided by 100 is the METER sensor version
(e.g., 389 is version 3.89).
631800001| ≤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 1A 0!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 6 for an explanation of response parameters.

Table 2 aM! command sequence

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 6 for an explanation of response parameters.

Table 3 aC! measurement command sequence

NOTE: Please see the SDI-12 Specifications v1.3 document for more information.

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.

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

Table 4 aR0! measurement command sequence

Table 5 aR3! measurement command sequence

NOTE: This command does not adhere to the SDI-12 response format or timing. See METER SDI-12 Implementation for more information. The values in this command are space delimited. As such, a + sign is not assigned between values and a ­ sign is only present if the value is negative.

PARAMETERS

Table 6 lists the parameters, unit measurement, and a description of the parameters returned in command responses for ES-2.

Table 6 Parameter Descriptions

2. ttt| s| Maximum time measurement will take (fixed width of 3) | —| Tab character | —| Carriage return character | —| Line feed character | µS/cm| Electrical conductivity | °C| Temperature | —| ASCII character denoting the sensor type

For ES-2, the character is q