# LimeSDR full span Spectrum Analyzer

**URL:** <https://discourse.myriadrf.org/t/limesdr-full-span-spectrum-analyzer/6248>\
**Category:** General Discussion\
**Created:** [27 June 2020 04:12 UTC](https://discourse.myriadrf.org/t/limesdr-full-span-spectrum-analyzer/6248 "2020-06-27T04:12:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mzs](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/mzs/32/2678_2.png) [@mzs](https://discourse.myriadrf.org/u/mzs)\
**Post date:** [29 June 2020 12:50 UTC](https://discourse.myriadrf.org/t/limesdr-full-span-spectrum-analyzer/6248/5 "2020-06-29T12:50:32Z")

</div>

You could always try doing it the original way, that was a slower manual two step process, without any GUI:

1. So you would collect power at each frequency into to a flat CSV text file over a number of minutes/hours/days, depending on your number of runs and integration time on each, using something like [https://github.com/xmikos/soapy\_power](https://github.com/xmikos/soapy_power) (there are others).
2. And then you would render that collected data into an image that a human can see and actually understand: [http://kmkeen.com/rtl-power/](http://kmkeen.com/rtl-power/) (scroll down to " Rendering"), as long as the selected output file format is compatible any of the rendering tools should work.

At a very minimum it may help you narrow down if the problem is with soapy\_power , with qspectrumanalyzer, or even an unexpected parameter being provided.

---

_[View the full topic](https://discourse.myriadrf.org/t/limesdr-full-span-spectrum-analyzer/6248)._