discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Help, dont understand gr.hier_block proper use


From: address@hidden
Subject: [Discuss-gnuradio] Help, dont understand gr.hier_block proper use
Date: Tue, 7 Feb 2006 11:23:50 -0500

Hello all,

I have been trying to make my own version of the gmsk2 benchmark for ask
modulation.  I am getting the following error:

Using RX d'board A: <none>
self =  <mrts.blksimpl.ask.ask_demod object at 0xb7a70dcc>
Traceback (most recent call last):
  File "./benchmark_ask_rx.py", line 128, in ?
    main()
  File "./benchmark_ask_rx.py", line 121, in main
    fg = my_graph(options.rx_subdev_spec, options.decim, rx_callback,
options.log)
  File "./benchmark_ask_rx.py", line 81, in __init__
    rx_callback, log)
  File "./benchmark_ask_rx.py", line 62, in __init__
    threshold=threshold)
  File "/home/mrobitaille/GRworking/MRTS/src/lib/mrts/blksimpl/ask_pkt.py",
line 74, in __init__
    self.ask_demod = ask.ask_demod(fg, *args, **kwargs)
  File "/home/mrobitaille/GRworking/MRTS/src/lib/mrts/blksimpl/ask.py",
line 75, in __init__
    input_rate = self.adc_freq() / self.decim_rate() # 64 MS/s // 250 =
AttributeError: 'ask_demod' object has no attribute 'adc_freq'

I believe its due the the gr.hier_block.__init__.

Per the DShen tutorial states "Either head or tail may be None indicating a
sink or source respectively.".  The gmsk2_demod(_pkg) modules dont seem to
follow this.  I would think these blocks should be sink but seem to be
source per DShen statement (tail is None).  I also see that there is times
where both are etheir none or the same.

Could someone please clarify?

Also, could someone look at my code and see why I am getting the error.

Thanks,
Mike


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Attachment: benchmark_ask_rx.py
Description: benchmark_ask_rx.py

Attachment: ask.py
Description: ask.py

Attachment: ask_pkt.pyc
Description: ask_pkt.pyc


reply via email to

[Prev in Thread] Current Thread [Next in Thread]