Specifications

M1 Control RS-232 ASCII String Protocol Page 49 of 68 Rev. 1.79 July 16, 2009

3 = Current Temperature setting from controller with

thermostat else not used. Version 5.1.6

4 = CoolSetPoint VV= [Cool setpoint if in Cool/auto mode, 01

to 99]

5 = HeatSetPoint VV= [Heat setpoint if in heat/auto mode, 01

to 99]

00 – future use

CC – Checksum

Example:

0Bts01704004B Set Thermostat Cool Set Point

element – Thermostat 01 to 70 degrees.

Reply Thermostat Data will reply to Set Thermostat Data.

4.35.4 Request - Omnistat 2 From PC to M1 ASCII Protocol (t2)

This request command allows for requesting data from theM1XSP that is connected

to the HAI Omnistate 2 HVAC Thermostat. The Omnistat 2 protocol is required to

build the ASCII command strings. M1 version 5.1.9 or later is required for this

command.

2A – ELK Packet Length in ASCII hex, 42 length

t2 – ELK Command “t2” – PC to Omnistat command via M1.

D[36]… – 36 ASCII Hex bytes comprising 18 binary bytes of Omnistat data,

including Checksum.

“0” right padded.

RA – Start/Remote Address, Bit 7 = 1

DA – Data Length/Message Type

Data – 0 to 15 binary data bytes, converted to 0 to 30 ASCII Hex bytes

CKSUM – Omnistat 2 checksum is last byte of Omnistat 2 data before

padding.

00 – Future use

CC – ELK Checksum

CRLF

4.35.5 Reply - M1 to PC with Omnistat 2 ASCII Hex data (T2)

This is the reply from the M1XSP connected to the HAI Omnistat 2 HVAC

Thermostat. M1 version 5.1.9 or later is required for this command.

2A – ELK Packet Length in ASCII hex, 42 length

T2 – ELK Command “T2”, Omnistat 2 to PC command..

D[36]… – 36 ASCII Hex bytes comprising 18 binary bytes of Omnistat 2 data,