SDR# SDR# Plug-in: Frequency Scanner updated

[thewraith2008]

Glad it helped,

The reality is, not all SDR# plug-ins are compatible with each other.
It's easier to just setup a SDR# for each purpose you wish to use it for. Prior to SDR# v1717 the size was only about 6 Mb.



Latest version (v1.4.1.0) can be found here: MEGA - Download

 

[Andyjuk]

Installed with SDR# 1700 and 1732 without the Community package.
No problems so far. Logging seem to be working well.
I just wish I'd known about this plugin before I bought a Bearcat BCT15X a few weeks ago.
It's just as sensitive and runs rings around the BCT15X for speed. 230 to 390 MHz in 1.9 seconds !
I'm running an ancient AOR 3000A, the 15X and an Airspy R2 with SDR#, Diamond 777 antenna and Cross Country Wireless antenna splitter so I can compare all three.

Thanks and keep up the good work.

 

[thewraith2008]

As of SDR# 1740, the problem with the channel analyzer panel when in the position 'Up', has now been fixed. (see image)
This fix is in SDR# not in the Frequency scanner plug-in, so no update of plug-in is required.

Latest version (v1.4.1.0) can be found here: MEGA - Download

 

[PatrickPierre73]

Hi there !

I've been playing with 1.4.1.0 version for a few days, and really enjoy it.

Something puzzles me though : I can"t get the "Show session hits" option to display the real number of hits. The value in brackets remains (0) regardless of the number of scan stops on a given frequency.
Am I doing something wrong or is it a known "problem" ? Thanks

 

[thewraith2008]

Hi there !

I've been playing with 1.4.1.0 version for a few days, and really enjoy it.

Something puzzles me though : I can"t get the "Show session hits" option to display the real number of hits. The value in brackets remains (0) regardless of the number of scan stops on a given frequency.
Am I doing something wrong or is it a known "problem" ? Thanks

You would need to make sure that logging is enabled.

I have already changed that for a future version as well as a fix for the "8.33Khz channel selector" with newer SDR# versions (1740+).
When I get some time I'll package it up and upload it.



Latest version (v1.4.1.0) can be found here: MEGA - Download

 

[PatrickPierre73]

Thanks for the prompt reply.
I wasn't aware that 'logging' had to be enabled. And it wasn't.

as well as a fix for the "8.33Khz channel selector" with newer SDR# versions (1740+)

Just out of curiosity, what is the problem with the 8.33 step and latest SDR# versions ? (I'm currently running 1733, but I was about to download 1763 that was released today).

 

[thewraith2008]

Just out of curiosity, what is the problem with the 8.33 step and latest SDR# versions ? (I'm currently running 1733, but I was about to download 1763 that was released today).

Fixed: 8.33 Khz channel selector ("Configure > General")
- SDR# v1740+ changed the step size of "8.33 kHz" [8330] to "8.3333 kHz" [8333]
  Because of this, the "8.33Khz channel selector" was not enabled in these newer versions.

This only affects the manual (frequency) tuning of SDR# (if option enabled) and is not part of the step size used for the scanner itself.

 

[mancow]

Where is 8.33 used? I've never encountered an 8.33 frequency that I know of.

 

[thewraith2008]

Where is 8.33 used? I've never encountered an 8.33 frequency that I know of.

The 8.33 KHz step size is used in the 118-137 MHz aviation band.
It was created to increase available channels in busy regions (i.e. Europe)



Latest version (v1.4.1.0) can be found here: MEGA - Download

 

[rumcajs_tr]

Great plugin and excellent work!
One suggestion - Would it be possible to combine it with the CTCSS/DCS decoders plugins to record not only found frequency but also tone? Often, the active tone indicates, that there is a real traffic on the channel, not just random QRM.

 

[BetaCygni]

Hi thewraith2008,
Great functionality, thank you! Could a future version please have CSV logging field options for signal duration and maximum signal strength during that duration and time in 24 hour clock please (as BCTool+ used with my BCT-15X has)? The first 2 would help separating interference from genuine signals and the last would simplify parsing with external scripts.
Many thanks BetaCygni

 

[thewraith2008]

Hi thewraith2008,
Great functionality, thank you! Could a future version please have CSV logging field options for signal duration and maximum signal strength during that duration and time in 24 hour clock please (as BCTool+ used with my BCT-15X has)? The first 2 would help separating interference from genuine signals and the last would simplify parsing with external scripts.
Many thanks BetaCygni

At this point, only the option to use 24hr timestamp in the log has been added.
Not sure about adding "signal duration and maximum signal strength during that duration"
A log entry is created at initial signal detection so duration is not possible.
I have added a SNR value (as returned by API) for testing but as above, this value is captured at initial signal detection and may not be the stabilized and expected value.



Latest version (v1.4.1.0) can be found here: MEGA - Download

 

[BetaCygni]

Hi thewraith2008,
OK Yes understand that you can't write the duration if you're creating the log entry at the start not the end of the transmission. Also understand re the possibly un-stabilised SNR value. Thought it was worth asking.
Thanks again for the great update
Cheers BC

 

[thewraith2008]

This is a update v1.4.4.0 to the great Frequency Scanner plug-in for SDR#.

This plug-in version adds/changes and fixes some items:

1.4.4.0 - Released

Added: Logging keyword to use for activity log.
- Use 'time_24h' to output time in 24 hour format

Added: Auto skip - 'Reset timer on over'
- When enabled, will reset the auto skip timer (if 'Auto Skip' is enabled) on every 'over' seen.
  This will allow longer on going activity to continue without triggering the auto skip.
  If a carrier, single over or single/multiple overs on a repeater is greater than the set duration, then auto skip will trigger.

1.4.3.0 - Not released

Changed: The logging of session hit totals is now enabled independently of the frequency activity logging.
- Hit totals logging is enabled in Configure > Channel Analyser > 'Log totals at end of each session'

Changed: UI labelling for channel analyser positions and some logging options

1.4.2.0 - Not released

Added: Logging - Output session frequency activity hit count totals
- Filename: 20xx_xx_xx_session_activity_hits.txt (saved in location set by "LOG file save path" in "Configure > Logging")
  Log has start/end date/time, scan mode, selected ranges and each entry has "frequency[Hz]: Group - Name [session hit totals for frequency]"
- To use, enable both "Enable logging" and "Show session hits (for frequency activity)"

Fixed: 8.33 Khz channel selector ("Configure > General")
- SDR# v1740+ changed the step size from "8.33 kHz" [8330] to "8.3333 kHz" [8333]
  Because of this, the "8.33Khz channel selector" could not be enabled correctly in these newer versions.

Updated: PDF Documentation
- Please read it

see changelog.txt for more details

NOTE: The core of the scanning logic has not been changed.

Documentation has been created to help with it's installation and usage, please read it.
NOTE: Support is not guaranteed. Especially if the answers are contained in the documentation or on this forum.

I have tried to be as thorough as possible with the documentation to explain usage and features.
I believe any questions can be answered by reading this documentation.
This documentation most likely is not complete and may contain errors and is not laid out as good as it could be.

Testing has mainly been done with SDR# 1700.
Limited testing has been done with SDR# 1765.
NOTE: SDR# has been going through some changes (1732+) and the new features may see this plug-in play up.


Download
NOTE: Use 7zip or WinRAR to extract files from the .7z file and read the .PDF file for installation and usage of files with SDR#.

HASH: bffa575ffeecd0404d5d63fb96eaca40

 

[rumcajs_tr]

Thanks for your work!
Regarding my question about CTCSS / DCS functionality with the scanner and recorded hits, is there any chance of implementing this?

 

[thewraith2008]

Thanks for your work!
Regarding my question about CTCSS / DCS functionality with the scanner and recorded hits, is there any chance of implementing this?

At the moment, probably none.
Not really sure of the impact on performance for adding such a thing.
If I did look at adding, it would probably only be CTCSS as I have never seen DCS been used around here.



Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here

 

[rumcajs_tr]

Understod. Implementing this would require major changes to the plugin. At least for storing the ctcss information. Also, this would either require dependency on separate ctcss plugin installed or implementing simple ctcss detection directly into the frequency scanner plugin. I also agree, that 99,5% is ctcss not dcs. Regarding the impact on the scan speed, of course the detection would trigger only after a signal hit so I guess no impact on the scan speed. When no ctcss is found, the the record would be without it.
On the other hand this would be a total game changer in searching for new frequencies. Imagine running sdr# with this plugin while at work and just recording hits with ctcss when you come home. Same as with the Uniden Discovery function, but 100 times faster.
Anyway, I hope that You might consider adding this somewhere in the future.
Thank you 😊

 

[PatrickPierre73]

Fixed: 8.33 Khz channel selector ("Configure > General") - SDR# v1740+ changed the step size from "8.33 kHz" [8330] to "8.3333 kHz" [8333]

A stupid question : if still running SDR# 1733 (or even previous versions), do you recommand using 1.4.4.0 or will this update be a problem with the "old" 8.330 SDR# step size ?
Thanks a lot.

Best regards.

 

[thewraith2008]

A stupid question : if still running SDR# 1733 (or even previous versions), do you recommand using 1.4.4.0 or will this update be a problem with the "old" 8.330 SDR# step size ?
Thanks a lot.

Best regards.

Frequency Scanner v1.4.4.0 will work with versions of SDR# from v1700-1765. (May some earlier and later versions)

The fix (to the 8.33 KHz channel selector) was made to work with the SDR# (internal) step size value of 8330 or 8333.
The issue did not affect the scanning part of the plug-in. (where you define the scan ranges)



Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here

 

[radiostationx]

Hi thewraith2008, using latest version v1.4.4.0, Thanks for this. Is there a chance that this setting (from an old version) can be returned.
MTIA