Tag Archives: WWVB

Amateur Radio, ARRL Ohio Section, Computing, Ohio Section Journal

Ohio Section Journal – The Technical Coordinator – September 2019 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…

Read the full edition at:

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

A ham in the section asked me about obtaining the latest Linux kernel. Not wanting to deal with problems found after the operating system install media was released, the latest stable kernel version available was what he wanted to be installed during setup.

Before I get started, if you are not familiar with Linux and have not read my April 2018 OSJ article, I encourage you to do so as some of the terminology defined will be used here.

There is not an easy answer to the question which version of the kernel is “stable.” The answer is: it depends. Depends on:

  • Definition of stable. There will always be bugs and constant fixes being released. Most IT personnel take ‘stable’ to mean: the least amount of issues after testing and polishing.
  • Linux distribution. How well does a kernel version work with the packages and drivers of a distribution. Availability of a new stable kernel depends on maintainers, developers, and the community’s time to update everything including programs, libraries, and drivers. Then test, document, ship, and address bug reports.

At kernel.org, there is a giant yellow button which indicates “latest stable kernel.” As of this writing, currently 5.3. Terminology on the Kernel Archives website for the different kernel types:

  • mainline = beta
  • stable = less issues
  • longterm = maintained and updated longer, typically for business production systems
  • linux-next = patches for the next version of mainline, stable, longterm

Logging into a handful of updated Linux devices I have around the house, their kernel versions:

  • Fedora 30: 5.2.14
  • AllStar Node (Debian 9): 4.9.0
  • Raspberry Pi – AllStar node (Arch): 4.14.97
  • Raspberry Pi – stock install (Raspbian Buster): 4.19.66
  • Wireless access point: 2.6.36

You’ll notice exactly zero are on 5.3. Even Fedora, which is considered a “bleeding-edge” Linux operating system will lag behind. Fedora is currently a single release behind the stable channel. Each distribution has their own definition of “stable” because it’s up to each distribution to maintain and update their releases.

A similar situation exists for software packages too. There will often be different versions of the same named package between different Linux distributions. Packages Managers almost always lag behind source code releases. For example, the Linux printing system software called CUPS for Common UNIX Printing System (cups.org), its latest is version 2.3.0. The latest in the Fedora 30 package manager is version 2.2.12. Therefore, 2.2.12 is the latest stable CUPS install for Fedora 30. Version 2.3.0 will be available when it is approved.

I have nearly 2000 packages installed on one of my systems! That seems like a lot but some are very small and Linux is very modular. Some are programs I installed like VLC or YouTube downloader. Others, I have no idea. Those are likely dependencies for other packages or programs pre-installed by the distribution. Anything beginning with “lib” is a shared common library. Packages prefixed with a program name are modules of that program: “cups” is the core printing system while “cups-filters” are the printer libraries for CUPS. Some are required system packages. “tzdata” is time zone data – so the system knows about different time zones, changes DST correctly, and processes leap-seconds. “Mint-themes” are themes for the Linux desktop GUI Cinnamon.

Linux diehards will “compile from source.” To get the absolute latest and greatest features and fixes, this practice involves downloading the plain-text source code and compiling it into machine executable code manually. It takes alot of trial-and-error to get a successful compile. Not only is the program source needed but the source code for any dependencies and libraries will also be required. Most will say this is to validate the code, add their own custom modules to the kernel, or do kernel development.

Could someone download and compile kernel 5.3 for Fedora, Ubuntu, Mint, or any other distribution? Absolutely. Fedora has a process documented to update the kernel manually. It’s 15 pages. Or you can run a single command. You choose. But you have to deal with any issues that arise from using a custom version of the kernel and doing so is unsupported by most distributions. I have no reason to be on a later kernel version before it is made generally available by the Fedora project.

Unless there are bandwidth concerns, there is little reason to worry about installing the latest version of the OS. The package manager will handle all updates to the kernel, operating system, and programs. Updates through the package manager have been approved for that version of the operating system by those who maintain those programs. It does not mean updates are 100% bug free. There is no need to install updates the minute they are available – even every-couple-weeks will be OK. We’ve all been trained like Pavlov’s dog to install updates the minute we see that pop-up. Thanks Windows. Cherry-picking is not a good idea either – unless you have a specific reason not to install an update, like an incompatible version of Java with another program.

How to install the latest Linux OS updates? I’m a command line guy because I was brought up on the DOS and Linux command lines. Recent Linux distributions have both a CLI (command line interface) and a GUI (graphical) package manager. Once the Live CD install is complete, reboot. When logged in, open a terminal window.

For Red Hat based systems (Fedora, CentOS), run:
sudo dnf -y update
Replace dnf with ‘yum’ on older installs.

For Debian based systems (Ubuntu, Mint, Raspbian, etc), there are two commands:
sudo apt -y update
sudo apt -y upgrade

The -y option means “assume yes” to any download questions or repository updates. GUI versions vary but usually involve refreshing the repository data and selecting all updates. These should always be run after a fresh install. When complete, reboot the machine. I run these update commands about once a week, maybe more if I’m waiting for an update or fix. These can be run at any time after installation as well.

On the topic of operating systems, the much beloved Microsoft operating system Windows 7 will no longer be supported after January 14, 2020. Windows 7 reaching end-of-life means there will be no further security updates – in theory. Even after Windows XP reached EOL, Microsoft went back and patched some “really bad” vulnerabilities in all operating systems, including XP. I can’t say the January 14th date will be extended or moved beyond that date nor can I say how long Windows 7 will remain a safe operating system to use. For the first time ever at the beginning of this year, the number of Windows 10 users just passed the number of Windows 7 users. That means about half of Windows users are still running version 7. There was talk of hackers stockpiling Windows XP exploits that would be released the minute Microsoft stopped updating XP, bringing the world to its knees. That was more hype by the media than reality. Chrome and Firefox browsers continued to support XP until a time came when they decided it was more work than it was worth.

A conversation I had recently, this person was of the mind that Windows 7 is going to stop working all together after January. Not true. It will still work as normal after January 14. You may see nag screens saying Win7 is no longer supported encouraging update to Windows 10. This is not a requirement to continue using your computer because Windows 7 will continue to run fine, you know, until the machine dies. There will be problems installing 7 on certain newer hardware because Microsoft thinks regression testing and customizations for Windows 7 security on modern hardware will introduce more problems. This time may, however, be the last chance you can upgrade to Windows 10 for free, for the life of the computer. If you qualify and have the latest Windows 7 updates installed, you will receive a pop-up from Windows saying ‘Microsoft recommends upgrading to Windows 10.’ This is a similar promotion to the one I talked about in April 2016.

In general, users have grown numb to the constant updating and bloatware of Windows 10. Believe it or not, Microsoft solved all the real problems with Windows 10. It’s called Microsoft Windows 10 LTSC (Long-Term Servicing Channel). It’s fantastic. It doesn’t force you into feature updates, doesn’t have the Windows Store crap, Cortana junk, or Customer Experience tracking. Feature updates can be delayed 18-24 months instead of having to be applied every 6 months. Not to mention Microsoft has frequently pulled back feature updates nearly as soon as they are released due to lack of adequate testing. The gotchya is you need access to a costly MSDN subscription. This version is out there if you look for it. Microsoft heavily criticizes the use of LTSC saying ‘users want feature updates.’ No, they don’t, that’s why users are seeking out a usable version of your crappie ‘modern’ operating system.

Time Code Generator for WWVB (wwv100.com)

The oldest continuously operating radio station in the world deserves a grand celebration. The Northern Colorado Amateur Radio Club (NCARC) will operate a special event amateur radio station with the call sign WW0WWV, on the WWV property starting September 28 and going 24-hours a day through October 2. For information on the Special Event Station visit: wwv100.com. In addition, HamSCI and the Case Amateur Radio Club of Case Western Reserve University (W8EDU) will sponsor a “Festival of Frequency Measurement” on WWV’s centennial. They are hoping to measure 5 MHz propagation over a given day and compare measurement techniques. HamSCI’s first attempt at measurements occurred during the total solar eclipse in 2017.

Jim – W8ERW, Technical Specialist for the Ohio Section, gave an informative presentation at the Wood County Amateur Radio Club in August about ARDEN MESH networking. He talked about generations of devices used for MESH networking, including the infamous Linksys blue-box, and brought many pieces of his own equipment for demonstration. Seneca county is getting involved and finding plenty of uses for MESH. If you would like a presentation for your club about MESH, get in touch with Jim.

Thanks for reading and 73… de Jeff – K8JTK

Amateur Radio, ARRL Ohio Section, Ohio Section Journal

Ohio Section Journal – The Technical Coordinator – February 2019 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…

Read the full edition at:

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

A couple months ago, I received a question regarding digital mode transmissions. This ham was using Fldigi and wondered about “strange” transmissions at the start of a BPSK-63 transmission. BPSK-31 looked OK.

Strange tones (circled in orange) on the Fldigi waterfall

These tones are known as RSID, Reed Solomon IDentifier, designed by Patrick Lindecker, F6CTE. RSID tones are codes used to automatically identify digital signals and often precede a digital transmission. These are a burst of tones lasting 1.4 seconds with a bandwidth of 172 Hz. They are robust being decoded down to -16 dB, which is better than most digital modes. According to the W1HKJ documentation for Fldigi, programs that support RSID are:

  • PocketDigi, Vojtech, OK1IAK
  • FDMDV, Cesco, HB9TLK
  • DM780, Simon, HB9DRV – part of Ham Radio Deluxe
  • fldigi, Dave, W1HKJ
  • Multipsk, Patrick, F6CTE

The documentation link has a table of all RSID codes. Not all variations of baud, tones, and bandwidth are assigned a code because RSID is limited to a total of 272 unique codes. The programs listed support RSID, not necessarily all modes assigned an RSID code. Typically, that means the program will not react to codes for which it does not support.

RX RSID enabled

To detect RSID alongside the desired operating mode, digital programs will run a separate detector listening for these tones while the main detector focuses on decoding the selected mode. To receive RSID tones in Fldigi, the option on the main screen in the upper-right “RxID” needs to be green (enabled).

RSID announcement

The default behavior of Fldigi, I think, is a little weird. When an RSID is received, an announcement will be displayed in the receive pane (tan box). The blue clickable text takes you back to the previous frequency at the time the RSID was received. It does not move you to the frequency of the received RSID. An example, RSID was received at 1300 Hz on the waterfall. The cursor is currently on 1500. The clickable link in the receive pane will return the cursor back to 1500. Fldigi will search for RSID in the vicinity of the cursor (about +/- 200 Hz), not across the entire waterfall.

Useful configuration options are available in the Configure menu -> Other -> IDs. The “Searches passband” option will listen across the entire waterfall. “Notify only” will display a popup box when an RSID is received. You’ll have the option to click “go to” that frequency.

TX RSID enabled

Consequently, on the transmit side, “TxID” needs to be enabled for Fldigi to transmit RSID tones. Fldigi offers an option other programs don’t, transmit RSID at the end of the transmission. I don’t see much use for this as your signal is gone but someone might want to be ready for the next station in the exchange or break-in.

Why wouldn’t a station see RSID tones for a (B)PSK-31 signal? Two reasons: PSK-31 is a common mode that most hams, who have operated digital on the air for any period of time, would encounter. No need to keep identifying commonly used digital signals. According to Fldigi, CW, RTTY, and BPSK-31 are the only supported ones that fall into this category. The second reason is bandwidth. Transmitting an RSID of 172 Hz will clobber more than a couple nearby PSK-31 transmissions.

