[abgeschlossen] eBUS Adapter 3.0 Betatest

JimKnopf · 13 Dezember 2020, 17:07:05

Hi John!

Ich konnte den Wemos wiederbeleben. Ich habe ihn erneut geflasht und unter Advanced die Speichergröße auf 16 MByte gestellt, in der Hoffnung dass der Speicher oberhalb des Programms gelöscht wird.
Jetzt komme ich wieder in das Konfigurationsmenü aber die Werte werden nicht gespeichert. Regelmäßig wird noch immer ein Reset ausgeführt. Eine andere Spannungsversorgung habe ich ausprobiert, kein Unterschied.

Code Auswählen

Enter your choice: F
Performing hard factory reset...
EEPROM reset, rebooting...

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 3584, room 16 
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld


Welcome to eBUS adapter 3, build 20201122
Configured as WIFI access point EBUS without password.
For configuration with web browser, connect to this WIFI and open http://192.168.4.1/
Entering configuration mode.
Chip ID: 009BC25D
Hostname: ebus-9bc25d

Factory-Reset funktioniert leider auch nicht. Anscheinend kommt die Firmware nicht an den Speicher ran.
EDIT: Jetzt konnte ich den Wemos vollständig wiederbeleben. Wichtig!: wer mit NodeMCU unter Windows flasht sollte unbedingt die neuste Version verwenden. Zu finden unter: https://github.com/marcelstoer/nodemcu-pyflasher/releases
Hier unter Erase Flash : "yes, wipes all data" auswählen, damit der Speicher wirklich vollständig gelöscht wird, nicht nur der Bereich vom neuen Programm überschrieben wird.
Bei mir hat das geholfen.

Jetzt zum eigentlichen testen.
Der Adapter 3 hängt parallel mit dem bisherigen Adapter 2 (selbst gefädelt) zusammen mit der ISM7 von Wolf an der Heizung.
Während der Adapter 2 weiterhin recht ordentlich Daten liefert, hat der Adapter 3 (während Adapter2 nur passiv ist) probleme mit pollen von Daten:
Ja, wer lesen kann ..... ,,enh:" musste noch vor die ip, jetzt läufts.

Gruß,
Burkhard

Reinhart · 13 Dezember 2020, 19:03:33

zum Problem mit den Wemos, wie John schon schreibt sind die manchmal etwas zickig. Ich habe daher in den Testkits die ich versendet habe die alle schon geflasht und getestet ob sich der AP aufspannt!

Aber wie auch JimKnopf schon festgestellt hat, ist bei Fehlfunktionen oft ein totaler Reset notwendig und den Dingern wieder Leben einzuhauchen.

LG

JimKnopf · 13 Dezember 2020, 19:11:35

Ich habe jetzt auch erste Ergebnisse:
Größtenteils läuft alles perfekt. Recht selten kommt aber folgendens:

Code Auswählen

2020-12-13 19:07:22.082 [update notice] received write feuerung betrd QQ=10: Brauchwasser_Heizen;Kesselpumpeaus;51.69;-;-;60.0;-
2020-12-13 19:07:22.137 [bus error] device status: eBUS comm error: framing
2020-12-13 19:07:22.138 [bus error] arbitration start error
2020-12-13 19:07:22.320 [update notice] sent poll-read regler WarmwasserSoll QQ=01: 60.0

~~Soll ich das ISM7 noch abnabeln? Nicht dass das dazwischen funkt.~~Ich habe es abgehängt, bzw. den Strom weggenommen. Fehler bleiben.Habe jetzt log="all error" mit in den Aufruf genommen.
Gruß,Burkhard

john30 · 13 Dezember 2020, 20:33:42

Zitat von: JimKnopf am 13 Dezember 2020, 19:11:35
Ich habe jetzt auch erste Ergebnisse:
Größtenteils läuft alles perfekt. Recht selten kommt aber folgendens:
Code Auswählen Erweitern
2020-12-13 19:07:22.082 [update notice] received write feuerung betrd QQ=10: Brauchwasser_Heizen;Kesselpumpeaus;51.69;-;-;60.0;- 2020-12-13 19:07:22.137 [bus error] device status: eBUS comm error: framing 2020-12-13 19:07:22.138 [bus error] arbitration start error 2020-12-13 19:07:22.320 [update notice] sent poll-read regler WarmwasserSoll QQ=01: 60.0

~~Soll ich das ISM7 noch abnabeln? Nicht dass das dazwischen funkt.~~Ich habe es abgehängt, bzw. den Strom weggenommen. Fehler bleiben.Habe jetzt log="all error" mit in den Aufruf genommen.
Gruß,Burkhard

Das ist jetzt ein neuer Detailgrad, der erst mit dem Adapter 3 möglich ist. Hier ist jetzt erkennbar, dass eine Arbitrierung regulär vom ebusd verloren wurde, was dann auch gleichzeitig zu einem RS232 Framing Error geführt hat.
Aber ich sehe schon, das als Fehler einzustufen ist etwas zu krass, denn es handelt sich um völlig normales und zu erwartendes Verhalten an einem Multi-Master Bus wie diesem.

