Author Archives: KD5HIY

2017 Field Day Results

2017 Field Day Results
Submitted via the Web on 7/8/17
QSO Summary
BandCWPwr(W)DigitalPwr(W)PhonePwr(W)
80m00002150
40m271500046150
20m61500040150
GOTA000045
Total33-0-92-
QSO MethodCWDigitalPhoneTotal
Total QSOs33092125
Total Points66 *092158
158 x 2316
Bonus Points:
DescriptionPointsMethod
100% Emergency Power300No Commercial Power Used
Media Publicity100Reported to Star Telegram
Social media100Facebook/Twitter
Public Location100Hurst Community Park
Public Information Table100
Natural power QSOs100Solar Power
Site Visit100Elected Official
Site Visit100Hurst FD Chief Palla
Youth participation20Jordan, KG5DLI
1 Youth operators0
1 Youth participants0
GOTA Bonus0Four Operators
Submitted via the Web50Web Submission
Safety officer100Greg, KA9SUU
Total Bonus Points1170
GOTA Bonus: No CoachQSOsPoints
Carrie, KD5YIZ40
EarnedBonusTotal
31611701486
* 2 x Muliplier Qualification

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.