ⓘ 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
Winlink over radio: a setup order that works, from Telnet test to RMS gateway and P2P
This is a discussion starter for anyone setting up Winlink Express for real RF use. Most failed first attempts come from doing the steps out of order, so here is an order that isolates problems. I'd like to hear where people's own workflows differ.
Step 1 is the account and the Telnet session. Install Winlink Express, enter your callsign and password, and do a Telnet Winlink session first. Telnet goes over the internet to the Winlink system, so it proves the account, password, and mailbox work before any radio is involved. Passwords are case-sensitive, so check capitalization before you blame the radio. Keep your recovery email current, because resetting a forgotten password is much easier with it. On RF the password is only used for authentication. Amateur rules still forbid obscuring the meaning of a message, so nothing you send should be treated as private.
Step 2 is choosing a mode, which is mostly a question of band and hardware.
On VHF/UHF you have Packet Winlink (AX.25) and VARA FM. Packet needs either a hardware TNC or a software TNC such as Dire Wolf, reached through KISS or AGWPE. VARA FM runs on a sound card interface, and its wider mode really wants a radio with a flat-audio data port rather than the microphone path.
On HF the main choices are VARA HF, ARDOP, and Pactor. VARA HF and ARDOP both use a sound card. Pactor needs a dedicated hardware modem, and gateway availability for it varies by area. Check the gateway list for what is actually reachable from you before buying anything.
Step 3 is gateway selection. In the Winlink Express session window, open the channel selection list and update it over the internet while you still have a connection. The list shows RMS gateways with frequency, mode, distance, and on HF a propagation estimate. Treat the estimate as guidance, not a promise. The frequency shown for HF is usually the center frequency, so make sure your CAT control or manual dial setting accounts for the USB offset. Listen before you transmit, and if a channel is busy, pick another gateway.
Step 4 is a local test. Before relying on a distant gateway, try a nearby one, or run a P2P session with another station. P2P connects two stations directly with no gateway or internet. Both sides need compatible software, the same mode, and one station listening while the other initiates the connection. Messages in the outbox addressed to the peer are exchanged. P2P is also a good way to isolate whether a failure is your audio chain or the gateway path.
Step 5 is messages and forms. Winlink Express includes templates, including ICS-213. A form opens in a browser, you fill it in, and it is attached to the message so the receiving station's Winlink Express can display it. Keep messages short, especially over HF.
Questions for the thread: which part of this order trips people up most, and how do you handle sound card level setting on shared-use PCs? How do you structure regular practice, such as the Winlink Wednesday habit?
This is a discussion starter for anyone setting up Winlink Express for real RF use. Most failed first attempts come from doing the steps out of order, so here is an order that isolates problems. I'd like to hear where people's own workflows differ.
Step 1 is the account and the Telnet session. Install Winlink Express, enter your callsign and password, and do a Telnet Winlink session first. Telnet goes over the internet to the Winlink system, so it proves the account, password, and mailbox work before any radio is involved. Passwords are case-sensitive, so check capitalization before you blame the radio. Keep your recovery email current, because resetting a forgotten password is much easier with it. On RF the password is only used for authentication. Amateur rules still forbid obscuring the meaning of a message, so nothing you send should be treated as private.
Step 2 is choosing a mode, which is mostly a question of band and hardware.
On VHF/UHF you have Packet Winlink (AX.25) and VARA FM. Packet needs either a hardware TNC or a software TNC such as Dire Wolf, reached through KISS or AGWPE. VARA FM runs on a sound card interface, and its wider mode really wants a radio with a flat-audio data port rather than the microphone path.
On HF the main choices are VARA HF, ARDOP, and Pactor. VARA HF and ARDOP both use a sound card. Pactor needs a dedicated hardware modem, and gateway availability for it varies by area. Check the gateway list for what is actually reachable from you before buying anything.
Step 3 is gateway selection. In the Winlink Express session window, open the channel selection list and update it over the internet while you still have a connection. The list shows RMS gateways with frequency, mode, distance, and on HF a propagation estimate. Treat the estimate as guidance, not a promise. The frequency shown for HF is usually the center frequency, so make sure your CAT control or manual dial setting accounts for the USB offset. Listen before you transmit, and if a channel is busy, pick another gateway.
Step 4 is a local test. Before relying on a distant gateway, try a nearby one, or run a P2P session with another station. P2P connects two stations directly with no gateway or internet. Both sides need compatible software, the same mode, and one station listening while the other initiates the connection. Messages in the outbox addressed to the peer are exchanged. P2P is also a good way to isolate whether a failure is your audio chain or the gateway path.
Step 5 is messages and forms. Winlink Express includes templates, including ICS-213. A form opens in a browser, you fill it in, and it is attached to the message so the receiving station's Winlink Express can display it. Keep messages short, especially over HF.
Questions for the thread: which part of this order trips people up most, and how do you handle sound card level setting on shared-use PCs? How do you structure regular practice, such as the Winlink Wednesday habit?
Link to comment
https://www.hamradiobase.com/forums/topic/11008-winlink-over-radio-a-setup-order-that-works-from-telnet-test-to-rms-gateway-and-p2p/Share on other sites