W0ANM
- IRLP Node 3106 Operating Guide
General Guidelines
The normal FCC and repeater rules apply, remember it’s still radio!
IRLP global operating rules always apply.
Local node operating rules always apply in addition to the general guidelines.
Many of our codes are unique only to this node.
Never discuss any codes when connected to, or using other nodes.
When traveling ask for permission and guidelines to use other nodes.
Always identify before sending any DTMF codes.
You must listen for active QSO’s before using the link. Check status by sending the DTMF code “*0” (star-0).
QSO’s in progress have priority over outgoing link calls.
Local users should yield to incoming link calls.
You must leave a 2 second pause between transmissions.
Due to delays in the IRLP you must wait 1 second before speaking after pressing your PTT.
Pause for 15 seconds when joining a reflector.
Always disconnect for local only QSOs.
If you have any specific questions not covered here please contact W0ANM<at>arrl.net.
Operating Hours
The node will be open for outgoing calls from 7 am to 11 pm local time.
The node will go into receive only mode during the overnight hours.
Incoming calls from other nodes may bring up the link and QSO with local stations at any time.
The distant end node control operator is responsible for monitoring the link activity during our nighttime hours.
You may find the node disabled during the normal or nighttime operating hours.
This shutdown may be due to:
Link down for maintenance,
An Internet connection problem.
Lack of a control operator.
shutdown may be due to a timeout (see Timers), link down for maintenance, an Internet connection problem or lack of a control operator.
Timers
Link Timer
This timer is set to 4 minutes. It is the maximum amount of key-down time for a single transmission.
Inactivity Timer
Currently set for “disable”. Timer is reset by local COS. Activity from remote stations does not reset this timer. If the distant node has a shorter inactivity timer it may close the connection first. This allows for monitoring of the reflectors. This value may change depending upon irlp node operation.
Procedures
• Common Modes
There are two connection modes for an IRLP connection. Direct one-to-one or, one-to-many via a Reflector.
Direct connect is just like it sounds where repeater (node) "A" connects direct with node "B". With this type of link the two nodes are interconnected and no other IRLP connections are possible. While repeaters "A" and "B" are connected, anyone attempting to connect with either node will be told by a recording that - "The node you are calling is currently connected to call sign" however all local traffic on each repeater will be heard on the other repeater as well.
While Direct Connect is preferred for a city to city chat, the most common type of connection in use today is via a reflector. A reflector is a Linux computer that is not connected to any radio but rather sits on lots of Internet bandwidth capable of allowing many repeaters to be inter-connected together by streaming the received audio back to all other connected stations. At any given time there are usually 6 to 10 repeaters around the world interconnected via a reflector.
You can always check which stations are connected to a reflector by visiting the "In Calls" page. A complete list of all nodes and their status may be found at http://status.irlp.net
Node Use
The first thing we must all remember is to leave a gap between transmissions. Having said that this is a good time to list the three main rules when connected to a node or reflector:
1. Pause
2. Pause
3. Pause
Due to the slight increase in delays created by multiple Tone Squelch radios in the links between the repeater and IRLP link radio, a slight change in our normal operating procedures is required with IRLP. By leaving a pause between transmissions it:
allows users on other nodes a chance to check in.
allows other nodes time to send touch-tone commands to drop their node.
The most important guideline to remember is leaving a pause after pressing the PTT button as well as between transmissions.
Local QSOs
Remember, you may not always hear the other simplex user when using the node. I may activate a simplex repeater, which is basically a parrot module that will repeat everything the node hears and re-transmits it. I understand that this becomes very awkward to use. It's best to use a local repeater.
Making Connections
Just as you would listen before transmitting on any repeater. You must listen for at least 10-15 seconds for current activity before making any transmissions. There may already be an active connection or local QSO in progress.
Always identify before using any control codes.
The standard method to connect to a node or reflector is to use the node number. To connect to node 9250, key your radio, wait 1 second, and then send 9250.
Example
"This is call sign send dtmf", wait for link up message then, listen, pause, listen, pause then announce yourself. It's a good idea to announce your location as in "call sign Saint Michael, MN".
Please note that some nodes require an additional unpublished prefix to the standard codes. These nodes are closed for various reasons; contact the owner of that node if you require access. When planning a trip out of the local area it is best to check in advance to see if a node is open. Simply key your radio, wait 1 second and send "73" to disconnect from any node or reflector. You can only disconnect during pauses between transmissions. You cannot disconnect while someone is speaking from the local or remote node.
Error Messages
From time-to-time you may receive error messages when attempting to connect with a node or reflector. The most common ones are:
"The node you are calling is not responding, please try again later"
This is caused by a loss of Internet connectivity to one end of the call attempt.
"BEEP Error- The call attempt has timed out, the connection has been lost"
This error occurs when a node is OFF-LINE. Some nodes such as in the UK use dial-up connections and then, only for short periods. Also there may be temporary net or node problems.
"The Connection Has Been Lost"
If the Internet connection drops; this error message will be heard. I found this out when I accidentally kicked out my network cable while working around the node computer.
Shortcuts
I have created shortcuts codes. These allows for easier access when mobile.
Here is a list of the current shortcuts:
|
DTMF CMD |
Node |
Description |
|---|---|---|
|
*0 |
|
Link Status Query |
|
*1 |
|
Announces Current Time |
|
*2 |
|
Announces Current Weather for Minneapolis |
|
*411 |
|
Play Announcement (Future) |
|
*310 |
|
Disable - Simplex Repeater Mode (Future) |
|
*311 |
|
Enable - Simplex Repeater Mode (Future) |
|
A1 |
9078 |
REF9078 Alaska, USA |
|
A2 |
9201 |
REF9201 Indianapolis, IN USA |
|
A3 |
9208 |
REF9208 Indianapolis, IN USA |
|
A4 |
9250 |
REF9250 Las Vegas, NV USA |
|
A5 |
9350 |
REF9350 LAX, CA USA |
|
A6 |
9353 |
REF9353 LAX, CA USA |
|
A7 |
9876 |
REF9876 Denver, CO USA |
|
A8 |
9750 |
REF9750 UK Reflector |
|
|
|
|
|
|
|
|
Notes: