Blog

 

 

 


 

 



 

SDR-Radio.com

rss

Assorted ramblings from the developer


Release: 3.0.4

Download here [Link].

What's new / changed in 3.0.4:

SDRs

  • ADALM-PLUTO transmit and receive support added.

  • Airspy HF+ support library upgraded to latest release, CPU usage now much lower.

  • Airspy HF+ supports pre-production units properly, also units with old / original firmware.

  • ANAN code given a lot of attention, working much better.

  • bladeRF2 now checks that the frequency is within the supported range.

  • Lime transmit support added.

General

New

  • Added Pseudo Stereo (ribbon bar, Receive, Mode..., Pseudo Stereo).

  • Downconverter supports frequencies up to 999.9 GHz.

  • Frequency database supports a Custom CSV layout.

  • Frequency display supports frequencies up to 999.9 GHz.

  • If there are no receivers a warning is displayed.

  • Signal History - added Slower and Very slow.

Fixes

  • Audio buffering logic updated (the way I maintain the buffer between demodulation and the playback / VAC device). This is simpler, cleaner and gives me a good base for the future. See the Playback Buffering page for options.

  • Audio recording – a check is made that the folder exists before the recording is started.

  • Fixed spectrum display in Auto mode when input signal is very low / zero.

  • Fixed crash adjusting the Span (bottom of display).

  • Fixed crash caused by a change in output device options such as enabling spatial sound.

  • Fixed obscure bug in the Select Radio user interface.

  • Fixed SAM demodulation, PLL was not working fast enough.

  • More visibility/sanity checks when restoring a window position (example: Select Radio).

  • Obscure fatal bug saving/recalling complex Favourite definitions fixed.

  • Product name and date now always shown at the top of the main display with all display styles (long-standing MFC bug fixed).

  • More logic in coding where the program priority is raised when the system starts.

  • If the signal is muted due to input overload a warning icon is now shown in the status bar, previously just the Auto Mute text was shown. (This caught me out a couple of times).

Recording Scheduler

  • Interface redesigned, simplified with no loss of functionality.

Satellite

Display

  • Now displays correct TX mode in the main window's ribbon bar tooltips.

  • Now uses fixed point fonts for name and times.

  • Fixed fatal error selecting a world map which cannot be opened.

  • External Radio now supports both Rig 1 and Rig 2.

  • TLE data now has better sanity checking.

Server

  • Reduced dangling connections on the server.




Comments are closed.



Recent Posts

  • Google Turbo Posted 2 days ago
    Turbo, An Improved Rainbow Colormap for Visualization  https://ai.googleblog.com/2019/08/turbo-improved-rainbow-colormap-for.html On Tuesday, August 20, 2019 Google posted an interesting colour scheme which they named 'Turbo'. Read more about this in the blog entry (link is above). Below is the colour map in action on the 25m shortwave broadcast band. As of 3.0.13 this is a standard colourmap[ in SDR Console. Also of interest is the use of a SNR (Signam to Noise) S Meter option.
  • S-Meters Posted 2 days ago
    After much pestering by users, I finally added an Analog S-meter to SDR Console. These will be available in 3.0.13, coming to a desktop near you soon. Background A few weeks previously a reasonable logic was implemented for measuring the noise floor. Purists will not be happy, but they rarely are, but it works for me. Take the output from the SDR radio, ignore 15% of the bandwidth at the high and low end of the output to avoid the ant-alias filtering, and we're left with a healthy 70% of the signal. Now sort the FFT bins by value, take the mean of the lowest 10% and that's the noise floor. Digital Starting with the standard digital metere: Analog Here are a few screenshots of the Analog S Meter. First a tradition meter in S units. Red = peak signal Yellow = current signal Grey = noise floor   Here's a dBm meter, same colours as above.   And here.s a Signal to Noise (SNR) meter.
  • Pluto on Es'Hail 2 Posted 2 weeks ago
    Here's a screenshot of my Pluto SDR on Es'Hail 2, this screenshot shows the suggested settings for pluto(bottom left-hand side). Note the RX Gain is set to Slow Attack (Manual value is ignored) and the Visual is set to -40dB.
  • Windows Upgrade Posted 2 weeks ago
    Yesterday I powered on a small ATOM 330 server which was last started five years ago. Well, up came Windows 7 Professional and of course the normal zillions of updates appeared. Anyway, I wondered whether the now officially expired free update from Windows 7 to Windows 10 was still available. Google brought me to this link on www.zdnet.com . In https://www.zdnet.com/article/heres-how-you-can-still-get-a-free-windows-10-upgrade/ the suggestion is to  go to the Download Windows 10 webpage whioch I did. then I clicked the Download too now button. Thereafter I just followed my nose and two hours later my little server was proudly running a licemced version of Windows 10. So the free upgrade from Windows 7 to Windows 10 is till available! Toodles
  • Release: 3.0.12 Posted 3 weeks ago
    Download here [Link]. What's new / changed in 3.0.12: General CW Skimmer bugs resolved, confirmed as working by Kurt, DF4XX. Data recorder supports Range values of 48kHz and 96kHz. Frequency display overflow error fixed. Memory definitions > 2 GHz could crash the console – fixed. Radio Calibration window changed to avoid confusion, now shows 0 PPM instead of None when no calibration is in effect. Rare hang situation during program start found and fixed. DX Cluster See https://www.sdr-radio.com/Console/DXCluster. Ribbon Bar, View, Spectrum, DX Cluster.  Markers must be enabled: Ribbon Bar, View, Spectrum, Markers. Comes with a list of suggested nodes. Autostart option. Can be docked anywhere. Runs even when window is closed. Cluster implements a timeout / reconnect logic: If no messages are received for 60 seconds an ‘echo # keepalive’ command is sent, this will reset the reconnect timer if the cluster node is running. If no messages are received for a further 30 seconds: The connection is closed, The connection is restarted.
Read More »