How do I calculate the minimum detectable signal?
Add the thermal noise floor, the receiver noise figure, and the required SNR. MDS equals −174 dBm/Hz plus 10·log₁₀ of the bandwidth in Hz, plus the noise figure in dB, plus the required SNR in dB. For a 12.5 kHz channel with a 6 dB noise figure needing 12 dB of SNR, the thermal floor is −174 + 41 = −133 dBm, the receiver floor is −127 dBm, and the MDS is −115 dBm. The calculator does this live and also expresses the result as a voltage and a field strength.
What is the difference between the noise floor and the minimum detectable signal?
The noise floor is the noise power at the receiver input, kTB plus the noise figure. The minimum detectable signal is the noise floor plus the SNR the demodulator needs to actually recover the signal. So the MDS is always above the noise floor by the required SNR. A signal exactly at the noise floor has a 0 dB SNR, which is the classic definition of the minimum detectable signal for a simple energy detector, but a real demodulator needs several dB more, and that margin is the required SNR term.
Why does a wider bandwidth raise the minimum detectable signal?
Because thermal noise is spread evenly across frequency, so a wider channel collects more of it. The noise power rises as 10·log₁₀ of the bandwidth, which is 3 dB for every doubling. A 25 kHz channel has a 3 dB higher floor than a 12.5 kHz channel and therefore a 3 dB worse sensitivity, all else equal. This is why narrowband systems are more sensitive and why reducing the receiver bandwidth to match the signal improves the minimum detectable level.
How can a GPS or LoRa receiver detect a signal below the noise floor?
Through processing gain. A spread spectrum waveform occupies far more bandwidth than its information rate, and the receiver correlator concentrates the signal energy while averaging the noise, recovering a processing gain of 10·log₁₀ of the bandwidth divided by the information rate. That gain is subtracted from the demodulator SNR to give the effective SNR needed at the input, so the sensitivity drops by the processing gain and can sit tens of dB below the thermal noise floor. A GPS C/A signal spreads 50 bit/s across about 2 MHz for roughly 46 dB of gain, which is why it works far under the noise.
How do I check whether a datasheet sensitivity is realistic?
Compare it against the thermal floor for its bandwidth. The gap between the quoted sensitivity and the thermal floor is the sum of the noise figure and the required SNR, so it should be a positive number of a sensible size, typically 10 to 25 dB. If the quoted sensitivity is below the thermal floor for the stated bandwidth, it is physically impossible and the bandwidth or the figure has been misread. The Spec Audit mode does this automatically, flags the impossible case, and splits the budget into the implied noise figure and SNR.
What required SNR should I use?
It depends on the modulation and the target error rate. A simple detection threshold is 0 dB, analog SSB or AM voice needs about 10 dB, analog FM to 12 dB SINAD needs about 12 dB, digital voice like P25 or DMR reaches its reference error rate around 5 dB, QPSK needs about 10 dB, and 64-QAM needs around 22 dB. The Reference tab lists these as indicative ranges for orientation. They are not a specification, and the real figure is whatever the demodulator in your radio needs for the error rate you are designing to.
Does the range calculation include terrain and clutter?
No. The range figures use free space path loss alone, so they are an optimistic upper bound rather than a prediction. Real paths lose more to clutter, terrain, diffraction, building penetration, and rain or fog fade, and gain nothing back. The tool states the free space assumption explicitly and leaves the excess path loss and the fade margin to be added separately, so you can see the free space bound and then apply the site specific losses knowingly. For a full propagation prediction use a path loss or coverage tool.
Does any data leave my browser?
No. The calculator runs entirely in your browser. No bandwidths, sensitivities, or link parameters are submitted to a server. Useful for commercially confidential work, classified projects, or environments where information security policy prohibits sending engineering data to third party services.