Setup and alarms

Use this page after the product-specific 1-Wire wiring is complete.

For general command syntax, see VikMote Command Guide.

Use this page for active 1-Wire setup, sensor-list commands, and channel-based alarm settings.
Commands on this page: OTLIST, OTSEARCH, OTREDO, OTDEL, and OTDELALL.
Configure recipient delivery separately on Shared Runtime > Recipients when the same logical channel must use the shared runtime recipient setup.
1-Wire data output can be shared through DataGuard when a mapped sensor value must be logged or exported to Emiko. Configure sensor discovery and channel mapping here, then continue on DataGuard via 1-Wire.

Activation

Enable 1-Wire before searching for sensors.

Parameter Index Range Format Default Example

WIRETYPE

0..1

0 = Disabled

1 = 1-Wire temperature sensors enabled

WIRETYPE 1

Alarm Delivery Model

1-Wire alarms become active from the channel settings on this page. Recipient delivery and DataGuard export are optional next steps.

Use the shared default recipient groups SSYS, ESYS, and TSYS when 1-Wire alarms should follow the normal shared runtime recipient setup.
Use SOT#, EOT#, and TOT# only when one 1-Wire channel must send to different recipients than the shared defaults.
Keep the same channel number across alarm limits, alarm texts, dedicated recipients, and DataGuard for the same sensor.
Configure alarm behavior first, then recipient delivery, and finally optional DataGuard export.

Commands

The commands below are used to build and maintain the 1-Wire sensor list and logical channel assignment.

Sensor Discovery and Mapping

Use OTLIST to review the current channel assignment before you change alarms or logging.
Use OTSEARCH when you want to add newly connected sensors without rebuilding the full list.
Use OTREDO when a new installation needs a fresh list from scratch, or when the stored list must be rebuilt completely.

Command	Function
`OTLIST`	Shows the current 1-Wire sensor list and the logical channel assignment.
`OTSEARCH`	Searches for 1-Wire sensors, appends new sensors, and keeps existing logical channel numbers when possible.
`OTREDO`	Clears the current 1-Wire list and rebuilds the full logical channel mapping from the detected sensors.

Important: if OTREDO is used on an existing installation, verify all channel-specific alarm and DataGuard settings afterward because the logical channel assignment can change.

List Cleanup

Use OTDEL to remove missing sensors after a search cycle.
Use OTDELALL only when the stored sensor list must be cleared completely.

Command	Function
`OTDEL`	Removes sensors from the stored list when they are no longer present after a search cycle.
`OTDELALL`	Clears the entire stored 1-Wire sensor list.

Commissioning Sequence

Enable 1-Wire with WIRETYPE 1.
Run OTREDO on a new installation, or OTSEARCH when adding sensors to an existing installation.
Run OTLIST and verify which physical sensor is mapped to each logical channel.
Configure the required alarm limits, hysteresis, delay, and optional texts for the relevant channels.
If alarms must be delivered to recipients, use the shared default recipient groups or configure dedicated 1-Wire recipient groups for the affected channels.
Only after the channel mapping is correct, continue to DataGuard for the channels that should be logged or exported.

Example Setup Flow

WIRETYPE 1 enables 1-Wire.
OTREDO builds the sensor list from scratch on a new installation.
OTLIST verifies the assigned logical channel.
OTMIN1 30 sets the low alarm limit for channel 1.
OTMAX1 250 sets the high alarm limit for channel 1.
OTHYS1 5 sets hysteresis for channel 1.
OTFIL1 60 sets the alarm delay for channel 1.
OTHTXT1 High water temperature sets the high alarm text for channel 1.
OTLTXT1 Low water temperature sets the low alarm text for channel 1.
OTNTXT1 Water temperature normal sets the return-to-normal text for channel 1.
If channel 1 should use different recipients than the shared defaults, configure SOT1, EOT1, or TOT1 on Recipients and Notifications.
If channel 1 should be logged or exported, continue on DataGuard via 1-Wire and use the same channel number there.

Alarm limits

Low alarm limit

Set the low alarm limit for each logical channel that should raise a low-temperature alarm.

Parameter Index Range Format Default Example

OTMIN#

1..10

-2147483647..2147483647

0 = Low alarm disabled

Other values = Temperature threshold

OTMIN1 250

High alarm limit

Set the high alarm limit for each logical channel that should raise a high-temperature alarm.

Parameter Index Range Format Default Example

OTMAX#

1..10

-2147483647..2147483647

0 = High alarm disabled

Other values = Temperature threshold

OTMAX1 2800

Hysteresis

Use hysteresis to avoid repeated alarm switching around the same threshold.

Parameter Index Range Format Default Example

OTHYS#

1..10

0..32767

0 = No hysteresis

Other values = Temperature change

OTHYS1 50

Filter and delay

Use the filter value to delay alarm activation and return-to-normal handling for brief spikes.

Parameter Index Range Format Default Example

OTFIL#

1..10

0..127

0 = No delay

1..127 = Filter delay level

OTFIL1 60

Alarm texts

Alarm texts are optional user messages tied to the same logical channel number as the corresponding alarm parameters.

Up to three channels share the same text storage group.
The combined stored text in one group cannot exceed 254 characters.
The available length for one text therefore depends on the other alarm texts already stored in the same group.
If a text is stored alone in its group, the practical maximum is 252 characters.

The three text parameters have different roles and must use the same channel number as the related alarm limits.

OTLTXT# sends the low-alarm text and must use the same channel number as OTMIN#.
OTHTXT# sends the high-alarm text and must use the same channel number as OTMAX#.
OTNTXT# sends the return-to-normal text for the same channel after an active low or high alarm.

Alarm text - low

Use OTLTXT# to define the message sent when the temperature crosses the low alarm limit on that same channel.

Parameter	Index	Range	Format	Default	Example
`OTLTXT#`	1..10	-	Text string	-	`OTLTXT1 Low water temperature`

Alarm text - high

Use OTHTXT# to define the message sent when the temperature crosses the high alarm limit on that same channel.

Parameter	Index	Range	Format	Default	Example
`OTHTXT#`	1..10	-	Text string	-	`OTHTXT1 High water temperature`

Alarm text - normal

Use OTNTXT# to define the message sent when the temperature returns to normal after a low or high alarm on that same channel.

Parameter	Index	Range	Format	Default	Example
`OTNTXT#`	1..10	-	Text string	-	`OTNTXT1 Water temperature normal`

Recipients and notifications

1-Wire alarms can use the shared default recipient groups without any dedicated 1-Wire recipient setup.

Use the shared default groups when 1-Wire alarms should go to the same SMS, email, or voice recipients as other shared runtime alarms.
Use SOT#, EOT#, and TOT# only when one 1-Wire channel must use different recipients than the shared defaults.
Keep the same channel number across alarm limits, alarm texts, recipient routing, and any DataGuard export for the same sensor.
Configure alarms first, then configure recipient delivery on Shared Runtime > Recipients and Notifications.

Report Through DataGuard

This page owns the 1-Wire source setup. If a configured 1-Wire channel must be logged in DataGuard or exported onward to Emiko, continue on DataGuard via 1-Wire.

Use the same logical channel number in the 1-Wire source setup and the DataGuard reporting setup.
Configure sensor discovery, channel mapping, alarms, and recipient delivery here before adding DataGuard reporting.

Example: if OTLIST shows that a sensor is mapped to channel 3, then that same sensor must use channel 3 in its alarm limits, alarm texts, recipient routing, and DataGuard reporting setup.