Table Of Contents

MT Matched Filter (MT Apply Matched Filter (Generic)) (G Dataflow)

Version:
    Last Modified: February 7, 2018

    Applies a matched filter to a PAM, ASK, QAM, and PSK-modulated input waveform. The node returns the matched filtered output with a duration equal to an integer number of symbols, thus ensuring continuability from one iteration to the next.

    Use MT Align To Ideal Symbols to locate and realign the matched-filtered waveform at the ideal symbol timing instant.

    connector_pane_image
    datatype_icon

    input complex waveform

    The continuous-time modulated complex baseband waveform data.

    spd-note-note
    Note  

    The sample rate of the input complex waveform must be an even integer multiple of the samples per symbol value. Use MT Resample (Complex Cluster) to adjust the sample rate before matched filter application.

    datatype_icon

    t0

    Trigger (start) time of the Y array.

    Default: 0.0

    datatype_icon

    dt

    Time interval between data points in the Y array.

    Default: 1.0

    datatype_icon

    Y

    The complex-valued signal-only baseband modulated waveform. The real and imaginary parts of this complex data array correspond to the in-phase (I) and quadrature-phase (Q) data, respectively.

    datatype_icon

    matched filter coefficients

    An ordered array containing sample-spaced coefficients for the desired matched filter. Wire the matched filter coefficients parameter of MT Generate Filter Coefficients to this parameter. Ensure that the value of samples per symbol matches the matched samples per symbol value used to generate the filter coefficients.

    You can also specify custom matched filter coefficients.
    spd-note-note
    Note  

    This node does not verify the absence of intersymbol interference in custom filter coefficients before applying the matched filter.

    datatype_icon

    samples per symbol

    Number of samples per information symbol in the input complex waveform.

    Default: 16

    datatype_icon

    error in

    Error conditions that occur before this node runs.

    The node responds to this input according to standard error behavior.

    Standard Error Behavior

    Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

    error in does not contain an error error in contains an error
    If no error occurred before the node runs, the node begins execution normally.

    If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

    If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

    Default: No error

    datatype_icon

    reset?

    A Boolean that determines whether the node continues matched filtering using the previous iteration states.

    TRUE Resets the matched filtering process.
    FALSE Continues performing matched filtering from the previous iteration. Matched filtering begins from the last iteration state on subsequent calls.

    Default: TRUE

    datatype_icon

    output complex waveform

    The output matched filtered continuous-time I/Q baseband waveform.

    datatype_icon

    t0

    Trigger (start) time of the Y array.

    Default: 0

    datatype_icon

    dt

    Time interval between data points in the Y array. The reciprocal of this value is equal to the system sample rate.

    Default: 1.0

    datatype_icon

    Y

    The complex-valued signal-only baseband modulated waveform. The real and imaginary parts of this complex data array correspond to the in-phase (I) and quadrature-phase (Q) data, respectively.

    datatype_icon

    error out

    Error information.

    The node produces this output according to standard error behavior.

    Standard Error Behavior

    Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

    error in does not contain an error error in contains an error
    If no error occurred before the node runs, the node begins execution normally.

    If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

    If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Not supported

    Web Server: Not supported in VIs that run in a web application


    Recently Viewed Topics