SDR# SDR# Plug-in: Frequency Scanner updated

[hamradionl]

I use the old ranges for AIR VHF - UHF i install in 2020. I try again a fresh install mabe it helps SDR# is funny program.
By the way,
Some old version was possible to move the red / yellow buttons to separate window (not be inside the scanner it self). the new version cant find these settings?

 

[Magpie]

The yellow and red line are still present in v2213. Suggest you copy the latest dll into the SDR# folder.

 

[hamradionl]

The yellow and red line are still present in v2213. Suggest you copy the latest dll into the SDR# folder.

The up/down buttons

 

[gnirtS]

I guess this thread is the best place for it.

I think i already know the answer but want confirmation....
I assume SpyServer (Pi) wont work in combination with this?

This plugin works fine natively on my laptop and likewise SpyServer works perfectly on the Pi4 (hardwired lan).
However when scanning it appears to work but doesnt see a single signal or stop at all despite transmissions being visible on the waterfall.

I can think of various reasons why this wont work but just in case ive missed some settings can someone confirm this?

Airspy Mini / Pi4 2gb / Gigabit wired network.

 

[thewraith2008]

The Frequency Scanner requires the full IQ bandwidth (of the SDR) to work correctly.
I'm not 100%, but I'm sure I read it somewhere that SpyServer only sends full IQ data of the IF filtered bandwidth and the rest is only FFT data of the remaining spectrum.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[gnirtS]

That may well be correct - the "Use Full IQ" is greyed out and i havent found any way at all to enable it.

 

[hamradionl]

AIRSPY R2 - 10 MSPS
setup scan ranges i the scanner config
Air scan 8.330 KHz steps scan range 118 - 137 is work fine and very fast

Air scan 5 KHz steps scan range 225 -390
this give lots of trouble, hangs, stops, crashes, screen freezes or the scan speed seem get slower after minutes ending in a full hang or freeze SDR#
One thing notice the mouse not or very slow responding to clicks, while screen freezes
CPU = 25 - 45%
test in clean SDR# install
SDR# 1700 + scanner 2.0.0.0
SDR# 1700 + scanner 2.1.0.0
SDR# 1700 + scanner 2.2.0.0
SDR# 1700 + scanner 2.2.10
SDR# 1700 + scanner 2.2.13 2 files SDR# map
SDR# 1784 + scanner 2.2.13 2 files
SDR# 1854 + scanner 2.2.13 2 files plugin map

 

[thewraith2008]

That may well be correct - the "Use Full IQ" is greyed out and i havent found any way at all to enable it.

I think you stop playing SDR# (after it's connected) then "Use Full IQ" is enabled.
It may only be available when smaller samplerates are used.
You will probably see a lot of dropped samples using it with higher samplerates.
Small bandwidths (samplerates) are not good to use with Frequency Scanner but as I said, I don't think it will work via spyserver anyway.

AIRSPY R2 - 10 MSPS
setup scan ranges i the scanner config
Air scan 8.330 KHz steps scan range 118 - 137 is work fine and very fast

Air scan 5 KHz steps scan range 225 -390
this give lots of trouble, hangs, stops, crashes, screen freezes or the scan speed seem get slower after minutes ending in a full hang or freeze SDR#
One thing notice the mouse not or very slow responding to clicks, while screen freezes
CPU = 25 - 45%
test in clean SDR# install
SDR# 1700 + scanner 2.0.0.0
SDR# 1700 + scanner 2.1.0.0
SDR# 1700 + scanner 2.2.0.0
SDR# 1700 + scanner 2.2.10
SDR# 1700 + scanner 2.2.13 2 files SDR# map
SDR# 1784 + scanner 2.2.13 2 files
SDR# 1854 + scanner 2.2.13 2 files plugin map

Scanning large ranges with a small step sizes will kill performance always.
The issue is with the channel analyzer having to update something like 33000 channels (225-390 MHz @ 5KHz) on every pass.

Using 'Auto suspend draw' (for the channel analyzer) may help when it triggers to reduce CPU usage and possible improving performance.
Breaking up the ranges and using expected step sizes also may reduce channel count improving performance.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[W4KRR]

I'm using v2.2.13.0 with SDR# v1854.

I've noticed that, depending on the frequency range I'm scanning, the frequency display at the top of the SDR# screen doesn't change. For example, when I scan the VHF railroad frequencies, 160.215 to 161.565MHz, the frequency at the top of the SDR# window will be stopped on some random railroad frequency. This gives the appearance that it isn't scanning. But it is, because when a frequency becomes active it will display the correct frequency. But when scanning the VHF aircraft band, 118 to 136 MHz, the frequency display at the top of the SDR# window changes as it's scanning.

Is this expected behavior?

Also: Should the step size that is specified in the scan range window override any step size that is selected in SDR#?

And: The padlock icons don't appear to do anything. Unless I'm doing something wrong.

 

[hamradionl]

With all the air traffic (many c17's) over west europe from UK to central Eu, i try monitor Mil Air UHF. Not very succesfull to be honest

SDR# 1700
When i stop the scanner, the analyser (SDR#) freezes completely (Audio still there) for about 1 - 3 minutes before scanner window close it self and the analyser (SDR#) is back to live.
SDR# 1854 It look like not suffer from this "freezing".

 

[thewraith2008]

I'm using v2.2.13.0 with SDR# v1854.

I've noticed that, depending on the frequency range I'm scanning, the frequency display at the top of the SDR# screen doesn't change. For example, when I scan the VHF railroad frequencies, 160.215 to 161.565MHz, the frequency at the top of the SDR# window will be stopped on some random railroad frequency. This gives the appearance that it isn't scanning. But it is, because when a frequency becomes active it will display the correct frequency. But when scanning the VHF aircraft band, 118 to 136 MHz, the frequency display at the top of the SDR# window changes as it's scanning.

Is this expected behavior?

If your scan range is 160.215 to 161.565MHz and your SDR is > 1.35MHz wide, then the VFO will only change when a frequency is active within that range as you have seen. This is normal as the scan range does not require any addition tuning of segments.

The channel analyzer signal levels been updated is usually the only indicator of scanning activity (as well as 'Scan >>>') when scanning small scan ranges, but this can be harder to see if using the dynamic noise floor option.

I have thought about adding a basic animation of the 'Scan >>>', 'Scan <<<' text in the channel analyzer panel, but I'm not sure that would help that much to further indicate that there is actually something going on in these cases.

Also: Should the step size that is specified in the scan range window override any step size that is selected in SDR#?

Yes

And: The padlock icons don't appear to do anything. Unless I'm doing something wrong.

They are disabled while scanning to prevent random/accidental clicking.
On larger scan ranges, it maybe harder to see the individual frequency that the lockout state was changed on. Use the zoom.


Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[hamradionl]

to remove the scanner (grey, red and Yellow buttons) out of the scanner window, like below the scanner window?
How to?

 

[thewraith2008]

to remove the scanner (grey, red and Yellow buttons) out of the scanner window, like below the scanner window?
How to?

You can't.
Use the 'Buttons alpha' option to reduce buttons visibility while scanning.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[hamradionl]

Understand its the airspy scanner

 

[TDR-94]

Has anyone used the Frequency Scanner with DSDPlus? When I have the DSDPlus plugin active and select scan on the frequency scanner, DSDPlus emits unsquelched noise the entire time. Is there anyway to have it squelched or muted until the Frequency Scanner actually stops on a frequency, the way the Frequency Scanner normally works when not using DSDPlus?

 

[Sparky_ND]

I scan a mix of p25 and analog for a zello feed 24/7. Under control select "passive digital monitor", and under input select "monitor source audio if no sync and signal present" if your scanning a mix, if it's all digital you can select no source monitoring and eliminate he squelch noise at the beginning of transmissions.

 

[TDR-94]

I scan a mix of p25 and analog for a zello feed 24/7. Under control select "passive digital monitor", and under input select "monitor source audio if no sync and signal present" if your scanning a mix, if it's all digital you can select no source monitoring and eliminate he squelch noise at the beginning of transmissions.

Where are these settings located? In the DSDPlus plugin or in the Frequency Scanner?

 

[Sparky_ND]

Where are these settings located? In the DSDPlus plugin or in the Frequency Scanner?

In the standalone dsdplus software, you'll have to use vbcable or something similar to connect the audio, there's a few tutorials on YouTube on how to use dsdplus with viritual audio cable software. I'd post up a link but it's already past my bedtime.....

 

[TDR-94]

In the standalone dsdplus software, you'll have to use vbcable or something similar to connect the audio, there's a few tutorials on YouTube on how to use dsdplus with viritual audio cable software. I'd post up a link but it's already past my bedtime.....

I've never seen those settings in DSDPlus 1.101 Looks like you are using DSD+ Fastlane.

 

[slicerwizard]

Has anyone used the Frequency Scanner with DSDPlus? When I have the DSDPlus plugin active and select scan on the frequency scanner, DSDPlus emits unsquelched noise the entire time. Is there anyway to have it squelched or muted until the Frequency Scanner actually stops on a frequency, the way the Frequency Scanner normally works when not using DSDPlus?

Are you sure it's DSD+ making the noise? I don't see any options in DSD+ 1.101 to pass raw source audio.