Author Archive
MFJ / Timewave Noise Canceller Shootout
July 1st, 2017 | 
Author: 
A previous blog described a series of tests that Mark, VA7MM, performed demonstrating the effectiveness of his newly acquired MFJ- 1026 Noise Canceller.
He, along with Guy, VA7GI, recently had the opportunity to compare the performance of the MFJ against Guy's Timewave ANC-4.
I'll let Mark describe the results:
I'll let Mark describe the results:
NoiseCancellerShootout 2017 Report:
Guy Immega, VA7GI, and Mark Mattila, VA7MM, undertook side by side comparative tests of Timewave ANC-4 and MFJ-1026 noise cancellation gear (photos attached) by listening to interference at VA7MM in the HF spectrum between 7 MHz and 14 MHz. The program Spectran was used with the receiver on AM to adjust each unit for best performance and observe the relative performance of each. A system of coaxial relays was used to switch instantaneously between the units (photos attached).
Findings:
For practical purposes Timewave’s ANC-4 and MFJ’s 1026 are equal performers for eliminating interference in the HF spectrum.
Our findings corroborate the earlier findings of VE7CA that are posted on his website.
Switching the units in and out of noise was previously assessed on 40m CW, broadcast and raw noise. Examples of these tests are in a previous blogspot.
Commentary:
- main antenna in the tests was a multiband dipole at 30m above the ground.
- noise sense antenna was a Cushcraft R7 vertical antenna located 20m away from the main antenna.
- receiver was an Icom IC-746Pro.
- main antenna in the tests was a multiband dipole at 30m above the ground.
- noise sense antenna was a Cushcraft R7 vertical antenna located 20m away from the main antenna.
- receiver was an Icom IC-746Pro.
- both units tested have the same nulling capability.
- the preamp on the MFJ was found to be useful in certain instances for boosting the noise signal.
- in one test instance the Timewave unit produced intermod with AM broadcast leaking into the receiver when the noise gain was set near maximum.
- in instances where noise was coming from more than one direction, the filters could eliminate one noise source, or the other, but not both.
General Observations:
- the Timewave and MFJ filters have a learning curve to figure out how to quickly and precisely null out noise. A couple of evenings of tinkering was required to figure out how to use the unit with different noise sense antennas and different types of noise.
- the Timewave and MFJ filters have a learning curve to figure out how to quickly and precisely null out noise. A couple of evenings of tinkering was required to figure out how to use the unit with different noise sense antennas and different types of noise.
- the noise sense antenna is critical and must pick up a strong noise signal for the units to work effectively. In most instances for local interference at VA7MM the noise sense antenna is near the ground and vertically polarized and the main antenna is high above the ground and horizontally polarized.
- both noise amplitude and phase need to be alternately adjusted to attain a good null on the units.
- using Spectran or SDR with the receiver on AM helps in adjusting the units.
Next Steps:
- discussions are on combining the noise canceller with a small vertical plane receive loop on 160 or 80m. The idea is that the combination of the two could enable noise in two directions to be nulled. The receive loop would be pre-amplified.
- having two noise cancellers in series was also discussed as a means of nulling noise from two directions. An issue with this approach is that more processing electronics are put ahead of the front end of the receiver and this introduces its own noise and may create intermodulation.
- having two noise cancellers in series was also discussed as a means of nulling noise from two directions. An issue with this approach is that more processing electronics are put ahead of the front end of the receiver and this introduces its own noise and may create intermodulation.
- I like that the MFJ unit has gain controls for both the noise antenna and the main antenna. Other differences include MFJ providing both relay and RF sense T/R switching whereas the Timewave only has RF sense capability. The noise antenna connector on the MFJ is an SO-239which I find more practical than the RCA phono socket on the Timewave. As far as mechanical construction is concerned, the Timewave is more robustly built.
We’re open to any questions on these findings.
We’re open to any questions on these findings.
73,
Mark Mattila, VA7MM
Guy Immega, VA7GI
MFJ / Timewave Noise Canceller Shootout
A previous blog described a series of tests that Mark, VA7MM, performed demonstrating the effectiveness of his newly acquired MFJ- 1026 Noise Canceller.
He, along with Guy, VA7GI, recently had the opportunity to compare the performance of the MFJ against Guy's Timewave ANC-4.
I'll let Mark describe the results:
I'll let Mark describe the results:
NoiseCancellerShootout 2017 Report:
Guy Immega, VA7GI, and Mark Mattila, VA7MM, undertook side by side comparative tests of Timewave ANC-4 and MFJ-1026 noise cancellation gear (photos attached) by listening to interference at VA7MM in the HF spectrum between 7 MHz and 14 MHz. The program Spectran was used with the receiver on AM to adjust each unit for best performance and observe the relative performance of each. A system of coaxial relays was used to switch instantaneously between the units (photos attached).
Findings:
For practical purposes Timewave’s ANC-4 and MFJ’s 1026 are equal performers for eliminating interference in the HF spectrum.
Our findings corroborate the earlier findings of VE7CA that are posted on his website.
Switching the units in and out of noise was previously assessed on 40m CW, broadcast and raw noise. Examples of these tests are in a previous blogspot.
Commentary:
- main antenna in the tests was a multiband dipole at 30m above the ground.
- noise sense antenna was a Cushcraft R7 vertical antenna located 20m away from the main antenna.
- receiver was an Icom IC-746Pro.
- main antenna in the tests was a multiband dipole at 30m above the ground.
- noise sense antenna was a Cushcraft R7 vertical antenna located 20m away from the main antenna.
- receiver was an Icom IC-746Pro.
- both units tested have the same nulling capability.
- the preamp on the MFJ was found to be useful in certain instances for boosting the noise signal.
- in one test instance the Timewave unit produced intermod with AM broadcast leaking into the receiver when the noise gain was set near maximum.
- in instances where noise was coming from more than one direction, the filters could eliminate one noise source, or the other, but not both.
General Observations:
- the Timewave and MFJ filters have a learning curve to figure out how to quickly and precisely null out noise. A couple of evenings of tinkering was required to figure out how to use the unit with different noise sense antennas and different types of noise.
- the Timewave and MFJ filters have a learning curve to figure out how to quickly and precisely null out noise. A couple of evenings of tinkering was required to figure out how to use the unit with different noise sense antennas and different types of noise.
- the noise sense antenna is critical and must pick up a strong noise signal for the units to work effectively. In most instances for local interference at VA7MM the noise sense antenna is near the ground and vertically polarized and the main antenna is high above the ground and horizontally polarized.
- both noise amplitude and phase need to be alternately adjusted to attain a good null on the units.
- using Spectran or SDR with the receiver on AM helps in adjusting the units.
Next Steps:
- discussions are on combining the noise canceller with a small vertical plane receive loop on 160 or 80m. The idea is that the combination of the two could enable noise in two directions to be nulled. The receive loop would be pre-amplified.
- having two noise cancellers in series was also discussed as a means of nulling noise from two directions. An issue with this approach is that more processing electronics are put ahead of the front end of the receiver and this introduces its own noise and may create intermodulation.
- having two noise cancellers in series was also discussed as a means of nulling noise from two directions. An issue with this approach is that more processing electronics are put ahead of the front end of the receiver and this introduces its own noise and may create intermodulation.
- I like that the MFJ unit has gain controls for both the noise antenna and the main antenna. Other differences include MFJ providing both relay and RF sense T/R switching whereas the Timewave only has RF sense capability. The noise antenna connector on the MFJ is an SO-239which I find more practical than the RCA phono socket on the Timewave. As far as mechanical construction is concerned, the Timewave is more robustly built.
We’re open to any questions on these findings.
We’re open to any questions on these findings.
73,
Mark Mattila, VA7MM
Guy Immega, VA7GI
CLE 220 Results
Last weekend's midday CLE seems to have drawn a lot of interest for a summer event.
Perhaps it was because listeners could participate without having to burn the midnight oil as is usually the case when listening 'live' and not recording with an SDR.
Listening time was restricted to between 1100 and 1500 hours local time, to see what could be heard via daytime groundwave.
In spite of having a low noise seaside listening location, I was surprised to only hear beacons in B.C. and Washington state, with not as much as a whisper from Oregon, Alberta, Idaho, Montana or lower Alaska. The furthest beacon I heard was ZZP-248 in the Queen Charlottes, at 486 miles. I would have wagered that most regions would see similar results, with groundwave distances being fairly constant throughout North America, but this was not the case.
Participants in the central states seemed to enjoy much greater groundwave coverage than here on the west coast. It seems that the rugged Coastal ranges and the Rockies do have a pronounced effect on daylight propagation when skywave is not involved. Beacon ERP cannot be ignored as well as location and ground system efficiency ... some definitely get out much better than others even though output powers may be the same.
Anthony Casorso, ADØVC, listening near Denver, Colorado with an Elad SDR and a 17' Low Noise Vertical (LNV), managed several +500 mile catches but all N-S or to the east.
Bill Riches, WA2DVU, in Cape May, NJ, found SJ-212 in Saint John, New Brunswick, 635 miles to the north with his Perseus and Wellbrook loop.
Dave Tomasko, K9QU, in Galena, Illinois, caught OKS-233 in Oshkosh, NE at 625 miles and FOR-236 in Forsyth, Montana, at a whopping 845 miles with his R-75 and Wellbrook ALA100 loop.
These were heard here at 11 a.m. local time using my Perseus SDR and inverted-L tuned to 300kHz:
24 18:00 200.0 YJ Victoria - Sidney Island, BC, CAN
24 18:00 203.0 YBL Campbell River, BC, CAN
24 18:00 214.0 LU 'Cultus' Abbotsford, BC, CAN
24 18:00 216.0 GRF GRAYE - Fort Lewis, WA, USA
24 18:00 223.0 YKA Kamloops, BC, CAN
24 18:00 227.0 CG Castlegar, BC, CAN
24 18:00 236.0 YZA Ashcroft, BC, CAN
24 18:00 240.0 BVS Skagit/Bay View - Burlington, WA, USA
24 18:00 242.0 ZT Port Hardy, BC, CAN
24 18:00 248.0 ZZP Dead Tree - Queen Charlotte Is, BC, CAN
24 18:00 251.0 YCD Nanaimo, BC, CAN
24 18:00 257.0 LW Kelowna - Wood Lake, BC, CAN
24 18:00 266.0 VR Vancouver - Lulu Island, BC, CAN
24 18:00 269.0 YK 'Brilliant' Castlegar, BC, CAN
24 18:00 272.0 XS Prince George, BC, CAN
24 18:00 284.0 FHR Friday Harbor Apt, WA, USA
24 18:00 290.0 YYF Penticton, BC, CAN
24 18:00 293.0 MB Mill Bay - Sidney, BC, CAN
24 18:00 312.0 UNT Naramata, BC, CAN
24 18:00 325.0 YJQ Bella Bella (Campbell Island), BC, CAN
24 18:00 326.0 DC Princeton Municipal Apt, BC, CAN
24 18:00 328.0 LAC 'Lacomas' Fort Lewis, WA, USA
24 18:00 332.0 WC White Rock (Abbotsford), BC, CAN
24 18:00 338.0 K Ediz Hook - Port Angeles, WA, USA
24 18:00 344.0 XX Abbotsford, BC, CAN
24 18:00 348.0 MNC 'Mason Co' Shelton, WA, USA
24 18:00 350.0 NY Enderby, BC, CAN
24 18:00 353.0 RNT Renton Municipal Apt, WA, USA
24 18:00 356.0 ON 'Okanagan' Penticton, BC, CAN
24 18:00 359.0 YQZ Quesnel, BC, CAN
24 18:00 359.0 YAZ Tofino - Vancouver Island, BC, CAN
24 18:00 362.0 BF 'Nolla' Seattle, WA, USA
24 18:00 368.0 ZP Sandspit - Moresby Island, BC, CAN
24 18:00 371.0 YK 'Donny' Yakima, WA, USA
24 18:00 374.0 EX Rutland (Kelowna), BC, CAN
24 18:00 378.0 AP Active Pass (Mayne Island), BC, CAN
24 18:00 382.0 YPW Powell River, BC, CAN
24 18:00 382.0 AW WATON - Marysville, WA, USA
24 18:00 385.0 WL Williams Lake, BC, CAN
24 18:00 389.0 YWB Kelowna, BC, CAN
24 18:00 400.0 QQ Comox, BC, CAN
24 18:00 408.0 MW PELLY - Moses Lake, WA, USA
24 18:00 414.0 YZK Harper Ranch, BC, CAN
24 18:00 515.0 CL ELWHA - Cresent Beach, WA, USA
CLE 220 Results
Last weekend's midday CLE seems to have drawn a lot of interest for a summer event.
Perhaps it was because listeners could participate without having to burn the midnight oil as is usually the case when listening 'live' and not recording with an SDR.
Listening time was restricted to between 1100 and 1500 hours local time, to see what could be heard via daytime groundwave.
In spite of having a low noise seaside listening location, I was surprised to only hear beacons in B.C. and Washington state, with not as much as a whisper from Oregon, Alberta, Idaho, Montana or lower Alaska. The furthest beacon I heard was ZZP-248 in the Queen Charlottes, at 486 miles. I would have wagered that most regions would see similar results, with groundwave distances being fairly constant throughout North America, but this was not the case.
Participants in the central states seemed to enjoy much greater groundwave coverage than here on the west coast. It seems that the rugged Coastal ranges and the Rockies do have a pronounced effect on daylight propagation when skywave is not involved. Beacon ERP cannot be ignored as well as location and ground system efficiency ... some definitely get out much better than others even though output powers may be the same.
Anthony Casorso, ADØVC, listening near Denver, Colorado with an Elad SDR and a 17' Low Noise Vertical (LNV), managed several +500 mile catches but all N-S or to the east.
Bill Riches, WA2DVU, in Cape May, NJ, found SJ-212 in Saint John, New Brunswick, 635 miles to the north with his Perseus and Wellbrook loop.
Dave Tomasko, K9QU, in Galena, Illinois, caught OKS-233 in Oshkosh, NE at 625 miles and FOR-236 in Forsyth, Montana, at a whopping 845 miles with his R-75 and Wellbrook ALA100 loop.
These were heard here at 11 a.m. local time using my Perseus SDR and inverted-L tuned to 300kHz:
24 18:00 200.0 YJ Victoria - Sidney Island, BC, CAN
24 18:00 203.0 YBL Campbell River, BC, CAN
24 18:00 214.0 LU 'Cultus' Abbotsford, BC, CAN
24 18:00 216.0 GRF GRAYE - Fort Lewis, WA, USA
24 18:00 223.0 YKA Kamloops, BC, CAN
24 18:00 227.0 CG Castlegar, BC, CAN
24 18:00 236.0 YZA Ashcroft, BC, CAN
24 18:00 240.0 BVS Skagit/Bay View - Burlington, WA, USA
24 18:00 242.0 ZT Port Hardy, BC, CAN
24 18:00 248.0 ZZP Dead Tree - Queen Charlotte Is, BC, CAN
24 18:00 251.0 YCD Nanaimo, BC, CAN
24 18:00 257.0 LW Kelowna - Wood Lake, BC, CAN
24 18:00 266.0 VR Vancouver - Lulu Island, BC, CAN
24 18:00 269.0 YK 'Brilliant' Castlegar, BC, CAN
24 18:00 272.0 XS Prince George, BC, CAN
24 18:00 284.0 FHR Friday Harbor Apt, WA, USA
24 18:00 290.0 YYF Penticton, BC, CAN
24 18:00 293.0 MB Mill Bay - Sidney, BC, CAN
24 18:00 312.0 UNT Naramata, BC, CAN
24 18:00 325.0 YJQ Bella Bella (Campbell Island), BC, CAN
24 18:00 326.0 DC Princeton Municipal Apt, BC, CAN
24 18:00 328.0 LAC 'Lacomas' Fort Lewis, WA, USA
24 18:00 332.0 WC White Rock (Abbotsford), BC, CAN
24 18:00 338.0 K Ediz Hook - Port Angeles, WA, USA
24 18:00 344.0 XX Abbotsford, BC, CAN
24 18:00 348.0 MNC 'Mason Co' Shelton, WA, USA
24 18:00 350.0 NY Enderby, BC, CAN
24 18:00 353.0 RNT Renton Municipal Apt, WA, USA
24 18:00 356.0 ON 'Okanagan' Penticton, BC, CAN
24 18:00 359.0 YQZ Quesnel, BC, CAN
24 18:00 359.0 YAZ Tofino - Vancouver Island, BC, CAN
24 18:00 362.0 BF 'Nolla' Seattle, WA, USA
24 18:00 368.0 ZP Sandspit - Moresby Island, BC, CAN
24 18:00 371.0 YK 'Donny' Yakima, WA, USA
24 18:00 374.0 EX Rutland (Kelowna), BC, CAN
24 18:00 378.0 AP Active Pass (Mayne Island), BC, CAN
24 18:00 382.0 YPW Powell River, BC, CAN
24 18:00 382.0 AW WATON - Marysville, WA, USA
24 18:00 385.0 WL Williams Lake, BC, CAN
24 18:00 389.0 YWB Kelowna, BC, CAN
24 18:00 400.0 QQ Comox, BC, CAN
24 18:00 408.0 MW PELLY - Moses Lake, WA, USA
24 18:00 414.0 YZK Harper Ranch, BC, CAN
24 18:00 515.0 CL ELWHA - Cresent Beach, WA, USA
Hunting For Daytime NDBs In CLE 220
 |
| AP-378 Mayne Island, BC |
It's hard to believe but this coming weekend will see another CLE challenge!
No need however, to stay up until the wee hours for this one, as CLE220 is a mid-day affair ... just log what you are able to hear during the day from your location. The entire band is fair-game as well, from 190 - 1740kHz.
Everyone is encouraged to send their logs (see below) so the RNA / REU NDB databases can be kept as up-to-date as possible.
I know that I won't have any trouble hearing AP-378 shown above since it's only about 3/4 mile from my antenna! I'm always curious just how far it can be heard during the day and would encourage listeners on the west coast to have a good listen for it and please let me know if you can hear it.
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 usually on one small slice of the NDB spectrum.
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. With your receiver in the CW mode, listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are tone-modulated with a 1020 Hz tone approximately.
For example, 'AA' near Fargo, ND, 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
SUMMER MIDDAY EVENT
How many normal NDBs can you log around midday?
In this event we can probably cheat the QRN and hardly hear any (but if
you do have a midday storm coming overhead, disconnect and switch off
immediately of course)
Listening around midday is a good way to check our listening stations and
to find out if changes really have made improvements in reception.
Or maybe you could try the CLE listening from a 'field' location instead of
(please, NOT as well as) from home?
Days: Fri. 23 June - Mon. 26 June
Times: Within 2 hours of ‘real’ Midday (see below)
QRG: 190 - 1740 kHz
NDBs Normal NDBs only, plus any UNIDs
(not DGPS, NAVTEX or Amateur)
### IMPORTANT ## If your house clocks have moved one hour
forward for 'summer time' (or 'daylight saving'), your listening
times each day will be BETWEEN 11 IN THE MORNING
and 3 IN THE AFTERNOON (15:00) on your LOCAL clocks.
If your clocks were NOT changed, maybe in Arizona (?), or
in the Southern Hemisphere where it is now mid-winter,
your times each day will be from 10 a.m. to 2 p.m. LOCAL.
(The above matches our agreed definition for daytime listening)
Of course, all our logs will show UTC times, as always.
Our usual simple log-making 'rules' apply:
Post your CLE log to the List in a plain text email if possible please,
with CLE220 at the start of its title, showing on each log line:
# The Day No.(e.g. ‘23’) or the full date (e.g. ‘2017-06-23’)
and UTC (the day changes at 00:00 UTC).
# kHz - the nominal published frequency, if known.
# The Call Ident.
Please show those main log items FIRST, with any other details such as
location and distance LATER in the same line.
Don't forget to give your own location and brief details of your equipment.
It also makes good reading if you add your thoughts on the CLE and any
amusing events that happened during it.
I will send the usual 'Any More Logs?' email at about 17:00 UTC on Tuesday
so you can check that your log has been found OK. Do make sure that your
log has arrived on the list by 08:00 UTC on Wednesday 28th June at the
very latest.
I’m so grateful to Joachim who will again be making the combined results for
us.
As usual, you can get further helpful information about this and past CLEs
via Alan's CLE Information Section, http://www.ndblist.info/cle.htm
CLE107 was our last CLE rather like this one - way back in July 2008!
Good listening
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA [email protected]
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
(Reminder: If you wish you can use a remote receiver for your loggings,
stating its location and owner - with their permission if required.
NB: THAT RECEIVER must be located within 2 hours of ‘real’ midday.
A remote listener may NOT also use another receiver, whether local or
remote, to obtain further loggings for the same CLE).
SUMMER MIDDAY EVENT
How many normal NDBs can you log around midday?
In this event we can probably cheat the QRN and hardly hear any (but if
you do have a midday storm coming overhead, disconnect and switch off
immediately of course)
Listening around midday is a good way to check our listening stations and
to find out if changes really have made improvements in reception.
Or maybe you could try the CLE listening from a 'field' location instead of
(please, NOT as well as) from home?
Days: Fri. 23 June - Mon. 26 June
Times: Within 2 hours of ‘real’ Midday (see below)
QRG: 190 - 1740 kHz
NDBs Normal NDBs only, plus any UNIDs
(not DGPS, NAVTEX or Amateur)
### IMPORTANT ## If your house clocks have moved one hour
forward for 'summer time' (or 'daylight saving'), your listening
times each day will be BETWEEN 11 IN THE MORNING
and 3 IN THE AFTERNOON (15:00) on your LOCAL clocks.
If your clocks were NOT changed, maybe in Arizona (?), or
in the Southern Hemisphere where it is now mid-winter,
your times each day will be from 10 a.m. to 2 p.m. LOCAL.
(The above matches our agreed definition for daytime listening)
Of course, all our logs will show UTC times, as always.
Our usual simple log-making 'rules' apply:
Post your CLE log to the List in a plain text email if possible please,
with CLE220 at the start of its title, showing on each log line:
# The Day No.(e.g. ‘23’) or the full date (e.g. ‘2017-06-23’)
and UTC (the day changes at 00:00 UTC).
# kHz - the nominal published frequency, if known.
# The Call Ident.
Please show those main log items FIRST, with any other details such as
location and distance LATER in the same line.
Don't forget to give your own location and brief details of your equipment.
It also makes good reading if you add your thoughts on the CLE and any
amusing events that happened during it.
I will send the usual 'Any More Logs?' email at about 17:00 UTC on Tuesday
so you can check that your log has been found OK. Do make sure that your
log has arrived on the list by 08:00 UTC on Wednesday 28th June at the
very latest.
I’m so grateful to Joachim who will again be making the combined results for
us.
As usual, you can get further helpful information about this and past CLEs
via Alan's CLE Information Section, http://www.ndblist.info/cle.htm
CLE107 was our last CLE rather like this one - way back in July 2008!
Good listening
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA [email protected]
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
(Reminder: If you wish you can use a remote receiver for your loggings,
stating its location and owner - with their permission if required.
NB: THAT RECEIVER must be located within 2 hours of ‘real’ midday.
A remote listener may NOT also use another receiver, whether local or
remote, to obtain further loggings for the same CLE).
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. It's also a good place to submit your CLE log! 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 Daytime NDBs In CLE 220
|
| AP-378 Mayne Island, BC |
It's hard to believe but this coming weekend will see another CLE challenge!
No need however, to stay up until the wee hours for this one, as CLE220 is a mid-day affair ... just log what you are able to hear during the day from your location. The entire band is fair-game as well, from 190 - 1740kHz.
Everyone is encouraged to send their logs (see below) so the RNA / REU NDB databases can be kept as up-to-date as possible.
I know that I won't have any trouble hearing AP-378 shown above since it's only about 3/4 mile from my antenna! I'm always curious just how far it can be heard during the day and would encourage listeners on the west coast to have a good listen for it and please let me know if you can hear it.
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 usually on one small slice of the NDB spectrum.
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. With your receiver in the CW mode, listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are tone-modulated with a 1020 Hz tone approximately.
For example, 'AA' near Fargo, ND, 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
SUMMER MIDDAY EVENT
How many normal NDBs can you log around midday?
In this event we can probably cheat the QRN and hardly hear any (but if
you do have a midday storm coming overhead, disconnect and switch off
immediately of course)
Listening around midday is a good way to check our listening stations and
to find out if changes really have made improvements in reception.
Or maybe you could try the CLE listening from a 'field' location instead of
(please, NOT as well as) from home?
Days: Fri. 23 June - Mon. 26 June
Times: Within 2 hours of ‘real’ Midday (see below)
QRG: 190 - 1740 kHz
NDBs Normal NDBs only, plus any UNIDs
(not DGPS, NAVTEX or Amateur)
### IMPORTANT ## If your house clocks have moved one hour
forward for 'summer time' (or 'daylight saving'), your listening
times each day will be BETWEEN 11 IN THE MORNING
and 3 IN THE AFTERNOON (15:00) on your LOCAL clocks.
If your clocks were NOT changed, maybe in Arizona (?), or
in the Southern Hemisphere where it is now mid-winter,
your times each day will be from 10 a.m. to 2 p.m. LOCAL.
(The above matches our agreed definition for daytime listening)
Of course, all our logs will show UTC times, as always.
Our usual simple log-making 'rules' apply:
Post your CLE log to the List in a plain text email if possible please,
with CLE220 at the start of its title, showing on each log line:
# The Day No.(e.g. ‘23’) or the full date (e.g. ‘2017-06-23’)
and UTC (the day changes at 00:00 UTC).
# kHz - the nominal published frequency, if known.
# The Call Ident.
Please show those main log items FIRST, with any other details such as
location and distance LATER in the same line.
Don't forget to give your own location and brief details of your equipment.
It also makes good reading if you add your thoughts on the CLE and any
amusing events that happened during it.
I will send the usual 'Any More Logs?' email at about 17:00 UTC on Tuesday
so you can check that your log has been found OK. Do make sure that your
log has arrived on the list by 08:00 UTC on Wednesday 28th June at the
very latest.
I’m so grateful to Joachim who will again be making the combined results for
us.
As usual, you can get further helpful information about this and past CLEs
via Alan's CLE Information Section, http://www.ndblist.info/cle.htm
CLE107 was our last CLE rather like this one - way back in July 2008!
Good listening
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA [email protected]
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
(Reminder: If you wish you can use a remote receiver for your loggings,
stating its location and owner - with their permission if required.
NB: THAT RECEIVER must be located within 2 hours of ‘real’ midday.
A remote listener may NOT also use another receiver, whether local or
remote, to obtain further loggings for the same CLE).
SUMMER MIDDAY EVENT
How many normal NDBs can you log around midday?
In this event we can probably cheat the QRN and hardly hear any (but if
you do have a midday storm coming overhead, disconnect and switch off
immediately of course)
Listening around midday is a good way to check our listening stations and
to find out if changes really have made improvements in reception.
Or maybe you could try the CLE listening from a 'field' location instead of
(please, NOT as well as) from home?
Days: Fri. 23 June - Mon. 26 June
Times: Within 2 hours of ‘real’ Midday (see below)
QRG: 190 - 1740 kHz
NDBs Normal NDBs only, plus any UNIDs
(not DGPS, NAVTEX or Amateur)
### IMPORTANT ## If your house clocks have moved one hour
forward for 'summer time' (or 'daylight saving'), your listening
times each day will be BETWEEN 11 IN THE MORNING
and 3 IN THE AFTERNOON (15:00) on your LOCAL clocks.
If your clocks were NOT changed, maybe in Arizona (?), or
in the Southern Hemisphere where it is now mid-winter,
your times each day will be from 10 a.m. to 2 p.m. LOCAL.
(The above matches our agreed definition for daytime listening)
Of course, all our logs will show UTC times, as always.
Our usual simple log-making 'rules' apply:
Post your CLE log to the List in a plain text email if possible please,
with CLE220 at the start of its title, showing on each log line:
# The Day No.(e.g. ‘23’) or the full date (e.g. ‘2017-06-23’)
and UTC (the day changes at 00:00 UTC).
# kHz - the nominal published frequency, if known.
# The Call Ident.
Please show those main log items FIRST, with any other details such as
location and distance LATER in the same line.
Don't forget to give your own location and brief details of your equipment.
It also makes good reading if you add your thoughts on the CLE and any
amusing events that happened during it.
I will send the usual 'Any More Logs?' email at about 17:00 UTC on Tuesday
so you can check that your log has been found OK. Do make sure that your
log has arrived on the list by 08:00 UTC on Wednesday 28th June at the
very latest.
I’m so grateful to Joachim who will again be making the combined results for
us.
As usual, you can get further helpful information about this and past CLEs
via Alan's CLE Information Section, http://www.ndblist.info/cle.htm
CLE107 was our last CLE rather like this one - way back in July 2008!
Good listening
Brian
----------------------------------------------------------
From: Brian Keyte G3SIA [email protected]
Location: Surrey, SE England (CLE coordinator)
----------------------------------------------------------
(Reminder: If you wish you can use a remote receiver for your loggings,
stating its location and owner - with their permission if required.
NB: THAT RECEIVER must be located within 2 hours of ‘real’ midday.
A remote listener may NOT also use another receiver, whether local or
remote, to obtain further loggings for the same CLE).
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. It's also a good place to submit your CLE log! 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!
RFI … Radio Spectrum’s Global Warming?
 |
| courtesy: http://www.arrl.org/utilities |
The FCC's recent publication of an Order and Consent Decree (DA-17-471) has me wondering if this action signals new interest in cracking-down on those who manufacture and distribute unapproved spectrum polluting noise-generating devices or is it just a once-in-awhile muscle flex with little change in overall policy ... hopefully it's the former!
Highlights of the agreed upon notice:
Section 302 of the Act authorizes the Commission to promulgate reasonable regulations to minimize harmful interference by equipment that emits radio frequency energy....Specifically....that “[n]o person shall manufacture, import, sell, offer for sale, or ship devices or home electronic equipment and systems, or use devices, which fail to comply with regulations....
.... the Commission establishes technical requirements for transmitters and other equipment to minimize their potential for causing interference to authorized radio services ... the Commission administers an equipment authorization program to ensure that equipment reaching the market in the
United States complies with the technical and administrative requirements set forth in the Commission’s rules. The equipment authorization program requires, among other things, that radio frequency devices must be tested for compliance with the applicable technical requirements in accordance with one of three authorization procedures—i.e., certification, Declaration of Conformity, or verification—prior to marketing.
... the Rules prohibits the marketing of radio frequency devices unless the device has first been properly authorized, identified, and labeled in accordance with the Rules ...
... a privately-held company that manufactures and distributes lighting fixtures that are used in residential and commercial properties ... under-cabinet LED light fixtures were reportedly causing interference to AM/FM radio transmissions.
During the course of the investigation, the evidence revealed that ... the LED light fixtures were not tested and authorized under the Commission’s equipment authorization rules prior to marketing.
... the Bureau’s Spectrum Enforcement Division issued a Letter of Inquiry (LOI) ... directing to submit a sworn written response to a series of questions relating to ... the marketing of its LED lighting fixtures in the United States.
... continued to market the light fixtures at issue for certain times during an approximately five-month period after receipt of the LOI.
Other highlights indicate that the company in question acknowledged their violation and agreed to appoint a Compliance Officer in charge of implementing new company protocols, including the retraining and education of employees dealing with compliance issues. As well, a $90,000 civil penalty was imposed on the company for the violation.
As a point of interest, I can't ever recall seeing similar notifications being released or reported here in Canada by our FCC equivalent, the ISEDC. Hopefully they also take similar actions, but if so, they don't seem to be reporting it ... perhaps I'm just not looking in the proper places.
As I've mentioned here previously, for too many radio amateurs, the growing noise floor throughout the radio spectrum has become a global threat for the healthy pursuit of our hobby. Even if we saw the immediate implementation of rigorous new tight standards, crackdowns and prosecutions of offenders, it may already be too late to reverse the damage we are now seeing ... in many respects, it's the 'global warming' of the RF spectrum and there may be no turning back without immediate action.
