To use the IRLP node, you simply need to program your radio to use 446.0500 with a PL Tone of 141.3.
Listen to be sure no conversations are in process.
Keyup, pause for 1 second before entering the IRLP node you want to connect to.
You should hear a connect message upon successful connection to the node. Remember to PAUSE, PAUSE, PAUSE. To disconnect, keyup and send DTMF codes 73. You will hear a disconnect message upon successful disconnect.
Node Number 3198
Node City Enid
Node Province/State OK
Node Owner/Sponsor Tim McAnally-EARC-WA5QYE
Node Base Frequency (MHz) 446.0500
Node Offset Frequency (KHz) 0.0000
Node PL (Hz) 141.3
Operating Tips & Bits
PAUSE, PAUSE, PAUSE
The three most important rules for successful contacts.
Please leave plenty of space between transmissions. For many nodes, the only time control ops can get in to disconnect is between transmissions. Also remember to key up and wait for a half second or so before speaking. The exact amount of delay varies by node and linking technology, but PTT across IRLP is not as fast as local carrier squelch simplex.
When first connecting, remember you may be dropping into a conversation in progress, so wait 30 seconds or so before transmitting to avoid interrupting a QSO.
Resist the temptation to break into a QSO unless invited or the conversation is obviously open. It is rude to interrupt an eyeball QSO, it is rude on the radio too. "I-Layer" propagation always provides a good path, so there is no need to hurry to work the "rare one" before the band dies out.
Calling CQ is a great way to solicit a contact. Every Ham knows what that means. If you are specifically trying to make a contact, be sure to make that fact known in your call, especially if you are demonstrating IRLP.
All Topics of conversation within the realm of "Good Amateur Practice" are allowed. There are no specifically prohibited topics, but remember you have an international audience thus your conversation will be heard worldwide. If you are discussing IRLP operating procedures or practices, remember that node access and policies vary considerably based upon local requirements.
When disconnecting, it is not necessary to announce that fact to everyone connected. In fact, a disconnect announcement can be disruptive if you are sneaking in between transmissions of a QSO you are otherwise not a part of. Just bleep in your code and be gone. If you are fortunate enough to have a full duplex control connection, it is actually completely silent if you disconnect on top of another transmission.
IRLP Node 3198
|EARC EchoIRLP Cheat Sheet.pdf||382.45 KB|