Hi Bastian,
Correct me if am wrong, I inserted a tagged_stream_to_pdu block between the
clock_recovery_mm and the rxout pad sink. Isn't that the right way to run
the transceiver script.
Regards,
Ruecan
--
View this message in context:
On 04/07/2014 05:17 PM, Ruecan wrote:
Correct me if am wrong, I inserted a tagged_stream_to_pdu block between the
clock_recovery_mm and the rxout pad sink. Isn't that the right way to run
the transceiver script.
what blocks did you actually install?
If you talk about the 15.4 stuff from
Hi Bastian,
I am talking about the examples/ieee802_15_4_PHY.grc flowgraph and in order
to generate the ieee802_15_4_PHY.py I need to get the pads connected that's
when I inserted the tagged_stream_to_pdu block as I said.
Here is a snapshot
On 04/07/2014 05:47 PM, Ruecan wrote:
I am talking about the examples/ieee802_15_4_PHY.grc flowgraph and in order
to generate the ieee802_15_4_PHY.py I need to get the pads connected that's
when I inserted the tagged_stream_to_pdu block as I said.
Here is a snapshot
Hello Ruecan,
On 04 Apr 2014, at 22:56, Ruecan naceuram...@gmail.com wrote:
Did anyone encountered such an error while running the transceiver.py script
of 802.15.4 on GR 3.7
thread[thread-per-block[20]: block tagged_stream_to_pdu (10)]: tagged
stream does not contain a pdu_length tag
As
Hello GR,
Did anyone encountered such an error while running the transceiver.py script
of 802.15.4 on GR 3.7
thread[thread-per-block[20]: block tagged_stream_to_pdu (10)]: tagged
stream does not contain a pdu_length tag
I tried adding:
self.blocks_tagged_stream_to_pdu_0 =
