eBus Schaltung in Betrieb nehmen

Begonnen von Reinhart, 23 Dezember 2015, 15:19:45

Vorheriges Thema - Nächstes Thema

john30

Zitat von: darkside40 am 25 Oktober 2021, 13:17:57
1. Macht es heute überhaupt noch Sinn mit der 1.6er Platine anzufangen? Ich habe die Idee das ich an die serielle Schnittstelle der Adapterplatine einen Wemos D1 (hab ich noch rumliegen) mit der dementsprechenden Firmware hänge. Oder macht das gar keinen Sinn und ich sollte mich direkt in die Warteliste für ne v3 Adapterplatine hängen?
2. Im Reichelt Warenkorb ist der Optokoppler in zwei Varianten enthalten mit unterschiedlichem Übertragungsverhältnis. Warum ist das so bzw. ist es egal welchen ich nehme?
1.6 würde ich definitiv nicht mehr nehmen, da am Bus zu stark Strom gezogen wird und das Einstellen des Potis schon sehr umständlich ist
author of ebusd

darkside40

Okay danke für die Info.
Dann werde ich mal schauen ob ich mir den v3 Adapter zulege, aber so wie ich gelesen habe wird es mit der nächsten Lieferung wohl nichts vor 2022, oder?
Ich meine es ist nicht so dringend für mich. Derzeit hängt an der Therme ein Tado und das macht seine Sache ganz gut aber irgendwann möchte ich im Smarthome halt komplett ohne Cloud auskommen.

john30

Zitat von: darkside40 am 26 Oktober 2021, 10:25:52
Okay danke für die Info.
Dann werde ich mal schauen ob ich mir den v3 Adapter zulege, aber so wie ich gelesen habe wird es mit der nächsten Lieferung wohl nichts vor 2022, oder?
Ich meine es ist nicht so dringend für mich. Derzeit hängt an der Therme ein Tado und das macht seine Sache ganz gut aber irgendwann möchte ich im Smarthome halt komplett ohne Cloud auskommen.
das kommt bisschen drauf an, ob die in der Vergangenheit reservierten dann auch abgerufen werden (es melden sich einige einfach nicht mehr).
author of ebusd

Shaggy_12

Zitat von: john30 am 26 Oktober 2021, 21:51:51
das kommt bisschen drauf an, ob die in der Vergangenheit reservierten dann auch abgerufen werden (es melden sich einige einfach nicht mehr).
Also bei mir ging es sehr schnell, ich kämpfe zwar noch mit den csv-Dateien, aber ich hab die 119 Seiten hier auch noch nicht durch :)

Wenn man ein ernsthaftes Interesse hat und das dann aufrecht behält wirds sicher was :)

mirror

#1774
Nach langem klaglosem Betrieb vom ebus v2 Adapter auf eine Raspi 3+ mit buster (kernel 4.19) habe ich mir durch update und upgrade das System zerschossen. Nichts geht mehr - weder ein sudo make install des ttyebus Treibers (Speicherfehler bzw. einfrieren des modprobe commands) noch modprobe -r ttyebus (ttyebus in use trotz service stop).
Ich neige zur totalen Neuinstallation des OS. Doch welches Raspbian zieht man sich auf um dann den ttyebus Treiber laut github Anleitung zu installieren? Buster oder schon das Bullseye? Möglichst ohne patch oder downgrade Orgie der Kernel sourcen.

EDIT:
Ich habe noch eine Kopie des images (buster) gefunden, wenn auch nicht ganz aktuell. Die Installation von ttyebus ging nur nach https://github.com/eBUS/ttyebus/issues/12 und mit dem branch kernel_5_10_hack von https://github.com/unamehere/ttyebus. Ist nicht ganz sauber, aber geht erstmal.

ebusd wurde nach John's wiki aus den github sourcen installiert und fhem neu aufgesetzt. Die Verbindung zw. ebusd und fhem scheint OK, nach den Daten und Grafiken zu urteilen.
Allerdings steht im fhem logfile:
2021.11.28 14:50:04 3: Opening EBUS device 192.168.178.11:8888
2021.11.28 14:50:04 1: EBUS: Can't connect to 192.168.178.11:8888: Network is unreachable


Verstehe ich nicht ganz - ist 8888 nicht die default port Nummer?
pi@raspberrypi:~ $ sudo lsof -i | grep -e LISTEN
cupsd      446      root    6u  IPv6  14161      0t0  TCP localhost:ipp (LISTEN)
cupsd      446      root    7u  IPv4  14162      0t0  TCP localhost:ipp (LISTEN)
mosquitto  494 mosquitto    5u  IPv4  15969      0t0  TCP *:1883 (LISTEN)
mosquitto  494 mosquitto    6u  IPv6  15970      0t0  TCP *:1883 (LISTEN)
sshd       518      root    3u  IPv4  17207      0t0  TCP *:ssh (LISTEN)
sshd       518      root    4u  IPv6  17217      0t0  TCP *:ssh (LISTEN)
dnsmasq    533   dnsmasq    5u  IPv4  16101      0t0  TCP *:domain (LISTEN)
dnsmasq    533   dnsmasq    7u  IPv6  16103      0t0  TCP *:domain (LISTEN)
perl       592      fhem    4u  IPv4  20832      0t0  TCP *:8383 (LISTEN)
perl       592      fhem    5u  IPv4  18546      0t0  TCP *:7072 (LISTEN)
perl       592      fhem    6u  IPv4  17735      0t0  TCP *:8083 (LISTEN)
perl       592      fhem    7u  IPv4  17736      0t0  TCP *:8084 (LISTEN)
perl       592      fhem    8u  IPv4  17737      0t0  TCP *:8085 (LISTEN)
ebusd      970      root    5u  IPv4  21507      0t0  TCP *:8888 (LISTEN)

Kann mir bitte jemand ein Tip zu der fhem log Meldung geben.
Danke


Slanesh

Hallo zusammen,

ich bin gestern endlich mal dazu gekommen meinen eBus Adapter V1.6 zusammenzubauen. Jetzt bin ich im Wiki beim Abgleichen des Poti angekommen. Dazu habe ich eine Verständnisfrage: Muss hierzu der eBus Apapter bereits an den eBus angeschlossen werden, damit die "<aa" angezeigt werden, oder kann ich das "trocken" machen?

Gruß Slanesh
Intel NUC, 2x HM-LAN, 1x CUL-USB, 2x CCU2, 1x Harmony-Hub, 20x HM-LC-Sw1PBU-FM, 5x HM-LC-SW1-PL2, JeeLink mit 15x TX-29-DTH, 7x HM-SEC-SC-2, 3x HM-LC-SW1-BA-PCB, 8x HM-SEC-SD, 3x HM-SEC-MDIR-2, 2x HM-ES-PMSw1-Pl, 8x HmIP-BWTH, 3xHM-CC-RT-DN, 16xHM-LC-Bl1PBU-FM, 8x HM-SEC-SCo, 1xHM-ES-PMSw1-SM

Reinhart

ja, sonst kommen ja keine Signale!
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

raimundl

Nur zur Info:

Habe gestern mein System upgedatet (RPi3 mit Stretch und ebus Platine V3 über Ethernet)

Danach kein Signal mehr von der Platine erhalten. Nach doch einiger Suchzeit habe ich folgendes herausgefunden:
In der /etc/default/ebusd war meine Konfigurationszeile verschwunden - vielleicht durch überspielen beim Gesamtupdate???
Eine Wiederherstellung der Konfiguration brachte das ganze System wieder problemlos zum Laufen.

Ebus inkl. der jeweiligen Platinen läuft seit Jahren problemlos und einwandfrei (Dank an die Entwickler)!

LG

Homematic: Licht, Heizung, Alarm, Alexa ... auf einen RaspberryPi3+mit OS "Stretch" und RPI-RF-MOD mit piVCCU3 (HMCCU), ca. 40 HM Komponenten, alexa, MobileAlerts, Hue Ledstripes....

Slanesh

#1778
Hallo zusammen,

ich habe auf meinem Raspberry (Raspberry OS Bullseye) den ebusd Version 21.3.v21.3-130-g13221e2 mit dem ebus Adapter V1.6 nun am laufen und über MQTT an FHEM angebunden. Allerdings scheitere ich meiner Meinung nach daran die richtigen CSV-Dateien zu integrieren. Ich hatte verstanden, dass die aktuelle Version der ebusd sich die CSVs automatisch über cfg.ebusd.eu herunterlädt. Das Verzeichnis /etc/ebusd/ ist bei mir allerdings leer. Nach meinem Verständnis sollten hier doch die heruntergeladenen CSVs landen, oder?

Konfiguration meiner /etc/default/ebusd
EBUSD_OPTS="--scanconfig --accesslevel=* --mqttport=1883 --mqttjson --mqtthost=192.168.1.28 --mqtttopic=ebusd/%circuit/%name --configpath=http://cfg.ebusd.eu/"


ebusctl info
version: ebusd 21.3.v21.3-130-g13221e2
update check: revision v21.3 available
device: /dev/ttyUSB0
access: *
signal: acquired
symbol rate: 23
max symbol rate: 104
min arbitration micros: 550
max arbitration micros: 4228
min symbol latency: 5
max symbol latency: 7
reconnects: 0
masters: 3
messages: 68
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU01;SW=0304;HW=8802", loaded "vaillant/08.hmu.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0111;HW=0103"


Auszug aus dem /var/log/ebusd.log
2021-12-29 02:20:04.530 [main notice] ebusd 21.3.v21.3-130-g13221e2 started with auto scan on device /dev/ttyUSB0
2021-12-29 02:20:04.703 [bus notice] bus started with own address 31/36
2021-12-29 02:20:04.708 [bus notice] signal acquired
2021-12-29 02:20:04.850 [mqtt notice] connection established
2021-12-29 02:20:04.997 [bus notice] new master 71, master count 2
2021-12-29 02:20:05.043 [bus notice] new master 03, master count 3
2021-12-29 02:20:05.043 [update notice] received unknown MS cmd: 7108b5110107 / 050000000101
2021-12-29 02:20:13.093 [update notice] received unknown MS cmd: 7108b5110107 / 050000000101
2021-12-29 02:20:14.149 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:20:14.870 [bus notice] scan 08: ;Vaillant;HMU01;0304;8802
2021-12-29 02:20:14.870 [update notice] store 08 ident: done
2021-12-29 02:20:14.874 [update notice] sent scan-read scan.08  QQ=31: Vaillant;HMU01;0304;8802
2021-12-29 02:20:14.874 [bus notice] scan 08: ;Vaillant;HMU01;0304;8802
2021-12-29 02:20:15.047 [main notice] read common config file vaillant/broadcast.csv
2021-12-29 02:20:15.075 [main notice] read common config file vaillant/scan.csv
2021-12-29 02:20:15.103 [main notice] read common config file vaillant/general.csv
2021-12-29 02:20:15.190 [main notice] read scan config file vaillant/08.hmu.csv for ID "hmu01", SW0304, HW8802
2021-12-29 02:20:15.254 [main notice] found messages: 65 (0 conditional on 0 conditions, 0 poll, 10 update)
2021-12-29 02:20:15.526 [update notice] sent unknown MS cmd: 3108b5090124 / 09003231313731383030
2021-12-29 02:20:15.694 [update notice] sent scan-read scan.08 id QQ=31:
2021-12-29 02:20:15.953 [update notice] sent scan-read scan.08 id QQ=31:
2021-12-29 02:20:16.117 [update notice] sent scan-read scan.08 id QQ=31: 21;17;18;0010019759;1610;005992;N3
2021-12-29 02:20:16.117 [bus notice] scan 08: ;21;17;18;0010019759;1610;005992;N3
2021-12-29 02:20:18.399 [bus notice] scan 76: ;Vaillant;VWZIO;0111;0103
2021-12-29 02:20:18.400 [update notice] store 76 ident: done
2021-12-29 02:20:18.400 [update notice] sent scan-read scan.76  QQ=31: Vaillant;VWZIO;0111;0103
2021-12-29 02:20:18.401 [bus notice] scan 76: ;Vaillant;VWZIO;0111;0103
2021-12-29 02:20:18.584 [update notice] sent unknown MS cmd: 3176b5090124 / 09003231313731373030
2021-12-29 02:20:18.812 [update notice] sent scan-read scan.76 id QQ=31:
2021-12-29 02:20:18.997 [update notice] sent scan-read scan.76 id QQ=31:
2021-12-29 02:20:19.005 [bus notice] max. symbols per second: 104
2021-12-29 02:20:19.183 [update notice] sent scan-read scan.76 id QQ=31: 21;17;17;0010019373;3100;005380;N9
2021-12-29 02:20:19.184 [bus notice] scan 76: ;21;17;17;0010019373;3100;005380;N9
2021-12-29 02:20:19.216 [main error] unable to load scan config 76: no file from vaillant with prefix 76 found
2021-12-29 02:20:19.216 [main error] scan config 76: ERR: element not found
2021-12-29 02:20:21.157 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:20:25.071 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:20:29.427 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:20:44.335 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:20:45.317 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:20:53.369 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:20:54.428 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:21:01.399 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:21:04.473 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:21:09.474 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:21:14.566 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:21:25.680 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:21:33.660 [update notice] received read hmu State QQ=71: 0;0;on;ready
2021-12-29 02:21:34.718 [update notice] received unknown MS cmd: 7108b507030bffff / 0101
2021-12-29 02:21:41.691 [update notice] received read hmu State QQ=71: 0;0;on;ready


List meines MQTT2_ebusd_21.3_5879 Devices auf das ich das Template eBus_deamon_splitter angewendet habe
Internals:
   CFGFN     
   CID        ebusd
   DEF        ebusd
   DEVICETOPIC MQTT2_ebusd_21.3_5879
   FUUID      61cb9494-f33f-799c-48c6-df45db396336e811
   IODev      myBroker
   LASTInputDev myBroker
   MSGCNT     1373
   NAME       MQTT2_ebusd_21.3_5879
   NR         13405
   STATE      Status:
1:true
Signal:
2:true
<br>Uptime: 0 000 00:21
   TYPE       MQTT2_DEVICE
   myBroker_MSGCNT 1373
   myBroker_TIME 2021-12-29 02:41:40
   JSONMAP:
     Status01_0_value _Vorlauf
     Status01_1_value _Ruecklauf
     Status01_2_value _Aussentemp
     Status01_3_value _Warmwasser
     Status01_4_value _WWSpeicher
     Status01_5_value _Pumpenstatus
     Status02_0_value _HWCMode
     Status02_1_value _Maximaltemperatur
     Status02_2_value _ReglerMaxTEMP
     Status02_3_value _ReglerCurrentTemp
   OLDREADINGS:
   READINGS:
     2021-12-29 01:33:15   0_name          energy
     2021-12-29 01:33:15   0_value         0
     2021-12-29 01:33:15   1_name          energy
     2021-12-29 01:33:15   1_value         0
     2021-12-29 01:33:15   2_name          onoff
     2021-12-29 01:33:15   2_value         on
     2021-12-29 01:33:15   3_name          state
     2021-12-29 01:33:15   3_value         ready
     2021-12-29 02:20:20   associatedWith  MQTT2_ebusd_21.3_5879
     2021-12-29 01:09:01   attrTemplateVersion 20200824
     2021-12-29 02:41:40   formatedUptime  0 000 00:21
     2021-12-29 02:20:04   running         true
     2021-12-29 02:20:21   scan            "finished"
     2021-12-29 02:20:20   signal          true
     2021-12-29 01:09:01   state           getKnown
     2021-12-29 02:22:21   updatecheck     "revision v21.3 available"
     2021-12-29 02:41:40   uptime          1296
     2021-12-29 02:20:04   version         "ebusd 21.3.v21.3-130-g13221e2"
Attributes:
   IODev      myBroker
   autocreate 1
   bridgeRegexp (ebus..*?)/(bai|\d+|cc|e7f|ehp|f\d\d|hc|he.|hmu|hwc|mc|mc.\d|omu|omu.\d|pms|rcc|rcc.\d|sc|sdr_p|solar|ui|uih|v\d\d|v81.\d|vd\d|vl\d|vr_\d\d|zeo)/.*:.* "$1_$2"
(ebus..*?)/(global|broadcast|general|scan([^/]*))/.*:.* "$1"
   comment    NOTE: additional templates and code have been downloaded from svn (contrib).
   devStateStyle style="text-align:right"
   jsonMap    Status01_0_value:_Vorlauf Status01_1_value:_Ruecklauf Status01_2_value:_Aussentemp Status01_3_value:_Warmwasser Status01_4_value:_WWSpeicher Status01_5_value:_Pumpenstatus Status02_0_value:_HWCMode Status02_1_value:_Maximaltemperatur Status02_2_value:_ReglerMaxTEMP Status02_3_value:_ReglerCurrentTemp
   model      eBus_daemon_splitter
   readingList ebusd/scan\x5c\x2e08/:.* { json2nameValue($EVENT) }
ebusd/scan\x5c\x2e08/id:.* { json2nameValue($EVENT) }
ebusd/scan\x5c\x2e76/:.* { json2nameValue($EVENT) }
ebusd/scan\x5c\x2e76/id:.* { json2nameValue($EVENT) }
ebusd/global/version:.* version
ebusd/global/running:.* running
ebusd/global/scan:.* scan
ebusd/global/uptime:.* uptime
ebusd/global/signal:.* signal
ebusd/global/updatecheck:.* updatecheck
   room       MQTT2_DEVICE
   setList    getKnown:noArg ebusd/list onlyknown
  getAll:noArg ebusd/list
   stateFormat Status:
1:running
Signal:
2:signal
<br>Uptime: formatedUptime
   userReadings formatedUptime:uptime.* {my $m = ReadingsVal($name,"uptime",0)/60;; return sprintf "0 000 00:%02d", $m if $m < 60;; my $h = $m / 60;; $m %= 60;; return sprintf "0 000 %02d:%02d", $h, $m if $h < 24;; my $d = $h / 24;; $h %= 24;; return sprintf "0 %03d %02d:%02d", $d, $h, $m if $d <365;; my $y = $d / 365;; $d %= 365;; return sprintf "%d %03d %02d:%02d", $y, $d, $h, $m}


List des Devices MQTT2_ebusd_hmu, wobei mir unklar ist um was es sich hier handelt
Internals:
   CFGFN     
   CID        ebusd_hmu
   DEF        ebusd_hmu
   DEVICETOPIC MQTT2_ebusd_hmu
   FUUID      61cbad01-f33f-799c-3e6e-467ebdacc18747aa
   IODev      myBroker
   LASTInputDev myBroker
   MSGCNT     234
   NAME       MQTT2_ebusd_hmu
   NR         14356
   STATE      ???
   TYPE       MQTT2_DEVICE
   myBroker_MSGCNT 234
   myBroker_TIME 2021-12-29 02:44:42
   READINGS:
     2021-12-29 02:44:42   0_name          energy
     2021-12-29 02:44:42   0_value         0
     2021-12-29 02:44:42   1_name          energy
     2021-12-29 02:44:42   1_value         0
     2021-12-29 02:44:42   2_name          onoff
     2021-12-29 02:44:42   2_value         on
     2021-12-29 02:44:42   3_name          state
     2021-12-29 02:44:42   3_value         ready
     2021-12-29 01:34:09   associatedWith  MQTT2_ebusd_21.3_5879
Attributes:
   IODev      myBroker
   readingList ebusd/hmu/State:.* { json2nameValue($EVENT) }
   room       MQTT2_DEVICE


Ich denke der Fehler aus dem Log "[main error] unable to load scan config 76: no file from vaillant with prefix 76 found" ist der Knackpunkt. Gibt es zu diesem Vaillant Device einfach kein Config-File?

Für einen Hinweis wäre ich sehr dankbar. Habe mir jetzt die halbe Nacht um die Ohren geschlagen und komme einfach nicht weiter.

Viele Grüße
Slanesh
Intel NUC, 2x HM-LAN, 1x CUL-USB, 2x CCU2, 1x Harmony-Hub, 20x HM-LC-Sw1PBU-FM, 5x HM-LC-SW1-PL2, JeeLink mit 15x TX-29-DTH, 7x HM-SEC-SC-2, 3x HM-LC-SW1-BA-PCB, 8x HM-SEC-SD, 3x HM-SEC-MDIR-2, 2x HM-ES-PMSw1-Pl, 8x HmIP-BWTH, 3xHM-CC-RT-DN, 16xHM-LC-Bl1PBU-FM, 8x HM-SEC-SCo, 1xHM-ES-PMSw1-SM

Nighthawk

Hallo zusammen,

ich verzweifle gerade an der Inbetriebnahme des eBus Schaltung, irgendwie will ebusd nicht mit dem Adapter.

Die Jumper sind wie hier beschrieben gesetzt: https://adapter.ebusd.eu/img/smd-usb.jpg


ebusd habe ich nach der Anleitung https://github.com/john30/ebusd/wiki/1.-Build-and-install compiliert und installiert.

Egal ob ich die Configuration in /etc/default/ebusd mache

EBUSD_OPTS="--scanconfig --accesslevel=* --latency=20 -d enh:/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0 --address=ff"


Log:
2022-01-04 09:20:18.528 [main notice] ebusd 21.3.v21.3-130-g13221e2 started with auto scan on enhanced device /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020>
2022-01-04 09:20:19.242 [bus notice] device status: resetting
2022-01-04 09:20:19.248 [bus notice] bus started with own address ff/04
2022-01-04 09:20:19.722 [bus notice] device status: reset
2022-01-04 09:20:22.351 [bus notice] device invalid
2022-01-04 09:20:27.357 [bus notice] device status: resetting
2022-01-04 09:20:27.358 [bus notice] re-opened /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0
2022-01-04 09:20:27.363 [bus notice] device invalid
2022-01-04 09:20:32.369 [bus notice] device status: resetting
2022-01-04 09:20:32.377 [bus notice] re-opened /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0
2022-01-04 09:20:32.641 [bus notice] device status: reset
2022-01-04 09:20:42.556 [bus notice] device invalid


