search

john30 / ebusd-configuration

ebusd configuration files
GNU General Public License v3.0
174 stars 272 forks source link

Vaillant hcmode no pumpstate in Status01 #38

Open absalom-muc opened 7 years ago

absalom-muc commented 7 years ago

Hi john,

Thank you very much for your great program!

I believe that there might be a bug in hcmode for Vaillant. The last byte of Status01 is not related to the pumpstate. Instead it represents the 'active burner' (similar to Mode/Betriebsart) with the 3 options (off, heater, water). I tested these options with the following results:

Heater=off, WW=off
[update info] update MS cmd: 1008b5110101 / 0960500004441e0000ff
[update notice] update bai Status01 QQ=10: 48.0;40.0;4.000;34.0;15.0;off

Heater=on, WW=off
[update info] update MS cmd: 1008b5110101 / 09282600043a420100ff
[update notice] update bai Status01 QQ=10: 20.0;19.0;4.000;29.0;33.0;on

Heater=off, WW=on
[update info] update MS cmd: 1008b5110101 / 09926e00046e1e0400ff
[update notice] update bai Status01 QQ=10: 73.0;55.0;4.000;55.0;15.0;4

Could you have a look on it? Thank you. absalom

andig commented 7 years ago

@absalom-muc I can confirm your finding for ecoTEC 146. It's the 3-way vent position we're seing in the last byte imho. What I'm wondering- as it's already decoded as on/off/decimal if it should be all decimals or 4 should be mapped to 'warm water' or similar?

absalom-muc commented 7 years ago

So far I've the following understanding:

bit0: burner for heater (0/1 : off/on)
bit1: overrun (so far I've only seen in combination with bit0=1 (0/1 : no overrun/overrun) ???
bit2: burner for warm water (0/1 : off/on)

I will check some logs more in the next days and will give you further feedback. Especially for bit1 I'm not sure if it is really related to an overrun. Do you know what is overunning?

absalom-muc commented 7 years ago

In my point of view it makes sense to map '4' to 'warm water'. But I'm not sure if it is really related to pumpstate only because it is !=0 only when heating is active. For bit 1 (overrun) I've no more findings

john30 commented 7 years ago

you should be able to check the values against bai BMUB51101HwcState/BMUB51101BoilerFlowTemp/BMUB51101ErrorStatus/BMUB51101StorageTemp

absalom-muc commented 7 years ago

During the test BMUB51101HwcState was always 2 and BMUB51101ErrorStatus always 0. The other values are visible in the diagram: log_20170115

As you can see pumpstate is related to SDFlame.

andig commented 6 years ago

@john30 I've just done another simple test regarding Status01 last byte by manually forcing HW preparation, this is the listen result:

700 HwcOpMode = day
700 HwcTempDesired = 70

bai Status01 = 34.0;49.0;19.438;-;53.0;off
broadcast vdatetime = 12:58:54;30.09.2017
vr_70 SensorData = 31.31;-;-;-;23.06;23.00;c8 7c 00
bai Status01 = 48.5;50.5;19.625;-;53.0;off <-- vent is still off
bai Status01 = 50.0;51.0;19.438;-;53.0;off <-- vent is still off
vr_70 SensorData = 31.38;-;-;-;23.06;23.00;c8 7c 00
700 Hc1FlowTemp = 23.0625
700 Hc2FlowTemp = 23
700 HwcTempDesired = 70 <-- not sure why this is repeated
bai ModulationTempDesired = 0.0
bai Status01 = 50.5;51.5;19.625;-;52.5;off
bai Status02 = auto;60;52.0;70;70.0 <-- changed off to target temp
vr_70 SensorData = 31.38;-;-;-;23.25;23.06;c8 7c 00
bai Status01 = 52.5;50.5;19.625;-;52.5;4 <-- changed off to 4 (hwc vent open)
vr_70 SensorData = 31.31;-;-;-;23.44;23.06;c8 7c 00
bai Status01 = 60.5;51.0;19.625;-;52.5;4 <-- flowtemp begins to rise
john30 commented 6 years ago

ok interesting. so do you think the last byte is a ventilator status?

andig commented 6 years ago

ok interesting. so do you think the last byte is a ventilator status?

@john30 if the question was for me- I believe the last part of the decoded Status01 (the last byte?) is the setting of the 3-way-vent where 4 means hot water preparation. This is also what @absalom-muc says above:

In my point of view it makes sense to map '4' to 'warm water'.

andig commented 6 years ago

Ping @john30 do you need additional info for this one?

john30 commented 6 years ago

I don't have time for this right now. All the configuration issues are kind of on hold as I'm busy with soldering many many new interfaces and preparing a maintenance release of ebusd. Furthermore I started to work on the first 3.0 configuration files and I'd like to do changes there rather than in the the 2.1.x version.

andig commented 4 years ago

Ping @john30 is there anything I could help with regarding the 3.0 configs?

john30 commented 4 years ago

basically a conversion from 2.1 to 3.0 is needed while combining the two 2.1 language file pairs into one 3.0 file. I started working on that, but it still needs to be worked on

robuboot commented 4 years ago

0=cooling 1=auto or off 2=heating 3=water

weimens commented 3 years ago

ebusd_status01_5 For the vaillant ecotec plus vcw the last byte of the Status01 is also not the pumpstate. Looks more like an combined Status of ValveSet and Flame.

Nico184 commented 2 years ago

If anybody is still interested in this issue: I can confirm that the last byte is not pumpstate but it is a status of the EcoTec. I discovered the value 8 for last byte if EcoTec is in mode Funktionsmenü (Fachhandwerkerebene -> Testprogramme -> Funktionsmenü) For heating the value is 1 (ON) for loading hot water the value is 2 (OVERRUN) Hardware: EcoTec VC 266/5-5