eBus Schaltung V2 in Betrieb nehmen

[Reinhart]

Das ist mir bei der Ansicht der Bilder auch aufgefallen, ein Wert von 2.0 bei der Heizkurve ist schon sehr hoch.
Bei mir steuert sich die Heizkurve ja automatisch nach dem Wärmebedarf und der Aussentemperatur (Wichtung=Durchschnitt des Öffnungswinkels  der Thermostatventile) und liegt bei den jetzigen Temperaturen von etwa -4 Grad Durchschnitt zwischen 0,9 - 1,0.

Das hängt natürlich von der Beschaffenheit der Heizung und des Hauses ab. Aber im allgemeinen kann man sagen, je flacher diese Kurve ist, desto sparsamer arbeitet die Heizung.

LG

[Gyrinx]

Hallo Zusammen,

die Heizkurve 2.0 ist dem Umstand geschuldet, das der Wärmetauscher für Warmwasser verkalkt ist und der Installateur erst nächste Woche kommt. Danach kann ich die Kurve wieder auf hoffentlich wieder auf 1.6 stellen.

Das war jetzt erst einmal die Notlösung, damit meine Frau nicht erfriert. Der Problematik bin ich durch ECMD und den astronomisch hohen Brennerstarts für Warm Wasser auf die Spur gekommen. Weiterhin konnte ich sehen, da die Heizung für Warmwasser jedesmal 60 Minuten gebraucht hat, statt 15 Minuten und daher das Heizen zu kurz kam.

Generell sieht das Haus so aus:
Doppelhaushälfte, Keller, Erdgeschoss, Obergeschoss und Dachboden
Zusammen ca. 180qm. Baujahr 1980. Kalksandstein mit leichter Dämmung (Glaswolle 5cm) und Vollklinker
Den Dachboden haben wir frisch saniert.
Verbrauch an Gas für Warmwasser und Heizung war bisher 18000kWh. Seid letztem Jahr allerdings 23000kWh, was dem Wärmetauscher geschuldet war und bei der jährlichen Inspektion der Therme dem Installateur nicht aufgefallen war.

Dank EBUS & FHEM habe ich nun auch als Laie ein paar Diagnosemöglichkeiten, da die Calormatic 430 nicht wirklich aussagekräftig ist.

VG, Dirk

VG,
Dirk

[Gyrinx]

Hallo Reinhart,

Du hast einen schonen Graphen eingerichtet.
Hast Du ein Beispiel parat, wie Du die Logs und den Graphen definiert hast?

Danke & VG,
Dirk

[Reinhart]

ich weiß jetzt nicht genau was du wissen willst, aber ich benutze die dblog zum loggen.

Code Auswählen Erweitern

define FileLog_Vorlauf FileLog ./log/Vorlauf-%Y.log Vorlauf
entweder du benutzt ein Filelog, dann sieht das so aus

Code Auswählen Erweitern

define weblink_Vorlauf SVG myDbLog:weblink_Vorlauf:HISTORY
oder die dblog, die ist im Wiki gut beschrieben wie man die einrichtet.

Und der Plot wird dann so wie im Bild definiert (bei der dblog).

LG

[goosst]

Hello

I will ask my question in English since my German writing isn't great (but an answer in German is also highly appreciated ).

setup I'm trying to get working:

• I  recently bought a version 2.2 of the base board with dc-converter.
• I'm trying to connect it via USB with a raspberry pi (see picture attached), mainly for testing/debugging want to move to an esp later
• vaillant ecotec plus (currently with a wireless thermostat), the board is connected with the e-bus

This is the output on the raspberry pi, so it looks like the board gets detected.

Code Auswählen Erweitern


dmesg | grep cp210
[    2.881760] usbcore: registered new interface driver cp210x
[    2.881836] usbserial: USB Serial support registered for cp210x
[    2.881999] cp210x 1-1.3:1.0: cp210x converter detected
[    2.897572] usb 1-1.3: cp210x converter now attached to ttyUSB0


