Monday 2 January 2012

Anti-cycling mode and the d.2 parameter


Sometimes the boiler enters an anti-cycling mode, which is intended to prevent it from trying to re-start inappropriately quickly. Here I gratefully reproduce UpgradeME's explanation of the d.2 boiler code, which determines how long it waits before re-starting:
"This may also be of some use, which explains how the 'anti-cycle' operates. 
Vaillant d.2 code - Example of operation  
Let's assume d.2 is set at 60, the modulating controller is currently requesting a flow temperature of 40C and the burner has already fired. The boiler upon entering anti-cycle mode starts a timer, counting up from zero, with an initial 'goal' of waiting 38.5 minutes, from the following table:

[Caution - MikeH has recorded in the comments below that for his 415, installed in about 2008, the values he gets are as in the table, except in the row above the one indicated. In other words, for a target flow temperature of 70C, his boiler is using the values that the table gives in the 65C row. A 418 boiler fitted in about late 2010 uses the figures given by table without adjustment.]
If after waiting 20 mins, the room temperature drops, the controller then changes its flow temperature request from 40C to say 60C. The anti-cycle time for 60C is 17 mins, but as the timer has already reached 20 mins, there is no anti-cycle time remaining (it's actually now -3mins) so the boiler then fires the burner again.
[anti-cycle time from table] - [timer] = [time remaining before boiler is allowed to re-start]
Initially that would have been be 38.5-0 = 38.5 min then changed to 17-20=-3mins 
The above example is assuming a modulating controller set in 'analog' mode where the flow temperature demand is dynamic. If set to 'two-point' mode (or using a.n.other room stat), the flow temperature is static and set via the dial on the front of the boiler. As an example for a static flow temperature demand, if the boiler was set at 65C, after it enters anti-cycle mode the boiler will wait 11.5 minutes before firing again with d.2 set at 60, or 4.5mins with d.2 set at its default of 20. Pump is off and zone valve(s) are closed during anti-cycling period."
I've edited this description slightly from UpgradeME's text to make it clearer (and in particular have altered the equation, which seemed to have the two parameters the wrong way round). Let me know if I've got the wrong end of the stick here.

I suspect that the way the timer is described as working (counting up) is not strictly accurate, since parameter d.67 is "remaining burner anti cycling time" (i.e. a count down). I had already noticed what appeared to be a countdown as one of the vrDialog-recorded bits of data on my system, but had not worked out exactly where it came from or what it was doing. I shall post some graphs of how d.67 looks when I have time.

The way the ecoTEC manual describes this process is:

"The burner is electronically locked for a specific time after each time it is switched off ("re-start interlock") to avoid frequent switching on and off of the burner (energy losses).
The burner anti-cycle time is only activated for the heating operation. Hot water operation during a burner anti-cycle time does not affect the timer.
The individual anti-cycle time can be matched to the hydraulic and thermal properties of the heating installation. In the factory the burner anti-cycle time is set to a value of 20 minutes. It can be varied under diagnosis point "d.02" within the range 2 minutes to 60 minutes. The individual effective anti-cycle time is calculated from the momentary target feed temperature and the set maximum burner anti-cycle time.
The timer can be reset or cancelled by actuating the appliance main switch. The remaining burner anti-cycle time left after switching off by the controller in heating operation can be called up under diagnosis point "d.67". The individually effective burner anti-cycle times with respect to the feed temperature and the maximum set burner anti-cycle time can be taken from Table 7.2"
It does sound from this as though d.2 could be relevant to micro firing, since "avoid[ing] frequent switching on and off of the burner" is exactly what we aim to do. However, I cannot presently see that the d.2 setting can be the (sole) cause of micro firing in my system, for instance. I have not changed it from the factory setting of 20 min. I routinely see micro firing at a target flow temperature of 40C, which the table indicates as corresponding to an anti cycling time of 13 min. But the boiler often tries to re-start immediately (within seconds), rather than waiting anything like 13 min. The sorts of timescales indicated by the table look more like what is controlling the interval between periods of short firing.

Can anyone explain to me when the boiler does enter anti cycling mode? That is status code S.8. Sometimes when the boiler switches off, it goes to S.7 (pump over run, which presumably means that it keeps pumping for a period determined by parameter d.1)  but not to S.8. But sometimes it goes to S.8. For instance, see the status code graph during a few minutes of micro firing that is on the page called "The problem" - there it never enters S.8, so can d.2 be relevant at all during this period? Perhaps it ought to be going to S.8, since it would then wait a respectable length of time before re-firing instead of doing so straight away.

8 comments:

  1. I agree with the operation of d2, I am currently running at 60 and this seems to work with a minimum flow temp set at 55C.

    But tonight when I got home I noticed something strange, the temperature being called for was 56C that is a curve of 1.8, outside temp reported as 5C room temperature set at 21C and actual room temperature approaching this at 20.5C.

    What happened was it reached a flow temperature of 56C and shut off, so I checked d67 and to my surprise it was only showing 6 (mins) and it was reading status code S7. After 6 mins the flow temp had dropped to 46C which was not enough to stop an overshoot. The next cycle d67 was at 9 mins and this time it dropped further to 40C which was still not low enough.

    So my observation is why was d67 suddenly so low when I have defiantly observed it at figures closer to the table at the top of this page.

    ReplyDelete
  2. Update to my last post, on the third retry d67 was this time 50 mins but still showing S7 but after the pump went off, d1 set to 20 mins the status has changed to S8. So what has happened there, no other parameters have change at least not much.

    ReplyDelete
  3. d.2 is the MAXIMUM anti-cycle period at 20C, shown in minutes. The default is 20 mins.

    The table shows the different MAX waiting time when the flow temperature requested is higher than 20C.

    The starting of the anti-cycle period is linked to the delta between d.40 & d.41. I don't have the exact details to hand but IIRC the burner stops when there is around 4 or 5C delta. The boiler then enters s.7 (pump overrun) to remove excess heat from the HEX if it or the flow temp was high.

    Assuming it has entered s.7, after the time defined in d.1 has elapsed (default 5 mins) the "equation" is checked to see if the boiler should enter s.8 (Anti cycling mode) and for how long.

    I guess a flow chart would help to show/define the process if anyone has time to create one (perhaps in Visio?), I could offer help reviewing it!?

    (NOTE: The above is based on my observations and logical reasoning. It has not been supplied or verified by Vaillant)

    ReplyDelete
  4. On my 3 year old 415 the ant-cycling times seem to be exactly those in the table BUT all temperatures 5c below those stated. For example, at 65 target d2=70 gets 11.5 not 6.5 as stated.
    This is handy cos it would not work with the tabled figures.

    I find the anti-cycling times consistent if the boiler is doing "normal cycling". If the boiler tries to restart but doesn't make it past the initial "minute" then it will try "several" times in "a few" minutes usually without success. It then reverts to full anti-cycling time but can change its mind. I think that can be because the boiler thinks it is cool enough. All of this seems to be useful after a hot-water heating session.

    My setup is very sensitive to getting stuck in failed restart scenarios so I have to make sure d2 is good and long. It seems to be luck that it is just long enough.

    ReplyDelete
  5. MikeH,

    If the requested flow temperature is 65C, and you have d.2 set at 60 (Max), the MAXIMUM anti-cycling time would be 11.5 minutes from the above table. (Left hand column is requested flow temp, top row is d.2 setting, middle is the maximum anti-cycle time)

    Are you saying you get something different?

    ReplyDelete
  6. UpgradeMe,

    Yes, I would get 17 minutes - which the table gives for 60C. Weird, but as I say - convenient.
    What happens on yours? Is it actually as the table?

    ReplyDelete
  7. MikeH,

    Interesting. I get as per the table. Does anyone else reading get the same/different?

    It sounds like either there is an 'offset' setting somewhere, the table changed in different firmware revisions or perhaps the VRC430 adding another dimension to the anti-cycle equation!?

    I wonder if there are version numbers printed on the main boards we could compare!?

    ReplyDelete
  8. I to could do with a longer time at higher flow temps like MikeH but my 428 behaves the same as the table

    ReplyDelete