Vaillant VRC 720/2-3 - how to write TimeSlots?

[andreiandreiandreiandreiandrei]

Hello Dear Community,

Anybody knows how to write TimeSlots on Vaillant VRC 720/2-3?

config file has this Timers, let's say for Monday:

r,,hwcTimer.Monday0,timer monday 1,,,,0000,,,rTimeSlotWithTemp,,,
r,,hwcTimer.Monday1,timer monday 2,,,,0001,,,rTimeSlotWithTemp,,,
r,,hwcTimer.Monday2,timer monday 3,,,,0002,,,rTimeSlotWithTemp,,,
w,,hwcTimer.Monday,timer monday,,,,00,,,wTimeSlotWithTemp,,,
r,,ccTimer.Monday0,timer monday 1,,,,0000,,,rTimeSlotWithoutTemp,,,
r,,ccTimer.Monday1,timer monday 2,,,,0001,,,rTimeSlotWithoutTemp,,,
r,,ccTimer.Monday2,timer monday 3,,,,0002,,,rTimeSlotWithoutTemp,,,
w,,ccTimer.Monday,timer monday,,,,00,,,wTimeSlotWithoutTemp,,,
r,,z1Timer.Monday0,timer heating monday 1,,,,0000,,,rTimeSlotWithTemp,,,
r,,z1Timer.Monday1,timer heating monday 2,,,,0001,,,rTimeSlotWithTemp,,,
r,,z1Timer.Monday2,timer heating monday 3,,,,0002,,,rTimeSlotWithTemp,,,
w,,z1Timer.Monday,timer heating monday,,,,00,,,wTimeSlotWithTemp,,,
r,,z2Timer.Monday0,timer heating monday 1,,,,0000,,,rTimeSlotWithTemp,,,
r,,z2Timer.Monday1,timer heating monday 2,,,,0001,,,rTimeSlotWithTemp,,,
r,,z2Timer.Monday2,timer heating monday 3,,,,0002,,,rTimeSlotWithTemp,,,
w,,z2Timer.Monday,timer heating monday,,,,00,,,wTimeSlotWithTemp,,,
r,,z3Timer.Monday0,timer heating monday 1,,,,0000,,,rTimeSlotWithTemp,,,
r,,z3Timer.Monday1,timer heating monday 2,,,,0001,,,rTimeSlotWithTemp,,,
r,,z3Timer.Monday2,timer heating monday 3,,,,0002,,,rTimeSlotWithTemp,,,
w,,z3Timer.Monday,timer heating monday,,,,00,,,wTimeSlotWithTemp,,,

There are different entrys for read, one for each Slot, and one for write, as we can see above. While it is very clear how to read:

Z1Timer_Monday0 htm=00:00;htm_1=24:00;slottemp=12.0 [Temperature stored in the slot. Degrees Celsius]

meaning Monday in slot0 from 0:00 to 24:00 keep 12 degrees. It is unclear for me how to write new values in:

w,,z1Timer.Monday,timer heating monday,,,,00,,,wTimeSlotWithTemp,,,

as could be more timeslots per day.

Also, while I understand

ctlv3 Z1Timer_Timeframes = 1;1;1;1;1;1;1

as how many timeslots each day has, this is read only. I do not understand what this Timer.Config means:

r,,z1Timer.Config,timer Configuration(static atm? describes featue set?),,,B555,a30000,,,HEX:9,,,Configuration
with values:
ctlv3 Z1Timer_Config = 00 0c 0a 05 01 0c 05 1e 00

One last question, what does it referes to the ccTimer definitions? I have read that .cc is circulation circuit, but I don't see the context of timeslot for circulation.

Thank you

[andreiandreiandreiandreiandrei]

The ccTimer definitions, I presume, address the external circuit pump, not the one inside the bai or ehp as

ctlv3 CcTimer_Config = 03 01 01 00 00 00 ff ff 00
ctlv3 CcTimer_Friday0 = 00:00;00:00
ctlv3 CcTimer_Friday1 = 00:00;00:00
ctlv3 CcTimer_Friday2 = 00:00;00:00
ctlv3 CcTimer_Monday0 = 00:00;00:00
ctlv3 CcTimer_Monday1 = 00:00;00:00
ctlv3 CcTimer_Monday2 = 00:00;00:00
ctlv3 CcTimer_Saturday0 = 00:00;00:00
ctlv3 CcTimer_Saturday1 = 00:00;00:00
ctlv3 CcTimer_Saturday2 = 00:00;00:00
ctlv3 CcTimer_Sunday0 = 00:00;00:00
ctlv3 CcTimer_Sunday1 = 00:00;00:00
ctlv3 CcTimer_Sunday2 = 00:00;00:00
ctlv3 CcTimer_Thursday0 = 00:00;00:00
ctlv3 CcTimer_Thursday1 = 00:00;00:00
ctlv3 CcTimer_Thursday2 = 00:00;00:00
ctlv3 CcTimer_Timeframes = 0;0;0;0;0;0;0
ctlv3 CcTimer_Tuesday0 = 00:00;00:00
ctlv3 CcTimer_Tuesday1 = 00:00;00:00
ctlv3 CcTimer_Tuesday2 = 00:00;00:00
ctlv3 CcTimer_Wednesday0 = 00:00;00:00
ctlv3 CcTimer_Wednesday1 = 00:00;00:00
ctlv3 CcTimer_Wednesday2 = 00:00;00:00

the values read are only time intervals (start;end), not the start;end;temp like for hwc and zones (z1,z2...)

still unclear how to read _Config

[andreiandreiandreiandreiandrei]

Ok, it was a bit tricky, but I succeeded to set the timeslots. So, first I found in the 15.ctlv2.tsp the definition like this:

  /** timer heating monday */
  @inherit(w_11)
  @ext(0)
  model Z1Timer_Monday {
    value: wTimeSlotWithTemp;
  }

and in _templates.tsp the definition of wTimeSlotWithTemp:

/** Complete Slot for writing the time table settings. */
model wTimeSlotWithTemp {
  slotIndex: slotIndex;
  slotCount: slotCount;
  slotTimeFrame: slotTimeFrame;
  slotTemp: slotTemp;
}

So, it is necessary to send slotIndex, which I assumed is the 0,1,2 from the end of Z1Timer_Monday0. So, index=0, count=1 I sent:

ebusctl write -c ctlv3 Z1Timer_Monday "0;1;00:00;24:00;20" ;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday0;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday1;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday2;  \
ebusctl read -c ctlv3 -f -v Z1Timer_Timeframes
0;1;00:00;24:00;20.0

ctlv3 Z1Timer_Monday0 htm=00:00;htm_1=24:00;slottemp=20.0 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday1 htm=00:00;htm_1=00:00;slottemp=- [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday2 htm=00:00;htm_1=00:00;slottemp=- [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Timeframes slotcount=1;slotcount_1=1;slotcount_2=1;slotcount_3=1;slotcount_4=1;slotcount_5=1;slotcount_6=1

So I set 20 degrees for the hole day of Monday. Sure, the read commands are only for checking.
Then I made more tests, and the slotTemp accepts numbers from 5.0 degree to 30.0 with a step of 0.1.

Next, obviously, I tried to write slot index 1 and 2, but:

ebusctl write -c ctlv3 Z1Timer_Monday "0;3;22:00;24:00;12.5"
ebusctl write -c ctlv3 Z1Timer_Monday "1;2;22:00;24:00;12.5"

didn't work. Two hours and a pause later, I made some mistakes, and it initiated the second timeslot:

$ ebusctl write -c ctlv3 Z1Timer_Monday "0;2;00:00;22:00;11.5";  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday0;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday1;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday2;  \
ebusctl read -c ctlv3 -f -v Z1Timer_Timeframes
0;2;00:00;22:00;11.5

ctlv3 Z1Timer_Monday0 htm=00:00;htm_1=22:00;slottemp=12.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday1 htm=00:00;htm_1=00:00;slottemp=- [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday2 htm=00:00;htm_1=00:00;slottemp=- [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Timeframes slotcount=1;slotcount_1=1;slotcount_2=1;slotcount_3=1;slotcount_4=1;slotcount_5=1;slotcount_6=1

 $ ebusctl write -c ctlv3 Z1Timer_Monday "1;2;22:00;24:00;11.5";  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday0;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday1;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday2;  \
ebusctl read -c ctlv3 -f -v Z1Timer_Timeframes
1;2;22:00;24:00;11.5

ctlv3 Z1Timer_Monday0 htm=00:00;htm_1=22:00;slottemp=11.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday1 htm=22:00;htm_1=24:00;slottemp=11.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday2 htm=00:00;htm_1=00:00;slottemp=- [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Timeframes slotcount=2;slotcount_1=1;slotcount_2=1;slotcount_3=1;slotcount_4=1;slotcount_5=1;slotcount_6=1

See that first command 0;2;00:00;22:00;11.5 didn't changed the temp to 11.5, but after the second command it was changed.

So, in conclusion, the system do the changes after it receives all the slots defined with the second value (3 in our case) like this:

$ ebusctl write -c ctlv3 Z1Timer_Monday "0;3;00:00;06:00;10.5" ;  \
ebusctl write -c ctlv3 Z1Timer_Monday "1;3;06:00;12:00;11.5";  \
ebusctl write -c ctlv3 Z1Timer_Monday "2;3;12:00;24:00;12.5";  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday0;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday1;  \
ebusctl read -c ctlv3 -f -V Z1Timer_Monday2;  \
ebusctl read -c ctlv3 -f -v Z1Timer_Timeframes
0;3;00:00;06:00;10.5

1;3;06:00;12:00;11.5

2;3;12:00;24:00;12.5

ctlv3 Z1Timer_Monday0 htm=00:00;htm_1=06:00;slottemp=10.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday1 htm=06:00;htm_1=12:00;slottemp=11.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Monday2 htm=12:00;htm_1=24:00;slottemp=12.5 [Temperature stored in the slot. Degrees Celsius]

ctlv3 Z1Timer_Timeframes slotcount=3;slotcount_1=1;slotcount_2=1;slotcount_3=1;slotcount_4=1;slotcount_5=1;slotcount_6=1

Notice the slotcount=3 from the first position in Z1Timer_Timeframes

So it remains unknown the Z1Timer_Config varible.