Open moustic999 opened 5 years ago
So far I have seen the f7
telegram only in context with hiding or dis-hiding of settings on my RC310.
This means that the telegram appears to have a bit mask for displaying offsets of a selected data set.
(03:04:21.204) Gateway -> Thermostat, type 0x03FF telegram: 48 90 F7 00 03 FF 01 B9 (CRC=83)
(03:04:21.234) Thermostat -> 0x48, type 0xFF01 telegram: 10 48 F7 00 FF 01 B9 35 19 08 (CRC=87)
I guess that's how it works:
With the first telegram the gateway queries the thermostat for the f7
telegram for EMS+ dataset 01 b9
and requests to get data from offset 00
with desired lenth of 03
bytes.
The thermostat replies and sends the f7
telegram. In its datablock it repeats which dataset gets masked, followed by the bitmask in three bytes.
The bitmask 35 19 08
masks the Offsets of the 01b9
telegram like this:
0x08 0x19 0x35
00001000 00011001 00110101
| | | | | |
| | | | | Offset 0x00
| | | | Offset 0x07
| | | Offset 0x08
| | Offset 0x0f
| Offset 0x10
Offset 0x13
It would also be possible that the bitmask is not to hide the setting, but to mark it as write-protected (so the setting disappears on the RC in my case). But I can't check this with my hardware, because I only read on the bus.
to help you decoding this F7, here is the log I got : F7 Message for 01B9
F7 message for 01A5
Request Content for 01A5 ( in 2 times because msg longer that MAX lenght)
Request Content for 01B9
Hopefully it will help you to explain how it works and maybe find the use of many offset...