Bandlimited threshold detector

Introduction
Sometimes a DSP application will call for signal detection of an intermittent signal (only present in the spectrum part of the time). A simplistic way to detect signal is by way of a frequency domain threshold, when an FFT bin exceeds that threshold the signal is 'detected'. Using a 'dumb' threshold would be a first obvious choice for triggering a detection event. The threshold level is the same across the entire spectral window and it is set to a value above the observed noisefloor, but below the minimum level of a particular signal we are trying to detect. With this simple approach (a straight line across the spectrum), a detection event is triggered anytime the threshold is exceeded. Ideally our threshold would only trigger on the specific signals we want to detect, those signals may be clustered together in frequency in a range or band contained within the spectral observation window. If we restrict the detection criteria to only a simple level threshold, some signals within our observation window may trigger a detection in error (since we only want to detect signals in a subband of our observation window) If we can restrict the threshold to not only power, but also frequency, we can still look at a large frequency range and see what else is present, but only trigger a detection if the threshold is crossed within the defined portion of spectrum.

Generate Synthetic RF Spectrum with Intermittent Carriers

 * broadband noise
 * narrowband signals with intermittent behavior
 * a large wideband signal

Set Visual Boundary Lines around a segment of the Frequency Spectrum and a Threshold Level

 * Visualize the Synthetic RF Spectrum in the Frequency Domain
 * Create an adjustable threshold (horizontal line) that is displayed in the frequency window and also can be manually adjusted by the user.
 * Add upper and lower frequency boundaries (vertical lines) which will restrict the threshold trigger to signals within the boundary box.

Detection
the portion of the spectrum contained within the frequency boundary lines crosses the threshold.
 * instantiate logic using in-tree blocks to compare the incoming signal's spectrum to the upper/lower frequency boundaries and only display
 * instantiate logic to compare the spectrum contained within the frequency boundary lines to the threshold and only display the portion that
 * use a custom python block to trigger a file recording of the bin number and indices of any threshold crossings we detect

Content
The flowgraph for this tutorial is shown below along with the GRC file needed if you would like to test it out.





Generate 'Synthetic RF Spectrum'
In the following example we will: Generate a synthetic signal for testing. It is assumed that you are comfortable enough in GNURadio to understand what these blocks are doing.



This portion of the flowgraph:


 * generates gaussian noise for the overall noisefloor (simulating environmental broadband noise)
 * Simulates a wideband carrier by lowpass filtering a noise source that is uncorrelated with the noise in the overall spectrum
 * Creates two narrowband carriers which are each modulated by square waves of different frequencies to simulate intermittent transmissions

Create A Visual Utility to Set Detection Boundaries for Frequency and Level
This portion of the flowgraph is where we get creative with Vectors.

For this Flowgraph, we will have an overall FFT size used to display our synthetic frequency spectrum. In this example it will be 8192 FFT bins.

Dumb Threshold
For the 'dumb threshold', a vector where all values are adjustable will allow us to use a QT GUI Range Widget to dynamically raise and lower the threshold. This can be done by creating a QT GUI Range Widget  and entering   where has the value 8192, the overall FFT size for the flowgraph.

At runtime, the  QT GUI Range Widget will set all the indices of this vector to the same value which will display as a horizontal line spanning the entire frequency window. When the variable is adjusted, the line moves up/down.

Frequency Boundary Box
For the frequency boundary box, it gets a little more complicated. Consider a simple case of a vector with length 9, where the vector values are with indices.

On a plot, we get a shape like this ____|____ where the flat parts across the bottom are 4 values of -1000 (index 0-3) on the left and 4 values of -1000 on the right (index 5-8) with one value in the middle (index 4) with value +1000. In GNURadio when we represent baseband samples as RF signals in the frequency domain (QT Frequency Sink) we limit the y-axis of the observation window to defaults of +10dB and -140dB, because we won't likely be able to receive signals greater than say +20 on a relative scale with common A/D's in SDR's. Therefore, if we insert a vector into a QT Vector GUI with values that exceed our viewing window, we will only see a vertical line in the window for the value of +1000. We can use that line as a boundary using some array logic in with python expressions.

For the Upper/Lower boundaries we will create vector sources where each vector will adjust it's left and right sides so that both of them combined will equal 8191, adding the vertical line's index to the left and right sides will make the total vector length add up to the FFT length 8191+1=8192

This section of the flowgraph is shown here:



The parameters for the 3 Vector Source blocks are shown here:



= 8192

is the extremely low value from our simple length 9 vector example (-1000)

is the extremely high value from our simple length 9 vector example (+1000)

is a QT GUI Range Widget that we use to adjust the position of the vertical line that indicates the lower frequency boundary of the frequency boundary box

is a QT GUI Range Widget that we use to adjust the position of the vertical line that indicates the upper frequency boundary of the frequency boundary box

The upper and lower frequency boundary vectors will be constructed to expand or contract in length based on the desired position of their vertical boundary lines.

Both vertical boundary lines follow the same logic. In the case of the lower boundary line:

The left half of the vector can be expressed as, which says that the number of bins to the left of the vertical line's position (the 'left side' of the vector) will be equal to the position of the vertical line. So if the vertical line's position is index: 512, there will be 512 values to it's left (0-511)

The right half of the vector can be expressed as, which says that the number of bins to the right of the vertical line's position (the 'right side' of the vector) will be equal to the number of bins between the vertical line's position index (512) and the rest of the total vector length 8192 (512-8192). We subtract 1 to account for the vertical line's position itself.

When the vertical line position is adjusted with the QT GUI Range Widget, the left/right sides will adjust accordingly in real-time. The total will always be the overall FFT Length (8192).





Add the synthetic signal to the Display
Since the incoming signal is really the main event in spectrum monitoring, we should probably add that to the spectrum window with the threshold and frequency boundary lines. The 4th input (input 3) on the QT GUI Vector Sink is where we add our synthetic signal.

In the section above, we showed how the synthetic signal can be constructed from several different sources and summed together to create one stream of data. Before we put it into our frequency display we need to also convert the time domain to a spectral representation. In this example, we do this by using the Log Power FFT block, which is a combination of several GNURadio blocks in one:
 * stream to vector
 * vector decimation (frame rate)
 * complex to mag squared

The output is the same type as the threshold and frequency boundary lines (float32) and is also a vector.

This part of the flowgraph is shown here:



When we display these, we will see our synthetic signal's spectral representation, our threshold and frequency boundary lines superimposed on top of the spectrum, show here:



Detection
Now that we have lines we can move around our signal, we can also use the variables to do some comparison to only display/passthrough signal if it's within the frequency boundary box and above the threshold.

By identifying which FFT indices (bins) that fall between the lower/upper frequency boundary lines, we can create a value to compare against our incoming signal's spectral representation.

This is done here in the flowgraph:



The value of  represents a run-time callback, where the value changes as the upper/lower frequency boundary lines are adjusted.



This is used to create a vector of length 8192, where all vector indices that are either to the left of the lower frequency boundary line OR to the right of the upper frequency boundary line are an extremely low number. The vector indices in between the upper/lower frequency boundary positions are 0.



When added to the incoming signal's spectral representation, this results in a vector of length 8192 which preserves the synthetic signal's vector indices between the lower/upper frequency boundary lines.

If the upper/lower frequency boundary lines are set just below and just above the two narrow band carriers, the displayed result is shown below:



Now the output of the lower/upper frequency boundary check is passed to one input of a  block where it is compared against the threshold.



The output is a vector where every index is greater than or equal to the threshold value.



Embedded Python Block to Record Detections
Up until this point, only in-tree blocks have been used. At this point, if we would like to write all values above the threshold, a very simple custom block can be used to extract them from the output of the max block above by comparing against the threshold value as it changes.



The following Embedded Python block will determine if the incoming data is greater than the threshold, thus rejecting the threshold itself and recording only the spectra from the synthetic signal that is above the threshold AND within the frequency boundary. The output file contains the timestamp of the detection, a list of bin numbers and a list of corresponding magnitudes.

Example:

1661155430.9426177[5323 5324 5325 5326],[-58.806225 -49.62006 -47.60839  -52.316525] 1661155431.0243776[5323 5324 5325 5326],[-58.734993 -49.58642  -47.59074  -52.312286] 1661155431.1061163[5323 5324 5325 5326],[-58.690277 -49.577198 -47.589127 -52.305576] 1661155431.1887715[5323 5324 5325 5326],[-58.769714 -49.585815 -47.57643  -52.278713] 1661155431.2700336[5323 5324 5325 5326],[-58.6992   -49.582836 -47.58903  -52.30743 ] 1661155431.3521397[5323 5324 5325 5326],[-58.765884 -49.599594 -47.594917 -52.30714 ] 1661155431.4342203[5323 5324 5325 5326],[-58.766293 -49.591564 -47.59711  -52.32647 ]

Embedded Block Code
""" Embedded Python Blocks:

Each time this file is saved, GRC will instantiate the first class it finds to get ports and parameters of your block. The arguments to __init__ will be the parameters. All of them are required to have default values! """

import numpy as np from gnuradio import gr import time

class blk(gr.sync_block): # other base classes are basic_block, decim_block, interp_block """Embedded Python Block example - a simple multiply const"""

def __init__(self, vec_len=8192, peak_detect_file="/tmp/indexes.data"): # only default arguments here """arguments to this function show up as parameters in GRC""" gr.sync_block.__init__(           self,            name='Embedded Python Block',   # will show up in GRC            in_sig=[(np.float32,vec_len),(np.float32,vec_len)],            out_sig=None        ) # if an attribute with the same name as a parameter is found, # a callback is registered (properties work, too). self.peak_detect_file=peak_detect_file

def work(self, input_items,output_items): for vecindx in range(len(input_items[0])): if len(np.nonzero(input_items[0][vecindx] > input_items[1][vecindx][0])[0])>0: #print("number of crossings: ", len(np.nonzero(input_items[0][vecindx] > input_items[1][vecindx][0])[0])) #print(" level of crossings: ", np.nonzero(input_items[0][vecindx] > input_items[1][vecindx][0])) #print(" index of crossings: ", input_items[0][vecindx][np.nonzero(input_items[0][vecindx] > input_items[1][0])]) with open(self.peak_detect_file,'a') as fobj: fobj.write(str(time.time)+str(np.nonzero(input_items[0][vecindx] > input_items[1][vecindx][0])[0])+","+str(input_items[0][vecindx][np.nonzero(input_items[0][vecindx] > input_items[1][0])])+'\n') return len(input_items[0])

NOTE: It is true that the last step above could be skipped and this custom block used instead if all we want is the values written to file, however the above step allows a simple way to clearly visualize which values are above the threshold.

Here is a brief demo of the flowgraph in action:



Prerequisites

 * Intro to GR usage: GRC and flowgraphs


 * Streams and Vectors