Setting it up?

[MarenB]

Alright, I did make some progress:

• ESP32 (Wroom) arrived
• M-Bus converter arrived
• Firmware compiled and flashed
• connection to MQTT-Broker established
• wired everything together and connected to connector 145 of the heater

First results:

• LED of the converter blinks
• no connection, virtualvitotrol/connected == false
• heater failed with some error code (forgot to take a note)

Questions:

• my heater has a second circuit incl. internal extension H1 -> does that possibly cause a adress conflict?
• how sensitive is the M-Bus in general, i.e. to open lines and how long may the wire be? I installed ~1m and left the ends open once (converter removed) and I think that may also have caused an issue
• the purpose of the jumper is to provide power from VDD, so it must be plugged in, correct?

[MarenB]

It re-occured. Error codes are BA and C5, basically announcing communication issues. Disconnected the ESP32 from power now to see if it also happens, when the installation is passive.

I also checked the "Kurzabfrage" and line 9 stays completely zero, means no remote control deteced for any heating circuit. Guess, I need to activate debugging and carry my PC downstairs...

[MarenB]

Ok, I'll give up for today, I guess.
I do not get a connection, but at least the heater works like before :)

Because of #6 (comment) I still do not use the latest version.

However, I think there might be a mistake in the default config for ESP 32: pins 16+17 should refer to Serial2, don't them? But Serial0 doesn't work for me either...

These are my current settings:

`#define MODBUS_BAUD SERIAL_8E1
#define ModbusSerial Serial2
#define DebugSerial Serial

#define DEBUG false`

[meks007]

pull the latest commit and try to #include "wifi_mgr_portal.h" after #include "mqtt.h" in main.h

or, alternatively, skip the wifi manager by defining your wifi / mqtt stuff in configuration.h:

//#define WIFI_SSID "CHANGEME"
//#define WIFI_PASSWORD "CHANGEME"
//#define WIFI_HOST "Virtual Vitotrol"

and

//#define MQTT_HOST "CHANGEME"
//#define MQTT_USER "CHANGEME"
//#define MQTT_PASS "CHANGEME"

[MarenB]

Forgot to mention:

• D2 (the LED next to the M-Bus terminals) is now fully illuminated, with just a little variaton in brightness (based on data traffic?)
• RX-LED is constantly lit just a tiny bit
• TX-LED is off
• Jumper is connected.
• LED1 is off.

Will need to check VDD, I guess.

[dumpfheimer]

Ok, so I checked my wiring. I am using GND and 3.3V to the TTL and 16 on RXD, 17 on TXD (on the ESP32). My RX and TX LEDs only light up when in use

[MarenB]

btw, there's a typo in the instructions:

Connect MB_A and MB_D to the Terminals 145

Should be "MB_B", not _D. And it might be worth noting that polarity doesn't matter.

[dumpfheimer]

1m should be no issue at all. M-Bus was designed for electrical metering devices
I have the jumper installed
Not sure about the extension but my GUESS is that it should be fine as long as you do not have another "remote control".

Did you set up the heater for a remote control?

It would be great if you could keep track of what you needed to do, so we could compile a better TODO / Setup guide for others

[MarenB]

yeah, read in the manuals meanwhile that 15m is fine. That was just a stupid error of myself assuming that the four terminals of the converter are designed for two wire pairs next to each other, but it's 1+3 and 2+4.

[MarenB]

Setting up the heater:
I didn't find any reference in its manual to inform it about the remote control being installed. The only things I can change is the influence of the actual room temperature (parameter b2), the pump logic (parameter b5) and in which mode (normal/reduced) it should apply (parameter b0).
But if I understand the installation manual of the Vitotrol correctly, all you have to do is connecting the remote control and select at that one onto which heating circuit it shall affect. I believe, this influences the device's ID on the bus and the heater detects it automatically then.

[dumpfheimer]

could you post the output of http://192.168.XX.XX/ ? there might be some useful information there

[dumpfheimer]

very strange. I normally only get dataset 29 and 52, never had 25. the whole concept of the 3f/3b command seems to be misunderstood, thogh. I am very interested in the communications you will hopefully be able to record

[dumpfheimer]

{25: [253,135]29: [2,0,63,87,40,24,18,201,63,0,198,0]}

Ah, nice! is it 9° outside?
Its interesting you have so many values. I only have this: {29: [0,0,0,0,0,0,14,0,0,0,196,0]}

[MarenB]

You can be sure, I will record everything :) If accessible, I will record the UART, otherwise KM.

[MarenB]

{25: [253,135]29: [2,0,63,87,40,24,18,201,63,0,198,0]}

Ah, nice! is it 9° outside? Its interesting you have so many values. I only have this: {29: [0,0,0,0,0,0,14,0,0,0,196,0]}

It is, indeed!

[dumpfheimer]

The temperatures are *2, so 18 is actually 9. I am guessing 87 is your warm water, which would be 43.5°?
63 (=31.5) is your abgas temp maybe?
87 (=43.5) warmwater?
40 (=20?) .. some setpoint?
24 (=48?) .. umwälzpumpe drehzahl?
18 (=9).. outside temp
63 (31.5) abgas temp again? =)
0.. freezing point of water
198 (0b11000110) seems to be a status register (meaning every bit is a true/false of something)

[MarenB]

These data are just a few seconds apart:

{25: [253,135]29: [6,0,75,86,40,24,18,201,75,0,198,0]}

Most values should be self-explaining, tempk is Kesseltemperatur, VL Vorlauf, WW Warm water

[dumpfheimer]

do you get a register 52 after some time?

[MarenB]

Ok, let's close this particular thread with a final success report:

Yellow: target temp normal (21°C)
Blue and purple: two relevant actual room temperatures obtained via Aquara Zigbee Sensors; which ever is lower is sent to the heater
Orange: target water temperatur upstream the radiators
Blue and "nervous": outside temp before low pass filter

There's a clearly visible influence of the actual room temperature, that's fantastic!
Next task is probbably to adopt the heating curve.

[MarenB]

No, nothing else since ~3500s uptime.

[dumpfheimer]

what vitotrol did you end up ordering?

[MarenB]

Sorry, I didn't know it would open a new thread, when I reply by email.

I ordered a used Vitotrol 200A, the cheapest one I found and the one we don't know how it would communicate in my system environment.
Because actually it should be compatible according to the heater's manual. Maybe it does something unexpected, when it recognizes my heater request message, we'll find out soon.

[MarenB]

[dumpfheimer]

to be honest, I think your heater might not be compatible with the 200A. It is, however, very badly documented, so I might be wrong.

[dumpfheimer]

For anyone reading up: the remote was compatible! =)

[MarenB]

And for those who want to read more:

#24 (comment)