# Gr\_correlate\_access\_code\_bb question

**URL:** <https://www.ruby-forum.com/t/gr-correlate-access-code-bb-question/103126>\
**Category:** GNU Radio\
**Created:** [May 2, 2007, 3:39am UTC](https://www.ruby-forum.com/t/gr-correlate-access-code-bb-question/103126 "2007-05-02T03:39:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danhobbs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a5b964/32.png) [@danhobbs](https://www.ruby-forum.com/u/danhobbs)\
**Post date:** [May 2, 2007, 3:39am UTC](https://www.ruby-forum.com/t/gr-correlate-access-code-bb-question/103126/1 "2007-05-02T03:39:21Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

Hey all,

Sorry to bring up painful memories :). I did some calculations to work  
out frequency drift of the USRPs, and I wanted to know where I’m going  
wrong.

The crystals in the RFX 2400 are spec’ed at 50ppm error, which is to say  
that the maximum frequency offset between the sender and receiver is  
then 2 \* 50 ppm \* 2.462 GHz (802.11b Channel 11) = 246.2 kHz.

246.2 kHz sampled at 64 MHz is 246.2 kHz \* 2pi / 64 MHz which is  
approximately 0.02417 radians / sample.

At, say, DBPSK 250kbps, oversampled by a factor of 2, that means we  
decimate by 128 (500 ksamples per second), to then get at most ~3.094  
radians per sample drift.

With DBPSK this could flip all of our bits! Does that mean we in fact do  
need to worry about the case where the complement of the access code is  
detected? Is my understanding of the meaning of ppm error wrong? Does  
the distribution we assume for the frequency offset make this  
possibility negligible?

Thanks!

- -Dan  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.3 (GNU/Linux)  
Comment: Using GnuPG with Mozilla - [http://enigmail.mozdev.org](http://enigmail.mozdev.org)

iD8DBQFGN+uOy9GYuuMoUJ4RAoGqAKDQEPs1o5BtCEsfMo4PLm9zLh09CwCeIi/8  
9wr0qg+XJ2dexNuIRPr0tgw=  
=8wIA  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![danhobbs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a5b964/32.png) [@danhobbs](https://www.ruby-forum.com/u/danhobbs)\
**Post date:** [May 2, 2007, 4:21am UTC](https://www.ruby-forum.com/t/gr-correlate-access-code-bb-question/103126/2 "2007-05-02T04:21:24Z")

</div>

On 5/1/07, Dan H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> that the maximum frequency offset between the sender and receiver is  
> then 2 \* 50 ppm \* 2.462 GHz (802.11b Channel 11) = 246.2 kHz.

I think 50ppm is a total drift of the 64MHz oscillator, so no +/- just  
50ppm being the max deviation between two crystals.

Brian

---

<div class="post-metadata">

**Author:** ![danhobbs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a5b964/32.png) [@danhobbs](https://www.ruby-forum.com/u/danhobbs)\
**Post date:** [May 2, 2007, 4:29am UTC](https://www.ruby-forum.com/t/gr-correlate-access-code-bb-question/103126/3 "2007-05-02T04:29:24Z")

</div>

Dan H. wrote:

> that the maximum frequency offset between the sender and receiver is  
> need to worry about the case where the complement of the access code is  
> detected? Is my understanding of the meaning of ppm error wrong? Does  
> the distribution we assume for the frequency offset make this  
> possibility negligible?

No it means you have to estimate the carrier frequency offset and remove  
it, even in DBPSK. You do this by using the access code to find the  
frequency offset and the differentially detect it.

> Thanks!
> 
> - -Dan

Bob

–  
AMSAT Director and VP Engineering. Member: ARRL, AMSAT-DL,  
TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. ARRL SDR WG Chair  
“If you’re going to be crazy, you have to get paid for it or  
else you’re going to be locked up.” Hunter S. Thompson
