Ok, but it is not clear for me how to open a ticket in gr bug tracker...
On Wed, Aug 7, 2013 at 4:35 PM, Marcus Müller <mar...@hostalia.de> wrote: > Yes, please attach it to your ticket. > > Am 07.08.2013 14:28, schrieb Anton Komarov: > > Marcus, am i supposed to share e.g. 10 seconds of captured spectrum so you > can play with it on your side? > > > On Wed, Aug 7, 2013 at 4:18 PM, Marcus Müller <mar...@hostalia.de> wrote: > >> Hi Anton, >> it is really hard to capture apco25 signals in Germany. >> Could you really open a ticket, attach a few captured samples saved using >> a file sink, >> and the 3.6 and 3.7 flowgraphs; or provide some kind of test case with >> GNU Radio Signal sources >> that simulate a signal. Be sure to attach screenshots of your waterfall >> plots. >> It is really hard to guess what goes wrong otherwise. >> >> Greetings, >> Marcus >> >> Am 07.08.2013 13:56, schrieb Anton Komarov: >> >> Ok, i've attached very simple grc chart >> with slider you can change the frequency, two waterfalls shows spectrums >> before and after xlating. >> So i had test it in apco25 env and took apco signals as a reference. So >> when i saw signal e.g. at 451.378 MHz and tuned to it i saw no signal after >> xlating nevertheless it was the same time on waterfall before xlating. >> >> You can test this chart with you radio environment. >> >> Then i testing the same logic with gr 3.6 (code is not compatible i >> have to redraw it..) and here it is! xlating worked like a charm. >> >> >> On Wed, Aug 7, 2013 at 1:48 PM, Martin Braun (CEL) >> <martin.br...@kit.edu>wrote: >> >>> On Wed, Aug 07, 2013 at 01:00:32PM +0400, Anton Komarov wrote: >>> > Hi, made an attempt to test my python scripts with new 3.7.0 of GR >>> > >>> > and what i am seeing xlate fir filter is broken >>> > >>> > >>> > previously xlate worked perfect with 3.6 version >>> > >>> > >>> > tested with waterfalls and i see wrong xlating >>> > >>> > i think developers should pay attention to this issue >>> >>> Hi Anton, >>> >>> can you please elaborate on this bug. Ideally, could you post an issue >>> on our tracker: http://gnuradio.org/redmine/projects/gnuradio/issues >>> >>> Specify what you configured, what the expected outcome was and what >>> happened instead. >>> >>> Thanks, >>> MB >>> >>> -- >>> Karlsruhe Institute of Technology (KIT) >>> Communications Engineering Lab (CEL) >>> >>> Dipl.-Ing. Martin Braun >>> Research Associate >>> >>> Kaiserstraße 12 >>> Building 05.01 >>> 76131 Karlsruhe >>> >>> Phone: +49 721 608-43790 >>> Fax: +49 721 608-46071 >>> www.cel.kit.edu >>> >>> KIT -- University of the State of Baden-Württemberg and >>> National Laboratory of the Helmholtz Association >>> >>> _______________________________________________ >>> Discuss-gnuradio mailing list >>> Discuss-gnuradio@gnu.org >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> >> >> >> _______________________________________________ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
