User Tools

Site Tools


howto:winlink

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
howto:winlink [2020/10/02 08:34] – [Peer-to-Peer (P2P) Messages] va7fihowto:winlink [2023/11/05 05:08] (current) va7fi
Line 1: Line 1:
- 
 ====== Winlink ====== ====== Winlink ======
 This section outlines how to send and receive messages with [[https://winlink.org/WinlinkExpress |Winlink Express]].  More information about how to configure the hardware can be found on the [[signalink|Signalink How-To]]. This section outlines how to send and receive messages with [[https://winlink.org/WinlinkExpress |Winlink Express]].  More information about how to configure the hardware can be found on the [[signalink|Signalink How-To]].
Line 33: 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. +  * **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.
  
 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:
Line 75: Line 74:
  
   * The first step is to create a script: {{ :howto:p2pscript.png }}   * The first step is to create a script: {{ :howto:p2pscript.png }}
-  * In this example, I named it ''LSO to SCE'' so I can reuse it easily later: {{ :howto:p2pscript2.png }} +  * In this example, I named it ''SCE (LSO)'' so I can reuse it easily later: {{ :howto:p2pscript2.png?425 }} 
-  * Once saved, select it and press **''Start''**: {{ :howto:p2pscript3.png }}+  * Once saved, select it and press **''Start''**: {{ :howto: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:
Line 82: Line 81:
   * 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 [[/howto/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.
 +
 +
 +<WRAP center round tip 85%>
 +As Robert pointed out (see email with ''Subject: BPQ'' from Nov 4, 2023),  some digipeater require adding a port number (but some don't).
 +</WRAP>
 +
 +Here is a short list of scripts that work as of Nov 5, 2023 (replace ''[callsign]'' with the destination callsign):
 +<WRAP group>
 +<WRAP third column>
 +  c ve7lso-8
 +  conn
 +  c [callsign]
 +  conn
 +</WRAP>
 +<WRAP third column>
 +  c ve7wod-8
 +  conn
 +  c [callsign]
 +  conn
 +</WRAP>
 +<WRAP third column>
 +  c ve7spr-8
 +  conn
 +  c 2 [callsign]
 +  conn
 +</WRAP>
 +</WRAP>
 +
 +
 +<WRAP center round important 85%>
 +Note the ''2'' on the third line of the last script.  Failing to add the port number there will give the following error:
 +  VE7SPR-8} DOWNLINK CONNECT NEEDS PORT NUMBER - C P CALLSIGN
 +  Found script connection response CONNECT NEEDS PORT NUMBER - C P CALLSIGN
 +</WRAP>
 +
  
 ==== Digipeaters ==== ==== Digipeaters ====
 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:
  
-^Callsign ^-8 ^-10 ^Sponsor / Location ([[https://k7fry.com/grid/ |Gridsquare]]) ^Last MHeard | +{{pdfjs 800px,600px>/howto/mheard.pdf}}
-|VA7ARE   |-8 |    |Arbustus Ridge Emergency Preparedness |Oct 12020 | +
-|VA7BCE     |-10 |Beaver Creek Volunteer Fire Department Amateur Radio Club, Port Alberni (CN79OG) |Oct 1, 2020| +
-|VA7CCD   |-8 |    |  |Feb 29, 2020 | +
-|VA7CIF   |-8 |    |Strathcona Regional District, Cortes Island (CO70MB)  | | +
-|VA7DXP   |-8 |-10 |David Evans, Ladysmith |Oct 1, 2020 | +
-|VA7EGP   |-8 |    |Strathcona Regional District Emergency Program, Campbell River   |Oct 1, 2020| +
-|VA7EO    |-8 |-10 |Paul Giffin, Gabriola Island (CN89CE) |Oct 1, 2020 | +
-|VA7MWP   |-8 |    |Mid Island Emergency Coordinators and Managers, Duncan |Oct 1, 2020| +
-|VA7PF    |-8 |-10 |Devan Banman, Nanaimo |Feb 29, 2020 | +
-|VA7PRG   |-8 |    |Strathcona Regional District Emergency Program, Campbell River   |Oct 1, 2020| +
-|VA7QBE     |-10 |Qualicum Beach Fire Department, About 40km west of Nanaimo (CN79SC) |Oct 1, 2020| +
-|VA7SSI   |-8 |    |Capital Regional District Emergency Program, Victoria |Feb 24, 2020| +
-|VA7ZWR   |-8 |-10 |Walter Seiler |Feb 29, 2020| +
-|VE7CRD   |-8 |    |Capital Regional District Emergency Program, Victoria  |Oct 1, 2020| +
-|VE7CRP   |-8 |    |Capital Regional District Emergency Program, Victoria  |Oct 1, 2020| +
-|VE7GCT   |-8 |    |Glenn C Terrell, Mill Bay|Oct 1, 2020| +
-|VE7GEC   |-8 |-10 |Michael J. Hale, Gabriola |Oct 1, 2020| +
-|VE7GN    |   |-10 |Michael J. Hale, Gabriola Island (CN89CD)  |Oct 1, 2020| +
-|VE7LSO   |-8 |-10 |CVRD - Emergency Communications Team, Ladysmith |Oct 1, 2020| +
-|VE7PRL   |-8 |    |Capital Regional District Emergency Program |Oct 1, 2020 | +
-|VE7RYF   |-8 |-10 |Mt McDonald at 1500ft |Oct 1, 2020| +
-|VE7SKR   |-8 |-10 |CVRD HQ station, Duncan (CN88DS) |Oct 1, 2020 |  +
-|[[http://www.ssiarc.ca/frequencies.php |VE7SPR]]  |-8 |-10 |Salt Spring Island ARC, SPI (CN88GT) |Oct 1, 2020| +
-|VE7TXD   |-8 |-10 |Mid Island Emergency Coordinators and Managers |Oct 1, 2020| +
-|VE7WOD   |-8 |    |CVRD - Emergency Communications Team |Oct 1, 2020|+
  
  
Line 119: Line 128:
   * [[http://www.ve7ed.com/projects.html]]   * [[http://www.ve7ed.com/projects.html]]
   * [[https://winlink.org/RMSChannels]]   * [[https://winlink.org/RMSChannels]]
 +
 +===== Winlink Message via Digipeater =====
 +If a Winlink station (-10) is too far to be reached directly, a digipeater station (-8) can be used to relay the message.
 +  * Write your message as a ''Winlink Message'' (not ''P2P Message'')
 +  * Open a ''Packet Winlink'' session (not ''Packet P2P'')
 +  * Connection type: ''Script''
 +  * Add a script like this one:<code>
 +c ve7lso-8
 +conn
 +c ve7gn-10
 +conn
 +</code>
 +  * Select your script and start.
 +
 +In this example, my message will be sent to VE7LSO-8, which will repeat it to VE7GN-10, which will then send it to the CMS via the internet.
 +
 +
 +
 +===== Message Templates =====
 +
 +Templates are a way to send complex pre-formatted ''html'' forms while keeping the bandwidth low.  The basic idea is to:
 +  * Select a template from Winlink, which opens a form in your web browser.
 +  * Use the web browser to fill out the form and "Submit" it back to Winlink.
 +  * The attachment that's actually sent via Winlink is an ''xml'' file that contains the information you entered in the form without any of the fancy formatting (thus keeping the size small).
 +  * Once the receiver opens the message, Winlink uses that ''xml'' file and puts it into its **local** ''html'' form to re-constitute the fancy formatting.
 +
 +The result is that both the sender and the receiver see the fancy form, but only the actual information is transmitted (not the formatting).  Of course, this only works if both stations have the same local template, which is why it's important to keep Winlink templates up-to-date.
 +
 +If you use the same template often, there are two things you can do to expedite the process.
 +
 +==== Template Shortcut ====
 +The first is to set a template shortcut:
 +  * Click on ''Message'' and select ''Set favorite tempates...'' \\ {{ .winlink:winlinktemplate01.png }}
 +  * Click on ''Browse'', select the form you want to save, and give it a name. \\ {{ .winlink:winlinktemplate02.png }}
 +  * To use it, open a new message and click on the name you entered earlier. \\ {{ .winlink:winlinktemplate03.png }}
 +
 +==== Save Message Data ====
 +Many templates allow you to save the message body so you can quickly reload it later.  In my example:
 +  * I first wrote the message I want to save **without the date**
 +  * Then ''Save Quick Message Data'', which will save a basic ''txt'' file.
 +
 +When it's time to use it:
 +  * I click on ''Load Quick Message Data'' and
 +  * Click in the ''Date/Time:'' field to populate it.
 +  * Then click ''Submit'' to send it back to Winlink.
 +
 +{{ winlinktemplate04.png }}
 +
 +
 +
 ===== EasyTerm by UZ7HO ===== ===== EasyTerm by UZ7HO =====
 <WRAP round todo box center 80%>  <WRAP round todo box center 80%> 
howto/winlink.1601652899.txt.gz · Last modified: 2020/10/02 08:34 by va7fi