ebusd
ebusd copied to clipboard
Unstable connection
I have switched ebus adapter 3 from wemos to USB connected to raspberry. With wemos had a strange problem that after 2 monthsthe wemos became unresponsive. Reboots didn't help
Now i'm experienincg strange issues with rapberry. It connects sometimes and sometimes doesn't. And looking at the raw data - seems quite weird. Doesn't look like a valid signal. Checked the cables already. Reset the boiler (Protherm) but still the same
ebusd --lograwdata --configpath=http://ebusd.eu/config/ --scanconfig=full -f -d /dev/ttyUSB0 2021-12-30 09:26:42.988 [main notice] ebusd 21.3.v21.3 started with full scan on device /dev/ttyUSB0 2021-12-30 09:26:43.462 [bus notice] bus started with own address 31/36 2021-12-30 09:26:43.517 [bus notice] signal acquired 2021-12-30 09:26:44.865 [bus notice] <fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:46.214 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:47.885 [bus notice] ...<fefefefefefefffc7ffffefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:49.227 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:50.575 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:51.924 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:53.272 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:53.463 [main notice] starting initial full scan 2021-12-30 09:26:54.625 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:55.973 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:57.319 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:26:58.666 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:27:00.017 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:27:01.362 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:27:02.715 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:27:04.061 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe...
and then after 4 minutes 2021-12-30 09:31:21.997 [bus notice] ...<fefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe... 2021-12-30 09:31:24.036 [bus error] signal lost and after that 2021-12-30 09:32:37.600 [bus notice] re-opened /dev/ttyUSB0
And that's it
And this is what i get when the communications just get lost midpoint
2021-12-30 10:17:52.712 [main notice] update check: OK 2021-12-30 10:17:57.528 [main error] read bai PartloadHcKW cached: ERR: invalid position 2021-12-30 10:18:02.065 [bus error] device status: eBUS comm error: framing 2021-12-30 10:18:04.086 [bus error] signal lost 2021-12-30 10:18:05.282 [bus notice] signal acquired 2021-12-30 10:18:07.495 [bus error] device status: eBUS comm error: framing 2021-12-30 10:18:09.064 [bus error] signal lost 2021-12-30 10:18:27.526 [main error] read bai PartloadHcKW cached: ERR: invalid position 2021-12-30 10:18:28.049 [bus error] send to 08: ERR: no signal, give up 2021-12-30 10:18:28.049 [bus error] send message part 0: ERR: no signal 2021-12-30 10:18:57.530 [main error] read bai PartloadHcKW cached: ERR: invalid position 2021-12-30 10:19:12.573 [bus notice] device status: resetting 2021-12-30 10:19:12.573 [bus notice] re-opened /dev/ttyUSB0 2021-12-30 10:19:12.698 [bus notice] device status: reset 2021-12-30 10:19:27.526 [main error] read bai PartloadHcKW cached: ERR: invalid position
On the ebus i have only a protherm boiler connected. Wires from the ebus connector to adapter 3 are 1,5mm2 To exclude any inerference i have even soldered the wires to the adapter 3 with no luck
Any possible reasons? Or a faulty ebus adapter 3?
this looks a lot like you have another process using the same ttyUSB0 device. candidates for such processes are fhem and other stuff. you can check with lsof if another process is using the device
this looks a lot like you have another process using the same ttyUSB0 device. candidates for such processes are fhem and other stuff. you can check with lsof if another process is using the device
It's a fresh raspberry install. Nothing except ebusd is installed and nothing is quering ttyUSB0. Have checked that.
did you jumper the adapter to non-enhanced mode? If not, you need to use -d enh:/dev/ttyUSB0
instead of -d /dev/ttyUSB0
closed due to inactivity