hErMeS · 13 Dezember 2020, 21:38:56

Meinen Fehler mit dem ebusd Daemon habe ich mittlerweile gefunden. Das kleine, aber nicht wegzulassende "enh:" beim Device direkt davor.
Jetzt erhalte ich auch Meldungen.
Wird das in einer späteren Version automatisch abgeprüft so dass man das eventuell weg lassen kann? Anleitung genau lesen, ich weiß. 4 kleine Zeichen die über Erfolg und Misserfolg entscheiden.

Weisen folgende Meldungen (alles auf bus gefiltert) auf irgendein Problem hin?

Code Auswählen

2020-12-13 20:17:16.919 [main notice] ebusd 3.4.v3.4-96-g96d5623 started
2020-12-13 20:17:16.920 [main info] loading configuration files from /etc/ebusd
2020-12-13 20:17:16.972 [main error] error reading config files from /etc/ebusd: ERR: duplicate entry, last error: vaillant/15.370.csv:10: ERR: duplicate entry, duplicate ID
2020-12-13 20:17:16.975 [bus notice] bus started with own address 31/36
2020-12-13 20:17:17.015 [bus notice] signal acquired
2020-12-13 20:17:17.401 [bus notice] device status: reset
2020-12-13 20:17:17.401 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:17:17.452 [bus info] arbitration delay 286 - 286 micros
2020-12-13 20:17:17.463 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:17:25.402 [bus notice] new master 10, master count 2
2020-12-13 20:17:25.463 [bus notice] new master 03, master count 3
2020-12-13 20:17:25.464 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:17:25.516 [bus info] arbitration delay 219 - 286 micros
2020-12-13 20:17:25.527 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:17:35.485 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:17:35.536 [bus info] arbitration delay 219 - 288 micros
2020-12-13 20:17:35.547 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:17:45.544 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:17:45.607 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:17:55.605 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:17:55.656 [bus info] arbitration delay 219 - 343 micros
2020-12-13 20:17:55.667 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:18:05.669 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:18:05.731 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:18:15.725 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:18:15.787 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:18:25.785 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:18:25.847 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:18:33.756 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:18:34.240 [bus info] arbitration delay 219 - 366 micros
2020-12-13 20:18:34.251 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:18:39.161 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:18:39.644 [bus info] arbitration delay 219 - 529 micros
2020-12-13 20:18:39.655 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:18:45.005 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:18:45.086 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:18:55.963 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:18:56.025 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:19:06.028 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:19:06.090 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:19:16.083 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:19:16.146 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:19:26.143 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:19:26.206 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:19:36.208 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:19:36.270 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:19:46.269 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:19:46.331 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:19:56.333 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:19:56.396 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:20:06.358 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:20:06.420 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:20:16.413 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:20:16.475 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:20:26.472 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:20:26.534 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:20:36.536 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:20:37.092 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:20:46.628 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:20:46.691 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:20:56.647 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:20:56.711 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:21:06.710 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:21:06.773 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:21:16.771 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:21:16.834 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:21:26.839 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:21:26.901 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:21:36.903 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:21:36.965 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:21:46.959 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:21:47.021 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:21:57.019 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:21:57.082 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:22:07.080 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:22:07.143 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:22:17.144 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:22:17.206 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:22:27.208 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:22:27.271 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:22:37.237 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:22:37.299 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:22:47.289 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:22:47.351 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:22:57.349 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:22:57.412 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:23:07.414 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:23:07.476 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:23:17.471 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:23:17.533 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:23:27.531 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:23:27.593 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:23:37.591 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:23:37.654 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:23:47.659 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:23:47.722 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:23:57.720 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:23:57.783 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:24:04.438 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:24:04.933 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:24:10.041 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:24:10.330 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:24:17.831 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:24:17.894 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:24:27.899 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:24:27.961 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:24:37.963 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:24:38.025 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:24:48.027 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:24:48.091 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:24:58.048 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:24:58.111 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:25:08.111 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:25:08.173 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:25:18.160 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:25:18.222 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:25:28.224 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:25:28.286 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:25:37.322 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:25:37.944 [bus error] poll heb Yield failed: ERR: read timeout
2020-12-13 20:25:48.336 [bus info] poll cmd: 3115b509030d1f00
2020-12-13 20:25:48.399 [bus error] poll heb CollPumpHRuntime failed: ERR: read timeout
2020-12-13 20:25:58.400 [bus info] poll cmd: 3115b509030d1e00
2020-12-13 20:25:58.462 [bus error] poll heb Yield failed: ERR: read timeout

Jetzt habe ich aber noch auf dem Raspberry Pi 1b ein kleines Problem. Der will auf /dev/ttyAMA0 nichts rausrücken. Das Device ist vorhanden.

Code Auswählen

