eBus Adapter Version 2.0 / 2.1 / 2.2

[fim]

Reinhart, vielen Dank!

[galileo]

Hallo fim!

C1 (10 uF) muss entfallen. Dieser Kondensator führt zu einer schlechten Kurvenform an Bus.
R10 und D5 können in der Folge entfallen, weil unnötig (stört aber auch nicht wenn sie bleiben)

LG

[fim]

C1 (10 uF) muss entfallen. Dieser Kondensator führt zu einer schlechten Kurvenform an Bus.
R10 und D5 können in der Folge entfallen, weil unnötig (stört aber auch nicht wenn sie bleiben)

galileo, Vielen Dank!
Ja, ja, ich erinnere mich, dass in C1 (10uF) keine Notwendigkeit besteht.
Wie ich es verstehe, bedeutet dies, dass P10 und D5 zu Debuggingzwecken auf der Platine sind.
Mit anderen Worten, es stellt sich heraus, dass man ein solches Schema sicher verwenden kann?

[galileo]

Ja, passt so. Nur der CNY17 muss ein CNY17-4 sein.
LG

[galileo]

Hallo fim,
Da ist noch ein fataler Fehler: Du hast die beiden Grounds zusammengeschlossen. Diese müssen aber getrennt sein.
Also links von den Optokopplern ein eigenes Netz "GND2" und rechts von den Optokopplern "GND".
LG

[fim]

Da ist noch ein fataler Fehler: Du hast die beiden Grounds zusammengeschlossen. Diese müssen aber getrennt sein.
Also links von den Optokopplern ein eigenes Netz "GND2" und rechts von den Optokopplern "GND".

Hallo galileo,
Vielen Dank!

Entschuldigung für meine Nachlässigkeit, ich habe mit Optokopplern nicht gut gearbeitet.
jetzt: OK1 (GND2) und...    OK2 (rotate MR180)

LG

[CrazYoshi]

Hi guys,
I have received the eBus Adapter and now I successfully connected to my network. What I don't understand so far is if the adapter is able to share the ebus with my Vaillant thermostat inside my place or I have to unplug it.
I don't know if the eBus can supply enought power to run both correctly.

Let me know!

[Reinhart]

Hello CrazYoshi!

The eBus is simply wired in parallel, so you clamp the board parallel to it. For 98% of users, the power of the eBus is sufficient. It only becomes critical when many devices ( >4-5 ) have been connected to the bus.

Please do not disconnect the Calormatic, test it!

LG
Reinhart

[CrazYoshi]

Hello CrazYoshi!

The eBus is simply wired in parallel, so you clamp the board parallel to it. For 98% of users, the power of the eBus is sufficient. It only becomes critical when many devices ( >4-5 ) have been connected to the bus.

Please do not disconnect the Calormatic, test it!

LG
Reinhart

Ok thanks for your quick reply.
I have successfully connected ebusd with the eBus Adapter. Now from the webpage of the WeMos I see:

Code Auswählen Erweitern

Build: 20171230
Chip ID: 009f4801
CPU frequency: 80
Free heap: 37192
Hostname: ebus-9f4801
ebusd device string: 192.168.1.23:9999
ebusd connected: yes (inactive)
eBUS signal: acquired
But if I run ebusctl info from my raspi I get:

Code Auswählen Erweitern

version: ebusd 3.1.v3.0-35-gb0e20b7
update check: revision v3.1-1-g60a18d1 available, broadcast.csv: different version available
signal: no signal
reconnects: 0
masters: 1
messages: 10
conditional: 0
poll: 0
update: 7
address 31: master #8, ebusd
address 36: slave #8, ebusd
What should I do now?How can I start see some heating data?

[john30]

What should I do now?How can I start see some heating data?

I guess you need to initiate a full scan, as it seems you have no controller attached to the bus.

[CrazYoshi]

I guess you need to initiate a full scan, as it seems you have no controller attached to the bus.

I have performed a full scan but the result it's still the same:

Code Auswählen Erweitern

pi@homedaemon:~ $ ebusctl scan full
done
pi@homedaemon:~ $ ebusctl scan result
done
pi@homedaemon:~ $ ebusctl info
version: ebusd 3.1.v3.0-35-gb0e20b7
update check: revision v3.1-1-g60a18d1 available, broadcast.csv: different version available
signal: no signal
reconnects: 0
masters: 1
messages: 10
conditional: 0
poll: 0
update: 7
address 31: master #8, ebusd
address 36: slave #8, ebusd


[john30]

Code Auswählen Erweitern


...
signal: no signal
...


without signal, the scan is useless. did you set up the device string in /etc/default/ebusd according to the wemos settings?

[CrazYoshi]

without signal, the scan is useless. did you set up the device string in /etc/default/ebusd according to the wemos settings?

yes, I change the file /etc/default/ebusd:

Code Auswählen Erweitern

# /etc/default/ebusd:
# config file for ebusd service.

# Options to pass to ebusd (run "ebusd -?" for more info):
EBUSD_OPTS="--scanconfig -d 192.168.1.23:9999"

# MULTIPLE EBUSD INSTANCES WITH SYSV
# In order to run multiple ebusd instances on a SysV enabled system, simply
# define several EBUSD_OPTS with a unique suffix for each. Recommended is to
# use a number as suffix for all EBUSD_OPTS settings. That number will then be
# taken as additional "instance" parameter to the init.d script in order to
# start/stop an individual ebusd instance instead of all instances.
# Example: (uncomment the EBUSD_OPTS above)
#EBUSD_OPTS1="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0 -p 8888 -l /var/log/ebusd1.log"
#EBUSD_OPTS2="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900acTF-if00-port0 -p 8889 -l /var/log/ebusd2.log"
#EBUSD_OPTS3="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900beCG-if00-port0 -p 8890 -l /var/log/ebusd3.log"

# MULTIPLE EBUSD INSTANCES WITH SYSTEMD
# In order to run muiltiple ebusd instances on a systemd enabled system, just
# copy the /usr/lib/systemd/system/ebusd.service file to /etc/systemd/system/
# with a different name (e.g. ebusd-2.service), remove the line starting with
# 'EnvironmentFile=', and replace the '$EBUSD_OPTS' with the options for that
# particular ebusd instance.


This is what WeMos show:

Code Auswählen Erweitern

Build: 20171230
Chip ID: 009f4801
CPU frequency: 80
Free heap: 37392
Hostname: ebus-9f4801
ebusd device string: 192.168.1.23:9999
ebusd connected: yes (inactive)
eBUS signal: acquired

[Reinhart]

have you the correct Ip an Port?


LG

[CrazYoshi]

have you the correct Ip an Port?
LG

if I undestand correclty I have to change both ebusd TCP port and Management TCP port to 8889 and 9999, correct?
Below my actual WeMos config

Here instead ebusd log after configuration change to the one you posted:

Code Auswählen Erweitern


2018-02-17 12:46:19.429 [main notice] SIGTERM received
2018-02-17 12:46:19.980 [main notice] ebusd 3.1.v3.0-35-gb0e20b7 started with auto scan
2018-02-17 12:46:20.179 [bus notice] bus started with own address 31/36
2018-02-17 12:46:20.179 [bus notice] signal acquired
2018-02-17 12:46:20.241 [bus notice] new master 10, master count 2
2018-02-17 12:46:21.292 [bus notice] new master 03, master count 3
2018-02-17 12:46:22.349 [main notice] ebusd stopped
2018-02-17 12:46:28.533 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:46:28.772 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:46:28.938 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:46:30.317 [main error] scan config 08: ERR: read timeout
2018-02-17 12:46:32.690 [main error] scan config 15: ERR: read timeout
2018-02-17 12:46:38.574 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:46:38.839 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:46:38.938 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:46:39.101 [update notice] unknown MS cmd: 1008b5110102 / 06011496467864
2018-02-17 12:46:48.593 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:46:48.857 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:46:48.939 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:46:58.595 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:46:58.881 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:46:58.939 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:47:08.585 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:47:08.898 [update notice] unknown MS cmd: 1008b5040100 / 0a00ffffffffffffff6008
2018-02-17 12:47:08.940 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:47:09.108 [update notice] unknown BC cmd: 10feb516080045101306010215
2018-02-17 12:47:09.403 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:47:09.653 [update notice] unknown MS cmd: 1008b5110102 / 06011496467864
2018-02-17 12:47:09.914 [update notice] unknown MS cmd: 1008b5110100 / 0903020c001f10000000
2018-02-17 12:47:10.169 [update notice] unknown MS cmd: 1008b5100305ff01 / 0101
2018-02-17 12:47:10.381 [update notice] unknown MS cmd: 1008b512020064 / 00
2018-02-17 12:47:10.634 [update notice] unknown MS cmd: 1008b5120204ff / 0101
2018-02-17 12:47:10.857 [update notice] unknown BC cmd: 10feb51603016008
2018-02-17 12:47:18.634 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:47:18.860 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:47:18.940 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:47:28.623 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:47:28.886 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:47:28.947 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:47:38.639 [update notice] unknown MS cmd: 1008b5110101 / 09403f6008ffff0000ff
2018-02-17 12:47:38.909 [update notice] unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2018-02-17 12:47:38.948 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2018-02-17 12:47:39.179 [update notice] unknown MS cmd: 1008b5110102 / 06011496467864