When I try to run this command I don't get anything out.

Code Auswählen Erweitern

pi@raspberrypi:~ $ ebusd -f --scanconfig
2019-02-02 17:11:58.572 [main notice] ebusd 3.3.v3.3 started with auto scan
2019-02-02 17:11:59.061 [bus error] unable to open /dev/ttyUSB0: ERR: generic device error
2019-02-02 17:11:59.061 [bus notice] bus started with own address 31/36
2019-02-02 17:11:59.061 [bus notice] device invalid
2019-02-02 17:12:04.066 [bus error] unable to open /dev/ttyUSB0: ERR: generic device error
2019-02-02 17:12:04.066 [bus notice] device invalid
2019-02-02 17:12:09.071 [bus error] unable to open /dev/ttyUSB0: ERR: generic device error
2019-02-02 17:12:09.071 [bus notice] device invalid



So my questions:

• I'm confused with the dc-converter, am I using it correctly in this setup?
• I don't have a 17V supply to debug the steps described here https://ebus.github.io/adapter/base.en#measuring-plan. Any other advice to find potential bugs in my soldering?
• Any known reasons for getting this type of error?

Thanks in advance!

[Reinhart]

Hello!

When I look at the photo I see many "cold" solder joints (see the diodes) . Have you possibly used lead-free solder, that does not work! Otherwise, solder everything again, so that solder is also sucked through the holes on the top.

greetings
Reinhart

[john30]

Thanks in advance!

at least your red and yellow LEDs are not at the right position, so you have to exchange those. why? because the voltage for each LED is different.

to find out about the UART problem, you could disconnect it from the base board. after that the generic device errors have to disappear from the ebusd.log. if not, then the UART is most probably damaged.

oh another thing: is there any other tool running on the rpi that might use the /dev/ttyUSB0 device? I know that fhem sometimes does if things like autocreate are enabled. so please make sure it does never use the /dev/ttyUSB0, otherwise you risk damaging your heater!

[goosst]

Thanks, for the quick response.

When I look at the photo I see many "cold" solder joints (see the diodes) . Have you possibly used lead-free solder, that does not work! Otherwise, solder everything again, so that solder is also sucked through the holes on the top.

Redone them, all should be fine now.

at least your red and yellow LEDs are not at the right position, so you have to exchange those. why? because the voltage for each LED is different.

Well, that wasn't mentioned on the paper that came with the board. Looking at the website it's indeed documented ... .
Are these LEDs needed for the functioning of the board or can I just cut them off? I might damage the board before I get them desoldered.

to find out about the UART problem, you could disconnect it from the base board. after that the generic device errors have to disappear from the ebusd.log. if not, then the UART is most probably damaged.

So I just plugged in the little blue board to my raspberry pi and to my laptop. Gives the same error (see below).
I still have an FTDI lying around, is that one still supported in v2.2?

Code Auswählen Erweitern

2019-02-03 13:49:52.506 [bus error] unable to open /dev/ttyUSB0: ERR: generic device error
2019-02-03 13:49:52.507 [bus notice] bus started with own address 31/36
2019-02-03 13:49:52.507 [bus notice] device invalid
2019-02-03 13:49:57.509 [bus error] unable to open /dev/ttyUSB0: ERR: generic device error


Thanks!

[goosst]

fyi, tried to get the adapter to work on:

• rapsberry pi (with raspbian)
• ubuntu 18.10
• another old computer I had lying around (installed MKlinux on it for testing this)

on the first two, I got the message:

Code Auswählen Erweitern

[bus notice] device invalid
[bus error] unable to open /dev/ttyUSB0: ERR: generic device error
I had tried the same with my FDTI adapter and got the same error messages.

On the third computer (i386 architecture), the errors disappeared ...

Code Auswählen Erweitern

2019-02-03 18:52:51.824 [main notice] ebusd 3.3.v3.3 started with auto scan
2019-02-03 18:52:52.274 [bus notice] bus started with own address 31/36
2019-02-03 18:55:02.366 [main notice] update check: revision v3.3-4-g212b22d available


