[Discuss-gnuradio] RE: Discuss-gnuradio Digest, Vol 31, Issue 1

[Ravichandran_Shivakumar]

Hi Eric,
        Thanks for your reply.As you said I have gone through the
document which you have told and created my own class.Now I need to put
this on USRP board.We need to know where exactly we must put these codes
into to the board???.is it on the EEPROm or how will the CPU and the
board co-ordinate each other to this????

Any one Pl add on to this.

Regards
Ravi

-----Original Message-----
From:
address@hidden
[mailto:address@hidden
org] On Behalf Of address@hidden
Sent: Thursday, June 02, 2005 4:13 AM
To: address@hidden
Subject: Discuss-gnuradio Digest, Vol 31, Issue 1

Send Discuss-gnuradio mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."


Today's Topics:

   1. RE: Discuss-gnuradio Digest, Vol 30, Issue 27
      (Ravichandran_Shivakumar)
   2. Re: Repeat: Mac? (Oskar Lissheim-Boethius)
   3. Re: RE: Discuss-gnuradio Digest, Vol 30, Issue 27 (Eric Blossom)
   4. accuracy problem? (David P. Reed)
   5. Re: accuracy problem? (Eric Blossom)
   6. Re: accuracy problem? (Matt Ettus)
   7. gui for HF sideband listening - HF Explorer (cswiger)
   8. Digital Communication using GNU Radio. (Sachi)


----------------------------------------------------------------------

Message: 1
Date: Wed, 1 Jun 2005 09:25:41 +0530
From: "Ravichandran_Shivakumar" <address@hidden>
Subject: [Discuss-gnuradio] RE: Discuss-gnuradio Digest, Vol 30, Issue
        27
To: <address@hidden>
Message-ID:
        
<address@hidden>
Content-Type: text/plain;       charset="us-ascii"

Hi ,
        I am using GNU radio for the first time.can anyone tell me where
or how exactly should I plug in my code after I have defined some
classes of my own???.
I am planning do it using separate receiving and transmitting section
and plug it in separately.

Any one help me on this Pl.....

Regards
Ravi



DISCLAIMER:
This email (including any attachments) is intended for the sole use of
the intended recipient/s and may contain material that is CONFIDENTIAL
AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or
copying or distribution or forwarding of any or all of the contents in
this message is STRICTLY PROHIBITED. If you are not the intended
recipient, please contact the sender by email and delete all copies;
your cooperation in this regard is appreciated.






------------------------------

Message: 2
Date: Wed, 1 Jun 2005 17:28:33 +0200
From: Oskar Lissheim-Boethius <address@hidden>
Subject: Re: [Discuss-gnuradio] Repeat: Mac?
To: Jonathan Jacky <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

On 1 jun 2005, at 00.08, Jonathan Jacky wrote:

>
> On Mon, 30 May 2005, Oskar Lissheim-Boethius wrote:
>
>
>> Any news on Mac OS X compatibility yet?
>>
>
> I've got gnuradio-core from CVS running on Mac OS X 10.3.8 "Panther".
> However there were some unobvious steps in the build procedure that  
> I got to work.  I believe what I did was unnecessarily  
> complicated.  I plan to post instructions for a simplified  
> procedure after I confirm that it works.
>
> I'm working on gr-wxgui.  I've got a tweaked version (not the CVS  
> version) of scopesink.py working.  See the following long message  
> to discuss-gnuradio.
>
> I haven't yet started on any audio or USRP.
>
> Jon Jacky

Sounds great. Keep us updated on the progress. I'm on Tiger now, so  
it might be even more unobvious steps to get it running here. Sorry I  
can't help you with the work, I'm not much of a programmer ;)



Yours sincerely,

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
O S K A R   L I S S H E I M  -  B O E T H I U S
 >    Composer & Designer
 >    Avocade Creations
 >    Home: www.avocade.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20050601/c15
70d6b/attachment.html

------------------------------

Message: 3
Date: Wed, 1 Jun 2005 10:10:51 -0700
From: Eric Blossom <address@hidden>
Subject: Re: [Discuss-gnuradio] RE: Discuss-gnuradio Digest, Vol 30,
        Issue 27
To: Ravichandran_Shivakumar <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

On Wed, Jun 01, 2005 at 09:25:41AM +0530, Ravichandran_Shivakumar wrote:
> Hi ,
>       I am using GNU radio for the first time.can anyone tell me where
> or how exactly should I plug in my code after I have defined some
> classes of my own???.
> I am planning do it using separate receiving and transmitting section
> and plug it in separately.
> 
> Any one help me on this Pl.....
> 
> Regards
> Ravi

Hi Ravi,

The best way is to follow the suggestions in 
http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html
It has you build your new blocks outside of the main gnu radio code
base.  

Eric




------------------------------

Message: 4
Date: Wed, 01 Jun 2005 16:12:16 -0400
From: "David P. Reed" <address@hidden>
Subject: [Discuss-gnuradio] accuracy problem?
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I'm trying to install the gnuradio software from CVS on Fedora Core 3 on

an AMD64 (x86_64) laptop (and python 2.3).   Aside from annoying 
pathname bugs and quirks with FFTW linking, which I will report 
separately, I get the following error when testing gnuradio-core, where 
a unittest fails.   Anyone who has a clue why this imprecision might be 
happening?  If I change this one test to check for 5 digits after the 
decimal point, it works...

Also, has anyone gotten gnuradio to run on x86_64?

======================================================================
FAIL: test_complex_to_arg (__main__.test_complex_ops)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./qa_complex_to_xxx.py", line 111, in test_complex_to_arg
    self.assertFloatTuplesAlmostEqual (expected_result, actual_result,
6)
  File 
"/gnuradio/gr-build/gnuradio-core/src/python/gnuradio/gr_unittest.py", 
line 55, in assertFloatTuplesAlmostEqual
    self.assertAlmostEqual (a[i], b[i], places, msg)
  File "/usr/lib64/python2.3/unittest.py", line 322, in 
failUnlessAlmostEqual
    raise self.failureException, \
AssertionError: 2.3561944901923448 != 2.3561935424804688 within 6 places






------------------------------

Message: 5
Date: Wed, 1 Jun 2005 13:46:03 -0700
From: Eric Blossom <address@hidden>
Subject: Re: [Discuss-gnuradio] accuracy problem?
To: "David P. Reed" <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

On Wed, Jun 01, 2005 at 04:12:16PM -0400, David P. Reed wrote:
> I'm trying to install the gnuradio software from CVS on Fedora Core 3
on 
> an AMD64 (x86_64) laptop (and python 2.3).   Aside from annoying 
> pathname bugs and quirks with FFTW linking, which I will report 
> separately, I get the following error when testing gnuradio-core,
where 
> a unittest fails.   Anyone who has a clue why this imprecision might
be 
> happening?  If I change this one test to check for 5 digits after the 
> decimal point, it works...
> 
> Also, has anyone gotten gnuradio to run on x86_64?

Hi David,

Some folks have GNU Radio running on x86_64.  I just took delivery on
one the other day, but haven't had a chance to spend any time with it.

I think the difference you're seeing is that GCC for the x86_64 uses
the SSE scalar mode instructions at 32-bits instead of the x87
instructions with 80-bits of precision.

Eric




------------------------------

Message: 6
Date: Wed, 01 Jun 2005 13:39:04 -0700
From: Matt Ettus <address@hidden>
Subject: Re: [Discuss-gnuradio] accuracy problem?
To: "David P. Reed" <address@hidden>
Cc: discuss gnuradio <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1

David P. Reed wrote:
> I'm trying to install the gnuradio software from CVS on Fedora Core 3
on
> an AMD64 (x86_64) laptop (and python 2.3).   Aside from annoying
> pathname bugs and quirks with FFTW linking, which I will report
> separately, I get the following error when testing gnuradio-core,
where
> a unittest fails.   Anyone who has a clue why this imprecision might
be
> happening?  If I change this one test to check for 5 digits after the
> decimal point, it works...
> 
> Also, has anyone gotten gnuradio to run on x86_64?

You can ignore this test.  Every architecture seems to return slightly
different results.

Matt




------------------------------

Message: 7
Date: Wed, 1 Jun 2005 17:35:48 -0400 (EDT)
From: cswiger <address@hidden>
Subject: [Discuss-gnuradio] gui for HF sideband listening - HF
        Explorer
To: discuss gnuradio <address@hidden>
Message-ID: <address@hidden>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Gang - Here's a fully working gui for my weaver code, with all the
features I wanted and support for the Powermate knob. Features

* AGC
* Demods both upper and lower sideband at the same time, allowing
  independant sideband listening (one in each ear, stereo), or mono
  LSB or USB.
* Audio filters from 600 to 3600hz
* frequency, volume and filter sliders operate by either the mouse
  or Powermate knob
* Function adjusted by the Powermate selectable by pressing the knob or
  clicking on buttons. You can use the slider to quickly make large
  changes in frequency then use the knob for fine tuning in 100hz steps
* Supports fast fwd and rewind when playing from a file, by either
  clicking on buttons for large delta-T or using the knob for smaller
  time steps
* Menubar
* Statusbar with freq, vol and filter
* gui laid out with wxGlade and the *.wxg files are available for
further
  editing

Future plans include AM (coming very soon), live usrp support with band
selection, record audio to file, selectable tuning steps, agc signal
strength meter, etc.

http://webpages.charter.net/cswiger/hfx/

Right now it's tailored to crusing around an 80meter band datafile I
made earlier but will be making it more general and, with the
appropriate
front end hardware, give Kenwood & company a run for their money.

--Chuck





------------------------------

Message: 8
Date: Wed, 1 Jun 2005 15:40:52 -0700 (PDT)
From: Sachi <address@hidden>
Subject: [Discuss-gnuradio] Digital Communication using GNU Radio.
To: discuss gnuradio <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=iso-8859-1

Hi all friends

I plan to use GNU Radio to develop some digital
modulation and demodulation schemes. Could anyone of
you guys tell me what kinds of digital modulation and
demodulation schemes have been implemented in our
group and where I can find the code?

I've noticed there is fsk transmission and receiving
codes in the example folder. But my experiments don't
go well. I simply use an amplifier as the front end
(no frequency trans) and I sent a file via the Tx and
try to receive the signal using another laptop with
usrp board. But I can receive nothing but some weired
characters. Can anyone of you help me with it? What's
the correct way to run this FSK code?

Thanks so much in advance

Sachi


                
__________________________________ 
Discover Yahoo! 
Use Yahoo! to plan a weekend, have fun online and more. Check it out! 
http://discover.yahoo.com/




------------------------------

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


End of Discuss-gnuradio Digest, Vol 31, Issue 1
***********************************************



DISCLAIMER:
This email (including any attachments) is intended for the sole use of the 
intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE 
COMPANY INFORMATION. Any review or reliance by others or copying or 
distribution or forwarding of any or all of the contents in this message is 
STRICTLY PROHIBITED. If you are not the intended recipient, please contact the 
sender by email and delete all copies; your cooperation in this regard is 
appreciated.