oder direkt im Terminat starte:
pi@Pi:~ $ ls -l /dev/serial/by-id
insgesamt 0
lrwxrwxrwx 1 root root 13  3. Jan 09:29 usb-FTDI_FT232R_USB_UART_AL02VI9U-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13  4. Jan 07:36 usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13  3. Jan 09:29 usb-Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_010672B0-if00-port0 -> ../../ttyUSB2

pi@Pi:~ $ sudo ebusd --scanconfig -d /dev/ttyUSB0 -f

2022-01-04 09:16:13.248 [main notice] ebusd 21.3.v21.3-130-g13221e2 started with auto scan on device /dev/ttyUSB0
2022-01-04 09:16:13.634 [bus notice] bus started with own address 31/36
2022-01-04 09:16:13.903 [bus notice] device invalid
2022-01-04 09:16:18.908 [bus notice] re-opened /dev/ttyUSB0
2022-01-04 09:16:19.186 [bus notice] device invalid
^C2022-01-04 09:16:24.107 [main notice] SIGINT received
2022-01-04 09:16:24.192 [bus notice] re-opened /dev/ttyUSB0
2022-01-04 09:16:28.903 [main notice] ebusd stopped

pi@Pi:~ $ sudo ebusd --scanconfig -d /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0 -f

2022-01-04 09:16:37.208 [main notice] ebusd 21.3.v21.3-130-g13221e2 started with auto scan on device /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0
2022-01-04 09:16:37.593 [bus notice] bus started with own address 31/36
2022-01-04 09:16:41.785 [bus notice] device invalid
2022-01-04 09:16:46.793 [bus notice] re-opened /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0
2022-01-04 09:16:53.336 [bus notice] device invalid
^C2022-01-04 09:16:54.123 [main notice] SIGINT received
2022-01-04 09:16:57.698 [main notice] ebusd stopped


gibt es die Fehlermeldung "device invalid".

Mache ich hier etwas falsch, oder stimmt etwas mit dem Adapter nicht?

Reinhart

Zitat von: Slanesh am 29 Dezember 2021, 02:52:04
ich habe auf meinem Raspberry (Raspberry OS Bullseye) den ebusd Version 21.3.v21.3-130-g13221e2 mit dem ebus Adapter V1.6 nun am laufen und über MQTT an FHEM angebunden. Allerdings scheitere ich meiner Meinung nach daran die richtigen CSV-Dateien zu integrieren. Ich hatte verstanden, dass die aktuelle Version der ebusd sich die CSVs automatisch über cfg.ebusd.eu herunterlädt. Das Verzeichnis /etc/ebusd/ ist bei mir allerdings leer. Nach meinem Verständnis sollten hier doch die heruntergeladenen CSVs landen, oder?

Hallo,
bevor du dich jetzt an die Auswertung von MQTT stürzt, solltest du erst versuchen deinen Device VRZIO irgendwie ausfindig machen was das genau ist und selbst eine csv erstellen bzw. aus einem ähnlichen Gerät kopieren. D.h. du musst die csv händisch laden und versuchen das zu interpretieren. So wie es aussieht, funktioniert ja dein Adapter 1.6 problemlos. Es gab schon mal einen Post der auch so eine VWZIO hatte (Wärmepumpe?), der kam aber meines Wissens auch nicht so recht weiter.


Die jetzt geladene 08.hmu.csv bietet dir ja nicht gerade viel an. Immerhin kannst auch den Broadcast schon auswerten, welcher auch in MQTT schon ankommen müsste.
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

Reinhart

Zitat von: Nighthawk am 04 Januar 2022, 10:25:07
ich verzweifle gerade an der Inbetriebnahme des eBus Schaltung, irgendwie will ebusd nicht mit dem Adapter.
Egal ob ich die Configuration in /etc/default/ebusd mache

EBUSD_OPTS="--scanconfig --accesslevel=* --latency=20 -d enh:/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_84e3dc3b00deea11b020cf149a583cc7-if00-port0 --address=ff"


Der Uart vom Adapter3 wird ja schon richtig gefunden und sitzt auf ttyUSB0. Ist es richtig, dass du einen Adapter V3 hast?

Versuche doch einmal den über ttyUSB0 zu laden. Der lange Namen des serial Device wird auf ttyUSB0 verlinkt.

--scanconfig --accesslevel=* --latency=20 -d enh:/dev/ttyUSB0 --address=ff

LG
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

Girgl

Hallo Gemeinde,

