Sun Coast Amateur
Radio Club Society

User Tools

Site Tools

You are here: home » links » winlink
links:winlink

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
links:winlink [2023/11/05 05:08] – created - external edit 127.0.0.1links:winlink [2024/11/24 13:26] (current) – va7fi
Line 5: Line 5:
  
 When composing a new message, you must choose how the message will be sent: When composing a new message, you must choose how the message will be sent:
-{{ :howto:winlinkmessagemode.png }}+{{ :links:winlinkmessagemode.png }}
   * **Winlink Message**: Your station makes a radio connection to a Radio Message Server (RMS). The RMS makes an Internet connection to a Common Message Server (CMS) that is the central message repository. Your messages are sent via radio to the RMS and then through the Internet to the CMS until the recipient connects and downloads messages addressed to themselves.  This mode is efficient and highly reliable. Winlink operates multiple CMS that synchronize with each other frequently to provide completely redundancy. If an RMS is down and unable to receive a connection, the client can connect to a different RMS. Since all messages are stored in the central CMS database, it doesn’t matter which RMS the sender and recipient connect to.   * **Winlink Message**: Your station makes a radio connection to a Radio Message Server (RMS). The RMS makes an Internet connection to a Common Message Server (CMS) that is the central message repository. Your messages are sent via radio to the RMS and then through the Internet to the CMS until the recipient connects and downloads messages addressed to themselves.  This mode is efficient and highly reliable. Winlink operates multiple CMS that synchronize with each other frequently to provide completely redundancy. If an RMS is down and unable to receive a connection, the client can connect to a different RMS. Since all messages are stored in the central CMS database, it doesn’t matter which RMS the sender and recipient connect to.
   * **Radio-Only Message**: Where as the previous mode relies on an Internet connection between the RMS and a CMS, the Radio-Only mode does away with the CMS and the internet connection it relies on. Instead, messages are sent to a designated RMS for storage until it is retrieved by the recipient. This mode of operation can operate with local and total Internet outages.   * **Radio-Only Message**: Where as the previous mode relies on an Internet connection between the RMS and a CMS, the Radio-Only mode does away with the CMS and the internet connection it relies on. Instead, messages are sent to a designated RMS for storage until it is retrieved by the recipient. This mode of operation can operate with local and total Internet outages.
Line 14: Line 14:
 So the steps to compose a message are to: So the steps to compose a message are to:
   - Select how the message will be sent as.   - Select how the message will be sent as.
-  - Enter the recipient's address (usually their callsign, which may or may not require an [[/howto/ssid |SSID]])+  - Enter the recipient's address (usually their callsign, which may or may not require an [[/links/ssid |SSID]])
   - And lastly, after the message is written, **Post to Outbox**, which saves the message locally and marks it to be sent.   - And lastly, after the message is written, **Post to Outbox**, which saves the message locally and marks it to be sent.
  
Line 20: Line 20:
  
 ===== SSID ===== ===== SSID =====
-Before going into more details, it might be worth taking a small detour to learn about SSIDs (the dash number after the callsign) since it has a different meaning depending on whether it's for APRS or Winlink.  See the [[/howto/ssid |SSID How-To]] for more info.+Before going into more details, it might be worth taking a small detour to learn about SSIDs (the dash number after the callsign) since it has a different meaning depending on whether it's for APRS or Winlink.  See the [[/links/ssid |SSID How-To]] for more info.
  
  
 ===== Winlink Messages ===== ===== Winlink Messages =====
  
-{{ :howto:opensessionwinlink.png}}The type of connection needed is chosen from the **Open Session** drop down menu.+{{ :links:opensessionwinlink.png}}The type of connection needed is chosen from the **Open Session** drop down menu.
  
 Messages that are marked to be sent as Winlink Messages require a Winlink connection: Messages that are marked to be sent as Winlink Messages require a Winlink connection:
Line 32: Line 32:
   * **Pactor Winlink** is an HF connection to an RMS. It requires an expensive [[wp>PACTOR]] TNC between the radio and computer.   * **Pactor Winlink** is an HF connection to an RMS. It requires an expensive [[wp>PACTOR]] TNC between the radio and computer.
   * <del>**Winmor Winlink**</del>  Winmor is deprecated.  See [[/blog/2020-09-15/no_more_winmor |here]] for more info.   * <del>**Winmor Winlink**</del>  Winmor is deprecated.  See [[/blog/2020-09-15/no_more_winmor |here]] for more info.
-  * **Ardop Winlink** is another HF connection to an RMS that doesn't necessarily require a TNC. The IC-7300, for example, can connect to the computer directly with a simple USB cable.  The connection is slower than PACTOR however. For more details, see the [[howto/winlink_ardop |Winlink Ardop]] page.+  * **Ardop Winlink** is another HF connection to an RMS that doesn't necessarily require a TNC. The IC-7300, for example, can connect to the computer directly with a simple USB cable.  The connection is slower than PACTOR however. For more details, see the [[links/winlink_ardop |Winlink Ardop]] page.
  
 For Winlink connections, the address and frequency of the session must match that of a RMS chosen (not that of the recipient).  A list of RMS can be found in the **Channel Selection** table: For Winlink connections, the address and frequency of the session must match that of a RMS chosen (not that of the recipient).  A list of RMS can be found in the **Channel Selection** table:
-{{ :howto:channelselection.png }}+{{ :links:channelselection.png }}
 Once the table is updated, select an RMS near you, and ensure that the frequency of your radio matches that of the RMS listed in the table and press **''Start''**.  At this point, two things will happen: Once the table is updated, select an RMS near you, and ensure that the frequency of your radio matches that of the RMS listed in the table and press **''Start''**.  At this point, two things will happen:
   - All the Winlink messages in your Outbox will be sent to the RMS and forwarded to the CMS, and   - All the Winlink messages in your Outbox will be sent to the RMS and forwarded to the CMS, and
Line 48: Line 48:
  
 ===== Peer-to-Peer (P2P) Messages ===== ===== Peer-to-Peer (P2P) Messages =====
-{{ :howto:p2popensession.png}}Messages that are marked to be sent as Peer-to-Peer Messages require a P2P connection:+{{ :links:p2popensession.png}}Messages that are marked to be sent as Peer-to-Peer Messages require a P2P connection:
   * **Packet P2P** is a direct VHF or UHF connection between the two stations exchanging messages.   * **Packet P2P** is a direct VHF or UHF connection between the two stations exchanging messages.
   * **Pactor P2P** is a direct HF connection between the two stations exchanging messages using the PACTOR protocol.   * **Pactor P2P** is a direct HF connection between the two stations exchanging messages using the PACTOR protocol.
Line 56: Line 56:
 ==== Direct ==== ==== Direct ====
 For a ''Direct'' P2P connections, the address and frequency of the session must match that of a recipient (there is no RMS): For a ''Direct'' P2P connections, the address and frequency of the session must match that of a recipient (there is no RMS):
-{{ :howto:p2pstart.png }}+{{ :links:p2pstart.png }}
   * Ensure that the frequency of your radio matches that of the recipient.   * Ensure that the frequency of your radio matches that of the recipient.
   * Ensure that the recipient has a P2P session open.   * Ensure that the recipient has a P2P session open.
Line 71: Line 71:
  
 ==== Script ==== ==== Script ====
-It's possible to connect to a station out of reach using a digipeater.  On Vancouver Island, multiple digipeaters are setup on 144.970 MHz with an [[/howto/ssid |SSID]] of ''-8'' and require a ''Script'' to access.  For example, for ''VE7HZF'' to send a message to ''VE7SCE'' via ''VE7LSO-8'', all three stations need to be on 144.970 MHz:+It's possible to connect to a station out of reach using a digipeater.  On Vancouver Island, multiple digipeaters are setup on 144.970 MHz with an [[/links/ssid |SSID]] of ''-8'' and require a ''Script'' to access.  For example, for ''VE7HZF'' to send a message to ''VE7SCE'' via ''VE7LSO-8'', all three stations need to be on 144.970 MHz:
  
-  * The first step is to create a script: {{ :howto:p2pscript.png }} +  * The first step is to create a script: {{ :links:p2pscript.png }} 
-  * In this example, I named it ''SCE (LSO)'' so I can reuse it easily later: {{ :howto:p2pscript2.png?425 }} +  * In this example, I named it ''SCE (LSO)'' so I can reuse it easily later: {{ :links:p2pscript2.png?425 }} 
-  * Once saved, select it and press **''Start''**: {{ :howto:p2pscript3.png?560 }}+  * Once saved, select it and press **''Start''**: {{ :links:p2pscript3.png?560 }}
  
 If you monitor the traffic as you connect to the digipeater, you'll notice a few things: If you monitor the traffic as you connect to the digipeater, you'll notice a few things:
   * Everything you send to ''VE7LSO-8'' is being repeated by the digipeater for ''VE7SCE''   * Everything you send to ''VE7LSO-8'' is being repeated by the digipeater for ''VE7SCE''
-  * Your callsign (in this case ''VE7HZF''), is being retransmitted by the digipeater as ''VE7HZF-15''.  See the [[/howto/ssid |SSID How-To]] page for more info.+  * Your callsign (in this case ''VE7HZF''), is being retransmitted by the digipeater as ''VE7HZF-15''.  See the [[/links/ssid |SSID How-To]] page for more info.
   * The exchange takes more than twice the time of a direct connection because unlike a voice repeater that repeats in real time, a digipeater waits for you to stop transmitting before it repeats it.   * The exchange takes more than twice the time of a direct connection because unlike a voice repeater that repeats in real time, a digipeater waits for you to stop transmitting before it repeats it.
  
Line 120: Line 120:
 From Roberts Creek, VA7FI is able to hear the following digipeater (''-8'') and RMS (''-10'') stations on 144.970 MHz: From Roberts Creek, VA7FI is able to hear the following digipeater (''-8'') and RMS (''-10'') stations on 144.970 MHz:
  
-{{pdfjs 800px,600px>/howto/mheard.pdf}}+{{pdfjs 800px,600px>/links/mheard.pdf}}
  
  
Line 183: Line 183:
 </WRAP> </WRAP>
  
-An easy way to connect a radio to a computer using a Signalink is to use the UZ7HO Soundmodem program (see the [[howto:signalink|Signalink How-To]] for more information).  But another really good program by UZ7HO is [[http://uz7.ho.ua/packetradio.htm | EasyTerm]], which allows you to connect to another station and send specific commands to it.+An easy way to connect a radio to a computer using a Signalink is to use the UZ7HO Soundmodem program (see the [[links:signalink|Signalink How-To]] for more information).  But another really good program by UZ7HO is [[http://uz7.ho.ua/packetradio.htm | EasyTerm]], which allows you to connect to another station and send specific commands to it.
  
 For example, VE7HZF connected to ''VE7LSO-8'' and typed ''H'': For example, VE7HZF connected to ''VE7LSO-8'' and typed ''H'':
Line 199: Line 199:
  
 ==== Setup ==== ==== Setup ====
-{{ :howto:easytermsetup.png }}+{{ :links:easytermsetup.png }}
 |<   100% 50% 50%   >| |<   100% 50% 50%   >|
 ^  EasyTerm Setup screen.  ^  SoundModem Settings screen.  | ^  EasyTerm Setup screen.  ^  SoundModem Settings screen.  |
links/winlink.1699189699.txt.gz · Last modified: by 127.0.0.1