Could there be a bug in the ebusd-debian ?

Although I can't work on it anymore for another two weeks, I think I'm a step closer .

regards
Stijn

[Reinhart]

If you have the opportunity to test another UART, that would be the easiest debugging solution.

LG

[john30]

Are these LEDs needed for the functioning of the board or can I just cut them off? I might damage the board before I get them desoldered.

at least the red one is needed, potentially also the green one, the yellow one can be skipped.

[szita]

Hello, my question would be, with this panel I can stop the boiler, the boiler? can you send data directly to the heater?Ariston genius one
good for the panel?
Thanks Szita

[nols]

Also meine Ebus Platine läuft jetzt mit MQTT. Ich kann auch schon von der Vaillant Therme Daten auslesen.

Code Auswählen Erweitern

[08:41:57] openhabian@openHABianPi:~$ ebusctl i
version: ebusd 3.3.v3.3-10-gfa434e5
update check: revision v3.3-4-g212b22d available, broadcast.csv: different version available, vaillant/15.350.csv: different version available, vaillant/bai.308523.inc: different version available, vaillant/broadcast.csv: different version available, vaillant/errors.inc: different version available, vaillant/hcmode.inc: different version available
signal: acquired
symbol rate: 42
max symbol rate: 99
min arbitration micros: 3
max arbitration micros: 47
min symbol latency: 4
max symbol latency: 9
reconnects: 0
masters: 3
messages: 410
conditional: 7
poll: 0
update: 9
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0609;HW=5502", loaded "vaillant/bai.308523.inc", "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=35000;SW=0114;HW=7102", loaded "vaillant/15.350.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd

Das Readall.sh Script zeigt mir vieles an:

Code Auswählen Erweitern

[08:12:57] openhabian@openHABianPi:~/ebusd/contrib/scripts$ ./readall.sh
350 ActualPumpPower = ERR: invalid position in decode
350 ActualRoomTempDesired = ERR: invalid position in decode
350 ActualTempDesired = 0
350 ActualWeekday = Mon
350 BypassValve = off
350 C1C2State = off
350 CirPump = off
350 ClockSwitchSummerWinterDone = 29
350 CMResetCnt = ERR: invalid position in decode
350 CollPumpHRuntime = ERR: invalid position in decode
350 COMErrorCnt = 3347
350 ComfTempDesired = ERR: invalid position in decode
350 ComfTempEnabled = on
350 ControlMode = 91
350 Date = ERR: invalid position in decode
350 DcfDaten = ERR: invalid position in decode
350 DisableAutoSync = 0
350 eBUSCRC = 0
350 eBUSFifoDiffCntMax = 0
350 EDControlEnabled = off
350 EEpromMaxInkonsCnt = ERR: invalid position in decode
350 ElectronicCartridge = off
350 FillmodeStartTime = 0
350 FlowTempMin = 0.00
350 FrostProtectDelay = 43
350 HeatingCurve = ERR: invalid position in decode
350 HwcState = 0
350 HwcTempDesired = 0.00
350 HydraulicMixer = 32
350 HydraulicScheme = 0
350 IsInFloorPavingDrying = 36
350 IsInHoliday = 0
350 IsInParty = 233
350 IsInQuickVeto = 120
350 IsInSavingsFunction = off
350 IsInSingleHwcLoadingMode = off
350 IsInTeleSwitch = 2
350 LegioProtectionEnabled = no
350 LegioProtectionState = on
350 LegioPump = off
350 LoadingDelayEnabled = 50
350 LVResetCnt = ERR: invalid position in decode
350 NumCollPanels = 120
350 OffDiff = 42
350 OffsetDesTemp = 16.06
350 ONDiff = 72
350 ONMAXDiff = 1
350 ONMINDiff = 0
350 OperatingMode = 227
350 OperatingModeHwc = on
350 OperatingmodeStartTime = 0
350 OtShutdownLimit = ERR: invalid position in decode
350 OutsideTemp = 16.06;19
350 OutsideTempOffset = ERR: invalid position
350 POCResetCnt = ERR: invalid position in decode
350 PrevOperatingMode = 16
350 PumpPower = 0
350 QuickVetoTemp = ERR: invalid position in decode
350 ReducedNightTemp = ERR: invalid position
350 ResetOperatingTimes = off
350 ResetYield = 7
350 RestoreOpModeAfterHoliday = on
350 resvdColl1Sensor = 1590.19;99
350 resvdColl2Sensor = ERR: invalid position in decode
350 resvdCollPump1 = 0
350 resvdCollPump2 = 0
350 resvdStorage1Sensor = 23.06;ok
350 resvdStorage2Sensor = ERR: invalid position in decode
350 resvdStorage3Sensor = ERR: invalid position in decode
350 ROCRoomSet = 16.06
350 RoomTemp = ERR: invalid position in decode
350 RoomTempOffset = 16.06
350 RoomTempOffsetSelfWarming = ERR: invalid position in decode
350 RoomTempSwitchOn = modulating
350 RTCAdjustment = ERR: invalid position in decode
350 SavingsFunctionTime = ERR: invalid position in decode
350 SolFlowRate = ERR: invalid position in decode
350 SolHwcMaxLoadTemp = ERR: invalid position in decode
350 SolPumpBlockingTime = 0
350 StackeBUSTaskMax = 0
350 StackLifeCheckTaskMax = 30
350 StackMainTaskMax = 0
350 StartCircuitAeration = off
350 StateOfRoomCon = 1
350 StatusDcf = ok
350 SwitchOffParty = on
350 TeleSwOperatingMode = eco
350 Time = ERR: invalid position
350 TimeWindows = ERR: invalid position in decode
350 UV1State = 0
350 Variant = ERR: invalid position in decode
350 VariantDKRefreshCnt = 8
350 WDResetCnt = ERR: invalid position in decode
350 WeekDayProgSwitch = off
350 YearCalendarActive = off
350 Yield = ERR: invalid position in decode
350 YieldSensor = ERR: invalid position in decode
350 ZweipunktAnalogSlct = -
bai AccessoriesOne = ERR: invalid position in decode
bai AccessoriesTwo = ERR: invalid position in decode
bai ACRoomthermostat = off
bai APCComStatus = 0
bai APCLegioProtection = ERR: invalid position in decode
bai averageIgnitiontime = 1.4
bai BlockTimeHcMax = ERR: invalid position in decode
bai BoilerType = 2
bai ChangesDSN = 0
bai CirPump = off
bai CounterStartattempts1 = 0
bai CounterStartattempts2 = 0
bai CounterStartAttempts3 = 0
bai CounterStartAttempts4 = 0
bai currenterror = -;-;-;-;-
bai DateTime = nosignal;-:-:-;-.-.-;-
bai dcfState = nosignal
bai DCFTimeDate = ERR: argument value out of valid range in decode
bai DCRoomthermostat = on
bai DeactivationsIFC = 0
bai DeactivationsTemplimiter = 0
bai DeltaFlowReturnMax = 21.38
bai DisplayMode = 2
bai DSN = 13025
bai DSNOffset = 25
bai DSNStart = 13000
bai EBusHeatcontrol = ERR: invalid position in decode
bai EbusSourceOn = on
bai EbusVoltage = on
bai errorhistory = ERR: end of input reached
bai expertlevel_ReturnTemp = -1.81;cutoff
bai ExternalFaultmessage = off
bai externalFlowTempDesired = ERR: invalid position in decode
bai externalHwcSwitch = off
bai ExternGasvalve = 240
bai ExtFlowTempDesiredMin = ERR: invalid position in decode
bai ExtStorageModulCon = no
bai extWP = off
bai FanHours = 2193
bai FanMaxSpeedOperation = 6000
bai FanMinSpeedOperation = 750
bai FanPWMSum = 0
bai FanPWMTest = 0
bai FanSpeed = 0
bai FanSpeedOffsetMax = ERR: invalid position in decode
bai FanSpeedOffsetMin = ERR: invalid position in decode
bai FanStarts = 0
bai Flame = off
bai FlameSensingASIC = 576
bai FloorHeatingContact = off
bai FlowsetHcMax = 75.00
bai FlowsetHwcMax = ERR: invalid position in decode
bai FlowSetPotmeter = ERR: invalid position in decode
bai FlowTemp = 41.00;ok
bai FlowTempDesired = 0.00
bai FlowTempMax = 78.75
bai Fluegasvalve = off
bai FluegasvalveOpen = on
bai Gasvalve = off
bai Gasvalve3UC = off
bai GasvalveASICFeedback = off
bai GasvalveUC = off
bai GasvalveUCFeedback = off
bai HcHours = 2002
bai HcPumpMode = ERR: invalid position in decode
bai HcPumpStarts = 26136
bai HcStarts = 27000
bai HcUnderHundredStarts = 72
bai HeatingSwitch = on
bai HoursTillService = ERR: invalid position in decode
bai HwcDemand = no
bai HwcHours = 121
bai HwcImpellorSwitch = no
bai HwcPostrunTime = ERR: invalid position in decode
bai HwcSetPotmeter = ERR: invalid position in decode
bai HwcStarts = 11000
bai HwcSwitch = on
bai HwcTemp = 38.38;ok
bai HwcTempDesired = ERR: invalid position in decode
bai HwcTempMax = ERR: invalid position in decode
bai HwcTypes = 80
bai HwcUnderHundredStarts = 87
bai HwcWaterflow = 0.00
bai HwcWaterflowMax = 10.23
bai Ignitor = off
bai InitialisationEEPROM = no
bai IonisationVoltageLevel = 83.2
bai maintenancedata_HwcTempMax = 70.00
bai maxIgnitiontime = 2.6
bai minIgnitiontime = 0.2
bai ModulationTempDesired = 69.6
bai OutdoorstempSensor = -60.44;cutoff
bai OverflowCounter = yes
bai ParamToken = 3
bai PartloadHcKW = ERR: invalid position in decode
bai PartloadHwcKW = ERR: invalid position in decode
bai PartnumberBox = 00 20 11 22 37
bai PositionValveSet = 100
bai PowerValue = 10 04 53 14 64 18
bai PrAPSCounter = 0
bai PrAPSSum = 0
bai PrEnergyCountHc1 = 7249600
bai PrEnergyCountHc2 = 0
bai PrEnergyCountHc3 = 0
bai PrEnergyCountHwc1 = 433422
bai PrEnergyCountHwc2 = 0
bai PrEnergyCountHwc3 = 0
bai PrEnergySumHc1 = 1001361589
bai PrEnergySumHc2 = 0
bai PrEnergySumHc3 = 0
bai PrEnergySumHwc1 = 164931851
bai PrEnergySumHwc2 = 0
bai PrEnergySumHwc3 = 0
bai ProductionByte = 4
bai PrVortexFlowSensorValue = 0
bai PumpHours = 3753
bai PumpHwcFlowNumber = -
bai PumpHwcFlowSum = 60173
bai RemainingBoilerblocktime = 0
bai ReturnRegulation = ERR: invalid position in decode
bai ReturnTemp = 41.62;64869;ok
bai ReturnTempMax = 73.19
bai SecondPumpMode = ERR: invalid position in decode
bai SerialNumber = 30 30 30 30 38 31 31 35
bai SetFactoryValues = no
bai SetMode = auto;0.0;-;-;1;0;1;0;0;0
bai SHEMaxDeltaHwcFlow = 14.75
bai SHEMaxFlowTemp = 71.31
bai SolPostHeat = ERR: invalid position in decode
bai Statenumber = 31
bai Status = ERR: invalid position in decode
bai Status01 = 40.5;41.5;-;38.0;40.0;off
bai Status02 = auto;60;75.0;70;65.0
bai Status16 = ERR: invalid position in decode
bai Storageloadpump = 0
bai StorageLoadPumpHours = 223
bai StorageloadPumpStarts = 10707
bai StorageLoadTimeMax = ERR: invalid position in decode
bai StoragereleaseClock = ERR: invalid position in decode
bai StorageTemp = 40.12;ok
bai StorageTempDesired = 56.00
bai StorageTempMax = 68.12
bai TargetFanSpeed = 0
bai TargetFanSpeedOutput = 0
bai TempDiffBlock = 0
bai TempDiffFailure = 0
bai TempGradientFailure = 0
bai Templimiter = off
bai TemplimiterWithNTC = yes
bai TempMaxDiffExtTFT = 0.00
bai Testbyte = 3
bai TimerInputHc = on
bai ValveMode = ERR: invalid position in decode
bai ValveStarts = 9862
bai VolatileLockout = no
bai VolatileLockoutIFCGV = no
bai VortexFlowSensor = ERR: invalid position in decode
bai WarmstartDemand = yes
bai WarmstartOffset = ERR: invalid position in decode
bai WaterHcFlowMax = 1800
bai WaterPressure = 1.665;ok
bai WaterpressureBranchControlOff = off
bai WaterpressureMeasureCounter = 97
bai WaterpressureVariantSum = 65425
bai WP = off
bai WPPostrunTime = ERR: invalid position in decode
bai WPSecondStage = off
broadcast datetime = ERR: no data stored
broadcast error = ERR: no data stored
broadcast hwcStatus = ERR: no data stored
broadcast id = ERR: invalid address
broadcast load = ERR: no data stored
broadcast outsidetemp = ERR: no data stored
broadcast signoflife = ERR: no data stored
broadcast vdatetime = 08:17:30;08.02.2019
general valuerange = ERR: invalid address
memory eeprom = ERR: invalid address
memory ram = ERR: invalid address
scan.08 id = 21;16;39;0010019276;0001;013459;N1
scan.15 id = 21;16;38;0020124472;0082;027362;N1

