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

Decoder desired for Mueller Systems Hot Rod transmitter (water meter) #2719

Closed
howardtopher opened this issue Nov 12, 2023 · 16 comments
Closed
Labels
device support Request for a new/improved device decoder feedback request for more information; may be closed id 30d if not received

Comments

@howardtopher
Copy link

FCC info: https://fcc.report/FCC-ID/SM6-HOTRODV2ML
FCC test report: https://fcc.report/FCC-ID/SM6-HOTRODV2ML/1840648.pdf

I've been running rtl_433 for a bit and see almost 40 Neptune R900 meters, but none of them are mine. After opening up the meter box, it turns out my street has a different brand meter (Hersey Meters) with a Hot Rod v2 transmitter attached.

Based on the FCC test report, this meter is in 905-925MHz and uses GFSK modulation. Researching rtl_433 it seems it's not really great at GFSK. I've had rtl_433 output unknown sample files, but I get a lot of them (about 100 files in 30 seconds of time) and not sure if they are these meters or not. Since there's at least a whole street of them, there could be a lot of noise here.

I have the ID of my meter and can go out and look at the cubic feet measurement when ever I grab signals. According to the documentation this transmitter is supposed to transmit every 3 seconds over a range of frequencies so it should hopefully be quite talkative, but not really able to specifically trigger a broadcast.

I'm willing to provide whatever I can, but I may need guidance with the CLI parameters to get rtl_433 to properly see the GFSK signal.

@gdt gdt added the device support Request for a new/improved device decoder label Nov 26, 2023
@gdt gdt changed the title Add support for Mueller Systems Hot Rod transmitter (water meter) Decoder desired for Mueller Systems Hot Rod transmitter (water meter) Nov 26, 2023
@klohner
Copy link
Contributor

klohner commented Jan 8, 2024

Is this the same device as discussed in this other issue thread?

Decoder for Mueller Hot Rod V1 Water Meter Transmitter #2752

@howardtopher
Copy link
Author

Yes, that looks to be the same device.

@dolai1
Copy link

dolai1 commented Jan 8, 2024

That would be neat if they are using all the same protocol, but I am not sure that that is the case. Mine (in the referenced issue) is a "v1" unit that is "HI" power (SM6-HOTRODV1HI), for which I could not find FCC info or a test report...

@klohner
Copy link
Contributor

klohner commented Jan 9, 2024

Well, to investigate further, we'll need to look at some .cu8 files.

@howardtopher , would you please generate some .cu8 files from your device, zip, and post here?

@howardtopher
Copy link
Author

Even though I have a hotrodv2, I believe it's using the same protocol as the v1 in the other issue. The first 8 digits in the codes are my meter ID. I've attached samples from my meter. I ran the water for a while and only got the consumption number to change one time. I can do this again if we need more samples.

codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {75}14426616042f1201f80
codes : {76}1442661604978900fc0
codes : {75}14426616092f1201f80
codes : {75}14426614092f1201f80
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {76}1442661604978900fc0
codes : {75}1442661604978900f80
codes : {76}1442661604978900fc0
codes : {77}1442661604978900fc00
codes : {76}1442661604978900fc0
codes : {76}1442661604979500570
codes : {76}1442661604979500570
codes : {76}1442661604979500570

hotrod-samples.zip

@dolai1
Copy link

dolai1 commented Jan 11, 2024

Oh, nice! These match mine, then (2752).
Take the first 64 bits and plug them into here with CRC-8/ITU:
https://crccalc.com/
And you get the checksum at the end.

You got a lot of high-quality codes. Did you use the same rtl_433 command that I did, or something different? How far were you from the transmitter? I'm wondering how I can improve the consistency of my reads.

@howardtopher
Copy link
Author

You got a lot of high-quality codes. Did you use the same rtl_433 command that I did, or something different? How far were you from the transmitter? I'm wondering how I can improve the consistency of my reads.

Yes, I used the same command. I have my antenna in the attic and it happens to be on the same side of the house as the water meter. Meter is about 40 ft from the house, in the ground, just under a lid.

@dolai1
Copy link

dolai1 commented Jan 12, 2024

Oh, nice.
Mine were captured from inside the house but more like from ~150' from the meter, which is under a cast lid. I did mount the transmitter on the wall of the pit from the inside close to the surface, which improved reception. Putting the antenna on a ground plane (metal file cabinet) also made quite a big difference.

@ProfBoc75
Copy link
Collaborator

Hi @howardtopher :

As discussed in the other issue #2752
I started to write the decoder, I would like some more codes / more samples.

Notice that from the cu8 files I analyzed, the pulse is more around 26 µs than 20.
Can you try this:

rtl_433 -f 909M -R 0 -X 'n=hotrod,m=FSK_PCM,s=26,l=26,r=2500,preamble={24}feb100,bits>=72'

I would like to confirm the data layout at the volume level, with 5, 6 or 7 nibbles after the ID.

Possible bitbenchs

Let me know.

I will pull a request soon, starting with volume based on 5 nibbles / 20 bit.

@ProfBoc75 ProfBoc75 added the feedback request for more information; may be closed id 30d if not received label Mar 28, 2024
@howardtopher
Copy link
Author

Can you try this:

rtl_433 -f 909M -R 0 -X 'n=hotrod,m=FSK_PCM,s=26,l=26,r=2500,preamble={24}feb100,bits>=72'

I would like to confirm the data layout at the volume level, with 5, 6 or 7 nibbles after the ID.

@ProfBoc75

I've attached a bunch new samples using the command you provided. Hope these help!

hotrod-samples-pulse-26.zip

@ProfBoc75
Copy link
Collaborator

ProfBoc75 commented Mar 31, 2024

Thanks for your feedback, sounds like the water meter is based on 7 nibbles and not the 5 nibbles, from your samples, you have only 2 values, and always BCD values (binary coded decimal, i.e. base 10, never hexa values like a, b, c, d, e, or f):

0512080
0512228

Each time the 2 last nibbles from the 7 are numbers, never letter from Hexa coding. So, they are BCD values that belongs to the volume of gallons.

I'm waiting samples after @dolai1 will receive a new sdr device.

My decoder is ready, I commented the 7 nibbles decoding, just have to uncomment lines 98, 99 and to comment the 5 nibbles part , lines 88, 89, 90, 106 and test

@dolai1
Copy link

dolai1 commented Apr 1, 2024

I think that 2887 now takes care of this. Thank you both.

@ProfBoc75
Copy link
Collaborator

Yes, I merged my PR, the other issue was automatically closed by the PR.

Remaining this issue, @howardtopher if the last version of rtl_433 is working properly for you, we can close it.

@howardtopher
Copy link
Author

I'm not sure what's going on here, it's probably something I'm doing wrong. I've updated to the most recent commit. I'm not getting anything from the meter. What's weird is even using the commands from earlier when I was gathering data captures I still am not receiving anything. I've not changed anything in my setup and can still receive other things with rtl_433. Surely the battery in the hotrod transmitter didn't just happen to die. That would be really coincidental. Any other ideas beyond that why I can't hear it all of a sudden?

@ProfBoc75
Copy link
Collaborator

@howardtopher : could be an antenna issue, may be you moved it.

I put some verbose information into the decoder, try this:

rtl_433 -f 909M -R 255:vv -M level

Play with the gain option and try with -Y minmax option also.

@gdt
Copy link
Collaborator

gdt commented Jun 3, 2024

Seems like we think this is fixed and are not 100% sure. I am therefore closing, and if that's wrong please add a request to reopen with rationale.

@gdt gdt closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device support Request for a new/improved device decoder feedback request for more information; may be closed id 30d if not received
Projects
None yet
Development

No branches or pull requests

5 participants