-
Notifications
You must be signed in to change notification settings - Fork 45
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
CRC-issues #6
Comments
Check out the fork https://github.com/afflux/rtl-wmbus.git it can receive C1 telegrams. |
Got perfect reception right away! Thanks! |
I have the same problem with a Lorenz water meter, which is a rebranded Engelmann Waterstar M.
I already tried the fork by @afflux, the output above is from the fork. What would you suggest I do to see where the CRC problem originates? |
Can you test xaelsouths latest master? It supports C1. |
Yes, I have originally started with that one and after reading what you wrote in wmbusmeters/wmbusmeters#99, I started to look into rtl_wmbus some more, saw this issue right here and then also tried the version by afflux. I get the same output no matter what I do. |
@makuser Strage, do you receive other meters of the same model? The radio decoding code is currently outside of my competence. |
I only have one meter for testing of this model, but already requested a second one.
Okay, too bad. You also don't know if there are any debug options in rtl-wmbus I could enable to see what the expected and sent CRC values are?
Okay, sure. I will try to source one of these. The amb8465 seems to be the better choice, am I right on that? And should it be a AMB8465 or AMB8465-M? |
I think it is AMB8465-M |
sooo. The AMB8465-M finally arrived on friday and I was able to run wmbusmeters with the AMB8465. How shall I proceed best, so that we can test and fix this? |
makuser, could you test with the newest version? |
I have to consider this issue closed because of no response from users and because some fixes on C1 were made, which should improve the C1 receiver quality. |
Seem to have some strange issue with CRC errors. The "10030325" is a Kamstrup flowIQ 2200 and I'm pretty sure the IDs are the same. Have tried with three different dongles including a rtlsdr-v3 and some combinations of antennas. Have received different levels of RSSI but seem unable to get a single packet with OK CRC. Any ideas?
C1;0;1;2019-12-12 17:40:03.000;8;7;10030332;0x3644372c320303103a163108f01920a85417a08312020a019d8f8af8cfad73221b05c33dfc6618a93c5a6277d1de1d5d071f8242f959c1
C1;0;1;2019-12-12 17:40:28.000;117;117;10030325;0x3644372c250303103a16ff00f01920c49674902ae43a6f88c416e528d90a0bb8bcea9de6b949f3a6b4d54183c8c99c136e707694a659c1
C1;0;1;2019-12-12 17:42:52.000;8;8;10030330;0x3644372c300303103a164320f01920afd1ead56723e577f2faf31e9fd6b860a3f5e6e78fe9847d997fd7defec2483df3e0c4e43dc159c1
C1;0;1;2019-12-12 17:43:46.000;113;116;10030325;0x3644372c250303103a160138f01920b27d02632ce5a00a92d9686d9c13ad578b579cc79c637a89724fe757bd59de898bfa469b4c0159c1
C1;0;1;2019-12-12 17:45:49.000;29;32;10030266;0x3644372c660203103a164c14f41920c4c93344c164e0f85a5fe9ba080e1f7e08c6ca62052e6437057af458c2f0ec2ab2756a20fe2b59c1
The text was updated successfully, but these errors were encountered: