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 support for basv3 VRC 720/3f #462

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

burmistrzak
Copy link

@burmistrzak burmistrzak commented Jan 1, 2025

All registers have been verified to work with a Vaillant sensoCOMFORT VRC 720/3f, running SW=0760;HW=7304.

Basis for this PR is the main basv.tsp file, with additional messages borrowed from @jonesPD's version of ctlv2.csv.
Conversion to TSP was done manually.

Additional features (compared to basv) include:

  • Hybrid manager
  • Cooling mode
  • Improved SFMode
  • Corrected OpMode set
  • Offsets/calibration
  • Away mode
  • Manual temperature setpoints
  • Room humidity
  • Timers (zone, hwc, cc, silent mode)

Also huge thanks to @stadid & @chrizzzp for their excellent ground work!

@burmistrzak
Copy link
Author

@jonesPD 👋 Do you by chance know, if/how the additional states of hcpumpstate from jonesPD@5fd6437 were verified?

@jonesPD
Copy link

jonesPD commented Jan 2, 2025

See here

stadid#5 (comment)

@burmistrzak
Copy link
Author

Finally managed to manually integrate a sizable chunk of the registers discovered by @stadid from @jonesPD's fork. 😅
I also did some more cleanup to ensure we have a somewhat consistent naming scheme.

@burmistrzak burmistrzak changed the title Add baseline support for basv3 Add support for basv3 Jan 4, 2025
@stadid
Copy link
Contributor

stadid commented Jan 5, 2025

Finally managed to manually integrate a sizable chunk of the registers discovered by @stadid from @jonesPD's fork. 😅

It was a team work with @chrizzzp and @jonesPD.

@burmistrzak
Copy link
Author

Big thanks to everyone involved in decoding the VRC 720! 🙌

It's interesting that there're apparently slight differences between the wired and wireless models, but that might also be caused by a newer revision/firmware... @stadid Which revision of VRC 720/? do you have on hand?

@stadid
Copy link
Contributor

stadid commented Jan 7, 2025

@burmistrzak

Which revision of VRC 720/? do you have on hand?

I have VRC720/2 identified as CTLV2
My guess is that BASV3 is wireless equivalent of CTLV3
While BASV2 is wireless equivalent of CTLV2

@burmistrzak
Copy link
Author

My guess is that BASV3 is wireless equivalent of CTLV3

Exactly my thinking! BAS might be short for Base Station

Question now is, are PrEnergySum & Co. also unsupported on CTLV3, or is this just a weird quirk of the wireless model? 🤔

@stadid
Copy link
Contributor

stadid commented Jan 8, 2025

Question now is, are PrEnergySum & Co. also unsupported on CTLV3, or is this just a weird quirk of the wireless model? 🤔

Do you have any Energy consumption values you can see directly in the regulator menu?

My guess is the following: all PrEnergy**** data do not "stored" in the regulator. Regulator acting as a buffer between the equipment and the native app/EBUSD. So regulator by itself stores any energy values only in case it could read them from the actual equipment (boiler, heat pump, etc) . I can confirm this at least for VRC700. It may happen that your equipment do not provide necessary data for BASV3 to return you appropriate values. Also the process of reading those values from the equipment is not frequent.

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@burmistrzak

I also have have the VRC 720/2 regulator and the following values can be read:

r;w,,PrEnergySumHcThisMonth,this months energy consumption heating,,,,4F00,,,energy4,,,current month electricity consumption heating
r;w,,PrEnergySumHwcThisMonth,this months energy consumption hot water,,,,5000,,,energy4,,,current month electricity consumption hot water
r;w,,PrEnergySumHcLastMonth,last months energy consumption heating,,,,5300,,,energy4,,,last month electricity consumption heating
r;w,,PrEnergySumHwcLastMonth,last months energy consumption hot water,,,,5400,,,energy4,,,last month electricity consumption hot water
r;w,,PrEnergySumHc,total energy consumption heating,,,,5700,,,energy4,,,total year electricity consumption heating
r;w,,PrEnergySumHwc,total energy consumption hot water,,,,5800,,,energy4,,,total year electricity consumption hot water

The following does not work (also not the PrFuel... registers):

#r;w,,PrEnergySum,total energy consumption,,,,5C00,,,energy4,,,total year electricity consumption

My heat generator is an Arotherm split heat pump.

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@stadid

My guess is the following: all PrEnergy**** data do not "stored" in the regulator. Regulator acting as a buffer between the equipment and the native app/EBUSD. So regulator by itself stores any energy values only in case it could read them from the actual equipment (boiler, heat pump, etc) . I can confirm this at least for VRC700.

I noticed the total energy statistics differ between regulator (ctlv2) and heat generator (hmu). The total values are similar, but not identical. I have the impression the regulator performs its own energy statistics calculations based on daily update polls from the heat generator around midnight (I haven't fully confirmed this). Every midnight I can see yet unidentified data being polled from the heat generator by the regulator:

2025-01-01 00:00:00.674 [update notice] received unknown MS cmd: 1008b516081002ffff03002132 / 0b12ffff0300213200000000
2025-01-01 00:00:00.974 [update notice] received unknown MS cmd: 1008b516081002ffff03008131 / 0b0200ff03008131ec81d948
2025-01-01 00:00:01.274 [update notice] received unknown MS cmd: 1008b516081003ffff03002132 / 0b13ffff0300213200000000
2025-01-01 00:00:01.624 [update notice] received unknown MS cmd: 1008b516081003ffff03002130 / 0b0300ff03002130fd0d0a4a
2025-01-01 00:00:01.934 [update notice] received unknown MS cmd: 1008b516081000ffff03002132 / 0b0000ff03009f317c023d4a
2025-01-01 00:00:07.604 [update notice] received unknown MS cmd: 1008b516081002ffff03032132 / 0b12ffff0303213200000000
2025-01-01 00:00:07.914 [update notice] received unknown MS cmd: 1008b516081002ffff03038131 / 0b02000003038131e343bf48
2025-01-01 00:00:08.255 [update notice] received unknown MS cmd: 1008b516081003ffff03032132 / 0b13ffff0303213200000000
2025-01-01 00:00:08.559 [update notice] received unknown MS cmd: 1008b516081003ffff03032130 / 0b03000003032130980d034a
2025-01-01 00:00:08.859 [update notice] received unknown MS cmd: 1008b516081000ffff03032132 / 0b00000003039f317bfc354a
2025-01-01 00:00:09.159 [update notice] received unknown MS cmd: 1008b516081002ffff03042132 / 0b12ffff0304213200000000
2025-01-01 00:00:09.464 [update notice] received unknown MS cmd: 1008b516081002ffff03048131 / 0b0200030304813155f05147
2025-01-01 00:00:09.760 [update notice] received unknown MS cmd: 1008b516081003ffff03042132 / 0b13ffff0304213200000000
2025-01-01 00:00:10.174 [update notice] received unknown MS cmd: 1008b516081003ffff03042130 / 0b03000303042130aa0ce047
2025-01-01 00:00:10.984 [update notice] received unknown MS cmd: 1008b516081000ffff03042132 / 0b00000303049f312962df47
2025-01-01 00:00:11.844 [update notice] received unknown MS cmd: 1008b516081002ffff03052132 / 0b12ffff0305213200000000
2025-01-01 00:00:13.284 [update notice] received unknown MS cmd: 1008b516081002ffff03058131 / 0b0200060305813100000000
...

I don't know yet what data it contains, but the 'b516' origin of the data points towards energy statistics, as the following definitions suggest (I think they are from a different heat generator and don't work for my system, that's why they are commented out).

#*r,,,,,,B516,1A,,,IGN:1,,,,,,,,,,,,,,,,,,,,,
#r,,YieldThisYear1,,,,,010100,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear2,,,,,010200,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear3,,,,,010300,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear4,,,,,010400,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear5,,,,,010500,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear6,,,,,010600,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear7,,,,,010700,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear8,,,,,010800,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear9,,,,,010900,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear10,,,,,010A00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear11,,,,,010B00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,YieldThisYear12,,,,,010C00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
# Electric power consumption,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
#r,,ConsumptionThisYear1,,,,,020100,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear2,,,,,020200,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear3,,,,,020300,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear4,,,,,020400,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear5,,,,,020500,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear6,,,,,020600,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear7,,,,,020700,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear8,,,,,020800,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear9,,,,,020900,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear10,,,,,020A00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear11,,,,,020B00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,
#r,,ConsumptionThisYear12,,,,,020C00,month,,D1B,,,,,,IGN:1,,,,,,energy,,,,,,,,,

@burmistrzak
Copy link
Author

Do you have any Energy consumption values you can see directly in the regulator menu?

@stadid Yes, I have all values for Env. Yield as well as Consumption for Heating, Cooling and DHW.

The following does not work (also not the PrFuel... registers):
#r;w,,PrEnergySum,total energy consumption,,,,5C00,,,energy4,,,total year electricity consumption

@chrizzzp Yep, same here. I guess you also see all values on the regulator itself, right?
Our system is a single circuit with uniTOWER plus & aroTHERM plus.

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0902;HW=5103", loaded "vaillant/08.hmu.hw5103.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=BASV3;SW=0760;HW=7304", loaded "vaillant/15.basv3.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0902;HW=5103"
address f1: master #10
address f6: slave #10, scanned "MF=Vaillant;ID=NETX3;SW=0124;HW=0404"

@burmistrzak
Copy link
Author

I don't know yet what data it contains, but the 'b516' origin of the data points towards energy statistics, as the following definitions suggest (I think they are from a different heat generator and don't work for my system, that's why they are commented out).

The yearly stats from the HMU also don’t work for us…
@chrizzzp What HW & SW do you have exactly?
I‘m planning to improve the HMU definition for these newer generations of heat pumps. 😊

@TheEragon
Copy link

Do you have any Energy consumption values you can see directly in the regulator menu?

@stadid Yes, I have all values for Env. Yield as well as Consumption for Heating, Cooling and DHW.

The following does not work (also not the PrFuel... registers):
#r;w,,PrEnergySum,total energy consumption,,,,5C00,,,energy4,,,total year electricity consumption

@chrizzzp Yep, same here. I guess you also see all values on the regulator itself, right? Our system is a single circuit with uniTOWER plus & aroTHERM plus.

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0902;HW=5103", loaded "vaillant/08.hmu.hw5103.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=BASV3;SW=0760;HW=7304", loaded "vaillant/15.basv3.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0902;HW=5103"
address f1: master #10
address f6: slave #10, scanned "MF=Vaillant;ID=NETX3;SW=0124;HW=0404"

I have if it helps

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0901;HW=5103", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104", loaded "vaillant/15.ctlv2.csv"
address 26: slave, scanned "MF=Vaillant;ID=VR_71;SW=0201;HW=0503", loaded "vaillant/26.vr_71.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0902;HW=5103", loaded "vaillant/76.vwzio.csv"
address f1: master #10
address f6: slave #10, scanned "MF=Vaillant;ID=NETX2;SW=4035;HW=5703"

@burmistrzak
Copy link
Author

@TheEragon Thx! Looks like you also have the older VRC 720/2, correct?
Are there any registers that don’t work for you?

@stadid
Copy link
Contributor

stadid commented Jan 8, 2025

@chrizzzp

I noticed the total energy statistics differ between regulator (ctlv2) and heat generator (hmu). The total values are similar, but not identical. I have the impression the regulator performs its own energy statistics calculations based on daily update polls from the heat generator around midnight (I haven't fully confirmed this). Every midnight I can see yet unidentified data being polled from the heat generator by the regulator

I have the similar data (regulator requests energy stats from the equipment about once a day).
BTW native app (MyVaillant), could read this data directly from the equipment. At least in some situations it's true. I've came across reports when one user connected internet gateway to his system which do not have the regulator and was able to read boiler stats, however could not manage his system (due to regulator absence).

@TheEragon
Copy link

@TheEragon Thx! Looks like you also have the older VRC 720/2, correct? Are there any registers that don’t work for you?

Almost all HMU registers are missing at the moment, but @jonesPD covered them in https://github.com/jonesPD/ebusd-configuration

@stadid
Copy link
Contributor

stadid commented Jan 8, 2025

@burmistrzak

Do you have any Energy consumption values you can see directly in the regulator menu?

@stadid Yes, I have all values for Env. Yield as well as Consumption for Heating, Cooling and DHW.

And if you try to read those registers using EBUSD what do you get?
i.e. do you see any data in the registers mentioned by @chrizzzp?

r;w,,PrEnergySumHcThisMonth,this months energy consumption heating,,,,4F00,,,energy4,,,current month electricity consumption heating
r;w,,PrEnergySumHwcThisMonth,this months energy consumption hot water,,,,5000,,,energy4,,,current month electricity consumption hot water
r;w,,PrEnergySumHcLastMonth,last months energy consumption heating,,,,5300,,,energy4,,,last month electricity consumption heating
r;w,,PrEnergySumHwcLastMonth,last months energy consumption hot water,,,,5400,,,energy4,,,last month electricity consumption hot water
r;w,,PrEnergySumHc,total energy consumption heating,,,,5700,,,energy4,,,total year electricity consumption heating
r;w,,PrEnergySumHwc,total energy consumption hot water,,,,5800,,,energy4,,,total year electricity consumption hot water

@stadid
Copy link
Contributor

stadid commented Jan 8, 2025

@chrizzzp

I have the impression the regulator performs its own energy statistics calculations based on daily update polls

Could be. Also some rounding may occur and that's why results are different. You've compared results Regulator<->Arotherm right after they are polled from your heating unit (around midnight)?

@burmistrzak
Copy link
Author

And if you try to read those registers using EBUSD what do you get?

@stadid Yes, got all the aforementioned registers, except PrEnergySum and PrFuelSum.
Reading PrEnergySum directly returns nothing useful...

root@1d2f5fff35d8:/# ebusctl hex 15b52406020000005c00
00

@stadid
Copy link
Contributor

stadid commented Jan 8, 2025

@burmistrzak

And if you try to read those registers using EBUSD what do you get?

@stadid Yes, got all the aforementioned registers, except PrEnergySum and PrFuelSum. Reading PrEnergySum directly returns nothing useful...

root@1d2f5fff35d8:/# ebusctl hex 15b52406020000005c00
00

As @chrizzzp has the similar results it seems that this part of the config is similar in CTLV2 and BASV3

@burmistrzak
Copy link
Author

burmistrzak commented Jan 8, 2025

@stadid Looks like it, yeah. I tried searching for the missing registers in between known ones, but haven’t found anything so far…

Btw. do the various timers work for you? If so, I‘ll integrate them as well.

@burmistrzak
Copy link
Author

When this PR hopefully gets merged, it might could become the new default for CTLV3, CTLV2, and BASV2.
So in case someone has a CTLV* and is feeling adventurous: Give this PR a shot and report back your findings! 😇

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@burmistrzak

@chrizzzp What HW & SW do you have exactly?

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU00;SW=0902;HW=5103", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=CTLV2;SW=0514;HW=1104", loaded "vaillant/15.ctlv2.csv"
address 26: slave, scanned "MF=Vaillant;ID=VR_71;SW=0104;HW=0503", loaded "vaillant/26.vr_71.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZ00;SW=0522;HW=5103", loaded "vaillant/76.vwz00.csv"
address f1: master #10
address f6: slave #10, scanned "MF=Vaillant;ID=NETX2;SW=4035;HW=5703", loaded "vaillant/f6.netx2.csv"

Seems we have the same SW/HW for the hmu, but different regulators (of course, I have VRC720/2).

I‘m planning to improve the HMU definition for these newer generations of heat pumps. 😊

Great, I'm happy to assist!

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@burmistrzak

I tried searching for the missing registers in between known ones, but haven’t found anything so far…

Did the same previously, no luck either.

Btw. do the various timers work for you? If so, I‘ll integrate them as well.

Yes, if treated properly. We had separate PRs for this:

stadid#3
stadid#4

@burmistrzak
Copy link
Author

burmistrzak commented Jan 8, 2025

@chrizzzp Oh well, guess we’ll have to live without them then. Not a big deal, IMHO.

Let’s see if these timers will work for me as well… 👀

Edit: Once I‘m done with that, would you be willing to give this PR a try on your end? I can pre-compile the CSVs for you, if necessary.

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@stadid

Could be. Also some rounding may occur and that's why results are different. You've compared results Regulator<->Arotherm right after they are polled from your heating unit (around midnight)?

Well, the value PrEnergySumHc from the regulator is actually higher (3.279 kWh) than the value TotalEnergyUsage from the heat pump (3.211 kWh). The first one does not include DHW, while the latter one should. This offset is more or less constant over the last 1.5 years. I'm not sure what is the origin of this offset as I record data only since then. I also think the difference is too big to be explained only by rounding errors. I think we still have to find the energy statistic registers of the heat generator used by the regulator to calculate the energy values.

BTW: the regulator displays the following values for which no CTL/BASVxx registers have been found yet:

  • TotalEnergy for this/last month/year and all time total (this could simply be the sum of DHW + HC + COOLING)
  • DHWEnergy for this/last year
  • HCEnergy for this/last year
  • EnvYield for this/last month/year
  • CoolingEnergy for this/last month/year and all time total
  • SolarYield this/last month/year (only available with solar circuit present)

@chrizzzp
Copy link

chrizzzp commented Jan 8, 2025

@burmistrzak

Slightly off-topic, but if you have time, could you please check on your BASV3 regulator menu whether there is an option to set the 'DHW Alternative Point' in addition to 'Heating Alternative Point' (should be in Settings/Installer Level/Installation configuration/Installation)?

The first defines the temperature under which exclusively the secondary (backup) heater is used in DHW mode, the latter is the same for the heating mode.

Interestingly, the older CTLV1/V2/BASV1/V2 units lack this option. They only features a single 'Alternative Point' which corresponds to the 'Heating Alternative Point'. Thus with these regulators it is (so far) not possible to use the alternative (backup) heater in DHW mode exclusively (only bivalent mode is possible).

I'm wondering whether the menu option has simply been forgotten in the CTLV1/V2/BASV1/V2 units or if this functionality is really not there?

In order to find out it would be great if the CTLV3/BASV3 register of the 'DHW Alternative Point' could be identified... Maybe the register exists also in the CTLV1/V2/BASV1/V2 units and the DHW alternative heater could be used exclusively (e.g. if the primary heater is blocked, or to exclusively enable the immersion heater and not the heat pump).

Here are the registers for the bivalent/alternative points identified so far. Do they work for your regulator?

*r,,,,,,B524,02000000,,,IGN:4,,,
*w,,,,,,B524,02010000,,,,,,
r;w,,HwcBivalencePoint,,,,,0100,,,tempv,,,Bivalence point hot water heating
r;w,,HcAlternativePoint,,,,,2200,,,tempv,,,exclusively alternate heating below alternative point (-21=off)
r;w,,HcBivalencePoint,,,,,2300,,,tempv,,,Bivalence point heating

@burmistrzak
Copy link
Author

burmistrzak commented Jan 8, 2025

Slightly off-topic, but if you have time, could you please check on your BASV3 regulator menu whether there is an option to set the 'DHW Alternative Point' in addition to 'Heating Alternative Point' (should be in Settings/Installer Level/Installation configuration/Installation)?

@chrizzzp Just checked and we have both available, but set to Off.

Here are the registers for the bivalent/alternative points identified so far. Do they work for your regulator?

Already implemented. 😉

root@ed037086b4ea:/# ebusctl read HwcBivalencePoint
-20

root@ed037086b4ea:/# ebusctl read HcBivalencePoint
-12

root@ed037086b4ea:/# ebusctl read HcAlternativePoint
-21

Haven't identified HwcAlternativePoint yet tho...

Edit: Maybe I'm silly, but I can't seem to get ebusctl to log raw messages on the bus... Any hints?

@chrizzzp
Copy link

chrizzzp commented Jan 9, 2025

@burmistrzak

Edit: Maybe I'm silly, but I can't seem to get ebusctl to log raw messages on the bus... Any hints?

Did you check the standard ebusd logfile? Usually this has all information necessary to decode unknown messages (time stamp, raw data, decoded known messages). Log level is set to 'notice' in my case.

@burmistrzak
Copy link
Author

Did you check the standard ebusd logfile? Usually this has all information necessary to decode unknown messages (time stamp, raw data, decoded known messages). Log level is set to 'notice' in my case.

@chrizzzp I increased the log level, changed HwcAlternativePoint on the regulator, but haven't see anything useful yet...

@burmistrzak
Copy link
Author

@john30 This one should be good for review! 🤞
Functionality has been verified to the best of my abilities.

@burmistrzak burmistrzak changed the title Add support for basv3 Add support for basv3 VRC 720/3f Jan 12, 2025
@chrizzzp
Copy link

chrizzzp commented Jan 12, 2025

@burmistrzak

I increased the log level, changed HwcAlternativePoint on the regulator, but haven't see anything useful yet...

I'm afraid the change of HwcAlternativePoint on the regulator will not produce a message sent over EBUS (as it only affects the regulator behaviour itself). It will be not so easy to find the corresponding register in the BASV3.

Just an idea: Here's a list of still unknown (nonbinary) definitions from the general section of the 15.ctlv2.csv. Maybe some of these values show anything when the HwcAlternativePoint is changed?

*r,,,,,,B524,02000000,,,IGN:4,,,
r,,xUnknown04,(konstant 0),,,,0400,,,UIN,,,
r,,xUnknown0B,(konstant 0),,,,0B00,,,SIN,,,
r,,xUnknown13,(konstant 0 cooling 2),,,,1300,,,UIN,,,
r,,xUnknown1C,(konstant 80),,,,1C00,,,tempv,,,
r,,xUnknown25,(konstant 0),,,,2500,,,SIN,,,
r,,xUnknown31,(konstant 0 cooling 5),,,,3100,,,SIN,,,
r,,xUnknown5E,(0),,,,5E00,,,energy4,,,
r,,xUnknown5F,(0),,,,5F00,,,UIN,,,
r,,xUnknown60,(konstant 12 cooling 0),,,,6000,,,SIN,,,
r,,xUnknown61,(konstant 0),,,,6100,,,SIN,,,
r,,xUnknown65,(konstant 0),,,,6500,,,SIN,,,
r,,xUnknown67,(VR70 konfig 1 konstant -),,,,6700,,,tempv,,,
r,,xUnknown68,(VR70 konfig 1 konstant -),,,,6800,,,tempv,,,
r,,xUnknown7E,(konstant 0),,,,7E00,,,EXP,,,
r,,xUnknown80,(konstant 0),,,,8000,,,EXP,,,
r,,xUnknown81,(konstant 10),,,,8100,,,EXP,,,
r,,xUnknown85,(konstant -),,,,8500,,,tempv,,,
r,,xUnknown86,(konstant 60),,,,8600,,,SIN,,,
r,,xUnknown89,(konstant 15),,,,8900,,,SIN,,,
r,,xUnknown8A,(konstant 1),,,,8A00,,,EXP,,,
r,,xUnknown8B,(konstant 55),,,,8B00,,,EXP,,,
r,,xUnknown8D,(konstant 0),,,,8D00,,,SIN,,,
r,,xUnknown8E,(konstant 0),,,,8E00,,,SIN,,,
r,,xUnknown8F,(konstant 0),,,,8F00,,,SIN,,,
r,,xUnknownA5,(konstant 0),,,,A500,,,EXP,,,
r,,xUnknownAF,(konstant 0),,,,AF00,,,EXP,,,
r,,xUnknownB0,(konstant 0),,,,B000,,,EXP,,,
r,,xUnknownB1,(konstant 0),,,,B100,,,EXP,,,
r,,xUnknownB2,(konstant 4543),,,,B200,,,HEX:*,,,
r,,xUnknownB9,(konstant 0),,,,B900,,,EXP,,,
r,,xUnknownBA,(konstant 0),,,,BA00,,,EXP,,,
r,,xUnknownBB,(konstant 0),,,,BB00,,,EXP,,,
r,,xUnknownBC,(konstant 0),,,,BC00,,,EXP,,,
r,,xUnknownBD,(konstant 0),,,,BD00,,,EXP,,,
r,,xUnknownBF,(konstant 0),,,,BF00,,,EXP,,,
r,,xUnknownDA00,(konstant 01.01.2019),,,,DA00,,,date,,,
r,,xUnknownDB00,(konstant 01.01.2019),,,,DB00,,,date,,,
r,,xUnknownEF00,(konstant 20),,,,EF00,,,EXP,,,
r,,xUnknownF200,,,,,F200,,,HEX:*,,,
r,,xUnknownF300,,,,,F300,,,HEX:*,,,
r,,xUnknownF600,(konstant 15),,,,F600,,,EXP,,,
r,,xUnknownFB00,(konstant 10),,,,FB00,,,EXP,,,
r,,xUnknownFC00,(konstant 62),,,,FC00,,,EXP,,,
r,,xUnknownFE00,(konstant 13),,,,FE00,,,EXP,,,
r,,xUnknownFF00,(konstant 25),,,,FF00,,,EXP,,,

@burmistrzak
Copy link
Author

@chrizzzp Hmm, none of the applicable registers (of type tempv) changed… Could it be that this functionality might not be exposed to eBus, and is handled entirely in firmware? 🫣

@chrizzzp
Copy link

@burmistrzak
Thanks for checking.

Yes, internal handling is also possible although I don't think so as it would also preclude Vaillant to remotely control the alternative point setting. I think the register just hast to be found... (probably in higher address ranges not yet explored). I'd probably look for a register with datatype EXP that has the default value of -21 (alternative point disabled) as with HcAlternativePoint.

@burmistrzak
Copy link
Author

I think the register just hast to be found... (probably in higher address ranges not yet explored). I'd probably look for a register with datatype EXP that has the default value of -21 (alternative point disabled) as with HcAlternativePoint.

@chrizzzp What ranges exactly haven’t been explored yet? I might give them a try.

@chrizzzp
Copy link

@burmistrzak

I think from the general section:
*r,,,,,,B524,02000000,,,IGN:4,,,
the registers from 6000 to FF00 have not been thoroughly analysed.

Same with the HWC section:
*r,,,,,,B524,02000100,,,IGN:4,,,
The current mapping ends at register 1300:
r,,HwcUnknown13,(konstant 0),,,,1300,,,onoff,,,

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

Successfully merging this pull request may close these issues.

5 participants