oops program mail have sent my email without finishing it
I got ride of the droop in my low frequency square wave input by disabling
the automatic DC offset by doing the following:
self.u = usrp.source_c()# usrp is data source
self.u.set_dc_offset_cl_enable(0x0, 0xf)
On Fri, Nov 11, 2005 at 12:02:18PM -0500, [EMAIL PROTECTED] wrote:
> No I have not yet made that change. I have been trying to figure out how
> to use it. I don't understand the brief description
>
> /*!
>* \brief Enable/disable automatic DC offset removal control loop in FPGA
>*
>
TECTED]
Date: Fri, 11 Nov 2005 01:47:29 -0800
To: [EMAIL PROTECTED], discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Using USRP w/o Daughterboard's
On Thu, Nov 10, 2005 at 05:18:26PM -0700, Robitaille, Michael wrote:
> Thanks Eric, I got my direct interface to the USRP working an
On Thu, Nov 10, 2005 at 05:18:26PM -0700, Robitaille, Michael wrote:
> 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 th
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
On Tue, Nov 08, 2005 at 11:37:25AM -0700, Robitaille, Michael wrote:
> On Monday, November 07, 2005 10:31 PM Eric Blossom Wrote
>
> No I have not 'butch' in an EEPROM and I have done nothing that could have
> hosed the USRP. All I did is put two small leads on the mating connector to
> input a si
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 needs to see the eeprom on the
>> >> daughterboard
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 needs to see the eeprom on the
> >> daughterboard that I don't have and really don't need.
>
>
> On Sun, 6 Nov 2005
>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 that's been in CVS for quite a
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.
The code that's been in CVS for quite a while treats "no rx
daughterboard" as if there were a Basic Rx d
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
On Sat, Nov 05, 2005 at 05:50:17PM -0700, Robitaille, Michael wrote:
> 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.
>
> I did look at the AD9
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
On Fri, Nov 04, 2005 at 02:40:06PM -0700, Robitaille, Michael wrote:
> > > 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 Basi
On Fri, Nov 04, 2005 at 02:19:59PM -0700, Robitaille, Michael wrote:
> Eric's reply
>
> >From looking at the Basic RX board schematic, I can see what pins are being
> used from the high speed A/D and I have modified a connecter to input the
> signals on those pins. It would seem that I could make
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
> > 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
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
>
On Thu, Nov 03, 2005 at 11:40:42AM -0700, Robitaille, Michael wrote:
> 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 late
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
20 matches
Mail list logo
