Category Archives: SDR

Ahoy! Decoding eight GMDSS Channels in a Convoy

Decoding all GMDSS channels at once: Black Cat System’s groundbreaking GMDSS Decoder.

Chris Smolinski, W3HFU, did it again: after his multi-channel attack to ALE, he now offers this highly innovative concept also for GMDSS – Black Cat GMDSS. In addition to an extraordinary sensitive decoder, it also includes smart processing of the data – from looking up vessel’s complete data from ITU’s Ship Station List (internet connection needed) to saving all data to a fully-fledged database. Welcome aboard! Now let’s set sail!

3000+ Messages a Day – received on HF

The Global Maritime Distress and Safety System is a system of different maritime communications tools on frequencies ranging from as low as 424kHz [NAVTEX] over HF and VHF up to satellite channels in the GHz region. This blog entry focus on Black Cat GMDSS decoder, hence on HF. There, the six main channels range from 2MHz to 16MHz. Reception of both, Coastal Stations and vessels, is from around the world. In this case from Vestmannaeyjar Radio in Iceland to Cape Town Radio in South Africa, and from Valparaiso Playo Ancha Radio in Chile to Taupo Maritime Radio in New Zealand. You may hear vessels of each and every kind, from small ones for pleasure to the biggest oil tankers, and all over the world. Monitoring on all six main channels in parallel, often raises 3000+ messages a day!

Robust FSK mode

Transmission is done in 2-FSK with 170Hz shift and at speed of 100Bd. Waveform is ‘kind of SITOR-B, repeating each character twice with a 400ms spread to enhance proper decoding under adverse propagation (Rec. ITU-R M.493-11). To establish a call, each station has been assigned to an unique MMSI, or Maritime Mobile Security Identity number consisting of now nine digits, in future 10 digits. MMSIs starting with 00 denote a Coastal Station, e.g., 004123100 for Guangzhou Radio/China. There is a set of 127 symbols, with the first numbers 00 to 99 representing numbers, and each of the remaining number specific situations like “110” denoting “Man over board”. The software has to look up those source-coded messages in a codebook to print a readable message, giving some sense.

Smart coding

One message is about 6.4 seconds long. it starts with a short dot-pattern/phasing sequence for automatic tuning, followed by the content. In this live example, JRCC Australia (MMSI 003669991) is calling Merchant Oil tanker Signal Maya (MMSI 248410000) on 12577kHz at 15:59:43 UTC on November 21, 2021.
There are transmitted 23 groups (“Symbols”) in GMDSS :

  • 120 120 021 007 061 000 000 108 000 050 030 000 010 118 126 126 126 126 126 126 126 122 111

and decoded as follows:

  • 120 120 -> Format
  • 021 007 061 000 000 -> Address – MMSI of called station
  • 108 -> Category
  • 000 050 030 000 010 -> Self MMSI – MMSI of calling station
  • 118 126 -> first and second [none in this case, “idling”] telecommand message
  • 126 126 126 -> frequency message [none in this case, “idling”]
  • 126 126 122 -> end of message
  • 111 -> error-check character [ECC]
  • After a look-up in the codebook this turns into:
  • Format: Individual call
  • Address [to]: 210761000
  • Category: Safety
  • Self MMSI [from]: 005030001
  • First telecommand: Test

… even smarter decoding!

Still not much enlightment. But BCS-GMDSS is at your service. It looks up all the cryptic numbers at different sources, even tapping official ITU webpage to enrich the vessel’s MMSI with its stunning mutltitude of information. Wrapping it up, decoding and looking-up in an internal codebook (Coastal Station) as well as in ITU sources (vessels), the above mentioned 23 symbols come out in full glory reading:

[2021-11-21 14:59:43] 12577
Symbols: 120 120 021 007 061 000 000 108 000 050 030 000 010 118 126 126 126 126 126 126 126 122 111
Self MMSI: 005030001 – Australia – JRCC AUSTRALIA 26 20′ 48″ S 120 33′ 52″ E 13669 km, 92 deg
Address: 210761000 – Cyprus
Ship: SALT LAKE CITY | Callsign: C4DS2 | MMSI: 210761000 | Cyprus (Republic of) (CYP) | Vessel ID: 9314129 | EPIRB: BE1 | 06/12/2017
Class: Merchant | Bulk carrier | | 89076 tons | 26 persons | INMARSAT C MINI M INMARSAT M VHF DSC | 24 hr service
Owner: NOBEL NAVIGATION CO LTD POB 50132 LIMASSOL CYPRUS
Misc: Former Name: THALASSINI NIKI | | EPIRB ID: 210761000 | | Telephone Bands: STUV | AAIC: GR14 | | CO | |
Format: Individual call Category: Safety First telecommand: Test

As you have seen, I already mixed some theory with some practice – as you know me.

Now for some features of the software, plus some hints to make the most out of it.

Some basics, you must be tuned to

BCS-GMDSS offers up to 8 channels in parallel which by default are set to the main six GMDSS channels plus two with only rarely traffic observed, also on 2MHz. Those channels are fed by a SDR, ideally covering the whole range from 2MHz to 17MHz, alias-free. In this range you have to place the up to eight channels, RX1 … RX8, and have their output set to VAC1 … VAC8. The inputs of the decoder have to match those VAC numbers – see screenshot.

Here, six GMDSS channels have been set with SDRC software, controlling a Winradio Sigma SDR at 20MHz bandwidth.

Take some care to think about mode, tuned frequency and audio frequencies, and bandwidth. Mode can be USB, CW-U or FSK, whatever your SDR’s software offers. It is, however, mandatory that the center frequency of the audio output must match the centre frequency of the input of the decoder! Otherwise there will be no decoding.

I am using free SDRC software by Simon Brown, G4ELI, easily providing all eight channels via VAC software. I am using CW-U and a bandwidth of 400Hz, giving some room for stations which might deviate by some 10Hz from the assigned channel – the decoder automatically compensates for this. With this setup (see screenshots below), the frequency readout shows the assigned channels, plus centre frequencies of decoder and receiver are matching (here 1700Hz, as ITU recommends). The bandwidth offers a good balance of SNR and tolerance for stations with a slight offset. Your mileage may vary in some aspects, e.g., you may prefer SSB-USB mode, or your software has a BFO if you use CW …
You may also use the wrong sideband (LSB instead of USB) with your receiver – but than you just have to tick “Invert” in the decoder’s Setting menu as it then changes Mark and Space frequencies.

Center frequency set to 1700Hz, low to 1500Hz, High to 1900Hz – resulting in a bandwidth of 400Hz. The signal of Finisterre Radio on 8414,5kHz matches these values.
With center frequency of the audio output (1700Hz) and center frequency of the decoder (1700Hz) matching, a signal falls into both passbands – that of the receiver on the right side with spectrum and spectrogram, and that of the decocoder on the left with spectrum, amplitude and also the Setup menu.

Order! How to cruise through this Ocean of Messages

BCS-GMDSS cleverly combines a most powerful decoder with some extras to calm the rogue waves of decoded information. First, you may reduce (or extend) the degree of information you fetch form the ITU page: Edit -> Settings -> MMSI Lookup. It is very interesting to see the maximum of data (“Most Details”), but with everyday’s monitoring just “Basic” or “Detailed” may run the show. This creenshot is showing the differences:

Five different depth of data output: from “Details: None” to “Details: Most Details” – with all the same audio being decoded.

The second step is to distinguish the vessels from the coastal stations by color. I set the latter ones to show up in blue:

Here, messages from Coastal Stations are printed in blue (Edit -> Highlight Coastal Stations, set color).

Next, BCS-GMDSS offers a Coastal Station’s database. It is a real database which, e.g., each column can be sorted. In the screenshot below, I had sorted them according to their total messages received. Then “Yusa Radio” has been double-clicked to inspect the timestamps of reception:

Coastal Station do have an extra porthole offering some interesting statistics. Each column can be sorted, and a double-click reveals timestamps of one station.

The “Loggings Database Search” is like a supertanker, containing all your logs which can be sorted by a double-click, plus being queried for each column, also combining different criteria. This is the most powerful database any GMDSS decoder has on board. See screenshot below for just one example:

The whole log of 12’590 entries had been queried for messages from Coastal Stations on 2187.5kHz on November 21, 2021 for 24 hours. This answer is of course just a small part of the whole reply from the database.

Addendum: Where are they cruising?

The location of most Coastal stations is openly available, and their geographical coordinates are internally looked up by the software – even calculation of the distances to your location (Edit -> Settings -> Latitude:/Longitude:) is done automatically.
But where are the vessels cruising? They only rarely transmit their location in GMDSS on HF. But if they have an AIS, or Automatic Identification System, you have a fair chance to get the actual location. This system comes in two tastes: AIS and LRTI, or Long Range Identification and Tracking. AIS is using VHF. Propagation restricts the range to some ten kilometers. LRTI is using satellite (INMARSAT). There are some webpages where you get at least AIS for free – just to mention VesselFinder, VesselTracker and MarineTraffic. Their business model is to offer subscriptions for one year at a price of about 1’200 US-$ for LRTI (satellite) data, aimed mainly to the professionals. But most of those companies offer (limited) access to their AIS data for free. The two screenshots below show the difference.

Scattered with vessels: VesselFinder’s professional version listen to all seven oceans via satellite, but offers …
… free acces to AIS data (VHF) which is due to propagation and volunteers feeding this net to those coastal regions.

The example above, bulk carrier Salt Lake City, is only availabe on LRIT. So free data are about one week old. Nevertheless, you get at least a clue where the ship had been. And if time plays no role, just look it up exactly this week later …

For free, we get only a weeks’s old satellite information. At least we can can see the bulk carrier had started from Manila on November 14, heading to Abbot Point in Australia where it is expected on November 29. A rough estimate is that she may have been cruising through the Banda Sea at the time of being called by JRCC Australia.

If you have received the following message, you are lucky:

[2021-11-22 17:02:38] 2187.5
Self MMSI: 229375000 – Malta
Ship: CMA CGM FORT DESAIX | 9HA5478 | 229375000 | MLT | MLT | 9400174 | 229375000 | 04/08/2021
Address: 002275300 – France – MRCC CORSEN 48 40′ 60″ N 2 19′ 0″ W 947 km, 252 deg
Format: Individual call Category: Safety First telecommand: Test

This vessel is covered by AIS (VHF) with its up-to-date data available for free at VesselFinder.

Multi-channel ALE Decoder: Listing and Logging

As if by magic, a file [invoked, marked yellow] completes the decoded messages to a complete and easily readable log. ALE callsign “111111” had no entry in the file, therefore this unidentified USAF aircraft cannot be solved.

Chris Smolinski’s Black Cat Systems ALE Decoder has changed monitoring ALE messages which are widely used onf HF to provide an automatic link establishment. It has set the standard not only by its unsurpassed sensitivity and the option to decode up to 24 channels in parallel, but also with its look-up table for “translating” cryptic ALE callsigns into stations and locations of flesh and blood. Tahnks to this, the usual decoded message of just

  • 7527.0 [Frequency in kHz] USB [mode] 2021-11-10 22:54:24 [date/time] 16 [BER] TO TSC TIS K62

turns into:

  • 7527.0 USB 2021-11-10 22:54:24 16
    TO TSC COTHEN Technical Service Center Orlando FL USA
    TIS K62 USGC MH-65D/E Short Range Recovery Helicopter Dolphin #6562 USA

This blog entry provides a description of the system as well as a list of 3’200+ ALE callsigns as a First Aid Kit.

How Callsigns come into Life

This feature is a major achievement in DXing. And it is, too, that innovative that we have to set our sails into unchartered sea. [Do you remember the completely blank OCEAN-CHART. in Lewis Caroll’s “The Hunting of the Snark” from 1876? You are here!]

The general idea of the software is to look-up each decoded callsign in a list of tab-separated information where you already had collected metadata like organization, station, location, country – anything you consider important.
The software then looks up each callsign – as above TSC and K62 -, introduces all the information in a neat way and prints it all together in the window. Even more, as the software automatically fills a logfile with all this for later inspection, edition and further processing by spreadsheet or database. Smart! And unique!

The callsigns’ document and its quality (extent, reliability, consistency …), of course, plays a pivotal role, see following illustration – shit in, shit out.

Information is circling from your Reference Database into the decoder’s look-up files (folder “ale_callsigns”) and back.

Whatever format your Reference Database may have, it will and must put out a simple tab-separated textfile.

It helps if you think of different type of data (organization, location, country …) as of different fields or cells, each separated by a TAB from each other – see an example with just one entry below.
All data fenced in by TAB can contain arbitrary characters, such as spaces, brackets, commas etc.

ALE CallOrganizationNameLocationTypeITU
HNCUSCGHarriet LanePortsmouth VAWMEC-903USA
Each cell/field is separated by a TAB. “Harriet” and “Lane” are separated by just a blank and as a result handled as one cell/field “Harriet Lane”.

Different output Formats for different Tastes

The decoder may present the same decoded message plus the same information from your callsign file in different ways, controlled by the “Settings” menu of the decoder:

Let us now decline the different Message Formats for a simple message of LNT calling J10 on November 6th, 2021 at 22:19:59 UTC, with data from “ale_callsigns”, see lines 16 to 18 :

Same message and same decode, but different formats and different log entries as well.

The sources for e.g., line 42 are marked in colors:

Divide and conquer

The look-up table(s) must be saved in a directory called “ale_callsigns” (lower case!) in the Documents directory for your user account.

The look-up table must be saved in the Documents directory for your user account.

Above you see not only one callsigns’ file, but many. There is a reason for that: If you have a large callsign file, undoubtedly some one and the same callsign will be valid for two or several stations. If the software detects this case, it prints (original decoded message):

  • 03 5732.0 USB 2021-11-10 22:29:03 31 TWAS J51 Ambiguous – multiple entries

This is because the list contains (in this case) two entries under callsign J51, namely:

  • J51 Royal Moroccan Armed Forces MRC
  • J51 USGC MH-60T Medium Range Helicopter #6051 USA

You can evade this ambiguity by defining different jobs with matching callsigns lists. If you want to check the channels of USCG/COTHEN, you should query your database for USCG only, save this set and invoke just this reduced set of callsigns instead of the complete bunch – divide et impera. This technique in most cases reduces the problem or even avoids it at all.
There maybe also the effect of a “false positive”: if a callsign doubles on two different stations, but you have listed only one under this callsign, being this the wrong one for the given case.

Basic Reference List: Database or Spreadsheet

I keep my data in a very simple FileMaker database with each entry carrying an individual number ALE_ref.

Example for one entry in my FileMaker database

Then you can query the list: “Tell me all USCG entries located in Alaska!”, getting this window out of your database. This must be exported as TAB-separated file (“USCG_ALS”) and put into the “ale_callsigns” folder of your “Documents” directory.

Result after asking for all USCG entries, located in Alaska.

Of course, you may use any type of spreadsheet and/or database.

You can see the content of folder “ale_callsigns” in the dropdown menu “Callsigns” of the decoder. There you have the choice to select one, two or many files or even “all”.

Under “Callsigns” there are listed all available callsigns files. Here I choose file “Full.tab” with 3175 entries of which 2956 are unique – as the decoder tells you under tab ” Channel 1″.

Callsigns: A First Aid Kit, 3’000+ entries

To become a bit acquainted with this new function, I prepared a list of callsigns containing only very few basic data. It must, of course, contain the callsign for looking up. I then provided fields for the organziation (USCG), the station itself, its location and the ITU 3-letter code. All fields/cells mut be separated by a TAB. For each field which is left empty (i.e., if you don’t know the location), you must insert a TAB instead. Otherwise, the other data may be wrongly allocated in your log. I also tried to keep a balance of streamlined data and the obvious desire not to have be a Rear Admiral of the Navy to understand all the acronyms. The list works perfect for the decoder, plus as sink and as source for your by far more flexible reference database/spreadsheet.

I plan to extend the list as well as to correct the mistakes. Your support is welcome!

The list is a first approach in format and content. It surely works fine. As all work in this field, it combines information from many different sources, contributors to UDXF must be named first. The list is also flavored with my own monitoring log of more than 11000 entries, being all different in call/frequency. In addition, there is a lot of information around in the web – surprisingly often from the organizations themselves, but also from flight spotters, vessel spotters etc. I am sure that all information used is “open”, as otherwise I couldn’t had no access to it … got it?

You can download the zipped list here:

If this doesn’t work, drop me a line under dk8ok_at_gmx.net.

Decoding ADS-B with free QIRX software

QIRX’ dashboard, decoding ADS-B: in the middle you see spectrum and spectrogram (“waterfall”) of the ADS-B signals. The window at the bottom lists alls received aircraft with additional data, whereas the top window places them onto a map.

In the last two blog entries, I took a look at the DAB capabilities of free software QIRX by Clem Schmidt, DF9GI, from Frankfurt. It directly works with RTL-SDR, Airspy and RSP2 SDRs. I tried this very smart software from my location near Hannover/North Germany now also with ADS-B, mostly with my RSP2.

ADS-B stands for “Automatic Dependant Surveillance – Broadcast” and is an automatic service where aircraft continuously transmits several vital data on around 1.090MHz. Most important part of these data is the 2D location of the aircraft which it gets by GPS plus height by a baromatric altimeter. From this position data, many other data are derived, e.g. climbing/sinking or speed. If matched to databases, you will also see type of aircraft, flight number and many other data.

“The internet” provides many services showing the results of ADS-B and other data, collected from receivers all over the world, among them Flightradar24, OpenSky, FlightAware and AirNavRadarbox. They each provide many additional data, somtimes available at different schemes. Most provide free access to much of their data, with some more specific data behind their paywall. OpenSky as a scientific and non-profit organization offers billions of datasets for free, see Scientific Datasets. QIRX uses an OpenSky data base with about 650’000 entries.

Backbone of all these services is a net of ADS-B receivers, connected via the internet and curated by each company.

QIRX shows some capabilities of such a receiving station, using a proper antenna and a simple SDR. It decodes the I/Q stream of it. ADS-B is transmitted via pulse-position modulation, or ppm. The system is explained in ICAO Annex 10 Volume IV [free download].

With QIRX, you must set the sampling rate of you SDR to 200000[Hz], as other sampling rates won’t work, see screenshot below.

To decode ADS-B, you must set the sample rate for your SDR to 2000000Hz.

After that, and having started QIRX in ADS-B mode, decoding is done automatically. Release your seatbelts, and simply relax by viewing the activities above your head. Coverage largely depends on the “view” of you antenna and a few other factors like te sensitivity of your SDR and the attenuation of your cable connecting your antenna with your SDR. Some web services, thanks to anticipatory obedience/security reasons/data protection etc., do mute some “special” flights . This is not the case, of course, with this setup. QIRX always provides stable decoding at even low SNRs – great!

Last, but not least, please find below a comparison of FlightRadar24 and QIRX setup with Flight Number TK1554/THY6KG, Hannover->Istanbul, starting from Hannover Airport. One difference between both screenshots is that at my location (Burgdorf), I got the Airbus only after it had climbed to an atlitude of 200m or so, whereas the FR24 receivers are placed at positions allowing for tracking the aircraft from even the runway.

Starting from Hannover to Istanbul: the airbus on track around Hannover. Top window shows the flight via FlightRadar24 web service, and even from the runway. Bottom window shows it received with QIRX from Burgdorf (red point in the northeast).

Also small aircraft is equipped with transponders, but not necessarily with ADS-B transponders, broadcasting the position, derived from their GPS. These small aircraft may haveonly Mode-S transponders on board, transmitting identification, height and squawk (transponder code) as assigned by their responsible ATC, or Air Traffic Control.

HF: Doppler, Signal Level and Time

Two views of the carrier of Sofia-Kostinbrod on 9400kHz from 15:30 to 18:30 UTC: On top the frequency within a window of 2Hz height only, at the bottom the synchronized HF level of this carrier; see text. [Click onto the picture for a better view.]

What you see in the picture at the top, is a mostly hidden gem of HF propagation. I took the carrier of Sofia-Kostinbrod transmitter form Bulgaria (250kW) on 9400kHz and observed it for three hours. In the upper window you see the frequency wihtin a window of 2Hz height only. You see two strong carriers: one nearly in parallel to the x-axis, the other snaking some fraction of one Hertz below it.

With one transmitter only on this frequency: How does this happen?

It’s multipath propagation. The signal takes one way via a groundwave-like way, the upper trace. It reveals a very slight drift downwards. As I use a GNSS-controlled receiver, the FDM-S3 from Elad, this miniscule drift should be happen within the transmitter, not the receiver.
The snaking trace stems from a second way, most likely via the F2 layer of the ionosphere. As the ionosphere is prone to winds and an ever dynamic change of its ionization, it is moving. And with all moving objects, also this causes a Doppler effect to waves. This is exactly what we see – the angular speed of the ionosphere, relative to the “groundwave-like” signal.
You may also see at least two weaker traces, caused by two further ways, hence showing other Doppler shift.

In the diagram at the bottom, you see the combined level of all traces. Because they reach the reeiver at different time and, hence, different phases, their addition leads to an ever changing signal level, called: fading.

I hope to continue this work with some other examples in the future, also taking fade-in and fade-out into account.

Doppler: Following Airplanes’ tracks

Carrier and Doppler trace (left), locations of transmitter, receiver and track of flight NH8406 – March 27, 2021, around 16:45 UTC [click onto the screenshot for richer detail]

Working on a project which will focus on Doppler spread of HF channels (see at the bottom) and other impairements, I also bumped into some more prominent Doppler catches, namely on the VHF aero band. I took the AM carrier of nearby Hannover VOLMET on 127.4 MHz and observed doppler traces about plus/minus 200Hz the carrier frequency. Following the acitvity in the airspace via Flightradar24 in parallel, it is easy to match traces and aircrafts. In this case, I nailed cargo flight NH8406 from Frankfurt to Narita/Tokyo. It is important to remember what is shown in left part of the screenshot: it is the signal of Hannover VOLMET, reflected by this moving Boeing 777-F. Thus, the reflected frequency shows a Doppler frequency shift – depending on the relative speed in respect to transmitter and receiver. A positive Doppler frequency signals that the aircraft is approaching my location. When it turns to the lower frequencies, I see the aircraft passing.

Things get more complex wen it comes to the Doppler shift at HF propagation. You will also see planes, but effects from high winds in the upper atmosphere, coming and fading of ionospheric layers and the influences of the geomagnetic field are prevailing. Due to the much lower frequencies, the effects are just about a tenth compared to thie above example on VHF.

See below a result from my observations on HF as a preview.

Carrier of TRT Emirler, Turkey, in the 19 meter band. Just after sunrise, the carrier splits into two, and you also see double lines due to magnetoionic effects. The window shos about 3Hz in the vertical, and about 40 minutes in the horizontal scale.

Medium Wave: Signals May tell sunris/Sunset at their transmitter’s site

The two stronger carriers (Romania left, Algeria right) exhibit Doppler-shifted scatter; see text for a more detailed explanation.

During my expeditions into the thicket of mediumwave offsets, I bumped into pictures like that at the top. In the lower part of the screenshot, you see two carriers mit seahorse-like structures looking to the right. In the evening, they look towards the West.

This is one of the several effects which can be seen at local sunrise/sunset. Here, the carrier gets “clouded” and show frequency changes. These effects are associated with Doppler shift (moving of ionospheric patches/layers) as well as scattering caused by irregularities of the ionosphere, most notably Travelling Ionospheric Disturbances, or TID. Whereas the Doppler shift, by vertical moving of reflecting layers like combining of F1- and F2-layer to one and lower F-layer when approaching darkness, is comparatively small, high wind speeds in these regions can cause a much faster horizontal movement of such regions. This, in turn, may cause a Doppler shift of about 1Hz or even higher in the medium wave range.

The Figure at the top demonstrates this effect at two transmitters on 1422kHz, namely SRR Radio România Actualități from Râmnicu Vâlcea/Olănești (sunrise 05:55 UTC/sunset 15:12 UTC; distance 1433km) and Radio Coran/Radio UFC/Radio Culture/Chaîne 3 from Ouled Fayet/Algeria (sunrise 06:58 UTC/sunset 17:00 UTC; distance 1840 km). Seen from midnight, sunrise first occurs at the Romanian transmitter, followed by the Algerian one with the seahorse-like pattern of the scatter towards the higher frequencies. Around each local sunset, first Romania sees darkness, followed by Algeria. Here, the scatter pattern turns towards the lower frequencies. In the insert at the right, contrast has been sharpened to additionally reveal a split-up of these carriers due to propagation into two paths.

This effect often helps to determine the local sunrise/sunset of a carrier. I marked what presumably is the carrier of MBC Radio 1 from Matiya/Malawi, sunrise 03:22 UTC; listed 02:00 to 22:00 UTC, but obviously on a 24 hours’ service this Tuesday.

Both Figures at the bottom try for some detective work without knowing specific offsets (because not available) but relying only on schedule and the above mentioned propagational effect. Crime scene takes place on 1233kHz, where we want to scrutinize two channels, one on 1232,9937 kHz, the other on 1232,9951kHz.

Distinctive scatter, associated with local sunrise at the transmitter, provides a strong hint towards the location.

The s/off- and the s/on pattern match that of Chinese National Radio #17’s Kazakh service. Incidentally, sunrise takes place in Qinghe at 01:42 UTC, and in Boertala at 02:04UTC – next Figure. Boertala is listed with 10kW (stronger signal), Qinghe with 1kW. Unfortunately, the f/out time of other CNR17 transmitters on this channel is mostly covered by phase noise from Rádio Dechovka in the Czech Republic and Absolute Radio in the United Kingdom.

Some CNR17 locations and the terminator during sunrise in Boertala, see text. Visualized with free Simon’s World Map.

Here I am indebted to Jens Mielich, Head of the ionosonde at Juliusruh/Germany, who was so kind to comment on this observation. According to him, the observed Doppler shift of 1Hz on 1422kHz should have been caused by a refracting medium, moving at an (angular) speed of roughly 105m/s. At Juliusruh, he observed e.g., an ionospheric drift of 311m/s±93m/s from East towards West on January 19, 2021 at 04:19 UTC: “You will get a positive Doppler shift during a West/North drift, and a negative one at East/South drift.” He adds that further investigations on a more longer time series are needed.


PSKOVNDB: An exciting new software for Mediumwave DXers

See the bunch of carriers on 590kHz at the left. PskovNDB shows at the right a diagram of noise, the combined signal strength of the 200Hz window and the signal strength of the carrier just picked.
Here the very carrier of VOCM/St. John’s had been clicked instead. You easily see that this signal is dominating the channel – only one of the many exciting features of free PskovNDB software!

Recently, I came across an upgraded version of Ivan Monogarov’s PskovNDB software, already having collected all laurels available as being the Gold Standard for chasing non-directional beacon, or NDBs. Recently, Ivan had expanded his tool with some as unique as exciting features for the avid medium wave DXer.

At a first view, it converts recorded WAV files (also: RF64 format, done with SDRC V3 software) into spectrograms of high resolution in which you can easily see the number of stations, measure their precise offset and see their signal strength.

A second view reveals the smart feature of producing diagrams of each signal – plus noise level and the combined power of the whole window. You can see both in the screenshots on top of this page.

A third view almost exactly helps to distinguish between signals where you can here music, listen at least to some words or phrases, or which do provide full audio.

Nothing more? Yes. Under the hood, there is much more. So, you can do automatically recordings each day and also automatically send them to PskovNDB software for showing the spectrograms, one after the other, like on a film roll. This enables you to pick the recording of the most promising day(s) for further inspection.

I wrote a short introduction to the beta version of this free software, and Ivan was so kind to add some most helping notes to this. You can download it here. It contains also some additional information, i.e. a link for downloading the software.

Spassiba, Ivan, for another software breakthrough!

Medium Wave: Offset Atlas – all 9 kHz channels Plus VLF & Longwave, 24 hours

The “Atlas” shows screenshots of all 9kHz channels on Medium Wave within a 50Hz window, sometimes better. It also shows some odd channels plus Time Signal Stations on VLF and all Broadcasting Longwave Channels. You can download it for free to determine accurate and stable offset readings over 24 hours (zoom in by e.g. 400%)

With the new Elad FDM-S3 and its OCXO/GNSS-stabilized clock, I did a 24h recording of the whole medium wave band on January 19, 2021 in Northern Germany; plus longwave on Januar 21, 2021. Free software SDRC V3 enabled me to make up a spectrogram of each channel within a window of 50Hz width, and at a frequency raster of 9kHz on medium wave. You can easily see:

  • sign-on/sign-off
  • fade-in/fade-out
  • accurate and stable frequency offset over full 24h down to a millihertz
  • frequency control of the transmitter’s oscillator (stable, drift, sinus, sawtooth …)
  • propagational effects (doppler, scatter …)

The format is PDF, DIN-A4, landscape, resolution 300dpi – see screenshot at the bottom. This allows you to zoom to a factor of about 400% to search for details and better read out of the time/frequency scale. It weighs 865MB. You can download it here, and open it with your PDF reader (you can also point your mouse cursor onto the link, click right mouse key, and choose “Save under …”). Leafing from one page to another gives an interesting overview.

A similar Atlas showing a raster of 10kHz is also available for free – just scroll to the previous post of this blog. It is also planned to publish a general article about the background, about what to do with such a tool, and how to do this by yourself.

I am sure that it will open some new horizons on Medium Wave DXing, including accurate offsets over up to 24h.

Medium Wave: Offset Atlas – all 10 kHz channels, 24 hours

The “Atlas” shows screenshots of all 10kHz channels on Medium Wave within a 50Hz window, sometimes better. You can download it for free to determine accurate and stable offset readings over 24 hours (zoom in by e.g. 400%)

With the new Elad FDM-S3 and its OCXO/GNSS-stabilized clock, I did a 24h recording of the whole medium wave band on January 19, 2021 in Northern Germany. Free software SDRC V3 enabled me to make up a spectrogram of each channel within a window of 50Hz width, and at a frequency raster of 10kHz. You can easily see:

  • sign-on/sign-off
  • fade-in/fade-out
  • accurate and stable frequency offset over full 24h down to a millihertz
  • frequency control of the transmitter’s oscillator (stable, drift, sinus, sawtooth …)
  • propagational effects (doppler, scatter …)

The format is PDF, DIN-A4, landscape, resolution 300dpi – see screenshot at the bottom. This allows you to zoom to a factor of about 400% to search for details and better read out of the time/frequency scale. It weighs 559MB. You can download it here, and open it with your PDF reader (you can also point your mouse cursor onto the link, click right mouse key, and choose “Save under …”). Leafing from one page to another gives an interesting overview.

Yes, a similar Atlas showing a raster of 9kHz is under way and will be published also here in due time. It is also planned to publish a general article about the background, about what to do with such a tool, and how to do this by yourself.

I am sure that it will open some new horizons on Medium Wave DXing, including accurate offsets over up to 24h.

Aloha: KUAU from Haiku/Hawaii, received on January 19, 2021 by DK8OK. Proofs are frequency, plus the rather unique fade-in/fade-out in the European afternoon.

Comments and suggestions are appreciated: dk8ok@gmx.net.

Millihertzing with Software “Carrier Sleuth”

24 hours on 590kHz on January 19, 2021 in Northern Germany, reveals a couple of North American signals with VOCM of St. John’s, Newfoundland being the strongest and KQNT Spokane on 590.002kHz/Washington State the most interesting with reception also in the afternoon.

“Millihertzing” seems to become “le must” of this season. The most recent software stems from smart software author Chris Smolinski, W3HFU, who over many years offers inspiring software,this new one dubbed Carrier Sleuth. It mainly analyzes I/Q-WAV files from software-defined radios at high resolution, being a perfect tool for measuring offset frequencies on mediumave. The screenshot at top shows such a spectrogram which covers 20Hz in width and 24h in length on 590kHz.

Why using “Carrier Sleuth”, when haveing SDRC V3 at hand? First, it works together with a multitude of WAV formats from many different SDR software (see Chris’ list, which is still expanding). Secondly, it let you hop from one channel (9kHz or 10kHz) to the next – if a proper part of the spectrum has already been converted from WAV to FFT. It also provides coverting spectrograms to CSV to apply some statistics on each signal. There are many more smart feature, and Chris will even add some exciting more, e.g. processing I/Q files in real time to save a lot of time.

With my bread-and-butter software being SDRC V3, recording in WAV RF64 one-file format (which sometime swells to nearly 10TB), “Carrier Sleuth” can even digest these recordings with a workaround: specify an interesting part of the medium wave, defined by upper and lower channel and time segment, and convert this into simple WAV. This is easily done with SDRC V3’s Data File Editor. It is also the way, Carrier Sleuth produced the screenshot at top of this page.

Chris published this software first on December 10, 2020. He eagerly looks for bug reports, applications and further suggestions form the users. Take a free test drive; registration code 19.99 US-$.

« Older Entries