search

inls718 / documentation

This repository contains documentation for the INLS718 Spring 2017 semester project.
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Important Blocks: GFSK #19

Open griffinac opened 7 years ago

griffinac commented 7 years ago

Find information on GFSK block

griffinac commented 7 years ago

1. How info is mapped currently in GRC? GFSK: Gaussian Frequency Shift Keying modulator and demodulator. A GFSK modulator is similar to a FSK modulator, except that before the baseband waveform goes into the FSK modulator, it is passed through a Gaussian filter to make the transitions smoother so to limit its spectral width. Gaussian filtering is a standard way for reducing spectral width. GFSK Python block code: http://gnuradio.org/redmine/projects/gnuradio/repository/revisions/71127c2d4082119ea086f9f881b349922ed8cf24/entry/gr-digital/python/gfsk.py

Control: GFSK Demod: User drags it into the flowgraph, then assigns it an ID, sensitivity, gain mu, mu, omega relative limit, and freq error. These fields are already populated with numbers and colors (not sure what they mean). The verbose and log fields have drop down menus for choice of “on” or “off.” In the box at the bottom, it shows the users if the source and sink port are connected. GFSK Mod:User drags it into the flowgraph, then assigns it an ID, samples/symbol, sensitivity, and BT. These fields are already populated with numbers and colors (not sure what they mean). The verbose and log fields have drop down menus for choice of “on” or “off.” In the box at the bottom, it shows the users if the source and sink port are connected.

Effect: Properties are modified if needed.

2. What is a more effective way of doing that? Suggestions: Identify what the colors mean and provide more description in each field when the user places mouse over it. (I.e., in the GFSK mod, when users places mouse over BT field, a description and example would be useful.)