Author Archive
YADD
Maritime Traffic - courtesy: www.marinetraffic.com/ |
Until very recently, I had believed that there were no longer any HF maritime operations left, other than various Coast Guard weather announcements and an emergency watch on certain USB frequencies.
Over the past week I have discovered that HF maritime activity is still alive and well, through the worldwide Digital Selective Calling (DSC) system, which has been around in one form or another since the early 90's as part of the Global Maritime Distress and Safety System (GMDSS) ... I guess I was just asleep at the switch, having not been aware of the HF DSC activity!
Although it's not CW, there's still ample opportunity to hear and follow global shipping traffic as vessels of all types contact coastal land stations or call each other. One requirement that keeps the DSC frequencies busy is the requirement for vessels to test their systems at least once per week, providing many opportunities to log various coastal stations or add a new ship to your logbook. Ships can be heard calling coastals for a routine signal test, setting up an SSB phone QSO on a specified frequency or just calling another ship for a test or a phone sked. As well, DSC can be used to send a distress message alert in times of emergency.
Messages are sent in an error-correcting FSK mode, similar to the Navtex system, using the same speed and shift of 100 baud /170Hz. There are a few programs that can be used to decode the DSC messages but one of the best and most popular is the freely available "YADD", by Dirk Claessens .
YADD stands for "Yet Another DSC Decoder" and is an offshoot of Dirk's equally popular and effective "YAND", a free Navtex decoder.
YADD and several other software decoders can be downloaded from the NDB List Info site ... the best source of hands-on information for topics involving NDBs, Navtex, DGPS, DSC DXing and more.
After downloading and installing YADD and setting audio levels correctly, YADD began decoding signals with ease.
The spectrum display at the top of YADD's screen shows the audio passband coming from the receiver. With the receiver in the CW mode, DSC signals will appear on the frequency that your receiver's BFO offset frequency is set for. I prefer an offset of 400Hz so the spectrum display shows the signal at 400Hz, with the tuning cursor centered on a signal. A narrow CW filter should also be selected but no narrower than 170Hz.
Each vessel using the system, as well as the coastal land stations, have a unique 9-digit MMSI number (Maritime Mobile Service Identity). Once the software detects the MMSI numbers being used, it can then display the vessel's name (or the coastal's location and distance) so you know who you are listening to ... it's all very slick!
After initially running my receiver for a few minutes on the 12MHz DSC channel, I decided to look up the location of the first two ships I had heard, using one of the Internet's marine traffic sites.
I was surprised to find that my first catch was a large tanker under way in Kola Bay, having just departed Murmansk, in the Russian Arctic. Vessel number two was also under way along the east coast of South Korea.
The YADD screen above is showing the large bulk carrier 'SALANDI' (3FEB9) calling Rio de Janeiro Radio (PWZ) today on 16804.5KHz.
Courtesy: Henk Guddee |
I soon discovered an active group of DSC DXers in Yahoo Group's DSC List, which I quickly joined and started asking a lot of questions. The 'Files' section also contains the latest list of ship MMSI numbers so that your YADD look-up text file can be kept up-to-date.
One of the group members, GM4SLV, has set up a wonderful website called YaDDNet devoted to collecting and posting listener's decoded loggings in realtime. One of YADD's features is the ability to automatically upload decoded signals, similar to PSK Reporter. It's an easy 30-second job to configure YADD to upload your spots to the net. His site also contains the latest MMSI look-up file used by YADD which is updated in real time from the latest log postings ... presently at 34,566 vessels!
Clicking on any of the uploaded ship names displayed in the real time YaDDNet log, automatically takes you to an online vessel-tracking site which usually has a picture of the ship along with all of its information, including its present position.
If you set up YADD to do some listening, I'd strongly urge you to also set it up so that your decoded spots are uploaded to the YaDDNet page in real time. Configuring this capability is very simple. Your latest logs will also keep the MMSI database up-to-date for all YADD users.
If, like me, you have missed the maritime CW activity on HF, you may find monitoring DSC traffic of interest ... both ships and coastals. I may even try QSLing some of the coastals again, many of which will still issue a traditional card QSL, upholding a long standing shortwave radio tradition ... but grab them while you can!
From my collection. Heard 4349KHz CW Aug '96 |
YADD
Maritime Traffic - courtesy: www.marinetraffic.com/ |
Until very recently, I had believed that there were no longer any HF maritime operations left, other than various Coast Guard weather announcements and an emergency watch on certain USB frequencies.
Over the past week I have discovered that HF maritime activity is still alive and well, through the worldwide Digital Selective Calling (DSC) system, which has been around in one form or another since the early 90's as part of the Global Maritime Distress and Safety System (GMDSS) ... I guess I was just asleep at the switch, having not been aware of the HF DSC activity!
Although it's not CW, there's still ample opportunity to hear and follow global shipping traffic as vessels of all types contact coastal land stations or call each other. One requirement that keeps the DSC frequencies busy is the requirement for vessels to test their systems at least once per week, providing many opportunities to log various coastal stations or add a new ship to your logbook. Ships can be heard calling coastals for a routine signal test, setting up an SSB phone QSO on a specified frequency or just calling another ship for a test or a phone sked. As well, DSC can be used to send a distress message alert in times of emergency.
Messages are sent in an error-correcting FSK mode, similar to the Navtex system, using the same speed and shift of 100 baud /170Hz. There are a few programs that can be used to decode the DSC messages but one of the best and most popular is the freely available "YADD", by Dirk Claessens .
YADD stands for "Yet Another DSC Decoder" and is an offshoot of Dirk's equally popular and effective "YAND", a free Navtex decoder.
YADD and several other software decoders can be downloaded from the NDB List Info site ... the best source of hands-on information for topics involving NDBs, Navtex, DGPS, DSC DXing and more.
After downloading and installing YADD and setting audio levels correctly, YADD began decoding signals with ease.
The spectrum display at the top of YADD's screen shows the audio passband coming from the receiver. With the receiver in the CW mode, DSC signals will appear on the frequency that your receiver's BFO offset frequency is set for. I prefer an offset of 400Hz so the spectrum display shows the signal at 400Hz, with the tuning cursor centered on a signal. A narrow CW filter should also be selected but no narrower than 170Hz.
Each vessel using the system, as well as the coastal land stations, have a unique 9-digit MMSI number (Maritime Mobile Service Identity). Once the software detects the MMSI numbers being used, it can then display the vessel's name (or the coastal's location and distance) so you know who you are listening to ... it's all very slick!
After initially running my receiver for a few minutes on the 12MHz DSC channel, I decided to look up the location of the first two ships I had heard, using one of the Internet's marine traffic sites.
I was surprised to find that my first catch was a large tanker under way in Kola Bay, having just departed Murmansk, in the Russian Arctic. Vessel number two was also under way along the east coast of South Korea.
The YADD screen above is showing the large bulk carrier 'SALANDI' (3FEB9) calling Rio de Janeiro Radio (PWZ) today on 16804.5KHz.
Courtesy: Henk Guddee |
I soon discovered an active group of DSC DXers in Yahoo Group's DSC List, which I quickly joined and started asking a lot of questions. The 'Files' section also contains the latest list of ship MMSI numbers so that your YADD look-up text file can be kept up-to-date.
One of the group members, GM4SLV, has set up a wonderful website called YaDDNet devoted to collecting and posting listener's decoded loggings in realtime. One of YADD's features is the ability to automatically upload decoded signals, similar to PSK Reporter. It's an easy 30-second job to configure YADD to upload your spots to the net. His site also contains the latest MMSI look-up file used by YADD which is updated in real time from the latest log postings ... presently at 34,566 vessels!
Clicking on any of the uploaded ship names displayed in the real time YaDDNet log, automatically takes you to an online vessel-tracking site which usually has a picture of the ship along with all of its information, including its present position.
If you set up YADD to do some listening, I'd strongly urge you to also set it up so that your decoded spots are uploaded to the YaDDNet page in real time. Configuring this capability is very simple. Your latest logs will also keep the MMSI database up-to-date for all YADD users.
If, like me, you have missed the maritime CW activity on HF, you may find monitoring DSC traffic of interest ... both ships and coastals. I may even try QSLing some of the coastals again, many of which will still issue a traditional card QSL, upholding a long standing shortwave radio tradition ... but grab them while you can!
From my collection. Heard 4349KHz CW Aug '96 |
July’s EME Window
With QSLs still arriving from previous 2m EME action, I was looking extra forward to late July's very short window.
When last month's activity was interrupted by my 140W brick amplifier catching fire, I was anxious to see if my repairs and homebrew RFC would still allow me to play on the moon. With July's best-positioned moonrises being too close to the sun (which was also rising at the same time), I was only able to spend a short time over two days before the moon travelled too far to the south and into my neighbour's trees.
Luckily I was rewarded with what seemed like very good lunar conditions, enabling me to easily work six different stations ... three of them being all-time new ones and boosting my EME initials total to 112.
I2FAK Franco / 16x19 el array
RK3FG Anatoly / 4x15 el array
G4SWX John / 4x16 el array
F4DJK Paul / 4x11 el array / #110
F5AQX Andre / 4x11 el array / #111
DL9DBJ Hartmut / 4x10 el array / #112
In addition, DL1VPL told me that he was able to copy me with his single 12el Yagi during the QSO with I2FAK! Needless to say, a contact between two single Yagi stations would be truly remarkable. I've only been able to copy a single Yagi station once over the years.
I was gratified to see that letting the smoke out of my little amplifier last month apparently caused no permanent damage and the repair seems to be holding up ... but I'll leave the bottom off for now just in case it gets any more crazy ideas.
When last month's activity was interrupted by my 140W brick amplifier catching fire, I was anxious to see if my repairs and homebrew RFC would still allow me to play on the moon. With July's best-positioned moonrises being too close to the sun (which was also rising at the same time), I was only able to spend a short time over two days before the moon travelled too far to the south and into my neighbour's trees.
Luckily I was rewarded with what seemed like very good lunar conditions, enabling me to easily work six different stations ... three of them being all-time new ones and boosting my EME initials total to 112.
I2FAK Franco / 16x19 el array
RK3FG Anatoly / 4x15 el array
G4SWX John / 4x16 el array
F4DJK Paul / 4x11 el array / #110
F5AQX Andre / 4x11 el array / #111
DL9DBJ Hartmut / 4x10 el array / #112
In addition, DL1VPL told me that he was able to copy me with his single 12el Yagi during the QSO with I2FAK! Needless to say, a contact between two single Yagi stations would be truly remarkable. I've only been able to copy a single Yagi station once over the years.
F4DJK's 4x11 el array |
F5AQX's 4x11 el array |
DJ9DBJ's 4x10 el array |
I was gratified to see that letting the smoke out of my little amplifier last month apparently caused no permanent damage and the repair seems to be holding up ... but I'll leave the bottom off for now just in case it gets any more crazy ideas.
July’s EME Window
With QSLs still arriving from previous 2m EME action, I was looking extra forward to late July's very short window.
When last month's activity was interrupted by my 140W brick amplifier catching fire, I was anxious to see if my repairs and homebrew RFC would still allow me to play on the moon. With July's best-positioned moonrises being too close to the sun (which was also rising at the same time), I was only able to spend a short time over two days before the moon travelled too far to the south and into my neighbour's trees.
Luckily I was rewarded with what seemed like very good lunar conditions, enabling me to easily work six different stations ... three of them being all-time new ones and boosting my EME initials total to 112.
I2FAK Franco / 16x19 el array
RK3FG Anatoly / 4x15 el array
G4SWX John / 4x16 el array
F4DJK Paul / 4x11 el array / #110
F5AQX Andre / 4x11 el array / #111
DL9DBJ Hartmut / 4x10 el array / #112
In addition, DL1VPL told me that he was able to copy me with his single 12el Yagi during the QSO with I2FAK! Needless to say, a contact between two single Yagi stations would be truly remarkable. I've only been able to copy a single Yagi station once over the years.
I was gratified to see that letting the smoke out of my little amplifier last month apparently caused no permanent damage and the repair seems to be holding up ... but I'll leave the bottom off for now just in case it gets any more crazy ideas.
When last month's activity was interrupted by my 140W brick amplifier catching fire, I was anxious to see if my repairs and homebrew RFC would still allow me to play on the moon. With July's best-positioned moonrises being too close to the sun (which was also rising at the same time), I was only able to spend a short time over two days before the moon travelled too far to the south and into my neighbour's trees.
Luckily I was rewarded with what seemed like very good lunar conditions, enabling me to easily work six different stations ... three of them being all-time new ones and boosting my EME initials total to 112.
I2FAK Franco / 16x19 el array
RK3FG Anatoly / 4x15 el array
G4SWX John / 4x16 el array
F4DJK Paul / 4x11 el array / #110
F5AQX Andre / 4x11 el array / #111
DL9DBJ Hartmut / 4x10 el array / #112
In addition, DL1VPL told me that he was able to copy me with his single 12el Yagi during the QSO with I2FAK! Needless to say, a contact between two single Yagi stations would be truly remarkable. I've only been able to copy a single Yagi station once over the years.
F4DJK's 4x11 el array |
F5AQX's 4x11 el array |
DJ9DBJ's 4x10 el array |
I was gratified to see that letting the smoke out of my little amplifier last month apparently caused no permanent damage and the repair seems to be holding up ... but I'll leave the bottom off for now just in case it gets any more crazy ideas.
Hunting For NDBs In CLE 221
YBV - 370kHz (VE3GOP) |
This coming weekend will see another CLE challenge. This time the hunting grounds will be: 370.0 - 384.9 kHz.
For those unfamiliar with this monthly activity, a 'CLE' is a 'Co-ordinated Listening Event', as NDB DXers around the world focus their listening time on one small slice of the NDB spectrum.
A nice challenge in this one is to hear the Berens River (Manitoba) NDB, 'YBV', on 370 kHz. 'YBV' is a 25-watter and is well heard, having been logged from coast-to-coast as well as in Europe. Look for 'YBV's CW identifier, repeated every 10.4 seconds, on 370.373 kHz with your receiver in the CW mode.
YBV's 25W TX Rack (VE3GOP) |
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. Listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are modulated with a 1020 Hz tone approximately.
For example, 'AA' in Fargo transmits on 365 kHz and its upper sideband CW identifier is tuned at 366.025 kHz while its lower sideband CW ident can be tuned at 363.946 kHz. Its USB tone is actually 1025 Hz while its LSB tone is 1054 Hz.
Often, one sideband will be much stronger than the other so if you don't hear the first one, try listening on the other sideband.
Canadian NDBs normally have an USB tone only, usually very close to 400 Hz. They also have a long dash (keydown) following the CW identifier.
All NDBs heard in North America will be listed in the RNA database (updated daily) while those heard in Europe may be found in the REU database. Beacons heard outside of these regions will be found in the RWW database.
From CLE organizer Brian Keyte, G3SIA, comes the usual 'heads-up':
Hi all,
Please join us in our 221st coordinated Listening Event which starts
this Friday. All are very welcome.
Please join us in our 221st coordinated Listening Event which starts
this Friday. All are very welcome.
CLEs are not contests - if you enjoy taking part you will be a winner!
54 of us sent logs for CLE204 back in February 2016 when we
listened on these same frequencies.
It will certainly be tougher for most of us at this time of year.
Days: Friday 28 July - Monday 31 July
Times: Start and end at midday, your LOCAL TIME
Range: 370 - 384.9 kHz
Just log all the NDBs that you can identify with their nominal (listed)
frequencies in the range (it includes 370 kHz, but not 385 kHz)
plus any UNIDs that you come across there.
Please send your CLE log to the List in a plain text email if possible
(not in an attachment) with 'CLE221' at the start of its title.
Show on each log line:
# The date (e.g. 2017-07-29, etc., or just 29) and UTC.
(the date changes at 00:00 UTC)
# kHz (the nominal published frequency, if known)
# The Call Ident.
Show those main items FIRST - other optional details such as Location
and Distance go LATER in the same line.
If you send interim logs, please also send a 'Final' (complete) log.
As always, tell us your own location and brief details of the equipment
that you were using during the weekend.
I'll send the usual 'Any More Logs?' email at about 17:00 UTC on
Tuesday - you can check from it that your log has been found OK.
All logs must arrive on the list by 08:00 UTC on Wednesday 2nd
August at the very latest.
Joachim has again offered to make the combined results which he
Range: 370 - 384.9 kHz
Just log all the NDBs that you can identify with their nominal (listed)
frequencies in the range (it includes 370 kHz, but not 385 kHz)
plus any UNIDs that you come across there.
Please send your CLE log to the List in a plain text email if possible
(not in an attachment) with 'CLE221' at the start of its title.
Show on each log line:
# The date (e.g. 2017-07-29, etc., or just 29) and UTC.
(the date changes at 00:00 UTC)
# kHz (the nominal published frequency, if known)
# The Call Ident.
Show those main items FIRST - other optional details such as Location
and Distance go LATER in the same line.
If you send interim logs, please also send a 'Final' (complete) log.
As always, tell us your own location and brief details of the equipment
that you were using during the weekend.
I'll send the usual 'Any More Logs?' email at about 17:00 UTC on
Tuesday - you can check from it that your log has been found OK.
All logs must arrive on the list by 08:00 UTC on Wednesday 2nd
August at the very latest.
Joachim has again offered to make the combined results which he
hopes to complete on that day.
To help your listening, seeklists and maps for your part of the World
To help your listening, seeklists and maps for your part of the World
are available via the CLE page http://www.ndblist.info/cle.htm
Good listening - enjoy the CLE
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA ndbcle'at'gmail.com
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
Good listening - enjoy the CLE
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA ndbcle'at'gmail.com
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
These listening events serve several purposes. They:
- determine, worldwide, which beacons are actually in service and on-the-air so the online database can be kept up-to-date
- determine, worldwide, which beacons are out-of-service or have gone silent since the last CLE covering this range
- will indicate the state of propagation conditions at the various participant locations
- will give you an indication of how well your LF/MF receiving system is working
- give participants a fun yet challenging activity to keep their listening skills honed
Final details can be found at the NDB List website, and worldwide results, for every participant, will be posted there a few days after the event. If you are a member of the ndblist Group, results will also be e-mailed and posted there.
The very active Yahoo ndblist Group is a great place to learn more about the 'Art of NDB DXing' or to meet other listeners in your region. There is a lot of good information available there and new members are always very welcome. As well, you can follow the results of other CLE participants from night to night as propagation is always an active topic of discussion.
If you are contemplating getting started on 630m, listening for NDBs is an excellent way to test out your receive capabilities as there are several NDBs located near this part of the spectrum.
You need not be an ndblist member to participate in the CLEs and all reports, no matter how small, are of much value to the organizers.
'First-time' logs are always VERY welcome!
Reports may be sent to the ndblist or e-mailed to either myself or CLE co-ordinator, Brian Keyte (G3SIA), whose address appears above.
Please ... give the CLE a try ... then let us know what NDB's can be heard from your location! Your report can then be added to the worldwide database to help keep it up-to-date.
Good hunting!
Hunting For NDBs In CLE 221
YBV - 370kHz (VE3GOP) |
This coming weekend will see another CLE challenge. This time the hunting grounds will be: 370.0 - 384.9 kHz.
For those unfamiliar with this monthly activity, a 'CLE' is a 'Co-ordinated Listening Event', as NDB DXers around the world focus their listening time on one small slice of the NDB spectrum.
A nice challenge in this one is to hear the Berens River (Manitoba) NDB, 'YBV', on 370 kHz. 'YBV' is a 25-watter and is well heard, having been logged from coast-to-coast as well as in Europe. Look for 'YBV's CW identifier, repeated every 10.4 seconds, on 370.373 kHz with your receiver in the CW mode.
YBV's 25W TX Rack (VE3GOP) |
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. Listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are modulated with a 1020 Hz tone approximately.
For example, 'AA' in Fargo transmits on 365 kHz and its upper sideband CW identifier is tuned at 366.025 kHz while its lower sideband CW ident can be tuned at 363.946 kHz. Its USB tone is actually 1025 Hz while its LSB tone is 1054 Hz.
Often, one sideband will be much stronger than the other so if you don't hear the first one, try listening on the other sideband.
Canadian NDBs normally have an USB tone only, usually very close to 400 Hz. They also have a long dash (keydown) following the CW identifier.
All NDBs heard in North America will be listed in the RNA database (updated daily) while those heard in Europe may be found in the REU database. Beacons heard outside of these regions will be found in the RWW database.
From CLE organizer Brian Keyte, G3SIA, comes the usual 'heads-up':
Hi all,
Please join us in our 221st coordinated Listening Event which starts
this Friday. All are very welcome.
Please join us in our 221st coordinated Listening Event which starts
this Friday. All are very welcome.
CLEs are not contests - if you enjoy taking part you will be a winner!
54 of us sent logs for CLE204 back in February 2016 when we
listened on these same frequencies.
It will certainly be tougher for most of us at this time of year.
Days: Friday 28 July - Monday 31 July
Times: Start and end at midday, your LOCAL TIME
Range: 370 - 384.9 kHz
Just log all the NDBs that you can identify with their nominal (listed)
frequencies in the range (it includes 370 kHz, but not 385 kHz)
plus any UNIDs that you come across there.
Please send your CLE log to the List in a plain text email if possible
(not in an attachment) with 'CLE221' at the start of its title.
Show on each log line:
# The date (e.g. 2017-07-29, etc., or just 29) and UTC.
(the date changes at 00:00 UTC)
# kHz (the nominal published frequency, if known)
# The Call Ident.
Show those main items FIRST - other optional details such as Location
and Distance go LATER in the same line.
If you send interim logs, please also send a 'Final' (complete) log.
As always, tell us your own location and brief details of the equipment
that you were using during the weekend.
I'll send the usual 'Any More Logs?' email at about 17:00 UTC on
Tuesday - you can check from it that your log has been found OK.
All logs must arrive on the list by 08:00 UTC on Wednesday 2nd
August at the very latest.
Joachim has again offered to make the combined results which he
Range: 370 - 384.9 kHz
Just log all the NDBs that you can identify with their nominal (listed)
frequencies in the range (it includes 370 kHz, but not 385 kHz)
plus any UNIDs that you come across there.
Please send your CLE log to the List in a plain text email if possible
(not in an attachment) with 'CLE221' at the start of its title.
Show on each log line:
# The date (e.g. 2017-07-29, etc., or just 29) and UTC.
(the date changes at 00:00 UTC)
# kHz (the nominal published frequency, if known)
# The Call Ident.
Show those main items FIRST - other optional details such as Location
and Distance go LATER in the same line.
If you send interim logs, please also send a 'Final' (complete) log.
As always, tell us your own location and brief details of the equipment
that you were using during the weekend.
I'll send the usual 'Any More Logs?' email at about 17:00 UTC on
Tuesday - you can check from it that your log has been found OK.
All logs must arrive on the list by 08:00 UTC on Wednesday 2nd
August at the very latest.
Joachim has again offered to make the combined results which he
hopes to complete on that day.
To help your listening, seeklists and maps for your part of the World
To help your listening, seeklists and maps for your part of the World
are available via the CLE page http://www.ndblist.info/cle.htm
Good listening - enjoy the CLE
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA ndbcle'at'gmail.com
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
Good listening - enjoy the CLE
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA ndbcle'at'gmail.com
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
These listening events serve several purposes. They:
- determine, worldwide, which beacons are actually in service and on-the-air so the online database can be kept up-to-date
- determine, worldwide, which beacons are out-of-service or have gone silent since the last CLE covering this range
- will indicate the state of propagation conditions at the various participant locations
- will give you an indication of how well your LF/MF receiving system is working
- give participants a fun yet challenging activity to keep their listening skills honed
Final details can be found at the NDB List website, and worldwide results, for every participant, will be posted there a few days after the event. If you are a member of the ndblist Group, results will also be e-mailed and posted there.
The very active Yahoo ndblist Group is a great place to learn more about the 'Art of NDB DXing' or to meet other listeners in your region. There is a lot of good information available there and new members are always very welcome. As well, you can follow the results of other CLE participants from night to night as propagation is always an active topic of discussion.
If you are contemplating getting started on 630m, listening for NDBs is an excellent way to test out your receive capabilities as there are several NDBs located near this part of the spectrum.
You need not be an ndblist member to participate in the CLEs and all reports, no matter how small, are of much value to the organizers.
'First-time' logs are always VERY welcome!
Reports may be sent to the ndblist or e-mailed to either myself or CLE co-ordinator, Brian Keyte (G3SIA), whose address appears above.
Please ... give the CLE a try ... then let us know what NDB's can be heard from your location! Your report can then be added to the worldwide database to help keep it up-to-date.
Good hunting!
Canada Post / QSLs / Magicband Transformations
Several weeks ago I mused about my interest in earth-mode VLF experiments, following the inspirational exploits of G3XBM in his earth-mode work a few years ago.
His low powered system utilizing a 5W audio IC and simple circuitry produced surprisingly interesting results over several kilometers.
With possible future experimenting in mind, I found a nice low-powered IC audio amplifier kit from China on e-Bay, capable of producing about 18W at 12V ... more with higher voltage and proper heat-sinking.
Whenever buying from China, I look for a dealer with the highest feedback rating and always compare their complaints versus the number of orders shipped. There always seems to be a few that are 99.9 - 100%, which, for me, has always assured that they are probably not selling junk. Anything lower than 98% can often be a red flag.
The kit was just $1.50 and with free-shipping, what's to lose?
A few weeks after I had placed my order, the nightly TV news had a spot regarding the problem that these "free shipping" packets were creating for Canada Post and their customers. It seems that in the past few months, as more and more "free" shipments were arriving from the far east, Canada Post had not been able to keep up with the processing. The news spot showed row upon row of shipping containers parked at the back of Vancouver International's (YVR) postal processing plant, with all of them filled with thousands of small "free" packets waiting to be processed!
It seems that each packet needs to be scanned by the border security folks (CBSA) for illegal material before it can be processed by Canada Post and the back-up was building at a tremendous rate. There appears to be little if any profit for Canada Post with these smaller untracked packages and they are given the lowest priority-rating possible.
In order to speed up the process, both CBSA and Canada Post facilities would need to expand their operational capabilities at the airport and I suspect there is no serious will to do this until pressured politically by angry customers.
All parcels from China that are mailed to Canada stop at Vancouver's YVR before going further. The mammoth recent increase in online "free-shipping", in spite of the normally estimated 3-4 week delivery time, has proven too attractive for customers and our domestic system has failed to meet the new load demands.
With this new information in mind, my e-Bay purchase would prove to be an interesting test of the system and of the TV news spot's accuracy. Normally, I would have expected my tiny parcel to arrive in about 30 days, but mine would be one that eventually ended up in the airport parking lot.
The kit finally arrived this week, with a delivery time of 89 days! Many online sellers will offer an inexpensive option to pay for faster shipping, something that will still take a couple of weeks but much better than three months. If you are given this inexpensive shipping option I would highly recommend that you choose it, and if not, ask for an alternative to "free shipping". Unless something changes soon, delays will continue to increase.
I also wonder, and perhaps you can comment below, are U.S. customers seeing the same long delays as we here in Canada are experiencing when the "free shipping" option is chosen?
QSLs in my mailbox always excite me ... especially like yesterday's, arriving in a thin light-brown envelope decorated with colorful stamps.
I'm 100% certain this is because of receiving similar-appearing envelopes containing QSL cards during my formative years from age eleven onward and how much enjoyment the cards from shortwave stations all over the world brought me at this young age. For me, there is no replacement for a paper QSL, but sadly, this long-standing tradition is slowly slipping away due to the high cost of mailing even a normal-size envelope.
Earlier this summer I had a nice run of JA's on 6m Es but this time, instead of CW, they were on JT65A. Yesterday's card was for one of the digital contacts.
Signals were weak, at -23 db ... far too weak to be heard on CW but easily readable during the 60 second deep-listen period mandated by the JT65A mode. With so many stations now listening higher in the band for JT-mode signals, there has been very little activity on CW and now, with the introduction of yet another new digital mode, FT8, even the digital activity is split into sections, with neither mode being compatible.
I have held off installing the newer WSJT-X version containing the FT8 fifteen-second transmission mode until all of the bugs are ironed out ... the software will likely be tweaked a few more times yet before it reaches the polished final version we see for JT65 and others.
FT8 has been designed for weaker 6m Es openings that are often too short in duration for the longer time periods needed by JT65's sixty-second sequences. FT8 contacts can be completed quickly, before short-lived signals can drop out, but the shorter sequences come at the cost of reduced sensitivity ... probably a worthwhile tradeoff.
Conventional mode activity on 6m has suffered tremendously with the introduction of these new modes and it seems that if you want to work weak signal DX (and not all do), sadly it may be digital or nothing at all if the trends continue.
If all of the DX moves from CW to digital, for me, much of the magic will disappear as well. Letting the computer do all of the thinking is not nearly as satisfying or enjoyable as using my brain and CW skills to put a new rare one in the log. Six meters continues to evolve and I'm not overly excited by the direction it seems to be going.