|(5 intermediate revisions by 2 users not shown)|
See [[MPSK SNR Estimator]], this block
simply outputs the SNR as a message, which can be outputted to the console using a [[Message Debug]] block.
See [[MPSK SNR Estimator]], this block outputs the SNR as a message , which can be outputted to the console using a [[Message Debug]] block.
Latest revision as of 22:58, 14 December 2020
See MPSK SNR Estimator, this block makes the same calculation but outputs the resulting SNR as a message instead of a tag, which can be outputted to the console using a Message Debug block.
This is a probe block (a sink) that can be used to monitor and retrieve estimations of the signal SNR. This probe is designed for use with M-PSK signals especially. The type of estimator is specified as the parameter in the constructor. The estimators tend to trade off performance for accuracy, although experimentation should be done to figure out the right approach for a given implementation. Further, the current set of estimators are designed and proven theoretically under AWGN conditions; some amount of error should be assumed and/or estimated for real channel conditions.
The estimator is normally placed before clock recovery.
The block has three output message ports that will emit a message every msg_samples number of samples. These message ports are:
- snr: the current SNR estimate (in dB)
- signal: the current signal power estimate (in dBx)
- noise: the current noise power estimate (in dBx)
Some calibration is required to convert dBx of the signal and noise power estimates to real measurements, such as dBm.
(R): Run-time adjustable
- Type (R)
- The type of estimator to use. See MPSK SNR Estimator for details about the types.
- Samples between SNR messages (R)
- [not implemented yet] after this many samples, a message containing the SNR (key='snr') will be sent
- Filter Alpha (R)
- The update rate of internal running average calculations. Needs to be between 0 and 1, where higher value adjusts faster to new data.
Insert description of flowgraph here, then show a screenshot of the flowgraph and the output if there is an interesting GUI. Currently we have no standard method of uploading the actual flowgraph to the wiki or git repo, unfortunately. The plan is to have an example flowgraph showing how the block might be used, for every block, and the flowgraphs will live in the git repo.
- C++ files
- Header files
- Public header files
- Block definition