-
Notifications
You must be signed in to change notification settings - Fork 272
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deciphering VR65 device messages #31
Comments
I think I can guess the messages because I did:
And I manually turned the CH and DHW valves on and off and then I got these messages! |
Update! I forced a Hot water and heating demand via my VRT350, and from there I could interpret the messages the VR65 is broadcasting, this is my best guess what these mean, when these messages are active they are constantly broadcast: #### Demand StatesCYL thermostat OFF, (no DHW Demand), also when everythings off CYL thermostat ON, (DHW Demand): CH Demand: No CH Demand: #### Valve StatesDHW Valve Open: DHW Valve Closed: CH Valve Open: CH Valve Closed: This could be the start of the csv (64.vr65.csv?):
How could I put ths into the csv format? |
as far as I can see it from the manual of the VR65, there is only a DHW demand, but no CH demand. So your findings are not entirely correct yet. BTW: you should be able to read the valve setting via PositionValveSet if you have the right BAI |
This is the potential CSV file for the findings:
you'll have to add the following line to your _templates.csv: |
Ah ok. Diverter position is set to mid position. So both can open simultaneously. |
Also just to clarify, the DHW demand is received via the CYL thermostat (it is a analogue device connected to the storage tank instead if the NTC/VF1. Ch demand is received by the vrt350 |
Hi John, I tried the CSV file and I got this:
I tried changing "V6500" to "v6500" but it didn't make a differece |
what name did you give the CSV and where did you put it? |
I called it "64.vr65.csv" I put it in /etc/ebusd/vaillant/ Installed ebusd via the deb package so it should have the correct PATH set |
you need to name it "64.v65.csv" instead |
Ahhhhh, I've done that now and restarted ebusd. I now get: [main error] error reading scan config file /etc/ebusd/vaillant/64.v65.csv for ID "v6500", SW0107, HW7602: ERR: invalid part type](url) |
I changed the CSV file to this after doing some testing:
The file is now read but I now get this:
Then afterwards I get:
When I see 'unknown' in the State, this is the message it is interpreting:
So maybe this might need adjustment in _templates.csv:
I will monitor the log and see when demand switches on what happens. |
I now got this:
Then it changed to: Now it changed to this:
But the command doesn't change:: Should there be a separate one to say both valves are open? This is still unknown, it always comes up regardless of the state of the v65, it seems to be the BAI talking to the v65? As I have a vrDIALOG module I will connect it and monitor the messages and compare them to see what the correct ones are |
Ok further testing:
But:
This should be: I have changed the line in _templates.csv to this: This now works! When both valves open, v65 state changes to both, when Ch valve is open, the state changes to heat. When dhw valve opens, the state changes to water |
okay great. thanks for testing the values, I just put in the values that seemed correct according to your first note. Anyway, I'll add the CSV and the templates to the repository. |
solved with e4c9de5 |
Hi John! It's been a long time!
My burner's heat exchanger failed 馃憥 so I had it replaced with the same model, but it's a completely different device with a different PCB and newer SW. I decided to update to the new ebusd and configuration files and my new burner works well with it. I see a lot of improvements and ebusd also runs very fast, so thanks!
Not sure if you remember but there was a slave device that did not have any messages for it in the newest vrDIALOG810.mdb that I had, which was strange because when I run vrDIALOG810 it actually can see my VR65 device and read it.
The VR65 is basically a device that the burner controls. It connects my DHW and CH circuits (two 2 port valves). It also has a sensor that detects DHW demand in my storage tank (a DHW thermostat on the storage tank completes the circuit when there is demand) which tells the burner there is DHW demand. There is also a VF1 (NTC) sensor on it but I have not used it as those are normally fitted to UniStor's.
I have been monitoring the ebusd log file trying to translate the unknown MS cmd: messages sent by the VR65 by seeing what the other circuits the BAI and 350 are doing at the time.
This is my scan result:
The V6500 is the VR65 device.
These are the unknown messages in the log:
You can see for 0200, 0232 and 0264, the message has a 1 or 0, so this must mean DHW Demand 1 or 0, DHW ValveState 1 or 0, and CH ValveState 1 or 0.
I'm not sure what "1008b512020064 / 00" does but I think maybe it's telling the CH ValveState to close?
"0364b5120202fe / 06fe000080ffff" I still don't know either.
Do you think I could start writing a CSV for this device? If so would you be able to advise me on how I can do this?
Also I get this error "[update error] unable to parse bai DateTime from 1008b5040100 / 0a00ffffffffffffff0080: ERR: argument value out of valid range". The BAI device has never understood DateTime, only vdatetime I think.
The text was updated successfully, but these errors were encountered: