John
John
you'd need to provide the CSVs and some ebusd logging
can't open your files
if you want to check for incomplete/bad messages, then you'd have to do raw logging with bytes and check the log exactly at the time you expect the change to...
if you can't find any related message logged by ebusd at the time you do the actions on the BM-2 controller, then it might just not send any message on...
hm, 71 (76) is not listed in the info, so it probably does not answer the ID query. but I'm not sure that this is the right message and since...
> As I understood each element should have 2parts:1 master + 1 slave In my config the component Nr. 51 has no master, the component Nr. f1 has no slave...
some of the bus error messages are related to framing during arbitration which should be normal. as long as you can retrieve values from the devices, this is expected
please provide ebusd logs with lograwdata=bytes for both cases including all the start parameters used
closed due to inactivity
I can't reproduce this on a RPi buster with 21.3. maybe this is related to the umask? you might want to check [this](https://wiki.debian.org/Debate/umask).