New binding - Rego 6xx based heat pumps

PeteW · June 6, 2017, 6:59am

IT’S WORKING

Had a few issues, I added an inverter, left the RX connected to TX and started to see random values returned again. Really weird, so removed the inverter, tried again, started ok, then got random values again…really strange!

I then just attached TX to RX on my rpi pins (ie, connected pin 14 to 15) and left it for a while, all consistent.

Then i realised it was noise!!! Which is why it kept receiving too many bytes and the return values were random. I put a resistor on the 3v and 5v inputs to the TXS018E and hey presto, everything started working!!!

I’m getting the first couple of values into my UI…

Can’t thank you enough @crnjan for all your help on this one. I’m just a novice but got there in the end…!

Now am adding the additional parameters and will build a more solid board. Just using a prototype board at the moment.

Pete

PeteW · June 6, 2017, 7:04am

Here’s an extract from my logs…clearly I’ve not mapped all the parameters yet, that’s my next step!

 could be found.
2017-06-06 06:58:51.217 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Reading value for channel 'sensorValues#radiatorReturn' ...
2017-06-06 06:58:51.299 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Sending 81020004090000000D
2017-06-06 06:58:51.548 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Received 0100023537
2017-06-06 06:58:51.550 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Got value for 'sensorValues#radiatorReturn' = 309
2017-06-06 06:58:51.552 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Reading value for channel 'sensorValues#outdoor' ...
2017-06-06 06:58:51.561 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '30.89999999999999857891452847979962825775146484375' for item 'GT1_Temperature' to handler for channel 'regoheatpump:ipRego6xx:ivt:registers#radiatorReturnGT1', because no thing with the UID 'regoheatpump:ipRego6xx:ivt' could be found.
2017-06-06 06:58:51.633 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Sending 810200040A0000000E
2017-06-06 06:58:51.810 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Received 0100006F6F
2017-06-06 06:58:51.811 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Got value for 'sensorValues#outdoor' = 111
2017-06-06 06:58:51.817 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '11.0999999999999996447286321199499070644378662109375' for item 'GT2_Temperature' to handler for channel 'regoheatpump:ipRego6xx:ivt:registers#outdoorGT2', because no thing with the UID 'regoheatpump:ipRego6xx:ivt' could be found.
2017-06-06 06:59:51.827 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Reading value for channel 'sensorValues#radiatorReturn' ...
2017-06-06 06:59:51.909 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Sending 81020004090000000D
2017-06-06 06:59:52.240 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Received 0100023537
2017-06-06 06:59:52.241 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Got value for 'sensorValues#radiatorReturn' = 309
2017-06-06 06:59:52.244 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Reading value for channel 'sensorValues#outdoor' ...
2017-06-06 06:59:52.249 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '30.89999999999999857891452847979962825775146484375' for item 'GT1_Temperature' to handler for channel 'regoheatpump:ipRego6xx:ivt:registers#radiatorReturnGT1', because no thing with the UID 'regoheatpump:ipRego

PeteW · June 6, 2017, 8:06am

Feeds mostly looking good, but for some reason I’m getting -ve numbers for a couple of values.

You seen that?

Hot Water' is regoheatpump:serialRego6xx:6c8a2d42:sensorValues#hotWater
Radiator Forward is  regoheatpump:serialRego6xx:6c8a2d42:sensorValues#radiatorForward

crnjan · June 6, 2017, 8:13am

Congratulations! Really awesome!

Can you please give some more info about your final wiring? So you didn’t need to invert the Tx node coming from rego unit?

AFAIK rego 6xx units use different mapping (addresses) for registers so please check if mappings are correct. If they don’t match, I can add an additional map to the binding, but would need the mapped values

Regarding hot water - do you have boiler integrated within the heat pump? Otherwise you should use the external hot water channel (you need to enable “show more” if doing it through the PaperUI).

And can you please share the logs regarding the negative values? As far as I tested, “strange” values are returned for channels, not supported by the rego unit or not setup (i.e. if you request indoor temp, but don’t have that sensor installed, since it is optional…).

crnjan · June 6, 2017, 8:35am

Just in case - please note not all channels are supported for each thing - the list of supported channels can be seen here. And the list of available channels depends on your setup. In your particular case:

hot water - I guess you have an external boiler and therefore you need to use the external hot water channel,
radiator forward - do you have combined heating (radiator/floor)? Otherwise I guess you don’t have the (optional) sensor (GT4 I believe) in place and therefore you are reading back “strange” values.

Please let me know if my assumptions are correct

PeteW · June 6, 2017, 9:15am

I did need to invert the RX from the Rego. Used a 74HC00N NAND gate to do the inverting.

Sorry, have no circuit drawing tools or skills ;0(

So my setup is:

RPI serial ports 14 (Tx) and 15 (Rx)
TXS018E converter (3v to 5v) (resistors on 3v and 5v V+ inputs)
74HC00N inverter

Data sent from Pi on port 14 (Tx)
Received by TXS018E on pin A4 (+3v side)
Converted to 5v by TXS018E and output on pin B4 (+5v side)
pin B4 connected to Rego DB9 blue wire (Rx pin2)

Data returned from Rego on DB9 yellow wire (Tx pin3)
Received by 74HC00N and inverted
Received by TXS018E on pin B5 (+5v side)
Converted to 3v by TXS018E and output on pin A4 (+3v side)
…back to RPI on port 15

I have also connected the DB9 +5v and GND wires to the GPIO PI terminals to give it the power it needs

You’re right - i don’t have an internal hot water tank, so external hot water channel is what i need.

I just have underfloor heating, no radiators, so that’s probably why radiator forward is not valid. I was thinking this was the flow value for the heating, as I was looking for ‘flow’ and ‘return’. Just picked up the wrong one.

I’ll take a look at all the data on the heat pump front panel tonight and let you know which ones have been mapped and which ones aren’t. I’ve got a Worcester Bosch Greenstore heat pump, intalled around 2011.

Will report back on all the logs tonight when I’m home again.

crnjan · June 6, 2017, 10:36am

Thanks for the info, I was a bit surprised since I thought you didn’t need to invert the Tx node, makes sense now.

The only thing I’m not sure if I got it right is the “TXS018E converter (3v to 5v) (resistors on 3v and 5v V+ inputs)” - why did you need to put the resistors for?

And I’m also not sure that “I have also connected the DB9 +5v and GND wires to the GPIO PI terminals” is a good idea. I’m not an expert in electronic, but I’d say that since rpi and heat pump have their own power sources there should be no need (and I would strongly advice against it) to interconnect them… Or maybe I just got it wrong… Can you take a picture of your setup?

PeteW · June 6, 2017, 10:44am

Yes, I’ll take a pic tonight.

I used the resistors as I was getting a lot of noise on the Tx and Rx. When I added them, it all started working ok.

I was not sure if I needed to connect the +5v on the DB9. I thought it needed that to work, but I will try without too.

crnjan · June 6, 2017, 11:23am

I would expect wiring to look something like this:

Comments?

PeteW · June 6, 2017, 11:50am

Nice

Almost what I have…the only difference is that i have my +5v source for TX018E side B coming from the RPI, as it can supply both +3 and +5. Do you think i should really be sourcing that from the D9 of the Rego? Might be safer!

Pete

crnjan · June 6, 2017, 12:51pm

A bit modified diagram, based on a quick look into the datasheet:

My suggestion would be to separate rego and rpi side as much as possible, in your case only keep GND connected together, both 7400 and TXS0108E’s B side should be powered by the rego unit (+5V). As you can see from the diagram, I’d say you don’t need to connect resistors to power supply pins as you described (nor I found any evidence within the datasheet that they might be needed). There only should be a pull down resistor on the OE pin so outputs are enabled when power supply is stable.

That are my two cents, won’t bother you anymore with suggestions, but wouldn’t like that anything happens to your controller unit (nor there is any guarantee that my suggestions are 100% safe ).

PeteW · June 6, 2017, 1:00pm

Really appreciate the suggestions. These are expensive bits of kit, so anything I can do to make double-sure it’s ok is a bonus - so thanks!

I think keeping the Pi and Rego sides completely separate is a good shout. Will tune.

Am so glad I have got this going with my prototype board. Will need to do something more robust, but have had fun so far!

PeteW · June 7, 2017, 9:32pm

Have updated my hardware to use the +5v side for components connected to the Rego and +3v side from connections to the rpi. So I’ve isolated them, so hopefully thats a bit safer and will protect my rpi and Rego.

Gone through all the item mappings, here what I have now…

useful data mappings you have implemented here, great stuff.

Couple of things to clarify…

What’s the difference between frontPanel#alarmLamp and deviceValues#alarm ?

I think ‘Switch Valve’ will be on when generating hot water, but I would like to know if it is supplying underfloor heating or DHW. Is there a way to tell this, it’s a 3 way valve I think (off, DHW only, Heating only, both) Could this be something to do with Switch Valve 2?

Don’t think I use the others that are not mapped, but will keep you up to date with my working.

I’ve managed to get the real-time status of each of these values for now, but I’ll be wanting to log some history and produce some graphs, esp the temps. Any recommendations on the best way to do this? I guess I should keep request interval to 60 seconds, that should be accurate enough.

PeteW · June 8, 2017, 5:30am

Actually, just read the openHab section on persistance, so i need to decide what method i want to use to store the data. I’ve also got an OpenEnergyMonitor which has a very good series data store in https://emoncms.org Am already using to log electricity consumption and has some great graphs / widgets, think it can receive MQTT messages there. May try that.

crnjan · June 8, 2017, 7:08am

Glad to hear it is working!

Regarding wiring - I’m curious, did you remove the resistors on 3v/5v inputs? Or do you still need them?

Yes, there are a lot of channels that a rego 6xx unit provides, I shared a link in my previous posts, where you can see all. As pointed out, some channels might not be available for your heat pump, depending on your model and setup, while others provide info that is not interesting or just too static - up to you to add those that you see fit

What’s the difference between frontPanel#alarmLamp and deviceValues#alarm ?

I’m not 100% sure, I believe both provide same information coming from different registers… The frontPanel# ones are actually one to one mapping between the lights you have on your heat pump’s front pannel:

heat pump
additional heat
hot water (DHW)
alarm

The “Switch Valve” is actually a 2 way valve and can either heat DHW or heating water, so only two states are possible; if both are needed, DHW has priority over heating water (i.e. floor heating). I have a mapping in place where in one case I see:

when switch valve is in position of heating water (i.e. floor heating) or:

when switch value is set to heat DHW.

For completeness, please see my setup (iPhone client, screens stitched together):

I can share my .items file for reference, please let me know.

I use InfluxDB and Grafana for storing data, it is really powerful and easy to use, there is also a great tutorial on hot to set it up.

I have a 30 seconds refresh interval in place, running for a couple of months without any problems, sample grafana chart can be seen here also:

Lastly, looking into provided screenshot, switch valve 2 and compressor speed are not available for rego 6xx units, please see list of supported channels.

Also, the cold fluid out value looks a bit strange - 67.9? Do you have it mapped correctly?

PeteW · June 8, 2017, 10:24am

Thanks for this. Like your graphs. I’ll give InfluxDB a try.

I kept the resistors on, as when i took them off I started to get noise again - lots of extra data.

I’ll review your link again with the list of channels, just to see if there are any other interesting data points I can get from my Greenstore.

If you wouldn’t mind sharing your .items file that would be good. I’d like to see how you’ve setup your Switch Valves. Mine currently just says ‘on’ or ‘off’ - maybe i need to change the item type.

I’m going to double-check my cold fluid values and mapping. They do look really high. Will report back.

crnjan · June 8, 2017, 7:15pm

I have a mapping in place within the .sitemap file for the switch value:

Text label="Switch valve [Heating water]" icon="radiator" visibility=[regoheatpump_ipRego6xx_ivt_deviceValues_switchValve == OFF]
Text label="Switch valve [Hot water]" icon="faucet" visibility=[regoheatpump_ipRego6xx_ivt_deviceValues_switchValve == ON]

to map on/off values.

A quick word on my setup - I have no .items or .thing file in place, only the .sitemap. Things and channels are setup as following:

first set “simple mode” to on within PaperUI | Configuration | System | Item Linking and hit Save,
add the rego thing within the PaperUI, make sure to set thing Id to some string, I use “ivt”,
add channels

Using this approach you now have a list of channels setup and they seem to have the following naming convention:

<binding>_<thing>_<thingid>_<group>_<channel>

I use the ipRego6xx thing and “ivt” as the thing id, as described above, so using above approach, I get a list of channels:

regoheatpump_ipRego6xx_ivt_sensorValues_outdoor,
regoheatpump_ipRego6xx_ivt_sensorValues_externalHotWater,
regoheatpump_ipRego6xx_ivt_sensorValues_radiatorReturn,
...

and than I use those in the sitemap:

sitemap house label="House" {
	Frame {
		Text label="IVT Greenline E11" item=regoheatpump_ipRego6xx_ivt_sensorValues_outdoor icon="boiler_viessmann" {
			Frame label="Sensor Values" {
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_outdoor
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_externalHotWater
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_radiatorReturn
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_radiatorForward
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_compressor
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_heatFluidOut
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_heatFluidIn
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_coldFluidOut
				Text item=regoheatpump_ipRego6xx_ivt_sensorValues_coldFluidIn
				Text label="Charts" icon="line" {
					Frame {
						Switch item=Combo_From_HP_Charts mappings=[6HOUR="6 Hours", 12HOUR="12 Hours", DAY="Day", WEEK="Week"]
						Image visibility=[Combo_From_HP_Charts == 6HOUR] refresh=60000 url="http://localhost:3000/render/dashboard-solo/db/heat-pump?panelId=1&width=600&height=300&from=now-6h&to=now&theme=light"
						Image visibility=[Combo_From_HP_Charts == 12HOUR] refresh=300000 url="http://localhost:3000/render/dashboard-solo/db/heat-pump?panelId=1&width=600&height=300&from=now-12h&to=now&theme=light"
						Image visibility=[Combo_From_HP_Charts == DAY] refresh=3000000 url="http://localhost:3000/render/dashboard-solo/db/heat-pump?panelId=1&width=600&height=300&from=now-1d&to=now&theme=light"
						Image visibility=[Combo_From_HP_Charts == WEEK] refresh=300000 url="http://localhost:3000/render/dashboard-solo/db/heat-pump?panelId=1&width=600&height=300&from=now-1w&to=now&theme=light"
					}
				}
			}
			Frame label="Control data" {
				Text item=regoheatpump_ipRego6xx_ivt_controlData_radiatorReturnTarget
				Text item=regoheatpump_ipRego6xx_ivt_controlData_radiatorReturnOn
				Text item=regoheatpump_ipRego6xx_ivt_controlData_radiatorReturnOff
				Text item=regoheatpump_ipRego6xx_ivt_controlData_radiatorForwardTarget
				Text item=regoheatpump_ipRego6xx_ivt_controlData_addHeatPower
			}
			Frame label="Device values" {
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_radiatorPump
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_heatFluidPump
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_coldFluidPump
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_compressor
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_additionalHeat3kW
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_additionalHeat6kW
				Text item=regoheatpump_ipRego6xx_ivt_deviceValues_alarm
				Text label="Switch valve [Heating water]" icon="radiator" visibility=[regoheatpump_ipRego6xx_ivt_deviceValues_switchValve == OFF]
				Text label="Switch valve [Hot water]" icon="faucet" visibility=[regoheatpump_ipRego6xx_ivt_deviceValues_switchValve == ON]
			}
			Frame label="Front Panel" {
				Text item=regoheatpump_ipRego6xx_ivt_frontPanel_heatPumpLamp
				Text item=regoheatpump_ipRego6xx_ivt_frontPanel_additionalHeatLamp
				Text item=regoheatpump_ipRego6xx_ivt_frontPanel_hotWaterLamp
				Text item=regoheatpump_ipRego6xx_ivt_frontPanel_alarmLamp
			}
			Frame label="Status" {
				Text item=regoheatpump_ipRego6xx_ivt_status_lastErrorTimestamp
				Text item=regoheatpump_ipRego6xx_ivt_status_lastErrorType
			}
		}
	}
}

I used this approach a lot when developing the binding when I was adding/removing the thing a lot. If you use i.e. “bosch” as your thing id, you should have something like this:

regoheatpump_serialRego6xx_bosch_sensorValues_outdoor

This way you can (more or less) easily add/remove the thing using PaperUI while have the same .sitemap - in case of course you need to do so in the first place

PeteW · June 8, 2017, 8:07pm

Great, thanks for sharing. This is really helping.

I’ve got the Switch Valve working. I think I’ll also add an extra piece of logic so it doesn’t display at all if the heat pump is not generating heat. ie, not producing hot water or heating water.

Have also got InfluxDB and Grafana up and running, going to capture some data tonight/tomorrow.

Will report back!

PeteW · June 9, 2017, 5:23am

On the ColdFluidOut value, its still really high. Just looked in the logs, and that’s what’s coming from the heat pump…

2017-06-09 05:13:40.171 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Got value for 'sensorValues#coldFluidOut' = 833

Just checked the temps front panel of my heat pump, and it is dsplaying:

Heat TrFluid Out (GT8) 83.3
Heat TrFluid In (G9) 15.2

If I look at the history in Grafana, ColdFluidOut looks to remain between 81 and 84 all night

Do you think my heat pump is running way too hot? (not really an OpenHab question!)

crnjan · June 9, 2017, 6:52am

Lets start with a disclaimer - I’m no heat pump expert , but my understanding is:

Cold fluid in/out - this is the temperature in medium where heat pump is taking temperature/energy from - i.e. in ground collector. In/out are referenced from the heat pump:

cold fluid in (GT10) = fluid temperature coming into the heat pump,
cold fluid out (GT11) = fluid temperature coming from the heat pump

So when heat pump is operating, the cold fluid in should have a bit higher value (temperature) as the one coming from the heat pump.

On the other hand, the heat fluid in/out is the temperature in medium (fluid) that heats your DHW or floor heating (depends on the switch valve). In/out are again referenced from the heat pump:

heat fluid out (GT8) = fluid coming from the heat pump,
heat fluid in (GT9) = fluid coming back to the heat pump

Naturally, when heat pump is operating, heat fluid out has slightly higher temperature than when it returns.

Your mapping should be like this:

GT1 = sensorValues#radiatorReturn,
GT2 = sensorValues#outdoor,
GT3 = sensorValues#externalHotWater,
GT6 = sensorValues#compressor,
GT8 = sensorValues#heatFluidOut,
GT9 = sensorValues#heatFluidIn,
GT10 = sensorValues#coldFluidIn,
GT11 = sensorValues#coldFluidOut

Heat TrFluid Out (GT8) 83.3
Heat TrFluid In (G9) 15.2

As you can see from above mapping, this is related to the “heat transfer fluid”, while the value:

2017-06-09 05:13:40.171 [DEBUG] [tpump.handler.Rego6xxHeatPumpHandler] - Got value for ‘sensorValues#coldFluidOut’ = 833

is referencing the “cold” fluid circuit - sensorValues#coldFluidOut = GT11.

Can you please double check values displayed directly on your heat pump (GTx) and based on the above mapping check that values match? I.e.

GT1 (heat pump display) = sensorValues#radiatorReturn (OH2 displayed value)