ebusd -f -d enh:/dev/ttyAMA0 --scanconfig --loglevel=debug
2020-12-13 19:36:44.129 [main notice] ebusd 3.4.v3.4-96-g96d5623 started with auto scan
2020-12-13 19:36:44.132 [main info] loading configuration files from http://ebusd.eu/config/
2020-12-13 19:36:44.172 [main info] reading templates /
2020-12-13 19:36:44.218 [main info] read templates in /
2020-12-13 19:36:44.220 [main info] reading file memory.csv
2020-12-13 19:36:44.263 [main info] successfully read file memory.csv
2020-12-13 19:36:44.265 [main info] reading file broadcast.csv
2020-12-13 19:36:44.311 [main info] successfully read file broadcast.csv
2020-12-13 19:36:44.313 [main info] read config files
2020-12-13 19:36:44.318 [main info] registering data handlers
2020-12-13 19:36:44.320 [main info] registered data handlers
2020-12-13 19:36:44.324 [bus notice] bus started with own address 31/36
2020-12-13 19:36:54.327 [main debug] performing regular tasks
2020-12-13 19:36:57.438 [network info] [00001] client connection opened 127.0.0.1
2020-12-13 19:36:57.442 [main debug] >>> i
2020-12-13 19:36:57.445 [main debug] <<< version: ebusd 3.4.v3.4-96-g96d5623
signal: no signal
reconnects: 0
masters: 1
messages: 11
conditio ...
2020-12-13 19:36:57.447 [network debug] [00001] wait for result
2020-12-13 19:36:57.458 [network info] [00001] connection closed
2020-12-13 19:36:58.442 [network debug] dead connection removed - 0
2020-12-13 19:37:02.447 [main debug] performing regular tasks

JimKnopf · 13 Dezember 2020, 23:59:44

Hi!

Ist es eigentlich grundsätzlich möglich zwei Temperatursensoren an dem Wemos anzuschließen?
Eine Anwendung wären z.B. Vorlauf- und Rücklauftemperatur vom Brauchwasser. Da habe ich jetzt zwei Funk-Temperatursensoren, würde aber gerne die Funklast im Haus reduzieren.
J7 ist ja für einen vorgesehen, könnte man noch direkt an den Wemos gehen?
Gruß,
Burkhard

JimKnopf · 14 Dezember 2020, 00:28:00

Hier noch einmal die letzten interessanten Meldungen:

Code Auswählen

2020-12-13 20:07:32.677 [bus error] device status: eBUS comm error: framing
2020-12-13 20:08:22.322 [bus error] poll solar SolarErfolg failed: ERR: SYN received
2020-12-13 20:25:09.060 [bus error] signal lost
2020-12-13 20:25:12.704 [bus error] send to 30: ERR: no signal, give up
2020-12-13 20:25:12.704 [bus error] send message part 0: ERR: no signal
2020-12-13 20:25:12.704 [mqtt error] write regler Mode: ERR: no signal
2020-12-13 20:32:08.815 [bus error] device status: eBUS comm error: framing
2020-12-13 20:32:08.815 [bus error] arbitration start error
2020-12-13 20:35:42.402 [bus error] poll regler HGStatus failed: ERR: read timeout
2020-12-13 20:38:59.121 [bus error] poll regler Raumtemperatur failed: ERR: read timeout
2020-12-13 20:40:54.217 [bus error] device status: eBUS comm error: framing
2020-12-13 20:40:54.218 [bus error] arbitration start error
2020-12-13 20:42:57.354 [bus error] poll regler Raumtemperatur failed: ERR: read timeout
2020-12-13 20:58:25.022 [bus error] device status: eBUS comm error: framing
2020-12-13 21:02:33.067 [bus error] signal lost
2020-12-13 21:08:50.498 [bus error] device status: eBUS comm error: framing
2020-12-13 21:14:34.029 [bus error] poll regler HGPWMPumpe failed: ERR: SYN received
2020-12-13 21:20:15.264 [bus error] send to 30: ERR: read timeout, retry
2020-12-13 21:21:17.071 [bus error] device status: eBUS comm error: framing
2020-12-13 21:21:17.071 [bus error] arbitration start error
2020-12-13 21:23:18.059 [bus error] signal lost
2020-12-13 21:34:44.130 [bus error] device status: eBUS comm error: framing
2020-12-13 21:34:44.131 [bus error] arbitration start error
2020-12-13 21:35:56.752 [bus error] device status: eBUS comm error: framing
2020-12-13 21:36:46.797 [bus error] device status: eBUS comm error: framing
2020-12-13 21:36:46.797 [bus error] arbitration start error
2020-12-13 21:43:15.116 [mqtt error] communication error: connection lost
2020-12-13 21:43:28.119 [mqtt error] publish: The client is not currently connected.
2020-12-13 21:43:46.161 [mqtt error] publish: The client is not currently connected.
2020-12-13 21:47:34.238 [bus error] poll regler Unbekannt1 failed: ERR: SYN received
2020-12-13 21:49:17.369 [bus error] device status: eBUS comm error: framing
2020-12-13 21:52:09.345 [bus error] poll solar ruecklauftemp failed: ERR: read timeout
2020-12-13 21:54:36.169 [bus error] poll regler Raumtemperatur failed: ERR: read timeout
2020-12-13 22:04:07.417 [bus error] device status: eBUS comm error: framing
2020-12-13 22:04:07.417 [bus error] poll solar ruecklauftemp failed: ERR: read timeout
2020-12-13 22:05:08.103 [bus error] device status: eBUS comm error: framing
2020-12-13 22:05:08.104 [bus error] arbitration start error
2020-12-13 22:06:47.198 [bus error] device status: eBUS comm error: framing
2020-12-13 22:06:47.199 [bus error] arbitration start error
2020-12-13 22:07:22.173 [bus error] poll regler HGPWMPumpe failed: ERR: read timeout
2020-12-13 22:08:03.232 [bus error] device status: eBUS comm error: framing
2020-12-13 22:11:48.414 [bus error] device status: eBUS comm error: framing
2020-12-13 22:19:18.756 [bus error] device status: eBUS comm error: framing
2020-12-13 22:20:33.832 [bus error] device status: eBUS comm error: framing
2020-12-13 22:20:33.832 [bus error] arbitration start error
2020-12-13 22:21:36.094 [bus error] poll regler Unbekannt1 failed: ERR: read timeout
2020-12-13 22:30:34.314 [bus error] device status: eBUS comm error: framing
2020-12-13 22:30:34.314 [bus error] arbitration start error
2020-12-13 22:34:22.151 [bus error] poll solar durchfl failed: ERR: read timeout
2020-12-13 22:35:09.485 [bus error] device status: eBUS comm error: framing
2020-12-13 22:47:07.054 [bus error] device status: eBUS comm error: framing
2020-12-13 22:47:07.054 [bus error] arbitration start error
2020-12-13 22:51:00.215 [bus error] device status: eBUS comm error: framing
2020-12-13 22:54:20.372 [bus error] device status: eBUS comm error: framing
2020-12-13 22:56:25.489 [bus error] device status: eBUS comm error: framing
2020-12-13 22:56:25.489 [bus error] arbitration start error
2020-12-13 22:56:48.227 [bus error] poll regler WarmwasserSoll failed: ERR: SYN received
2020-12-13 22:57:01.288 [bus error] poll regler HGStatus failed: ERR: read timeout
2020-12-13 22:57:40.680 [bus error] poll regler Unbekannt2 failed: ERR: wrong symbol received
2020-12-13 23:03:09.120 [bus error] device status: eBUS comm error: framing
2020-12-13 23:03:09.120 [bus error] arbitration start error
2020-12-13 23:16:51.412 [bus error] device status: eBUS comm error: framing
2020-12-13 23:36:12.356 [bus error] poll solar durchfl failed: ERR: read timeout
2020-12-13 23:37:22.112 [bus error] poll regler HGPWMPumpe failed: ERR: read timeout
2020-12-13 23:38:32.384 [bus error] poll regler Raumtemperatur failed: ERR: wrong symbol received
2020-12-13 23:38:32.388 [bus error] device status: eBUS comm error: framing
2020-12-13 23:39:47.466 [bus error] device status: eBUS comm error: framing
2020-12-13 23:43:29.824 [bus error] device status: eBUS comm error: framing
2020-12-13 23:43:34.425 [bus error] poll regler Unbekannt1 failed: ERR: SYN received
2020-12-13 23:43:44.376 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:43:50.254 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-13 23:44:19.858 [bus error] poll solar durchfl failed: ERR: read timeout
2020-12-13 23:44:52.513 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:44:54.930 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-13 23:45:51.780 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:45:55.825 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-13 23:46:58.562 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:47:00.201 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-13 23:48:05.555 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:48:10.341 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-13 23:58:08.311 [bus error] device status: eBUS comm error: framing
2020-12-13 23:58:12.155 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-13 23:58:15.595 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 00:06:43.866 [bus error] poll regler WarmwasserSoll failed: ERR: wrong symbol received
2020-12-14 00:08:18.417 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 00:08:20.405 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 00:09:06.911 [bus error] device status: eBUS comm error: framing
2020-12-14 00:09:06.911 [bus error] arbitration start error
2020-12-14 00:11:57.194 [bus error] device status: eBUS comm error: framing
2020-12-14 00:11:57.195 [bus error] arbitration start error
2020-12-14 00:18:23.679 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 00:18:25.371 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 00:21:29.386 [bus error] device status: eBUS comm error: framing
2020-12-14 00:23:57.282 [bus error] poll solar ruecklauftemp failed: ERR: wrong symbol received
2020-12-14 00:23:57.294 [bus error] device status: eBUS comm error: framing
2020-12-14 00:26:04.604 [bus error] device status: eBUS comm error: framing

Reinhart · 14 Dezember 2020, 09:52:13

Zitat von: JimKnopf am 13 Dezember 2020, 23:59:44
Hi!

Ist es eigentlich grundsätzlich möglich zwei Temperatursensoren an dem Wemos anzuschließen?
Eine Anwendung wären z.B. Vorlauf- und Rücklauftemperatur vom Brauchwasser. Da habe ich jetzt zwei Funk-Temperatursensoren, würde aber gerne die Funklast im Haus reduzieren.
J7 ist ja für einen vorgesehen, könnte man noch direkt an den Wemos gehen?
Gruß,
Burkhard

Ja das geht ohne Probleme, da ja jeder Sensor eine eigene 1-wire ID bekommt. Habe ich hier in einem Beispiel schon geschrieben, nimm dann aber die JSON Variante zur Auswertung da brauchst sonst in Fhem weiter nix zu tun und die Sensoren sollten auftauchen. Du kannst auch so wasserdichte Sensoren mit Kabel nehmen, die haben wir auch schon bei der Platine 2.x verbaut.

Code Auswählen

{"sensors": [{"sensor":0,"pin":6,"gpio":12,"address":"28ff1347b11501","value":23.6}]}
der JSON String sieht so aus.

Code Auswählen

{"sensors": [{"sensor":0,"pin":6,"gpio":12,"address":"28ff5c3db11501","value":22.9},{"sensor":1,"pin":6,"gpio":12,"address":"28ff1347b11501","value":27.1}]}

bei mehreren kommen halt mehrere mit unterschiedlicher Adresse.

Ich nehme die wasserdichten Sensoren auch zur Erfassung der Pooltemperatur!

LG

JimKnopf · 14 Dezember 2020, 11:34:12

Hi!

Die Wifi Variante läuft bei mir bis jetzt soweit stabiel, habe jetzt mal auf Ethernet gewechselt. Läuft jetzt seit 5 min ohne Probleme. Ausgaben durch "all error" poste ich dann später, wenn sich was gesammelt hat.
Meine Anlage habe ich mal soweit in die Signatur eingetragen. Aufgabenstellung bei mir: mitlesen von Telegrammen, pollen von gezielten Werten und schreiben des Modus der Heizungsanlage (Timer, nur Warmwasser) in Abhängigkeit der Öffnungsgrade der MAX! Heizkörperthermostate.
Bei nächster Gelegenheit werde ich mir mal ne Tüte Sensoren mitbestellen

.

EDIT: nach einer Stunde betrieb, hier die Ausgaben:

Code Auswählen

pi@raspberrypi:~ $ $ ebusd -f -enh:192.168.2.190:9999 -l /var/log/ebusd.log --latency=20000 --address=01 --configpath=/etc/ebusd/de --accesslevel=* --mqttport=1883 --mqttjson --mqtthost=192.168.2.101 --mqtttopic=ebusd/%circuit/%name --pollinterval=10 --enablehex --enabledefine --log="all error"
2020-12-14 11:28:02.564 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 11:28:08.511 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 11:29:09.258 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 11:29:12.871 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 11:30:15.778 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 11:30:18.502 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 11:31:46.975 [bus error] poll solar SolarErfolg failed: ERR: read timeout
2020-12-14 11:35:55.337 [bus error] poll solar ruecklauftemp failed: ERR: read timeout
2020-12-14 11:40:20.657 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 11:40:23.370 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 11:42:07.339 [bus error] device status: eBUS comm error: framing
2020-12-14 11:42:07.339 [bus error] arbitration start error
2020-12-14 11:50:25.020 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 11:50:28.042 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 11:58:09.192 [bus error] poll solar durchfl failed: ERR: read timeout
2020-12-14 12:00:31.609 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 12:00:33.887 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 12:01:46.523 [bus error] poll solar SolarErfolg failed: ERR: read timeout
2020-12-14 12:10:36.344 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 12:10:38.991 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 12:16:12.869 [bus error] device status: eBUS comm error: framing
2020-12-14 12:17:27.924 [bus error] device status: eBUS comm error: framing
2020-12-14 12:18:17.962 [bus error] device status: eBUS comm error: framing
2020-12-14 12:20:41.555 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 12:20:43.864 [mqtt error] decode scan.08 : ERR: argument value out of valid range
2020-12-14 12:21:56.347 [bus error] poll solar ruecklauftemp failed: ERR: read timeout
2020-12-14 12:22:03.135 [bus error] device status: eBUS comm error: framing
2020-12-14 12:25:23.293 [bus error] device status: eBUS comm error: framing
2020-12-14 12:30:47.269 [update error] unable to parse scan-read scan.08  from ff08070400 / 0a500106334202091b5130: ERR: argument value out of valid range
2020-12-14 12:30:49.269 [mqtt error] decode scan.08 : ERR: argument value out of valid range

Im Vergleich zu Wifi kein nennenswerter Unterschied, TOP!

.
Ihr habt nen super Job gemacht! Danke!!
Die RPI Version wollte ich nicht unbedingt testen, wäre aber zur Not möglich.
Ich bin jetzt bereit auf Wunsch Dinge gezielt zu testen, bzw. Situationen herbeizuführen wenn gewünscht.
Sagt einfach was ich machen soll. Falls keine besonderen Wünsche anstehen würde ich morgen wieder auf Wifi wechseln und lasse solange die Ethernetversion laufen lassen.
Gruß,
Burkhard

Gruß,
Burkhard

pc1246 · 14 Dezember 2020, 12:28:08

Moin zusammen
Wenn auch nur Mitleser, so doch zwei Anmerkungen von mir.
@JimKnopf: Kannst du das bitte in Codetags setzen was Du in #36 gepostet hast! Das ghet auch nachtraeglich!

Und zur WEMOS Problematik kann ich sagen, dass ich schon mal keinen neuen mehr bei mir zu Hause im WLAN finden konnte.
Letztendlich lag das wohl an der Fritte, die da irgendwie schlappgemacht hat. Also ganz zur Not bei solch einem Problem mal kurz das WLAN ausmachen, dann sollte man das loesen koennen.

Ich lese weiter gespannt mit!
Gruss Christoph

JimKnopf · 14 Dezember 2020, 12:45:32

Hi Christoph!

Mit den Codetags habe ich erledigt.
Das mit dem Wemos kann ich so bestätigen. Bei mir ist noch der vom Adapter 2.2 aktiv, taucht aber auch nicht immer in der Fritzbox auf.
Könnte evtl. daran liegen, dass er zwar im WLan hängt, aber sich nicht meldet. Den Adapter 2.2 spreche ich normalerweise nicht mehr an. Da war er auch nicht im WLan. Ich habe ebusd mit dessen IP zusätzlich aufgerufen. Hat sofort reagiert und tauchte dann auch im WLan wieder auf.
Vielleicht könnte man den Wemos, wenn er nicht von außen angesprochen wird, ein ping senden lassen, damit er nicht vergessen wird.

Gruß,
Burkhard

hErMeS · 14 Dezember 2020, 15:42:59

Hab eine Nachfrage zu den LED Stati

Die gelbe (Power) leuchtet ja dauerhaft wenn die Sekundärseite (Isolierter ebus Bereich) Strom durch die Primärseite (Eth, Pi, USB) hat.
Die blaue nur beim in Betrieb gehen? Denn die ist bei mir aus. Diese geht nur noch an während Daten auf den ebus gesendet werden. Hier allerdings auch teils mit unterschiedlicher Helligkeit während des Sendens. Beschreibung hierzu scheint nicht ganz zu passen.
Die grüne flackert fast durchgehend (Signalisierung des Empfanges von validen Datenpaketen oder einfach nur Daten?)
Die rote nur beim Senden.

edit:
Im Log taucht jetzt öfters teilweise auch mehrfach hintereinander ERR: read timeout during receive command ACK, switching to skip auf.

Code Auswählen


2020-12-14 18:23:40.515 [update info] received BC cmd: 10feb510020601
2020-12-14 18:23:45.744 [main debug] performing regular tasks
2020-12-14 18:23:47.881 [update info] received MS cmd: 1008b5110101 / 094c417006496d0100ff
2020-12-14 18:23:48.149 [update info] received MS cmd: 1008b5100900004cffffff000000 / 0101
2020-12-14 18:23:55.714 [bus debug] ERR: read timeout during receive command, switching to skip
2020-12-14 18:23:55.745 [main debug] performing regular tasks
2020-12-14 18:23:55.792 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:56.329 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:57.043 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:57.580 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:58.295 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:58.834 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:23:59.580 [update info] received MS cmd: 1008b5110101 / 094b414006496d0100ff
2020-12-14 18:23:59.847 [update info] received MS cmd: 1008b5100900004cffffff000000 / 0101
2020-12-14 18:24:05.745 [main debug] performing regular tasks
2020-12-14 18:24:07.950 [update info] received MS cmd: 1008b5110101 / 094b404006496d0100ff
2020-12-14 18:24:08.217 [update info] received MS cmd: 1008b5100900004cffffff000000 / 0101

Code Auswählen


