Opentherm counters are limited to 16 bits
Posted: Sat Nov 10, 2012 11:54 pm
I saw some strange numbers arriving in my system earlier this evening and just wanted to share that, so you won't start looking for a non-present bug like I did, for 10 minutes or so
While looking at the incoming information from my Opentherm Gateway, I saw something strange today.
Here's a small piece of the information: The number 65535 immediately caught my attention, for the obvious reason - can't be a coincidence, right..
So I had a look at the information from my Remeha Recom Interface, this one told a completely different story:
My first thought was that there must be something wrong in my Opentherm Gateway frame decoding, but that was not the case.
The fact is, that Opentherm can only handle 16-bit unsigned values for the Data ID regarding the number of burner starts! (Data ID 116 (decimal), Type u16).
So if you're connecting the Opentherm Gateway to a central heating that has been operational for some years (mine: 3), you can expect some "strange" numbers!
So remember this; 16 bit is the max!

While looking at the incoming information from my Opentherm Gateway, I saw something strange today.
Here's a small piece of the information: The number 65535 immediately caught my attention, for the obvious reason - can't be a coincidence, right..

So I had a look at the information from my Remeha Recom Interface, this one told a completely different story:
My first thought was that there must be something wrong in my Opentherm Gateway frame decoding, but that was not the case.
The fact is, that Opentherm can only handle 16-bit unsigned values for the Data ID regarding the number of burner starts! (Data ID 116 (decimal), Type u16).
So if you're connecting the Opentherm Gateway to a central heating that has been operational for some years (mine: 3), you can expect some "strange" numbers!
So remember this; 16 bit is the max!