Skip to main content

Buderus Logamatic & pool heating and a "dumb" thermostat

I had a number of posts about our Buderus heating system in the past, and I had a recent project I wanted to document, both for my future self and for those poor souls who seek solution for this or a similar problem.

So my Buderus has a heating circuit that heats a pool and the "need for heat" signal is provided by a simple relay in the pool system: when the relay is closed, that indicates it needs heat. When it's open, heat is not needed.

This is basically the same you would get from a "dumb" thermostat, whenever temperature is below the threshold the relay is closed, otherwise it is opened. Furnaces I've encountered in the past always used signals like that.

Not with Buderus though, in it a "temperature controlled" zone needs a MEC2 or a BFU installed, both Buderus products for serious $$$. These devices operate on a 1200 baud serial bus and are actually digital devices that connect to the Buderus control system.

Buried within the various Heating Circle options however I finally found a solution (in the not-so-great Buderus manual, chapter 15).

The elements of the solutions were:

  • I am using the day/night mode of the circuit, in day mode it is running, in night mode it is shut down.
  • To achieve that set setback type to "shutdown" (chapter 15.9), e.g. the circuit shuts down in setback (e.g. night) mode.
  • Then, set the "External changeover mode" (chapter 15.23), to "Day/night via terminals WF1 and WF3", this means that if the terminals WF1 and WF3 are closed (via the relay), the circuit switches to day mode, otherwise it remains in night mode.
  • The last change was that I had to disable frost protection (e.g. set the frost protection temperature to -20 degrees), as I didn't have a temperature sensor on this circuit, which means the assumed temperature is 0 degrees. This means that the circuit would remain running even if the relay is open.
That's roughly it. Took me a while to figure out, especially the last point. Now, I'll just have to install an Arduino/RPi to control that pin, but that's a different chapter.
Labels:

Comments

Post a Comment

Popular posts from this blog

syslog-ng fun with performance

I like christmas for a number of reasons: in addition to the traditional "meet and have fun with your family", eat lots of delicious food and so on, I like it because this is the season of the year when I have some time to do whatever I feel like. This year I felt like doing some syslog-ng performance analysis. After reading Ulrich Deppert's series about stuff "What every programmer should know about memory" on LWN, I thought I'm more than prepared to improve syslog-ng performance. Before going any further, I'd recommend this reading to any programmer, it's a bit long but every second reading it is worth it. As you need to measure performance in order to improve it, I wrote a tool called "loggen". This program generates messages messages at a user-specifyable rate. Apart from the git repository you can get this tool from the latest syslog-ng snapshots. Loggen supports TCP, UDP and UNIX domain sockets, so really almost everything can be me...
17 comments
Read more

syslog-ng OSE 2.1 released

I have just uploaded the first release in the syslog-ng Open Source Edition 2.1 branch to our website. It is currently only available in source format at this location: http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src This release synchronizes the core of syslog-ng to the latest PE version and adds the SQL destination driver. This is an alpha release and thus might be rough around the edges, but it basically only contains code already tested in the context of the Premium Edition. The SQL functionality requires a patched libdbi package, which is available at the same link. We're going to work on integrating all our libdbi related patches to the upstream package. If you want to know how the SQL logging works, please see the Administrator's Guide or our latest white paper Collecting syslog messages into an SQL database with syslog-ng. The latter describes the Premium Edition, but it applies to the Open Source one equally well.
6 comments
Read more

syslog-ng 3.2 changes

I've just pushed a round of updates to the syslog-ng 3.2 repository, featuring some interesting stuff, such as: SQL reorganization: Patrick Hemmer sent in a patch to implement explicit transaction support instead of the previous auto-commit mode used by syslog-ng. I threw in some fixes and refactored the code somewhat. Configuration parser changes: the syntax errors produced by syslog-ng became much more user-friendly: not only the column is displayed, but also the erroneous line is printed and the error location is also highlighted. Additional plugin modules were created: afsql for the SQL destination, and afstreams for Solaris STREAMS devices. Creating a new plugin from core code takes about 15 minutes. I'm quite satisfied. With the addition of these two modules, it is now possible to use syslog-ng without any kind of runtime dependency except libc. The already existing afsocket module (providing tcp/udp sources & destinations) is compiled twice: once with and once withou...
4 comments
Read more