# Signal Decoding Problems

**URL:** <https://www.ruby-forum.com/t/signal-decoding-problems/243786>\
**Category:** GNU Radio\
**Created:** [January 6, 2016, 12:25pm UTC](https://www.ruby-forum.com/t/signal-decoding-problems/243786 "2016-01-06T12:25:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [January 6, 2016, 12:25pm UTC](https://www.ruby-forum.com/t/signal-decoding-problems/243786/1 "2016-01-06T12:25:08Z")

</div>

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