[Discuss-gnuradio] NRZI decoding
Hi, I am trying to get a better understanding of different receiver blocks. In the ais-tools-gnuradio-1.0.2 (http://funwithelectronics.com/sdr/ais.php) source code (aisrcv-usrp.py), once symbols are mapped to bits after demodulation and symbol clock recovery the signal is sent to the following blocks: gr.diff_decoder_bb() and ais.invert10_bb() I suppose gr.diff_decoder_bb() is a differential decoder and ais.invert10_bb() only inverts bits (a 0 becomes a 1 and inversely). Am I wrong? I have done some documentation research on AIS and the signal is NRZI encoded before modulation. I don’t understand how these blocks perform NRZI decoding. Can someone please give me a brief explanation? Thanks, Irene -- View this message in context: http://www.nabble.com/NRZI-decoding-tp19389130p19389130.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Different input/output rate
I am trying to extract data from a Turbo Code signal. My block’s input is the signal with synchro sequences between frames. The block processes this input in order to drop FEC bytes and send only useful data on the ouput. The problem is I need a complete frame to process data correctly so any incomplete frame at the start or end of the capture is to be ignored. I don’t know how to handle this when implementing the forecast method. -- View this message in context: http://www.nabble.com/Different-input-output-rate-tp709242p18568232.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Different input/output rate
Eric Blossom wrote: > > On Fri, Jul 18, 2008 at 03:19:08PM -0700, irene159 wrote: >> >> Hi, >> >> I have the same problem. I have already taken a look at gr_simple_framer, >> but code seems slightly complicated. I would appreciate any >> explanations/comments on how to code different input and output rates. >> >> In the block I am coding the number of input items for an output item >> isn't >> constant. How can I handle this? >> >> Thanks, >> >> Irene > > All is revealed in: > > http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html > > Basically you subclass gr_block, provide forecast and general_work > methods, then call consume/consume_each at the tail end of your > general_work function. > > Eric > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > Thanks, I think I am starting to figure thinks out. When referring to gr_simple_framer (which I am using as an example), may you please help me understand the processing part (lines 76 to 89 in the .cc file)? So, we are adding a synchro sequence at the beginning of a frame of ‘payload_bytesize’ bytes. I suppose lines 79 to 87 in the while loop add the synchro sequence end the sequence number. Line 89 copies ‘payload_bytesize’ bytes of input data to output stream after de synchro sequence. But why write 0x55 ‘noutput_items’ bytes to ‘out’ ? -- View this message in context: http://www.nabble.com/Different-input-output-rate-tp709242p18564972.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Different input/output rate
Martin Dvh wrote: > > Hi Holger, >> The input of my signal block is a bytestream b. The output should >> also be a bytestream, but with a different number of outgoing items(not a >> multiple of b). >> In other words, after the transformation of the inputstream some >> extra-bytes >> have to be appended. >> For example: >> >> Input y Bytes ---> Output (y Bytes * x) + c ; where y and x are >> integers >> and c Overhead-Bytes: independent from input items >> >> The number of input items is not fixed. >> >> Is this possible or must the number of output items always be a multiple >> of the >> number of input items? > Yes, this is possible. > You have to extend from gr_block in stead of gr_sync_block. > You have to implement your own forecast block and call consume_all > yourself. > > Look at the gr_simple_framer block. It does just this. > (src/lib/general/gr_simple_framer.[cc,h,i)] > > Greetings, > Martin > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > Hi, I have the same problem. I have already taken a look at gr_simple_framer, but code seems slightly complicated. I would appreciate any explanations/comments on how to code different input and output rates. In the block I am coding the number of input items for an output item isn't constant. How can I handle this? Thanks, Irene -- View this message in context: http://www.nabble.com/Different-input-output-rate-tp709242p18538640.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Different input/output rate
Martin Dvh wrote: > > Hi Holger, >> The input of my signal block is a bytestream b. The output should >> also be a bytestream, but with a different number of outgoing items(not a >> multiple of b). >> In other words, after the transformation of the inputstream some >> extra-bytes >> have to be appended. >> For example: >> >> Input y Bytes ---> Output (y Bytes * x) + c ; where y and x are >> integers >> and c Overhead-Bytes: independent from input items >> >> The number of input items is not fixed. >> >> Is this possible or must the number of output items always be a multiple >> of the >> number of input items? > Yes, this is possible. > You have to extend from gr_block in stead of gr_sync_block. > You have to implement your own forecast block and call consume_all > yourself. > > Look at the gr_simple_framer block. It does just this. > (src/lib/general/gr_simple_framer.[cc,h,i)] > > Greetings, > Martin > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > Hi, I have the same problem. I have already taken a look at gr_simple_framer, but code seems slightly complicated. I would appreciate any explanations/comments on how to code different input and output rates. In the block I am coding the number of input items for an output item isn't constant. How can I handle this? Thanks, Irene -- View this message in context: http://www.nabble.com/Different-input-output-rate-tp709242p18538641.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Segmentation fault (core dump)
Hello, I have modified gr_constellation_decoder_cb.cc in order to have a second output stream (type float) sending back min_euclid_dist. http://www.nabble.com/file/p18313925/gr_constellation_decoder_cb.cc gr_constellation_decoder_cb.cc Please take a look and let me know if there are any errors, I am not sure of how to code two outputs with different data types. To update the code after this modification I have done a make and make install in the directory /usr/src/gnuradio/gnuradio-core/src/lib/general as well as in /usr/src/gnuradio/gnuradio-core/src/lib. I am now permanently receiving "Segmentation fault (core dump)" error message. Can somebody help me out ? Regards, Irene -- View this message in context: http://www.nabble.com/Segmentation-fault-%28core-dump%29-tp18313925p18313925.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re[Discuss-gnuradio] sampling precision
Hello, I run into some weird results on the rational_resampler.rational_resampler_ccf output. Look at picture 1 [1] bellow: Signal input : Carrier of 1,4 Mhz sampled at 640 Ksamp/s Interporlation resampler = 2 Decimation resampler = 3 Manual extract: fractional_bw: fractional bandwidth in (0, 0.5), measured at final freq (use 0.4) type fractional_bw: float Can someone give me more informations on the "rational_bw" parameter? Are there any files using resampling function that I can take a look at? [1] - http://www.nabble.com/file/p18280898/resampler.JPG resampler.JPG Regards, Irene -- View this message in context: http://www.nabble.com/Resampling-precision-tp18280898p18280898.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] two inputs/outputs of different data types
Hi,
I was just asking myself the same question but I'm not sure I understood
your answer.
Is it possible to have two output streams of different data types? I want
one to be unsignad char and the other one float or double. How is it to be
coded?
...: gr_sync_block (...,
gr_make_io_signature (1, 1, size_of (...))
gr_make_io_signature (1, 12, size_of (?)))
Regards,
Irene
Eric Blossom wrote:
>
> On Wed, Apr 26, 2006 at 11:50:39AM -0400, Chuck Swiger wrote:
>> How do you declare two inputs of different data types?
>>
>> Several atsc blocks pass a stream of 'float' and also 'syminfo'
>> (a struct of 4 ints).
>>
>> >From what I can tell, gr_sync_block allows many inputs and outputs,
>> but only of the same type(?).
>>
>> gr_block::gr_block (const std::string &name,
>> gr_io_signature_sptr input_signature,
>> gr_io_signature_sptr output_signature)
>>
>> where
>>
>> gr_io_signature (int min_streams, int max_streams, size_t
>> sizeof_stream_item)
>>
>> tia
>> --Chuck
>
> Hi Chuck,
>
> You're right. FWIW, the underlying representation is designed to
> support different types on each input or output stream, but the top
> level constructor, gr_io_signature, doesn't implement an interface to it.
>
> I'm pretty sure that sizeof(atsc::syminfo) is 4, which is the same as
> sizeof(float). This is true because the total width of the integer
> bit fields in atsc::syminfo is <= 32.
>
>
> Add
>
> assert(sizeof(float) == sizeof(atsc::syminfo));
>
> somewhere in work, and then cast away. We lose clarity in the i/o
> signature, but I'm pretty sure it'll work. [ It worked before ;) ]
>
>
> E.g.,
>
>int
>foo::work(...)
>{
> const float *in_sample = (const float *) input_items[0];
> const atsc::syminfo *in_tag = (const atsc::syminfo *) input_items[1];
>
> assert(sizeof(float) == sizeof(atsc::syminfo));
>
> ...
>}
>
> Eric
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
--
View this message in context:
http://www.nabble.com/two-inputs-outputs-of-different-data-types-tp4104088p18253966.html
Sent from the GnuRadio mailing list archive at Nabble.com.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Gr_mpsk_re ceiver_cc’s costas loop issue
Hello, I have recently been doing some tests, simulating QPSK-modulated transmissions and studying Costas loop performance. When doing this, I noticed a problem related to gr_mpsk_receiver_cc’s costas loop NCO frequency as I already mentioned in post [1]. I have created two test files: Testfile.py and Tesfile_modified.py. I have basically been working with Testfile.py but in order to better analyse output (in text file) I have created Testfile_modified.py where I have removed simple_framer and simple_correlator part which conditioned output (there is no output as long as simple_correlator doesn’t identify “a frame”). I have also slightly modified dqpsk.py file, gr_mpsk_receiver_cc.cc file (to print Costas loop NCO frequency for every iteration of the loop) and gr_simple_correlator.cc (just to space display). Please find terminal display in attached files: terminal_display_1, 2 and 3. I have configured different values of frequency_offset (channel_model block parameter). I have had no answer to my questions concerning this parameter in post [1] so I have taken this parameter to represent a slight deviation between theoretical transmission frequency and the real frequency at which the signal is sent (in Hz). “terminal_display” result files prove NCO’s frequency isn’t adapted to frequency_offset correction (even for small values of frequency deviation). [1] http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-td17605464.html http://www.nabble.com/file/p17757609/dqpsk.py dqpsk.py http://www.nabble.com/file/p17757609/gr_mpsk_receiver_cc.cc gr_mpsk_receiver_cc.cc http://www.nabble.com/file/p17757609/gr_simple_correlator.cc gr_simple_correlator.cc http://www.nabble.com/file/p17757609/terminal_display_1.txt terminal_display_1.txt http://www.nabble.com/file/p17757609/terminal_display_2.txt terminal_display_2.txt http://www.nabble.com/file/p17757609/terminal_display_3.txt terminal_display_3.txt http://www.nabble.com/file/p17757609/Testfile.py Testfile.py http://www.nabble.com/file/p17757609/Testfile_modified.py Testfile_modified.py -- View this message in context: http://www.nabble.com/Gr_mpsk_receiver_cc%E2%80%99s-costas-loop-issue-tp17757609p17757609.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Import issue
In my case, it works replacing "from gnuradio import blks2" by "from gnuradio.blks2impl import rational_resampler" but that doesn't explain why command line works from the terminal but not from the file... irene159 wrote: > > Hello, > > Concerning blks2 import (blks2.rational_resampler needed) > > "from gnuradio import blks2" works on python command line but not in > python file (ImportError: cannot import name blks2). > > Where can this come from? > > Regards, > Irene > > -- View this message in context: http://www.nabble.com/Import-issue-tp17688627p17695168.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Import issue
Hello, Concerning blks2 import (blks2.rational_resampler needed) "from gnuradio import blks2" works on python command line but not in python file (ImportError: cannot import name blks2). Where can this come from? Regards, Irene -- View this message in context: http://www.nabble.com/Import-issue-tp17688627p17688627.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
Hello again, Sorry, I am not familiar with GNU Radio and I just keep coming up with new questions... I am simulating a transmission using IF - Base Band frequency conversion and a channel_model block introducing noise and frequency offset. As I said I am particularly interested in the Costas loop performance. So first of all I would like to make sure frequency_offset parameter really stands up for a slight deviation between theoretical transmission frequency and the real frequency at which the signal is sent. What is the unit of this parameter? Hz? I would also like to have an idea of the approximative maximum frequency_offset value that can be corrected by the Costas loop. I am asking these questions because when looking closely at the Costas loop NCO frequency value I realized it is far from correcting configured frequency_offset and this even for small values. -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17650469.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
Thank you very much. You have been of great help! -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17648942.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re[Discuss-gnuradio] sampling
Hello, I am using blks2impl dqpsk modulator/demodulator. Since demodulator's "samples_per_symbol" value must be an integer >=2 and USRP samples at 64 Msamples/s with a 2^(n) possible decimation, I have to sample a 2100 kbps carrier (=1050 ksym/s). I found two blocks that may apparently be used for resampling: - rational_resampler() - rational_resampler_base_xxx() I am not sure of which one I should use. Does somebody know the difference between them? I've read that rational_resampler_xxx() is a high-level wrapper for gr.rational_resampler_base_xxx but I don't understand what it means. -- View this message in context: http://www.nabble.com/Resampling-tp17643534p17643534.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
OK, so far I have been able to call gr.mpsk_receiver_cc.freq() from dqpsk.py even if I haven't found were it is coded. print "NCO frequency : %f" % self.receiver.freq() My purpose is to study mpsk_receiver_cc Costas loop features and I would like to get Costas loop NCO frequency value for each circle in the loop. But how can I do this? -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17642800.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
By the way, in the "Simple Gnuradio User Manual v1.0" [1] p.110 appears sub function (11) gr.mpsk_receiver_cc.freq(). I haven't been able to find this function, does it really exist? I would like to have your opinion, is this document compliant to GNU Radio code? Regards, Irene [1] - http://www.ece.jhu.edu/~cooper/SWRadio/Simple-Gnuradio-User-Manual-v1.0.pdf -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17624979.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
Tom Rondeau wrote: > > Do "make install" from gnuradio-core/src/lib > > Tom > You got it! Thanks, Irene -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17623536.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Trace mpsk_receiver_cc()
George Nychis wrote: > > You need to do a make, and make install ... otherwise you don't add your > new modifications to the library and install the library for the python > code to access. > Hi, Thanks for giving me a hand. I tried "make" and "make install" in the /usr/src/gnuradio/gnuradio-core/src/lib/general/ directory and still nothing printed from the gr_mpsk_receiver_cc.cc file. There can be no mistake on the file: [EMAIL PROTECTED]:~# find / -name *mpsk_receiver* /usr/local/include/gnuradio/gr_mpsk_receiver_cc.h /usr/local/include/gnuradio/swig/gr_mpsk_receiver_cc.i /usr/include/gnuradio/gr_mpsk_receiver_cc.h /usr/include/gnuradio/swig/gr_mpsk_receiver_cc.i /usr/src/gnuradio/gnuradio-core/src/lib/general/.svn/text-base/gr_mpsk_receiver_cc.h.svn-base /usr/src/gnuradio/gnuradio-core/src/lib/general/.svn/text-base/gr_mpsk_receiver_cc.cc.svn-base /usr/src/gnuradio/gnuradio-core/src/lib/general/.svn/text-base/gr_mpsk_receiver_cc.i.svn-base /usr/src/gnuradio/gnuradio-core/src/lib/general/gr_mpsk_receiver_cc.i /usr/src/gnuradio/gnuradio-core/src/lib/general/.deps/gr_mpsk_receiver_cc.Plo /usr/src/gnuradio/gnuradio-core/src/lib/general/gr_mpsk_receiver_cc.lo /usr/src/gnuradio/gnuradio-core/src/lib/general/gr_mpsk_receiver_cc.cc /usr/src/gnuradio/gnuradio-core/src/lib/general/.libs/gr_mpsk_receiver_cc.o /usr/src/gnuradio/gnuradio-core/src/lib/general/gr_mpsk_receiver_cc.h [EMAIL PROTECTED]:~# Any clues? -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17618841.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Trace mpsk_receiver_cc()
Hello, I would like to study the implementation of Costas loop in gr.mpsk_receiver_cc. I need some additional information to be printed by this block. First of all can somebody tell me what code is executed when calling a block? Is it the constructor and the general_work function in .cc file? In my case, I have a test file calling dqpsk.dqpsk_demod. As can be seen in the dqpsk.py code, dqpsk_demod function uses a mpsk_receiver_cc block. I have added some printf commands almost everywhere in the mpsk_receiver_cc.cc code and got none of them printed on the terminal when executing my test file. Any hints on what is going on? I modified mpsk_receiver_cc.cc file I found in /usr/src/gnuradio/gnuradio-core/src/lib/general/. Regards, Irene -- View this message in context: http://www.nabble.com/Trace-mpsk_receiver_cc%28%29-tp17605464p17605464.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Simulate transmission
Hello, I would like to simulate a transmission in order to test the configuration of the receiver's Costas loop. I'd like to mix the modulated signal to IF, add some noise and convert back to baseband for demodulation. The frequency value configured for channel selection at reception is to be slightly different from the real frequency used. Do you think this model is representative? Here is how the simulation part is coded : # Transmission channel simulation (cc) # Mix to IF lo = gr.sig_source_c(sample_rate, gr.GR_SIN_WAVE, if_freq, 1.0, 0) mixer = gr.multiply_cc() fg.connect(lo, (mixer, 1)) # Take real part as transmit ctof = gr.complex_to_float() # Simulate noise in the channel noise = gr.noise_source_f(gr.GR_GAUSSIAN, noise_mag) air_noise = gr.add_ff() fg.connect(noise, (air_noise, 1)) # Mix to baseband / channel selection chan_taps = gr.firdes.low_pass(1.0, sample_rate, lp_cutoff, lp_tw, gr.firdes.WIN_HAMMING) chan_filter = gr.freq_xlating_fir_filter_fcf(1, chan_taps, if_freq, sample_rate) and it is connected as follows : fg.connect(..., objMod, mixer, ctof, air_noise, chan_filter, objDemod, ...) where objMod = dqpsk.dqpsk_mod() and objDemod = dqpsk.dqpsk_demod(). The code works without the transmission simulation part (fg.connect(..., objMod, objDemod, ...)). Once I implement the simulation, data received is corrupted. Is something wrong in the code? Regards, Irene -- View this message in context: http://www.nabble.com/Simulate-transmission-tp17517019p17517019.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
Steven Clark-2 wrote: > > hex 00 and 01 are not visible characters, which is why you aren't > seeing anything. Looking at the data, it looks like unpacked data (ie > only the bottom bit of each byte is being used). If you convert it > back to packed data, it may be you'll get your original message back. > GNURadio has a unpacked_to_packed block for this purpose. > Why does GNURadio dqpsk demodulator code use unpack_k_bits_bb instead of unpacked_to_packed_bb (since modulator uses packed_to_unpacked_bb)? What is it used for? Indeed, in my case it works much better replacing self.unpack = gr.unpack_k_bits_bb(self.bits_per_symbol()) by self.unpack = gr.unpacked_to_packed_bb(self.bits_per_symbol(), gr.GR_MSB_FIRST) in the dqpsk demodulator code. Thanks to WinHex I realised demodulated data is bit shifted (due to the filter). Implementing simple_framer and simple_correlator should solve this problem. I have tried using them but I get the following error: ValueError: source and destination data sizes are different: unpacked_to_packed_bb simple_correlator I am connecting my blocks as follows: Original text file > simple_framer > dqpsk modulator > Modulated.dat file Modulated.dat file > dqpsk demodulator > simple_correlator > Resultat.txt file. I've seen that the simple_correlator expects its input to be oversampled 8 times[1], I think the code honors this requirement : dqpsk_mod interp_fir_filter_ccf does oversampling and dqpsk.py samples_per_symbol value is 8. I haven't found information for simple_framer/simple_correlator inputs and outputs and have no idea where my "ValueError: source and destination data sizes are different" problem comes from. Any hints would be appreciated! Thank you for your help! Irene [1]http://www.nabble.com/Help-using-simple_framer-and-simple_correlator-td1515282.html#a1538068 -- View this message in context: http://www.nabble.com/Modulation-problem---tp17316660p17420699.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
Steven Clark-2 wrote: > > hex 00 and 01 are not visible characters, which is why you aren't > seeing anything. Looking at the data, it looks like unpacked data (ie > only the bottom bit of each byte is being used). If you convert it > back to packed data, it may be you'll get your original message back. > GNURadio has a unpacked_to_packed block for this purpose. > Why does GNURadio dqpsk demodulator code use unpack_k_bits_bb instead of unpacked_to_packed_bb (since modulator uses packed_to_unpacked_bb)? Indeed, it works much better replacing self.unpack = gr.unpack_k_bits_bb(self.bits_per_symbol()) by self.unpack = gr.unpacked_to_packed_bb(self.bits_per_symbol(), gr.GR_MSB_FIRST) in the dqpsk demodulator code. Demodulated data doen't look at all like original data but thanks to WinHex I realised that the problem comes from bit shifting due to the filter. How can I solve this? Would implementing simple_framer and simple_correlator work? I have tried using them but I always get the following error: ValueError: source and destination data sizes are different: x simple_correlator (I have tried several input blocks). I am trying to connect my original file to the simple_framer and then to the dqpsk modulator-demodulator. Then, I connect output to the simple_correlator and then to my Resultat.txt file. Is this OK? I've seen that the simple_correlator expects its input to be oversampled 8 times[1], but I don't know how I can do this... Could this be the solution? I haven't seen oversampling in the gmsk-test.py[2] example but I haven't been able to test either... Thank you for your help! Irene [1]http://www.nabble.com/Help-using-simple_framer-and-simple_correlator-td1515282.html#a1538068 [2]http://noether.uoregon.edu/~jl/gmsk/ -- View this message in context: http://www.nabble.com/Modulation-problem---tp17316660p17407191.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] QPSK modulation resampling
George Nychis wrote:
>
>
> irene159 wrote:
>>
>>>
>>> Hello,
>>>
>>> Just another question concerning the file "gr_mpsk_receiver_cc.cc".
>>>
>>> In the extract of code below, why are phase_error_detector_generic and
>>> decision_generic used for all BPSK, QPSK and other modulations?
>>> Have optimized algorithms for BPSK and QPSK already been implemented?
>>>
>>> // Select a phase detector and a decision maker for the modulation
>>> order
>>> switch(d_M) {
>>> case 2: // optimized algorithms for BPSK
>>>d_phase_error_detector =
>>> &gr_mpsk_receiver_cc::phase_error_detector_generic; //bpsk;
>>>d_decision = &gr_mpsk_receiver_cc::decision_generic; //bpsk;
>>>break;
>>>
>>> case 4: // optimized algorithms for QPSK
>>>d_phase_error_detector =
>>> &gr_mpsk_receiver_cc::phase_error_detector_generic; //qpsk;
>>>d_decision = &gr_mpsk_receiver_cc::decision_generic; //qpsk;
>>>break;
>>>
>>> default: // generic algorithms for any M (power of 2?) but not pretty
>>>d_phase_error_detector =
>>> &gr_mpsk_receiver_cc::phase_error_detector_generic;
>>>d_decision = &gr_mpsk_receiver_cc::decision_generic;
>>>break;
>>
>
> This is just a guess based on the block names... But given that the
> block names have "generic" in them, I'd guess they are generic enough
> to work with psk modulations given some configuration.
>
> - George
>
Well actually I do think phase_error_detector_generic and decision_generic
work for PSK modulations (such as BPSK and QPSK).
What I don’t understand is the use of the switch case block in the code (to
treat BPSK and QPSK separately from other modulations) as the code in all of
the cases considered is exactly the same. My first thought was that there
would be specific and more efficient functions for BPSK and QPSK but I only
see generic ones.
--
View this message in context:
http://www.nabble.com/Differential-QPSK-modulation-resampling-tp17276806p17357620.html
Sent from the GnuRadio mailing list archive at Nabble.com.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
Steven Clark-2 wrote:
>
> This is not surprising. It is likely that you are getting some initial
> garbage (non-standard-ascii characters) coming out, or that you have
> some bit errors.
>
> Don't open it in gedit. Try:
> python
> f = open('Resultat.txt')
> d = f.read()
> f.close()
> print(len(d))
> print(d)
> (or if d is really long, print(d[:50]))
>
When I tried this and
$ cat Resultat.txt
or even
$ less Resultat.txt
on the Terminal I didn't see anything at first but copying what seemed empty
into a file, I got:
[Discuss-gnuradio] Modulation problem ?
Hello, I am testing QPSK modulation. To do so, I have created a text file that I modulate and demodulate with blks2impl dqpsk.py. The problem is the resulting demodulated file, which I can not open: "Could not open the file Resultat.txt. gedit has not been able to detect the character coding. Please check that you are not trying to open a binary file. Select a character coding from the menu and try again." Help would be appreciated. Please find code files below. Regards, Irene http://www.nabble.com/file/p17316660/Modulation.py Modulation.py http://www.nabble.com/file/p17316660/Demodulation.py Demodulation.py -- View this message in context: http://www.nabble.com/Modulation-problem---tp17316660p17316660.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Differential QPSK modulation resampling
Hello,
Just another question concerning the file "gr_mpsk_receiver_cc.cc".
In the extract of code below, why are phase_error_detector_generic and
decision_generic used for all BPSK, QPSK and other modulations?
Have optimized algorithms for BPSK and QPSK already been implemented?
// Select a phase detector and a decision maker for the modulation order
switch(d_M) {
case 2: // optimized algorithms for BPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //bpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //bpsk;
break;
case 4: // optimized algorithms for QPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //qpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //qpsk;
break;
default: // generic algorithms for any M (power of 2?) but not pretty
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic;
d_decision = &gr_mpsk_receiver_cc::decision_generic;
break;
}
Regards,
Irene
--
View this message in context:
http://www.nabble.com/Differential-QPSK-modulation-resampling-tp17276806p17314530.html
Sent from the GnuRadio mailing list archive at Nabble.com.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Differential QPSK modulation details
Hello, I am using blks2impl dqpsk modulator/demodulator. Focusing on the qpsk demodulator: Since "samples_per_symbol" value must be an integer >=2 and USRP samples at 64 Msamples/s with a 2^(n) possible decimation, if I have a 2100 kbps carrier (=1050 ksym/s) : - How can I possibly obtain a correct "samples_per_symbol" value? - Do I need a resampler and if so, how should I use it? By the way, I might be wrong but I haven't seen were the Costas loop and time recovery are implemented in this file... Regards, Irene -- View this message in context: http://www.nabble.com/Differential-QPSK-modulation-details-tp17276806p17276806.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] 3rd order Costas Loop
Hello, I would like to know if a 3rd order Costas Loop is already available. I am specially interested in the capability of tracking a received waveform that experiences acceleration (rate of change in frequency) to solve Doppler shifts' issues. Thanks, Irene -- View this message in context: http://www.nabble.com/3rd-order-Costas-Loop-tp17233793p17233793.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] GNU Radio Companion execute error
Hello, I am also facing the “ImportError: cannot import name blks” problem. My OS is Ubuntu 7.10 and I am not sure what my gnuradio version is, I followed the wiki Ubuntu installing instructions [1] and installed gnuradio using: svn co http://gnuradio.org/svn/gnuradio/trunk gnuradio cd gnuradio ./bootstrap && ./configure && make && make chek && make install Josh Blum wrote: > > This is because the latest gnuradio trunk no longer has blks package. > You can run gnuradio 3.1.1 release with grc 0.69. Or, use the latest grc > trunk with the latest gnuradio trunk. > -Josh > I figured out this is the answer to my problem but I don’t know what I have to do to use the latest grc trunk (I am not really familiar with gnuradio yet). Regards, Irene [1] http://gnuradio.org/trac/wiki/UbuntuInstall -- View this message in context: http://www.nabble.com/GNU-Radio-Companion-execute-error-tp15606493p16851003.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNU Radio Companion execute error
Hello, I am also facing the “ImportError: cannot import name blks” problem. My OS is Ubuntu 7.10 and I am not sure what my gnuradio version is, I followed the wiki Ubuntu installing instructions [1] and installed gnuradio using: svn co http://gnuradio.org/svn/gnuradio/trunk gnuradio cd gnuradio ./bootstrap && ./configure && make && make chek && make install Josh Blum wrote: > > This is because the latest gnuradio trunk no longer has blks package. > You can run gnuradio 3.1.1 release with grc 0.69. Or, use the latest grc > trunk with the latest gnuradio trunk. > -Josh > I figured out this is the answer to my problem but I don’t know what I have to do to use the latest grc trunk (I am not really familiar with gnuradio yet). Regards, Irene [1] http://gnuradio.org/trac/wiki/UbuntuInstall -- View this message in context: http://www.nabble.com/GNU-Radio-Companion-execute-error-tp15606493p16850995.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ais-tools installation problem
> In the output of './configure --help' are there any options regarding > dll's? I think this line is what is fouling you up: > > > checking if package supports dlls... no > > hth, > > Jason. > No, I didn't see any option concerning dll, options available are: $ ./configure --help Usage: configure [options] [host] Options: [defaults in brackets after descriptions] Configuration: --cache-file=FILE cache test results in FILE --help print this message --no-create do not create output files --quiet, --silent do not print `checking...' messages --version print the version of autoconf that created configure Directory and file names: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [same as prefix] --bindir=DIRuser executables in DIR [EPREFIX/bin] --sbindir=DIR system admin executables in DIR [EPREFIX/sbin] --libexecdir=DIRprogram executables in DIR [EPREFIX/libexec] --datadir=DIR read-only architecture-independent data in DIR [PREFIX/share] --sysconfdir=DIRread-only single-machine data in DIR [PREFIX/etc] --sharedstatedir=DIRmodifiable architecture-independent data in DIR [PREFIX/com] --localstatedir=DIR modifiable single-machine data in DIR [PREFIX/var] --libdir=DIRobject code libraries in DIR [EPREFIX/lib] --includedir=DIRC header files in DIR [PREFIX/include] --oldincludedir=DIR C header files for non-gcc in DIR [/usr/include] --infodir=DIR info documentation in DIR [PREFIX/info] --mandir=DIRman documentation in DIR [PREFIX/man] --srcdir=DIRfind the sources in DIR [configure dir or ..] --program-prefix=PREFIX prepend PREFIX to installed program names --program-suffix=SUFFIX append SUFFIX to installed program names --program-transform-name=PROGRAM run sed PROGRAM on installed program names Host type: --build=BUILD configure for building on BUILD [BUILD=HOST] --host=HOST configure for HOST [guessed] --target=TARGET configure for TARGET [TARGET=HOST] Features and packages: --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --with-PACKAGE[=ARG]use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --x-includes=DIRX include files are in DIR --x-libraries=DIR X library files are in DIR --enable and --with options recognized: --enable-maintainer-mode enable make rules and dependencies not useful (and sometimes confusing) to the casual installer --enable-shared[=PKGS] build shared libraries [default=yes] --enable-static[=PKGS] build static libraries [default=yes] --enable-fast-install[=PKGS] optimize for fast installation [default=yes] --with-gnu-ld assume the C compiler uses GNU ld [default=no] --disable-libtool-lock avoid locking (might break parallel builds) --with-other-libc=/path/to/other/libc/dir Link against libc and other standard libraries installed in the specified non-standard location overriding default. O riginally added to be able to link against glibc 2.2 without making the user upg rade the standard libc installation --with-server-suffixAppend value to the version string. --with-mit-threads Always use included thread lib. --with-pthread Force use of pthread library. --with-named-thread-libs=ARG Use specified thread libraries instead of those automatically found by configure. --with-named-curses-libs=ARG Use specified curses libraries instead of those automatically found by configure. --with-named-z-libs=ARG Use specified zlib libraries instead of those automatically found by configure. --enable-thread-safe-client Compile the client with threads. --enable-assembler Use assembler versions of some string functions if available. --with-raid Enable RAID Support --with-unix-socket-path=SOCKET Where to put the unix-domain socket. SOCKET must be an absolute file name. --with-tcp-port=port-number Which port to use for MySQL services (default 3306) --with-mysqld-user=username What user the mysqld daemon shall be run as. --disable-largefileOmit support for large files --with-libwrap[=DIR]Compile in libwrap (tcp_wrappers) support --without-debug
Re: [Discuss-gnuradio] ais-tools installation problem
> In the output of './configure --help' are there any options regarding > dll's? I think this line is what is fouling you up: > > > checking if package supports dlls... no > > hth, > > Jason. > No, I didn't see any option concerning dll, options available are: $ ./configure --help Usage: configure [options] [host] Options: [defaults in brackets after descriptions] Configuration: --cache-file=FILE cache test results in FILE --help print this message --no-create do not create output files --quiet, --silent do not print `checking...' messages --version print the version of autoconf that created configure Directory and file names: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [same as prefix] --bindir=DIRuser executables in DIR [EPREFIX/bin] --sbindir=DIR system admin executables in DIR [EPREFIX/sbin] --libexecdir=DIRprogram executables in DIR [EPREFIX/libexec] --datadir=DIR read-only architecture-independent data in DIR [PREFIX/share] --sysconfdir=DIRread-only single-machine data in DIR [PREFIX/etc] --sharedstatedir=DIRmodifiable architecture-independent data in DIR [PREFIX/com] --localstatedir=DIR modifiable single-machine data in DIR [PREFIX/var] --libdir=DIRobject code libraries in DIR [EPREFIX/lib] --includedir=DIRC header files in DIR [PREFIX/include] --oldincludedir=DIR C header files for non-gcc in DIR [/usr/include] --infodir=DIR info documentation in DIR [PREFIX/info] --mandir=DIRman documentation in DIR [PREFIX/man] --srcdir=DIRfind the sources in DIR [configure dir or ..] --program-prefix=PREFIX prepend PREFIX to installed program names --program-suffix=SUFFIX append SUFFIX to installed program names --program-transform-name=PROGRAM run sed PROGRAM on installed program names Host type: --build=BUILD configure for building on BUILD [BUILD=HOST] --host=HOST configure for HOST [guessed] --target=TARGET configure for TARGET [TARGET=HOST] Features and packages: --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --with-PACKAGE[=ARG]use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --x-includes=DIRX include files are in DIR --x-libraries=DIR X library files are in DIR --enable and --with options recognized: --enable-maintainer-mode enable make rules and dependencies not useful (and sometimes confusing) to the casual installer --enable-shared[=PKGS] build shared libraries [default=yes] --enable-static[=PKGS] build static libraries [default=yes] --enable-fast-install[=PKGS] optimize for fast installation [default=yes] --with-gnu-ld assume the C compiler uses GNU ld [default=no] --disable-libtool-lock avoid locking (might break parallel builds) --with-other-libc=/path/to/other/libc/dir Link against libc and other standard libraries installed in the specified non-standard location overriding default. O riginally added to be able to link against glibc 2.2 without making the user upg rade the standard libc installation --with-server-suffixAppend value to the version string. --with-mit-threads Always use included thread lib. --with-pthread Force use of pthread library. --with-named-thread-libs=ARG Use specified thread libraries instead of those automatically found by configure. --with-named-curses-libs=ARG Use specified curses libraries instead of those automatically found by configure. --with-named-z-libs=ARG Use specified zlib libraries instead of those automatically found by configure. --enable-thread-safe-client Compile the client with threads. --enable-assembler Use assembler versions of some string functions if available. --with-raid Enable RAID Support --with-unix-socket-path=SOCKET Where to put the unix-domain socket. SOCKET must be an absolute file name. --with-tcp-port=port-number Which port to use for MySQL services (default 3306) --with-mysqld-user=username What user the mysqld daemon shall be run as. --disable-largefileOmit support for large files --with-libwrap[=DIR]Compile in libwrap (tcp_wrappers) support --without-debug
Re: [Discuss-gnuradio] ais-tools installation problem
Don Ward wrote: > > Try "./configure --help" (in your mysql directory) and see if you have > options like --enable-static, --enable-shared, --disable-static, > and/or --disable-shared. Depending on the defaults, to build a shared > library (a *.dll file on Windows---what you need) you may need to specify > "--enable-shared --disable-static" on your ./configure. Look carefully in > the output of ./configure and you should be able to find where it says if > it > is building shared or static libraries. > > -- Don W. > Hi, I do have the “--enable-share” compiling option: $ ./configure --help Usage: configure [options] [host] Options: [defaults in brackets after descriptions] … Features and packages: --enable-shared[=PKGS] build shared libraries [default=yes] Even though the default is “yes” when running ./configure $ ./configure loading cache ./config.cache … checking dynamic linker characteristics... Win32 ld.exe checking if libtool supports shared libraries... yes checking if package supports dlls... no checking whether to build shared libraries... no checking whether to build static libraries... yes checking for objdir... .libs creating libtool loading cache ./config.cache … I am completely lost, any ideas? Thanks, Irene -- View this message in context: http://www.nabble.com/ais-tools-installation-problem-tp16678654p16807471.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ais-tools installation problem
Hello, Well I downloaded mysql-3.23.43, I am not sure I’ve done the right choice. I did do some Internet research before installing it and that’s when I realized that there are many problems with mysql running on Cygwin although this version was said to work. Can somebody confirm? The point is there is no libmysqlclient.dll. I run ./configure, make and make install with no problem but I noticed the following message: Libraries have been installed in: /usr/local/lib/mysql If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag I don’t really understand what must be done to link against the libraries. I just added AM_LDFLAGS="-L/usr/local/lib/mysql" to the Makefile, did I miss something? When should the libmysqlclient.dll file have been created? The only files that were generated are libmysqlclient.a and libmysqlclient.la. What is the difference between .dll, .a and .la files? Which files are required for the library libmysqlclient to work? While searching for solutions I’ve read about dynamic linking, shared libraries, dynamic and static libraries… all this is still confusing for me so if someone doesn't mind giving some explanations I’ll appreciate. Thanks! Irene -- View this message in context: http://www.nabble.com/ais-tools-installation-problem-tp16678654p16742463.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ais-tools installation problem
Hello, I just noticed that I missed some things on the make output [3], specially: *** Warning: linker path does not have real file for library -lmysqlclient. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libmysqlclient and none of the candidates passed a file format test *** using a file magic. Last file checked: /usr/lib/python2.5/config/libpython2. 5.dll.a *** Warning: libtool could not satisfy all declared inter-library *** dependencies of module _ais. Therefore, libtool will create *** a static module, that should work as long as the dlopening *** application is linked with the -dlopen flag. So there is still a problem with libmysqlclient. I have libmysqlclient.a and libmysqlclient.la in /usr/local/lib/mysql. What does "linker path does not have real file for library -lmysqlclient" mean? I guess the second warning explains why no '_ais.dll' file was created and why I got the error above when I tried to do make check. How can I solve this problem? May I also have some precisions on –dlopen flag? Thank you for your help! [3] http://www.nabble.com/file/p16722570/MakeOutput.txt MakeOutput.txt -- View this message in context: http://www.nabble.com/ais-tools-installation-problem-tp16678654p16722570.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ais-tools installation problem
Hello, You were right; I got the problem solved by adding AM_LDFLAGS="-L/usr/local/lib/mysql" to ais-tools-gnuradio-1.0.1\src\Makefile.am. The ./configure and the make seem to run fine now but when I use make check in ais-tools-gnuradio-1.0.1\src\Python I get the following error: $ make check make check-TESTS make[1]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src/python' Traceback (most recent call last): File "./qa_howto.py", line 24, in import ais File "/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS/ais-tools-gnuradio- 1.0.1/src/lib/ais.py", line 6, in import _ais ImportError: No module named _ais FAIL: run_tests === 1 of 1 tests failed === make[1]: *** [check-TESTS] Error 1 make[1]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src/python' make: *** [check-am] Error 2 When comparing with the gr-howto-write-a-block-3.0.4 example I noticed that _howto.dll and _howto.dll.a files were created in the src\lib\.libs directory, while as in ais-tools-gnuradio-1.0.1\src\lib\.libs I found no file with a dll extension (a _ais.a file exists). Can this be the problem? Why wasn’t this file created? gr-howto-write-a-block-3.0.4 and ais-tools-gnuradio-1.0.1 Makefiles are almost the same (except for file names) and ais.i is pretty much like howto.i too. -- View this message in context: http://www.nabble.com/ais-tools-installation-problem-tp16678654p16718848.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] ais-tools installation problem
Hello, I would like to run ais-tools-gnuradio-1.0.1 [1] on Cygwin. Can somebody please give me the installation procedure? Are there any requirements to be considered before running the application (specially concerning Google Earth or DB)? I have installed mysql-3.23.43. I have run the standard installation sequence : ./configure ; make The configure worked perfectly without any error, but on the "make" I got the following : $ make make all-recursive make[1]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1' Making all in config make[2]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/config' Making all in src make[2]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src' Making all in lib make[3]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src/lib' make all-am make[4]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src/lib' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src/lib' make[3]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src/lib' Making all in python make[3]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src/python' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src/python' make[3]: Entering directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AI S/ais-tools-gnuradio-1.0.1/src' /bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 -Wall -Woverloaded-virtual -o aisgearthserver.exe gearth.o -lmysqlclient -lm -L/usr/local/lib -lgnuradi o-core -lfftw3f -lm -lgromnithread g++ -g -O2 -Wall -Woverloaded-virtual -o aisgearthserver.exe gearth.o -lmysqlcl ient -L/usr/local/lib /usr/local/lib/libgnuradio-core.dll.a /usr/local/lib/libff tw3f.dll.a /usr/local/lib/libgromnithread.dll.a -lwinmm -L/usr/local/lib -L/usr/ local/lib /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot find -lmysqlclient collect2: ld returned 1 exit status make[3]: *** [aisgearthserver.exe] Error 1 make[3]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/gnuradio-3.1.1/gnuradio-examples/python/AIS /ais-tools-gnuradio-1.0.1' make: *** [all] Error 2 Where does the problem come from and how can I solve it? [1] - http://funwithelectronics.com/sdr/ais.php Thanks, Irene -- View this message in context: http://www.nabble.com/ais-tools-installation-problem-tp16678654p16678654.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] libusb-win32 for USRP
Hello, I am running GNU Radio on Cygwin and I would like to use USRP hardware. Software requirements are still a confusing for me: - USRP Driver is successfully installed (following gnuradio.org/trac/wiki/USRPWindowsDriverInstall instructions) - libusb-win32-device-bin-0.1.10.1 and sdcc-2.6.0 are also installed - The PYTHONPATH is fixed to be /usr/local/lib/python2.5/site-packages - usrp and gr-usrp exist in /usr/src/gnuradio-3.1.1 1) Did I forget something? When trying to run “import usrp” I get an Import Error. I realised that “make” command in the usrp folder isn’t successful apparently due to usrp_basic.cc file errors all associated to usb such as usb.h include or functions like _usb_strerror. 2) Does anybody have an idea where the problem comes from? 3) I found usb.h in libusb-win32-device-bin-0.1.10.1 that I have placed in \usr\include\libusb-win32-device-bin-0.1.10.1, where must this folder be in order to be found when running make at \usr\src\gnuradio-3.1.1\usrp? Thank you for your help! Regards, Irene -- View this message in context: http://www.nabble.com/libusb-win32-for-USRP-tp16467790p16467790.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Measure BER
Hi! I’ve started performing modulation and demodulation on the same machine but the main purpose is to make them work separately afterwards. I’ve seen some BER values on the forums and I was wondering if an “official” block had already been developed to measure it. 1) Tom, May I please have a look at your block calculating BER? 2) When comparing data sent and data received, how can we detect bit lost in order to avoid clock shifting? In other words, if I’m sending “11010110” for example, and that the 4th bit is lost, a simple comparison will compare tx : “11010110” with rx : “1100110”. Detecting a lost is easy because the number of bits in reception will be inferior to the number of bits sent, but how can continue to compare the rest correctly? -- View this message in context: http://www.nabble.com/Measure-BER-tp14952951p14998913.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Measure BER
Hi all, I'm currently working on a GSMK modem, and I would like to calculate the BER of the link. I send data using gr.vector_source_b( ) connected to a GMSK modulator/demodulator and receive the signal in gr.vector_sink_b( ). 1) How can I measure BER from the vector_source and vector_sink ? 2) Does a BER calculator recovering from clock shifting (bit lost by clock sliding) exist ? Thanks ! -- View this message in context: http://www.nabble.com/Measure-BER-tp14952951p14952951.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
