Tag Archives: APRS

Ohio Section Journal – The Technical Coordinator – January 2023 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 Tom – WB8LCD 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 Tom 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 Ohio 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 click the Login button.
  • Login
  • When logged in successfully, it will say “Hello <Name>” in place of the Login button where <Name> is your name.  Click your Name.  This will take you to the “My Account” page.
  • On the left hand side, under the “Communication” heading (second from the bottom), click Opt In/Out
  • To the right of the “Opt In/Out” heading, click Edit
  • Check the box next to “Division and Section News.”  If it is already checked, you are already receiving the Ohio Section Journal.
  • Click Save
  • There should now be a green check mark next to “Division and Section News.”  You’re all set!

Now without further ado…


Read the full edition at:

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

Hey gang,

I’ve traveled for work to our other facilities and taken advantage of training related travel. We were thinking I would have more travel opportunities. However, due to business need, sequestered to our homes for 2 years, and the freaking economy – it hasn’t happened. I had the opportunity to attend a work conference earlier this month and it gave me ideas to promote ham radio.

Work conferences are an opportunity to attend sessions and talks to gain skills, education, knowledge, keep current with industry trends, and network with others. If you’ve been to forums at Dayton, work conferences are 2/3/4 days of forums focused on an industry or segment. These could be: sales, information technology, manufacturing, human resources, C-Suite topics, project management, or general trends – like how work-from-home has changed and challenged work in the last 3 years. Similar to indoor vendors at Dayton, companies will sponsor booths with giveaways, swag, and maybe an opportunity to find a new job.

A number of co-workers and myself attended a conference called CodeMash in Sandusky at the Kalahari Resort (near Cedar Point if you’ve never been). This year was CodeMash 10000 (binary for 16). It was my first time at this conference. The conference is developer (programmer) focused but had tracks for information security, data, and career development. There were fun things to do including board games, laser tag, a maker space, evening events including casino night, and access to the resort’s indoor waterpark. The full conference runs four days in two halves. The first two days are called the “Pre-Compiler” consisting of two four-hour sessions per day. These are deep dive table-top exercises, discussions, and hands-on labs. Second two days are more byte-sized (see what I did there?) one-hour talks.

For work-related conferences, travel and accommodations are often paid for by the employer because these are training and educational sessions related to employment, job description, or a particular project. The employer hopes attendees return with new ideas and out-of-the-box thinking.

Depending on conference, cost can be way above beyond one’s means to attend on their own. CodeMash tries to be reasonable allowing individuals to attend at their own expense, if desired. A full 4-day ticket is between $800-$1,100 and the 2-day between $400-$550. Booking rooms through the conference at Kalahari offers discounted rates over normal nightly rates, though attendees can opt to stay at near-by hotels to be more economical. Kids have their own events called KidzMash, free with a registered adult.

Presenters for this conference are chosen by submitting abstracts to the CodeMash committee. If chosen, presenters get a free ticket to the conference as compensation for presenting. Sponsored sessions are hosted by companies sponsoring the event – these are listed as such and were on the last day. Presenters can plug their business and/or employer as their company is likely covering remaining costs. At least one presenter said they were there on their own dime as their employer “didn’t see the benefit” – and yet their lab session was standing room only.

Intro to Docker session. I’m way in the back row on the right. Twitter: @OtherDevOpsGene

I figured I wouldn’t have much time to play radio as the schedule was pretty grueling with breakfast at 7 am and sessions wrapped up around 5 pm each day – not including evening activities. In the past, I’ll bring at least one radio, a mobile radio if I’m driving and know I’ll
have extra time. Though I was driving and staying at the resort for this conference, I brought an HT, hotspot, and a couple RTL-SDR dongles because I like monitoring the Ohio MARCS-IP public service system. I was not expecting to have ham radio interaction during the conference.

First day of the conference at breakfast, this guy sits down at my table. It looks like he’s got a Yaesu Fusion radio with a whip antenna. I asked him “ham radio?” He says “yep, you?” “Oh yeah.” Talked with Dan – AD8FY about ham activities and his experiences as a pilot. He informed me there was an unofficial UHF simplex frequency and there would be a number of hams at the conference. This did surprise me as I wasn’t expecting it but again, first time. Feeling pretty good about the conference and some connection to ham radio.

During one of the Pre-Complier sessions, learned there was a Slack instance for the conference. Slack is an instant messaging platform available on just about every device. Slack started out as a professional communications platform (like Microsoft Teams or Google Chat) but became accepted as a community platform for things such as this conference. In addition to messaging, Slack can do VoIP calls, video calls, file sharing, and text messaging in channels (like a conference room) or to individual users. A feature I like is persistent messaging allowing people to see prior messages after joining. For example, I joined the Slack instance on the second day of the conference but I was able to see messages from the previous day. This is different from other chat services which only show messages sent after one has joined the channel.

Guy – KE8VIY SDR live demo, receiving ADS-B broadcasts

CodeMash’s Slack had many different channels: events taking place during the conference, discussions around hotel reservations, and water park. Announcements – changes, cancellations, updates, and general information. General discussions. Major cities had channels for attendees from those areas to network, such as #cleveland. Pre-Complier portion of the conference had a channel for presenters to post their slide-decks and labs. Slides channel for presenters from the second-half of the conference. Hobby channels included beer, wine, music jam sessions, and ham radio. Oh, really?

KE8VIY asked to have a #ham-radio Slack channel. Ten people conversed about radio and when they were monitoring the simplex frequency. Call signs seen: WX8TOM, WX8NRD, KD8NCF, KE8VIY, and myself. I found out later KD8NCF gave a presentation at the conference on Real-Time Web Applications.

Thursday afternoon, while heading to an afternoon one-hour session, saw this guy (that’s his name too) outside one of the conference rooms pointing an antenna around. Figured he was doing Wi-Fi hunting or something. He too had a HT with him. This was Guy – KE8VIY. He was preparing for his presentation later that afternoon using software-defined radio to decode ADS-B (aircraft broadcasts). Though he was unsure there would be any aircraft to track as all flights were grounded earlier due to a possible cyber-attack.

I told him I would be attending his presentation. Knowing a ham was doing this session helped swing my decision in his favor because there was another equally interesting session on another hobby of mine, homelabbing. That decision paid off because not only was Guy’s presentation excellent, it got the wheels turning on more ways to promote ham radio. “Tracking Aircraft with Redis & Software-Defined Radio” (GitHub repo) was the presentation.

I’ve never used Redis. Reading up on it, the technology works mostly in-memory as a structured data store, often as a caching service (session, page, message queue) or key-value database. According to Wikipedia, Twitter uses Redis and Redis is offered by the big-name cloud providers AWS, Azure, and Alibaba.

Guy’s slides were professionally done and visually appealing. Coupled with the slides, his personality, humor, and live demos, (if I didn’t know anything about it) he made ham radio seem fun and interesting. He stated he is a new ham and excited about what he’s been able to do processing radio signals. The audience was highly engaged asking questions and feedback was positive from hams that saw the presentation.

Most maybe thinking: you don’t need a license to receive ADS-B, how is this related to ham radio? That’s the tie-in. He worked in history of digital signals, formats, and all the things rooted in ham radio: Morse Code, RTTY, and APRS. Then demonstrated how he used a modern technology platform and a radio to capture and process digital signals, all at a developer conference. Well done!

There are a lot of slides in his deck. Due to the one-hour time limit, the first 30 slides and some diagrams were covered. He utilized Dump1090 for turning signals into raw data. Then used Redis (also his employer) to process, store, and make data available to consumers.

These things fit my thinking of how ham radio should be promoted. Promoting to kids is admirable and exposing them to activities early in life is a great way to maybe hook them later in life. Credit to my parents because ham radio was one of those activities and it happened to stick. Though, I seem to be the exception rather than the norm. There are other things my parents had me join in school that didn’t stick and I really don’t miss those activities. A way kids get their license is part of a school program or curriculum. How many carry on and renew their license after 10 years is up? Retention needs work. Chances are better if family members are active and involved.

Guy – KE8VIY SDR live demo, ADS-B broadcasts shown on a map

I have been a huge fan of initiatives by the ARRL and clubs to use Makerspaces as a way to breathe new life into the hobby. Makers are like-minded people whom like to learn, create, and invent as does the experimentation side of ham radio.

Gainfully employed individuals would be my next target audience – you know, if I were on a committee. Somewhere in the neighborhood of 25-45-year-olds – those looking to keep themselves busy – whether they’re single, don’t yet have a family, or had their kids graduate college. These individuals have disposable income for equipment and time that can be devoted to learning and operating.

A conference like CodeMash is a near perfect match for promoting ham radio to technically minded individuals, including kids. Not having any statistical data, I would say the median age was probably mid-30’s, early 40’s. Obviously, there were younger and older individuals. With few exceptions from my interactions, participants were gainfully employed as their companies were picking up the tab for them to attend the conference. There were an estimated 1,400 attendees at this year’s conference. (attendance was still down from previous years, close to half). That’s 1,400 technical people, a great audience to promote ham radio.

Does a conference you attend offer a communications platform like Slack? Ask for a ham radio group to be created. Post a simplex frequency for general chit-chat. Maybe organize a meetup during meal time or after events that day to network with other hams. Maybe non-licensed people will drop into the channel or drop in at the meetup. Maybe they’ll get bit by the bug and be looking for an Elmer.

Think about current job responsibilities, technologies or services your company provides. Guy, in the spirit of ham radio, took an existing technology, re-purposed it to receive signals and turn the data into events, maps, and an API (application programming interface, used for integrating with other applications) from aircraft broadcasts.

How can a technology you’re created, are familiar with, maintain, or work with become an interesting presentation that ties in ham radio? Figure that out and maybe you’ll get a free ticket to a conference with the employer picking up the tab for travel expenses!

I brainstormed examples using technologies seen at the conference to do radio related things:

  • Real-time data processors like Kafka for mapping propagation
  • Networking skills and technology to improve resiliency and security of mesh networks
  • Table-top-exercise to recover from a disaster. Assume all existing connection and authentication methods are non-existent.
  • Receive signal data from a distributed radio network
  • APIs to administer digital systems with many connections
  • Automate test-cases and frequent software updates with GitHub pipelines
  • Incident response to handle compromises of repositories or stolen credentials
  • Docker & Kubernettes to build simple, easily deployable applications
  • Can the “cloud” fit the general directive of not relying on other technology? How to handle and recover from outages?
  • Designing web apps to replace multi-platform applications
  • Write the next white-paper
  • Create technical documentation standards

Development work isn’t part of my daily responsibilities since I changed jobs a number of years ago. Initially wasn’t too sure about the conference. In reality, I learned a lot about technologies I hadn’t yet explored on my own. Ham radio connections made it a much better experience and hope to attend next year. Let me know if you’ve done something to promote ham radio in a similar conference-type setting to like-minded (non-ham) individuals or used modern technology platforms to improve and better ham radio.

Thanks for reading and 73… de Jeff – K8JTK

NOTE: an article written by Bob – K8MD on a portable operation during a work trip was included in the printed edition. That is available by the full edition links at the top of this post.

Ohio Section Journal – The Technical Coordinator – February 2022 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 Tom – WB8LCD 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 Tom 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:

NOTE: it was pointed out after publication, I was spelling “Vara” incorrectly as “Vera” in this article.

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

Hey gang,

Ever heard of Winlink Wednesday? Many who operate digital or operate during emergencies are familiar with Winlink because it has proven to be useful and effective. Winlink is a radio messaging system that uses amateur-band radio frequencies. Features include E-mail messages, attachments, position reporting, weather bulletins, emergency relief communications, message relay, and form submission. This system is popular when the Internet is not available. Winlink was first used recreationally by mariners, RV campers, and missionaries.

That’s the Winlink part, what does Wednesday have to do with all this? Greg Butler – KW6GB, who I met at the Vienna Wireless Society’s Winterfest just outside of Washington, D.C., coined the term. It was an honor to meet with him because his video, an introduction to Winlink, is an excellent tutorial. Winlink Wednesday is a net. It then turned into a popular day to hold many Winlink nets. After talking with Greg, he invited me to participate in their net. Greg has since retired as Net Control Station and David – KN4LQN has taken over net responsibilities.

Most of us know that a “net” is an on-the-air gathering of hams which convene on a regular schedule, specific frequency, and organized for a particular purpose. Such as relaying messages, discussing a common topic of interest, severe weather, emergencies, or simply as a regular gathering of friends for conversation. It’s also an excellent time to test radios, antennas, and equipment. Most of us have participated in a voice net on a local repeater or even on the HF bands. “Digital nets” exist to practice these same concepts except using digital communication.