ich habe folgendes Problem, vielleicht kann mir ja jemand helfen.
Auf einem RPi Zero lief seit fast drei Jahren die RPi-Platine v2(fertig gelötet gekauft) zusammen mit 9x1-wire-Temperatursensoren(DS18b20) direkt an der Platine angeschlossen fehlerfrei. Auf dem Rpi Zero(stretch) lief lediglich eine fhem-Installation mit ebusd und 1-wire, sonst keine weiteren Applikationen. Dann erst Lesefehler auf dem ebus, danach ein kompletter Crash. Der RPi lies sich nicht mehr neu starten, deshalb neue sd-Karte und System neu aufgesetzt. Seitdem ist es nicht mehr möglich die ebus-Platine und die 1-wire-Sensoren gleichzeitig zu betreiben. Bei gleichzeitigem Betrieb loggt der ebus unregelmäßig, nicht nachvollziehbar, Fehler. Irgendwann "fängt" er sich wieder und verliert aber später wieder die Verbindung und so weiter. Die 1-wire Sensoren haben während der ebus-Fehler keine Probleme.
Bisher getestet:
Ein anders Netzteil für den RPi brachte keine Besserung.
Die ebus-Platine arbeitet ohne angeschlossene 1-wire-Sensoren einwandfrei.
Ich habe testweise mal nur fünf Sensoren angeschlossen, auch hier treten Fehler, aber nicht anscheinend nicht so häufig.
Bei neun angeschlossenen Sensoren kann sich der ebusd meist schon gar nicht verbinden.

Folgende Fragen, als Elektrinik-Laie, hätte ich:
Unterliegt die Platine oder eines der Bauteile einer natürlichen Alterung und sollte (regelmäßig) ersetzt werden?
Sind die 1-wire(GPIO 4, VCC, GND) Ausgänge auf der Platine durchgeschleift oder bezieht auch die ebusd Platine hier Strom/Daten.
Freue mich über jeden Rat.

/etc/default/ebusd
# /etc/default/ebusd:
# config file for ebusd service.

# Options to pass to ebusd (run "ebusd -?" for more info):
EBUSD_OPTS="--scanconfig"

# MULTIPLE EBUSD INSTANCES WITH SYSV
# In order to run multiple ebusd instances on a SysV enabled system, simply
# define several EBUSD_OPTS with a unique suffix for each. Recommended is to
# use a number as suffix for all EBUSD_OPTS settings. That number will then be
# taken as additional "instance" parameter to the init.d script in order to
# start/stop an individual ebusd instance instead of all instances.
# Example: (uncomment the EBUSD_OPTS above)
EBUSD_OPTS="--scanconfig -d /dev/ttyebus -p 8888 --configpath=/etc/ebusd/ --latency=100000 --loglevel=error -l /var/log/ebusd.log"
#EBUSD_OPTS1="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0 -p 8888 -l /var/log/ebusd1.log"
#EBUSD_OPTS2="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900acTF-if00-port0 -p 8889 -l /var/log/ebusd2.log"
#EBUSD_OPTS3="--scanconfig -d /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A900beCG-if00-port0 -p 8890 -l /var/log/ebusd3.log"

# MULTIPLE EBUSD INSTANCES WITH SYSTEMD
# In order to run muiltiple ebusd instances on a systemd enabled system, just
# copy the /usr/lib/systemd/system/ebusd.service file to /etc/systemd/system/
# with a different name (e.g. ebusd-2.service), remove the line starting with
# 'EnvironmentFile=', and replace the '$EBUSD_OPTS' with the options for that
# particular ebusd instance.


Daten zum ebusd:
pi@RPI-Zero:~ $ ebusctl info
version: ebusd 3.3.v3.3
update check: invalid request
signal: acquired
symbol rate: 46
max symbol rate: 115
min arbitration micros: 28
max arbitration micros: 1981
min symbol latency: 0
max symbol latency: 32
reconnects: 0
masters: 7
messages: 75
conditional: 0
poll: 0
update: 6
address 03: master #11
address 07: master #16
address 08: slave #11, scanned "MF=Kromschroeder;ID=  3B ;SW=" error: ERR: argument value out of valid range, loaded "kromschroeder/08.csv"
address 0c: slave #16, scanned "MF=Kromschroeder;ID=  ;SW=0204;HW=-"
address 10: master #2
address 15: slave #2, scanned "MF=Kromschroeder;ID=  ;SW=0204;HW=-"
address 30: master #3
address 31: master #8, ebusd
address 35: slave #3, scanned "MF=Kromschroeder;ID=  ;SW=0204;HW=-"
address 36: slave #8, ebusd
address 50: slave, scanned "MF=Kromschroeder;ID=  ;SW=0208;HW=-", loaded "kromschroeder/50.csv"
address 51: slave, scanned "MF=Kromschroeder;ID=  ;SW=0208;HW=-"
address 70: master #4
address 75: slave #4, scanned "MF=Kromschroeder;ID=  ;SW=0204;HW=-"
address f1: master #10

Das System:
pi@RPI-Zero:~ $ uname -a
Linux RPI-Zero 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux
pi@RPI-Zero:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

