Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiving FF byte over and over again #216

Open
LordGregorious opened this issue Jul 25, 2024 · 2 comments
Open

Receiving FF byte over and over again #216

LordGregorious opened this issue Jul 25, 2024 · 2 comments

Comments

@LordGregorious
Copy link

LordGregorious commented Jul 25, 2024

Hi. I hope someone is still out there to help.

I have been using libmbus on raspberry pis to communicate with a Relay PW250 to read water meters. I have several sites with this set up and it's always worked fine.

Until now. When I run mbus-serial-request-data at a baudrate of 2400 I just receive a 00 byte (not always), followed by the FF byte over and over again. It's a similar story with the mbus-serial-scan.

However when I connect my windows laptop to the PW250 and run MBSheet (at 2400 baudrate) it works perfectly fine.
I've tried with two different raspberry pis ( raspberry pi 3 and raspberry pi 5), tried different usb ports, tried with a different cable. The problem persists.

I've desperately searched and tried things but nothing has worked. Any help would be immensely appreciated. I can post logs if you need.

@cybermailer84
Copy link

which raspbian do you use. I have the same problem since my last updates. I will try an older raspbian version and have to check. I dont know exactly if something was changed and that causes the problem, but i think so.

@LordGregorious
Copy link
Author

The raspberry pi is running Debian GNU/Linux 12 (bookworm).
I found the issue was that one of the modules was water-damaged (or something) and was constantly sending out rubbish data, thus clogging the bus and all communication.

I recommend disconnecting your network of modules from the repeater and just testing a single module.
If it works fine then likely one of the modules is faulty and you'll have to manually go through them all to find it.

For me, it was set up floor by floor in an apartment complex, so I could test each floor individually until I found the one containing the faulty module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants