eBUS adapter 3

Welcome to eBUS Adapter 3!

This is the documentation of the eBUS adapter v3.1, which can be used to communicate with an eBUS enabled heating, ventilation or solar system.

The documentation of the previous version v3.0 is available here.

You can reserve such an adapter here and it will then be sent in sequence as soon as the next batch is available.

Introduction

Version 3 of the eBUS adapter fulfils the arbitration times required by the eBUS specification for the first time.

This is made possible by the use of a PIC which, among other things, brings the following advantages:

• minimal time delay due to hardware-related programming
• flexible, configurable variants for connecting to the host:
  • USB serial via CP2102 (onboard)
  • Raspberry Pi via GPIO/ttyAMA0
  • WIFI via LOLIN/Wemos D1 mini with ESP-8266
  • Ethernet via USR-ES1 module with W5500
• full support for ebusd enhanced protocol and standard protocol
• updatable firmware using a serial bootloader

In order to be able to get all these options on a 5cm x 5cm board, almost only SMD is used:

The SMD technology also offers some advantages:

• high packing density
• all variants on one board
• cheap assembly

Two of the variants also offer the option of connecting sensors and/or displays.

By using a DC-DC converter and galvanic isolation of the signals the eBUS is completely isolated and only marginal current is drawn from the eBUS without any fluctuation (class 0 according to specification chapter 10.7).

Connections

This is an overview of the individual components and their connections:

• Heating/ventilation/solar thermal system
  is connected to the adapter via a 2-wire cable.
• Adapter
  connected to ebusd either via
  • USB (UART),
  • GPIO (UART) of the Raspberry Pi,
  • WIFI (Wemos) or
  • LAN (USR-ES1 module with W5500).
• ebusd
  interprets the eBUS protocol and provides the data bidirectionally via MQTT, HTTP, KNX, and TCP port for Home-Assistant, KNX, Node-Red, FHEM, and others.

Variants

USB support is built into all variants, as an CP2102 is always assembled directly on the board. This is necessary, to e.g. update the PIC firmware or to adjust the Ethernet configuration.

The corresponding variant is set via ebuspicloader (or J12).

The protocol between ebusd and the adapter is either the eBUS protocol directly (“standard protocol”) or the ebusd “enhanced protocol”. The enhanced protocol uses all advantages of the adapter by handling the eBUS arbitration directly from the PIC firmware.

USB

To use the adapter via USB, just connect J2 with your host.

The variant is set via ebuspicloader (or J12) to USB.

The power is supplied directly via the USB connector J2 on the adapter.

The ebusd device configuration is e.g. -d ens:/dev/ttyUSB0, where ttyUSB0 might be different when several USB serial devices are connected.

Raspberry Pi

Using an at least 2x9 socket J8, the adapter can be plugged onto the Raspberry Pi directly.

The variant is set via ebuspicloader (or J12) to RPI.

The power is supplied directly via the Raspberry Pi GPIO socket J8.

The ebusd device configuration is: -d ens:/dev/ttyAMA0 --latency=50

Details on setting up the Raspberry Pi can be found here.

WIFI

By plugging a LOLIN/Wemos D1 mini with ESP-8266 onto socket J9, the adapter can be used via WIFI.

The variant is set via ebuspicloader (or J12) to WIFI.

The power is supplied directly via the USB connector J2 on the adapter. When the Wemos is configured correctly, no serial device appears on this USB connection.

Attention: The Wemos are incredibly delicate with regard to the power supply! A variety of effects come up when the power supply is insufficient, e.g. reboots, or no connection at all, or only poor and unstable connection to the Access Point.

The Wemos has to be flashed with a suitable firmware, e.g. ebusd-esp (starting from version 23.10.2022). ebusd-esp has to be configured to “Adapter 3.1 RX+TX high-speed”.

The ebusd device configuration is e.g. -d ens:192.168.178.2:9999, where 192.168.178.2 has to be replaced with the right IP address.

Ethernet

By plugging a USR-ES1 modul with W5500 onto socket J10, the adapter can be used via LAN.

The variant is set via ebuspicloader (or J12) to Ethernet.

The power is supplied directly via the USB connector J2 on the adapter.

The Ethernet configuration (IP address, network mask, gateway) is done via the bootloader in the PIC through the USB port J2, see here: Ethernet configuration. By default, it is configured for DHCP and the adapter appears with a host name prefix of “aebus3” in the router.

The ebusd device configuration is e.g. -d ens:192.168.178.2:9999, where 192.168.178.2 has to be replaced with the right IP address (ebusd enhanced high-speed mode is irrelevant for network-based transport).

The PIC firmware sets the MAC address of the adapter in the LAN to AE:B0:53:XX:XX:XX, where the XX depend on the ID of the PIC (AEB053 stands for “Adapter eBUS 3”).

Jumpers/pin headers, functions

In the variants with Wemos and Raspberry Pi, additional pin headers are available for connecting further components.

* To the points in brackets:

• I2C is currently not yet supported by the ebusd-esp firmware.

PIC AUX J12

This connector holds pins of the PIC and their assignment and usage depends entirely on the PIC firmware, see PIC Firmware.

Important note: The pins at J12 must never be connected to any pin on the other jumpers/pin headers/sockets as separate power sources are used here. Any connection endangers the adapter and devices on the eBUS!

PIC PROG J11

The PIC programming connector J11 allows updating the Firmware of the PIC including the bootloader with an appropriate programming device. This should only be necessary in rare cases, as the PIC was programmed before delivery and can be updated with newer firmware via the embedded bootloader. For more details, see PIC Firmware.

Additional functions

LEDs

The adapter has 4 LEDs with the following assignment:

• yellow: power supply PIC
• blue: signals from PIC
• green: eBUS receive
• red: eBUS send

The PIC is only supplied with power and can work at all when the yellow LED lights up. The green and red LEDs light up on the corresponding eBUS traffic and the green one lights up permanently if the eBUS line is not yet connected or the voltage level on the eBUS line is too low. The blue LED is controlled by the PIC firmware, which is described here.

Links

Here are some links that contribute to the topic or contain basic information:

• eBUS spezification (physikal layer OSI 1)
• documentation for Adapter V 3.0
• ebusd-esp firmware for Wemos D1
• ebusd wiki