Assistance in decoding signal

[InTheAbsenceOfAHorse]

Hi,

I'm trying to decode the signals from a scoreboard controller. I've been able to capture the signal and have tried the -A option to get a suggestion from the analyser but it doesn't seem to find anything. I THINK its either Manchester or differential Manchester encoded.

An example of the message is https://triq.org/pdv/#AAB03F0601002802140840042C01900C2C8491919191919191919191919191919191919191A19391919191B19193B1919193B19193B191919191919191919191919255+AAB02B0608002802140840042C01900C2CA19391919191B19193B1919193B19193B191919191919191919191919255+AAB02B0601002802140840042C01900C2CA19391919191B19193B1919193B19193B191919191919191919191919555

I've put a set of recordings I have at https://github.com/InTheAbsenceOfAHorse/rtl_433_tests/blob/master/tests/FSL%20Cricket%20Scoreboard%20Controlller/

All thoughts greatly appreciated

[zuckschwerdt]

Yes, looks like FSK 500 µs MC. This should work to get you data: rtl_433 -R 0 -X 'n=name,m=FSK_MC_ZEROBIT,s=500,l=500,r=1300'

[InTheAbsenceOfAHorse]

Thanks, Will give it a shot.

[InTheAbsenceOfAHorse]

Fantastic. Needed to invert the signal for it to make sense but you had it as close to spot on as you could possibly be.

[zuckschwerdt]

Thanks! To be fair you did all the work, I only had a brief look at the pulse data :)

[dwmw2]

I built a decoder for this in #3443

It's 38 bits of 101010 preamble, followed by ten mostly-identical copies of the actual data, each starting with three 111 bits, then 33 bits of Manchester-encoded data, then three 000 bits.

For some reason the 33rd bit of the Manchester-encoded data is sometimes '1' in the first copy, and '0' in the rest. I don't even bother to decode that one; I'm not even sure it's supposed to be there.

The remaining 32 bits are 0x3f2h1t0u with field#, hundreds, tens, units and literal 3210 which appears to be digit position? In the absence of a CRC I'm just using those high nybbles as a sanity check.

[dwmw2]

I can't get rtl_433 to decode it without using -Y minlevel=-1.5 though. I don't really see why; the signal is fairly clear: