-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to determine byte position in composed datapoints? #97
Comments
I think comparing the result of 0x1410 from different systems in different states might help. This is from a Vitocal 300-G with two heating circuits HK1 and HK2 both heating at the time: |
i'm currently trying to get frost protection from 0x1410, this is what 1410 looks like right now with frost protection currently ON. 1;5136;000001000100000000000000000001000000 will be taking another value tomorrow when it's warmer. |
so this is it with frost protection on and off byte 5 is frost prot for heating circuit 1 |
Die Frage ist ja, wie man das sicher rausbekommt, was was ist und ob es generell gilt und auch noch Gerätespezifisch ist. Für meine vitoCal 222 hab ich mich für folgendes entschieden (Heizkreis 1), was zu Deiner Erkenntnis passt: Ist der Frostschutz generell eingeschaltet => (4,"WP.HK1.FrostschutzEingeschaltet (1410_2)",0x1410,19,'b:2:2'), |
finding the byte positions empirically might be a way BUT I think the position assignment should be documented somewhere in the SQL/xml data, don't you think? |
e.g. with CU401B_S we have 19 1-byte values at addr. 0x1410:
so from what do we know which byte belongs to which value?
we are missing some info like 'BytePosition'...
initially I thought perhaps EventTypeOrder of ecnEventTypeEventTypeGroupLink might be the key but this seems to be a dead end
The text was updated successfully, but these errors were encountered: