Author Topic: ADALM-PLUTO as simple Spectrum Analyzer/w tracking (Read 14819 times)

albfer · « **on:** February 28, 2020, 02:08:25 pm »

HI All,

I wrote a windows application that work as Spectrum Analyzer/w tracking generator with SDR Devices (initial support for ADALM-PLUTO only).

Highlights:
- Spectrum Analyzer from 40MHz to 6015MHz, variable span from 2MHz to 5910MHz, marker and Max Hold features
- Spectrum Analyzer w/Tracking from 50MHz to 6000MHz (range 50MHZ->70MHz experimental), resolution from 50 to 1024 points, 0dB and -40dB calibration.
- Frequency generator from 50MHz to 6000MHz
- Configurable RX/TX level correction, with four curve embedded or with external files.

I distribute this application free of charge to the HAM radio community.

If you interested, visit the related page at my site http://www.albfer.com/en/2020/02/21/satsagen-2

See you soon!

Alberto

RoGeorge · « **Reply #1 on:** February 28, 2020, 02:49:17 pm »

Looks great, thank you!

This is a very nice surprise.

- IIRC it was not possible to use the same oscillator for the Tx and the Rx paths inside the AD9363, so it was not possible to control the phase between Tx and Rx. Did you find any tricks to overcome that?
- Will it be open source in the future?

I'm on Linux. This weekend I'll give it a try in Wine, and if it doesn't work, in a Windows VM.
Will let you know how it all went, thanks again!

Kalvin · « **Reply #2 on:** February 28, 2020, 06:02:06 pm »

Nice project, indeed!

Quote from: RoGeorge on February 28, 2020, 02:49:17 pm

- IIRC it was not possible to use the same oscillator for the Tx and the Rx paths inside the AD9363, so it was not possible to control the phase between Tx and Rx. Did you find any tricks to overcome that?

As far as I understood, this is a scalar network analyzer, not a vector network analyzer. I was playing with Pluto a year ago with a similar project for my antenna project with decently good results. Of course I wanted to make a vector network analyzer, but it was a painful observation that it was not possible to phase-lock the tx and rx oscillators in AD9363, so as far as know, Pluto cannot be used as a vector network analyzer. However, a scalar network analyzer is still a very useful and good tool. And of course, Pluto can be used as an SDR.

After playing with Pluto I decided to purchase miniVNA Tiny Plus. For hobby projects, the NanoVNA is also a nice, inexpensive tool for HF - UHF measurements. I think these tools (Pluto and VNAs) complement each other quite nicely.

albfer · « **Reply #3 on:** February 29, 2020, 07:19:55 am »

Thank you very much for your interest in my project!

Quote

- IIRC it was not possible to use the same oscillator for the Tx and the Rx paths inside the AD9363, so it was not possible to control the phase between Tx and Rx. Did you find any tricks to overcome that?

we working on that, but we don't found a cheap solution at the moment, it's more reasonable with another devices, probably.

Quote

- Will it be open source in the future?

it will likely become an Open Source library, meantime I am working on the porting of the application to other platforms.

I will look forward to the results of your tests in Wine!

Bicurico · « **Reply #4 on:** February 29, 2020, 02:24:02 pm »

Hello,

I am trying the software, but it does not work at all!

It starts, I can see the entry in the taskbar, but no window opens.

Any suggestion?

Regards,
Vitor

Bicurico · « **Reply #5 on:** February 29, 2020, 02:47:12 pm »

Got it to work.

The software does not like my three attached monitors!

I need to unplug one monitor for the window to appear on the desktop. i can than reconnect the third monitor.

Regards,
Vitor

albfer · « **Reply #6 on:** February 29, 2020, 03:16:18 pm »

Quote from: Bicurico on February 29, 2020, 02:47:12 pm

Got it to work.

The software does not like my three attached monitors!

I need to unplug one monitor for the window to appear on the desktop. i can than reconnect the third monitor.

Regards,
Vitor

Hello Vitor,

thank you, I will try to fix the problem in a multi-monitor system

Regards

Alberto

RoGeorge · « **Reply #7 on:** February 29, 2020, 05:11:50 pm »

Just tested it with some virtual machines:
- WinXPsp3 32bit virtual machine - all installs OK, but at start, satsagem.exe opens an err msgbox with the text "The procedure entry point inet_ntop could not be located in the dynamic link library WS2_32.dll."
- Win7sp1 64 bit virtual machine - IT WORKS, IT WORKS!!!

I have a 6GHZ spectrum analyzer /w generator.

Will try it with Ubuntu/WINE now.

RoGeorge · « **Reply #8 on:** February 29, 2020, 06:37:06 pm »

Ubuntu 18.10, Q4Wine 1.3.7, Wine-3.0.3:
- installed first the drivers, then the SATSAGEN, it starts, sees the ADALM-PLUTO
- 'Spectrum Analyzer' section appears to be working
- 'Generator' section half working, can change frequency, but can not turn the generated signal off, can change the TX Pwr numbers but the signal displayed by the SA always remains the same amplitude. For some reason, if the generator is set to 2402MHz, then the generated signal disappears from the display. Also note that the frequency can be changed, but is always shifted with 2 MHz, as seen in the attached picture, where the signal is still at 2405MHz instead of the 2407MHz (also note the generator is switched off and the signal is still generated).
- 'Spectrum Analyzer w/Tracking' section flashes the 'Calib. Req. 0dB', the red button can be pressed, but when the green button is pressed, instead of starting the calibration, the green button greys out itself and nothing happens on the display.

Since I don't know much about Wine, no idea how to debug that. I just run the driver installer, then the Satsagen installer, then made a shortcut to the installed satgen.exe and double click it from Wine.

For now, I'm very happy with the SATSAGEN working on Win7 VM, so I won't hammer Wine any longer.
Was waiting for such a nice tool since I bought the ADALM-PLUTO, thank you!

albfer · « **Reply #9 on:** March 01, 2020, 08:21:59 pm »

Quote from: RoGeorge on February 29, 2020, 06:37:06 pm

Ubuntu 18.10, Q4Wine 1.3.7, Wine-3.0.3:
- installed first the drivers, then the SATSAGEN, it starts, sees the ADALM-PLUTO
- 'Spectrum Analyzer' section appears to be working
- 'Generator' section half working, can change frequency, but can not turn the generated signal off, can change the TX Pwr numbers but the signal displayed by the SA always remains the same amplitude. For some reason, if the generator is set to 2402MHz, then the generated signal disappears from the display. Also note that the frequency can be changed, but is always shifted with 2 MHz, as seen in the attached picture, where the signal is still at 2405MHz instead of the 2407MHz (also note the generator is switched off and the signal is still generated).
- 'Spectrum Analyzer w/Tracking' section flashes the 'Calib. Req. 0dB', the red button can be pressed, but when the green button is pressed, instead of starting the calibration, the green button greys out itself and nothing happens on the display.

Since I don't know much about Wine, no idea how to debug that. I just run the driver installer, then the Satsagen installer, then made a shortcut to the installed satgen.exe and double click it from Wine.

For now, I'm very happy with the SATSAGEN working on Win7 VM, so I won't hammer Wine any longer.
Was waiting for such a nice tool since I bought the ADALM-PLUTO, thank you!

if you want to play SATSAGEN on wine again, there is a solution at the download page http://www.albfer.com/satsagen-download-page/ :
- download and execute SATSAGEN upg v. 0.2.0.3 (if a previously version is installed)
- run SATSAGEN, open settings and from tabsheet Extra check on Fix iio_channel_attr...

Thank you again!

Cheers

Alberto

RoGeorge · « **Reply #10 on:** March 01, 2020, 08:58:07 pm »

Satsagen v0.2.0.3 now works perfectly in Linux/Wine, too!

I used the upgrade version, satsagenupg_2.03.exe, and simply run it with Wine, without uninstalling v0.2.0.0. It all works correctly now, thank you.

You should rename it SATSAGEM, 'cause this is a gem tool for any ADALM-PLUTO owner.

albfer · « **Reply #11 on:** April 07, 2020, 04:31:42 pm »

Hi all!

the new version 0.2.2 of SATSAGEN is available at the link below:

http://www.albfer.com/satsagen-download-page/

Highlights of v. 0.2.2:

- Extension of analyzed band from 6 GHz to 12 GHz and beyond! (harmonic third mode)
- Multiplier offset RX/TX TSA in order to test amplifiers or multipliers
- Offset between transmitter and receiver in order to test conversion systems, like transverters
- Display and modify SA resolution bandwidth
- Save/Load TSA scans (by memory or files)
- VSWR unit
- Multiple TSA markers
- Multiple SA markers
- Calibration using a directional coupler or bridge, averaging open and short
- Generator/Sweeper Mode
- SA Span value - scale coherency
- Lock Zoom autoscale when TSA or SA restarts
- All knobs can drived by the mouse wheel
- Pause and step functionality
- Output sweep ramp with external USB D/A
- Backup and restore configuration to and from a file.
- Connection string Override
- Frequency reference setting

Video:

https://youtu.be/280YqpEZgj4

See you soon!

Cheers

Alberto

RoGeorge · « **Reply #12 on:** April 09, 2020, 01:51:54 pm »

Very nice, a very grateful thank you!

For those running SATSAGEN on Linux with Wine (here running Ubuntu 20.04 LTS and Wine 5.0), if there is an error like this one after pressing the 'Power' button inside SATSAGEN, with all the buttons greyed-out except for the 'Power' button:

Code: [Select]

09/04/2020 16:23:22 Connecting to ip:192.168.2.1
09/04/2020 16:23:22 Successfull connection to ip:192.168.2.1
09/04/2020 16:23:22 hw_model:Analog Devices PlutoSDR Rev.B (Z7010-AD9363)
09/04/2020 16:23:22 hw_model_variant:1
09/04/2020 16:23:22 hw_serial: ...
09/04/2020 16:23:22 fw_version:v0.28
09/04/2020 16:23:22 ad9361-phy,xo_correction:39999999
09/04/2020 16:23:22 ad9361-phy,model:ad9364
09/04/2020 16:23:22 local,kernel:4.9.0
09/04/2020 16:23:22 ip,ip-addr:192.168.2.1
09/04/2020 16:23:22 tx0_i scale a 0 return error Unknown error

then right click in the display area -> Settings -> Extra -> and check the checkbox 'Fix iio_channel_attr_write_double bad conversion'. Click 'OK', and then press off/on again on the 'Power' button in SATSAGEN. After this, the display grid should appear, and all the other buttons should now work, too.

Maybe you should mention about this in the download page, maybe put a note for Linux/Wine usage in the 'Extra' tab, too. I would have thought it is broken if I didn't know about this from the previous versions.

One more thing, what does the 'Power' do? Asking that because it feels to me like an unnecessary one more click. IMO, would be nice if 'Power' would be on by default, or even better, to remember the last state from the previous run (by autosaving the state of SATSAGEM settings and buttons at close, without asking, and auto-load them at the next run).

Later edit:

I think there is a minor bug with the 'TX Pwr' box, editing a number here is acting different from the other input boxes.

For example, if there is already a -40.0 written in the 'TX Pwr' box, double clicking the numbers will select the whole "-40.0", which is correct, but then, when start typing "-20" and "Enter", the old "40.0" number is not replaced with the typed number, ending with a positive "2040.0" instead of the desired "-20" typed, which after pressing 'Enter' will become "10.0". Also, simply pressing "-" seems to be toggling on and off the sign of the existing number, which is strange.

Later later edit:

All input boxes seems to act the same, it's the '-' sign that makes them behave strange. Inputting a positive number is working properly, only inputting a negative number makes them behave wrong.

RoGeorge · « **Reply #13 on:** April 09, 2020, 06:32:03 pm »

With the Spectrum Analyzer set as follows:
- "Frequency KHz" = 2 450 000, "Span MHz" = 100, "RX Gain" = 50.0
- "SA Max FFT Size" = 65536
- "MSample L." = 24, "FFT KSize" = 65
then it displays "RBW:2712Hz". By increasing to "MSample L." = 25, it displays "RBW:381Hz"

1. I don't understand, what "MSample L.", "FFT KSize" and "SA Max FFT Size" represents each, and what is the relation between them and the displayed "RBW", please?

2. Looks like a typo to me, shouldn't it be "kHz" with lower "k" instead of "KHz" with capital "K"?

albfer · « **Reply #14 on:** April 11, 2020, 01:34:15 pm »

Hi RoGeorge,

thank you again for your help, I have taken note of everything and I will try to insert the fixes in the next maintenance release.

I answer the question of point 1:

SATSAGEN may works in sweep mode by chunks of x MHz, depending of the Span and MSample Limit values inserted by the user.

MSample L. is the sampling rate value limit used of each chunk (for Pluto around of maximum 60 mega samples by second [MSPS]).
FFT KSize is the size of the fast Fourier transform process of each chunk.

For example, with 200MHz of Span and 40 of MSample L., the chunks are ten of 20MHz each: Span/(Span/(MSPS/2)).

The resolution bandwidth is sampling rate/FFT size, if we have used 8K of FFT size in the above example, RBW will be 4882: RBW=MSPS/FFTSize.

The SA Max FFT Size is the maximum value of FFTSize that user can set via RBW controls.
I have insert SA MAX FFT Size value in settings only as a precaution for mitigate performance issues in systems with poor hardware.

It's an argument a little hard to explain, I know.

I hope I have answered your questions.

Cheers

Alberto

RoGeorge · « **Reply #15 on:** April 13, 2020, 09:00:18 am »

Yes, that clarified the question perfectly, thank you.

Other nice to have for future SATSAGEN versions (so far playing with the SA and GEN sections only):

thousands separators, especially for frequency, because 4000000 kHz is much harder to read than 4 000 000 kHz.
the RBW indication on the display is very useful, would be nice to have that number displayed as a label near the buttons that adjust it, too, because when the display update is slow, there can be a considerable lag between turning the knob(s) and the apparition of the RBW value, making it hard to set to a desired value, need to turn a little, wait, turn a little more, wait again for visual feedback, and so on.
didn't looked in the datasheet, but I suspect the 65 displayed by FFT KSize should be 64, a power of 2.
turning the MSample L. knob from min to max, either with the mouse wheel or by drawing circles around, can take a lot of time. Would be nice (and also give a consistent behavior for the GUI) if all buttons will allow typing the desired number in a nearby box, like the knobs for frequency.

albfer · « **Reply #16 on:** April 15, 2020, 11:55:45 am »

Hi,

the new maintenance release v.0.2.2.1 of SATSAGEN is available at the link below:

http://www.albfer.com/satsagen-download-page/

- Fix AV libiio.dll when extend frequency range on new ADALM-PLUTO
- Fix inactive TXPwr control during Generator/Sweeper operation
- Fix of serial com open failure when close settings window
- Fix strange behavior of edit controls when pressing - key on all selected content
- Fix scaling of mouse wheel steps to accomodate Windows settings
- Fix updating markers values and title informations during hold state
- Fix not compliant BMP images saved and little improve of JPG quality
- Some little fixes of typo and other issues

Thank you!

Cheers

Alberto

albfer · « **Reply #17 on:** April 15, 2020, 11:59:50 am »

Quote from: RoGeorge on April 13, 2020, 09:00:18 am

Yes, that clarified the question perfectly, thank you.

Other nice to have for future SATSAGEN versions (so far playing with the SA and GEN sections only):
thousands separators, especially for frequency, because 4000000 kHz is much harder to read than 4 000 000 kHz.
the RBW indication on the display is very useful, would be nice to have that number displayed as a label near the buttons that adjust it, too, because when the display update is slow, there can be a considerable lag between turning the knob(s) and the apparition of the RBW value, making it hard to set to a desired value, need to turn a little, wait, turn a little more, wait again for visual feedback, and so on.
didn't looked in the datasheet, but I suspect the 65 displayed by FFT KSize should be 64, a power of 2.
turning the MSample L. knob from min to max, either with the mouse wheel or by drawing circles around, can take a lot of time. Would be nice (and also give a consistent behavior for the GUI) if all buttons will allow typing the desired number in a nearby box, like the knobs for frequency.

Hi RoGeorge,
I made some of your tips, others in the next releases.
Cheers
Alberto

albfer · « **Reply #18 on:** June 21, 2020, 12:32:49 pm »

Hi all!

On the SATSAGEN news page a video showing the marker operation of the coming soon version 0.3.1
http://www.albfer.com/en/satsagen-news/#content

Regards, Alberto

RoGeorge · « **Reply #19 on:** June 21, 2020, 01:50:06 pm »

That's good news. Spotted in the latest video a typo: "HZ", Hertz, should be written as Hz, capital H and lower case z (for example in the dropdown box "Unit", under the spectrum display area, and in the text annotations of the video). In full is Hertz, in honor of Heinrich Hertz. The old notation for frequency was in cycle/second and the fun of kilocycles (kc), megacycle (Mc) and less commonly kilomegacycle (kMc), for GHz.

Good idea laying that row of fast access buttons on the bottom.

9aplus · « **Reply #20 on:** June 21, 2020, 08:56:43 pm »

Hi Alberto,
Do you have plans to support Lime SDR soon ?

albfer · « **Reply #21 on:** June 22, 2020, 07:19:00 am »

not yet but it's a good idea!
Ciao
Alberto

Quote from: 9aplus on June 21, 2020, 08:56:43 pm

Hi Alberto,
Do you have plans to support Lime SDR soon ?

albfer · « **Reply #22 on:** June 23, 2020, 01:58:50 pm »

Hi All,

SATSAGEN v, 0.3.1 is ready to download!
http://www.albfer.com/en/satsagen-news/#content

regards, Alberto IU1KVL

RoGeorge · « **Reply #23 on:** June 23, 2020, 08:15:12 pm »

- I like the -POWERON start option

- removing the local oscillator image makes everything look very pro

- you've added so many new features and direct access buttons that it could be a major version increase
- the ability to choose an odd harmonic, up to the 9^th one, turns any ADALM PLUTO into a virtually 70MHz...54GHz tool. Don't tell the anti 5G movement that there are so many GHz in there!

- modulation modes for the generator will came in handy in many ways
- wow, you put a text to CW Keyer that can modulate the generator?! Nice, very nice!

Will play with SATSAGEN 0.3.1 this week, and let you know how it went, thanks for the new version.

LATER EDIT:
- spotted another typo, apart from the 'Unit' drop down menu ("HZ" instead of "Hz"), in the generator section, the harmonics instead of "3rd, 5rd, 7rd, 9rd", it should be "3^rd, 5^th, 7^th, 9^th". Only for 3 the termination is "rd", it came from "third". For the rest, the termination is "th", example, the fifth, seventh, and so on.

1, 2, and 3 are different, because they are spelled like first 1^st, second (2^nd) and third (3^rd), then the rest are "th", fifth (5^th), etc.

albfer · « **Reply #24 on:** June 27, 2020, 06:42:49 am »

Thank you so much, RoGeorge, I fix the label and the button of the toolbar also with the typo you have noticed.

Quote from: RoGeorge on June 23, 2020, 08:15:12 pm

- I like the -POWERON start option
- removing the local oscillator image makes everything look very pro
- you've added so many new features and direct access buttons that it could be a major version increase
- the ability to choose an odd harmonic, up to the 9^th one, turns any ADALM PLUTO into a virtually 70MHz...54GHz tool. Don't tell the anti 5G movement that there are so many GHz in there!
- modulation modes for the generator will came in handy in many ways
- wow, you put a text to CW Keyer that can modulate the generator?! Nice, very nice!

Will play with SATSAGEN 0.3.1 this week, and let you know how it went, thanks for the new version.

LATER EDIT:
- spotted another typo, apart from the 'Unit' drop down menu ("HZ" instead of "Hz"), in the generator section, the harmonics instead of "3rd, 5rd, 7rd, 9rd", it should be "3^rd, 5^th, 7^th, 9^th". Only for 3 the termination is "rd", it came from "third". For the rest, the termination is "th", example, the fifth, seventh, and so on.

1, 2, and 3 are different, because they are spelled like first 1^st, second (2^nd) and third (3^rd), then the rest are "th", fifth (5^th), etc.

albfer · « **Reply #25 on:** October 11, 2020, 08:40:41 am »

Hi all,

SATSAGEN v.0.4.0 is ready to download.
http://albfer.com/en/2020/10/11/satsagen-0-4/
Highlights:
- Dual device mode
- Generator with LO frequency output

ebclr · « **Reply #26 on:** October 12, 2020, 12:00:10 pm »

Grazie mille

albfer · « **Reply #27 on:** February 01, 2021, 07:57:56 am »

Hi all,

SATSAGEN 0.5.0.2 is available

-Works with:
- ADALM-PLUTO
- HackRF One
- RTL-SDR Dongles
- Simple Spectrum Analyzer series like NWT4000, D6 JTGP-1033, Simple Spectrum Analyzer, and so on.
- Video trigger, real-time trigger, and fast-cycle feature
- ADALM-PLUTO custom gain table and Extended linearization table for all devices
- Transmit from raw format files
- I/Q balance panel
- Waterfall
- RX/TX converter offset
- Video Filter average option
- Keyboard or mouse wheel moving markers
- Status Display

Waiting for you at https://www.albfer.com/en/2021/01/31/satsagen-0-5/

Let me know

Cheers

Alberto

RoGeorge · « **Reply #28 on:** February 01, 2021, 12:46:49 pm »

Wow, so many new features, thank you again!

Can hardly wait to try this new version on a PlutoSDR as Tx, together with an RTL-SDR for Rx.

Will let you know if any bugs will appear. So far just a question. In the https://www.albfer.com/en/2021/01/31/satsagen-0-5/ it is written

Quote

The standard gain table will be reloaded on the Pluto device at the power off of SATSAGEN to ensure the operation of other applications.

Is the gain table stored in a non-volatile place inside the PlutoSDR, or is it stored just in RAM and it will all revert to default if the PlutoSDR is unpowered then powered again?

For example, if by accident I unplug the USB cable from the PlutoSDR while the SATSAGEN is running (so without proper SATSAGEN shutdown to restor the original table), do I need to take any action to restore the default gain table from Analog Devices in order to use the PlutoSDR on another application or on another computer?

albfer · « **Reply #29 on:** February 01, 2021, 01:21:14 pm »

Thank you ROGeorge

The gain table is stored in RAM, a simple power cycle resets to the standard gain table.

The reload standard gain feature at the power off of SATSAGEN ensure the correct use of other applications in case of Pluto remains connected to the PC.

Cheers

Alberto

Quote from: RoGeorge on February 01, 2021, 12:46:49 pm

Wow, so many new features, thank you again!

Can hardly wait to try this new version on a PlutoSDR as Tx, together with an RTL-SDR for Rx.

Will let you know if any bugs will appear. So far just a question. In the https://www.albfer.com/en/2021/01/31/satsagen-0-5/ it is written
Quote
The standard gain table will be reloaded on the Pluto device at the power off of SATSAGEN to ensure the operation of other applications.
Is the gain table stored in a non-volatile place inside the PlutoSDR, or is it stored just in RAM and it will all revert to default if the PlutoSDR is unpowered then powered again?

For example, if by accident I unplug the USB cable from the PlutoSDR while the SATSAGEN is running (so without proper SATSAGEN shutdown to restor the original table), do I need to take any action to restore the default gain table from Analog Devices in order to use the PlutoSDR on another application or on another computer?

albfer · « **Reply #30 on:** November 08, 2021, 02:05:43 pm »

Hi All!

A new version is available to download...

SATSAGEN v.0.6.0.1

Highlights:

Spectrum Analyzer
-A Harmonic Mode (ADALM-PLUTO device only)
-A Unwanted signal components filter
-I Sweep time speeded up (ADALM-PLUTO device only)
-A Span-RBW coupled/uncoupled selector
-A FFT Rect Windowing selector
-A X-Zoom locked

Spectrum Analyzer w/Tracking
-A Scan progress bar
-A TX OFF button

Generator
-A Frequency and modulation amplitude controls
-A Up to three simultaneous signals for intermodulation measurements
-A Pseudorandom noise generator with notch filters for NPR measurements
-A ASK and FSK modulations

Devices
-A ADALM-PLUTO clones support (for rx/tx linearization only)
-A AD8317 and AD8318 Log Detectors (USB D/A interface v.3.0 required)
-I Simple spectrum analyzer devices protocol improved

Miscellaneous
-A Virtual Analog Power Meter for Log Detectors devices
-A Multisession support. Launch SATSAGEN with -config n parameter

Regards

Alberto

RoGeorge · « **Reply #31 on:** November 08, 2021, 04:45:00 pm »

Wow, so many new features.

On my Kubuntu 20.04 LTS + wine, the text behave differently. Numbers are much bigger and come in many sizes, sometimes they auto-change their size while typing/editing a number, and in the end it is displayed either truncated or as 00, like for example the Rx frequency in the attached capture.

Not sure if this is because some settings/updates in WINE, or because this version of SATSAGEM is different. I can still read the numbers by hovering the cursor and reading it in the tooltips popup, just that that the interface is harder to operate.

I'll let you know any further questions, and thanks!

coppercone2 · « **Reply #32 on:** November 08, 2021, 05:23:38 pm »

I tried Pluto and raspi with two power banks and it worked... appealing portable device

albfer · « **Reply #33 on:** November 09, 2021, 09:47:46 am »

Wow! Give me a picture of your setup, please!

Quote from: coppercone2 on November 08, 2021, 05:23:38 pm

I tried Pluto and raspi with two power banks and it worked... appealing portable device

RoGeorge · « **Reply #34 on:** November 09, 2021, 10:18:35 am »

I'd be curious, too, of how it looks like on RPi.

Meanwhile I've tried SATSAGEN v0.6.0.1 on Windows 10, and it all looks great.
All the controls are working as expected.

albfer · « **Reply #35 on:** November 09, 2021, 01:11:41 pm »

Hi!

Thank you so much for your comment!

It seems to be a font combination issue.

On my Ubuntu 20.0.4 works fine.

Regards

Alberto

Quote from: RoGeorge on November 08, 2021, 04:45:00 pm

Wow, so many new features.

On my Kubuntu 20.04 LTS + wine, the text behave differently. Numbers are much bigger and come in many sizes, sometimes they auto-change their size while typing/editing a number, and in the end it is displayed either truncated or as 00, like for example the Rx frequency in the attached capture.

Not sure if this is because some settings/updates in WINE, or because this version of SATSAGEM is different. I can still read the numbers by hovering the cursor and reading it in the tooltips popup, just that that the interface is harder to operate.

I'll let you know any further questions, and thanks!

RoGeorge · « **Reply #36 on:** November 09, 2021, 02:20:34 pm »

Found it!

It was the setting in the "winecfg" window.

The "Screen resolution" inside the tab "Graphics" slider must be set to 96 dpi (the default in Windows). Mine was set to 168, in order to display larger text in other programs running under WINE on a 4k monitor, like LTSpice or QucsStudio. Once the dpi is set to 96, it all looks just like it would run on Windows.

RoGeorge · « **Reply #37 on:** November 14, 2021, 07:35:04 pm »

It happened that this weekend I've installed FreeBSD on ZFS with KDE Plasma.
Tested SATSAGEN out of curiosity, and it worked just fine on FreeBSD, too!

Just like in Linux, use WINE to install and run SATSAGEN on FreeBSD. No drivers needed. In my setup I had to manually bring up the LAN over USB network adapter with a fixed IPv4 address (that's how ADALM-PLUTO will be seen).

coppercone2 · « **Reply #38 on:** November 16, 2021, 12:03:06 am »

well I broke the system down and all the parts went to other locations (cars), and the rpi is hooked up to something doing something right now so it will have to wait a while

The problem mine had was the "offset" in the middle of a spectrum created by what the program authors described as 'i/q imbalance offset'. The features that are added to the receiver programs (gnu radio, etc) designed to compensate for this offset did reduce it a little bit, but there was always a glaring line stuck in the middle of the spectrum, which irritated me. I tried to study this on forums for a little while but it seems that people have decided that its not really fixable. Other then it being slow to boot, it seemed OK, but I did not use it much. I thought about CM filters on the Pbanks and stuff but it seems that no matter what I do the project result will feel janky.

I thought to turn it into a laptop in a old box but its alot of work. It pisses me off too because the offset line is smack dab in the middle, even on a normal spectrum analyzer the useless left hand low frequency 'slope' is.. on the left hand. Whenever I looked at the SDR on my TV I wanted to get a rag and try to wipe off the line in the middle. As I understand it, its not a spectrum analyzer, and the real world uses don't care about it, but I wanted a 'fast signal scanner' to use in combination with other equipment, and quite frankly the IQ line ruined it visually. I just wanted it so I can see the spectrum in real time on the TV when I play with my tecsun radio... so the pi was just supposed to be a log/note book where I can write things and a spectrum viewer so I know how to setup the tecsun (just to look at the air band, since I was only able to get very spare audio from planes, I was trying to increase my probability of intercept, so I can squeeze something out of that little portable receiver on VHF in the living room)

https://www.reddit.com/r/RTLSDR/comments/93rewt/bought_a_plutosdr_and_i_have_a_static_line_in_the/

its like if you took a sharpie and drew a fake sine wave on your oscilloscope thats always there!

albfer · « **Reply #39 on:** November 16, 2021, 04:09:07 pm »

The local oscillator feedthrough can be filtered, enabling LO Flt or E Flt controls using the SATSAGEN application.
Cheers
Alberto

Quote from: coppercone2 on November 16, 2021, 12:03:06 am

well I broke the system down and all the parts went to other locations (cars), and the rpi is hooked up to something doing something right now so it will have to wait a while

The problem mine had was the "offset" in the middle of a spectrum created by what the program authors described as 'i/q imbalance offset'. The features that are added to the receiver programs (gnu radio, etc) designed to compensate for this offset did reduce it a little bit, but there was always a glaring line stuck in the middle of the spectrum, which irritated me. I tried to study this on forums for a little while but it seems that people have decided that its not really fixable. Other then it being slow to boot, it seemed OK, but I did not use it much. I thought about CM filters on the Pbanks and stuff but it seems that no matter what I do the project result will feel janky.

I thought to turn it into a laptop in a old box but its alot of work. It pisses me off too because the offset line is smack dab in the middle, even on a normal spectrum analyzer the useless left hand low frequency 'slope' is.. on the left hand. Whenever I looked at the SDR on my TV I wanted to get a rag and try to wipe off the line in the middle. As I understand it, its not a spectrum analyzer, and the real world uses don't care about it, but I wanted a 'fast signal scanner' to use in combination with other equipment, and quite frankly the IQ line ruined it visually. I just wanted it so I can see the spectrum in real time on the TV when I play with my tecsun radio... so the pi was just supposed to be a log/note book where I can write things and a spectrum viewer so I know how to setup the tecsun (just to look at the air band, since I was only able to get very spare audio from planes, I was trying to increase my probability of intercept, so I can squeeze something out of that little portable receiver on VHF in the living room)

https://www.reddit.com/r/RTLSDR/comments/93rewt/bought_a_plutosdr_and_i_have_a_static_line_in_the/

its like if you took a sharpie and drew a fake sine wave on your oscilloscope thats always there!

coppercone2 · « **Reply #40 on:** November 16, 2021, 09:02:38 pm »

hmm, maybe that prgoram will do it. Nothing I got to work on the raspi managed the line. The spectrum you have is very clear.

I will try it some time to see if it ressurects the project

albfer · « **Reply #41 on:** June 01, 2022, 08:37:23 am »

Hi all,

VNA with a Pluto revision C and SATSAGEN v.07.1.4, read more at https://www.albfer.com/en/2022/05/29/satsagen-v-0-7-1-4/#content

Cheers

Alberto

ozkarah · « **Reply #42 on:** June 28, 2022, 09:31:27 pm »

Great work man. Congrats.

Do you have any results on the flatness of the ADALM PLUTO tracking generator? Especially in 50-500 MHz frequencies..

rfclown · « **Reply #43 on:** January 28, 2023, 11:12:48 pm »

I can't believe that I just ran across this program. Amazing work Alberto. I just downloaded v0.7.2.0. I was starting to work on a spectrum analyzer thing in LabVIEW this week. I hadn't figured how I was going to deal with the filters; equalize, or just use a portion of the spectrum that was fairly flat. Now I don't have to do anything. I've been using the Pluto for a while now as a signal generator, but hadn't done anything useful with the receiver.

I set the frequency of the Spectrum Analyzer and Generator to an arbitrary 1GHz, and varied the span 1,2,3..12MHz. Interesting that some spans don't kill the carrier (1,11 and 12 MHz for instance) while others do what I expected from the Pluto Rx and nulled the signal like it was a DC offset. Maybe on some spans the center isn't really the programmed value?

The Fast-Cycle and MaxHold enable me to do what I was needing at the moment to help debug a Bluetooth issue. I was borrowing a RSA506B last week to do some field work. Now I can do what I need for that task with a Pluto+SATSAGEN. I had brought a Pluto along for a signal source and a nanoVNA to check cables and antennas. I can probably do it all in the future with this and a directional coupler.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: ADALM-PLUTO as simple Spectrum Analyzer/w tracking (Read 14819 times)

Share me