Closed AloisKlingler closed 3 years ago
there might be issues with buffering done by the serial converter.
if you run ebusd with --lograwdata=bytes
for a while, you can see the delay of incoming data
2021-03-08 10:35:18.946 [bus debug] send/receive symbol latency 5 ms
2021-03-08 10:35:18.948 [bus notice] >50
2021-03-08 10:35:18.953 [bus notice] <50
2021-03-08 10:35:18.953 [bus debug] send/receive symbol latency 5 ms
2021-03-08 10:35:18.955 [bus notice] >01
2021-03-08 10:35:18.962 [bus notice] <01
2021-03-08 10:35:18.962 [bus debug] send/receive symbol latency 6 ms
2021-03-08 10:35:18.963 [bus notice] >01
2021-03-08 10:35:18.969 [bus notice] <01
2021-03-08 10:35:18.969 [bus debug] send/receive symbol latency 5 ms
do you mean these messages?
yes. here you can see a usual latency of 4-6 ms. but you should set the "--latency" to at least 20ms
closed due to inactivity
Hi John,
I am using a USB adapter from here (https://www.mikrocontroller.net/topic/346833). The adapter has a FTDI USB converter. It is connected (and working without issues) on a raspberry pi 1, attached without any additional hub, by a short USB cable. There is one device, a brink renovent excellent 300 cabled on the adapter.
if I use "--latency=0" as mentioned in the wiki I constantly can see "bus error signal lost" in log:
nevertheless the communication works, so I can fetch and send data from/to the brink WTW unit.
if I use "--latency=100" (e.g. "--latency=10" does not help) this errors are gone:
which latency should be used by a USB connection, and if 0 needs to be used, is there anything wrong in my setup?
symbol rate is sometimes 22
Thank you!
Best regards Alois