Decoding of half point Z1_Temp (TOP56) values

[joostvnm]

This commit adds decoding of .50 values for the Z1 temp, decoding is done in the same way as the fractional values for water temperatures. I expect that the same can be done for Z2 temp with bit 3 & 4 of byte 119, but I can not test this myself.

I have been running this for 2 weeks and the result are as expected. The temperature now increases and decreases by half degrees now:

[IgorYbema]

are you sure it is only +0.5 and not also 0.25 or 0.75 like in top5 and top6?

[IgorYbema]

I also think they could be the fractionals for TOP36 and TOP37 instead of TOP56 and TOP57. Someone with panasonic service center access can verify this please?

[joostvnm]

are you sure it is only +0.5 and not also 0.25 or 0.75 like in top5 and top6?

I only ever get the values 0x11and 0x13 for byte 119, so only 0b0001 and 0b0011 for the lower bits. And if i remember correctly (cant test this unfortunately) panasonic cloud also only does .0 and .5 values.

[joostvnm]

I also think they could be the fractionals for TOP36 and TOP37 instead of TOP56 and TOP57. Someone with panasonic service center access can verify this please?

My L series all in one does not seem to implement top 36 and 37, it always shows -78, but byte 119 changes.

[IgorYbema]

Mine is currenty 0x12 so different than you. That means your change isn't complete and we can't merge this.
I hope some others join to look into the service cloud if they can find out the correlation.

[MiG-41]

@joostvnm ,can you pass to me one packet/answer from HP ? ( so i havea starting point for L gen. ) . Perhaps only in higher versions there is a posibility to have it.

[joostvnm]

@joostvnm ,can you pass to me one packet/answer from HP ? ( so i havea starting point for L gen. ) . Perhaps only in higher versions there is a posibility to have it.

Is this the data you need?

-- heatpump data --
[000]: 71 C8 01 10 56 95 62 91 00 55 00 16 00 00 00 00 00 00 00 00 59 15 13 55 56 15 55 55 66 19 A9 00 
[032]: 00 00 00 00 00 00 93 9C A3 80 A8 71 67 97 99 00 00 00 00 00 00 00 00 00 00 00 80 85 5B 8A 85 85 
[064]: D0 7B 78 1F 7E 1F 1F 79 79 8D 8D 9A 9A 76 80 A3 A3 7B 8F 90 85 80 8F 8A 94 9E 8F 8A 94 9E 85 8F 
[096]: 8A 02 79 78 BC 15 7E 7C 3D 78 7C 00 00 00 95 75 55 21 87 15 59 05 22 11 66 21 51 15 01 54 8F F7 
[128]: FF E2 D5 0C 29 99 83 92 0C 28 98 94 00 AA 84 9C 99 32 32 9A A3 32 32 32 93 9A 8F 92 97 8A 85 00 
[160]: 8D 00 00 1A 01 01 01 00 00 22 00 01 01 01 01 79 01 01 01 5C 02 00 AC 02 00 01 00 00 01 00 00 08 
[192]: 01 00 00 00 00 00 00 04 94 17 7A 
-- extra data --
[000]: 71 C8 01 21 8A EA 01 00 00 00 00 00 00 00 10 00 01 00 01 00 01 00 01 00 01 00 01 00 00 00 01 00 
[032]: 00 00 01 00 00 00 01 00 00 00 01 00 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
[064]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
[096]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
[128]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
[160]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
[192]: 00 00 00 00 00 00 00 00 00 00 14 

[MiG-41]

Ok, so modifing byte 119 i noticed only influence to TOP56 and TOP57. ( not influancing at all for TOP36 or TOP37).

split is like this : bit 0 , 1 and 2 is responsible for TOP56 , bit 3,4 and 5 for TOP57 . Bit 6 and/or 7 nothing to do with TOP36 or TOP37.
so setting bits like:
000 - results decrease of temperature by 0,25
001 - is base ( no increase or decrese)
010 - results adding 0,25
011 - results adding 0,50
100 - results adding 0,75
101 - results adding 1,00
110 - results adding 1,25
111 - results adding 1,50

So i.e. setting 3F in byte 119 will increse booth TOP56 and 57 for +1,5 deg( compared to base setting 09) . ( probably some values HP will never set , but this how service cloud interprete it).

Still wondering why 09 is not a real base , but 11 ( but if TOP57 not exist it doesn't matter anyway).

For sure this is valid for byte 118 and TOP5 and TOP6 as well ( don't recall what was decoded before).

[IgorYbema]

Could be if zone 2 isn't used that it defaults to 0b010. So when zone 2 is inactive and zone 1 temp is on base it goes to 0x11 (0b0001001). Did you test with zone 2 active @MiG-41 ?

But it looks to be the same as top5 and top 6 then. There we found out it only uses:
0b001 = add 0
0b010 = add 0.25
0b011 = add 0.5
0b100 = add 0,75

[MiG-41]

I used as a base above data from @joostvnm , and there is no Zone 2 active, and base value is as you wrote .
Then just changed bytes responsible for TOP57 ,TOP36 and TOP37 , and for service cloud it doesn't matter , just shows actual values.
Then i played with byte 119....
So generally is same as for TOP5 and TOP6 ( i played with byte 118 in same way).
From formal thing you could add in code this other 4 cases of bits ( since Service Cloud recognize it maybe it will b usefull in future).

And BTW. Someone noticed in Service cloud Zone 1/2: Water Temperature ( with corresponds to TOP36 and TOP37) fractual values ? Any idea with byte can be rosponsible for that ( if any)...

[IgorYbema]

No and those top36 and top37 are only visibile if you have the optional pcb and have temp sensors connected (or emulation is on). Maybe I'll try to build a test device like you have also where I can fiddle around with the hex values. Have to re-open my panasonic service account again :)

[MiG-41]

HP it self will not send TOP36 and TOP37 ( or it will be set ,but with values -78 or something like that) , but modified data with proper values sent to Service Cloud will be decoded and showed there withou any veryfication...

[IgorYbema]

Tested byte#119 for my H-series heatpump but it doesn't change. It keeps it at 0x12 (0b010 for both fractionals). Maybe it wasn't implemented yet correctly in the H-series.

[MiG-41]

On my H is even worse , i have constant 0x24 , with from what i have been decoded , on booth values should be deducted 0,24 ....

[geduxas]

i have optional PCB with my H Series T-CAP (and 2 zones), and 119 byte is always 0x12

[IgorYbema]

On my H is even worse , i have constant 0x24 , with from what i have been decoded , on booth values should be deducted 0,24 ....

0x24 = 0b00 100 100
So both fractional 0b100 and therefore add 0.75. So not deducting.
But still don't know why on our H-series this seems to be illogical

[MiG-41]

And such data Servica Cloud is not able to display also:

[MiG-41]

No , again my mistake...
It actually add this 0,75 ! :)

But i noticed one pik, where value was 0x23 instead 0x24...

[MiG-41]

Today i nodiced , that at my side byte 119 have value 0x1B , with means add 0,50 to booth....
So looks like it is depending on something ,but not really changing as it should ( on H version at least).

[geduxas]

Today i nodiced , that at my side byte 119 have value 0x1B , with means add 0,50 to booth.... So looks like it is depending on something ,but not really changing as it should ( on H version at least).

you on H series and it changes? my pump always shows 0x12

[MiG-41]

Yes , it changes...

Today i alo observe values :0x1B , 0x1C , 0x22, 0x23, 0x24 ...

[MiG-41]

Just discovered , that probably (at least in H) byte 119 is not for Z1&Z2_Water , but for Z1&Z2 Room !
When i start publishing SetZ1RoomTemp and/or SetZ2RoomTemp byte 119 start changing !

EDIT:
When not using internal thermostat or thermistor mode ( then TOP36 Z1_Water_Temp is equal to TOP56 Z1_Temp and TOP37 equal TOP 57 ) , you can't set Z1_Room and Z2_Room , but fractals are still works in byte 119 :)
Maybe this is fixed in next gen...

EDIT2: I though that Optional PCB ccould be o smart , that when there is no set thermostat or thermistor mode ,it sends equal values , but @geduxas real board byte 119 should change....

EDIT3 : @joostvnm what sensor you have ,and where exacly connected ? In L-series Z1 sensor is on main PCB ( not Optional ) ? How it is described ? Water or Room ?

[joostvnm]

EDIT3 : @joostvnm what sensor you have ,and where exacly connected ? In L-series Z1 sensor is on main PCB ( not Optional ) ? How it is described ? Water or Room ?

I dont have an extra sensor connected. The temp is from the sensor in the controller. It's the zone 1 room temperature.

[MiG-41]

So at your setup ( internal thermostat) TOP56 is equal to TOP33 ? !

[joostvnm]

So at your setup ( internal thermostat) TOP56 is equal to TOP33 ? !

No TOP33 doesnt seem to be used in my set up, it always shows 23 degrees. TOP56 is equal to my room temperature

[MiG-41]

But is you switch mode from Internal thermostat to other ( like external thermostat or thermistor) it should show room themperature from that sensor in controller...

[MiG-41]

So any thoughts about it ?
Everybody agree , that byte 119 is not a fractionals for TOP56 and TOP57 in each case ?
Maybe it is only in situation ,when TOP56&57 are reading room temperatures ( internal thermostat or thermistor).
When TOP56&57 are mesuring water temp. it is not their fractionals ? ( or is it only in H... )

[geduxas]

So any thoughts about it ? Everybody agree , that byte 119 is not a fractionals for TOP56 and TOP57 in each case ? Maybe it is only in situation ,when TOP56&57 are reading room temperatures ( internal thermostat or thermistor). When TOP56&57 are mesuring water temp. it is not their fractionals ? ( or is it only in H... )

I have h series 12kW t-cap using external thermostat's, driving by compensation curve.. byte 119 is stable and not changing at all

[MiG-41]

Yes , and i wrote you why... You have a real optional PCB and it sends constant value 0xFF on bytes 10 and 11 , conect thermistors/or potenciometers ( anything with you could vary this temperatures) to Z1&Z2 Room Themperature , and it will be not stable anymore...

[MiG-41]

I got confirmation , that on J series , when using Contoler as Internal thermostat , Zone1:Actual (water/outlet/room/pool) temperature ( so TOP56 with 119 fractions) is also reading internal temperature with resolution 0,5deg ( at least in range 22,5 - 24,5 deg).
But here RC-1:Room thermostat ( so TOP33) is also working ( showing temperature without fractionals). - @joostvnm not confirm this on his L...
And generally Zone1:Actual (water/outlet/room/pool) temperature (and Zone 2 ) as well ... Has fractionals from byte 119 , it is only a case when HP will use it or not...