METER BARO Module

BARO INTEGRATOR GUIDE

DESSCRIPTION SENSOR

The BARO Module is a precise barometer to compensate for matric potential measurements of TEROS 31 and TEROS 32 tensiometers. The BARO Module can be used as a standalone sensor to compensate one or more tensiometers at a measuring site, or as a digital/analog converter to compensate a connected TEROS 31 or TEROS 32 value and convert the SDI-12 signal into an analog voltage output (only 8-pin version). The BARO Module and TEROS 32 combination can be used as a T8 tensiometer replacement. For a more detailed description of how this sensor makes measurements, refer to the BARO Module User Manual.

APPLICAZIONI

• Barometric pressure measurement
• Barometric compensation of matric potential measurements
• Digital/analog converter for directly connected TEROS 31 and TEROS 32 tensiometers
• Appropriate for non-METER data loggers to connect TEROS 31 and TEROS 32

AVVANUTAGES

• U sensoru digitale cumunica parechje misurazioni nantu à una interfaccia seriale
• Volu à pocu ingressutage esigenze
• U disignu di bassa putenza supporta i registratori di dati operati da batterie
• SDI-12, Modbus RTU or tensio LINK serial communications protocol supported
• Analog output supported (only 8-pin version)

SPECIFICATION

SPECIFICAZIONI DI MISURA
Pressione barometrica
Gamma	+ 65 kPa to +105 kPa
Risoluzione	± 0.0012 kPa
Accuratezza	± 0.05kPa
Temperature
Gamma	-30 à + 60 °C
Risoluzione	± 0.01 °C
Accuratezza	± 0.5 °C
SPECIFICAZIONI DI COMMUNICAZIONE
Output
Analog Output (8-pin connector only)0 to 2,000 mV (default)0 to 1,000 mV (configurable with tensio VIEW)
Digital OutputSDI-12 communications protocol tensio LINK communication protocol Modbus RTU communication protocol
Cumpatibilità di Data Logger
Analog Output Any data acquisition system capable of switched 3.6- to 28-VDC excitation and single-ended or differential voltage measurement at a greater than or equal to 12-bit resolution.
Digital Output Any data acquisition system capable of 3.6- to 28-VDC excitation and RS-485 Modbus or SDI-12 communication.
SPECIFICHE FISICHE
Dimensioni
Lunghezza	80 mm (3.15 in)
Larghezza	29 mm (1.14 in)
Altezza	30 mm (1.18 in)
Lunghezza di u cable
1.5 m (standard)NOTE: Contact Customer Support if a nonstandard cable length is needed.
Tipi di cunnessu
4-pin and 8-pin M12 plug connector or stripped and tinned wires
CONFORMITÀ
EM ISO/IEC 17050:2010 (Marcu CE)

CIRCUIT EQUIVALENT E TIPI DI CONNESSIONE
Refer to Figure 2 to connect the BARO Module to a data logger. Figure 2 provides a low-impedance variant of the recommended SDI-12 specification.

BARO MODULE INTEGRATOR GUIDE

PRECAUZIONI

I sensori METER sò custruiti à i più alti standard, ma l'usu impropriu, a prutezzione impropria o l'installazione impropria pò dannà u sensoru è possibbilmente annullà a garanzia. Prima di integrà i sensori in una rete di sensori, seguite l'istruzzioni d'installazione cunsigliate è implementate salvaguardi per prutege u sensoru da interferenze dannusu.

CUMUNICAZIONI SENSORI
METER digital sensors feature a serial interface with shared receive and transmit signals for communicating sensor measurements on the data wire. The sensor supports SDI-12, tensio LINK, 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 METER Customer Support if the protocol choice for the desired application is not obvious.

• SDI-12 INTRODUZIONE
  SDI-12 hè un protocolu basatu in standard per l'interfaccia di i sensori à i registratori di dati è l'equipaggiu di acquisizione di dati. Sensori multipli cù indirizzi unichi ponu sparte un busu cumuni di 3 fili (putenza, terra è dati). A cumunicazione bidirezionale trà u sensoru è u logger hè pussibule sparte a linea di dati per trasmette è riceve cum'è definitu da u standard. E misurazioni di i sensori sò attivate da u cumandamentu di u protocolu. U protocolu SDI-12 richiede un indirizzu di sensoru alfanumericu unicu per ogni sensoru in u bus in modu chì un logger di dati pò mandà cumandamenti è riceve letture da sensori specifichi.
  Scaricate l'SDI-12 Specification v1.3 per sapè più nantu à u protocolu SDI-12.
• RS-485 INTRODUCTION
  RS-485 is a robust physical bus connection to connect multiple devices to one bus. It is capable of using very long cable distances under harsh environments. Instead of SDI-12, RS-485 uses two dedicated wires for the data signal. This allows the use of longer cables and is more insensitive to interference from outside sources, since the signal is related to the different wires, and supply currents do not influence the data signal. See Wikipedia for more details on RS-485.
• TENSIOLINK RS-485 INTRODUCTION
  tensioLINK is a fast, reliable, proprietary serial communications protocol that communicates over the RS-485 interface. This protocol is used to read out data and configure features of the device. METER provides a tensioLINK PC USB converter and software to communicate directly with the sensor, read out data, and update the firmware. Please contact Customer Support for more information about tensioLINK.
• MODBUS RTU RS-485 INTRODUCTION
  Modbus RTU is a common serial communications protocol used by Programmable Logic Controllers (PLCs) or data loggers to communicate with all kinds of digital devices. The communication works over the physical RS-485 connection. The combination of RS-485 for the physical connection and Modbus as serial communications protocol allows fast and reliable data transfer for a high number of sensors connected to one serial bus wire. Use the following links for more Modbus information: Wikipedia and modbus.org.
• INTERFACE U SENSORE À UN 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.
  The BARO Module can also be configured and measured via tensioLINK using METER software tensioVIEW, available to download at meter.ly/software. To connect a BARO Module to a computer a tensioLINK USB converter and a suitable adapter cable is necessary.
• METER SDI-12 IMPLEMENTATION
  If a BARO Module is connected between a TEROS 31 or 32 tensiometer, both the barometric air pressure and the absolute pressure of the TEROS tensiometer can be read out via Modbus. The compensated matrix potential can be read out via Modbus as well.
  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 8–9. Out of the factory, all METER sensors start with SDI-12 address 0 .
• CONSIDERAZIONI SENSOR BUS
  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. METER SDI-12 sensors can be power-cycled and read on the desired measurement interval or powered continuously and commands sent when a measurement is desired based on specified communication timing. Many factors influence the effectiveness of the bus configuration. Visit metergroup.com per articuli è seminarii virtuali chì cuntenenu più infurmazione.

CONFIGURAZIONE SDI-12

Table 1 lists the SDI-12 communication configuration.

Table 1      Cunfigurazione di cumunicazione SDI-12
Baud Rate	1,200
Start Bits	1
Bits di dati	7 (LSB prima)
Bit di parità	1 (ancu)
Stop Bits	1
Lògica	Invertitu (attivu bassu)

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

COMMANDI SDI-12 COMUNI
Questa sezione include tavule di cumandamenti SDI-12 cumuni chì sò spessu usati in un sistema SDI-12 è e risposti currispondenti da i sensori METER.

COMANDU DI IDENTIFICAZIONE (aI!)
U cumandamentu di Identificazione pò esse usatu per ottene una varietà di informazioni dettagliate nantu à u sensoru cunnessu. Un example di u cumandamentu è a risposta hè mostrata in Example 1, induve u cumandamentu hè in grassu è a risposta seguita u cumandamentu.

Example 1 1I!113METER␣ ␣ ␣BARO␣

Parametru	Carattere fissu  Lunghezza	Descrizzione
1 eiu !	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	Indica chì u sensoru di destinazione supporta a specificazione SDI-12 v1.3.
METER ␣ ␣ ␣	8	Vendor identification string.( METER and three spaces  ␣ ␣ ␣ for all METER sensors)
BARO␣	6	Sensor model string.This string is specific to the sensor type. For the BARO, the string is BARO .
100	3	Sensor version.This number divided by 100 is the METER sensor version (e.g., 100 is version 1.00).
BARO-00001	≤13,variable	U numeru di serie di u sensoru. Questu hè un campu di lunghezza variabile. Pò esse omessi per i sensori più antichi.

CAMBIARE L'INDIRIZZE 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 , and 0 – 9 ). An exampL'output da un sensor METER hè mostratu in Esample 2, induve u cumandamentu hè in grassu è a risposta seguita u cumandamentu.

Example 2 1A0!0

Parametru	Carattere fissu  Lunghezza	Descrizzione
1A0!	4	Data logger command. 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.

IMPLEMENTATION COMMAND
I seguenti tabelle listanu i cumandamenti pertinenti di Misurazione (M), Continuu (R) è Concurrent (C) è cumandamenti di Dati (D) successivi, quandu hè necessariu.

IMPLEMENTAZIONE DI COMANDI DI MISURA
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 5 for an explanation of response parameters.

Tabella 2 am! sequenza di cumandamenti

Cumanda	Risposta
Stu cumandamentu rappurta valori mediu, accumulatu, o massimi.
aM!	attn
aD0!	a± ± +
Cumenti	When a slave TEROS tensiometer is connected, <Press> hold the barometric compensated tensiometer output. If the BARO module is used in standalone <Press> returns the current barometric pressure.
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 <CR><LF> is sent from the sensor signaling the measurement is ready. Either wait until   seconds have passed or wait until the service request is received before sending the data commands. See the SDI-12 Specifications v1.3

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 <CR><LF> 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.

IMPLEMENTAZIONE DI COMANDI CONCURRENT MEASUREMENT
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 5 for an explanation of response parameters.

	Table 3      aC! measurement command sequence
Cumanda	Risposta
Stu cumandamentu riporta i valori istantanei.
aC!	attnn
aD0!	a± ± +
NOTE: The measurement and corresponding data commands are intended to be used back to back. After a measurement commanc is pro- cessed by the sensor, a service request a<CR><LF> is sent from the sensor signaling the measurement is ready. Either wait until ttt sec- onds have passed or wait until the service request is received before sending the data commands. Please see the SDI-12 Specifications v1.3 document for more information.

NOTE: The measurement and corresponding data commands are intended to be used back to back. After a measurement commanc is pro-cessed by the sensor, a service request a<CR><LF> is sent from the sensor signaling the measurement is ready. Either wait until ttt sec-onds have passed or wait until the service request is received before sending the data commands. Please see the SDI-12 Specifications v1.3 document for more information.

IMPLEMENTAZIONE DI COMANDI DI MISURA CONTINUA
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. aR0! returns more characters in its response 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 for an explanation of the command sequence and see Table 5 for an explanation of response parameters.

	Table 4      aR0! measurement command sequence
Cumanda	Risposta
Stu cumandamentu rappurta valori mediu, accumulatu, o massimi.
aR0!	a± ± +
NOTE: This command does not adhere to the SDI-12 response timing. See METER SDI-12 Implementation for more information.

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

PARAMETRI
Table 5 lists the parameters, unit measurement, and a description of the parameters returned in command responses for the BARO Module.

		Table 5      Descrizzione di i paràmetri
Parametru	Unità	Descrizzione
±	—	Signu pusitivu o negativu chì denota u signu di u prossimu valore
a	—	Indirizzu SDI-12
n	—	Numero di misure (larghezza fissa di 1)
nn	—	Numeru di misurazioni cù u cero iniziale se necessariu (larghezza fissa di 2)
ttt	s	A misurazione di u tempu massimu pigliarà (larghezza fissa di 3)
	—	Carattere di tabulazione
	—	Carattere di ritornu di u carru
	—	Carattere di alimentazione di linea
	—	ASCII character denoting the sensor type For BARO Module, the character is ;
	—	Checksum seriale METER
	—	METER 6-bit CRC

METER MODBUS RTU SERIAL IMPLEMENTATION
Modbus over Serial Line is specified in two versions – ASCII and RTU. BARO Modules communicate using RTU mode exclusively. The following explanation is always related to RTU. Table 6 lists the Modbus RTU communication and configuration.

Table 6      Modbus communication characters
Baud Rate (bps)	9,600 bps
Start Bits	1
Bits di dati	8 (LSB prima)
Bit di parità	0 (nimu)
Stop Bits	1
Lògica	Standard (attivu altu)

Figure 11 shows a message in RTU format. The size of the data determines the length of the message. The format of each byte in the message has 10 bits, including Start and Stop Bit. Each byte is sent from left to right: Least Significant Bit (LSB) to Most Significant Bit (MBS). If no parity is implemented, an additional stop bit is transmitted to fill out the character frame to a full 11-bit asynchronous character.

The Modbus application layer implements a set of standard Function codes divided into three categories: Public, User-defined, and Reserved. Well-defined public function codes for BARO Modules are documented in the Modbus Organization, Inc. (modbus.org) community.

For a reliable interaction between the BARO Module and a Modbus Master, a minimum 50ms delay is required between every Modbus command sent on the RS-485 bus. An additional timeout is needed for every Modbus query; this timeout is device-specific and depends on the quantity of the polled registers. Generally, 100ms will work fine for most of the BARO Module.

SUPPORTED MODBUS FUNCTIONS

Table 7 Function Definitions

Funzione Codice	Azzione	Descrizzione
01	Read coil/port status	Reads the on/off status of discrete output(s) in the ModBusSlave
02	Leghjite u statu di input	Reads the on/off status of discrete input(s) in the ModBusSlave
03	Leghjite i registri di holding	Reads the binary contents of holding register(s) in the ModBusSlave
04	Leghjite i registri di input	Reads the binary contents of input register(s) in the ModBusSlave
05	Force single coil/port	Forces a single coil/port in the ModBusSlave to either on or off
06	Scrivite un registru unicu	Writes a value into a holding register in the ModBusSlave
15	Force multiple coils/ports	Forces multiple coils/ports in the ModBusSlave to either on or off
16	Scrivite parechji registri	Writes values into a series of holding registers in the ModBusSlave

DATA REPRESENTATION AND REGISTER TABLES
Data values (setpoint values, parameters, sensor-specific measurement values, etc.) sent to and from the BARO Module use 16-bit and 32-bit holding (or input) registers with a 4-digit address notation. The address spaces are virtually distributed in different blocks for each data type. This is an approach to the Modbus Enron implementation. Table 8 shows the four main tables used by the BARO Module with their respective access rights. Table 9 describes the sub-blocks for each different data type representation.

Please note that some Modbus dataloggers use addressing with a +1 offset. This sometimes causes confusion and is based on a Modbus specification void. If there are problems in implementing your Modbus program on the datalogger always try testing different register offsets and data types. Using a known value, like temperature, where it’s known what value to expect is a good practice to start testing.

Table 8      Modbus Primary Tables
Numero di Registru	Tipu di table	Accessu	Descrizzione
1xxx	Bobine di output discrete	Leghjite / Scrive	on/off status or setup flags for the sensor
2xxx	Cuntatti di input discreti	Leghjite	sensor status flags
3xxx	Registri di input analogicu	Leghjite	numerical input variables from the sensor (actual sensor measurements)
4xxx	Analog Output Holding Registers	Leghjite / Scrive	numerical output variables for the sensor (parameters, setpoint values, calibrations etc.)

Per esample, register 3001 is the first analog input register (first data address for the input registers). The numeric value stored here would be a 16-bit unsigned integer-type variable that represents the first sensor measurement parameter (pressure value). The same measurement parameter (pressure value) could be read at register 3201, but this time as a 32-bit floating-point value with a Big-Endian format. If the Modbus Master (Datalogger or a PLC) supports only 32-bit float-values with a Little-Endian format, then one could read the same measurement parameter (same pressure value) at register 3301. The Virtual Sub-Blocks are meant to simplify the user’s effort in programming the Modbus query of the sensors.

Table 9      Modbus Virtual Sub-Blocks
Numero di Registru	Accessu	Taglia	Sub-Table Dati Tipu
X001-X099	Leghjite / Scrive	16 bit	interu firmatu
X101-X199	Leghjite / Scrive	16 bit	interu senza signu
X201-X299	Leghjite / Scrive	32 bit	float Big-Endian format
X301-X399	Leghjite / Scrive	32 bit	float Little-Endian format

REGISTER MAPPING

	Table 10      Registri di Holding
41000 (41001 *)	Indirizzu Modbus Slave
Descrizzione detallata	Read or update the sensor’s modbus address
Tipu di dati	Numeru interu micca firmatu
Gamma permessa	1 - 247
Unità	–
Cumenti	Updated slave address will be stored in the sensor’s nonvolatile memory

	Table 11      BARO Module Input Registers
32000 (32001 *)	Soil Water Potential
Descrizzione detallata	Compensated tension value from tensiometer
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	-200 à +200
Unità	kPa
Cumenti	Tensiometer needs to be connected as slave
32001 (32002 *)	Temperatura di u Terrenu
Descrizzione detallata	High accuracy on board temperature measurement
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	-30 à +60
Unità	degC
Cumenti	Tensiometer needs to be connected as slave
32002 (32003 *)	Sensor Supply Voltage
Descrizzione detallata	On board supply voltage misurazione
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	-10 à +60
Unità	Volti
Cumenti	–
32003 (32004 *)	BARU Status
Descrizzione detallata	Binary status
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	0/1
Unità	–
Cumenti	–
32004 (32005 *)	BARO Reference Pressure
Descrizzione detallata	On board high accuracy barometric pressure measurement
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	+70 à +120
Unità	kPa
Cumenti	–

Table 11 Baro Module Input Registers (continued)
32005 (32006 *)	Tensiometru Pressione
Descrizzione detallata	Absolute pressure value from tensiometer
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	-200 à +200
Unità	kPa
Cumenti	Tensiometer needs to be connected as slave
32006 (32007 *)	BARU Temperature
Descrizzione detallata	On board temperature measurement
Tipu di dati	32 bit floating Big-Endian
Gamma permessa	-30 à +60
Unità	degC
Cumenti	–

*Some devices report Modbus register addresses with an offset of +1. This is true for Campbell Scientific Loggers and Dataker loggers. In order to read the desired register use the number in the parenthesis.

EXAMPLE USING A CR6 DATALOGGER AND MODBUS RTU
U Campbell Scientific, Inc. CR6 Measurement and Control Datalogger supports Modbus master and Modbus slave communication to integrate Modbus SCADA networks. The Modbus communications protocol facilitates the exchange of information and data between a computer/HMI software, instruments (RTUs), and Modbus-compatible sensors. The CR6 datalogger communicates exclusively in RTU mode. In a Modbus network, each slave device has a unique address. Therefore, sensor devices must be configured correctly before connecting to a Modbus Network. Addresses range from 1 to 247. Address 0 is reserved for universal broadcasts.

PROGRAMMING A CR6 DATALOGGER
The Programs running on the CR6 (and CR1000) Loggers are written in CRBasic, a language developed by Campbell Scientific. It is a high-level language designed to provide an easy yet extremely flexible and powerful method of instructing the data logger how and when to take measurements, process data, and communicate. Programs can be created using either the ShortCut Software or edited using the CRBasic Editor, both of which are available for downloading as stand-alone applications on the official Campcampana scientifica websitu (www.campbellsci.com). ShortCut Software (https://www.campbellsci.com/shortcut) CRBasic Editor (https://www.campbellsci.com/crbasiceditor)

A typical CRBasic program for a Modbus application consists of the following:

• Variables and constants declarations (public or private)
• Units declarations
• Parametri di cunfigurazione
• Data tables declarations
• Logger Initializations
• Scan (Main Loop) with all the sensors to be quired
• Function call to the Data Tables

CR6 LOGGER RS-485 CONNECTION INTERFACE
The universal (U) terminal of the CR6 offers 12 Channels that connect to nearly any sensor type. It gives the CR6 the ability to match more applications and eliminates the use of many external peripherals.
The Modbus CR6 connection shown in Figure 12 uses the RS-485 (A/B) interface mounted on terminals (C1-C2) and (C3-C4). These interfaces can operate in Half-Duplex and Full-Duplex. The serial interface of the BARO Module used for this example is connected to (C1-C2) terminals.

BARO Module to CR6 Datalogger Wiring Diagram

After assigning the BARO Module a unique Modbus Slave Address, it can be wired to the CR6 logger according to Figure 12. Make sure to connect the white and black wires according to their signals, respectively, to the C1 and C2 ports—the brown wire to 12V (V+) and the blue to G (GND). To control the power supply through your program, connect the brown wire directly to one of the SW12 terminals (switched 12V outputs).

EXAMPLE PROGRAMMI

SUPPORTU CLIENTI

AMERICA DI NORD
I rapprisentanti di u serviziu di u cliente sò dispunibuli per dumande, prublemi o feedback da u luni à u vennari, da 7:00 am à 5:00 pm ora di u Pacificu.

• E-mail: support.environment@metergroup.com
• sales.environment@metergroup.com
• Telefono: +1.509.332.5600
• Fax: +1.509.332.5158
• Websitu: metergroup.com

EUROPA

• Customer service representatives are available for questions, problems, or feedback Monday through Friday,
• 8:00 to 17:00 Central European time.
• E-mail: support.europe@metergroup.com
• sales.europe@metergroup.com
• Telefono: +49 89 12 66 52 0
• Fax: + 49 89 12 66 52 20
• Websitu: metergroup.com

Se cuntattate METER per email, include l'infurmazioni seguenti:

• Nome
• Indirizzu
• Numeru di telefonu
• Indirizzu mail
• Numeru di serie di l'instrumentu

Descrizzione di u prublema

NOTA: Per i prudutti acquistati attraversu un distributore, cuntattate direttamente u distributore per assistenza.

STORIA REVISIONE
U tavulu chì seguita lista rivisioni di documenti.

Revisione	Data	Firmware compatible	Descrizzione
00	6.2025	1.10	Liberazione iniziale

FAQ

What should I do if I need a nonstandard cable length?

Contact Customer Support for assistance with nonstandard cable lengths.

How do I know which communication protocol to use for my application?

Evaluate the advantages and challenges of each protocol based on your application needs. If unsure, contact METER Customer Support for guidance.

Documenti / Risorse

METER BARO Module [pdfGuida di l'utente TEROS 31, TEROS 32, BARO Module, BARO Module, Module

Referenze

• Manuale d'usu