2020-12-14 18:18:38.890 [update info] received MS cmd: 1008b512020064 / 00
2020-12-14 18:18:39.131 [update info] received MS cmd: 1008b5120204ff / 0101
2020-12-14 18:18:39.373 [update info] received MS cmd: 1008b513020508 / 00
2020-12-14 18:18:39.587 [update info] received BC cmd: 10feb510020601
2020-12-14 18:18:39.814 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:40.059 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:40.303 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:40.547 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:40.792 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:41.036 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:41.281 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:41.525 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:41.770 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:42.013 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:42.258 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:42.502 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:42.748 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:42.992 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:43.236 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:43.477 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:43.721 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:43.965 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:44.209 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:44.453 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:44.697 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:44.939 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:45.183 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:45.428 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:45.670 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:45.914 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:46.158 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:46.438 [update info] received MS cmd: 1008b5110101 / 094c4170064a6d0100ff
2020-12-14 18:18:46.706 [update info] received MS cmd: 1008b5100900004cffffff000000 / 0101
2020-12-14 18:18:46.935 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:47.180 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:47.424 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:47.631 [main debug] performing regular tasks
2020-12-14 18:18:47.667 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:47.912 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:48.156 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:48.400 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:48.645 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:48.890 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:49.134 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:49.379 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:49.624 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:49.868 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:50.112 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:50.357 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:50.599 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:50.844 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:51.089 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:51.333 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:51.578 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:51.822 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:52.066 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:52.311 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:52.555 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:52.800 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:53.044 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:53.288 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:53.532 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:53.777 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:54.019 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:54.264 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:54.508 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:54.751 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:54.958 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:55.489 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:55.732 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:55.976 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:56.054 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:56.725 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:57.306 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:57.978 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:58.733 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:18:59.521 [update info] received MS cmd: 1008b5110101 / 094c4170064a6d0100ff
2020-12-14 18:18:59.789 [update info] received MS cmd: 1008b5100900004cffffff000000 / 0101
2020-12-14 18:19:00.018 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:00.263 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:00.507 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:00.752 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:00.996 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:01.240 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:01.484 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:01.729 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:01.972 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 18:19:06.326 [update info] received MS cmd: 1008b5110101 / 094c4170064a6d0100ff

Reinhart · 14 Dezember 2020, 19:58:15

die blaue Led zeigt die Kommunikation mit dem Pic an, kann aber je nach Betriebsart unterschiedlich sein. Leider hats du nicht geschrieben, wie du den Adapter betreibst, USB, Rpi, Wlan oder Ethernet.

Bist du sicher das du die Jumper deiner Betriebsart entsprechend richtig gesetzt hast?

LG

hErMeS · 14 Dezember 2020, 20:35:25

Zitat von: Reinhart am 14 Dezember 2020, 19:58:15
Bist du sicher das du die Jumper deiner Betriebsart entsprechend richtig gesetzt hast?

Betrieb aktuell per USB. Habe von den LED's auch ein Video gedreht falls man sich das Anschauen möchte.

Jeglicher scan command schlägt bei mir fehl. Liegt dies am anderen ebus-Device?
Es ist bisher immer ein ziemlich großer Zeitversatz (nicht nur Minuten) bis die devices hier komplett benannt werden.

Code Auswählen


scan.08  = no data stored
scan.15  = Vaillant;70000;0613;6903

Code Auswählen


2020-12-14 19:24:38.645 [network info] [00002] connection closed
2020-12-14 19:24:39.329 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:24:39.329 [update notice] received unknown MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:24:39.521 [network debug] dead connection removed - 0
2020-12-14 19:24:40.644 [main debug] performing regular tasks
2020-12-14 19:24:40.644 [bus info] scan 15 cmd: 3115070400
2020-12-14 19:24:48.124 [update info] received MS cmd: 1008b5110101 / 094d420006416b0100ff
2020-12-14 19:24:48.124 [update notice] received unknown MS cmd: 1008b5110101 / 094d420006416b0100ff
2020-12-14 19:24:48.124 [bus debug] start request 31
2020-12-14 19:24:48.124 [bus debug] arbitration start with 31
2020-12-14 19:24:48.177 [bus debug] arbitration won
2020-12-14 19:24:48.177 [bus debug] arbitration delay 275 micros
2020-12-14 19:24:48.177 [bus info] arbitration delay 275 - 375 micros
2020-12-14 19:24:48.177 [bus debug] switching from ready to send command
2020-12-14 19:24:48.188 [bus debug] notify request: ERR: read timeout
2020-12-14 19:24:48.188 [main error] scan config 15: ERR: read timeout
2020-12-14 19:24:48.188 [bus debug] ERR: read timeout during send command, switching to skip
2020-12-14 19:24:48.913 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:24:48.913 [update notice] received unknown MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:24:50.189 [main debug] performing regular tasks
2020-12-14 19:24:58.143 [update info] received MS cmd: 1008b5110101 / 094d420006416b0100ff

edit:
hier hat ebusd nach dem reload die Gerätedaten erhalten können (die vaillant csv files in den config ordner kopiert), allerdings ebenfalls erstmal ein timeout
Log ist um die update notice received unkown cmd gekürzt

Code Auswählen

2020-12-14 19:38:17.075 [network info] [00005] client connection opened 127.0.0.1
2020-12-14 19:38:17.075 [network debug] [00005] wait for result
2020-12-14 19:38:17.075 [main debug] >>> reload
2020-12-14 19:38:17.075 [main info] loading configuration files from /etc/ebusd
2020-12-14 19:38:17.075 [main info] reading templates /
2020-12-14 19:38:17.076 [main info] read templates in /
2020-12-14 19:38:17.076 [main info] reading file broadcast.csv
2020-12-14 19:38:17.077 [main info] successfully read file broadcast.csv
2020-12-14 19:38:17.077 [main info] reading file memory.csv
2020-12-14 19:38:17.078 [main info] successfully read file memory.csv
2020-12-14 19:38:17.078 [main info] read config files
2020-12-14 19:38:17.078 [main debug] <<< done
2020-12-14 19:38:17.079 [network info] [00005] connection closed
2020-12-14 19:38:17.486 [bus notice] new master 03, master count 2
2020-12-14 19:38:17.512 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:38:18.076 [network debug] dead connection removed - 0
2020-12-14 19:38:22.078 [main debug] performing regular tasks
2020-12-14 19:38:22.078 [bus info] scan 08 cmd: 3108070400
2020-12-14 19:38:22.572 [bus notice] new master 10, master count 3
2020-12-14 19:38:22.631 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:38:22.631 [bus debug] start request 31
2020-12-14 19:38:22.631 [bus debug] arbitration start with 31
2020-12-14 19:38:22.683 [bus debug] arbitration won
2020-12-14 19:38:22.683 [bus debug] arbitration delay 377 micros
2020-12-14 19:38:22.683 [bus info] arbitration delay 275 - 377 micros
2020-12-14 19:38:22.683 [bus debug] switching from ready to send command
2020-12-14 19:38:22.694 [bus debug] notify request: ERR: read timeout
2020-12-14 19:38:22.694 [bus debug] ERR: read timeout during send command, switching to skip
2020-12-14 19:38:22.694 [main error] scan config 08: ERR: read timeout
2020-12-14 19:38:23.303 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:38:23.874 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:38:24.695 [main debug] performing regular tasks
2020-12-14 19:38:24.695 [bus info] scan 15 cmd: 3115070400
2020-12-14 19:38:32.714 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:38:32.715 [bus debug] start request 31
2020-12-14 19:38:32.715 [bus debug] arbitration start with 31
2020-12-14 19:38:32.767 [bus debug] arbitration won
2020-12-14 19:38:32.767 [bus debug] arbitration delay 237 micros
2020-12-14 19:38:32.767 [bus info] arbitration delay 237 - 377 micros
2020-12-14 19:38:32.767 [bus debug] switching from ready to send command
2020-12-14 19:38:32.778 [bus debug] notify request: ERR: read timeout
2020-12-14 19:38:32.778 [bus debug] ERR: read timeout during send command, switching to skip
2020-12-14 19:38:32.778 [main error] scan config 15: ERR: read timeout
2020-12-14 19:38:33.504 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:38:33.757 [update info] received MS cmd: 1008b5110102 / 06033c9646826e
2020-12-14 19:38:34.779 [main debug] performing regular tasks
2020-12-14 19:38:42.770 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:38:42.770 [update notice] received unknown MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:38:43.038 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:38:44.779 [main debug] performing regular tasks
2020-12-14 19:38:52.827 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:38:53.094 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:38:54.779 [main debug] performing regular tasks
2020-12-14 19:39:02.891 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:39:03.159 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:39:03.434 [update info] received MS cmd: 1008b5040100 / 0a03053920141201200006
2020-12-14 19:39:03.690 [update info] received MS cmd: 1008b5110102 / 06033c9646826e
2020-12-14 19:39:03.928 [update info] received BC cmd: 10feb516080003392014120120
2020-12-14 19:39:04.192 [update info] received MS cmd: 1008b5110100 / 086b021426040f0081
2020-12-14 19:39:04.410 [update info] received BC cmd: 10feb51603010006
2020-12-14 19:39:04.653 [update info] received MS cmd: 1008b5100305ff01 / 0101
2020-12-14 19:39:04.780 [main debug] performing regular tasks
2020-12-14 19:39:04.889 [update info] received MS cmd: 1008b512020064 / 00
2020-12-14 19:39:05.131 [update info] received MS cmd: 1008b5120204ff / 0101
2020-12-14 19:39:05.372 [update info] received MS cmd: 1008b513020508 / 00
2020-12-14 19:39:05.584 [update info] received BC cmd: 10feb510020601
2020-12-14 19:39:07.435 [bus debug] ERR: read timeout during receive command, switching to skip
2020-12-14 19:39:07.514 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:08.052 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:08.764 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:09.302 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:10.016 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:10.555 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2020-12-14 19:39:11.337 [update info] received MS cmd: 0315070400 / 0ab5373030303006136903
2020-12-14 19:39:11.337 [bus notice] scan 15: ;Vaillant;70000;0613;6903
2020-12-14 19:39:11.337 [update notice] store 15 ident: done
2020-12-14 19:39:12.948 [update info] received MS cmd: 1008b5110101 / 094d420006406b0100ff
2020-12-14 19:39:13.215 [update info] received MS cmd: 1008b5100900004dffffff000000 / 0101
2020-12-14 19:39:14.780 [main debug] performing regular tasks

An was liegt es dass das Gerät beim scannen nicht erkennbar wird?

Reinhart · 14 Dezember 2020, 20:46:10

wie hast du denn die Adresse des ersten Adapters eingestellt, läuft der auch auf Adresse 31?

Poste doch bitte einmal die config und wenn möglich kannst du ein Foto der Platine machen?

LG