john30
VMS8D - AuroStep Plus (VIH250/4) - unknown device?
Hi all, new to eBusd, but curious to know what it can mean to my setup:
- Ecotec plus VCW376 (that is found within BAI)
- Aurostep plus VIH250 with VMS8D interior
- both interconnected on the ebus, but NO thermostat (only a basic on-off connected to the VCW)
Installed ebusd with USB adapter on a raspberry pi. Scanning results are:
ebusd -f -d /dev/ttyUSB0 --configpath=http://ebusd.eu/config/ --scanconfig=full --pollinterval=180
2019-12-06 18:16:06.298 [main notice] ebusd 3.4.v3.3-51-g57eae05 started with full scan 2019-12-06 18:16:06.531 [bus notice] bus started with own address 31/36 2019-12-06 18:16:06.552 [bus notice] signal acquired 2019-12-06 18:16:16.532 [main notice] starting initial full scan 2019-12-06 18:16:18.313 [bus notice] new master 01, master count 2 2019-12-06 18:16:18.314 [bus notice] scan 06: ;Vaillant;VMD01;0108;1703 2019-12-06 18:16:18.314 [update notice] store 06 ident: done 2019-12-06 18:16:18.314 [update notice] sent scan-read scan.06 QQ=31: Vaillant;VMD01;0108;1703 2019-12-06 18:16:18.314 [bus notice] scan 06: ;Vaillant;VMD01;0108;1703 2019-12-06 18:16:18.484 [bus notice] new master 03, master count 3 2019-12-06 18:16:18.485 [bus notice] scan 08: ;Vaillant;BAI00;0104;7803 2019-12-06 18:16:18.485 [update notice] store 08 ident: done 2019-12-06 18:16:18.485 [update notice] sent scan-read scan.08 QQ=31: Vaillant;BAI00;0104;7803 2019-12-06 18:16:18.485 [bus notice] scan 08: ;Vaillant;BAI00;0104;7803 2019-12-06 18:16:22.219 [main error] unable to load scan config 06: no file from vaillant with prefix 06 matches ID "vmd01", SW0108, HW1703 2019-12-06 18:16:22.219 [main error] scan config 06: ERR: element not found 2019-12-06 18:16:24.800 [main notice] read common config file vaillant/scan.csv 2019-12-06 18:16:24.858 [main notice] read common config file vaillant/general.csv 2019-12-06 18:16:24.917 [main notice] read common config file vaillant/broadcast.csv 2019-12-06 18:16:24.978 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0104, HW7803 2019-12-06 18:16:25.742 [update notice] sent scan-read scan.08 id QQ=31: 2019-12-06 18:16:26.459 [update notice] sent scan-read scan.08 id QQ=31: 2019-12-06 18:16:27.176 [update notice] sent scan-read scan.08 id QQ=31: 2019-12-06 18:16:27.895 [update notice] sent scan-read scan.08 id QQ=31: 21;18;07;0010021845;1300;257184;N9 2019-12-06 18:16:28.148 [main notice] found messages: 211 (3 conditional on 25 conditions, 0 poll, 9 update) 2019-12-06 18:16:29.178 [update notice] sent scan-read scan.08 id QQ=31: 21;18;07;0010021845;1300;257184;N9 2019-12-06 18:16:29.900 [update notice] sent scan-read scan.08 id QQ=31: 21;18;07;0010021845;1300;257184;N9 2019-12-06 18:16:30.618 [update notice] sent scan-read scan.08 id QQ=31: 21;18;07;0010021845;1300;257184;N9 2019-12-06 18:16:31.333 [update notice] sent scan-read scan.08 id QQ=31: 21;18;07;0010021845;1300;257184;N9 2019-12-06 18:16:31.333 [bus notice] scan 08: ;21;18;07;0010021845;1300;257184;N9 2019-12-06 18:18:14.641 [bus notice] scan ed: ;Vaillant;VMD01;0108;1703 2019-12-06 18:18:14.641 [update notice] store ed ident: done 2019-12-06 18:18:14.641 [update notice] sent scan-read scan.ed QQ=31: Vaillant;VMD01;0108;1703 2019-12-06 18:18:14.641 [bus notice] scan ed: ;Vaillant;VMD01;0108;1703 2019-12-06 18:18:23.480 [update notice] sent unknown MS cmd: 31edb5090124 / 09003231313832303030 2019-12-06 18:18:23.666 [update notice] sent scan-read scan.ed id QQ=31: 2019-12-06 18:18:23.853 [update notice] sent scan-read scan.ed id QQ=31: 2019-12-06 18:18:24.038 [update notice] sent scan-read scan.ed id QQ=31: 21;18;20;0010017717;3110;004422;N2 2019-12-06 18:18:24.038 [bus notice] scan ed: ;21;18;20;0010017717;3110;004422;N2 2019-12-06 18:18:24.097 [main error] unable to load scan config ed: no file from vaillant with prefix ed matches ID "vmd01", SW0108, HW1703 2019-12-06 18:18:24.097 [main error] scan config ed: ERR: element not found 2019-12-06 18:20:26.159 [main notice] update check: revision v3.4 available
ebusd command line gives:
ebusctl i version: ebusd 3.4.v3.3-51-g57eae05 update check: revision v3.4 available signal: acquired symbol rate: 23 max symbol rate: 86 min arbitration micros: 721 max arbitration micros: 977 min symbol latency: 5 max symbol latency: 14 reconnects: 0 masters: 3 messages: 213 conditional: 3 poll: 0 update: 9 address 01: master #6 address 03: master #11 address 06: slave #6, scanned "MF=Vaillant;ID=VMD01;SW=0108;HW=1703" address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0104;HW=7803", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv" address 31: master #8, ebusd address 36: slave #8, ebusd address ed: slave, scanned "MF=Vaillant;ID=VMD01;SW=0108;HW=1703"
ebusctl find -d scan.06 = Vaillant;VMD01;0108;1703 scan.08 = Vaillant;BAI00;0104;7803 scan.08 id = 21;18;07;0010021845;1300;257184;N9
I can read some stuff:
ebusctl read -V flame bai Flame =off [Flammensignal]
But when using hot water (with solar boiler under threshold temperature), the flame remained off whilst the VCW was actively heating the water.
Other commands are failing:
ebusctl read time ERR: element not found
So my questions are:
- is this solar boiler (VMS) not available hence I cannot query it?
- is a (vaillant) thermostat a required element on the ebus before you can query stuff from the VCW?
- can I "promote" the ebus USB connector as a "real" vaillant thermostat so the VCW actually talks to it?
Thanks for your feedback!
you could try re-using the pms files for the VMS. I think I remember that somebody did the same and had some success at least.
Hi John, yes, copying the 06.pms.csv did something magically happen, I now have this:
vmd ASIDetected = 36 vmd BufferControlDiff = ERR: invalid position in decode vmd BufferControlInt = ERR: invalid position in decode vmd BufferControlPress = ERR: invalid position in decode vmd BufferPumpPower = 0 vmd CountryZone = 144 vmd CurrentASCStateforASI = 0 vmd CurrentASCStateforExternals = 0 vmd CurrentBufferTempDesired = ERR: invalid position in decode vmd currenterror = -;-;-;-;- vmd CurrentFlow = 960 vmd CurrentSolTempDesired = ERR: invalid position in decode vmd CurrentSystemMode = 60 vmd CurrentVPMLoadingMode = 167 vmd Date = 14.12.2019 vmd DateAndTimeIsSet = off vmd errorhistory = ERR: end of input reached vmd ExternalHcRequest = 14 vmd ExternalHcTempDesired = 156 vmd ExternalHwcRequest = 34 vmd ExternalHwcTempDesired = 0 vmd FlowSensorFrequency = 0 vmd ForceStartSolPumpKick = off vmd InternalHcTempDesired = 0 vmd InternalHwcTempDesired = 160 vmd MonitorBufferPIDValue = ERR: invalid position in decode vmd MonitorMatlabHcCalculation = ERR: invalid position in decode vmd MonitorMatlabHwcCalculation = ERR: invalid position in decode vmd MonitorMatlabLast5minSolAverage = ERR: invalid position in decode vmd MonitorMatlabState = 0 vmd MonitorOverheatState = 0 vmd MonitorSolPIDValue = ERR: invalid position in decode vmd Ntc1RawData = ERR: invalid position in decode vmd Ntc1Sensor = 14.88;ok vmd Ntc2RawData = ERR: invalid position in decode vmd Ntc2Sensor = -39.69;cutoff vmd Ntc3RawData = ERR: invalid position in decode vmd Ntc3Sensor = 20.44;ok vmd Ntc4RawData = ERR: invalid position in decode vmd Ntc4Sensor = ERR: invalid position in decode vmd PowerOnCounter = 160 vmd RequestForExternalDateTimeSetting = 36 vmd RTCLowVoltageCounter = 240 vmd RunTimeBufferPumpHours = ERR: invalid position in decode vmd RunTimeBufferPumpMinutes = 0 vmd RunTimePump1Hours = 1550 vmd RunTimePump1Minutes = 34 vmd SolControlDiff = ERR: invalid position in decode vmd SolControlInt = ERR: invalid position in decode vmd SolControlPress = ERR: invalid position in decode vmd SolPumpPower = 0 vmd SolPumpRelay = off vmd Time = 14:20:32 vmd Variante = 0 vmd YieldCurrentDay = 37008 vmd YieldTotal = 1168
Much better than previously, but some of the values (eg returning temperature gycol is -39°C) cannot be correct. However I can already query if my pump is working or not, and that is already good news.
Thanks for your support John!
Hi @Strobistar, did you make any progress regarding the VMS8D ? I have the same, we could share our researches.
Hi @pagaille,
I ran my ebusd scripts till Summer, discovered (with the help of a couple of DS18B20 sensors) that something was wrong with my glycol tubes, now waiting for my plumber to switch the inlet and outlet tubes (hot glycol was pumped up to cool down on the roof). Disconnected everything because in winter time, the solar boiler thing is not working anyway. I only used the pump status ebus value to see when the pump was working, and mapped that on my DS18B20 sensor data.
To make it work, the last trick I used was posted above, copy-pasted vmd06 on a local repository.
Did you do other things to have more data coming out of the VMD?
Thanks! Strobistar
You mean the in and out tubes are reversed ?? OMG how the the hell is it possible !? I discovered my installation was also done completely against the recommandations and had to retube everything 🙁 Even for a wannabe plumber like me it was only a question of reading the f** manual, which looks already to much asking for some 🙁
FYI : there is solar production in winter. Only a small amount of direct sun is enough to warm the panels >60°C and thus reduce the electricity needed to get the water to 60°C. I usually reach 4KWh on a cold but sunny day.
I'll try to edit the configuration file to get a least pump information and temperature sensors. I'll report my findings here.
Yes, glycol was pumped up top down, and never reached the temperature sensor at the opposite side. Hence that reading (in late afternoon) gave readings +50C°, glycol of 45°C was pumped up and came down 30°C, in the end cooling my boiler drastically. That's a newbie error... So for sunny days like we had this day, the display SHOWS 3-4kWh however temperature reading is merely 20°C. So I'm wasting electricity (luckily I got a surplus of 1MWh of my good working solar panels).
In my setup, simply copy that vmd06 file, no need of editing, then you can read out vmd Ntc1Sensor = 20.44;ok and vmd Ntc3Sensor = 20.44;ok plus the % power of the pump: SolPumpPower
Hope this helps!
I read the following. Not a lot of a values looks ok
# ebusctl find -v
broadcast datetime = no data stored
broadcast error = no data stored
broadcast hwcStatus = no data stored
broadcast id = no data stored
broadcast id = no data stored
broadcast load = no data stored
broadcast outsidetemp = no data stored
broadcast signoflife = no data stored
broadcast vdatetime = no data stored
general valuerange = no data stored
memory eeprom = no data stored
memory ram = no data stored
scan id = no data stored
scan.06 = MF=Vaillant;ID=VMD01;SW=0108;HW=1703
scan.06 id = prefix=??;year=??;week=??;product=??????????;supplier=????;counter=??????;suffix=??
vmd ASIDetected = onoff=6
vmd BufferControlDiff = (ERR: invalid position for 3106b509030d2700 / 0101)
vmd BufferControlInt = (ERR: invalid position for 3106b509030d2600 / 0101)
vmd BufferControlPress = (ERR: invalid position for 3106b509030d2500 / 0101)
vmd BufferPumpPower = power=0
vmd CountryZone = =144
vmd CurrentASCStateforASI = =0
vmd CurrentASCStateforExternals = =0
vmd CurrentBufferTempDesired = (ERR: invalid position for 3106b509030d4900 / 0100)
vmd currenterror = no data stored
vmd CurrentFlow = =960
vmd CurrentSolTempDesired = (ERR: invalid position for 3106b509030d1800 / 0100)
vmd CurrentSystemMode = =0
vmd CurrentVPMLoadingMode = =74
vmd Date = date=02.11.2020
vmd DateAndTimeIsSet = onoff=off
vmd errorhistory = no data stored
vmd ExternalHcRequest = onoff=112
vmd ExternalHcTempDesired = desiredtemp=0
vmd ExternalHwcRequest = onoff=off
vmd ExternalHwcTempDesired = desiredtemp=0
vmd FlowSensorFrequency = =0
vmd ForceStartSolPumpKick = onoff=off
vmd InternalHcTempDesired = =1
vmd InternalHwcTempDesired = =16
vmd MonitorBufferPIDValue = (ERR: invalid position for 3106b509030d2b00 / 0100)
vmd MonitorMatlabHcCalculation = (ERR: invalid position for 3106b509030d5400 / 0100)
vmd MonitorMatlabHwcCalculation = (ERR: invalid position for 3106b509030d5300 / 0100)
vmd MonitorMatlabLast5minSolAverage = (ERR: invalid position for 3106b509030d1700 / 0100)
vmd MonitorMatlabState = =0
vmd MonitorOverheatState = =0
vmd MonitorSolPIDValue = (ERR: invalid position for 3106b509030d2c00 / 0100)
vmd Ntc1RawData = (ERR: invalid position for 3106b509030d0000 / 0100)
vmd Ntc1Sensor = temp=31.00;sensor=ok
vmd Ntc2RawData = (ERR: invalid position for 3106b509030d0100 / 0100)
vmd Ntc2Sensor = temp=-39.69;sensor=cutoff
vmd Ntc3RawData = (ERR: invalid position for 3106b509030d0200 / 0100)
vmd Ntc3Sensor = temp=38.38;sensor=ok
vmd Ntc4RawData = (ERR: invalid position for 3106b509030d0300 / 0100)
vmd Ntc4Sensor = (ERR: invalid position for 3106b509030d0800 / 0100)
vmd PowerOnCounter = =160
vmd RequestForExternalDateTimeSetting = onoff=6
vmd RTCLowVoltageCounter = =240
vmd RunTimeBufferPumpHours = (ERR: invalid position for 3106b509030d4c00 / 0100)
vmd RunTimeBufferPumpMinutes = minutes0=0
vmd RunTimePump1Hours = hoursum2=3591
vmd RunTimePump1Minutes = minutes0=14
vmd SolControlDiff = (ERR: invalid position for 3106b509030d2a00 / 0100)
vmd SolControlInt = (ERR: invalid position for 3106b509030d2900 / 0100)
vmd SolControlPress = (ERR: invalid position for 3106b509030d2800 / 0101)
vmd SolPumpPower = power=0
vmd SolPumpRelay = onoff=off
vmd Time = time=10:09:54
vmd Variante = =0
vmd YieldCurrentDay = energy=37008
vmd YieldTotal = energy4=761
You got much more information than I had with mine (although plenty of errors), but your Ntc1Sensor and Ntc3Sensor report back values. Ntc1 is the roof sensor in the collector, as it seems to be 31°C, I'm imagining that sun is shining at your place :) Have a look on your display top left, it should read this 31°C. For the Ntc3 (boiler internal temp), you could look top right, or you go into debug mode on your screen (hold the bottom (or was it top?) buttons, go into installation, opt in 17 and go into the test menus for the temperature sensors).
I made some good progress. See my PR : https://github.com/john30/ebusd-configuration/pull/199
Hi @pagaille that is great stuff, my ebus reader is currently offline, I'll sync your additions when back online!
Thank you!
Hi, @pagaille, hi @Strobistar I have an ebus adapter reading from my Ecotec Plus, throug the fantastic ebusd daemon, working since last year and getting comsuptions to fine tunning hours and temperatures to get more confortable at home saving gas when possible.
I also have an aurostep plus. But the ebus in the aurostep has no current, and I haven´t found any information about the way to conect the ebus in the aurostep with the ebus in the adapter or in the ecotec.
Could you please let me know how to do this? Maybe this is so silly question as to conect the three devices in one single point? (of course, keeping the both poles of the ebus) Maybe the two wires of the ecotec conectect together to the two wires or the aurostep, and that four wires conected to the ebus adapter? Could you share a picture of that?
Another question, the file 06.vmd.csv where do I get it to download, and in whitch path do I have to save it?
As soon I have it working I promise to report here the info from the aurostep to feed your progress in case this can help you. And of course I can help you anyway I´ll try to.
Thanks in advance.
Hi @aguti2, Regarding wiring: the ebus is, as the word states, a bus. You have to connect each of the two wires with each other. On the same 2 wires, all other devices (eg thermostat) are connected to. My VCW heating is simply connected with those 2 wires to the Aurostep. In the same connector, I plugged in 2 wires for the ebus reader. As long as your Aurostep is receiving 220V, I suspect the ebus to be on, but verify in the installer menu that "ebus" is indeed ticked on.
Regarding location of the files: what I did: I downloaded all to /etc/ebusd, where you have your template.csv, broadcast.csv and memory.csv, plus the most important directory: vaillant. Within that directory, you paste the new 06.vmd.csv from @pagaille.
Last but not least, to use these files, you have to instruct ebusd to use them:
usr/bin/ebusd -d /dev/ttyUSB0 --configpath=/etc/ebusd/ --scanconfig=full --pollinterval=180 --latency 5000 --acquiretimeout=15000
--> look at the configpath parameter.
Good luck! Strobistar`
Hi @aguti2 - happy to see that there other than me that are interested un the Aurostep controller.
the ebus in the aurostep has no current, and I haven´t found any information about the way to conect the ebus in the aurostep with the ebus in the adapter or in the ecotec.
True. The aurostep controller is a slave and has no bus power supply. As far as I know you simply have to connect it to a powered master (your Ecotec heater) to make it work, preferably something like flat or round 0,75mm2. There is an internal redresser, so polarity doesn't matter. The cabling structure is free.
Another question, the file 06.vmd.csv where do I get it to download, and in whitch path do I have to save it?
As far as I know @john30 has not merged my PR so you must download it here https://github.com/john30/ebusd-configuration/pull/199 and replace it into the /etc/ebusd/vaillant folder.
Extremely curious to learn about your findings, especially the information that are exchanged between the ecotec and the aurostep.
Hello @Strobistar and @pagaille
Thanks for your super fast answer.
That´s what I suspected, the bus concept is clear, but sometimes is necesary some kind of buffer, voltage adapter or level shifter, polarity, etc.... And this devices are very expensive to try and error. Now it´s clear for me, each pair of wires connected in the same connector. Solved. Thank you.
About the files, I´ll try and tell you. Maybe tomorrow because I´m out today.
And yes, I´m curious too about the info between ecotec and aurostep. I´ll tell you.
And @pagaille now you know that you´re not alone, ;-)
Thanks guys for your help and anwsers. I´ll tell you about my discoveries.
Have a good day.
Well, to my understanding, an ecotec nor aurostep are very chatty. I haven't seen a single bit transferred between the two of them. I suspect that if you have a Vaillant thermostat that that one will query those systems (eg heating curve) and that the ebus reader then can show these values.
Keep us posted!
Hi @pagaille,
I have seen that you have made your own power supply for the aurostep.
Would you share any thing more to guide me. For example the power source and voltage, if you have any pictures, any help would be appreciated. The schematic is good but incomplete without voltage input.
Now in winter I can power the ebus with my ecotec, but here un Spain in May I use to power off the ecotec for some mounths, nearly 6 mounths, so if I can have a power source for the aurostep, I could keep powering of the ecotec in summer time.
But only if you don´t mind, don´t feel obligated. Thanks in any case.
Indeed. The power supply is of a special kind : it's a constant current (50mA) AND voltage limiter (24V) PS. The ebus specification contains a typical schematic that I used to build mine on a breadboard.
Hello @pagaille, Thank you for your fast answer as usual, very kind.
This is a very simple design, but if you have it in a breadboard, i think would be enough. I´ll try and again I´ll tell you.
Thanks again.
Hello @Strobistar and @pagaille, Last night I made conection between the ecotec and the aurostep. No smoke at all so there was good news. It took several restarts of the daemon, but at last the aurostep apeared in the bus. Only a few more tries because there was too late, but I couldn´t get the @pagaille csv file loaded.
If I use the --configpath=/etc/ebusd/ and downloaded the csv files and get then copied to the path /etc/ebusd/ the daemon loads the local 08.bai.csv but the variables of the ecotec weren´t availables, and the log tells that there are template.csv, broadcast.csv and memory.csv diferents.
If I don´t use the --configpath, the --scanconfig works well and the daemon download the 08.bai.csv and the ecotec speaks to the bus correctly. But as the daemon dont download the @pagaille csv as expected there is no chat from the aurostep.
Any way I´ll try today, I´ll have a bit more time today to do some more research.
Where do you download the csvs? I got them from https://github.com/john30/ebusd-configuration/tree/master/ebusd-2.1.x/en and perhaps it´s not the updated one
I´ll tell you about my progress.
Have a good day and thanks for reading.
Hi @aguti2 !
I did once a git-clone towards my system:
git clone https://github.com/john30/ebusd-configuration.git if [ -d /etc/ebusd ]; then sudo mv /etc/ebusd /etc/ebusd.old; fi sudo ln -s $PWD/ebusd-configuration/ebusd-2.1.x/de /etc/ebusd
By doing so, you have all the original files from the git repository. Then you copy in the 06.vmd.csv and with the configpath set, you should see both ecotec and aurostep.
Good luck!
Thank you @Strobistar,
I´ve copied from the url, not tried with git clone. I´ll try this afternoon.
Thank you so much. I´ll tell you about it.
Hi guys, @Strobistar and @pagaille,
That worked fine!!!!! Thanks for your support.
I did the git clone and worked fine, but as you can see the ebusctl goes on with differents csvs, but in the end it´s working with both, the ecotec and the aurostep.
Now integrated in my HomeAssistant:
That was four hours later, so the graphics are still useless, but in a few days the graphs will be very usefull.
As I get the state of the variables though a mqtt request, with the FlowRate and PowerOnCounter variables I have a dismiss with the mqtt values, because I couldn´t find the rigth string in the mqtt tree, but I think I´ll find them.
The next step would be the improvement of the variables readed, such as the Kwh generated, maybe the amount of water in a target temperature, I don´t know, I suposse there will be a lot of usefull values.
So, thank you very much for your help and anwers. your tips have saved me a lot of time. Thank you.
Have a very good weekend.
Hey @aguti2, nice to hear ! I'm also looking forward to find the solar yield field. I hope you'll be more acute than me 😊
Out of curiosity, what's your ΔT between T5 and T1 (when the solar pump is working) ? Mine fluctuates between 10-15K, probably because the pipes up to the roof are quite long.
If anybody is interested to get the instant (solar) power : the formula is (FlowRate * 10) * (T1-T6) / 14.
The 10 multiplier is there to get the flow rate in L/Min. That factor could probably be incorporated into the CSV files.
Integrating the values will convert the instant power to energy (kWh).
Credits : https://www.navitron.org.uk/forum/index.php?topic=8391.0
@ John30 Need some help I am trying to connect a Solar Boiler auroSTEP plus VMS8D via Ebus. I have a eBUS Adapter 3 and the Ebusd deamon installed on a RPi. I think the installation and coniguration is Ok because when I type "ebusctl info" in the monitor, I get this answer: version: ebusd 21.2.v21.2-48-g24a6525 signal: acquired symbol rate: 100 max symbol rate: 101 reconnects: 0 masters: 1 messages: 11 conditional: 0 poll: 0 update: 4 address 31: master #8, ebusd address 36: slave #8, ebusd After I power the eBus adapter the blue LED flashes some times, then lights for a second and then the yellow and green LEDS are on constantly. In the eBUS adapter documentation I found that this means power adapter Ok and no communication with boiler or voltage on ebus too low. Since my system is stand alone, I have built the power supply in this thread and I measure 22,4 Volts on the bus. Any ideas what could be the problem or some more tests I can perform to find a solution? Thanks in advance, JP
Hi JP!
As your output states "masters: 1" and "messages: 11", I do think you are successfully connected.
What does "ebusctl find -v" give as output?
From my scrapbook, have a look at the following commands:
"ebusd -f -c /tmp --logareas bus --loglevel info --lograwdata=bytes -d /dev/ttyUSB0"
(should dump a lot of "aa"'s)
Then run a "full scan":
"ebusd -f -d /dev/ttyUSB0 --configpath=http://ebusd.eu/config/ --scanconfig=full --pollinterval=180"
(if it states device blocked, you might have to kill the existing running ebusd).
Hope this helps! Strobistar
Your aurostep is not seen on the bus (it has adress 06 or ED.
If the vms is the only device on the bus along the controller you need to ebusd generate the syn messages. Use --generatesyn in order to do so.
Matthieu G. (en mode mobile)
Le 8 nov. 2021 à 18:20, jpslootmans @.***> a écrit : @ John30 Need some help I am trying to connect a Solar Boiler auroSTEP plus VMS8D via Ebus. I have a eBUS Adapter 3 and the Ebusd deamon installed on a RPi. I think the installation and coniguration is Ok because when I type "ebusctl info" in the monitor, I get this answer: version: ebusd 21.2.v21.2-48-g24a6525 signal: acquired symbol rate: 100 max symbol rate: 101 reconnects: 0 masters: 1 messages: 11 conditional: 0 poll: 0 update: 4 address 31: master #8, ebusd address 36: slave #8, ebusd After I power the eBus adapter the blue LED flashes some times, then lights for a second and then the yellow and green LEDS are on constantly. In the eBUS adapter documentation I found that this means power adapter Ok and no communication with boiler or voltage on ebus too low. Since my system is stand alone, I have built the power supply in this thread and I measure 22,4 Volts on the bus. Any ideas what could be the problem or some more tests I can perform to find a solution? Thanks in advance, JP
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Hello,
I should have mentioned that the eBus Adapter 3 is the Ethernet version. ebusctl find -v gives this: broadcast datetime = no data stored broadcast error = no data stored broadcast id = no data stored broadcast id = no data stored broadcast signoflife = no data stored memory eeprom = no data stored memory ram = no data stored
my option string is: 'EBUSD_OPTS="--scanconfig -d enh:192.168.0.179:9999 --latency=80 --httpport 8889"' @ pagaille: do I put the "--generatesyn" in the option string?