thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
I've never seen that option before, what's it do?
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
SDR# SDR# Plug-in: Frequency Scanner updated
- Thread starter thewraith2008
- Start date
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
causeway74
Member
- Joined
- Jan 6, 2017
- Messages
- 53
I suspect it takes the value of the checkbox beside each frequency in Frequency Manager to determine what to scan.
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
To which checkbox do you refer, I don't have any next to frequencies.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
causeway74
Member
- Joined
- Jan 6, 2017
- Messages
- 53
To which checkbox do you refer, I don't have any next to frequencies.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
is this the standard FreqMan plugin? The vasili option has a checkbox beside each frequency.
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
I use the one that comes with SDR#, never used the other one.
I'll have to look into it one day to see if it works with scanner plug-in.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
I'll have to look into it one day to see if it works with scanner plug-in.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
The alternative that Vasili wrote will likely not work well with 'skinned' sdrsharp versions. If that is the case then it's probably a bit of a dead-end* for most users** of sdrsharp
* without extra work on that specific plugin as well
**most users will be opting for new versions and pretty much every new user will download the latest version rather than search out v1700 (or similar pre-Telerik ones)
rumcajs_tr
Member
Hello,
I have one suggestion for improving the scanner plugin - to add "avoid ranges".
Explanation: when I define search ranges (from-to), the range is for example 440 - 470 MHz with 12.5kHz step. But there are two "gaps" which I would like to avoid - 457,40-458,50 and 467,40-468,55. Right now, that means that I have to define 3 ranges instead one (440,00-457,40, 458,50-467,40 and 468,55-470,00) which causes of course slower scan as the AirSpy has 8MHz range so it tunes the band in each defined range. OR I can define the range as 440-470 and manually click and lock out the desired frequencies one-by-one in the scanner interface on the bottom of the screen, but this is quite time consuming and when I reset the lockouts globally, I have to define it again).
I hope I described it in clear way, feel free to ask. It kind of remins me the Uniden's "broadcast screen" function, with the exception, that with the SDR design these "avoid ranges" don't have to be scanned, but sipped.
Possible implementation: add a new button next to "Edit scan ranges" labeled "Edit avoid ranges". The scanner engine would work like now but respect the avoid ranges (not scanning these). The respective frequency bars in the "channel analyzer" could have a specific new colour for these "avoid ranges"
There is another suggestion with connection to this - is there a possibility do implement indivitual buttons (the icons with the closed and open lock) - one for "permanent lockout" (valid until reseted manually - it is how the current lockout works) and new "temporary lockout" (valid only in the current scan run, reseted automatically after scan stop - for avoiding only temporary interference).
Thank you for constatnt development of this plugin and I home my suggestion will help and can be implemented. Thi is my no.1 plugin!
I have one suggestion for improving the scanner plugin - to add "avoid ranges".
Explanation: when I define search ranges (from-to), the range is for example 440 - 470 MHz with 12.5kHz step. But there are two "gaps" which I would like to avoid - 457,40-458,50 and 467,40-468,55. Right now, that means that I have to define 3 ranges instead one (440,00-457,40, 458,50-467,40 and 468,55-470,00) which causes of course slower scan as the AirSpy has 8MHz range so it tunes the band in each defined range. OR I can define the range as 440-470 and manually click and lock out the desired frequencies one-by-one in the scanner interface on the bottom of the screen, but this is quite time consuming and when I reset the lockouts globally, I have to define it again).
I hope I described it in clear way, feel free to ask. It kind of remins me the Uniden's "broadcast screen" function, with the exception, that with the SDR design these "avoid ranges" don't have to be scanned, but sipped.
Possible implementation: add a new button next to "Edit scan ranges" labeled "Edit avoid ranges". The scanner engine would work like now but respect the avoid ranges (not scanning these). The respective frequency bars in the "channel analyzer" could have a specific new colour for these "avoid ranges"
There is another suggestion with connection to this - is there a possibility do implement indivitual buttons (the icons with the closed and open lock) - one for "permanent lockout" (valid until reseted manually - it is how the current lockout works) and new "temporary lockout" (valid only in the current scan run, reseted automatically after scan stop - for avoiding only temporary interference).
Thank you for constatnt development of this plugin and I home my suggestion will help and can be implemented. Thi is my no.1 plugin!
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
You can select a range of frequencies then lock them all out, but if you always clear them then this won't help.
Another approach (which the other version of the plug-in uses) is to store the lockouts used, in each defined range.
This way you could use multiple ranges with the same frequency range but have different lockouts set.
This will unfortunately break the save file (scanner_entryes.xml) compatibility.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
rumcajs_tr
Member
You are right,
this is what I do now - manually select range of frequencies (by dragging the mouse) and then scanning. However, the manipulation with this is quite complicated (have to zoom to individual "columns" to precisely see the exact start and finish) and with the fact that there is no "temporary" lockout and I have to reset all lockouts from time to time, this is a real pain to do. So now I stick with defining multiple search ranges (often in the same 8MHz segment) to solve this, but it significantly slows the scan.
This is why I suggested the new "avoid ranges" function. Do you think it is possible to implement?
this is what I do now - manually select range of frequencies (by dragging the mouse) and then scanning. However, the manipulation with this is quite complicated (have to zoom to individual "columns" to precisely see the exact start and finish) and with the fact that there is no "temporary" lockout and I have to reset all lockouts from time to time, this is a real pain to do. So now I stick with defining multiple search ranges (often in the same 8MHz segment) to solve this, but it significantly slows the scan.
This is why I suggested the new "avoid ranges" function. Do you think it is possible to implement?
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
If you define a range 440-470 and then just lockout the frequencies in the ranges of 457,40-458,50 and 467,40-468,55 (because you say don't need them), why clear the lockouts all the time, why not keep them in place?
I don't see a reason to add a "avoid ranges" function. You avoid them by not defining them.
The way the scanner allocates channels for scanning, it does not allow for avoiding parts of frequencies ranges.
It scans multiples of the visual bandwidth (2 MHz), the frequencies in that bandwidth are tested for a signal only if they are not locked out or if they exists in Freq DB (depends on scan mode).
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
I don't see a reason to add a "avoid ranges" function. You avoid them by not defining them.
The way the scanner allocates channels for scanning, it does not allow for avoiding parts of frequencies ranges.
It scans multiples of the visual bandwidth (2 MHz), the frequencies in that bandwidth are tested for a signal only if they are not locked out or if they exists in Freq DB (depends on scan mode).
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
rumcajs_tr
Member
OK, I admit it is more an issue with Airspy (8 MHz Bandwidth) than RTL-SDR (2MHz bandwidth).
I will try to explain why I clear all lockouts - this is because during longer perion of scanning, I normally get 20-40 individual lockouts - these are individual frequencies all across the range. So from time to time, I want to clear these avoids. I can either clear all by dragging the mouse from left to right (which is what I do) or I can manually pick segments of band to clear while not touching the other avoid segment which I want to keep. It may sound easy bud doing it several times per day and using the mouse and zoom, it is quite complicated.
It would be much easier, if the plugin would allow "permanent lockouts" and "temporaray lockouts" - same as Uniden scanners can. This could be also a solution without implementing the "avoid ranges" function and probably much easier to implemment.
I will try to explain why I clear all lockouts - this is because during longer perion of scanning, I normally get 20-40 individual lockouts - these are individual frequencies all across the range. So from time to time, I want to clear these avoids. I can either clear all by dragging the mouse from left to right (which is what I do) or I can manually pick segments of band to clear while not touching the other avoid segment which I want to keep. It may sound easy bud doing it several times per day and using the mouse and zoom, it is quite complicated.
It would be much easier, if the plugin would allow "permanent lockouts" and "temporaray lockouts" - same as Uniden scanners can. This could be also a solution without implementing the "avoid ranges" function and probably much easier to implemment.
Here I manually edit the scanner_entryes.xml file that is used with an R2.
First section of my lockouts is the birdies in numerical order and these are followed by (again in numerical order) a few local frequencies which I know will cause problems.
That part of the file remains quite static.
Anything after those is from daily use and can vary.
When I go to view the activity logs I take a moment to delete any entries that have been added to the list on the fly whislt searching. Save the file again and my 'default' problem frequencies are still locked out ready for next time. Only takes a moment.
First section of my lockouts is the birdies in numerical order and these are followed by (again in numerical order) a few local frequencies which I know will cause problems.
That part of the file remains quite static.
Anything after those is from daily use and can vary.
When I go to view the activity logs I take a moment to delete any entries that have been added to the list on the fly whislt searching. Save the file again and my 'default' problem frequencies are still locked out ready for next time. Only takes a moment.
rumcajs_tr
Member
Yes, for birdies you are rght - it can be done by editing the xml file. But if you want to lockout whole range, you would have to define all frequencies one by one within the range according to the step used.
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
I have added a "temporary lockout mode" for next release (among other things)
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
rumcajs_tr
Member
Excellent! Thank you. I will test it tonight and report.
EDIT: will test it as soon as it is released of course ...
EDIT: will test it as soon as it is released of course ...
hamradionl
Member
- Joined
- Mar 23, 2014
- Messages
- 730
Using AirspyR2
mountainrider
Member
Does it only work on VHF and UHF? I'm trying to scan the CB band but when I start the scan it goes to 245 kHz and stops.
SDR# v1.0.0.1750 firmware R3.0.6-CD. HF+ Discovery.
SDR# v1.0.0.1750 firmware R3.0.6-CD. HF+ Discovery.
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
Frequency Scanner will work anywhere the the dongle is capable of receiving.
Have you defined a range to scan? (e.g. 26.965-27.405 & 10KHz step size - AM)
What scan mode you using?
Some scan modes will not stop on anything if you don't have them saved in the Frequency Manager.
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
mountainrider
Member
I thought I had tried every permutation of frequency entry but I guess I hadn't. I defined the range as 26,960,000-27,405,000 and 10,000 step size and it seems to be working (local CBer's went silent, natch). Knowing the units of the inputs would help.
thewraith2008
Member
- Joined
- Nov 22, 2016
- Messages
- 1,867
Starting at 26.960 will not create the correct channels to scan.
26.960
26.970
26.980
26.990
27.000
...
when it should be
26.965
26.975
26.985
26.995
27.005
...
Latest version (v1.4.4.0) can be found here: MEGA - Download
Release post here
