search

Apollon77 / ioBroker.mbus

Communicate with mbus devices
MIT License
11 stars 9 forks source link

M-Bus ID 12 err: Error: Error: Failed to send/receive M-Bus request frame[12]. #331

Closed Klaus-Lucas closed 10 months ago

Klaus-Lucas commented 10 months ago

@Apollon77 Ich habe seit gestern sehr viele obige Fehlermeldung im Log. Es handelt sich um einen ABB Zweirichtungs-Stromzähler.

2023-09-12 07:47:04.832 - debug: mbus.0 (253748) Create State ABB-1793379.info.Id 2023-09-12 07:47:04.833 - debug: mbus.0 (253748) Create State ABB-1793379.info.Manufacturer 2023-09-12 07:47:04.834 - debug: mbus.0 (253748) Create State ABB-1793379.info.Version 2023-09-12 07:47:04.834 - debug: mbus.0 (253748) Create State ABB-1793379.info.ProductName 2023-09-12 07:47:04.835 - debug: mbus.0 (253748) Create State ABB-1793379.info.Medium 2023-09-12 07:47:04.836 - debug: mbus.0 (253748) Create State ABB-1793379.info.AccessNumber 2023-09-12 07:47:04.837 - debug: mbus.0 (253748) Create State ABB-1793379.info.Status 2023-09-12 07:47:04.837 - debug: mbus.0 (253748) Create State ABB-1793379.info.Signature 2023-09-12 07:47:04.838 - debug: mbus.0 (253748) Create State ABB-1793379.info.address 2023-09-12 07:47:04.838 - debug: mbus.0 (253748) Create State ABB-1793379.data.0-0-Current 2023-09-12 07:47:04.839 - debug: mbus.0 (253748) Create State ABB-1793379.data.1-0-Current 2023-09-12 07:47:04.839 - debug: mbus.0 (253748) Create State ABB-1793379.data.2-0-Current 2023-09-12 07:47:04.839 - debug: mbus.0 (253748) Create State ABB-1793379.data.3-0-Current 2023-09-12 07:47:04.840 - debug: mbus.0 (253748) Create State ABB-1793379.data.4-0-Current 2023-09-12 07:47:04.840 - debug: mbus.0 (253748) Create State ABB-1793379.data.5-0-Current 2023-09-12 07:47:04.840 - debug: mbus.0 (253748) Create State ABB-1793379.data.6-0-Current 2023-09-12 07:47:04.841 - debug: mbus.0 (253748) Create State ABB-1793379.data.7-0-Current 2023-09-12 07:47:04.841 - debug: mbus.0 (253748) Create State ABB-1793379.data.8-0-Current 2023-09-12 07:47:04.841 - debug: mbus.0 (253748) Create State ABB-1793379.data.9-0-Current 2023-09-12 07:47:04.841 - debug: mbus.0 (253748) Create State ABB-1793379.data.10-0-Current 2023-09-12 07:47:04.842 - debug: mbus.0 (253748) Create State ABB-1793379.data.11-More records follow 2023-09-12 07:47:04.842 - debug: mbus.0 (253748) Create State ABB-1793379.data.12-0-Current 2023-09-12 07:47:04.842 - debug: mbus.0 (253748) Create State ABB-1793379.data.13-0-Current 2023-09-12 07:47:04.843 - debug: mbus.0 (253748) Create State ABB-1793379.data.14-0-Current 2023-09-12 07:47:04.843 - debug: mbus.0 (253748) Create State ABB-1793379.data.15-0-Current 2023-09-12 07:47:04.843 - debug: mbus.0 (253748) Create State ABB-1793379.data.16-0-Current 2023-09-12 07:47:04.843 - debug: mbus.0 (253748) Create State ABB-1793379.data.17-0-Current 2023-09-12 07:47:04.843 - debug: mbus.0 (253748) Create State ABB-1793379.data.18-0-Current 2023-09-12 07:47:04.844 - debug: mbus.0 (253748) Create State ABB-1793379.data.19-0-Current 2023-09-12 07:47:04.844 - debug: mbus.0 (253748) Create State ABB-1793379.data.20-0-Current 2023-09-12 07:47:04.844 - debug: mbus.0 (253748) Create State ABB-1793379.data.21-0-Current 2023-09-12 07:47:04.844 - debug: mbus.0 (253748) Create State ABB-1793379.data.22-0-Current 2023-09-12 07:47:04.844 - debug: mbus.0 (253748) Create State ABB-1793379.data.23-0-Current 2023-09-12 07:47:04.845 - debug: mbus.0 (253748) Create State ABB-1793379.data.24-0-Current 2023-09-12 07:47:04.845 - debug: mbus.0 (253748) Create State ABB-1793379.data.25-0-Current 2023-09-12 07:47:04.845 - debug: mbus.0 (253748) Create State ABB-1793379.data.26-0-Current 2023-09-12 07:47:04.845 - debug: mbus.0 (253748) Create State ABB-1793379.data.27-0-Current 2023-09-12 07:47:04.845 - debug: mbus.0 (253748) Create State ABB-1793379.data.28-0-Current 2023-09-12 07:47:04.846 - debug: mbus.0 (253748) Create State ABB-1793379.data.29-0-Current 2023-09-12 07:47:04.846 - debug: mbus.0 (253748) Create State ABB-1793379.data.30-0-Current 2023-09-12 07:47:04.846 - debug: mbus.0 (253748) Create State ABB-1793379.data.31-0-Current 2023-09-12 07:47:04.846 - debug: mbus.0 (253748) Create State ABB-1793379.data.32 2023-09-12 07:47:04.846 - debug: mbus.0 (253748) Create State ABB-1793379.data.lastStatus 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.0-0-Current: 3466 (unit: 10 Wh) with factor 0.01 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.1-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.2-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.3-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.4-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.5-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.6-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.7-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.8-0-Current: 0 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.847 - debug: mbus.0 (253748) Value ABB-1793379.data.9-0-Current: B1.30.0 (unit: Firmware version) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.10-0-Current: B23 113-100 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.11-More records follow: (unit: ) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.12-0-Current: 9245 (unit: 1e-2 W) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.13-0-Current: 770 (unit: 1e-2 W) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.14-0-Current: 6339 (unit: 1e-2 W) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.15-0-Current: 2137 (unit: 1e-2 W) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.16-0-Current: 2318 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.17-0-Current: 2298 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.18-0-Current: 2310 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.19-0-Current: 4000 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.20-0-Current: 3994 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.21-0-Current: 3998 (unit: 1e-1 V) with factor 0.1 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.22-0-Current: 259 (unit: m A) with factor 0.001 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.23-0-Current: 312 (unit: m A) with factor 0.001 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.24-0-Current: 464 (unit: m A) with factor 0.001 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.25-0-Current: 4998 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.26-0-Current: 425 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.27-0-Current: 3 (unit: Manufacturer specific) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.28-0-Current: 0 (unit: binary) with factor 0 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.29-0-Current: 884 (unit: 10 Wh) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.30-0-Current: 872 (unit: 10 Wh) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.31-0-Current: 1709 (unit: 10 Wh) with factor 0.01 2023-09-12 07:47:04.848 - debug: mbus.0 (253748) Value ABB-1793379.data.32: (unit: ) with factor 0 2023-09-12 07:47:06.437 - debug: mbus.0 (253748) Process: 12 2023-09-12 07:47:08.687 - warn: mbus.0 (253748) M-Bus ID 12 err: Error: Error: Failed to send/receive M-Bus request frame[12]. 2023-09-12 07:47:08.687 - warn: mbus.0 (253748) M-Bus Devices with errors: 1 from 7

Das gesamte Debug-Log kannst du dir es hier runterladen. Das M-Bus Schnittstelle im Zähler eine Macke hat, kann ich eigentlich ausschließen. Ich alle Werte auslesen kann:

k_003 k_004 k_005 k_006 k_007 k_008

Kannst du mir ggf. weiterhelfen, wo das Problem liegt?

Versions:

Apollon77 commented 10 months ago

Hast DU den MBus Master mal "restarted" 8also usb raus, 30s warten, neu rein?

Klaus-Lucas commented 10 months ago

@Apollon77 Ja, habe ich gemacht. Leider kein Erfolg. Das Kabel hatte am Ende wohl einen Bruch. Nachdem ich es gekürzt und neu abisoliert hatte, kam der Fehler nicht mehr. Vielen Dank für deine Mühe.

Klaus-Lucas commented 10 months ago

Bitte schließen

Klaus-Lucas commented 9 months ago

Darf ich dich nochmal wegen MBus belästigen?

Apollon77 commented 9 months ago

Was ist denn?

Klaus-Lucas commented 9 months ago

Wenn ich wieder die Frame Fehler bekomme, wäre ein Debuggen mit mbus-serial-request-data-multi-reply eine Möglichkeit das rauszubekommen oder würde ich genau das sehen, was du ausgibst? Denke das Libmbus die Verbindung zur Hardware ist. Ich kann ja mit Lorrus immer die Zähler auslesen, wenn dein Adapter Frame-Fehler meldet. Da ich für Lorrus die gleiche Harware und Verkabelung nutze, kann es in meinem Verständnis nur am NUC PC hängen, wo unter Proxmox der USB-Port zur iobroker-VM durchgereicht wird. Ich würde dann einmal in der Proxmox-VM den USB-Port debuggen und dann in der iobroker-VM.

Apollon77 commented 9 months ago

Ja genau, der Adapter nutzt eine Lib die auf libmbus aufsetzt. Es sollte also so funktionieren wie libmbus (oder halt nicht). Sonst gabs noch einen Weg ein Debug binatryder lib zu nutzen dann gäbe es mehr logs ... muss aber suchen wie das ging :-)