Sdr free ip scanner

16channel = 1lowpass = 5000sampleRate = 22050server = localhostport = 8000password = hackmemountPoint = 12345678name = NameThen power cycle your pi to restart darkice.Now from a web browser on the same network as the pi browse to RadioReference.com - Scanner Frequencies and Radio Frequency Reference or if that doesn't work try Of course you need to use your pi's ip address. This will open up the icecast server web page on the pi. click the .m3u button to listen to the stream. #16 Now one more somewhat bizarre problem... I was able to do all that, and now I figured out how to address the pi using my iPhoneBut, it seems like the scanner audio is in verrrrrry slow motion. 1 second of audio seems to be almost a full ten seconds slowed down. Is there any way to fix this? #17 Now one more somewhat bizarre problem... I was able to do all that, and now I figured out how to address the pi using my iPhoneBut, it seems like the scanner audio is in verrrrrry slow motion. 1 second of audio seems to be almost a full ten seconds slowed down. Is there any way to fix this? In your darkice.cfg file try changing the samplerate to either 11025, or to 44100 #18 In your darkice.cfg file try changing the samplerate to either 11025, or to 44100 Perfect, I changed the samplerate to 44100 and it's working greatThanks for all your help! Maybe I'll make a new guide and send it over to the guys at the wiki #19 Hi, I too am trying to stream audio. I'm using a RPi3B with an RTL-SDR and OP25. I'm getting an error when I try to start Darkice. Code: DarkIce: DarkIce.cpp:1273: can't open connector [0] Any suggestions would be helpful. I am only trying to stream locally for now but if all goes well, I intend to set up a Broadcastify feed.Thanks in advance. #20 Hi, I too am trying to stream audio. I'm using a RPi3B with an RTL-SDR and OP25. I'm getting an error when I try to start Darkice. Code: DarkIce: DarkIce.cpp:1273: can't open connector [0] Any suggestions would be helpful. I am only trying to stream locally for now but if all goes well, I intend to set up a Broadcastify feed.Thanks in advance. Streaming from RTL-SDR is an entirely different animal. Darkice is looking for input from a sound card. The output from RTL-SDR is stdin/stdout. You would somehow need to route that through an audio program. I believe that it can be done be may not be as easy as one might hope. I have never been successful. Check out this thread for example:

Compressed file and dragged it to the 'plugin' folder, as usual). Attached is the error message I get.Note that the same issue occurs if running Frequency Scanner 2.2.10.0.I will run some old SDR# versions for the time being, 1716 and 1732. Difficult to keep up with Prog's releases as sometimes there are multiple releases of a 'number' never mind new numbers. .1844 and .1845 lasted seconds and as I type we are on the fourth number today... .1846Scanner plugin works fine with .1843, I missed .1844 but plugin fails to run with .1845 and .1846One can only guess that Prog breaks things regularly...but of course it is his sofware users and plugin authors who he treats like idiots.It really is easier to keep a working directory of one of the older sdrsharp variants (as per the documentation thewraith2008 helpfully provides) for use with the scanner plugin - it works fine and saves the hairpulling when you think you might have done something wrong Last edited: Jan 18, 2022 #535 Looks like all these SDR# changes have busted the scanner plug-in for good. (and maybe other plug-ins)Bad luck for the new SDR#. Long live legacy SDR# (v1716).Latest version (v2.2.13.0) can be found here: MEGA - Download Release post here #536 And long live SDR# v1732. I am using Frequency Manager v1.1.7.1 and Frequency Scanner v2.2.13.0 with zero issues. These plug-ins are my go-to-tools for managing and scanning large chunks of spectrum. My latest hunt [again] is sweeping across the air-band looking for new offerings. It never ends. Thank you @thewraith2008! #537 stopt upgrade SDR# after 1700 And switch to SDR++ just suggestion for those give it a try make some plugin #538 Running SDR# 1716 and 1732, I notice something wrong with "Show 8.33 KHz channel name (in main spectrum)" feature.It's of course enabled, SDR# step is set to 8.33. as usual. Before scanning, the "channel name" is displayed as expected, but as soon as I run the scan, it disappears. I don't have the '8.33 channel selector' plug-in installed.Anyone ?Is there something I'm doing wrong ? (was perfectly working with

Not complete and may contain errors and is not laid out as good as it could be.No real testing has been done with the newer SDR# from v1717 and above.Main testing has been done with SDR# 1700.NOTE: SDR# has been going through some changes (1732+) and it's new features may see this plug-in play up.NOTE: To use the CTCSS/DCS feature (added in v2.2.12.0), you are required to update the CTCSS and DCS plug-ins to v1.3.2.0+. (use same link below)DownloadNOTE: Use 7zip or WinRAR to extract files from the .7z file and read the .PDF file for installation and usage of files with SDR#.NOTE: Don't select the Download as ZIP option in MEGA, just select standard download.HASH: 75e3716ef4d9aa8f0ddfd6e68e8791b0 #531 @thewraith2008 It works as it should right now. I will test it in the following days, but I think the scanner is much better as it is not stopping on fake signals that often. I've narrowed the channel bandwidth for signal detection and resetting noise floor every 2 minutes. One more question - reset timer on 'over' has no meaning when you have Wait time set to 0, correct? #532 One more question - reset timer on 'over' has no meaning when you have Wait time set to 0, correct? Probably not, it will just reset when scanner resumes as a 'over' will leave a pause(wait) greater than 0.Latest version (v2.2.13.0) can be found here: MEGA - Download Release post here #533 Hi there !I just downloaded CTCSS 1.3.2 and Frequency Manager 2.2.13 and SDR# latest rev, #1845.Frequency Scanner simply won't start.I suppose I did the install properly (unzipped the compressed file and dragged it to the 'plugin' folder, as usual). Attached is the error message I get. Note that the same issue occurs if running Frequency Scanner 2.2.10.0.I will run some old SDR# versions for the time being, 1716 and 1732.Many thanks for your great work. scan.JPG 83.5 KB · Views: 13 #534 Hi there !I just downloaded CTCSS 1.3.2 and Frequency Manager 2.2.13 and SDR# latest rev, #1845.Frequency Scanner simply won't start.I suppose I did the install properly (unzipped the

But the scanner plugin does not show up in the plugins to the left of SDR#. Copied the old dll back in, with no other changes, and V1700 starts ok and the scanner plugin returns and runs correctly. Did a clean install of V1700 and the same thing happened, new dll doesn't run but the old dll works fine. OS is Win 7 64 bit. Any ideas? #4 I'm not sure why you don't see it.I just tested with a fresh SDR# 1700 in both Windows 7 32 bit and Windows 10 64 bit and both showed up.I don't have a Windows 7 64 bit to test with, but I sure that alone wouldn't stop it to show in SDR#.I tested the DLL in zip and it's same as one I'm testing with.Check that when you extracted the DLL, it actually extracted correctly.Check file size and MD5 hash (with HashMyFiles).Something (like AV) may have blocked it from extracting correctly.The extraction program you used maybe not working right with the 7z file. I use 7zip. WinRAR may cause problems, not sure. #5 New DLL working fine for me Latest Win10 update and Latest SDR# Thank you thewraith2008Love the new easy lock/unlock feature #6 I only use wrinrar and haven't had any problems with extracting the files.Plugin working fine with sdrsharp 1700 on windows 10 64bit and windows 7 64bitNot tried it with 1732 as that was consigned to the bin #7 I only use wrinrar and haven't had any problems with extracting the files.Plugin working fine with sdrsharp 1700 on windows 10 64bit and windows 7 64bitNot tried it with 1732 as that was consigned to the bin Thanks for the info, good to know WinRAR is OK with 7zip and that the plug-in works OK in Windows 7 64 bit (using SDR# 1700) #8 This is an update to the great Frequency Scanner plug-in for SDR#. This is great news. Thank you! #9 Copied the new dll into my V1700 to replace the prior version dll which worked correctly , no other changes were made. V1700 starts ok but the scanner plugin does not show up in the plugins to the left of SDR#. Copied the old dll back in, with no other changes, and V1700 starts ok and the scanner plugin returns and runs correctly. Did a clean install of V1700 and the same thing happened, new dll doesn't

HereDownloadNOTE: 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: 3347af87e5fc8ffbdd76f850543d7eef #17 Can someone explain the expected values for Detect? PDF mentions to increase by +20 but what is the optimum/default - 100? Detect (Slow down scan speed to allow for better detection of active signal)The value acts as a delay to allow the 'receiver' to stabilize so the plug-in does not miss active signals. For the audio mute I've always wondered what this does. Is there a difference between having it disabled v having a value of 0? 'Use audio mute' and 'Noise protection delay'The audio mute is independent of the SDR# squelch but in the end does the same thing (maybe better).You may get better results using this with scanner plug-in than using the SDR# squelch with scanner plug-in.'Noise protection delay' This helps eliminate the crash at end of transmission.Don't use it if also decoding digital signals as well. Is there any way this could be made to work with 8.33 spacing for airband? Have you tried? What are you seeing that it should not be doing.The bandwidth and step size is available when you define scan ranges.The scanner plug-in channelizes the defined range based on these values. #19 Detect (Slow down scan speed to allow for better detection of active signal)The value acts as a delay to allow the 'receiver' to stabilize so the plug-in does not miss active signals.'Use audio mute' and 'Noise protection delay'The audio mute is independent of the SDR# squelch but in the end does the same thing (maybe better).You may get better results using this with scanner plug-in than using the SDR# squelch with scanner plug-in.'Noise protection delay' This helps eliminate the crash at end of transmission.Don't use it if also decoding digital signals as well.Have you tried? What are you seeing that it should not be doing.The bandwidth and step size is available when you define scan ranges.The scanner plug-in channelizes the defined range based on these values. Thanks for quick fix - this is working perfectly now.Re. questions above...8.33 spacing - I use frequency manager and so for a local frequency of 122.125 with 8.33khz steps, my vfo will actually land on something like 122.124.680. When I look at the recordings I get 'unknown groups' because the frequency manager frequency and the slightly offset vfo