Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ADD] VR39 support #226

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions ebusd-2.1.x/de/vaillant/08.v3x00.csv
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# type (r[1-9];w;u),circuit,name,[comment],[QQ],ZZ,PBSB,[ID],field1,part (m/s),datatypes/templates,divider/values,unit,comment
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

file name should be 08.v3x.csv as trailing 0 are removed

#,v3x00,VR39,0020139898,,,,,,,,,,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what kind of circuit is this? is this a mixer or room controller? please note here

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://www.wolf-online-shop.de/Vaillant-VR39-Zusatzmodul-0020139898::38909.html

This is an interface ebus <> ProBus to connect old burners to ebus.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so it is targeting burners only and is only capable of talking to burners?

Copy link

@Silverstar Silverstar Jan 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The VR39 is an adapter for older burners, which do not have ebus but (in case of vaillant devices) an interface labelled "X6", to provide an ebus interface for ebus controllers.
The X6 interface is a proprietary vaillant serial interface, but there is some information public, e.g. https://old.ethersex.de/index.php/Vaillant_X6_Schnittstelle

I have a VR39 as well and would like to assist to get it supported. How can I provide useful data?
I have a Vaillant VC 136-E heater, currently controlled by a VRC410 (via the pin 7-8-9 interface), VR39 installed and an odroid sbc with the ebus adapter 3 installed. A VRC470 is available, but not installed, because I guess it is advantageous to analyse the VR39 alone first?

I attached some logs of the ebusd with and without the provided vr39 definition by rousseldenis. I'm unsure what's next. Grab/dump I guess, but I need some hints. Shall I install and configure the VRC470 and then run the ebusd logging for a while? Which options are necessary to be helpful?

ebusd_scan_VR39_with_first_definition.log
ebusd_scan_VR39_with_first_definition_with_lograw.log
ebusd_scan_VR39_without_definition.log
ebusd_scan_VR39_without_definition_with_lograw.log

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great @Silverstar !

Indeed, I've succeeded recognized VR39 with this first config file.

But, I didn't know how to "discover" features.

As I have currently some failures like 'No Oil', I suppose we can retrieve them through VR39. The link you gave is a first clue.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Long time, no see, I'm working again on getting the VR39 working with ebusd. I had to set up a new pi zero as the former sbc stopped working. I have now running it together with the VRC470 and I'm testing various configurations, which return useful values and want to strip them from those which return ERR.

@rousseldenis and @hallengreenn can you tell me how your VR39 are identifying themself on the ebus? I guess, that depending on the burner they are attached to, they will have different registers available and so we might need different configs for different burners with the vr39, so like vr39.vc136e, vr39.vc126, ... to address that.

Mine is "MF=Vaillant;ID=V3x00;SW=0118;HW=9902" on the VC 136 E and I'm wondering if there is a difference in SW / HW if on another burner (or is there any other value like a product ID?). If not, we might have to find another way to distinguish them - if necessary.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Silverstar The VR39 appears exactly the same as yours.

In fact, I think that interface should be unique on the bus.

I use only the commands from my VRC regulation and I haven't explored no more VR39 possible features

Copy link

@Silverstar Silverstar Jan 26, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your reply. I think that we might get some info about the burner only from the VR39, not from the VRC, so I'm interested to achieve some of the possibilities. I have tested all of the 08.bai... files against the VR39, made a list which items returned an error and which got a value back. Then I will check them against my burner which of those values match, because I already found differences in the different files, returning different values for the same named datapoint.
I actually found some datapoints which are error in one file and got a reply in another, as well as datapoints with values which are not in all of the others, so it will be a puzzle. :)

Which VRC do you have do you use?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a VRC 450 (I picked the 470 and adapted it, not found the time to do a PR for that)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bump...
I'm still at this, not much spare time for that but still willing to get this done. What I have found so far, that no other config fits completely or even to a large part and even the definition by rousseldenis don't match completely for me.

I'm wondering if I'm doing mistakes or if the vr39 just relays the data and so the addresses and data change depending on the connected burner, so same as with natively ebus equipped burners, some shared fields, some differ completely.
But how do the controllers know? My 470 is controlling the vc136e just fine through the vr39, and somehow they need to know how as well.

*r,,,,,,"B509","0D",,,,,,
*w,,,,,,"B509","0E",,,,,,
*wi,#install,,,,,"B509","0E",,,,,,
*ws,#service,,,,,"B509","0E",,,,,,
# ##### dia level 1 #####,,,,,,,,,,,,,
r,,CirPump,d.13 Circulation pump,,,,"7B00",,,onoff,,,Hot water circulation pump (via external module)
# ##### dia level 2 #####,,,,,,,,,,,,,
r;wi,,ReturnRegulation,d.17 Return regulation,,,,"0C04",,,onoff,,,heating flow/return regulation activation
r;wi,,HcPumpMode,d.18 CH pump mode,,,,"4904",,,UCH,0=post run;1=permanent;2=winter,,Pump mode
!include,errors.inc,,,,,,,,,,,,
!include,service.inc,,,,,,,,,,,,
11 changes: 11 additions & 0 deletions ebusd-2.1.x/en/vaillant/08.v3x00.csv
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# type (r[1-9];w;u),circuit,name,[comment],[QQ],ZZ,PBSB,[ID],field1,part (m/s),datatypes/templates,divider/values,unit,comment
#,v3x00,VR39,0020139898,,,,,,,,,,
*r,,,,,,"B509","0D",,,,,,
*w,,,,,,"B509","0E",,,,,,
*wi,#install,,,,,"B509","0E",,,,,,
*ws,#service,,,,,"B509","0E",,,,,,
# ##### dia level 1 #####,,,,,,,,,,,,,
r,,CirPump,d.13 Circulation pump,,,,"7B00",,,onoff,,,Hot water circulation pump (via external module)
r,,Flame,Flame,,,,"0500",,,UCH,240=off;15=on,,flame
!include,errors.inc,,,,,,,,,,,,
!include,service.inc,,,,,,,,,,,,