Transmission mode list

On the same configuration page, click “Transmission modes.” This list indicates which modes have RSID enabled. Clearing the checkbox will not transmit RSID for that mode. For example, operating a lot of BPSK-63 and the RSID annoys you, but not for MT63-2000, uncheck BPSK-63 in the list.

Transmitting RSID helps ensure receiving stations are tuned and decoded for modes like MFSK. Modes like JT65 have RSID tones but they’re not used during normal operation and could throw off the timing of the exchange. JT65 is also operates in designated windows of the digital sub-bands. It’s probably meant more for identifying EME transmissions using JT65.

RSID notification

The ‘strange’ transmissions are not strange at all but rather letting others know which modes are being operated.

WWV update

There was a lot of FUD (that’s fear, uncertainty, and doubt) around the future of WWV back in September of last year. You can check my article in the September edition of the OSJ or on my website. While not yet signed, the fiscal year budget for 2019 does include funding all WWV stations. As it turns out, this year is the 100th year of operation. A member of the Northern Colorado Amateur Radio Club has met with NIST management and is planning a special event station between September 28 – October 2. I’ll be anticipating that event and hope to work WWV.

Thanks for reading and 73… de Jeff – K8JTK

Amateur Radio, ARRL Ohio Section, Ohio Section Journal

Ohio Section Journal – The Technical Coordinator – September 2018 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…

Read the full edition at: http://arrl-ohio.org/news/2018/OSJ-Sep-18.pdf

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

Most hams and shortwave listeners know what the letters WWV mean. They are the call letters for the station that broadcasts the time, all the time. If you’ve never listened because you don’t have an HF radio or shortwave receiver, WWV is a shortwave radio station near Fort Collins, Colorado run by the U.S. National Institute of Standards and

WWV transmitter building (nist.gov)

Technology (NIST). WWV is the oldest continuously-operating radio station in the United States. It transmits time signals and bulletins in voice and digital formats on 2.5, 5, 10, 15, and 20 MHz AM 24/7/365.

The time and transmitted frequency of WWV is controlled by atomic clocks which are the most accurate standards due to the use of atoms as a time keeping element. Not only is the time broadcast by WWV the most accurate but the frequency of the transmitters is also the most accurate. WWVH is the Hawaiian sister station to WWV. WWVB is co-located with WWV but broadcasts a constant time code for radio-controlled clocks on 60 kHz. This is the frequency clocks that automatically set themselves listen to. Both WWV and WWVH announce Universal Coordinated Time (UTC) each minute and broadcast other recorded announcements including GPS health reports, oceanic weather warnings, and solar activity bulletins.

Cesium atomic clocks (nist.gov)

Whether you use these stations to calibrate equipment and instrumentation, calibrate ham radio digital software and hardware (Slow Scan TV or Fldigi), listen to bulletins, or use it as a beacon to check propagation, all of that is likely to end. NIST has proposed shutting down, by way of defunding, the WWV stations in their 2019 budget proposal. This means the 2011 NIST estimation of 50 million radio-controlled clocks and wristwatches equipped to receive WWVB will become obsolete. Not to mention it is an instrumental part in the telecommunications field and in scientific research. At first, WWVB was not listed in initial stories which made sense. Continuing to operate it would not obsolete radio-controlled clocks. But it too started to appear in later news stores.

In the ARRL report, the reason given for defunding these broadcast stations would be to “consolidate and focus” on other programs due to reductions in NIST funding. Taking the WWV stations off the air would save $6.3 million. The NIST FY (fiscal year) 2019 budget request for efforts related to Fundamental Measurement, Quantum Science and Measurement Dissemination is $127 million, which, the agency said, is a net decrease of $49 million from FY 2018. The administration’s overall NIST budget request is more than $629 million.

While I was distraught as I think most hams were, it gets more ridiculous when I started to break this down. Most people don’t understand huge numbers like millions, billions, and trillions of dollars because we’ll never see those numbers in our lifetimes and they’re just unrealistic. Let’s convert these figures into numbers most of us do understand. For comparison, I’m adding the published 2017 U.S. federal budget numbers: actual total revenue was $3.316 trillion and actual expenditures were $3.982 trillion. Breakdown is as follows:

15 Mhz WWV transmitter (nist.gov)
  • 2017 U.S. budget total revenue: $3,316,000
  • 2017 U.S. budget total expenditures: $3,982,000
  • NIST 2019 proposed budget: greater than $629
  • NIST 2019 proposed fundamental measurement budget: $127, which was reduced by $49
  • Shutting down the WWV stations saves: $6.30

A whopping $6.30! $6.3 million is almost 1% of the total proposed 2019 NIST budget or 0.00016% (rounded) of 2017 total expenditures. Yeah, it’s a HUGE burden!

I got pretty upset and there was noted concern over the shutdown proposal, especially amongst hams as would be expected since we utilize the service probably more than others. I figured everyone wouldn’t want their wall clocks to stop setting the time automatically. However, reality set in as the petition started at whitehouse.gov didn’t gain much traction. As of this writing, with less than 3 days before it closed, it gained a little less than 19% of the needed signatures for the White House to respond. Note: OSJ publication date will be after the petition closes.

What happens next? I haven’t heard if the dial-in phone numbers for WWV will be shut down or remain accessible: (303) 499-7111 for WWV (Colorado), and (808) 335-4363 for WWVH (Hawaii). Phone systems are converting to data services (VoIP) and there will be slight delays due to network switching, latency, and loss. If the phone numbers remain available, it will be better than nothing.

Canada has a similar time standard called CHU on 3.330 MHz & 14.670 MHz at 3 kW and 7.850 MHz at 10 kW. The 3 MHz station was strong into NE Ohio on one Thursday night as I’m writing this article. I’m also making the big assumption CHU will remain on the air. CHU broadcasts are AM with the lower side-band suppressed. Unfortunately, Canada doesn’t have the equivalent of WWVB and they relied on the U.S. for their radio-controlled clocks. Go U.S.! In other parts of the world, radio-controlled clocks rely on MSF in England and JJY in Japan.

Radio-controlled clocks will switch to some sort of other technology, likely GPS, listen for a cellular signal, or piggyback on WiFi. Radio-controlled clocks I’ve used set themselves in the middle of the night at about 3AM. Figuring most electronic noise emitting devices (like computers) would be off and longwave reception is better at night. GPS will reduce clock setup by one step. You won’t have to tell the clock in which time zone it is located. Ooohhh, yeah – that was so much work! I’m skeptical about using GPS. Any time I bring my car GPS into the house, it “lost satellite reception.” Being internal to a steel building (like an office), I do not see how this works at all without bringing the clock to the window to resync. More skepticism comes in the form of a question: what happens when the U.S. developed GPS system is unavailable? It could be unavailable because of solar flares, software bug, or an act of a nation-state. If you haven’t seen Dr. Tamitha Skov – WX6SWW’s solar reports, GPS is significantly affected by solar flares just like our HF bands, but in different ways. There are commercially available car navigation devices and smartphones that are capable of receiving both U.S. GPS and Russian GLONASS. Consider other parts of the world are developing their own global navigation systems and not relying on one single system, Europe: Galileo & China: BDS.

Computers and other Internet connected devices are not affected by the WWV shutdown. They utilize the Network Time Protocol (NTP) from publicly available time servers for syncing time.

I hope the best for WWV, WWVH, and WWVB. Maybe a private entity will buy out and continue to operate the stations. Nothing is looking too good without outrage from the public or more support than the few that signed the online petition. I’m getting tired of forced obsolescence.

Thanks for reading and 73… de Jeff – K8JTK