Winlink nets serve the same purposes as other nets: encourage participation, encourage regular use of the Winlink system, expand operators’ skills, of course test our equipment and the RF gateway network.

I’ve participated in a few digital communication practice sessions as part of a drill. Last time most users dusted off their digital equipment was during the previous drill. When it came time to setting up, using, and operating their equipment, it was an epic failure. Practicing is essential anytime, not just for digital operations.

Greg – KW6GB (left) demonstrating Winlink
at the Vienna Wireless Society’s Winterfest

Winlink is a store-and-forward E-mail system. Conducting nets on this system must utilize a methodology that works with the technology. Everyone sending check-in E-mails during a small window of time is not realistic. Most Winlink nets provide a weekly announcement or reminder to the previous week’s check-in list. Announcements are typically sent out a few days before the net begins accepting check-ins. Announcements will lay out check-in procedures, Winlink modes, and times during which messages will be accepted. Nets may require a simple one-line of text, others a Winlink form. Some have a discussion question for comment, others have a training exercise. A list of check-ins is often returned to the group a day or so after the net concludes. Some utilize other technologies like maps to show locations of net participants.

To check-in, after opening Winlink Express, compose a new message. Do not reply to the original message. There is no need to waste bandwidth having the net announcement text as part of the check-in message. In some cases, the station receiving check-ins is not the station that sent the announcement. Recipient’s or NCS’ call goes into the TO field. It’s not necessary to include the “@winlink.org” part of the address just as it’s not required if the sender and receiver are using the same E-mail provider or domain. Subject is usually the name of the net. Many ask for a single-line check-in consisting of a combination of callsign, first name, city, county, state, and mode/band used to check-in. For example, this is my standard one-line check-in:

K8JTK, Jeff, Westlake, Cuyahoga, OH (HF Vera)

I have found steps in weekly announcements to be straightforward. Some users complain about instructions that are reused where a screenshot does not match the form. It’s often the case a form is updated but an older screenshot was used or instructions have changed slightly after screenshots were taken. Some nets get 400 to 700 check-ins per week. If a check-in requires the NCS to do additional work because the operator didn’t follow correct procedure, they’re more likely to ignore, delete, and move on. Other examples: NCS requested a single-line with comma-separated

Check-in to the Ohio Winlink Net

values and you provided a
different value
each
on separate
lines,
provided a form when one wasn’t requested, or the wrong form was used – are all reasons a check-in may not be counted. There are, of course, system issues and unexpected results. One net found sending an APRS location beacon message over Winlink resulted in the Carbon Copy addresses being ignored. It’s a learning process for all.

Winlink has may operating modes and bands: APRS, ARDOP, AREDN, PACTOR, peer-to-peer, Packet, VERA HF, VERA FM, Telnet (that should cover most of them), or some combination. Nets accept check-ins using any method that works for the operator. A few will not accept Telnet as it’s not typically used over-the-air in the ham bands. Others will not accept peer-to-peer (P2P).

P2P allows one Winlink operator to send a message directly to another station over RF without the use of Winlink infrastructure. Originating station composes the message as a “Peer-to-Peer Message” then selects the appropriate P2P operating mode to match the receiving station. Receiving stations have to let others know frequency and times when they will be available for receiving messages. An NCS may use their station or designated assistants to receive P2P messages.

I haven’t used other Winlink clients such as PAT. It seems PAT does not have the forms one would expect to find in the Winlink Express client. That makes it difficult to operate alternative Winlink clients on devices that are more compact and portable such as a Linux device or Raspberry Pi. A way to get around this, have someone using Winlink Express send an example form to a station using the PAT client. The PAT station uses text editors to modify the fields by hand and return the form. Not as elegant as the interface using the browser.

I currently participate in six Winlink nets. There are probably some DX nets out there I’m unaware. Just like any open net, you do not have to be in the designated area to check-in or participate. I check into the North Texas and West Virginia Winlink nets among others. The West Virginia net receives more out-of-state check-ins than in-state. We even have Winlink nets right here in Ohio and in the Great Lakes region.

Included below is each net’s routine information from their weekly announcement. For more details, contact the NCS station or check their website/groups.io if available. To join any or all of these nets, simply check in!

To use KF5VO’s signing from the Winlink Wednesday NTX net, Happy Winlinking!

Ohio Winlink Net

From: K8EAF
Subject: OH Winlink Net Reminder

Hello Winlink Users,

This is a reminder of the OH Winlink Wednesday Net for *date*.

Just a one line with callsign, first name, city, county, state and via what mode/band (VHF, UHF, HF, SHF, TELNET, APRS, ARDEN, ARDOP, VARA, VARA FM). I'll log you in with any means of communication. Or just send a Homing Message Pigeon!

Enter my callsign in the "To" field (K8EAF). Subject field "OH Winlink Net Check-in". In the body field enter callsign, first name, city, county, state and via what mode/band. See example in my signature line below.

This is a good time to test drive the Winlink forms. Many operators like to use the Winlink Check-In form located in the General Forms tab.

All check-ins will be acknowledged, and a complete roster will be sent later in the week.

"Prior Planning Prevents Poor Performance!"

K8EAF, Ed, Cincinnati, Hamilton, OH (VHF)

Great Lakes Area Winlink Net

From: KB8RCR
Subject: Invitation to join the Great Lakes Area Winlink Net

Greetings!

I am the founder and net manager for the Great Lakes Area Winlink Net which was formed in March of 2021.

The premise of the net is to learn and be much more comfortable with Winlink and it's operation as in public service communications as well as emergency service communications can utilize Winlink. Another big part of the net is to learn a wide variety of the forms in the forms library. It is not important how you check in, but that you do check in. By that I mean, whether you get in via Telnet, or from some form of RF connection, your check in is still important to the net. The participation In using the forms are voluntary, but encouraged. If you cannot try the forms, just send a plain text message with the check in information requested below in this message.

The net meets each Wednesday and your check in will be accepted with late Tuesday night and the absolute cutoff is noon on Thursday (Eastern Time Zone) as that gives you plenty of time to check into the net.

The check in process can be a simple plain text check in, or placed in a form somewhere. Use this format for a proper check in:

CALLSIGN, FIRST NAME, CITY, COUNTY, STATE/PROVINCE, COUNTRY.

My checkin for example, would look like this: KB8RCR, RYAN, REMUS, MECOSTA, MI, USA

In the TO: section send your message to KB8RCR

In the Subject: line please put something like GLAWN Checkin (date of checkin)

A good tip for all of these Winlink nets is to use some type of word processing program or text file and just copy/paste your information. This is what I do at least.

Thanks for taking the time to read this, and to consider checking into the Great Lakes Area Winlink Net. I strongly encourage you to keep participating in your existing Winlink nets, and to consider checking in to the GLAWN  net too.

Respectfully Sent,
Ryan Lughermo, KB8RCR
Great Lakes Area Winlink Net Founder/Manager

Winlink Wednesday (Virginia)

From: KN4LQN
Subject: Winlink Wednesday Reminder (#xxx)

*** Winlink Wednesday (Episode #xxx) ***
** PRIMARY NCS - KN4LQN **

(This reminder is also on the web at https://winlinkwednesday.net/reminder.html)

Standard check-ins this week (no weather snapshots or attachments of any type, please).

WHO: All amateur radio operators
WHAT: Winlink Wednesday
WHEN: Wednesday, *date*, 0000-2359 EST (UTC: 0500 Wed - 0459 Thu)
HOW: This net will accept check-ins via Winlink only. Send a check-in via any RMS during the timeframe above, or participate in one or both of the P2P sessions below.

Please do not use a "Telnet Winlink" connection (which defeats the purpose of Winlink). The goal is to have the message leave your station via RF.

Please remember to use the correct format (check-in message on a SINGLE LINE) for check-in, as shown below, over an RF connection.

To: KN4LQN (or alternate NCS, as appropriate)
Subject: Winlink Wednesday Check-In
Message body: call sign, first name, city or town, county, state (HF or VHF, etc.)

See example in my signature line, below.

PEER-TO-PEER SESSIONS:
Morning session: 0730-0930 EST, (UTC: 1230 - 1430), ARDOP P2P, several frequencies (see chart below).
   Net Control Stations - Morning P2P Session Only
      Please check in through ONLY ONE of these stations:
   Status         Station   Dial Freq     Operator          Location
   Primary        KN4LQN    3582 kHz      David Elkins      Chesterfield County
   Alternate      KE4KEW    3565 kHz      Martin Krupinsky  Augusta County
   Alternate      KM4DC     3593 kHz      Don McCubbin      Fairfax County
      Messages sent to Alternate NCS must be addressed to the receiving station.

Evening session: 1900-2130 EST (UTC: 0000 Thu - 0230 Thu), VARA P2P, 3582 kHz (dial).
   Net Control Station - Evening P2P Session
   Status         Station   Dial Freq     Operator          Location
   Primary        KN4LQN    3582 kHz      David Elkins      Chesterfield County
      No Alternate Net Control Stations.

Watch Facebook for details when active.

On Thursday, all check-ins will be acknowledged, and a net report and complete roster will be published to the Web.

73,
KN4LQN, David, Chesterfield, VA (VHF)

Website: https://winlinkwednesday.net/

Weather snapshots are requested on the first Wednesday of the month (no attachments of any type). Standard check-ins are always welcome.

observation time, weather conditions, temperature <<<— WEATHER ON SECOND LINE of message body. A recent example of my check-in with weather snapshot:

K8JTK, Jeff, Westlake, Cuyahoga, OH (HF Vera)
0015L, overcast, winds S@15mph, 45dF

Third Wednesday of each month, an ICS-213 form can be submitted in place of the normal one-line check-in. Instructions are provided for trouble-free submission of the ICS-213 form.

Winlink Wednesday participants

Winlink Wednesday NTX (North Texas)

From: KF5VO
Subject: Winlink Wednesday NTX Reminder

It's that time once again for Winlink Wednesday!

*Discussion question of the week*


Other instructions:

Use the Winlink Check In template when checking in. As a reminder, to use the template, when the New Message screen is opened, click on the menu items Select Template --> Standard Templates --> GENERAL Forms --> Winlink Check In.txt.

Make sure in the Send To box to put my call sign, KF5VO.

In the location box, put the name of your city/town, and which gateway you're connecting through (if known).

IF YOU ARE USING SOMETHING OTHER THAN WINLINK EXPRESS TO CHECK IN:
If you are not using the forms, then whatever you type into the body of the message will be considered the "Comment" field on the form.


Happy Winlinking!


Please visit the Winlink Wednesday NTX web site for more info on how to check in to the net:
https://bit.ly/2TfJNJE

If you haven't already, please join our mailing list on Groups.IO https://groups.io/g/WinlinkWednesdayNTX

John indicated he likes to have stations use gateway nodes instead of peer-to-peer. That way a node administrator can be made aware of and resolve issues. It would be bad to find out a node was not operational for a local emergency. In the past, he has helped identify TNC issues and problems resulting from Microsoft’s Patch Tuesday and Windows Updates released the day before!

West Virginia Winlink Net (Thursdays)

From: WV8MT
Subject: WV Winlink Net Reminder

Calling All Radio Amateurs!
Calling All Radio Amateurs!

I will hold the * net number * installment of the West Virginia Winlink Net this Thursday, * date * from 00:00 to 23:59. I will take check ins all day at your convenience. Please make sure your check in follows the following format in the message body:

WV8MT, MIKE, SUGAR GROVE, PENDLETON, WV (VHF, HF, or P2P)

VARA P2P SESSION!
The VARA P2P Session will take place from 6pm and 9pm Thursday. This week we will be on 3530.5 (Center) 3529.0 (Dial) again.

Please feel free to share this announcement with your fellow Hams. If you have an email list, or a club social media page, or however you connect to your fellow Hams, share this information with them.

WV8MT NCS, MIKE, SUGAR GROVE, PENDLETON, WV

EmComm Training (Thursdays)

For a 300/400 level class in Winlink, this is your net. This group was previously named ARC-EmComm-Training. Every week is a new exercise with different instructions. Exercises range from sending APRS IS position beacons to completing Hospital Bed forms to sending E-mail folder summaries. Detailed instructions are provided each week to complete the exercise, sometimes with an accompanying video. Check the groups.io link below for the next exercise and participate to learn more than you’ve ever wanted to know about using Winlink.

Since each week is different, a common message isn’t possible. They do use “tactical clearing houses” based on FEMA region. Ohio is in FEMA region 5 so the clearing house E-mail address is ETO-05 which stands for “EmCom Training Organization,” region 5. The first is always is the letter “O” and the second is a zero “0”. More information is available on their site for clearing houses outside Ohio.

Section Managers, including our own WB8LCD, were the subject of the February 17th ETO training event. The exercise involved completing and sending your Section Manager a form providing the requested information.

Groups.io: https://emcomm-training.groups.io/g/main
Website: https://www.emcomm-training.org/

Bob Bruninga, WB4APR, became a silent key on Monday, February 7, 2022. Though I never interacted with Bob, I have used technology he developed. He was a pioneer in the development of Automatic Packet Reporting System, otherwise known as APRS. Technology he developed brought many hams into the hobby using packet radio for real time position, telemetry tracking, and reporting. He started his ham radio journey in 1963 with Novice call WN4APR. According to Amateur Radio Newsline, Bob was a US Navy veteran and a senior research engineer at the US Naval Academy’s small satellite lab in Annapolis, Maryland. He has probably contributed to many more advances than just ham radio, in ways we may never, ever, know.

A correction to my article last month: I incorrectly stated the 3.45 GHz band spectrum auction amount. It should have been $22.5 billion, not trillion.

Thanks for reading and 73… de Jeff – K8JTK

Ohio Section Journal – The Technical Coordinator – April 2020 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,

Stay at home: day 42. Continuing to work from home. Haven’t seen co-workers or friends in a month and a half. Regular lunch outings and after work happenings have long since terminated. Virtual meetings and conferences have replaced in person interaction. Participation in Ham Radio activities is on the rise! Nets are seeing higher check-in counts than they’ve ever seen. The curve is rising for digital modes and logged contacts.

Are we all having fun yet during Corona Fest 2020?

As people are forced to work from home due to closures, companies are utilizing videoconferencing services to keep in touch with employees and teams. These are now methods for coordinating efforts and relaying the latest to employees about the status of their company. A videoconferencing solution was likely available for employees to interact with remote team members or vendors world-wide. Now, those services are utilized all-day, every day. My company decided to begin the transition from WebEx to Microsoft Teams for meetings. I liked WebEx and it generally worked. MS Teams, well it’s part of Office 365 and that’s probably down again. Corona Fest is forcing usage of these collaboration solutions, not only companies but social organizations that previously met in person. These include popular names like Skype, Google Hangouts, and Zoom.

Those who value open sourced solutions should use Jitsi or Jitsi Meet to hold meetings. The service is completely free and open-source where anyone can look at the source code of the project. The difference between Jitsi and Jitsi Meet: Jitsi is a roll-your-own solution meaning you can download server packages or code and deploy an instance however you want. Jitsi Meet Online is an extremely easy-to-use alternative solution for holding meetings – with no installation required.

Settings up a meeting is easy as visiting the Jitsi Meet Online link, create a name for the meeting, click Go, set a meeting password, then send out the meeting URL or phone numbers to participants. A meeting can be created in a matter of seconds! Yes, POTS phone service is available as part of the meeting for free. Note, plain old telephone service audio options will not be encrypted due to the nature of the technology. There is nothing to download for desktop PCs with a web browser and most smart devices. Smart phone apps are available for iOS and Android including the F-Droid store. Functionally, Jitsi Meet offers the same features as the others: video, audio, chat, and shared desktop.

If I had to pick one thing that I don’t like about Jitsi it is the use of WebRTC. Web Real-Time Communication is also a free and open-source project that provides web browsers and mobile applications with real-time communication (RTC). WebRTC is included in all modern browsers and enabled by default in most. This technology allows audio and video communication to happen without the need

Jitsi Meet options menu

to install additional plugins or apps. Makes it very easy. There are a couple problems with WebRTC in highly privacy focused implementations. One problem is the communication is direct, peer-to-peer. This makes it possible for a skilled individual to learn real Internet Protocol (IP) addresses even while the other is utilizing a VPN. Use of a VPN can allow a user to appear as though their traffic is coming from a different IP and aids in masking actual location. Corporations use VPNs to establish secure communications from their network to their endpoint devices over networks with unknown integrity. Another problem is that end-to-end encryption is not possible with WebRTC. Jitsi addresses this issue in their security document. End-to-end encryption (also abbreviated “E2EE”) is a method where only the communicating users can read messages exchanged, preventing eavesdroppers anywhere along the communication path.

I wish people used better tools such as Jitsi. That’s why there’s choice. I would use this for any meetings I hosted. It seems like a really good open-source alternative to the other solutions.

Zoom became very popular very quickly, almost overnight. It was even recommended right here in last month’s OSJ. Attacks and threats emerge as a result of that popularity and pose risks for users and clubs who are using these services to host meetings. Cyber criminals are crafting email messages to steal logon credentials and packaging malware to look like a Zoom meeting installer.

For most of us, club meetings are not doing anything that’s overly sensitive with Zoom. Some organizations (companies, agencies) banned the use of Zoom citing flaws in the encryption implementation making it easy to exploit and three Chinese companies develop the applications. These should be taken into consideration but there has been no evidence of influence resulting from these issues. Zoom should be commended, though, due to their responsiveness in correcting vulnerabilities and privacy issues that have been discovered in recent weeks.

Free for accounts, everything is managed by the Zoom cloud, including encryption keys. Data is encrypted between the clients and Zoom servers. However, audio is not encrypted if a paid account is using the POTS phone line options.

Shortly after its popularity exploded, so did the number of unwanted participants in meetings leading to the term “Zoombombing.” Having someone crash a meeting is obnoxious and an unwanted disruption. Examples of this have made the rounds where Zoom sessions were hijacked by individuals saying or showing things that are lewd, obscene, racist, or antisemitic in nature where everyone in the session can see or hear. Students themselves conspired to have pranksters harass teachers in their online classes. Others utilized ‘Wardialing’ tools to discover unsecured Zoom sessions. Wardialing is an early hacking term where every number in an area code was dialed to find computers, bulletin board systems, servers, and fax machines. The resulting list would be used to guess login credentials and gain unauthorized access to those systems. One person I know had her yoga session crashed by an individual cursing and displaying symbols associated with the National Socialist German Workers’ Party. I have not heard about any disruption to ham radio club meetings.

There are steps the organizer can take or have someone else follow the directions in the Zoom support articles to prevent these issues. Not all of these configuration recommendations are needed for every meeting, follow ones applicable to that meeting. For example, you may not want to lock a club meeting from participants but instead use a waiting room approach.

Latest version: ensure participants are using the most recent client version. In April alone, there have been three updates to the Windows client.

Meeting password: posting a meeting link to social media will draw attention. Send the event password to known users through a direct message or other means where your participants are known.

Waiting room: virtual staging area for guests and participants until you’re ready for them to join.

Zoom War Dialer (krebsonsecurity.com)

Manage participants: remove any participants that should not be in the meeting and set who can share their screen.

Disable video, file transfer, annotations, and private chat: cut down on distractions, unsolicited content, or messages as needed.

Accidental removal of a participant: a booted user cannot rejoin a session using the same email address unless a few settings are changed.

Put participants on hold during breaks: attendees audio and video can be disabled during lunch, bio breaks, or private moments.

Video recordings: exercise discretion when recording content and know where that content is stored. Paid customers have the option to record a meeting to the cloud.

Following these tips can lead to a successful, uninterrupted meeting.

I saw a posting by the developer of the MMDVM software, Jonathan – G4KLX. Digital hotspot and repeater owners should follow these guidelines.

This message contains important information that I want disseminated far and wide please.

I have been approached by the people who run aprs.fi and REF001/REF030 (not the same people) about problems being caused by hotspots. This is down to usage and I hope that people will act on this information:

1. APRS, it is important that when configuring your hotspot, that you ensure that the suffix used for accessing aprs.fi is unique. For example if you use more than one hotspot, then ensure that for every mode and for every hotspot, the aprs.fi access callsign is unique. This is usually done by specifying a unique suffix to the callsign used by the hotspot. If more than one hotspot attempts to access aprs.fi with the same callsign+suffix combination, the first one is thrown off, and the new one connects. In the meantime the original one tries to connect and throw the new one off. This can happen multiple times per second, and is causing problems for them. Please, please, please, look at your configurations and if you have a duplicate, change one of them.

2. REF001/REF030, apparently the network load on these D-Star reflectors is now very high due to the number of hotspots connecting and staying connected. Could you please consider changing your gateway configuration so that you disconnect after a certain period of inactivity (this means local RF activity) so that they aren't overloaded. I know we like to listen out for activity, but we must also realise that D-Star popular reflectors const money to run, and that includes network and processor usage. A quick look at their dashboards will reveal the problem, they're huge.

Jonathan G4KLX

Set unique SSIDs for APRS on different modes and on different hotspots. Finding where APRS information originates isn’t always easy with hotspots. The OpenSPOT 1 has a location information box in settings but it is not transmitted directly by that device, rather Brandmeister pushes that information to the APRS network. Disabling APRS data on the Pi-STAR requires editing the config files and setting priority messages in Brandmeister. The priority message solution should work for OpenSPOT devices too.

ZUMSpot on Raspberry Pi Zero compared to a quarter

Unlink from reflectors, talkgroups, and systems when you’re not using them, especially ones with large numbers of connected users. Users are apparently leaving their devices connected to popular reflectors ting up bandwidth and resources unnecessarily.

To put this into perspective, when I looked at REF001 there were 850 remote/hotspot users connected, about the same on REF030. A mere 12 had transmitted since they were connected. A 5 second transmission is about 9KB worth of Internet traffic. Multiply that by 850 connected devices, that’s 7.6MB of traffic in 5 seconds to connected hotspots, many of which are not being used. That’s an estimated 80 gigabytes or so for an hour-long net. There are ping/heartbeat packets to all connected devices even when the reflector does not have an active radio transmission taking place.

Please check your hotspot APRS configurations and disconnect when not in use.

K8JTK Hub Interlink System

Anyone wanting a place to meet-up for checking on friends and fellow hams or looking for something to do can use a system I’ve been working on the last few months. Currently, it offers 6 full-time ham radio VoIP modes interlinked for interoperability. Ways to access the system:

  • EchoLink: K8JTK-R 233196
  • AllStar Link: 50394
  • Hamshack Hotline: 94026
  • DMR: Brandmeister TG 31983
  • D-STAR: DCS/XLX983 A
  • YSF: K8JTK Hub 17374

Since I’m working from home, I’ve linked up my Wires-X room: K8JTK-ROOM 40680

More information or updates on the system: http://www.k8jtk.org/ham-radio/k8jtk-hub-digital-voip-mutimode-interlink-system/

Thanks for reading and 73… de Jeff – K8JTK

Ohio Section Journal – The Technical Coordinator – August 2016 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://n8sy2.blogspot.com/2016/08/august-edition-of-ohio-section-journal.html

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

DSCF5081 K8JTKHey Gang,

As I’m beginning this month’s article some nasty storms just ripped through Cleveland on the 11th. There were branches, trees, wires, power lines down, and road closures on the west side due to those hazards, including my QTH of Westlake. Luckily I’ve heard of no injuries. If you’re not part of the NWS Skywarn program, please consider joining as a spotter. Skywarn is a volunteer program that helps the local National Weather Service office know what’s happening on the ground and assists in warning people about dangerous weather conditions. Training typically happens in the early spring for spotters. Check with your local club or Skywarn organization.

The Republican Nation Convention went off without major incident in Cleveland. I was working from home and had the scanner on most of that week. Three major trunked radio systems were utilized: MARCS, the new MARCS-IP (Multi-Agency Radio Communications System), and GCRCN (Greater Cleveland Radio Communications Network). If you didn’t set a wildcard or use UniTrunker to watch those systems, you probably missed a lot of the event communications. There were about 12 primary talk groups on GCRCN where most of the action took place. These were previously unidentified so they were not in any lists or databases that use Radio Reference. A wildcard stops on any talk group whereas programming specific talk groups into the scanner will only stop on transmissions for those talk groups. The “old” MARCS system was shut down immediately following the convention as it was kept online largely for backup. It has been replaced by the MARCS-IP system.

This month we learned the sad news of Hara Arena’s closing. No more Hamvention at Hara Arena after 52 years. The Dayton Amateur Radio Association put into action their contingency plans. It was announced that Hamvention will still be in the Dayton area. The new location is The Greene County Fair and Expo Center located in Xenia, Ohio. Michael Kalter and Ron Cramer talked about the new location on Ham Nation for about 30 minutes in episode 259. Couple of links worth visiting:

-Why we are saddened by the loss of the Hara Arena: http://ad8bc.com/bc/?p=601
-Hamvention Announces Venue for 2017: http://hamvention.org/hamvention-announces-venue-for-2017/
-Ham Nation episode 259: https://twit.tv/shows/ham-nation/episodes/259, or YouTube link: https://www.youtube.com/watch?v=g_OaKmllEDY

One of our Technical Specialists, David KD8TWG, has been involved with setting up a DMR repeater in Cleveland. The frequency is 442.0875 (+5 MHz standard offset) using Color Code 1. The repeater is connected to the K4USD cBridge (http://www.k4usd.org/). On that website is a listing of the “standard DMR Logo configuration” for repeaters connected to the bridge. Right now, your code plug should follow the layout listed on the site. A cBridge is a feature that allows interconnecting of repeaters over the Internet and a Color Code is equivalent to a PL tone or DCS on analog repeaters.

When I picked up my DMR radio at Dayton, I found a code plug that had repeaters in Dayton and Columbus for the drive home. It was a nice opportunity to quickly get on the air with DMR but I kept threating myself to write my own. With the installation of the repeater in Cleveland, I took the opportunity to do just that. What is a “code plug?” Some history I found online notes the origins came from wire plugs, later jumpers, which were plugged into the radio to enable certain options or features. Since everything is now processor based, the term continues to stick with the radio world and is a fancy word for ‘radio configuration.’ It contains transmit/receive frequencies, tone selections, timeout values, IDs, configuration settings, etc. I used the one I found in Dayton as a reference. Tytera MD-380 There is also a sample one on K4USD’s site for my radio. I compared the two and designed mine the way I thought worked best. Just because someone designed a code plug one way doesn’t mean you can’t modify or do it differently. It’s analogous to one ham’s memory channels are not the same as another. In the end, it took about 3 hours to make mine! Keep in mind that was a lot of learning and comparing, in addition I programmed all 65 possible talk groups so I don’t have to add them in later. From discussions on the air indications are it took others a few hours as well. But my code plug works! I couldn’t be happier. Well OK I could, apparently I’m just far enough away that my 5 watts doesn’t quite make the trip. I took the radio to work and tested it from there.

I am writing an introductory series for the Wood County Amateur Radio Club on getting started in digital modes. The first few articles were for those who have never worked digital and want to upgrade their station. Remaining articles will focus on a specific mode. I’ve completed 3 so far (starting in February): an introduction, station setup, and working JT65/9. Published versions can be found at the club’s website WSJT-X Conversation in the CQ Chatter newsletter: http://wcarc.bgsu.edu/. As I point out in the second article, Technician class licensees can still participate. All of these sound card digital modes can be operated over FM simplex or even a net on a repeater using an HT! There are clear downsides like not being able to transmit as far as an HF station and occupying the full 10 to 15 kHz FM, even though the bandwidth of the audio generated by the computer is less. Yes, this defeats the purpose of narrow bandwidth modes. Someone wanting to learn and experiment with these modes may get bitten by the bug and lead to a license upgrade. That’s how I did it. I plan to write an article every 2-3 months.

My dad and I had the opportunity to join the Toledo Mobile Radio Association (TMRA) on August 10. They had Chris Wilson N0CSW, National Sales Manager for Yaesu talk about their System Fusion. Chris did make it clear that the company was paying for travel so there would be some ‘sales pitches.’ The presentation was short but the program ended up being driven by the audience with a lengthy question and answer session. Some things I learned: the DR-2X Yaesu DR-2Xrepeater announced at Dayton is not going to be a replacement for the DR-1X, though they may have improved on some shortcomings. The 2X is more of a full featured repeater. It will have the ability to operate dual receive and dual transmit (but not at the same time) creating two repeaters from one unit. They are including voice messaging (like club meeting announcements). Mailboxes were users can record messages for others. This reminds me of the mailboxes repeaters used to have when autopatches were more prevalent. The 2X can monitor a separate control channel for commands. This repeater will not support WiresX but will have “MSRL” (Multi-Site Repeater Linking) via an add-on Ethernet port. Their linking technology will allow the repeater to be linked over any IP based network, including mesh. This brought to mind an interesting use-case where multiple low profile/portable repeaters could be linked at sites with mesh such as air ports, hospitals, and Red Cross shelters. This would create a linked repeater system where not as many users would have to setup cross-banding or run to the other end of a hospital to reach a radio. In contrast, something similar can be done using the AllStar Linking system. At the meeting there was alot of: “I would like this feature/I don’t like this feature in the radio,” “we’re having this problem setting up the repeater to do X” kind of Q&A. My take away from that, their plan is to add features to radios by firmware update and not always release new radios.

In addition to all the work David KD8TWG has been doing to get DMR up and running in Cleveland, he’s been helping repair and upgrade analog repeaters, and setting up APRS IGates around town. He will be giving a presentation on APRS at the Lake Erie Amateur Radio Association’s club meeting on August 30th. Dinner starts at 6:30pm with the meeting at 7:30, don’t need to have dinner to attend the presentation. Haven’t seen an official announcement on location yet but it’s expected to be at the Play Arcade in Mayfield Hts (5900 Mayfield Rd, Mayfield Heights, OH). Check the LEARA website for updates and for dinner reservations: http://www.leara.org/.

Raspberry Pi 3I will be giving my introductory Raspberry Pi presentation at the Cuyahoga Amateur Radio Society meeting, September 13 at 7:30pm. It will be updated as there is new hardware and innovations available. Their meeting location is the Busch Funeral Home, 7501 Ridge Rd, Parma, Ohio. More: http://www.2cars.org/.

Thanks for reading and 73… de Jeff – K8JTK

APRS RX IGate with RTL-SDR and Raspberry Pi

For sometime I wanted to experiment with an APRS IGate. Coverage was spotty at best in my area. There is an IGate in my city but it doesn’t receive so well. Recently there have been more IGates blanketing the area.

APRS stands for Automatic Packet Reporting System and has been developed since the late 1980s by Bob Bruninga – WB4APR. It’s a digital communication mode amateur radio operators use to primarily broadcast location information, though this wasn’t the intended use. It handles text messages, alerts, announcements, bulletins, and information of interest like weather station reports. APRS operates typically on a single frequency.  A system of relay stations and digipeaters repeat messages over a wide area. APRS Internet System (APRS-IS) are Internet connected receivers (IGates).

Any ham can add an icon or information to the APRS map.  The information is available on the Internet or to users on the local RF network.  Data is automatically tracked over time. APRS is frequently used to track mobile stations in a public service event or volunteers in a search and rescue event to visualize locations and track progress.

This project will utilize the Raspberry Pi and RTL-SDR dongle. The Raspberry Pi is a credit-card sized micro-computer intended for teaching computer science to students but became popular with the makers. RTL-SDR dongles are DVB-T (European standard) TV tuner dongles. It was found the signal data could be accessed directly which allowed them to be converted into wide band software defined radio receivers. The Pi costs about $35 and RTL-SDR about $20.

Since the RTL-SDR dongles are meant to receive high power wide bandwidth TV signals, they are not as as sensitive or frequency stable as a ham radio or scanner. Receiver performance will be a little less than an equivalent radio performing the same task but depends on the usual variables: amount of APRS activity, antenna height, antenna gain, propagation, etc, etc. With my antenna about 15 feet high, I get about 5+ miles of coverage. With band openings I’ve heard stations on the opposite side of town and across Lake Erie into Canada.

Even though this IGate will be non-transmitting (cannot relay packets from the Internet), packets are forwarded to APRS-IS. The higher profile – higher power Digitpeaters in the area will relay packets received by your IGate to the local RF network.

Assumptions

This guide is step-by-step in nature, meant for beginners, with brief explanations of the steps. It will help to have an understanding of Linux commands and scripting. Capitalization is important in Linux!

My setup is on my home LAN. The IGate could be installed at a remote site using a shared Internet connection. Be aware that firewalls that might block connection to the APRS-IS network on a shared connection. You may want to request or have port 22 open on your router for SSH to establish a remote connection.

If all wired options fall through, look for a cellular hotspot device such as a MiFi to install along with the Pi. Use the built in WiFi on the Pi 3 or approved WiFi dongles for earlier Pi devices. Associate the MiFi with your Pi (turning on WPA2 so no one else piggybacks on your connection). Test the setup before installing it. Don’t find out after leaving the site that the MiFi times out after a few hours.

Program versions

Applications and versions used in this writeup:

  • Windows 10 64 bit
  • Raspbian Jessie 2016-05-27
  • Win32 Disk Imager 0.9.5
  • PuTTY 0.67
  • SDR Sharp 1.0.0.1444
  • RTL-SDR 0.5.3
  • Multimon-NG ?
  • Pymultimonaprs 1.3.0

Parts list

Listed below are all the parts needed to get this project working. It is noted when items can be left out or substituted.

That’s all the parts needed for this project. Check out the AdaFruit Raspberry Pi page for other hardware that might be useful, like the USB to PS/2 adapter for example. Many of these parts are included in the Raspberry Pi Starter Pack.

Dongle Bits: Projects

This article appeared in the The Lake Erie Amateur Radio Association newsletter The Spirit of ’76 and ’88 June 2014 edition and The Wood County Amateur Radio Club newsletter CQ Chatter July 2014 edition.

Read the rest of the series in the Dongle Bits articles category.


We’re going to take a look at projects others have done with micro-computers and controllers. Many of these will be Amateur Radio related but I will highlight some getting started projects that show setup or basic programming. Since many Hams are into computers and programming, I will highlight some networking and server related uses. Finally, some of the more some crazy and unique setups I’ve come across.

First thing to note: if you receive this newsletter in printed form, you’ll want to go to the club’s website or get it in electronic form to view these links. Links will be to videos or instructions posted online. Any YouTube videos will start at the beginning of the segment.

Getting started tutorials

Ham Radio

I was informed the University of Akron Amateur Radio Club (W8UPD) was planning on using the Raspberry Pi for their second High Altitude Balloon launch on April 8, 2014. Though no reason was given, it was scrapped for the Beaglebone Black board. They configured it to send back Slow-scan TV images overlaid with telemetry information. Unfortunately, the launch was a failure due to high winds and “poorly placed trees.” Upon launch, the payload got snagged and caught in a tree.

I heard from John – N8MDP who setup his Raspberry Pi as a D-STAR hotspot as well. His setup works with the “X-Reflector” system. There are multiple D-STAR reflector systems that co-exist together on the network. His instructions are detailed and the setup is different than mine because different software is needed to access these alternative reflector systems. John installed a webserver on his Pi to control it from the Internet.

Raspberry Pi

Arduino

Networking and server

One of the first projects I saw was how to use the Raspberry Pi as a Home theater PC. This allows you to watch videos, listen to audio, or display photos accessible via the network on a TV.

A Pi can be turned into a home or portable access device used in conferences, competitions, demonstrations, or school project. Some examples are a router, network attached storage (NAS) device, web server, or secure virtual private network (VPN) server. The VPN server uses OpenVPN, an excellent encryption package that offers trust no one (TNO) encryption since you generate the encryption keys.

A useful project is the Raspberry Pi IP address IDer which speaks the IP address if you are operating headless and need to connect to it.

Cool and unique

Want to relive the 8-bit gaming days of the Commodore 64? There is a project called Commodore Pi to create a native Commodore 64 emulator and operating system for the Raspberry Pi.

Build a coffee table gaming rig.

Turn a Raspberry Pi into an FM transmitter.

If you like cheap phones, for $160 you can create your own Raspberry Pi smartphone.

Want to give your dog a treat via email? The Judd Treat Machine will do just that! Send an email to the dog’s email address, it dispenses the treat, snaps a picture, and replies with the picture attached.

The University of Southampton in England created the Raspberry Pi Supercomputer using 64 Raspberry Pi computers. They use a “message passing” system to distribute processing across all 64 devices. His son also helped out by building the rack to hold them out of… Legos!

Raspberry Pi and Lego Supercomputer

Other places for projects and news

Raspberry Pi forums.
Arduino forums.
Slashdot: (Pi) (Arduino).
Lifehacker: (Pi) (Arduino).
Reddit: (Pi) (Arduino).
Podcasts.
Search the Internet!

Next time, we’re going to move on to another type of dongle: the $20 software-defined radio.