Forum: GNU Radio Signal Decoding Problems

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
F44ef32b3ae95603b24f901b9fecc2f1?d=identicon&s=25 Jeremy Br (jeremy_br)
on 2016-01-06 12:25
Attachment: complex_signal (40 KB)
Attachment: magnitude (40 KB)
Attachment: bit (30 KB)
Attachment: mm_clock_recovery (40 KB)
Hey,
I'm trying to decode a Enocean signal, but can't link the received data
to the corresponding byte sequence, which was decoded by an Enocean
receiver.
Following the Enocean specifications the signal (attached) is
ASK-modulated with 125 kbit/s data rate. The Enocean protocol refers to
ISO Standard 14543-3-10:2012, but as a student I can't afford 130€ for
the document.

After computing the magnitude of the signal (attached) and mapping to 0
or 1 (attached), the MM clock recovery produces the attached bit
sequence.

I verified the MM generated bit sequence by reading the bits manually
out of the magnitude view. The sequence and signal edges are also
fitting in the 125 kbit/s frequency. Because the timing is covering the
signal edges instead of the high & lows, it can't be Manchester encoded
(or am I wrong?).

This bit sequence is produced by my flow graph:
101010101101010011010101110111011101110001011101101011010101101000101101110010101010

While the official Enocean reciever is producing this output:
0007,07,01,7A,F610018313E12001FFFFFFFF3100,07

|--data_length--|--optionaldata_length--|--type--|--crc_header--|--data--|--crc_data--|

Does someone has a clue, how the signal is modulated to produce these
data?

cheers
Jeremy
This topic is locked and can not be replied to.