Sdr Older Versions
Blanche Bunnell
A few days ago SDRSharp version 1920 was released. SDRSharp (SDR#) is a popular Windows program that is affiliated with Airspy SDR dongles, but is compatible with RTL-SDR and various other SDRs as well. The latest version gets rid of the relatively resource heavy Telerik UI library and replaces it with a much lighter weight library.
The author of SDR#, @lambdaprog, notes that v.1920 reduces memory usage by 85% and CPU utilization by 50%. The new version also improves scalability for high sample rates and number of spectrum slices and improves plugin compatibility. Several AOR brand SDRs are also now supported in v.1920.
On the note regarding improved plugin compatibility, we've noticed that in the v.1920 update the IF Average plugin has begun working again. The IF Average plugin is used for Hydrogen line radio astronomy experiments. In the past we had to use older versions of SDR# to make it work. We have updated our Hydrogen line tutorial to reflect this.
Been using SDR# for many years and am very satisfied with it along with the AirSpy HF Plus Discovery. Works great for ham, shortwave, CB and HF utility monitoring. Very thankful to those who were responsible for developing the software and hardware.
Why would he be a nutcase? His software is pretty good and is the industry standard more or less. The Airspy products are proper SDR recievers and not just another repurposed TV tuner that has an exploited I/Q sample mode like the SDRPlay and RTL-SDR products. Not to mention the paywall behind the SDRPlay software.
I will have to tr (narrow band of qualityy it as well as read more about it. I may have a friend install it in a spare old machine I have. That has a version of SDR# 14.3 something I think. I have tried some other software and had problems with the display showing a narrrow image of the magnitude of the signals).
Hi all,
thanks for this big project!
I came across OpenWrt as I like to take old electronic bricks and put them into new life.
With a old Pirelli modem, I was able to install the adviced version of the OpenWrt.
The purpose of this device it will be solely to make a RTL_TCP server in a remote location that has internet available. Installation has been succesful through the serial port and all seem ok.
The only problem is that in the available packages, I can't see and I can't get any rtl-sdr stuff.
Any suggestion will be very welcome.
Cheers!
Ignazio
Package table Package categories Clicking on a package category filters the Table of Packages below accordingly, but you can of course filter it manually by yourself. Filter by category Table of packages The table below shows 50 packages per...
It doesn't work.
I've tried many times, no success.
I've also tried via command line at SSH prompt, no success.
In the update packages list, rtl-sdr is not there, hence no install doable...
Thanks!
Anyway, sorted.
I'm a absolute noob on OpenWrt, the version loaded at first attempt was a old 10.xx
I have now a 21.02 and Rtl package was there and installed.
Noneless, I have some strange glitches that I still have to figure out.
Occasionally the router kill the service or it goes into strange behaviour.
Perhaps limited performance of my Pirelli hardware?
Techdata: Pirelli AliceGate AGPF This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram. DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version (18.06 or later)...
Thanks mates,
I had same thoughts and applied practically with good resoults. Reduced sampling to 1.024Mb and is decently usable. I also turned off a few services to reduce cpu load.
I have to mention that to make it work properly I had to downgrade gradually to version 19.04
This version hold variations once rebooted and is capable of accepting boot start of the RTL_TCP stack.
Quite happy of the results, after all is just a piece of electronic junk.
My neighbours were quite happy to get rid of.
One more candidate has arrived today, Huawei HG553, looks promising and better performances of Pirelli AGPF. Will try
that just means that it's available in a specific OpenWrt release, to see if it was available for older versions, click on the "Source" link to go on github and then click on the button with "openwrt-21.02" on the top left to open the menu of all OpenWrt versions (which are handled as branches on git).
I found this article showing that at least older versions of Backup Exec system recovery disk uses NTLM v2 but in my expereince testing SDR in Backup Exec 2012 I could only get the SDR session to log in if I reset my domain controller to use NTLM v1 authentication. Is there something that I haven't configured correctly or is this just the way it is? The security requirements of my system require me to use NTLM v2 only.
SDR-Bridge v1.5 contains new spport for either a single or for multiple FlexControls. This support is enabled and controlled from the Knobs tab. Knob support is independent of Skimmer and WriteLog integration. No Skimmers are needed to use the knobs.
The first three checkboxes on the Knobs tab control enabling and the overall behavior of the knobs. The first checkbox must be checked to enable knob support. In addition at least one of the next two checkboxes must be checked. If you have a single knob, check the second checkbox. This will cause your knob to track the active slice. If you have multiple knobs, check the third checkbox. This will assign up to four knobs, one to each IQ slot. The knob will control the slice selected in the Slice column of the IQ slot. After configuring these first two checkboxes, restarting SDR-Bridge is not required.
All knobs work the same. AUX1 controls RIT and AUX3 controls XIT. Click either button to enable. Long press or double click either button to clear the offset. AUX2 controls either AGC-T or AF volume for the slice. Long press or double click AUX2 to toggle between the two. Click the main knob to enable tuning.
SDR-Bridge v1.5 is a full release, not a beta. This means that the code will not expire. It is based on the latest version of the FlexAPI. New versions will become available with new features, bug fixes, and to cooridnate with changes in SmartSDR and the FlexAPI.
The new 1.0 beta version of SDR-Bridge launches Skimmer when you check the appropriate box on the Bridge tab. If you uncheck the box, it minimizes Skimmer. And if you have the box checked when you exit, SDR-Bridge will start Skimmer on that IQ the next time it is run.
The first time you launch a Skimmer from the Bridge panel, it will start with a preconfigured INI file. SDR-Bridge checks the audio configuration of your computer so it should be ready to go. If you make any changes in Skimmer Settings, when you exit Skimmer the changes will be recorded in the INI file.
On the Bridge tab, in the Sync panel, checking a Skim box will open a Skimmer for that IQ channel. The screenshot shows all four IQ channels active. Each is assigned a slice. The A slice is red because it is the TX slice. Active slices show yellow, to match the SmartSDR display.
If Stream is showing a single number, it is the panadapter center frequency. Once Skimmer is connected, it reports the actual frequency band it is skimming. Note that the panadapters are adjusted so that Skimmer is looking a bit below the band edge. That is because the IQ stream is actually about 80% of the selected bandwidth, so signals are not skimmed in the bottom and top few khz of the stream.
On Bridge View, you can bring the DAX panel up by clicking its button. If SkimSrv is installed in its default location the Skimmer Server button will start the app. Due to the way Windows initializes items in the system tray, both the DAX panel and the SkimSrv panel need to be opened for the first time from the tray. After that the Bridge buttons should work correctly.
The MuteAllButActive option is checked by default. It mutes all slices but the active one, as the name implies. This is true whether or not the slice is assigned to a DAX channel. That is why it is on the Radio tab. It is a radio global feature.
In the future there will be a pan assignment for slices that will allow more complex positioning of slices in the auditory field and more information about radio status. Also more control features will appear on this tab.
On the Logger tab, as of now there is only one logger, WriteLog. If you have WriteLog (even older versions should work fine), just start the program. After a few seconds, synchronization starts automatically. No port assignments are necessary because SDR-Bridge is CAT-free.
The first prototype of SDR-Bridge required a dozen manual steps to get everything going. Much effort has been put into simplifying the operation and improving the user experience. Let us know of further suggestions for features or improvements. And enjoy the show!
Kevin was using an older version of Raspberry Pi OS and also discovered that the installation script had been written blind (untested) and had a couple of issues, he referred to cloning direct from GitHub which is common practice, but that command was simply missing. No matter, I managed to change the commands script as below and started to compile it myself discovering that the Volk software v1.0 was no longer available. A helpful bash message informed me that v2 was available and I changed the script for that. I also had to include sudo and a mkdir for the CMake folder and set those permissions for it to work. After a very long wait and a few edits as I am running the current version of Raspberry PI OS 32 bit Buster. I compiled it for an RTL-SDR, but you can change one command and compiling for other versions should be really straightforward.
If you want to compile for other radios either edit or add extra lines like this one "cmake .. -DOPT_BUILD_RTL_SDR_SOURCE=ON", for more information about this go to the Module List, and look for the Sources list on the github page
If I am not mistaken, older versions of NetBackup use tar as their backup file format. That means you can potentially try using all-in-one archival solutions that support various flavors of tar to access your data inside backup files. However, the best course of action would be to install the appropriate version of NetBackup, which still supports your existing backup chain. You can find the binaries here _US/downloads/detail.REL247502#item2.
c80f0f1006