ebusd.log
2022-01-05 03:26:05.292 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 03:26:06.654 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:28:07.818 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:28:09.029 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:28:10.488 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:28:10.933 [bus error] send to 08: ERR: read timeout
2022-01-05 03:28:10.933 [bus error] send message part 0: ERR: read timeout
2022-01-05 03:28:11.311 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:28:12.621 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:28:14.499 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:28:15.256 [bus error] send to 08: ERR: SYN received
2022-01-05 03:28:15.256 [bus error] send message part 0: ERR: SYN received
2022-01-05 03:29:02.457 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:29:05.673 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:29:07.619 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:29:08.118 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:29:09.300 [bus error] send to 08: ERR: arbitration lost
2022-01-05 03:29:09.300 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 03:29:09.668 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:29:11.175 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:30:02.013 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:30:02.507 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:32:04.094 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:36:06.451 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:02.057 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:02.539 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:07.095 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:11.203 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:38:11.571 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:14.002 [bus error] send to 08: ERR: arbitration lost
2022-01-05 03:38:14.002 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 03:38:16.422 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:38:19.289 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:38:19.340 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:38:23.839 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:39:02.075 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:39:03.449 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:39:03.938 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:39:07.208 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:39:08.436 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:39:10.689 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:39:11.142 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:40:06.337 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:40:08.064 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:48:07.527 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:48:07.580 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:48:08.760 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:48:10.244 [bus error] send to 08: ERR: arbitration lost
2022-01-05 03:48:10.245 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 03:49:03.362 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:49:04.635 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:49:04.722 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:49:04.809 [bus error] send to 08: ERR: read timeout
2022-01-05 03:49:04.810 [bus error] send message part 0: ERR: read timeout
2022-01-05 03:49:09.039 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:49:10.479 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:49:11.744 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 03:49:15.092 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 03:49:15.092 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 03:49:15.648 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 03:51:07.630 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 03:57:07.509 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:02:03.261 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:02:03.680 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:02:10.375 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:02:11.909 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:02:11.909 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:02:13.454 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:02:14.725 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:02:14.855 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:02:14.939 [bus error] send to 08: ERR: read timeout
2022-01-05 04:02:14.939 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:02:15.388 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:03:05.313 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:03:10.069 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:03:11.602 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:03:13.404 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:03:13.404 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:03:20.883 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:03:30.823 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:03:35.798 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:03:43.684 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:03:43.684 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:03:50.629 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:06:07.500 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:06:08.114 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:06:10.721 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:06:11.132 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 04:06:11.132 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 04:06:15.642 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:06:20.262 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:06:21.501 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:06:24.364 [bus error] send to 08: ERR: read timeout
2022-01-05 04:06:24.365 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:08:07.910 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:08:09.109 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:08:10.070 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:08:13.835 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:08:13.835 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:08:19.297 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:08:19.665 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:08:23.293 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:08:24.897 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 04:08:24.898 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 04:09:02.383 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:09:03.833 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:09:04.747 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:09:04.834 [bus error] send to 08: ERR: read timeout
2022-01-05 04:09:04.835 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:10:05.282 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:10:05.858 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:10:07.770 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:10:09.300 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:10:09.300 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:10:10.826 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:10:10.909 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:10:10.992 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:10:11.073 [bus error] send to 08: ERR: read timeout
2022-01-05 04:10:11.073 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:10:13.755 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:10:14.302 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:10:14.332 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:10:15.505 [bus error] send to 08: ERR: SYN received
2022-01-05 04:10:15.505 [bus error] send message part 0: ERR: SYN received
2022-01-05 04:10:17.050 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:10:18.258 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:10:18.307 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:10:19.815 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:10:19.819 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:10:21.763 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:10:23.398 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:10:25.117 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:10:26.920 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:10:26.920 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:11:02.932 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:11:02.966 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:11:03.014 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:11:06.493 [bus error] send to 08: ERR: read timeout
2022-01-05 04:11:06.493 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:11:06.524 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:13:07.490 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:13:07.935 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:13:09.060 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:18:07.506 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:18:09.520 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:18:09.554 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:18:10.121 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 04:18:10.121 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 04:24:02.078 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 04:24:03.411 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:24:04.813 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:24:06.100 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 04:24:06.100 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 04:24:08.183 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:24:10.127 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:24:17.492 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:27:02.098 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:27:06.903 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:27:07.750 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:27:08.983 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 04:27:09.951 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:27:11.996 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:27:13.044 [bus error] send to 08: ERR: read timeout
2022-01-05 04:27:13.047 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:28:07.539 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:28:07.960 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:28:08.623 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:29:06.437 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 04:29:07.288 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:32:03.304 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:32:07.527 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:32:09.642 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:32:11.487 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:32:11.487 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:32:13.031 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:32:14.802 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:32:16.365 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:32:17.807 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:32:17.807 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:32:18.603 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:32:18.686 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:33:06.415 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:33:06.509 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:33:06.595 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:33:06.678 [bus error] send to 08: ERR: read timeout
2022-01-05 04:33:06.679 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:33:08.205 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:33:09.291 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:33:10.758 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:33:12.266 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:33:12.266 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:33:13.920 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:33:15.502 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:33:16.530 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:02.116 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:05.438 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:06.628 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:06.702 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:09.230 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:34:10.759 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:34:10.759 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:34:12.520 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:34:14.170 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:34:14.607 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:14.868 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:14.951 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:34:15.034 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:35:03.207 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:04.753 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:06.302 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:08.408 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:35:08.409 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:35:09.849 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:11.383 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:12.823 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:14.432 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:35:14.432 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:35:23.761 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:35:25.519 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:36:05.343 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:36:06.506 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:36:07.353 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:36:08.484 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:07.583 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 04:37:11.262 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:12.746 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:15.207 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:37:15.208 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:37:18.637 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:20.796 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:22.828 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:37:25.874 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:37:25.877 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:38:08.833 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:12.163 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:12.565 [bus error] send to 08: ERR: ACK error, retry
2022-01-05 04:38:13.925 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:38:13.926 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:38:15.915 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:17.169 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:38:17.302 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:38:17.747 [bus error] send to 08: ERR: read timeout
2022-01-05 04:38:17.748 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:38:18.852 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:38:19.940 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:21.470 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:22.915 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:38:22.918 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:38:24.565 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:26.038 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:27.545 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:29.025 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:38:29.025 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:38:30.465 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:31.729 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:33.274 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:34.819 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:38:34.819 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:38:36.355 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:37.795 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:39.235 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:38:40.803 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:38:40.803 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:03.187 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:04.870 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:05.991 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:39:07.178 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:07.179 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:08.619 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:10.059 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:11.594 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:13.139 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:13.139 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:16.478 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:17.919 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:19.359 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:20.829 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:20.829 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:22.334 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:23.984 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:25.424 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:26.961 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:26.961 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:28.404 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:30.011 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:31.556 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:32.996 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:32.996 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:39:34.600 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:36.073 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:37.582 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:39:39.021 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:39:39.022 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:03.213 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:04.757 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:06.294 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:07.737 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:07.738 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:09.178 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:10.618 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:11.880 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:13.428 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:13.428 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:16.735 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:18.209 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:19.653 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:21.332 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:21.332 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:22.879 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:24.426 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:25.900 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:27.136 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:27.136 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:28.576 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:30.016 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:31.550 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:33.132 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:33.132 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:40:34.691 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:36.230 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:37.671 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:40:39.111 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:40:39.111 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:03.225 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:04.772 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:06.311 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:07.752 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:07.752 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:09.192 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:10.739 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:12.280 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:13.933 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:13.934 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:17.225 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:18.665 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:20.126 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:21.659 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:21.659 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:23.204 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:24.750 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:26.289 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:27.730 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:27.730 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:29.170 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:30.610 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:32.145 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:33.795 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:33.796 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:41:35.349 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:36.891 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:38.331 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:41:39.771 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:41:39.771 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:03.182 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:04.683 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:06.147 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:07.654 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:42:07.654 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:09.094 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:11.306 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:14.488 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:15.963 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:42:15.963 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:18.281 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:20.574 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:22.108 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:23.684 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:42:23.684 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:25.295 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:26.564 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:28.004 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:29.444 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:42:29.444 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:30.911 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:33.689 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:40.633 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:42:50.590 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:42:50.591 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:42:55.556 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:43:02.997 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:43:10.911 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:43:20.837 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:43:20.837 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:43:22.244 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:47:06.218 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:47:07.677 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:47:08.123 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:47:08.206 [bus error] send to 08: ERR: read timeout
2022-01-05 04:47:08.206 [bus error] send message part 0: ERR: read timeout
2022-01-05 04:49:09.495 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:49:11.015 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:50:05.240 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:02.038 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:03.368 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:52:04.586 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:06.043 [bus error] send to 08: ERR: arbitration lost
2022-01-05 04:52:06.043 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 04:52:07.497 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:52:08.358 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:08.485 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:09.909 [bus error] send to 08: ERR: wrong symbol received
2022-01-05 04:52:09.909 [bus error] send message part 0: ERR: wrong symbol received
2022-01-05 04:52:13.587 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:52:14.068 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 04:52:14.196 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 04:56:06.433 [bus error] send to 08: ERR: SYN received, retry
2022-01-05 04:56:07.675 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 04:56:08.822 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:01:06.536 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:01:07.124 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 05:01:07.251 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 05:07:07.093 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:07:09.026 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:07:10.467 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:07:11.758 [bus error] send to 08: ERR: arbitration lost
2022-01-05 05:07:11.758 [bus error] send message part 0: ERR: arbitration lost
2022-01-05 05:07:13.307 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:07:14.525 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 05:32:02.339 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 05:37:06.409 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:37:07.586 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:37:08.674 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:37:09.644 [bus error] send to 08: ERR: read timeout
2022-01-05 05:37:09.644 [bus error] send message part 0: ERR: read timeout
2022-01-05 05:37:13.213 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:37:14.982 [bus error] send to 08: ERR: arbitration lost, retry
2022-01-05 05:44:07.529 [bus error] send to 08: ERR: wrong symbol received, retry
2022-01-05 05:44:09.772 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 06:37:05.354 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 07:02:06.522 [bus error] send to 08: ERR: read timeout, retry
2022-01-05 09:03:02.162 [bus error] send to 08: ERR: read timeout, retry


Reinhart

also natürliche Alterung kannst du nach so kurzer Zeit ausschließen und die 1-wire Anschlüsse sind ja nur durchgeschliffen.
Es gab schon einige Probleme mit Zenerdioden die vorzeitig ihren Betreib einstellten und die Adapter lahmlegten, aber das ist bei dir nicht der Fall.

Schau doch bitte mal in der Konsole mit "top" nach ob hier irgendwas die CPU einbremst oder stark belastet und eventuell die IOs in die Knie zwingt. Fehler auf dem Adapter glaub ich nicht, sonst würde es ohne die 1-wire Sensoren nicht funktionieren. Mir scheint es so, dass der ttyebus Treiber nicht oder nur träge zum Zug kommt und die serielle Übertragung gestört ist. Auffällig auch die Meldung das der Dämon den Updatecheck nicht schafft, funktioniert denn die Internetverbindung nach außen und vor allem DNS richtig?

Wenn bei meinem Raspi das Internet ausfällt, dann gibt es alle mögliche Fehler und träge Situationen die man sich kaum erklären kann weil es keinen offensichtlich erkennbaren Grund gibt.

LG
Reinhart
FHEM auf Raspy4 mit Bullseye + SSD, Homematic, ESP8266, ESP32, Sonoff, eBus, NanoCUL, MapleCUL, , MQTT2, Alexa

Girgl

Hallo Reinhart,

Danke für die Hinweise, top hat auf den ersten und die letzten Blicke (ich schau das öfters mal an) keine Aufffälligkeiten. Allerdings werde ich das wlan mal genauer anschauen müssen, kurz getestet war es teilweise sehr träge. Habe kürzlich auch eine zweite Fritzbox in Betrieb genommmen, vielleicht ist im mesh der Hund begraben.

LG Girgl