Tag Archives: Winlink

Ohio Section Journal – The Technical Coordinator – July 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-Jul-18.pdf

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

DSCF5081 K8JTKHey gang,

Around the time of Dayton, the FBI asked everyone to reboot their routers. Why would they do that? Over the last two years more than 500,000 consumer and small business routers in 54 countries have become infected with a piece of malware called “VPNFilter.” This sophisticated malware is thought to be the work of a government and somewhat targeted with many of the infected routers located in Ukraine.

Src: Cisco’s Talos Intelligence Group Blog

Security researchers are still trying to determine what exactly VPNFilter was built to do. So far, it is known to eavesdrop on Internet traffic grabbing logon credentials and looking for specific types of traffic such as SCADA, a networking protocol controlling power plants, chemical plants, and industrial systems. Actively, it can “brick” the infected device. Bricking is a term to mean ‘render the device completely unusable’ and being as useful as a brick.

In addition to these threats, this malware can survive a reboot. Wait, didn’t the FBI ask all of us to reboot our routers? Won’t that clear the infection? No. In order for this malware to figure out what it needs to do, it reaches out to a command-and-control server. A command-and-control server issues commands to all infected devices, thus being “controlled.” C&C, as they are often abbreviated, allows the bad guys in control a lot of flexibility. It can allow infected devices to remain dormant for months or years. Then, the owner can issue commands to ‘wake-up’ the infected devices (called a botnet) and perform intended tasks. Tasks can range from attack a site, such as DynDNS which I wrote about in November of 2016, to steal logon credentials for users connected to the infected router. Back to the question, the FBI seized control of the C&C server. When an infected router is rebooted, it will try to reach out to the C&C server again but instead will be contacting a server owned by the FBI. This only gives the FBI a sense of how bad this infection is. Rebooting will not neutralize the infection.

Affected devices include various routers from Asus, D-Link, Huawei, Linksys, MikroTik, Netgear, TP-Link, Ubiquiti, Upvel, and ZTE, as well as QNAP network-attached storage (NAS) devices. There is no easy way to know if your router is infected. If yours is on that list, one can assume theirs is infected. As if that wasn’t bad enough, many manufactures don’t have firmware updates to fix the problem. The ones that have fixed the problem did so years ago. Since no one patches their routers, that’s why there’s half a million infected.
First thing to do is gather information about the make, model, and current firmware of your router. Then check for announcements from the manufacturer about affected firmware versions or preventative steps. The only known way to clear this infection is to disconnect it from the Internet, factory-reset the router, upgrade the firmware (if one is available), and reconfigure it for your network – or simply throw it away.

If those last couple words strike fear into your heart, there are a couple options:

  • See if your ISP has a device they will send or install for you. It can be reasonably assumed that devices provided or leased by the ISP will be updated by the ISP.
  • Find someone in your club that knows at least the basics of networking to help reconfigure things
  • Many newly purchased devices come with some sort of support to get you up and running

If you’re a little more advanced and want to learn more about networking:

  • EdgeRouter-X
    Use 3rd party firmware. Currently they are not showing signs of being vulnerable to VPNFilter or other infections. 3rd party firmware projects are often maintained by enthusiasts. They are updated LONG past when the manufacturer stops supporting their own products and updates often happen quickly. Some of those projects include: OpenWRT/LEDE, DD-WRT, or Fresh Tomato.
  • A Linux box could be setup with Linux packages to mimic router functionality or use a distribution such as pfSense or OPNsense.
  • Another great device to use is the Ubiquity EdgeRouter-X for $49.
  • Check the “Comparison of Firewalls” for other ideas.

That $5 hamfest deal isn’t sounding so great anymore. It’s the law of economics for these companies too. $10, $30, or $100 for a device isn’t going to sustain programmer’s time to find, fix, troubleshoot, test, and release firmware updates for a 7-year-old device. It’s a struggle. I think it will come down to spending more on better devices which will be upgraded longer or spend $50-$100 every 3-5 years to replace an OK one.

The Department of Commerce released a report on the threat of botnets and steps manufactures could take to reduce the number of automated attacks. It hits on a number of good points but lacks many details. “Awareness and education are needed.” Whose responsibility is it to educate? I can write articles in the OSJ but I’m not going to be able to visit everyone’s house and determine if your devices are infected. “Products should be secured during all stages of the lifecycle.” Automated updates could take care of this problem but doesn’t address what-ifs. What if the update fails or worse yet, bricks your “Smart” TV as an example? Who is going to fix or replace them? Will they be fixed if it’s out of warranty? Not to mention operating system “updates” are bundled with more privacy violations and ways to monetize users.

There’s a lot of work to be done. I wish I had the answers. Regardless, we all need to be good stewards of the Internet making sure ALL attached devices are updated and current.

More technical details on VPNFilter and citation for this article: https://www.schneier.com/blog/archives/2018/06/router_vulnerab.html
https://blog.talosintelligence.com/2018/05/VPNFilter.html

Finally this month, thank you to all the clubs and groups that sent messages to this station via WinLink or NTS over Field Day weekend. It was the most I’ve ever received, about 12 – 15 messages altogether.

Thanks for reading and 73… de Jeff – K8JTK

Ohio Section Journal – The Technical Coordinator – February 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-Feb-18.pdf

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

DSCF5081 K8JTKHey gang,

Have a bunch of odds and ends for everyone this month.

Ham Cram Sessions

I received a piece of feedback worth sharing from December’s article on the “ham cram” type training sessions. One group in the section is working on a cram session for new licensees. That will be followed up with a “now what” session. The follow up session would have mentors and elmers available to help get new hams on the air. Depending on the success, this may be followed up with a General class too.

I think it’s a great idea to follow up with the “now what” session in a more relaxed environment for learning and getting them comfortable being on the air.

Digital Communications in Amateur Radio

Operating PSK31

I’ve been working on my Digital Communications in Amateur Radio series for the Wood County Amateur Radio Club. The series started with an overview of Ham radio digital modes and how to get your station setup with different interface options. From there I’ve been taking an introductory look into specific modes, though mostly ones used on HF. My articles are available in the club’s newsletter, CQ Chatter, found on the Wood County Amateur Radio Club Website (past years are on the CQ Chatter Archives page) or available on my site as well. Check them out to get an introductory look at digital modes.

Latest additions:

  • Conversational Digital Modes like PSK, RTTY, MFSK, Olivia (February 2017)
  • Narrow Band Emergency Messaging System or NBEMS (August 2017)
  • Winlink (February 2018)

Yaesu Fusion Announcements

After the New Year, Yaesu released an announcement with regard to their Fusion C4FM offerings.

  • The DR-2X purchase program will continue through June 30, 2018.
    • A trade-in program is available for current DR-1X repeater owners (they will not accept the beta version) towards the purchase of a DR-2X. $300 if you are trading in a DR-1X and only want the DR-2X repeater. If you wish to include the IMRS IP linking option in the DR-2X, the price will be $500.
    • Buying the DR-2X outright is $900. $1100 to include IMRS.
  • New Firmware will be released for DG-ID and DP-ID functionality in the DR-1X repeaters. Much like the Wires-X upgrade, it is very likely the repeater will need to be sent back to Yaesu for this firmware upgrade.
  • They are releasing the DR-1X FR. The DR-1X FR is a “factory refurbished” DR-1X for $400. It will have the DG-ID and DP-ID firmware already installed. The DR-1X FR cannot be used for the trade in program towards a DR-2X.

The discounted prices listed for the DR-2X and DR-1X FR require an application available from Yaesu. Firmware upgrade details or applications can be obtained by contacting John Kruk – N9UPC (Sales Manager for Yaesu USA) at j.kruk@yaesu.com or through the Yaesu Service department.

Yeesh. Lost yet? I won’t rehash my thoughts on Fusion (see August & September 2017 editions of the OSJ) but I think this announcement only further fragments their offering.

Tom Gallagher – NY2RF to Retire

Tom Gallagher – NY2RF is going to retire after 2 short years as CEO of the ARRL. For me the cliché is true: it only seems like yesterday. I appreciated Tom’s articles in QST and his behind the scenes look at the ARRL. As an MBA, I loved his explanation into some of the financials and reasons for the league raising membership dues in 2016 (July 2017 QST, Mythbusting: ARRL Not “A Big Radio Club”). The League may have $14.7 million in assets but that doesn’t mean that is money lying around. It goes toward programs and services to benefit members and non-members alike. Despite the non-profit status our government affords the organization, they need to pay competitive wages to employees and authors – otherwise they will go elsewhere. I also had the privilege to correspond with Tom on, I think, an excellent direction to get Makers into the ham radio hobby.

I wish Tom well in his retirement. Announcement: http://www.arrl.org/news/arrl-ceo-tom-gallagher-ny2rf-to-retire

Tinkercad

Speaking of Makers, I saw a video on the Amateur Logic podcast that demonstrated TinkerCAD electronics. If you’ve done anything with 3D printing, you’ve probably used Tinkercad. Tinkercad is a product of Autodesk, makers of software for architecture, engineering, and construction manufacturing. As Tommy demonstrates in the video, Tinkercad has an electronics section to simulate building electronic circuits and projects. This can be used as a great introduction into electronic circuit building for students and kids. The simulator has many types of electronic components: switches, capacitors, Arduinos, diodes, power supplies, oscilloscopes, potentiometers, resistors, ICs, breadboards, motors, servos, sensors, and of course – wires!

Tommy duplicates a simple blinking LED project he built in a previous episode using the simulator – even using the exact same Arduino code. I wondered if there was a product available to simulate circuit building and was quite impressed how well the simulator worked. Check it out in Amateur Logic episode 113. To sign up and start “tinkering,” go to: https://www.tinkercad.com/. 6 years or so ago, they were charging for the service. It appears when Autodesk took it over, it’s been free to use.

Scanner Anti-encryption Bill

Lastly for this month, I’m a scanner listener and I’m intrigued by the State of Ohio’s MARCS-IP public service safety system (Multi-Agency Radio Communications over IP). In short, it’s a state wide P25 digital communications system that allows users to be anywhere in the state and communicate with their agency. Once of the selling points for any commercial digital system is the ability to encrypt. Only those authorized can “unscramble” the transmission, meaning scanner listeners are locked out of listening to that particular group, or system in a few cases. Agencies love it and scanner listeners hate it.

Robert Wareham – N0ESQ

Our friends in the Colorado section made headlines last month when State Government Liaison and Section EC Robert Wareham – N0ESQ participated in drafting what is being called the “anti-encryption Bill.” With the backing of Colorado State Representative Kevin van Winkle (R), the bill outlaws blanket encryption by state and local governments striking a balance between transparency and the public’s right to monitor public agencies. Legitimate needs of confidential investigations and tactical operations are not protected under the bill. There are criminal penalties for those who monitor these communications to further a criminal enterprise, avoid arrest, detection, or escape capture.

While this bill only applies to Colorado, it could set a path for other states to draft something similar. Encryption for public radio systems is always a hot topic with completely valid points on both sides. There is a 51 page thread on the topic in the Radio Reference forums debating reasons both ways.

Thanks for reading and 73… de Jeff – K8JTK

Digital Communications in Amateur Radio: Winlink

This article appeared in the The Wood County Amateur Radio Club newsletter CQ Chatter February 2018 edition.

Read the rest of the series in the Digital Communications in Amateur Radio articles category.


Hurricane season wasn’t particularly fun in 2017. We had both extremes. Houston got hit with Hurricane Harvey which required little response from the ham community. Infrastructure stayed online. Disruption to communication systems and Internet was minimal. This left many hams wondering, ‘are we at the point where our infrastructure is stable enough to survive a category 4 hurricane?’ ‘Are hams still relevant since we were not needed for this type of event?’ We got the answer to those questions over the next month with two category 5 hurricanes. Irma impacted the state of Florida and Maria devastated the relatively poor U.S. possession of Puerto Rico. We went from wondering if ham radio was still relevant in emergency situations to rethinking training for extended deployment scenarios, all within a matter of weeks.

Ham radio news sources pointed out many communication techniques were utilized getting traffic in and out of affected areas. An ARRL press release indicated “Maxim Memorial Station W1AW at ARRL Headquarters is monitoring the HWN, 60-meter interoperability channel 2, and Winlink for any traffic.” Winlink gained prevalence in ham news media due to these disasters, gained popularity in emergency communications circles, and became an operating requirement for hams that assisted in Puerto Rico. Winlink is a very powerful and flexible system for exchanging all types of messages.

“Winlink (also known as Winlink 2000) is a worldwide radio messaging system that uses amateur-band radio frequencies to provide radio interconnection services that include email with attachments, position reporting, weather bulletins, emergency relief communications, and message relay” (Wikipedia). In other words, Winlink is a global email system via radio. The backbone uses the Internet for communication but users do not need an Internet connection. This makes the system popular in Emcomm when the Internet is not available. Winlink was first used recreationally by mariners, RV campers, and missionaries. The entire system is run by volunteers and a 501(c)(3) not-for-profit organization. Though similar in name, the “WIN System” is a popular IRLP repeater system based in California and entirely different.

https://www.winlink.org/content/getting_started_winlink_and_winmor

The Winlink system consists of multiple Common Message Servers (CMS) on multiple continents thought the world. The CMS servers form a “star” network configuration to coordinate traffic and provide services like email, webmail, telnet, bulletins, and reporting. Each CMS is a mirror image of the others for redundancy, failover, and outage situations. The Internet, by design, can work around outages. To date, there has been no global outage of the Internet – only regional. Having multiple servers, with redundant copies of the same data, means one or more could be affected by an outage and the system still functions. As of November 1, 2017, the CMS servers have been moved into the Amazon Web Services (AWS) cloud for greater redundancy.

Remote Message Servers (RMS) are scattered throughout the world and are the RF connection into the Winlink system. RMS gateways access the resources of the CMS servers via the Internet. These nodes are provided by hams familiar with the system and are setup on many ham bands (HF, VHF, UHF). On VHF/UHF, connectivity is limited to local clients. HF gateways serve a wider area but depend heavily on band conditions.

Finally, your computer runs the client software which interacts with services provided by the CMS, most often through an RMS gateway. The client software sends and receives messages. Size is limited to 120KB maximum, including attachments. Winlink uses a “store and forward” approach to messaging meaning clients are not constantly connected to an RMS or CMS gateway.

There are currently 6 client software applications available for Winlink. A feature comparison is available at: https://www.winlink.org/ClientSoftware. Winlink Express (formally RMS Express) is the preferred client because it’s developed by the system administrators and supports all features of the system. The software is well supported and frequently updated. The application looks and operates much like a stripped-down email client. Using a familiar email interface makes the application easy-to-use. Though free to download and use, Winlink Express is nagware. It will frequently prompt to purchase a key supporting development of the system. Registration of $24 is encouraged but not a requirement to use Winlink.

Winlink Express interacts with a wide selection of transceivers, provides different operating modes (PACTOR, Packet, Telnet, WINMOR Virtual TNC), and offers different connection methods (relay over mesh and D-STAR networks). It can be operated in any of four general methods:

  • Winlink: access messages on the CMS via an RF connection to an RMS gateway using the Internet.
  • Peer-to-Peer (P2P): messages exchanged directly with other users over RF, Internet, or mesh without the use of a RMS or CMS.
  • Radio-only: messages transferred between HF RMS gateways – without use of the Internet.
  • Telnet Post Office: connects to the CMS directly over the Internet.

A growing library of forms is available for ARES, RACES, SHARES, or MARS organizations including ICS, ARRL, and form types used in Ohio. The advantage of Winlink versus NBEMS is the ability to exchange messages over the public Internet. A form could be emailed directly to a government official instead of relayed via another ham. Winlink Express makes it easy to fill out or reply to forms by utilizing the local web browser. When composing a message, these forms are found under “Select Template.”

A “Query Catalog” accesses services provided by the CMS such as weather and marine forecasts, news, and propagation reports. Location coordinates can be reported through Winlink as well.

Winlink Express will work on a modern computer or Windows tablet running Windows Vista or later. The WINMOR Virtual TNC requires a 700 MHz or greater processor and 512 MB RAM or more due to the Digital Signal Processing (DSP) needed. An Apple or Linux version of Winlink Express is not available but it can be run using a virtual machine or dual-boot configuration. A Linux client is available but does not support all features.

This series primarily focuses on soundcard modes over HF and I will be discussing the WINMOR Virtual TNC. WINMOR is a low-cost interface utilizing the SignaLink USB for $120 as opposed to a PACTOR 3 dedicated hardware modem which can run $1,100 – $1,600. Low-cost hardware means tradeoffs. WINMOR is not anywhere near as fast or reliable as a PACTOR 3 modem, but it does a very good job.

To get started, first go to: ftp://autoupdate.winlink.org/User%20Programs/. Download two programs from the list of files: latest itshfbc program and Winlink_Express_install. ITS HF Propagation is prediction software to provide a rough estimate of the signal path quality between your QTH and remote RMS. Install both applications, order doesn’t matter. Click “next” through both installs, accepting defaults.

An Internet connection is required on the computer for initial setup. After starting Winlink Express, a “Winlink Express Properties” configuration will be seen. If not, click Settings, Winlink Express Setup. At a minimum the following fields must be completed: callsign, choose a password, enter a non-Winlink password recovery email, and grid square. Under Service Code, if you plan on using EMCOMM channels, make the code read: PUBLIC EMCOMM

I recommend checking Display list of pending incoming messages prior to download. This will display incoming message details prior to download allowing the user to select or reject messages based on size or sender. Click Update. An account will be setup on the Winlink system. The Winlink email address won’t become active until a message is sent through the CMS gateway. Click Remind Me Later on any Winlink Express Registration screens.

To create a message activating the Winlink email address, click the New message icon or click Message, New Message.

In the To field, enter your real email address. In the Subject field, enter something like “My first Winlink message.” In the message body, enter something like “This is my first Winlink message, whoo hoo!”

The message is ready to send, but wait! There is no “send” option. What gives?!? Since this system is store-and-forward, messages are Post to Outbox and appear in the “Outbox” System Folder. Messages in outbox can still be edited but will be sent when connected to a CMS.

Next to “Open Session,” in the drop-down select Winmor Winlink. Click Open Session.

Two more boxes will appear: “WINMOR WL2K Session” and “WINMOR Setup.” The WINMOR WL2K Session box is where an RMS gateway is selected and it displays the connection status.

You will be prompted to select the Capture and Playback soundcard devices in the WINMOR Setup box. For the SignaLink, select USB Audio CODEC. Leave all other settings at their defaults. Click Update. A third “WINMOR Sound Card TNC” box will appear. This window shows a waterfall along with transmit and receive state of the virtual TNC. Ignore this box for now.

On the SignaLink, begin with the TX and RX volume knobs set to the 12 o’clock position. Set delay (DLY) to the 2nd tick-mark (8 o’clock position).

If you have a way to control your radio through CI-V commands or equivalent, click Settings, Radio Setup, and configure the settings for the radio. Radio control makes it much easier when selecting different RMS gateway stations. Selecting a different station will automatically change the radio’s frequency and mode. With a VOX device like the SignaLink, for “PTT Port” select External. Click Update.

Back in the WINMOR Winlink Session box, click Channel Selection. An “HF Channel Selector” window will open. A message will ask to ‘update the channel list and recompute the propagation estimates now?’ Click Yes. If not asked, click Update Table Via Internet. This table will update with the current list of Winlink RMS gateway channels on HF. The list can be updated over radio in the future if desired.

Once updated, the presence of color in the “Path Reliability Estimate” and “Path Quality Estimate” columns mean the ITS HF Propagation predictor program is installed and working. Calculations are based on your grid square and solar flux index. Update the current grid square in Winlink Express setup and this table often when traveling. “Mode” is the bandwidth of the RMS node. A higher number means faster transfers are possible. “Hours” means the hours each day the node is online. “00-23” is all day, “02-13” is 02:00 – 13:00. The rest is self-explanatory.

To select a particular RMS gateway, double-click that row in the table. Gateways in green are good choices but ones at the top of the list may not always provide the best connection. Reliable gateways are found by trial and error and can be added to the “Favorites” list. If Rig Control is enabled, the radio should tune to the dial frequency of the RMS gateway and enter USB mode. If not, tune the radio’s display frequency to the “Dial Freq” (VERY important!) shown in WINMOR. Warm up the Tuner if it needs it. Remember to use no more than 30% power. Click Start.

If WINMOR thinks the channel is busy, it will prompt to verify you still want to connect because your transmissions maybe interfering with another station. Your radio will start pinging the remote RMS gateway station. In the WINMOR Sound Card TNC, above the receive indicator will be the “Measured T>R Latency” value. This measures the transmit/receive turnaround time. This should be less than 250ms and adjustable in part by the SignaLink DLY knob. Higher values will cause problems receiving from the RMS gateway. While receiving transmissions from the gateway, adjust the RX knob to a level that falls within the green portion of “Rcv Level.”

With any luck, your client will connect and your first Winlink message will be sent! There will be A LOT of back-and-forth (TX/RX switching) between your radio and remote RMS gateway. These are handshaking and acknowledgments or sending/receiving messages. When all messages are exchanged, the client will automatically disconnect from the RMS gateway. Clicking “Stop” will gracefully disconnect and ID at any time during a session. “Abort” should only be used when something is very wrong because communication is terminated immediately (without ID). Attempts will be made by the RMS to reestablish communication with the client before eventually timing-out.

