crawler#976
Expedition Leader
My personal policy is as follows:
I usually key up and say: "KE7IXX would like to access the IRPL node in appoximately 60 seconds. Is there any outstanding traffic on this repeater?"
I listen for the full minute, and if it's clear, say:
"This is KE7IXX controlling IRPL Node (XXXX) in (XXXXXXXX)" and while still transmitting type in the node number and then release the key.
After the node connects, pause and listen for traffic on the node freq. When clear, make your call.
Remember to pause before speaking - key up wait for one or two seconds before speaking to allow the connections to be made.
Also, wait for any squelch tails to drop before keying up after the last transmission.
When you've completed your call always thank the node owner for the useage before closing, even if you are part of the club that owns the node. While still transmitting type in 73, and release the key.
More info - excerts from:
http://www.narri.org/IRLP.html
I usually key up and say: "KE7IXX would like to access the IRPL node in appoximately 60 seconds. Is there any outstanding traffic on this repeater?"
I listen for the full minute, and if it's clear, say:
"This is KE7IXX controlling IRPL Node (XXXX) in (XXXXXXXX)" and while still transmitting type in the node number and then release the key.
After the node connects, pause and listen for traffic on the node freq. When clear, make your call.
Remember to pause before speaking - key up wait for one or two seconds before speaking to allow the connections to be made.
Also, wait for any squelch tails to drop before keying up after the last transmission.
When you've completed your call always thank the node owner for the useage before closing, even if you are part of the club that owns the node. While still transmitting type in 73, and release the key.
More info - excerts from:
http://www.narri.org/IRLP.html
IRLP OPERATING GUIDELINES
Listen to others use the IRLP to get the hang of it. Here is a few DO's and DON'Ts:
DO pause between transmissions to let other in or others to enter DTMF command.
DO hold your microphone PTT for one or more seconds before talking to allow all systems time to connect.
DO NOT try to make or break connections unless you are an authorized control operator.Those who control must identify themselves as controlling before sending DTMF command tones and return the node to the connection state you found it in, i.e., idle or connected to a node or reflector. Always ask if someone is using the connection before you change it.
DO NOT rag chew locally on a reflector or on a node connection. When the IRLP system is busy keep QSOs to 5 minutes or less.
DO pause for at least three to five seconds before talking after the node connects to a reflector to make sure you will not talk over a QSO in progress.
________________
Node-to-Node Connections
Direct one node-to-another node or one node-to-many via a connection to a Reflector. Direct connect Node-to-Node is just like it sounds where node "A" connects direct with node "B". In this mode the two nodes (repeaters) are interconnected and no other IRLP connections are possible. While "A" and "B" are connected, anyone attempting to connect with either node “A” or “B” will be told by a wave file recording that: "The node you are calling is currently connected to call sign or node number".
2) Node-to-Reflector Connections
The IRLP system has a hand full of servers called "reflectors" that allow for many nodes to connect together for nets, special activities or HF style QSOs. When a node is connected to a reflector it hears all the audio streams that are sent between the nodes that are connected to the reflector. Nodes will come and go freely to the reflectors, however, some node owners will leave their nodes connected to a reflector as a gateway for the local area.
__________________
WESTERN REFLECTOR OPERATIONS POLICIES
These operating procedures are provided help assure your enjoyment of the Western Reflector. Please pause for three seconds before talking upon connecting to any Western Reflector channel to allow the audio streams to reach your node, and to make sure a QSO is not in progress, before you start talking. Pause between transmissions to allow others into QSOs and key up for a long second so others will have chance to hear all other. Quick keying is not the sign of a good reflector user.
__________________
CURRENT USES OF THE W7AOR WESTERN REFLECTOR 925X CHANNELS 0 - 9
You are welcome on any of the Western Reflector channels. However, public service activities, or emergency traffic have priority over casual traffic on any channel. If a controlled net is in progress follow the direction of the net control station.
Channels 0 -9
Channel 0 (Main Channel) - 9250 Calling and QSOs
Channel 1 - 9251 Linking and QSOs
Channel 2 - 9252 Special Feeds - Listen Only
In the past NASA Audio Feed was active during Shuttle Missions and Space Station activities.
Channel 3 - 9253 Open QSO QSO and linking channel. California Activities and Emergency Services
Channel 4 - 9254 Hawaii–Pacific Rim Linking, Special Activities and Emergency Services.
Various nets and interconnections relating to the Hawaii-Pacific Rim are found on this channel. Guam conducts a wide area net on a weekly basis.
Channel 5 - 9255 Special Activities and QSO's.
High Altitude Arizona Balloon Launches Hear cross band repeaters activity via 9255. See Contact Jack W7JLC at Node 3182 or by e-mail jscra@cableone.net for more information. The webpages are: http://www.ansr.org and http://www.kd7lmo.net and the yahoo groups is http://groups.yahoo.com/group/Ballooning.
Channel 6 - 9256 Calling and QSO
Channel 7 - 9257 Calling and Nets.
This channel is used by American Red Cross, the Disaster Communicators Forum (DCF), and RACES organization residing outside Nevada (Nevada uses 9258 and *NV-GATE*.) The DCF and ARC uses 9257 and Echo link Conference Server *DCF-ARC* 336037 to link communicators together before, during, and after disasters. This is to augment local communications with communicators outside the effected areas.
In the past various individuals and Amateur Radio organizations have come forth to provide emergency response communications where it was needed. Those affected by a disaster deeply appreciate the dedication and effectiveness of ham radio operators. Recent disasters have reaffirmed the need for ham radio operators to augment governmental operations.
See http://groups.yahoo.com/group/DISASTER_COMMUNICATORS_FORUM/ This forum is for those who recognize the need to share information. including lessons learned, discuss preparedness planning and disaster relief coordination. It is intended that all organizations involved in preparedness and response, including, but not limited to ARC, ARES, RACES, FEMA, Sky warn, Salvation Army, ERC, and Homeland Security will participate in the Disaster Communicators Forum (DCF) for the betterment of the whole.
See http://groups.yahoo.com/group/VoIP_American_Red_Cross_Communicators_Net/ for net information and group communications.
Channel 8 - 9258 Calls and Nets
Ref 9258 (Channel 8) is linked to Echo link Conference Server NV-GATE (152566) and thus allows IRLP nodes on Channel 8 to talk to Echo link nodes on NV-GATE. The NV Section ARRL ARES-Skywarn uses this channel for nets.
Nevada ARES/Skywarn Net Every Wednesday at 7 PM Pacific Time. This net is for all parties interested in Skywarn activities. Other ARES business may follow Skywarn. All check-ins provide a weather report for practice and are able to check equipment.
Nevada State ARES/RACES Net Every Thrusday at 7 PM Pacific time. For the leasdership and all intersted parties.
Channel 9 - 9259 Reserved for ERC-ECS Nets. Not open for QSOs.
________________
Last edited: