Use this page when a configured 1-Wire channel must be logged in DataGuard or exported onward to Emiko.
The 1-Wire source setup is documented on 1-Wire Temperature Monitoring > Setup and alarms. This page explains when DataGuard is needed and owns the DataGuard reporting parameters for 1-Wire values.
Use DataGuard via Analog Inputs when the value comes from a physical analog input. Use DataGuard via Driver Communication when the value comes from a configured driver profile rather than a 1-Wire channel.
#) for all 1-Wire alarm, recipient, and DataGuard parameters that belong to the same sensor.OTEQT# and OTDATATYPE# on this page so Emiko receives the value under the correct equipment and data type.OTLOGMODE# and, when needed, OTLOGINT# or OTLOGHYS# on this page to control how the value is logged and exported.Data is only sent when the same channel has a valid equipment type, data type, and log mode.
OTEQT# must be greater than 0.OTDATATYPE# must be greater than 0.OTLOGMODE# must be greater than 0.Use the product page first when the 1-Wire value belongs to a product-specific setup. Use this page for the shared DataGuard reporting parameters.
| Product path | 1-Wire source | DataGuard values | Product setup |
| Standalone DataGuard | Mapped 1-Wire temperature channel. | OTEQT#=35 and the DTY required by the measured value. |
This page |
| OceanWatcher | 1-Wire temperature sensor used as an OceanWatcher temperature value. | Use OTEQT# and OTDATATYPE# for the selected OceanWatcher temperature path. |
OceanWatcher temperature setup |
| FlexVander | Optional field temperature value, for example soil temperature. | Use the equipment type and DTY required by the delivered field-value path. | FlexVander LX9 eco IO list |
| WeatherStation | Mapped 1-Wire temperature channel when the delivered WeatherStation setup uses that source. | Use WeatherStation equipment type when the value belongs to WeatherStation. | WeatherStation DataGuard setup |
This example shows a 1-Wire temperature sensor on channel 1 that should still use normal local alarms, but also be logged and exported onward.
OTLIST to verify that the sensor is mapped to channel 1.OTMIN1, OTMAX1, and alarm texts on the 1-Wire setup page.OTEQT1 so the value is reported under the correct Emiko equipment.OTDATATYPE1 so the value is sent as the correct data type.OTLOGMODE1 and, when needed, OTLOGINT1 or OTLOGHYS1 on this DataGuard reporting page.Configure these parameters after the 1-Wire sensor is enabled, discovered, and mapped to the correct logical channel.
Select which Emiko equipment type should own the reported 1-Wire value.
| Parameter | Index | Range | Format | Default | Example |
OTEQT# |
1..10 | 0..35 |
0 = None (disabled) 1..35 = EQT value for the equipment in Emiko Defined EQT IDs in this software: |
0 | OTEQT1 35 |
Select which data type the 1-Wire channel should be sent as in Emiko.
| Parameter | Index | Range | Format | Default | Example |
OTDATATYPE# |
1..10 | 0..1312 |
0 = None (disabled) 1..1312 = Data type (DTY) for the value sent to Emiko. See Shared Runtime Data Type Reference. |
0 | OTDATATYPE1 1101 |
Select how the 1-Wire value should be logged or exported for the selected channel.
| Parameter | Index | Range | Format | Default | Example |
OTLOGMODE# |
1..10 | 0..4 |
0 = None 1 = Periodic 2 = Periodic + threshold change 3 = Event 4 = Hybrid |
1 | OTLOGMODE1 2 |
Use this parameter when the selected log mode includes periodic logging.
| Parameter | Index | Range | Format | Default | Example |
OTLOGINT# |
1..10 | 0..31 |
0 = Disabled 10 = Every minute 17 = Every hour 23 = Every day |
19 | OTLOGINT1 19 |
Use this parameter when the selected log mode requires a minimum value change before a new value is stored.
| Parameter | Index | Range | Format | Default | Example |
OTLOGHYS# |
1..10 | 0..32767 |
0 = No change requirement Other values = Temperature change |
0 | OTLOGHYS1 25 |
Use 1-Wire Temperature Monitoring > Setup and alarms for sensor discovery, channel mapping, alarms, and recipient setup.
Use Shared Runtime Data Type Reference when the installation requires a DTY lookup before selecting OTDATATYPE#.
Public revision 21/08/2026