Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
111110000011111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111000000011111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
111110000011111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111
11111


From Protocol Doc:

Image Added



AcuRite 00606TX and 00782W3

These sensors have identical formats and add yet more variation in data encoding. Data bits are sent in big-endian order and nibbles are also in bigendian order (opposite to the 0964TX sensor). The data packet length is also different at 32 bits.


The status nibble's MSB is a "battery okay" flag which is normally one. It goes to zero when the battery drops below about 2.6 volts or so.


Temperature is a signed 12-bit value with resolution of 0.1C. For example, 25.6C is encoded as the value 256 (0x100 hexadecimal). A value of -0.1C is encoded as -1 (0xFFF hexadecimal).


There is an 8-bit hash code appended to check message integrity. It is the same algorithm as described for the Ambient Weather F007TH sensor below with two minor modifications. 1. The hash code value is initialized to zero instead of hexadecimal "0x64". 2. Start with the fifth value in the LFSR sequence depicted for the F007TH sensor -- 0xF1 instead of the first value, 0x3E.


References

...