---

---

IRLP in Clallam County   From the creator of IRLP The Internet Radio Linking Project was started back in November of 1997 as an attempt to use the internet to link radio systems across Canada. The first full time link that was established ran from Vancouver, BC to Saint John, NB. The link had many problems and was shut down in March of 1998 due to the numerous computer crashes and repeater lockups it was causing, and the lack of user control over the system.   I set out to design a better way to use the same technology to perform the same task, while improving usability, user control, and sound quality. My first breakthrough was to replace the existing operating system, Windows, with a more stable and versatile language. I chose Linux, a IBM form of the operating system UNIX, because of its superior networking characteristics, its reliability, and its ease of programming. I designed my own interface board to interface the radio to the computer. This allowed a large amount of delay to be removed from the system because two VOX circuits were no longer being used . I also wrote my own custom control software, and modified an existing voice-over-IP software package to accommodate the project. The final product was a combination of hardware and software that created a nearly seamless radio link between two remote sites on the internet. The product works so well that many people can not believe that they are talking through a link at all! Dave VE7LTD     What is IRLP? IRLP is an acronym for the Internet Radio Linking Project, the brainchild of Dave Cameron VE7LTD of Vancouver BC. IRLP is a state-of-the-art technology concept that links VHF/UHF-FM radio equipment together via the Internet (widely known as VoIP – Voice over IP), similar to how and why some large repeater systems are able to cover such a wide area. Without getting into detail, IRLP basically allows you to have a conversation with another ham or hams around the world by either connecting a local IRLP-equipped repeater or simplex base station to a remote repeater or simplex base station at a different location (known as a node), or by answering an incoming call initiated by a ham from a remote node. Here’s an example:             From what this sounds like, IRLP isn’t ham radio This issue depends on how each ham interprets ham radio and IRLP. It’s another method of conveying messages around the world, using wireless radios at each end. As K4KR states, “Is this the end of HF? [No.] HF radio is a very different kind of magic. On HF, you [can] build your own station and send your own signal to the other side of the earth. Just because Internet Linking allows you to talk to people around the world doesn’t mean it compares to HF. Hams get involved in HF to experience the magic of radio, not simply to talk to people around the world. There are many, non-ham-radio ways to talk around the world.” While it is true that radios are not connected directly to each other, there are radios fully utilized at each end which makes the experience just as interesting and has a multitude of contemporary real-world applications. By no means does IRLP intend, nor will IRLP EVER, replace skywave and satellite communications; IRLP is simply just another method, and has its limitations and vulerabilities as well, such as power and/or connectivity outages due to anything from an accidental cable-cutting mishap to catastrophic events such as an earthquake. It’s understood that this is an issue that ruffles the feathers of many hams, for and against IRLP. Before complaints are sent to the node owner, please read an interesting eHam.net article regarding IRLP. Located there are is about a year’s worth of readers’ messages for and against IRLP, and has some very strong points that must be considered before one becomes closed-minded about their opinion. How do I find out more about IRLP? Start here: IRLP.net – The Official IRLP website Then check out the following web sites: IRLP in Australia – An excellent place to read up on what IRLP is all about IRLP Suggested Operating Procedures for IRLP Users – How to use IRLP IRLP in depth – Another Canadian Invention is Sweeping the World Groups.io – IRLP information and discussion Before using ANY IRLP or EchoLink node Please be aware of the guidelines specific to each node prior to use. Reading and following the node guidelines is a manditory requirement and is expected to be followed every time you use IRLP or EchoLink. Guidelines common to all IRLP nodes, including reflector use, proper protocol, error messages, do’s and dont’s, and other tips are located at the official IRLP website: http://www.irlp.net – click on ‘IRLP guidelines’ See the EchoLink website regarding EchoLink procedures, use, etc. at http://www.echolink.org What nodes are available around here? Here are a few well-known IRLP nodes within range of our area. Click on the node for more information. Node 3249 – W7FEL–R, 146.760 – Joyce, WA, Striped Peak (public access) (repeater node) Node 1000 – VE7RHS, 145.270 – University of British Columbia, Vancouver, BC (repeater) Node 1020 – VE7RNA, 146.680 – Cowichan Valley ARS, Chemanius, BC (repeater) Node 1030 – VE7VIC, 146.840 – Westcoast ARA, Victoria, BC (repeater) Node 1040 – VE7RTC/VE7RSX, 443.950 & 52.830 – Westcoast ARA, Victoria, BC (repeater) Node 1170 – VE7RIA, 147.585 – Victoria Communications Club, Victoria, BC (simplex node) Node 1520 – VE7RRU, 446.025 – Victoria Communications Club, Victoria, BC (simplex node) Here is a document that details how to use IRLP in Clallam County. Who can I conctact locally about IRLP? Contact Bob by email at k6mby@olypen.com

How To Use IRLP on Striped W7FEL

July 1, 2015
W7FEL-­‐R IRLP Node Number 3249
The 3249 IRLP node is currently open-­‐for use by all licensed amateur radio operators. Use the standard IRLP method to connect to r emote nodes by sending the 4 digit remote node number with your radioDTMF pad. To disconnect, send “73” on your DTMF pad. Any remote node may also connect to node 3249 unless a control operator has disabled the node or otherwise limited IRLP connections.
If you have never talked over an IRLP connection, please review the links noted below. One important tip to remember, pause for a second after you key the MIC before you speak. This allows the
connection to complete across the network and helps avoid dropping syllables or words from the start of your transmission. See additional operating instructions below.
See www.irlp.net for Operating Guidelines and a list of active nodes.

The following DTMF code list controls features of the W7FEL IRLP system.

DTMF Code Description
Key radio, push nnnn -­‐ Connect to lRLP node or reflector number. No prefix is required.
Key radio, push 73 -­‐ Disconnect from node or reflector.
Key radio, push A1 -­‐ Reply with Node Status
Key radio, push A2 -­‐ reply with Node Name and Time
Key radio, push A3 -­‐ reply with Last call received
Key radio, push A4 -­‐ Reply with Last outbound call

How to use Echolink on Striped W7FEL

W7FEL-­‐R Echolink Node Number 557235
EchoIRLP is a project with a goal to share hardware and software resources for IRLP and Echolink systems. The EchoIRLP Yahoo Group explains this project in more detail. Software is installed that allows
the IRLP node system to connect to Echolink network node.
The software we have installed on the W7FEL IRLP node is referred to as the “EchoIRLP” project.

What this software does or does not do:
-­‐ does not allow you to cross connect the IRLP and Echolink networks together.
-­‐ does provide the W7FEL IRLP node access to available Echolink clients and conferences.
-­‐ does allow Echolink clients to connect to the W7FEL-­‐R Echolink node number 557235
Note: We are currently filtering Echolink PC client nodes that connect to the W7FEL-­‐R system. Echolink repeaters, links and conferences are not filtered. Outgoing connections from W7FEL-­‐R are also not filtered. This was implemented due to the number of silent connections, mostly from Echolink PC clients. If your Echolink connection to W7FEL-­‐R is rejected with a “not allowed” message, then your Echolink client node is being filtered. The following DTMF code list controls the operation of the W7FEL-­‐ R EchoIRLP node. You will see the operation is very similar to using IRLP. General EchoIRLP controls would be prefixed with “D”. This insures EchoIRLP node numbers are differentiated from IRLP node
numbers. Contact the node operator/controller, with any questions or problems.

DTMF Code Description
Key radio, push 73 -­‐ Disconnect from node, reflector or conference.
Key radio, push Dnnnnn -­‐ Connect to Echolink node number.
You must send all digits without un-­‐keying or dropping out of the repeater. Visit the Echolink current
logins listing web page for a list of active Echolink nodes or list the area Echolink nodes from the node
status search page. .
Echolink Status -­‐All nodes _
Echolink Link Status -­‐ Search by area
Basic Operating Instructions

1. The User should check the IRLP “node info” list at www.irlp.net or the Echolink node list at
   http://www.echolink.orq/logins.jsp to determine the availability of a given individual or
   reflector node.
2. The User dials the desired IRLP node connect command. NNNN for IRLP or DNNNNN (up to 6
   digits in node number) for Echolink.
3. The IRLP or Echolink system responds with a voice message indicating connection to the distant
   node.
4. The go ahead “courtesy” tone will be slightly delayed for the 1 second turnaround time and will
   change to indicate to all users that the repeater is in the IRLP or Echolink mode and to refrain
   from local activity.
5. If the distant individual node is busy with IRLP or Echolink or other RF traffic, the IRLP system
   will respond with “…node busy…”.
6. lt is desirable to monitor for 10 seconds prior to voice announcing your CQ, call, and location so
   that a QSO that might be in progress on the distant repeater can adjust to your node
   connection.
7. It is desirable to wait 1 second or more between each transmission to account for turn system
   around delays.
8. It is also recommended to wait 1 second or more after PTT to starting voice.
9. If there is no activity by either node within about 4 minutes, the nodes will be automatically disconnected.
10. Especially while connected to an IRLP reflector or Echolink Conference, it is common courtesy to pause between transmissions to allow breakers and for nodes to be able to enter DTMF disconnect commands.
11. When connected to a reflector, it is desirable to not have a long separate rag chew on the local
    node. Please disconnect the node from the reflector.
    Disconnecting a node connection:
12. The Member dials the IRLP or Echolink disconnect command 73
13. The distant IRLP or Echolink node will announce with a specific voice message that you are
    disconnected from the node.
14. The go ahead courtesy tone will return to normal to indicate to all users that the repeater is not
    in the IRLP or Echolink mode.