ⓘ Callsign lookups are in real time via the FCC database.
Vanity callsign availability is refreshed daily at 6:00 AM CST.
The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Building a Winlink station from scratch: Telnet first, then gateways, modes, P2P and forms
This thread is for sorting out a sensible order of operations for a Winlink setup, and for comparing notes on where things tend to go wrong. The software and gateway lists change, so treat specifics here as a starting point and check them against the current Winlink documentation. The outline below is the order that tends to cause the fewest headaches.
Step 1: Winlink Express and a Telnet session. Install Winlink Express on Windows and enter your callsign, a password and a recovery email address. Then do a Telnet Winlink session before touching a radio. Telnet connects over the internet straight to a CMS (Common Message Server). It confirms that your account works, that your password is typed correctly (it is case-sensitive), and that you can send and receive. Passwords are not sent in the clear during sessions. The server issues a challenge and the client answers it, but a mistyped or stale password still shows up as a failed login on every mode. Fix it on Telnet, where the failure can only be the account.
Step 2: understand the chain. A radio session goes from your station to an RMS (Radio Message Server, usually just called a gateway). The gateway has an internet link to the CMS, which stores and forwards your mail. When you connect, the gateway delivers your outbound messages and pulls down anything waiting for your callsign. Gateways are not the mailbox, and you do not leave mail on them. The CMS holds it, which is why a message sent while you are off the air will be waiting when you next connect through any gateway.
Step 3: pick the mode for the band. Winlink Express can use several modems. Packet (RMS Packet) is AX.25 on VHF/UHF, normally 1200 baud AFSK, sometimes 9600. VARA FM is the higher-speed VHF/UHF alternative, using your sound card or an interface. VARA HF and ARDOP are sound card modems for HF. Pactor needs an SCS hardware modem and is used on HF gateways too. Which one you need depends on what is actually listed near you, not on which one looks fastest on paper. Open the Channel Selection window in Winlink Express, update the channel list while you still have internet, and look at which modes and bands the nearby gateways support.
Step 4: gateway locations and the channel list. The Channel Selection window lists gateways with distance, bearing, mode and frequency. For HF it can also show propagation estimates. Two practical points. First, the list is cached on your computer, so refresh it before a deployment where internet may not exist. Second, the frequencies in the list are generally center frequencies, so if you tune by hand, remember the dial setting in USB is offset below that (about 1500 Hz below for modems centered at 1500 Hz). With CAT control configured, Winlink Express handles the math. A gateway being listed does not mean it is on the air and workable from your location right now, so have several candidates.
Step 5: TNC and sound card setup. For Packet you can use a hardware TNC or a software TNC like Dire Wolf, usually through a KISS connection (serial, Bluetooth or TCP). For VARA HF, VARA FM and ARDOP, the modem is a separate program that talks to Winlink Express over local ports, so the setup has two halves. First, get the modem alone to key the radio and see audio. Pick the correct sound device (a USB interface or the rig's built-in codec, not the computer speakers), choose a PTT method (CAT, serial RTS/DTR, VOX or the interface's own), and set levels. Second, point Winlink Express at the modem's host and port in its session settings. Keep transmit audio low enough that there is no ALC action. A clean, lower drive level beats a loud distorted one on every one of these modes. Turn off Windows sounds and any audio enhancements on the interface, or they will end up on the air.
Step 6: Radio-only, P2P and forms. Those need their own discussion. I will leave them to the replies, but the main questions are: when does Radio-only make sense, how does a P2P session differ from a gateway session, and how should ICS-213 and other forms be handled? Also, is anyone using Winlink Wednesday as a weekly drill, and how do you structure it?
A reminder on compliance: Winlink compresses data, but the protocol is published and the content must remain plain and legal for amateur service. The control operator is responsible for what goes out over the air, so no business traffic, and no content that violates local rules.
This thread is for sorting out a sensible order of operations for a Winlink setup, and for comparing notes on where things tend to go wrong. The software and gateway lists change, so treat specifics here as a starting point and check them against the current Winlink documentation. The outline below is the order that tends to cause the fewest headaches.
Step 1: Winlink Express and a Telnet session. Install Winlink Express on Windows and enter your callsign, a password and a recovery email address. Then do a Telnet Winlink session before touching a radio. Telnet connects over the internet straight to a CMS (Common Message Server). It confirms that your account works, that your password is typed correctly (it is case-sensitive), and that you can send and receive. Passwords are not sent in the clear during sessions. The server issues a challenge and the client answers it, but a mistyped or stale password still shows up as a failed login on every mode. Fix it on Telnet, where the failure can only be the account.
Step 2: understand the chain. A radio session goes from your station to an RMS (Radio Message Server, usually just called a gateway). The gateway has an internet link to the CMS, which stores and forwards your mail. When you connect, the gateway delivers your outbound messages and pulls down anything waiting for your callsign. Gateways are not the mailbox, and you do not leave mail on them. The CMS holds it, which is why a message sent while you are off the air will be waiting when you next connect through any gateway.
Step 3: pick the mode for the band. Winlink Express can use several modems. Packet (RMS Packet) is AX.25 on VHF/UHF, normally 1200 baud AFSK, sometimes 9600. VARA FM is the higher-speed VHF/UHF alternative, using your sound card or an interface. VARA HF and ARDOP are sound card modems for HF. Pactor needs an SCS hardware modem and is used on HF gateways too. Which one you need depends on what is actually listed near you, not on which one looks fastest on paper. Open the Channel Selection window in Winlink Express, update the channel list while you still have internet, and look at which modes and bands the nearby gateways support.
Step 4: gateway locations and the channel list. The Channel Selection window lists gateways with distance, bearing, mode and frequency. For HF it can also show propagation estimates. Two practical points. First, the list is cached on your computer, so refresh it before a deployment where internet may not exist. Second, the frequencies in the list are generally center frequencies, so if you tune by hand, remember the dial setting in USB is offset below that (about 1500 Hz below for modems centered at 1500 Hz). With CAT control configured, Winlink Express handles the math. A gateway being listed does not mean it is on the air and workable from your location right now, so have several candidates.
Step 5: TNC and sound card setup. For Packet you can use a hardware TNC or a software TNC like Dire Wolf, usually through a KISS connection (serial, Bluetooth or TCP). For VARA HF, VARA FM and ARDOP, the modem is a separate program that talks to Winlink Express over local ports, so the setup has two halves. First, get the modem alone to key the radio and see audio. Pick the correct sound device (a USB interface or the rig's built-in codec, not the computer speakers), choose a PTT method (CAT, serial RTS/DTR, VOX or the interface's own), and set levels. Second, point Winlink Express at the modem's host and port in its session settings. Keep transmit audio low enough that there is no ALC action. A clean, lower drive level beats a loud distorted one on every one of these modes. Turn off Windows sounds and any audio enhancements on the interface, or they will end up on the air.
Step 6: Radio-only, P2P and forms. Those need their own discussion. I will leave them to the replies, but the main questions are: when does Radio-only make sense, how does a P2P session differ from a gateway session, and how should ICS-213 and other forms be handled? Also, is anyone using Winlink Wednesday as a weekly drill, and how do you structure it?
A reminder on compliance: Winlink compresses data, but the protocol is published and the content must remain plain and legal for amateur service. The control operator is responsible for what goes out over the air, so no business traffic, and no content that violates local rules.
Link to comment
https://www.hamradiobase.com/forums/topic/11444-building-a-winlink-station-from-scratch-telnet-first-then-gateways-modes-p2p-and-forms/Share on other sites