[Discuss-gnuradio] Need help with LFRX

2007-07-05 Thread Pawel Koszut
Hi all !

I am interested in observing spectrum around 200kHz and tried the following 
command :
./usrp_fft.py -R A:0 -f 20 -d 112
with a coil antenna connected to RX-A input of LFRX daughterboard.

Should it work ?
If so, does it mean that there is something wrong with my antenna ?

Regards,
Pawel


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: Re: [Discuss-gnuradio] How to display mux value?

2007-05-22 Thread Pawel Koszut
Hi Steven,

It works fine !
Together with Charles Swiger's suggestions, you helped me with three possible 
approaches :
=
m = usrp.determine_rx_mux_value(self.u, options.rx_subdev_spec)
print "mux1 = %x" %(0x1 + m)
print "mux2 = ",hex(0x1 + m)
print "mux3 = 0x%08x" % (0xL & long(m))
=

Thanks for both of you,

Pawel


On Tuesday 08 May 2007 16:47, you wrote:
> (Sorry for sending this twice, Pawel, I forgot to send to list. Also I
> corrected a minor error I made)
>
> Hi Pawel-
>
> You've probably figured this out by now, but I ran into the same thing
> yesterday. Here's what I did.
>
> in_mux_value = usrp.determine_rx_mux_value(self.usrp_in,
> in_dcard_subdev_spec)
> print "RX mux value: 0x%08x" % (0xL & long(in_mux_value))
> self.usrp_in.set_mux(in_mux_value)
>
> The determine_*x_mux_value() method returns a (32 bit) int, but if the MSB
> is set, for example 0xF0F0F0F2, python thinks it's a negative number, which
> screws up the printing. Cast it to a long and mask off the bottom 32 bits.
>
> Hope that helps.
>
> -Steven
>
> On 4/28/07, Pawel Koszut <[EMAIL PROTECTED]> wrote:
> > Hi all !
> >
> > Who knows how to display mux value ?
> >
> > print "mux =", hex(usrp.determine_rx_mux_value(self.u,
> > options.rx_subdev_spec))
> >
> > displays negative values, for example -0xf0f0f0e
> > How to interpret negative value ?
> > and how to interpret 7 digit hex number istead of 8 digit.
> >
> > regards,
> > Pawel
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] How to display mux value?

2007-04-28 Thread Pawel Koszut
Hi all !

Who knows how to display mux value ?

print "mux =", hex(usrp.determine_rx_mux_value(self.u,options.rx_subdev_spec))

displays negative values, for example -0xf0f0f0e
How to interpret negative value ?
and how to interpret 7 digit hex number istead of 8 digit.

regards,
Pawel


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] LFRX installation questions

2007-04-08 Thread Pawel Koszut
Hi all !

I have several questions regarding LFRX daughterboard :

Why does LFRX have two inputs (RX-A and RX-B) and not one like DBSRX for 
example ?
Do I need a separate RF front end to use it ?
Is it necessary to reburn eeprom after installation of this daughterboard ?

Reagrds,
Pawel


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] graphical interface for gnu radio

2007-01-01 Thread Pawel Koszut
I tried it uder Ubuntu and openSuse and it runs fine.
(openSuse required python-gtk and pyxml packages)

Up to now, I have tested several visual components, and I had only problem with 
USRP source.
Below is detailed output.
I think it will be very useful tool and look forward as you continue this 
project.

Pawel


Traceback (most recent call last):
  File "RunnableFlowGraph.py", line 162, in ?
app.SetTopWindow(RunnableFlowGraph(sys.argv[1]))
  File "RunnableFlowGraph.py", line 51, in __init__
self.parse_nested_data(nested_data)
  File "RunnableFlowGraph.py", line 147, in parse_nested_data
if runnable_signal_block != None: self.signal_blocks_dict[id] = 
runnable_signal_block(*data_type_params)
  File "/home/pawel/programy_gr/grc_0.50/src/RunnableSignalBlocks.py", line 17, 
in USRP_SOURCE
u = usrp.source_c(USRP_number, decimation.parse())
  File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp.py", line 245, in 
__init__
_ensure_rev2(which)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp.py", line 82, in 
_ensure_rev2
v = _look_for_usrp(which)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp.py", line 74, in 
_look_for_usrp
d = usrp_prims.usrp_find_device(which)
NotImplementedError: Wrong number of arguments for overloaded function 
'usrp_find_device'.
  Possible C/C++ prototypes are:
usrp_find_device(int,bool)
usrp_find_device(int)


On Monday 01 January 2007 09:00, Josh Blum wrote:
> I have been working on a graphical interface for gnu radio. I was
> wondering if there are any gnu radio enthusiasts willing to check out my
> program and give me some feed back. I call it gnu radio companion or
> GRC. Here is the link http://www.joshknows.com/?key=grc
>
> Thanks,
> -Josh
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Problem with DBSRX rev 2.1: "No class defined to handle daughterboard (dbid = 13)"

2006-12-27 Thread Pawel Koszut
It works ok now, thanks Matt.

I burned eeprom because earlier I got a message "Invalid EEPROM contents"
It seems now that it wasn't necessary.

Pawel


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Problem with DBSRX rev 2.1: "No class defined to handle daughterboard (dbid = 13)"

2006-12-26 Thread Pawel Koszut
I have DBSRX rev 2.1, 
after burning eeprom with the command ./burn-db-eeprom -t dbsrx2 -A -f
an error appears when I try to use the daughterboard
"ValueError: No class defined to handle daughterboard (dbid = 13)"

Similar problem was addressed in
http://www.nabble.com/Problem-with-RFX1800:-"No-class-defined-to-handle-daughterboard"-t2068897.html
but in my case rebuilding with the latest version didn't solve the problem.

Any suggestions ? Below is detailed listing of the output.

Regards,
Pawel

=
[EMAIL PROTECTED]:/home/pawel/gnuradio/gnuradio-examples/python/usrp# 
./usrp_oscope.py -R A
Traceback (most recent call last):
  File "./usrp_oscope.py", line 252, in ?
main ()
  File "./usrp_oscope.py", line 248, in main
app = stdgui.stdapp(app_flow_graph, "USRP O'scope", nstatus=1)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/wxgui/stdgui.py", line 
36, in __init__
wx.App.__init__ (self, redirect=False)
  File "/usr/lib/python2.4/site-packages/wx-2.6-gtk2-unicode/wx/_core.py", line 
7700, in __init__
self._BootstrapApp()
  File "/usr/lib/python2.4/site-packages/wx-2.6-gtk2-unicode/wx/_core.py", line 
7352, in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/wxgui/stdgui.py", line 
39, in OnInit
frame = stdframe (self.flow_graph_maker, self.title, self._nstatus)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/wxgui/stdgui.py", line 
60, in __init__
self.panel = stdpanel (self, self, flow_graph_maker)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/wxgui/stdgui.py", line 
81, in __init__
self.fg = flow_graph_maker (frame, self, vbox, sys.argv)
  File "./usrp_oscope.py", line 82, in __init__
self.u = usrp.source_c(decim_rate=options.decim)
  File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp.py", line 250, in 
__init__
self.db = (db_instantiator.instantiate(self._u, 0),
  File "/usr/local/lib/python2.4/site-packages/gnuradio/db_instantiator.py", 
line 31, in instantiate
raise ValueError, "No class defined to handle daughterboard (dbid = %d)" % 
(dbid,)
ValueError: No class defined to handle daughterboard (dbid = 13)
=


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio