Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Marcus D. Leech
On 17/06/12 11:59 PM, Vikas N Kumar wrote: > > Got it to work. Changed the ~/.gnuradio/config.conf to use "nongl" for > wxgui and then commented out the set_callback() calls and the UI came > up. Now need to make sure that the software really works as expected > with those changes. > > > The wat

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Vikas N Kumar
On Sun, Jun 17, 2012 at 11:59 PM, Marcus D. Leech wrote: > Different X drivers?   Are you on a VM, or physical machine? Physical machine with NVIDIA 270.xx drivers using a GTX 550i card. Could just be the NVIDIA drivers ! ___ Discuss-gnuradio mailing l

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Vikas N Kumar
On Sun, Jun 17, 2012 at 11:56 PM, Vikas N Kumar wrote: > On Sun, Jun 17, 2012 at 11:50 PM, Marcus D. Leech wrote: >>> >>> >> The X window system error is likely due to some subtlety in OpenGL which >> has nothing directly to do with >>  Gnu Radio or Multimode. >> > > So any idea how to get around

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Marcus D. Leech
On 17/06/12 11:56 PM, Vikas N Kumar wrote: > On Sun, Jun 17, 2012 at 11:50 PM, Marcus D. Leech wrote: > >>> >>> >> The X window system error is likely due to some subtlety in OpenGL which >> has nothing directly to do with >> Gnu Radio or Multimode. >> >> > So any idea how to get a

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Vikas N Kumar
On Sun, Jun 17, 2012 at 11:50 PM, Marcus D. Leech wrote: >> >> > The X window system error is likely due to some subtlety in OpenGL which > has nothing directly to do with >  Gnu Radio or Multimode. > So any idea how to get around this ? ___ Discuss-gn

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Marcus D. Leech
On 17/06/12 11:46 PM, Vikas N Kumar wrote: > On Sun, Jun 17, 2012 at 11:16 PM, Marcus D. Leech wrote: > \\> This is almost certainly caused by having a version of Gnu Radio that > >> isn't up-to-date. Are you sure you're >> running the version you think you're running? The GIT master of Gnu

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Vikas N Kumar
On Sun, Jun 17, 2012 at 11:16 PM, Marcus D. Leech wrote: \\> This is almost certainly caused by having a version of Gnu Radio that > isn't up-to-date.  Are you sure you're >  running the version you think you're running?  The GIT master of Gnu > Radio has support for the >  'set_callback' function

Re: [Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Marcus D. Leech
On 17/06/12 11:09 PM, Vikas N Kumar wrote: > Hi > > I am using the ezcap RTL2838U USB dongle along with gnuradio 3.6.0 and > the svn latest version of Multimode.py on Debian Linux 6.0.2. I have > installed the HEAD git branches of rtl-sdr, gr-osmosdr and libosmocore > successfully. I have taken car

[Discuss-gnuradio] Multimode.py giving error with gnuradio 3.6.0

2012-06-17 Thread Vikas N Kumar
Hi I am using the ezcap RTL2838U USB dongle along with gnuradio 3.6.0 and the svn latest version of Multimode.py on Debian Linux 6.0.2. I have installed the HEAD git branches of rtl-sdr, gr-osmosdr and libosmocore successfully. I have taken care of all pre-requisites needed as well as in the build

Re: [Discuss-gnuradio] if uhd_transmitter instantiated after receiver, TX works, otherwise RX works

2012-06-17 Thread George Nychis
A little more information about this... The UHD version is 003.004.000-322fb97. Daughterboard: xcvr2450 usrp: n200 Interestingly, what seems to break things is the call to set_freq(). If I comment out the set_freq() in the instantiation of the receiver, the transmitter will work. If I comment i

Re: [Discuss-gnuradio] gnuradio transmission delay

2012-06-17 Thread Rick Graham
On Wed, Jun 13, 2012 at 8:15 PM, Phelps Williams wrote: > I have a simple bpsk transmitter setup with a custom udp source block > which outputs a fixed pattern if no data is available from the socket. > I have instrumented the block to indicate when data is read from the > socket inside of work(

Re: [Discuss-gnuradio] Questions

2012-06-17 Thread Josh Blum
On 06/17/2012 08:25 AM, Amr Youssef wrote: > Hi all , i have some questions : > > In " ./gr-digital/python/ofdm_packet_utils.py " file : > > 1- in pkt_dt = ' ' . join ((payload_with_crc ,'\x55')) > What is '\x55' representing to , i found it "U" in ASCII . Why U > specifically ? and

[Discuss-gnuradio] Questions

2012-06-17 Thread Amr Youssef
Hi all , i have some questions : In " ./gr-digital/python/ofdm_packet_utils.py " file : 1- in pkt_dt = ' ' . join ((payload_with_crc ,'\x55')) What is '\x55' representing to , i found it "U" in ASCII . Why U specifically ? and why we concatenate it with payload_with_crc ? 2- How

Re: [Discuss-gnuradio] RuntimeError: Failed to open rtlsdr device - some success

2012-06-17 Thread Phil
On 17/06/12 19:20, Alex DEKKER wrote: On 17/06/12 02:38, Phil wrote: By "reload udev" do you mean restart udevd? To be precise, reloading a service [usually] results in it re-reading its config without restarting it. Restarting it, stops it and starts it. Restarting udev will achieve the sam

Re: [Discuss-gnuradio] RuntimeError: Failed to open rtlsdr device - some success

2012-06-17 Thread Alex DEKKER
On 17/06/12 02:38, Phil wrote: By "reload udev" do you mean restart udevd? To be precise, reloading a service [usually] results in it re-reading its config without restarting it. Restarting it, stops it and starts it. Restarting udev will achieve the same end result in this case as reloadi

Re: [Discuss-gnuradio] gnuradio transmission delay

2012-06-17 Thread Rick Graham
On Thu, Jun 14, 2012 at 5:15 PM, Phelps Williams wrote: > I am not throttling the amount of data generated by my custom udp > source. I am generating enough output to match noutput_items passed > as the first argument to work(). My understanding is that > noutput_items is the number of bytes th