Winlink Express setup: choosing between Telnet, Packet, VARA, ARDOP, Pactor and P2P, and getting messages through
- Replies 2
- Views 13
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This is a working outline for a new Winlink Express station, plus a few open questions at the end. Correct anything I have wrong.
The basic architecture. Winlink is a message system, not a mode. Your client (Winlink Express on Windows) builds a message and connects by some method to a gateway, called an RMS (Radio Message Server). The RMS passes traffic to and from the central Winlink servers over the internet. The gateway is the only part that needs internet. Your station can be completely off-grid as long as you can reach a gateway by radio, or reach another station directly with a P2P session.
Session types in Winlink Express.
Telnet: connects to Winlink over the internet, with no radio involved. Use it to confirm your callsign, password, and message flow before touching a rig. Fix account problems here first, so they are not mixed up with RF problems later.
Packet: AX.25 through a TNC, either a hardware TNC or a software one such as a sound card modem using KISS. This is typically used on VHF/UHF through packet RMS gateways. It is simple and robust, but slow at 1200 baud, and it depends heavily on a clean path to the gateway.
VARA FM: a sound card modem for VHF/UHF FM. It is considerably faster than 1200 baud packet when the path is good. The software needs to be installed and configured separately from Winlink Express.
VARA HF: a sound card modem for HF SSB. The free version is speed-limited, and registration removes the limit. Its strength is adapting to changing conditions.
ARDOP: another open sound card HF mode. It is a common choice when someone wants an alternative to VARA, and it is supported through a separate ARDOP TNC program.
Pactor: needs a dedicated hardware modem (SCS). Pactor 1 and 2 are the older modes, and the faster levels need the matching modem capability. It is common on HF gateways, but it is the most expensive entry point.
P2P (peer to peer): a direct station-to-station connection using Packet, VARA, ARDOP or Pactor. No gateway or internet is involved. The two stations agree on a frequency and mode, and one calls the other. This suits local nets and served-agency work when the infrastructure is down.
Sound card and TNC checklist.
1. Use a data mode (USB for HF; data or FM-data input on VHF/UHF), and turn off speech processing, equalizers and noise reduction.
2. Set the PC audio output so the rig is not driven into ALC. Digital modes are not forgiving of overdrive, and splatter reduces your decode rate and annoys neighbors.
3. Decide on PTT early: CAT, serial RTS/DTR, a VOX-style interface, or a hardware interface. Test PTT with a dummy load before going on the air.
4. Disable Windows sound effects and any other app that might use the same audio device.
5. Set the PC clock accurately. Some modes are sensitive to timing, and a sloppy clock causes odd connection failures.
Passwords. You need your Winlink account password in Winlink Express for Telnet and for gateway sessions. Passwords are case sensitive. Keep a recovery email on the account so you can reset it if you forget it.
Questions for the group.
1. For someone with only one radio and one sound card interface, what is the practical order: Telnet test, then VARA FM to a local gateway, then HF?
2. How do you pick HF gateways when you cannot tell which ones are currently reachable?
3. What is the right way to configure and use Radio-only messages, and when would you use them instead of ordinary messages?
4. Any good practice for ICS-213 forms over low-speed links?
Link to comment
https://www.hamradiobase.com/forums/topic/11779-winlink-express-setup-choosing-between-telnet-packet-vara-ardop-pactor-and-p2p-and-getting-messages-through/Share on other sites