Ich habe die ebusd Version mit MQTT kompiliert und es läuft auch. Mit MQTTfx kann ich aber nur einige Daten sehen. Wie kann ich die anderen Daten auslesen und ändern?
Ich möchte eigentlich nur den Modus von Urlaub auf Automatisch stellen.
In der /etc/default/ebus habe ich folgende Parameter stehen:

Code Auswählen Erweitern

EBUSD_OPTS="-d /dev/ttyebus --scanconfig -p 8888 -l /var/log/ebusd.log --mqtthost=192.168.170.99 --mqttport=1883 --mqttuser=openhab --mqttpass=openhab --mqtttopic=ebus/%circuit/%name/%field"

Wie komme ich denn an die anderen Werte von z.B. der Calormatic 350?

[Reinhart]

Hallo,

der Fehler "invalid position in decode" deutet darauf hin, dass die CSV nicht exakt zu deiner Hardware/Software passt. Da es schon neuere CSV gibt, würde ich einmal testen auf Online CSV umzustellen und schauen ob die Erkennung dann besser wird. Schau auch einmal ob hier im Forum schon jemand die 350 angepasst hat.

Code Auswählen Erweitern

-c http://ebusd.eu/config/
hänge einfach den Parameter zu deiner Config dazu und restarte den Dämon.

LG
Reinhart

[Reinhart]

Nachtrag, ich kenne die 350 nicht aber schau einmal was der Eintrag IsInHoliday bewirkt!

Code Auswählen Erweitern

r;wi,,IsInHoliday,,,,,"2800",,,UCH,,,
dieses Register läßt sich beschreiben.

Das ist aber ein Installer Wert (wi), denn musst du in der Config zuerst freigeben sonst kannst du nicht schreiben.

Code Auswählen Erweitern

--accesslevel=*

LG