Error while running transceiver.py in 802.15.4 on GR 3.7

GNU Radio
#1

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 =
blocks.tagged_stream_to_pdu(blocks.float_t, “packet_len”)
self.blocks_pdu_to_tagged_stream_0_0_0 =
blocks.pdu_to_tagged_stream(blocks.byte_t, “packet_len”)

still get the same output, I don’t know where in the flowgraph I am
missing
those tags.

Regards,
Ruecan

–
View this message in context:
http://gnuradio.4.n7.nabble.com/error-while-running-transceiver-py-in-802-15-4-on-GR-3-7-tp47403.html
Sent from the GnuRadio mailing list archive at Nabble.com.

#2

Hello Ruecan,

On 04 Apr 2014, at 22:56, Ruecan [email protected] 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 far as I see there is not tagged_stream_to_pdu block in any of the
flow graphs, or am I missing something?
Maybe you mixed it up with pdu_to_tagged_stream?

I tried adding:

self.blocks_tagged_stream_to_pdu_0 =
blocks.tagged_stream_to_pdu(blocks.float_t, “packet_len”)
self.blocks_pdu_to_tagged_stream_0_0_0 =
blocks.pdu_to_tagged_stream(blocks.byte_t, "packet_len)

I would recommend to edit the flow graph in GRC instead of editing the
generated .py file.

Best,
Bastian

–
Dipl.-Inform. Bastian B.
Distributed Embedded Systems
University of Paderborn, Germany
http://www.ccs-labs.org/~bloessl/

#3

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:
http://gnuradio.4.n7.nabble.com/error-while-running-transceiver-py-in-802-15-4-on-GR-3-7-tp47403p47421.html
Sent from the GnuRadio mailing list archive at Nabble.com.

#4

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
https://github.com/bastibl/gr-ieee802-15-4

you just build the hierarchical block (open it in grc and ‘generate’
it). Then open the transceiver flow graph and start it. There is also a
script that shows how to start wireshark together with the transceiver
flow graph in the apps folder.

Best,
Bastian

#5

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

http://gnuradio.4.n7.nabble.com/file/n47425/Untitled.png

Regards,
Ruecan

–
View this message in context:
http://gnuradio.4.n7.nabble.com/error-while-running-transceiver-py-in-802-15-4-on-GR-3-7-tp47403p47425.html
Sent from the GnuRadio mailing list archive at Nabble.com.

#6

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

http://gnuradio.4.n7.nabble.com/file/n47425/Untitled.png

This is a Hier Block and the pads are the endpoints. They don’t have to
be connected. This block is used as a building block in the transceiver
flow graph.