-
Notifications
You must be signed in to change notification settings - Fork 1
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
eBUS Adapter Shield v5 & Raspberry Pi 5 #47
Comments
I tested it recently on a RPi 5 and it worked flawlessly. can you check if it works when only connecting the 4 first pins on the W2 connector? |
Many thanks for the support! I have successfully connected the adapter via the first 4 pins on the W2 and received data from the heating control with ebusd. Here is a printout of the /boot/config.txt. The status of the interface ("easi>") now also shows the connection to the eBus and ebusd. Unfortunately, I have to revise my information on the LED status when restarting (power) and the eBUS adapter is connected normally: I only had to make an adjustment in the ebusd config (/etc/default/ebusd).
The eBUS adapter does not occupy PIN31. Do you mean PIN13 (GPIO27) of the RPi 5? |
I guess with enable_uart=1 it won't work as the port is then used by a system console (this is only needed on older OS versions), so you probably answered yes to the login shell over serial here https://adapter.ebusd.eu/v5/raspberrypi.en.html#configuration-with-raspberry-pi-os |
Hi @Thde23 It looks like I have the same problem as you. I have changed the settings of the Adapter Shield so it's working through WiFi and now I see all kinds of data coming in through MQTT. So the Adapter Shield is working as expected, but somehow I can't connect it through my Raspberry Pi. Before I try to use the only first 4 pins. Is it already working as it should? Thanks! |
Hello @stroel, at the weekend I identified pin 13 (GPIO 27) as the cause of the problem. I have not yet been able to find out exactly what is wrong with pin 13. |
Hi @Thde23 Thank you for your feedback. But one thing which is still strange, like you said before, I see that I have /dev/ttyAMA10 instead of /dev/ttyAMA0. Anyway, I see data coming in through MQTT. |
I've tested it with Raspi 3B, 4B, and 5, measured with my osci, and found out that the timing and level during power up are quite different on the 5, so this can only work when removing the pin in the connection. instructions are placed to the docs and future versions will no longer have the issue with Raspi 5 |
Thanks @john30 Still working perfectly. Thanks! |
Hello,
I have already got the eBUS Adapter v5 running completely under the following configuration and have generated data points under ioBroker.
Now I have plugged eBUS Adapter v5 onto a Raspberry Pi 5 (Raspberry Pi OS (Debian 12)).
Then set everything up as described in the instructions at https://github.com/john30.
Unfortunately I get no signal at
ebusctl info
.When restarting (power), the blue LED only flashes once for 0.5s. The green and red LEDs do not light up at all!
When the button is pressed, only the blue LED lights up (voltage present).
I have activated and set up both Wifi Station/Clien and WiFi Access Point in the interface ("easi>").
A connection is established if the eBUS adapter is mounted on the Raspberry Pi 3b or is only operated separately with a 5V power supply unit.
If the adapter is mounted on the Raspberry Pi 5, a connection can no longer be established.
I suspect that the eBUS Adapter v5 is not booting correctly when it is mounted on the Raspberry Pi 5.
I used a Siemens 5V/3A control cabinet power supply.
ls -l /dev
dmesg | grep ttyAMA
pinctrl get 0-15
I would be grateful for any suggestions and hope the translation from german to english is reasonably understandable.
The text was updated successfully, but these errors were encountered: