RE: [Discuss-gnuradio] Good Python Intro

Does anyone have some good intro to WX (beside the following)? http://wxpython.org/tutorial.php Thanks, Mike -Original Message- From: Matt Ettus [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 5:20 PM To: discuss gnuradio Subject: [Discuss-gnuradio] Good Python Intro A series

RE: [Discuss-gnuradio] gmsk2 - CRC and whitening

I will check out to see if I can find the GCC. The whitening was very easy to implement. Thanks, Mike -Original Message- From: Eric Blossom [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:58 PM To: [EMAIL PROTECTED] Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnurad

RE: [Discuss-gnuradio] gmsk2 - CRC and whitening

Thanks, Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:03 PM To: Eric Blossom Cc: [EMAIL PROTECTED]; discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gmsk2 - CRC and whitening The following is a link to CRC16 for the

RE: [Discuss-gnuradio] gmsk error

I am in the process of implementing the whitener and will most likely do CRC16. For integrity check, I originally implemented of you a parity bit (yes it's limited to detecting on one bit error but my data load was small - two byte). Thanks, Mike -Original Message- From: Robert McGwier

RE: [Discuss-gnuradio] Help using simple_framer and simple_correl ator

On Monday, November 28, 2005 12:36 PM Eric wrote > I guess the first question that comes to mind is "why modulate at > all"? Why not just send your digital data as on-off-keying across > your optical interconnect? The modulation is for frequency multiplexing. There are multiple transmitters and

Re: [Discuss-gnuradio] Help using simple_framer and simple_correl ator

Use of gmsk2 versus simple_framer & simple_correlator.   The project I am working on has the following characteristics: 1.   Remote telemetry using optical link.  For proof of concept need to measure temperature from multiple sensors (5 thermocouples).  The temperature is represented

[Discuss-gnuradio] Displaying the Magnitude on the scope

I now able to demodulate my signals and would like to view the magnitude of the output rather than the real/img.  I tried to use the gr.complex_to_mag() operation and feed it in the scope_sink_f but I get a blank scope screen.   u_mag = gr.complex_to_mag() self.connect(u_xlated, u_mag)

RE: [Discuss-gnuradio] Reducing the ADC sample rate

Oops, I posted without a subject This is an attempt at correcting it. Will look at your reply n4hy. Thanks, Mike -Original Message- From: n4hy [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 9:18 AM To: Robitaille, Michael Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss

[Discuss-gnuradio] (no subject)

  On Monday, November 14, 2005 5:59 PM McGwier [mailto:[EMAIL PROTECTED] wrote:   > I am attempting to understand what advantage you would gain by reducing > the sample rate.  The FPGA's only jobs are run an oscillator, mix, and > resample using special form filters.  Now that the ha

RE: [Discuss-gnuradio] Reducing the ADC sample rate

On Monday, November 14, 2005 4:30 PM, Eric Blossom [mailto:[EMAIL PROTECTED] To: [EMAIL PROTECTED] >On Mon, Nov 14, 2005 at 06:17:16PM -0500, [EMAIL PROTECTED] wrote: >> On Fri, 11 Nov 2005 11:42:18 -0800, Eric responded: >> >> I just saw that in the schematic that the AD9862 gets its clock dirr

RE: [Discuss-gnuradio] Reducing the ADC sample rate

Alfred reply is exactly why I would like to change the sample rate. I am operating at low frequency and would like to be able to look at the signal with a different resolution in the frequency domain (time span = 1/sampling rate, require ring more points in FFT to get resolution). In my career I

Re: [Discuss-gnuradio] DC component and daughter-boards

Matt,   I have not and I hope it was a Basic RX board not a TX.   Mike   ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

RE: [Discuss-gnuradio] Using USRP w/o Daughterboard's

Thanks Eric, I got my direct interface to the USRP working and the usrp_oscope.py and ursp_fft.py examples work. I am very glad that the software defaults to a Basix Rx DB configuration when it finds no DB. One item that I am trying to chase down is that when I input a square wave at low frequ

Re: [Discuss-gnuradio] DC component and daughter-boards

In the post: http://lists.gnu.org/archive/html/discuss-gnuradio/2005-04/msg00303.html Matt indicates that "Feed your signal to the + input, and send the reference voltage (Vdd/2, 1.65V, available on the board) to the -

RE: [Discuss-gnuradio] Using USRP w/o Daughterboard's

On Monday, November 07, 2005 10:31 PM Eric Blossom Wrote >On Mon, Nov 07, 2005 at 04:40:29PM -0700, Robitaille, Michael wrote: >> >On Sat, Nov 05, 2005 at 05:50:17PM -0700, Robitaille, Michael wrote: >> >> >> The problem is that the software

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

>On Sat, Nov 05, 2005 at 05:50:17PM -0700, Robitaille, Michael wrote: >> The problem is that the software needs to see the eeprom on the >> daughterboard that I don't have and really don't need. On Sun, 6 Nov 2005 08:54:21 -0800, Eric Blossom wrote: > The code

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

Eric, thanks for your answers they are very helpful My post >>I can't get to the web page to see if there is any in inventory. If there is I will. I finally broke down and placed an order for the Basix RX board Saturday. I hope you have some in stock. My post >> I did look at the AD

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

Eric wrote > Why do you think that code will need to be modified? If I get the Basic RX board I don't. I can't get to the web page to see if there is any in inventory. If there is I will. > You'll want to look at the AD9862 data sheet to work out the right interface between the 9862 a

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

John posted > Matt has posted how to get very low frequencies -- all the way to DC I found Matt's post on modifying the Basic RX DB for DC operation. Disregard my request for a reference. Mike ___ Discuss-gnuradio mailing list Discuss-gnur

Re: [Discuss-gnuradio] setgid directories / usb permissions

Re: [Discuss-gnuradio] setgid directories / usb permissions Javs wrote: > Me too. I created a new mount point at /proc/bus/usb with usbfs for a regular 'user'account and now I am able to talk > to the usrp with the very first command. > Ahh..such a relief ! Thanks for all your pointers

Re: [Discuss-gnuradio] setgid directories / usb permissions

Eric replied > Please remind me which distribution you're using. FC4? Yes, it's FC4. > Generally speaking, having to run as root reflects a permission problem on /proc/bus/usb/ and files below. Yes it is. I made a group ( I don't seem to have a usb group build in FC4) and change t

[Discuss-gnuradio] Re: debugging

Good fix, usrp_oscope.py no longer locks up. Thanks Eric and Lee. Mike ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

> > frequencies to get the data rate up some. Based on my current > > specification, none of the DB would be of much use so I am trying to > > use the USRP w/o daughterboard's. John's response > Don't. Use the Basic daughterboards. The main board itself has no useful connectors for hook

Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's

Eric's reply > The code that defines determine_rx_mux_value is in > >gr-usrp/src/usrp.py > > It's pretty short. Thanks, I found it late last night after sending the post. > You are going to need some kind of daughterboard to get access to the high-speed A/D and D/A inputs and >

[Discuss-gnuradio] Using USRP w/o Daughterboard's

The project I am working is for remote sensing via an optic link. For the proof of concept I am using ASK (ON/OFF Keying) modulation at low data rate and low carrier frequencies (500Hz to 2.0 KHz - Yep real low). At a later date it will be changed to different modulation technique and higher freq

Re: [Discuss-gnuradio] No module name gnuradio

Finally got GNU Radio compiled and working with the USRP so I am out of the wood for now. I installed it in the 'standard' location, unfortunately I could do that only as the root and I can only run GnuRadio as root. I can't even use 'sudo' to run usrp_oscope.py. Not sure if I should move

Re: [Discuss-gnuradio] No module name gnuradio

First I want to tank everyone for there inputs. Some background, I am installing it on FC4 per the instruction given at KD7LMO's. I am using FC4 because at my initial research, the KD7LMO's seemed the most detailed and mentioned that it was done on FC3. Linux is new to me, I have experience i

Re: [Discuss-gnuradio] No module name gnuradio

Getting closer, Thanks Lamar, I did not know that PYTHONPATH needed to be an environment variable. I am now getting different error message when running usrp_oscope.py [EMAIL PROTECTED] usrp]$ sudo ./usrp_oscope.py Traceback (most recent call last): File "./usrp_oscope.py", line 30,

[Discuss-gnuradio] No module name gnuradio

I still get the following error when I try and run the usrp_oscope.py Traceback (most recent call lost): File ".ursp_oscope.py", line 27, in ? From gnuradio import gr, gru Import Error: No module named gnuradio Beside correcting the P

[Discuss-gnuradio] No module name gnuradio

In response to my post (see attachment) Eric wrote: >> My original >> I still get the following error when I try to run usrp_oscope.py or >> wfm-rcv_gui.py. >> >> Traceback (most recent call lost): >> >> File ".ursp_oscope.py", line 27, in ? >> >>

[Discuss-gnuradio] No module name gnuradio

LRK wrote: I install the programs needed to build gnuradio as root, some of these being "ports" in FreeBSD and thus easy to install. A couple I have to do by hand. Then I do the CVS download into space owned by the user gr and build it there without sudo. There are a couple of things to fix

Re: [Discuss-gnuradio] (no subject)

[EMAIL PROTECTED] wrote: I removed the xerces stuff from the build and install scripts last month. You may want to download the scripts again: http://www.kd7lmo.net/ground_gnuradio_baseline.html Yes

[Discuss-gnuradio] (no subject)

>On Fri, 21 Oct 2005 14:26:23 -0700, Eric Blossom wrote: >>On Fri, Oct 21, 2005 at 03:09:21PM -0600, Robitaille, Michael wrote: >> Hello all and thanks for your. >> >> I finally got all the baseline and gnuradio software installed per >> KD7LMO.net with

[Discuss-gnuradio] Installatin of USRP - many question related to sudo maybe

Hello all and thanks for your. I finally got all the baseline and gnuradio software installed per KD7LMO.net with some modification and still some question, for instance: 1- In the install_baseline.sh there is the installation of xerces-c-src-2_6_0 but not in the baseline build

[Discuss-gnuradio] USRP connectors

Can someone let me know what the part number and manufacturer for the connectors that connect to the USRP are.  I am guessing that it’s a female connector since those on the USRP look like male connectors.  Also, where can I bye them.   A product that Ettus Research main consider add are

[Discuss-gnuradio] Undefined reference to gr_fxpt

Hello all,   I have been trying to get the Gnu Radio 2.5 core to compile under the Fedora 4 Core.   I have been following the instruction given at KD7lmo and with some work; I have gotten the baseline packages to work.  I am using the tarball files since our network will not allow me to d