Re: [Discuss-gnuradio] slicing up a 'file-sink' capture?
The git version of inspectrum should do just what you want - you can select a period of time with the cursors and export it by right-clicking the spectrogram. On 24 September 2016 at 20:44, Cinaed Simson wrote: > Might want to look at inspectrum. > > The size of the FFT can be varied, it has zoom and an overlay for > determining symbol timing and can handle large files. > > No editing features however. > > I don't anything about baudline. > > The version I'm running requires qt5. > > See > > https://github.com/miek/inspectrum > > On 09/23/2016 04:02 PM, du...@duaneellis.com wrote: > > Hi - > > > > I've setup a front end, and captured about 10 to 20 seconds worth of > > data to a file sink (750M data file) > > > > The transmitted data is a small 8millisecond bursts, followed by a very > > long delay. > > > > I would like to have some means to 'zoom in and slice out' a few bits of > > data so I can do more work with it. > > > > I've tried baudline, while helpful - I can a very low level signal, > > followed by a huge signal, and back to a low level signal. > > > > My question is: > > > > Can you suggest a tool that I can use to "slice out" - the sections > > of interest? > > The closest example I can think of is using "head/tail" - into baud > > line ... > > And manually move my start/stop sample number until I get what I > > want. > > > > There's got to be a better way... > > > > for example I'd like to zoom in, select the region of interest then save > > that region. > > > > Then - these new files as input data for some tests. > > > > Thanks. > > > > > > > > ___ > > 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
Re: [Discuss-gnuradio] gnuradio for Windows
Lyman, Glad you were able to install GNURadio. The warnings you mentioned are indeed known but are just warnings. If you can be more specific about what didn't work, it would be quite helpful. GNURadio is more stable on Linux as that is the primary platform for most users. This Windows installer is relatively new so we are still working on a few issues, but we would like to hear what didn't work for you. Geof On Saturday, September 24, 2016, Lyman Paquette wrote: > Greetings, > > Recently I downloaded gnuradio for Windows to try as I do not have a > working Linux box at present. > > The install went smoothly but upon starting gnuradio the command window > came up and gave the following errors: > > Snip>>> > > setting gnuradio environment > > ** (python.exe:10624): WARNING **: Trying to register gtype > 'GMountMountFlags' as enum when in fact it is of type 'GFlags' > > ** (python.exe:10624): WARNING **: Trying to register gtype > 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' > > ** (python.exe:10624): WARNING **: Trying to register gtype > 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' > C:\Program Files\GNURadio-3.7\lib\site-packages\gnuradio\grc\main.py:43: > GtkWarning: Could not find the icon 'gnuradio-grc'. The 'hicolor' theme > was not found either, perhaps you need to install it. > > << > You probably already know about these but in case no one has let you know > I am posting here. > > Using Win 10 - 64bit with Python 3.5 installed. > > It seems to be able to do some things but not others. As I am just trying > to learn gnuradio I have not tested extensively. > > I will try your ubuntu build and upgrade gnuradio. > > > regards > L > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Flummoxed!
On 09/24/2016 12:34 PM, liverpudd wrote: > Working on the GNURADIO gr-rds to try and find out why it appears to be > finicky with what source drives it. Unfortunately I don't know anything about RDS. But as strange as this might sound, it almost appears as if the RDS module is configured to use RTL dongle raw I/Q data pairs and not the complex I/Q pairs used by the USRP and HackRF One? > > > > Set up three sources. USRP1, RTL Dongle(NooElec Blue with 0.5ppm TXCO ) > and the HackRF. > > > > Plugged a decent antenna and tuned to R2 (88.3MHz) a nice strong signal. > Whilst the radio works OK with all three sources, the RDS decoding would > only work with the RTL Dongle. > > > > Checked the input IQ level from the RTL dongle and adjusted the input > level to be the same from the USRP1 and the HackRF. No joy – no change > with either the USRP or HackRF decoding the RDS! > > > > Adjusted the Rx frequency 88.3MHz +/- 200KHz. The RDS decoder packed in > beyond +/- 100KHz on the RTL dongle. No joy with either the USRP or > HackRF, no matter what frequency offset I dialled in. > > > > Next adjusted the 1Msps sample rate using a Polyphase Arbitrary > Respampler. Adjusted it from 1Msps to +/- 50Ksps in small increments. > RTL dongle packed in the RDS decode a few Ksps either side of the > nominal centre of 1Msps. No joy from the USRP or HackRF no matter what > sample rate I set it to!!! > > > > Grasping at straws now, I put a phase rotator in line (can’t say I know > what exactly this block does!) but in any case I adjusted the phase by > +/- 5 degs. The RTL dongle packed in the RDS decode at about +/- 0.2 > degs. No joy with the USRP or HackRF, no matter what phase value I set > it to!!! > > > > So current situation is I do not know what is going on. I have adjusted > all that I can to no avail. Any ideas? > > > > Alistair > > > > ___ > 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] gnuradio for Windows
Greetings, Recently I downloaded gnuradio for Windows to try as I do not have a working Linux box at present. The install went smoothly but upon starting gnuradio the command window came up and gave the following errors: Snip>>> setting gnuradio environment ** (python.exe:10624): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (python.exe:10624): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' ** (python.exe:10624): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' C:\Program Files\GNURadio-3.7\lib\site-packages\gnuradio\grc\main.py:43: GtkWarning: Could not find the icon 'gnuradio-grc'. The 'hicolor' theme was not found either, perhaps you need to install it. <<___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] slicing up a 'file-sink' capture?
Might want to look at inspectrum. The size of the FFT can be varied, it has zoom and an overlay for determining symbol timing and can handle large files. No editing features however. I don't anything about baudline. The version I'm running requires qt5. See https://github.com/miek/inspectrum On 09/23/2016 04:02 PM, du...@duaneellis.com wrote: > Hi - > > I've setup a front end, and captured about 10 to 20 seconds worth of > data to a file sink (750M data file) > > The transmitted data is a small 8millisecond bursts, followed by a very > long delay. > > I would like to have some means to 'zoom in and slice out' a few bits of > data so I can do more work with it. > > I've tried baudline, while helpful - I can a very low level signal, > followed by a huge signal, and back to a low level signal. > > My question is: > > Can you suggest a tool that I can use to "slice out" - the sections > of interest? > The closest example I can think of is using "head/tail" - into baud > line ... > And manually move my start/stop sample number until I get what I > want. > > There's got to be a better way... > > for example I'd like to zoom in, select the region of interest then save > that region. > > Then - these new files as input data for some tests. > > Thanks. > > > > ___ > 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] Flummoxed!
Working on the GNURADIO gr-rds to try and find out why it appears to be finicky with what source drives it. Set up three sources. USRP1, RTL Dongle(NooElec Blue with 0.5ppm TXCO ) and the HackRF. Plugged a decent antenna and tuned to R2 (88.3MHz) a nice strong signal. Whilst the radio works OK with all three sources, the RDS decoding would only work with the RTL Dongle. Checked the input IQ level from the RTL dongle and adjusted the input level to be the same from the USRP1 and the HackRF. No joy - no change with either the USRP or HackRF decoding the RDS! Adjusted the Rx frequency 88.3MHz +/- 200KHz. The RDS decoder packed in beyond +/- 100KHz on the RTL dongle. No joy with either the USRP or HackRF, no matter what frequency offset I dialled in. Next adjusted the 1Msps sample rate using a Polyphase Arbitrary Respampler. Adjusted it from 1Msps to +/- 50Ksps in small increments. RTL dongle packed in the RDS decode a few Ksps either side of the nominal centre of 1Msps. No joy from the USRP or HackRF no matter what sample rate I set it to!!! Grasping at straws now, I put a phase rotator in line (can't say I know what exactly this block does!) but in any case I adjusted the phase by +/- 5 degs. The RTL dongle packed in the RDS decode at about +/- 0.2 degs. No joy with the USRP or HackRF, no matter what phase value I set it to!!! So current situation is I do not know what is going on. I have adjusted all that I can to no avail. Any ideas? Alistair ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
