Closed minitrue-nl closed 4 years ago
in most cases this is due to another device connected to the UART or another software using it for different purposes. I'd recommend changing from /dev/ttyUSB* to /dev/serial/by-id/... to prevent a reboot or plug in of another USB device to ruin your configuration
Thanks, that pointed me in the right direction. There was still another (modbus) program running in the background, messing with the /dev/ttyUSB0.
Hi, For more than a year I had ebusd running on my linux server trough eseras usb coppler without problems, but now (after adding another usb-device) I encountered problems.
Ebusd seems to run just fine as a program, but doesn't seem connected with the ebusd anymore. I used to have a full set up which could read all comunnication from vrc700, heatpump and everything.
if I run
sudo ebusd -f -c /tmp --logareas bus --loglevel info --lograwdata=bytes -d /dev/ttyUSB0
I see that there is a connection and data is coming in, but lots of the messages are >ff in stead of >aa as described in the docs. Could this be a hint to a solution? I rember from my first set up I actually saw the >aa's