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

Vaillant BASV0 config #196

Closed
xxxturboxxx opened this issue Nov 11, 2020 · 5 comments
Closed

Vaillant BASV0 config #196

xxxturboxxx opened this issue Nov 11, 2020 · 5 comments

Comments

@xxxturboxxx
Copy link

xxxturboxxx commented Nov 11, 2020

I was using a Vaillant VRC700 controller on my heating system and I was able to log all the ebus data. 2 weeks ago I changed the controller to a VRC720f which sends the data to its radio receiver which is connecet to the ebus.

The 15.700.csv did not work obviously and ebusd could not find a suitable config. Therefor I adapted the 15.700.csv and renamed it to 15.basv0.csv which worked fine for a while. But now I got some errors (see log).

What could be the reason for that an ho can I solve that

020-11-23 11:28:11.028 [main notice] ebusd 3.4.v3.3-51-g57eae05 started with full scan
2020-11-23 11:28:11.050 [bus notice] bus started with own address 31/36
2020-11-23 11:28:11.055 [bus notice] signal acquired
2020-11-23 11:28:19.315 [bus notice] new master 10, master count 2
2020-11-23 11:28:19.338 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2020-11-23 11:28:21.051 [main notice] starting initial full scan
2020-11-23 11:28:33.234 [main error] scan config 15: ERR: wrong symbol received
2020-11-23 11:28:37.763 [main error] scan config 52: ERR: CRC error
2020-11-23 11:28:44.869 [bus notice] new master 71, master count 3
2020-11-23 11:28:44.896 [bus notice] new master 03, master count 4
2020-11-23 11:28:44.896 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2020-11-23 11:28:50.433 [bus notice] scan 08: ;Vaillant;HMU01;0305;8802
2020-11-23 11:28:50.433 [update notice] store 08 ident: done
2020-11-23 11:28:50.433 [update notice] sent scan-read scan.08 QQ=31: Vaillant;HMU01;0305;8802
2020-11-23 11:28:50.433 [bus notice] scan 08: ;Vaillant;HMU01;0305;8802
2020-11-23 11:28:50.441 [main notice] read common config file vaillant/scan.csv
2020-11-23 11:28:50.442 [main notice] read common config file vaillant/broadcast.csv
2020-11-23 11:28:50.443 [main notice] read common config file vaillant/general.csv
2020-11-23 11:28:50.447 [main notice] read scan config file vaillant/08.hmu.csv for ID "hmu01", SW0305, HW8802
2020-11-23 11:28:50.451 [main notice] found messages: 62 (0 conditional on 0 conditions, 0 poll, 10 update)
2020-11-23 11:28:51.339 [update notice] received unknown MS cmd: 1076b512030f0001 / 0704030090011403
2020-11-23 11:28:57.562 [main error] scan config 15: ERR: CRC error
2020-11-23 11:29:02.538 [main error] scan config 52: ERR: CRC error
2020-11-23 11:29:05.374 [main error] scan config 76: ERR: CRC error
2020-11-23 11:29:13.101 [update notice] received unknown MS cmd: 1052b5230103 / 0f930100800080008000809301c87c01
2020-11-23 11:29:21.293 [main error] scan config 15: ERR: CRC error

@xxxturboxxx xxxturboxxx changed the title Vaillant VRC720f / BASV0 config Vaillant VRC720f / BASV0 config CRC error Nov 23, 2020
@xxxturboxxx xxxturboxxx changed the title Vaillant VRC720f / BASV0 config CRC error [Gelöst] Vaillant VRC720f / BASV0 config CRC error Nov 28, 2020
@xxxturboxxx
Copy link
Author

Nachdem mir leider niemand helfen konnte/wollte bin ich der Sache selbst auf den Grund gegangen.
Meine Vermutung ist, dass durch den Wechsel des Reglers dies in irgendeiner Form die Einstellung des Pottis am Esera-Koppler beeinflusst hat. Nach erneutem einstellen des Pottis funktioniert jetzt wieder alles wie gehabt.

Man könnte nun die 15.basv0.csv mit in die Online-config-Datenbank mit übernehmen. Diese ist wie gesagt identisch zur 15.700.csv und müsste nur umbenannt werden.

@john30
Copy link
Owner

john30 commented Jan 10, 2021

bitte in Zukunft nicht alles hier und in ebusd doppeln
funktionieren alle Nachrichten der 700.csv?

@john30 john30 reopened this Jan 10, 2021
@john30 john30 changed the title [Gelöst] Vaillant VRC720f / BASV0 config CRC error Vaillant BASV0 config Jan 10, 2021
@xxxturboxxx
Copy link
Author

bitte in Zukunft nicht alles hier und in ebusd doppeln
funktionieren alle Nachrichten der 700.csv?

Ja, es funktioniert alles wie vorher.

@splashmak
Copy link

splashmak commented Jan 17, 2021

Hello,
I did the exact same thing with the 720f regulator and even if a lot of things are ok, everything is not working :

The main issues for me are related to the temperature setpoint modification.
To achieve that I see 2 posibilities : (1) set the regulator to manual mode & (2) automatic mode "veto" temp command

  1. Ok to set the mode with z1OpMode parameter but can't modify the z1ActualRoomTempDesired
  2. Can not modify the temperature mode s1SFMode until I make a physical change on the 720f. After that even if I cancel the action it's accessible for some hours and everything work like a charm( I don't know how lang precisely yet). Difference is that when manually (with regulator action) doing it I have to set the action duration which is not done when using ebusd

By the way the z1DayTemp is not accessible when the z1NightTemp is. I check the first memory zones to find it but yeah ... maybe you have a trick to find it ?

readall_result.txt

@ppnacho
Copy link

ppnacho commented Aug 31, 2023

I have a VRC720f module controller and with ebusctl i don't appear in the answer console.
I only can see the next items,
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0902;HW=5103", loaded "vaillant/08.hmu00.full.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0607;HW=5103"

What .csv files must link to slave #2 and #9?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants