# Error while running transceiver.py in 802.15.4 on GR 3.7 **URL:** \ **Category:** GNU Radio\ **Created:** [April 4, 2014, 10:57pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271 "2014-04-04T22:57:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Detlef\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58f4c7/32.png) [@Detlef\_R](https://www.ruby-forum.com/u/Detlef_R)\ **Post date:** [April 4, 2014, 10:57pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/1 "2014-04-04T22:57:35Z")
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]: \]: 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](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](http://Nabble.com). ---
**Author:** ![naeo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/57b2e6/32.png) [@naeo](https://www.ruby-forum.com/u/naeo)\ **Post date:** [April 5, 2014, 11:16am UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/2 "2014-04-05T11:16:59Z")
Hello Ruecan, On 04 Apr 2014, at 22:56, Ruecan [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) 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]: \]: 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 > **[Home](https://www.bastibl.net/)** > > I'm Bastian Bloessl, a Research Group Leader at the Secure Mobile Networking Lab, TU Darmstadt. Checkout my blog, projects, publications, and resume; or connect on Github, Twitter, YouTube, or Facebook. ---
**Author:** ![naeo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/57b2e6/32.png) [@naeo](https://www.ruby-forum.com/u/naeo)\ **Post date:** [April 7, 2014, 5:18pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/3 "2014-04-07T17:18:32Z")
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](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](http://Nabble.com). ---
**Author:** ![naeo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/57b2e6/32.png) [@naeo](https://www.ruby-forum.com/u/naeo)\ **Post date:** [April 7, 2014, 5:38pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/4 "2014-04-07T17:38:24Z")
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 > **[GitHub - bastibl/gr-ieee802-15-4: IEEE 802.15.4 ZigBee Transceiver](https://github.com/bastibl/gr-ieee802-15-4)** > > IEEE 802.15.4 ZigBee Transceiver 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 ---
**Author:** ![naeo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/57b2e6/32.png) [@naeo](https://www.ruby-forum.com/u/naeo)\ **Post date:** [April 7, 2014, 5:48pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/5 "2014-04-07T17:48:57Z")
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](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](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](http://Nabble.com). ---
**Author:** ![naeo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/57b2e6/32.png) [@naeo](https://www.ruby-forum.com/u/naeo)\ **Post date:** [April 7, 2014, 5:52pm UTC](https://www.ruby-forum.com/t/error-while-running-transceiver-py-in-802-15-4-on-gr-3-7/240271/6 "2014-04-07T17:52:27Z")
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](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.