Pulling parameters from a Cascade Aerotherm Plus Heat pump #1288
Replies: 3 comments 13 replies
-
So generally when you connect two similar devices (like boilers or heat pumps in cascade mode) which otherwise would try to secure the same ebus address, Vaillant solve this by having you install a VR32 bus coupler to give the second device a different address. There is no way ebusd can 'guess' what device is behind a VR32 so there are no VR32 config files per say. I would say your heat pump behind the VR32 is presenting as address 18. If you search this forum, you should be able to see how you can rename the heat pump file to this address. I've posted a few responses on the forum. (I am short of time currently but if you are struggling, re-post and I'll see about tracking these down). You will likely also need to change the latency parameter as the VR32 does not play well with the official ebus spec |
Beta Was this translation helpful? Give feedback.
-
So, in a little bit more detail:
Basically, ebusd matches configuration files on start-up to the slave address of device (boiler, heat pump, controller etc.) and ID (and SW/HW versions if necessary) - see the wiki on auto config naming - https://github.com/john30/ebusd/wiki/4.7.-Automatic-configuration. Because any device could sit behind a VR32 - a boiler, heat pump or an air recovery system as examples, there is no way ebusd can work this out so consequently there are no vr32 configuration files in the repository. But since you know it's your heat pump, creating your own VR32 file (18.v32.csv) with the message definitions for a heat pump will allow the ebusd auto config to pick this file up and all should work fine! Here a few threads I've commented on where it seemed to work in a similar situation to yours: |
Beta Was this translation helpful? Give feedback.
-
Oh - and it's the ebus adapter you have on 31/36 (Looks like you've got a nice setup btw!) |
Beta Was this translation helpful? Give feedback.
-
Hi, I have 2 Aerotherm Plus 12 KW heat pumps that i am trying to pull data from. I can successfully pull data and see 1 heat pump when I do a scan (ebusctl info) but I cant (I dont think) can see the second heat pump.
You can see on address 36 it just says scanning but does not return a result. Maybe this is second heat pump. Is there a way to resolve what that is on address 36?
Doing a full scan I get this and that address does not appear.
Any help would be appreciated. I dont see any history of anyone with a cascade configuration using ebusd.
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions