Changes between Version 3 and Version 4 of GettingStarted
- Timestamp:
- 10/16/11 18:05:06 (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GettingStarted
v3 v4 9 9 10 10 {{{ 11 apt-get install build-essential libtool autoconf git-core pkg-config libfftw3-dev11 apt-get install build-essential libtool autoconf git-core pkg-config 12 12 }}} 13 13 … … 68 68 69 69 There are several possible targets depending on your hardware: 70 * u hd: For using any ettus hardware71 * u srp: To use the libusrp drivers for the USRP1 hardware72 * fcd p: To use the specific Fun Cube Dongle Pro drivers70 * usrp: To use the libusrp drivers for the USRP1 hardware (gnuradio has to be compiled with gr-usrp enabled) 71 * uhd: For using any ettus hardware (see [http://code.ettus.com/redmine/ettus/projects/uhd/wiki UHD Wiki] for build instructions) 72 * fcd: To use the specific Fun Cube Dongle Pro drivers ([https://github.com/csete/gr-fcd gr-fcd] has to be installed) 73 73 74 74 === Wireshark === … … 79 79 git clone git://git.osmocom.org/wireshark 80 80 cd wireshark 81 git checkout sylvain/gmr 81 82 ./autogen.sh 82 83 ./configure … … 91 92 92 93 You need to capture samples off the air and of course "there's an app for that". 93 For a first try the easier is to lookup a beam that match your geographic area by looking at Thuraya Beams and the associated map.94 For a first try the easier is to lookup a beam that match your geographic area by looking at Thuraya_Beams and the associated map. 94 95 95 96 Depending on the target hw you selected, options might vary. Example below is for the UHD version. You can lookup the available options using {{{gmr_multi_rx -h}}} . … … 105 106 * It can be pretty CPU intensive depending on the # of ARFCNs and how much they're spaced. 106 107 108 ==== [http://tetra.osmocom.org/trac/wiki/Funcube_Dongle FunCube Dongle] Build ==== 109 {{{ 110 ./gmr_multi_rx --gain 30 --gmr1-dl 941 942 943 111 }}} 112 113 * when receiving 3 consecutive channels, the middle channel will be distorted by the center peak caused by dc offset / iq imbalance 114 * when receiving 2 channels, each channel will have a small contribution of the center peak on the right or left side. 115 * best results may be achieved when receiving only one channel. 116 117 ==== Default USRP clock ==== 118 119 {{{ 120 ./gmr_multi_rx --gain 45 --gmr1-dl 941 942 943 121 }}} 122 123 Only 75% of the master output rate will be used on the usrp/uhd builds, because of insufficient attenuation of the fpga channelizer at filter edges. 124 125 ==== Modified USRP clocks ==== 126 127 * use --mcr to tell custom fpga frequency in Hz 128 129 {{{ 130 ./gmr_multi_rx --gain 45 --gmr1-dl 941 942 943 --mcr 52e6 131 }}} 132 133 * mcr of 59.904e6 Hz is gmr1-friendly, thus allowing to save on interpolation stage 134 135 {{{ 136 ./gmr_multi_rx --gain 45 --gmr1-dl 941 942 943 --mcr 59.904e6 137 }}} 138 107 139 === Analyzing them === 108 140 … … 112 144 * Run the {{{gmr_rx}}} compiled in the {{{src/}}} directory on the generated files: 113 145 * {{{gmr1_rx 4 /tmp/gmr1-dl-977-sps93600.cfile}}} 114 * View packets in wireshark 146 * View packets in wireshark using gmr1_bcch.* filters 115 147

