Posts Tagged ‘Beacon Monitor’

Beacon failure once again alerted me to a change in the NCDXF/IARU International Beacon Project status page so that I can manually update the beacon status file for VOAProp. I think it is worth a comment on the fact that 7 out of the 18 beacons appear currently to be off the air. This is the most I can recall being off at the same time. Some have been off for months. If you rely on the beacons to see whether a band is open, you may think conditions are worse than they really are. I hope all the beacons are soon restored to full operation.

Death of 20m incorrectly reported

It’s a good job I looked at the beacon reports this morning or I wouldn’t have noticed that there were no reception reports for the 20m band. The problem was that I had visited 20m yesterday and put the K3 into data mode. An annoying feature of the K3 is that when you change bands it restores the mode you last used on that band. It does that even if the band change is being made under software control, even if the mode it is restoring is inappropriate for the frequency you are changing to under the band plan. This is totally bonkers logic because no computer program worth its salt should make assumptions about the state of the radio so when changing the frequency it should also set the mode. Unfortunately if it sets the mode too quickly, or before the frequency change is sent, the K3 “feature” overrides the mode set by the software. Consequently the option in Faros to “force CW mode” doesn’t work on the K3 and you are left in the mode you last used on that band.

Faros is not alone in experiencing this problem. Complaints have been frequent on the Elecraft reflector that when clicking on DX cluster spots in various programs the radio changes to the right frequency but is in the wrong mode. One of the reasons I wrote KComm specifically for the Elecraft radios was that I could make it work the way the radios work instead of being stuck with some generic logic. But there is nothing I can do about programs I didn’t write. I wish that more ham radio applications were open source so you could fix problems like this yourself instead of having to ask a developer to make the necessary changes (and very often getting nowhere.)

Beacon monitoring with Faros

Alex, G7KSE wrote recently about monitoring the International Beacon Project beacons on 20, 17, 15, 12 and 10 metres, which gave me the idea to try it again for myself. I did try the Faros beacon monitoring software by VE3NEA a few years ago but being a tightwad I never registered it so the trial came to an end after 30 days. I was also less than enthusiastic about leaving the computer and radio running every day 24/7. Work out the power consumption and it can add a significant amount to the quarterly bill which is unlikely to go unnoticed by the chancellor of the exchequer (the XYL.)

These days the computer is usually running from when I get up (or after breakfast) until when I go to bed in order to run my HF and VHF APRS gateways so it is no extra trouble to do some beacon monitoring as well. I don’t have a spare radio or antenna so I will have to use my main radio (my K3) and antenna for the beacon monitor. This means that if I want to go on the air the beacon monitoring will stop. Currently my enthusiasm for actually making contacts is at a very low ebb so this is not much of a problem. I shall still shut down at night and restart in the morning, at least during the winter months when there is no night time propagation on 20m and up. Apart from the pointless waste of joules, the loud click from the K3 each time Faros changes bands will be a disturbance as the shack is only just across the landing from our bedroom.

The antenna I am using is the short multiband 80plus2 dipole bent to fit into the roof space, with additional 10m and 6m elements. It works fine on 20, 15, 12 and 10m. On 17m I can get a good SWR with the aid of the K3’s built-in tuner (which is the source of the loud clicks) but performance is noticeably down on the magnetic loop. However, the magnetic loop is used by my K2 for the HF APRS gateway so it is not available.

VE3SUN has written a very good article explaining how to set up a system to display the beacon reception charts created by Faros on a web page. It looked easy so I went ahead and set up an IBP Beacon Reception page on G4ILO’s Shack. I found that the WinSCP software that VE3SUN recommends to automate the uploading of the reception charts to the website popped up annoying windows whenever it updates so I used SyncBack SE instead. Unlike WinSCP it isn’t free, but I had purchased a license a few years ago and the code still worked with the latest version.

I converted the JavaScript in VE3SUN’s example page to PHP. This means that I can test for the existence of the beacon monitor graphics and display a friendly message rather than have the browser display a “missing picture” graphic if the monitor has not been running and that day’s GIF image doesn’t exist.

I have added to the page a short list of currently active beacon monitors to make it easy to compare my reception reports with other people’s. It would be nice if, instead of each beacon monitor having his own results on his own web site, there was a central site that collated all the IBP reception reports and displayed them on a map, like WSPR does. Perhaps that would rejuvenate interest in the IBP which seems to have been overshadowed in recent years by WSPR and reverse beacons.

Subscribe FREE to's
Amateur Radio Newsletter

We never share your e-mail address.

Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!

  • Matt W1MST, Managing Editor

Sign up for our free
Amateur Radio Newsletter

Enter your e-mail address: