Website Complaints!
Simon Brown • January 11, 2020
Font Size and Colour
So, the new website was launched two days ago and some viewers with ageing eyes complained about the text font - just not enough contrast. I find that I use the Chrome and Edge browsers with a default 125% zoom as I'm no spring chicken!
Also, I'm just a simple programmer with absolutely no graphic design skills at all but I do know how to use Google and found ux movement's website
which has a very interesting article "Why You Should Never Use Pure Black for Text or Backgrounds". This article covers:
- Pure Black Text & Backgrounds
- High Contrast for Accessibility
- Balanced Contrast for Readability
It's well worth reading.
As a result the default font is now bigger and the colour darker.
Version 1.6.1 This release fixes two fatal bugs in the new DX Spot feature. When the graphics engine is restarted, resources are correctly released. Fixed a resource leak when processing the MoseMove logic. Downloads are on the World Map page . Version 1.6 This release adds the display of DX Spots. Display spots are submitted to PSK Reporter which in turn are relayed by a MQTT Broker running on a high performance Akamia node. Spot Format Each spot consists of these fields: Sequence Frequency Band Mode Signal level Time stamp Sending station call, square, country Receiving station call, square, country Note: The country is the ADIF country. Spots are displayed as they arrive, currently no on-demand database. Bandwidth To reduce bandwidth from the broker, filtering is required for 80m up to and including 15m. Filtering requires at least one field below to be set in a definition: Receiver callsign, square or country. Sender callsign, square or country. Without filtering the bandwith from the broker could be excessive. For LF and VHF+ no filtering is required due to the lower number of spots sent on these bands. In a later version the bandwidth restriction may be reduced.
Version 1.6 This release adds the display of DX Spots. Display spots are submitted to PSK Reporter which in turn are relayed by a MQTT Broker running on a high performance Akamia node. Spot Format Each spot consists of these fields: Sequence Frequency Band Mode Signal level Time stamp Sending station call, square, country Receiving station call, square, country Note: The country is the ADIF country. Spots are displayed as they arrive, currently no on-demand database. Bandwidth To reduce bandwidth from the broker, filtering is required for 80m up to and including 15m. Filtering requires at least one field below to be set in a definition: Receiver callsign, square or country. Sender callsign, square or country. Without filtering the bandwith from the broker could be excessive. For LF and VHF+ no filtering is required due to the lower number of spots sent on these bands. In a later version the bandwidth restriction may be reduced.
SDR Television v1.1 May 18th, 2026: This is the official v1.1 release , code exactly the same as 1.0.16 which has survived testing for a few weeks. Lots of improvements since the last official kit. As with any software project, there's always room for improvements and new features, but for now here's a stable solution which works well with the QO-100 satellite. Many thanks to Sigi and the DATV test team. Downloads are at the bottom of this page.
SDR Television v1.0.14 April 12th, 2026: A new kit, lots of improvements since the last official kit. As with any software project, there's always room for improvements and new features, but for now here's a stable solution which works well with the QO-100 satellite. Many thanks to Sigi and the DATV test team. Downloads are at the bottom of this page.
SDR Television v1.0.9 March 13th, 2026: A new kit, lots of receive improvements since the last official kit. As with any software project, there's always room for improvements and new features, but for now here's a stable solution which works well with the QO-100 satellite. Many thanks to the DATV test team. Downloads are at the bottom of this page.
First Impressions
SDR Television v1.0.6 February 13th, 2026: A new kit, lots of receive improvements since the last official kit. As with any software project, there's always room for improvements and new features, but for now here's a stable solution which works well with the QO-100 satellite. Downloads are at the bottom of this page.
February 10th, 2026 Pluto Correct the FIR filter definitions, this has improved reception.
Follow These Steps If you're unsure how you add a radio definition to SDR Console, here are the steps you must follow. Start SDR Console (quite obvious really). From the Home tab on the ribbon bar, in the Radio panel click Select Radio , the Select Radio window is displayed. At the bottom right of the Select Radio window, click Definitions... , the Radio Definitions window is displayed. At the top left of the Radio Definitions window click Search , a list of all supported radios is displayed. Select the radio you want to add, for example Airspy, SDRplay. In this example the RX-888 will be added. When you select an option from the list in step 4, either a radio is found or not. If the radio is found, a window is displayed with the option of adding the new definition. If the radio is not found, an error window is displayed. If this is a radio connected by USB, make sure the USB port can supply enough power. After adding the definition, click Save in the Radio Definitions window. You can now select your radio in the Select Radio window. That's all folks! SDRplay If you are using a SDRplay you select SDRplay > V3 in step 5 above. Make sure you have also installed either SDRconnect , SDRuno or the latest API (currently 3.15 at the time of writing).