Once the test message is received in your actual email, your new callsign@winlink.org email address is now active! Send a reply to the test message through your real email. To call a different RMS gateway, click Channel Selection and select a different station. Wait 5 minutes or so for the reply email to reach the Winlink CMS. Click Start in the WINMOR Winlink session box. You will see your reply downloaded to the inbox! When replying to lengthy messages, I will keep a few sentences (paragraph at most) of the original message. This keeps the transmission time down. The original sender can look at the full message in their client sent folder.

Before going crazy telling people to send messages, there is one crucial piece to this system. Winlink uses a “whitelist” (approved senders list) approach for external email addresses. This keeps abuse and spam to a minimum. As a Winlink user, you are free to send messages using your Winlink address to other Winlink users. Other Winlink users can do the same, freely contacting you.

External email addresses are handled very different. An external email is any mail system other than Winlink (Gmail, Outlook, DACOR, Buckeye Cable, BGSU, etc.). If you first send a Winlink message to someone@someprovider.com, that email address is automatically added to your Winlink whitelist. That means email from someone@someprovider.com will be delivered to your Winlink inbox.

For an external email address to send you a message unsolicited to Winlink, there are two options: add that email to your whitelist ahead of time or the sender must put “//WL2K” in the subject line. Example: “//WL2K Holiday Meeting.” Anything with //WL2K in the subject is considered a deliverable message and will not be flagged as unauthorized. By default, all outgoing messages have this inserted automatically by Winlink Express. When some individual replies to your message, which would have //WL2K in the subject, it will be accepted. Any non-whitelisted (blacklisted) addresses or messages without //WL2K in the subject, the sender will receive a bounced error message saying “Sender not authorized for any recipient.”

Whitelists can be managed by logging on to the Winlink My Account page and click My Whitelist. That page will provide details how to update the whitelist using client commands, if desired.

Another important detail to remember, there is no expectation of privacy with the Winlink system. RMS gateway owners and Winlink administrators can read messages exchanged through the system. They are looking for Part 97 violations and inappropriate usage of the system. Violators will be blocked. I’m sure they would find details of your camping trip fascinating, but they really don’t care.

Email messages through this system are considered 3rd party traffic under Part 97. The email message resides on the CMS until you (a ham) make a connection to another ham’s station (RMS) to retrieve your messages. This is similar in nature to passing messages over the National Traffic System (NTS).

The list of services available through the Winlink system is extensive. Winlink is quite flexible allowing many different ways to access the system over RF, APRS, or Internet. Feel free to send a message to my Winlink email address, K8JTK—at—winlink.org. Replace “—at—” with the appropriate email symbol. Don’t forget to include //WL2K in the subject!

Find out more information:

Winlink website: https://winlink.org/

Introduction presentation: https://www.youtube.com/watch?v=UTx9pY1Akl8

Resource for beginners: https://www.winlink.org/content/getting_started_winlink_and_winmor

System tutorials, documents, and FAQs: https://www.winlink.org/content/winlink_book_knowledge

Terminology of the system: https://www.winlink.org/glossary

Winlink over APRS: https://www.winlink.org/APRSLink

Ohio Section Journal – The Technical Coordinator – December 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/12/december-edition-of-ohio-section-journal.html

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

DSCF5081 K8JTKHey Gang,

In October, I was invited by Medina County ARES to see a presentation about Winlink. I had heard of it as a way to send email messages over the HF bands. There were rumors around whether specialized hardware was needed and I really wanted to see what it was all about. Rick – K8CAV gave a great presentation on how it all works and some tips that really helped me get operating on Winlink.

Winlink, in short, is a way to send email via radio circuits frequently used by RV campers, boaters, and mariners where the Internet may not be available or reliable. It is a store and forward system meaning your messages will be held and delivered when you call into a gateway, much like the dial-up or BBS days. There are a number of ways the software will operate: connect to a remote gateway station over the air, operate peer-to-peer over-the-air, connect via the Internet using Telnet (yeah, yeah ‘telnet isn’t secure’ but neither is your email going out over the air), or webmail. Winlink has regional Central Messaging Servers (CMS) which connect to the Radio Messaging Servers (RMS) over the Internet. The RMS is the gateway your client connects to for sending and receiving messages over-the-air.

There is little privacy as other stations can read your messages but the intent is to have a worldwide emergency email messaging system. Messages can be exchanged with any email address (Gmail, your ISP) on the Internet using the assigned callsign@winlink.org email address. Stations conducting business will likely get blocked from the RMS gateways. Attachments can be included with messages but due to bandwidth, these should be kept to small files like CSV or TXT files – no multi-megapixel images or videos.

There are three pieces to the Winlink client software: RMS Express is the ’90’s looking email client, Winmor – the modem, and ITS HF Propagation is a third party software program that works with Winmor to determine propagation for connection reliability. I got Winlink setup and working with my radio and SignaLink so no specialized hardware is required. A lot of back-and-forth transmit and receiving happens between the client and gateway. The TX/RX turn-around time needs to happen quickly (under 200ms), longer will require a high number of retransmissions. One tip to help minimize the delay: set the SignaLink delay control no further than the second hash mark (8 o’clock position). To get started, go to ftp://autoupdate.winlink.org. Click “User Programs.” Download and install “Winlink Express Install,” and “itshfbc” to their default locations. To get an account created on the system, you need to send one email to an Internet address such as your personal email. In addition, Winlink has an “APRSLink” where you can check for messages, read, compose, forward, and delete all by sending APRS messages. Feel free to send me a message to “my call” at winlink.org. More: http://www.winlink.org/

I’ve also been playing around with a new device from Shark RF called the OpenSpot. It’s a small company with two guys in Estonia (South of Finland). Production is done on a batching basis so there is a waiting list. It seems like they’re shipping units close to once per month. Once I got the shipping notice, I had the device within a week. They say 3-6 business days shipping time and it arrived certainly within that range. The OpenSpot is a standalone digital radio gateway otherwise known as a hotspot. It currently supports DMR (Brandmeister, DMR+), D-STAR (DPlus/REF, DCS, XRF/DExtra, XLX), and System Fusion (FCS, YSFReflector). If the mode or network isn’t supported, they do take requests and will make additions available via firmware upgrades. Since it is a hotspot device a transceiver capable of operating that mode is required. They are doing something cool since DMR and Fusion use the AMBE2 codec. A DMR radio can be used to access the Fusion network and vice-versa (DMR Talk Groups with a Fusion radio).

The OpenSpot has a lot of flexibility, very well designed, and is superior to the DV4Mini. It doesn’t need different Raspberry Pi images for different modes like the DVMega. The device comes with everything: the OpenSpot hotspot, Ethernet cable, USB cable, USB power adapter, and antenna. It runs an internal webserver for device configuration. I even like how they do the firmware update process. The OpenSpot shows up as a drive to the computer and using the copy command – copy the firmware to it and voilà – done. For DMR, it will operate like a DV4Mini with the radio configured in TG 9 (talk-group) or it will operate like a repeater (my preference) where the Talk Groups are push-to-talk. All the TAC groups are available (310, 311, 312, etc) and call routing works. I could not get these to go on the DV4Mini. D-STAR works great too. You can link and unlink to reflectors using radio commands. It does not have a drop down for linking directly to a D-STAR repeater on the network. The only systems listed are reflectors. Forum posts describe how to link to a D-STAR repeater (like a DVAP or DNGL would do) using the “Advanced Mode” screens.

It’s not great for portability as it comes (in a car, for example). I have not tried any of the USB to Ethernet adapters with my smartphone or tried a Raspberry Pi as a WiFi to Ethernet bridge. OpenSpot requires an Ethernet cable connection meaning no WiFi though there are plans to add this and uses USB for power and firmware upgrades. As with these devices in DMR mode, they do not transmit a valid call sign. The radio ID is not valid identification. If you listen to a repeater in FM it will ID in CW. Unfortunately, the cost is about twice that of the DV4Mini 182.50 € which, when I ordered, was about $235 including shipping. More: https://www.sharkrf.com/

Other new tech (Christmas gifts?). With advancements in Software-Defined Radios (SDR) I’m seeing a new breed of devices hams can use as radios: your smartphone. Well, at least something that resembles a smartphone or tablet – still need the additional hardware. A device out of the UK called “MyDel Hamfone Smartphone Transceiver” is available. It offers a 3G cellphone, 70cm transceiver (500mw/1W) with camera, expandable SD card, and GPS. The few reviews are positive but there is some question if its FCC certified in the US. More: http://www.hamradio.co.uk/amateur-radio-handheld-radio-mydel-handhelds/mydel/mydel-hamfone-smartphone-transceiver-pd-6093.php

Bob – W2CYK and the guys over at RFinder (the online repeater directory of the ARRL) have released the “RFinder Android Radio.” Their device integrates 4G LTE & GSM cell technologies alongside FM (DMR is also available) radios into a device with the RFinder repeater directory database. The directory offers coverage maps and switching repeaters is a point-and-click away. They also boast the elimination of codeplugs for DMR. This is great as finding codeplugs, or the information for one, is not always readily available. More: http://androiddmr.com

This past month, the Parma Radio Club invited me to their meeting to give the Raspberry Pi presentation. There was a lot of good discussion and questions. This is always good to hear because you know the audience is engaged, thinking, and ultimately providing real-time feedback on the presentation. Thanks for having me at your meeting. More: http://www.parmaradioclub.com/

Don’t forget, National Parks on the Air will be wrapping up at the end of the year. According to Tom Gallagher – NY2RF, NPOTA is getting closer to #1MillionQSOs: https://twitter.com/hashtag/1millionqsos. Look out for those NPOTA stations to get your score up for your wallpaper (that is certificate if you don’t operate special events and contests).

Starting this past fall with the kickoff of new TV seasons, the CW is airing a show called “Frequency” loosely based off the 2000 Sci-Fi thriller of the same name. It starred Dennis Quaid and Jim Caviezel as father and son, Frank and John Sullivan. This was big with hams because the movie incorporated something that resembled ham-radio which allowed the father and son to talk 30 years into the past and future. The TV show has gotten positive reviews with a Rotten Tomatoes score of 74% with the biggest criticism being the back-and-forth between now and 20 years in the past. It airs Wednesday nights at 9pm (Ham Nation time so it gets the DVR treatment here) with the last couple episodes available on the CW website and on Netflix streaming. More: http://www.cwtv.com/shows/frequency/

Finally, don’t forget the HF Santa Net through Christmas Eve. Starts at 8:30 pm Eastern and can be found on 3916 kHz for the little ones to have a chance to talk with Santa! More: http://www.3916nets.com/santa-net.html

Thanks for reading. Happy holidays, Merry Christmas, and Happy New Year!

73… de Jeff – K8JTK

Radio Interface Setup – For getting started with Ham Radio Sound Card digital modes

Table of Contents

Introduction – page 1

Configuration
-Playback settings – page 2
-Recording settings – page 3

Testing and troubleshooting – page 4
-Transmit
-Receive

Recording with Audacity – page 5
-Recording settings
-Record all received and transmitted audio
-Timer recording
-Saving
-Playback

Sound card clock calibration – page 6

Introduction

This document will demonstrate basic setup of a radio interface device in the Windows Sound Control Panel to use with Ham Radio Sound Card digital modes. Programs include: Ham Radio Deluxe DM780, MMSSTV, Fldigi, wsjtx, FreeDV, Easypal. In addition, it will demonstrate how to record digital transmissions and play them back.

This is written with the beginner in mind and many concepts outlined step-by-step. It will provide direction for further experimentation on your own or on the net and direction for troubleshooting.

The SignaLink USB was used but these instructions can be adopted for similar devices. Those using other methods may find the settings and techniques useful.

SignaLink and many other external interfaces have external volume controls. Set these controls at half to start. Adjust these controls first as they are the easiest to adjust and fine tune while operating. If a situation occurs where you have too much/little audio with the volume controls set low/high, then adjust the Windows audio levels second.

It is important to point out:

  • Plugging the same device into a different USB port will be recognized as a new device by the system. This means the audio settings will need to be re-configured. In addition, the audio device settings in the digital mode program may need to be re-configured as well.
  • The process of setting audio levels is not exact.  Each system is different, drivers are programmed differently, hardware interacts differently with the operating system. It will take some time to fine tune audio levels.

Prepared for The Lake Erie Amateur Radio Association’s Digital Net (http://www.leara.org/).

Program versions

Windows 7 – 64 bit
Audacity 2.0.6

Resources

Still having trouble after using this tutorial? Read through the product manual and support documentation. Below are links for popular devices.

Specific instructions can be found online typically by searching: [name of application] [radio interface device]. Example: Fldigi SignaLink USB.

SignaLink

Homepage: http://www.tigertronics.com/

General support, operating tips, manuals, and modifications (all models): http://www.tigertronics.com/sl_suprt.htm

SL USB troubleshooting: http://www.tigertronics.com/slusbts.htm

Rigblaster

Homepage: http://www.westmountainradio.com/

Knowledge base: http://www.westmountainradio.com/knowledge_base.php

Drivers and manuals: http://www.westmountainradio.com/content.php?page=wmr-downloads