Author Archives: W5HRC

440 Repeater Move and Echolink Changes

We recently wrapped up a project of moving our 440 repeater from one location to a new one, greatly expanding our UHF foot print. Initial testing to determine our new coverage area have been very promising.
Echolink has traditionally been connected to this machine, but with the move, we must reconfigure our connection, so EchoLink will be offline for a short time while we work through this, setting up a new RF node.
Our frequency did not change. You can still find the repeater on 442.850+110.9, and it is open for anyone to use. The HEB area is showing to be completely covered, but a bit more testing to locate any dead spots or problem areas still needs to be done.
We are thankful to the City of Hurst for allowing us to repurpose a former public service antenna and other repeater equipment to make this happen. We hope to hear you on the air.

2017 First Quarterly Newsletter

Our next issue of the Hurst Amateur Radio Club Newsletter is here. We have the President’s Musings – Reflecting back on 2016. RACES Today where we talk about SKYWARN, what it is and what it is for. Followed by Upcoming Events, Back to Basics, Stuff to Know and follow up by remembering our Silent Key’s.
We are looking forward to 2017
Read the newsletter here:
HARC Newsletter for 1Q17

440 Echolink Now Offline

There have been some issues regarding Echolink and the computer it was running on. I first noticed some problems with audio during our last Sunday 440 net (10/30/16), when people tried to check in over Echolink, and you could hear the carrier, but no audio.
After doing some testing on the future 2m Echolink project, I discovered that our 440 repeater was not passing audio from Echolink. I messed with the computer for nearly thirty minutes Thursday night, and had no success in getting the audio to properly play on the 440 machine. It turns out, that Microsoft changed the audio subsystem in Windows 10, and many people have been having issues with it and Echolink.
Why did we upgrade the computer. We didn’t do it willfully. It upgraded during the time when Microsoft was really pushing the 10 upgrade, and changed it at some point to basically do an auto-install. We came in one Saturday morning and discovered the computer had upgraded. The audio issue wasn’t discovered immediately though.
I say all of this in order so you now know the reason I made the decision to take Echolink offline until a fix or correction can be made. I promise to make this a priority and get this resolved as soon as I can. Echolink for the 2m repeater is being tested and I really really hope to have it online by Thanksgiving.
[UPDATE] The Echolink node is now back online and ready for use.