Hello,
I got complex samples from the usrp2 from usrp2.source32fc. Is there a
gnu radio class to extract the time stamp from the data coming in from
the usrp2? I read on archive that the timestamp is included in the
Ethernet frame but I don't see any help on how to extract it. Has anyone
attempt
Pham,
Thanh
Sent: Tue 3/10/2009 3:51 PM
To: Discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] extract timestamp data
Hello,
I got complex samples from the usrp2 from usrp2.source32fc. Is there a
gnu radio class to extract the time stamp from the data coming in from
the usrp2? I read on archive
Cocuzzo, Daniel C. wrote:
I'm also wondering about how to extract ethernet packet information,
such as timestamp. If anyone has any pointers to reference materials
it would be greatly appreciated.
Hi,
As far as I know, there is a timestamp- field in the ethernet- packet
header. Look in "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cocuzzo, Daniel C. wrote:
> I'm also wondering about how to extract ethernet packet information,
> such as timestamp. If anyone has any pointers to reference materials it
> would be greatly appreciated.
>
> Thanks,
> Dan
>
>
The easiest way (depen
I was contemplating trying to use the timestamps and 4 antennas on the
same usrp{1,2} to try and create a smart antenna array for DOA...
Dimitris Symeonidis
"If you think you're too small to make a difference, try sleeping with
a mosquito!" - Amnesty International
On Thu, Mar 12, 2009 at 15:51,
ubject: Re: [Discuss-gnuradio] extract timestamp data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cocuzzo, Daniel C. wrote:
> I'm also wondering about how to extract ethernet packet information,
> such as timestamp. If anyone has any pointers to reference materials it
> woul
On Thu, Mar 12, 2009 at 09:51:18AM -0500, Douglas Geiger wrote:
> Cocuzzo, Daniel C. wrote:
> > I'm also wondering about how to extract ethernet packet information,
> > such as timestamp. If anyone has any pointers to reference materials it
> > would be greatly appreciated.
> >
> > Thanks,
> > Dan
On Tue, Mar 10, 2009 at 01:51:15PM -0600, Pham, Thanh wrote:
> Hello,
>
> I got complex samples from the usrp2 from usrp2.source32fc. Is there a
> gnu radio class to extract the time stamp from the data coming in from
> the usrp2? I read on archive that the timestamp is included in the
> Etherne
On Fri, Mar 13, 2009 at 7:53 AM, Eric Blossom wrote:
> Thus we will have a common base class for all blocks, and blocks may
> have input and output streams (like they do now) or the ability to
> send and receive messages, or both.
Just to amplify on this, this "message passing" addition to gr-bl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The details on all of this still need to be flushed out, but this is
> the basic idea.
>
> To all:
>
> * Do you think that this would allow you to easily build MACs or other
> packet based things in GNU Radio? Assume the USRP and USRP2 block
Blossom
Subject: Re: [Discuss-gnuradio] extract timestamp data / "The Plan"
To: "Pham, Thanh"
Cc: Discuss-gnuradio@gnu.org
Date: Friday, March 13, 2009, 7:53 AM
On Tue, Mar 10, 2009 at 01:51:15PM -0600, Pham, Thanh wrote:
> Hello,
>
> I got complex samples from th
Exciting! With a new message passing capability, we will have to rethink
the packet and ofdm mod stuff in blks2. It wouldnt be to hard to modify
GRC to have blocks with "message passing" inputs and outputs.
!!
-Josh
Johnathan Corgan wrote:
On Fri, Mar 13, 2009 at 7:53 AM, Eric Blossom wrote:
On Fri, Mar 13, 2009 at 11:25:17AM -0500, Douglas Geiger wrote:
> > The details on all of this still need to be flushed out, but this is
> > the basic idea.
> >
> > To all:
> >
> > * Do you think that this would allow you to easily build MACs or other
> > packet based things in GNU Radio?
On Fri, Mar 13, 2009 at 11:41:22AM -0700, Dustin Torres wrote:
> Eric,
> Yes I believe this would tremendously facilitate MAC development
> within GNU Radio. I have recently begun working on integrating a
> configurable MAC layer to be used with GNU Radio and a USRP board.
Thanks.
> I am using t
On Fri, Mar 13, 2009 at 07:53:26AM -0700, Eric Blossom wrote:
> There are two distinct but related features:
>
> The first is designed to uniformly allow blocks to have a "packet
> based" or "message passing" interface, similar to what we attempted
> with the "message block" (m-block) code. We ha
On Sat, Mar 14, 2009 at 01:37:21PM +0100, Martin Braun wrote:
> On Fri, Mar 13, 2009 at 07:53:26AM -0700, Eric Blossom wrote:
> > There are two distinct but related features:
> >
> > The first is designed to uniformly allow blocks to have a "packet
> > based" or "message passing" interface, simila
16 matches
Mail list logo
