Once ignited, the boiler (Tricom ProTherm 40-50 CI, 4 years old) in my vented system will not go off, causing it to eventually trigger the overheat cutoff (and much noise from my pump and pipework due to the insanely hot water inside).
I understand that a properly functioning boiler will ignite for maybe 20 mins to heat up the water and then automatically switch off until the heat has dropped enough to warrant coming back on briefly (e.g. 5 mins) to maintain the heat. This intermittent igniting should continue while I have my heating switched on.
This clearly isn't happening in my system. I have managed to simulate it and gain correct operation, by manually toggling my heating on and off to maintain the right temperature, which suggests that there is nothing else at fault besides my boiler.
Is this a correct assumption? All my rads have TRVs, and I do have a bypass, so I guess when all the rads are hot enough they close and the hot water goes round the bypass, which the boiler should sense is too hot. Is there any way to tell if it is the thermostat or the PCB at fault?
(Apologies to anyone who wasted any time reading my other thread. As you can see, I have streamlined my problem somewhat now.)
I understand that a properly functioning boiler will ignite for maybe 20 mins to heat up the water and then automatically switch off until the heat has dropped enough to warrant coming back on briefly (e.g. 5 mins) to maintain the heat. This intermittent igniting should continue while I have my heating switched on.
This clearly isn't happening in my system. I have managed to simulate it and gain correct operation, by manually toggling my heating on and off to maintain the right temperature, which suggests that there is nothing else at fault besides my boiler.
Is this a correct assumption? All my rads have TRVs, and I do have a bypass, so I guess when all the rads are hot enough they close and the hot water goes round the bypass, which the boiler should sense is too hot. Is there any way to tell if it is the thermostat or the PCB at fault?
(Apologies to anyone who wasted any time reading my other thread. As you can see, I have streamlined my problem somewhat now.)