5:10 besides the signal-generating NanoVNA-F v2, the signal-receiving SDRplay RSPdx could also contribute to the frequency measurement being off by what is specified on the sending side.
17:57 maybe plus-minus mistake? (assuming the "tinySA Ultra" shows correct values): with the receiving "tinySA Ultra" showing 10.1 dBm, and cable attenuation at 1 dBm, the sending side provides 11.1 dBm; but the sending "tinySA" is configured to send at 9.0 dBm. So it seems the "tinySA" is actually sending with more energy than what is configured.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
5:10 besides the signal-generating NanoVNA-F v2, the signal-receiving SDRplay RSPdx could also contribute to the frequency measurement being off by what is specified on the sending side.
This is indeed true. I need to invest in a frequency standard !
17:57 maybe plus-minus mistake? (assuming the "tinySA Ultra" shows correct values): with the receiving "tinySA Ultra" showing 10.1 dBm, and cable attenuation at 1 dBm, the sending side provides 11.1 dBm; but the sending "tinySA" is configured to send at 9.0 dBm. So it seems the "tinySA" is actually sending with more energy than what is configured.
That could well be true. The tolerance on this equipment is probably much higher than 1dB anyway.
Could it be that the Tiny SA was showing -db errors because of the noise floor (-28dbm from tiny SA with the -40db attenuator)?
That's a good point !