-
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
Modbus Connection Issue with Heidelbridge - Wallbox Flashing White and Blue #2
Comments
Hi darkblum,
Please also check the ESP32 serial port outputs. It should print a lot of messages (especially on startup), that might be helpful. Also: what kind of setup are you using? Breadboard or custom PCB? Which ESP32 board are you using exactly? |
Hello BorisBrock, I've managed to establish the correct connection to the wallbox. Initially, I thought that the A/B connection on the left and right sides of the PCB had the same orientation, but that wasn’t the case. On the left side, it’s B/A, while on the right side, it’s A/B. So now, there's no more blinking. I’ve also integrated the charger into EVCC and set up the load point, but my EV isn’t registering as "connected." The vehicle status always shows as "disconnected," and I’m getting the information through MQTT. My EV is entering a charging failure state due to no current being supplied and I don't hear the relais clicking from the Heidelberg. I am using ESP32 WROOM-32D with usb-c connector and no breadboard only jumper cables and WAGO connectors. What should I check next? |
Hi darkblum, I'm using this project with a VW ID3 and the vehicle connection detection works 100% reliably. This week I also connected a Skoda Enyaq from a neighbor and that also worked very well. Which car are you using? For solving your issue, I would recommend reading the serial outputs from the ESP32 with a serial monitor. HeidelBridge will read the register containing the connection status cyclically every few seconds, and there should be plenty of messages. This way we can see, if the wallbox is not detecting your vehicle at all, or if reading the register fails. So:
PS: Do you see other values from the wallbox in evcc? Did you check the MQTT values (e.g. with MQTT Explorer)? Do you see valid values here? |
Hi,the car I’m using is a Tesla Model 3. Ideally, I’d like the wallbox to charge different guest vehicles as well, so it would be best if no specific vehicle was predefined. I’m receiving new inputs via MQTT every few seconds, but all values are showing as 0. I’m using MQTT Explorer with Home Assistant, and I plan to analyze the logs later using VS Code/serial monitor or do you've a better idea to use serial monitor? Thanks for the help! |
Hi, it should not make any difference which car you are using. Only if you want it to show up in evcc in a defined way, you would need to do some additional configuration there. The VS Code Serial Monitor should work fine. That's what I'm using as well. PS: When compiling the code you can choose between two environments: "dummy" and "heidelberg". You could also try using "dummy", which will provide some hard coded values. These should definitely show up in MQTT/Home Assistant. |
Hello, first of all thank you for the great project. Unfortunately my Heidelberg EC is also blinking the Modbus Failure. It starts when configuring the Wallbox for Modbus and never ends. I checked the DIP Switches several timesI tried different rs232-Modbus Converter and also the wiring. No change. |
@nobsch First of all you should check what kind of error you are getting EXACTLY. The different blink patterns are described in the Heidelberg EC manual (chapter 1.6). The installation manual has all the relevant info on setting the dip switches etc. Just in case you want to double/tripple check. Regarding heidelbridge:
Feel free to attach an example log here (don't forget to press reset on the ESP32, so that the log also contains the initialization part). |
Thank you Boris. Error Code is the communication failure (6x White, 3xBlue). I have checked the dip Switches several times. Because there are only 2 changes to do, it is not so complex. |
Now I have tried it. |
@nobsch did you conect L and N the right way ( even if you have got a test setup with schuko connector). because if you connect L and N mixed up, the heidelberg box is blinking the same error code (=input voltage error) as with a communicating error... |
You mean the Power connection of the wallbox? |
Today I got response from Heidelberg support. |
Unfortunately, I am unable to establish a connection through the Heidelbridge.
I followed your instructions carefully:
However, the Wallbox is still flashing white and blue, indicating a Modbus error.
I also added a 120-ohm resistor between Pin A and B, but there has been no change.
Did I overlook something?
Let me know
The text was updated successfully, but these errors were encountered: