OVARC Repeaters

OVARC Repeater System

OVARC operates the following repeaters


 

Click here to view the most up-to-date and comprehensive information.

 


Keystone

Green Valley

146.62

Offset: -0.600 MHz

Tone: 156.7

Analog linked to the system repeaters

Echolink Node: 99946

 


Golder

Catalina

147.32

Offset: +0.600 MHz

Tone: 156.7

Analog linked to the system repeaters

Echolink Node: 99946


Marana

Marana Center

447.525

Offset: -5.0 MHz

Tone: 156.7

Analog linked to the system repeaters

Echolink Node: 99946


Main

Oro Valley PD

444.100

Offset: +5.0

Tone: 156.7

Analog linked to the system repeaters

Echolink Node: 99946

D-Star: W7AI___C normally linked to reflector XRF310 Module D

DMR static linked to # 3104668 KT7AZ (Tucson), dynamic linking controlled by User

YSF defaulted to room FCS204 (Arizona)


Calle

Calle Concordia

445.800

Offset: -5.0

Tone: 156.7

Analog not linked to the system repeaters

D-Star W7AI___B normally linked to reflector XRF310 Module D

DMR static linked to #3104668 KT7AZ (Tucson), dynamic linking controlled by User

YSF defaulted to room FCS73102 (SW)


Foothills

KC7AC QTH

445.1375

Offset: -5.0

Tone: 156.7

Analog not linked to the system repeaters

D-Star KG7PJV_B normally linked to reflector XRF310 Modules

DMR static linked to #3104668 (1) KT7AZ (Tucson), dynamic linking controlled by User

 


Camino

AE7GP QTH

440.7625

Offet: +5.0 (no analog)

D-Star KG7PJV B normally linked to refletor XRF310 Module D

DMR static linked to #3104668 (1) KT7AZ (Tucson), dynamic linking controlled by User

 


Tucson Mtn

Tucson Mountain

444.750

Offset: +5.0 (no analog)

D-Star W7NFL__B normally linked to reflector XRF310 Module D

DMR static linked to #3104668 (1) KT7AZ (Tucson), dynamic linking controlled by User

YSF defaulted to room FCS00204 (Arizona)

 


Saddlebrooke

Mountain View Area

445.5375

Offset: -5.0

Tone: 156.7

Analog not linked to the system repeaters

D-Star WD7ARC B normally linked to reflector XRF310 Module D

DMR static linked to #3104668 (1) KT7AZ (Tucson), dynamic linking controlled by User

YSF defaulted to room FCS00204 (Arizona)


In addition, we have the linked analog system transcoded to D-Star reflector XRF310 Module E for normal operation. This allows D-Star users to link to XRF310E and talk/listen to the linked analog system. We plan on shifting reflectors from XRF310E to XRF310D for the Sunday night net. This will allow D-Star users from locations around the world to participate in our Club net. Club members with D-Star hotspots can use their D-Star radio to check into the net using the transcoder. D-Star will be unlinked at Main for the duration of the net allowing analog use of the repeater. The transcoder will be moved back to XRF310E at the end of the net. EchoLink operation continues also.

OVARC Digital Repeater System and Map

map digi repeaters 2019

For more information please see the presentation

Digital Modes with Raspberry PI

 

Repeater information is subject to change. Please click here to see the current listing.

 

Echolink

The OVARC system supports the Echolink node W7AI-L node number 99946.

 

Repeater Best Practices

Starting a QSO

Using the term "CQ" when looking for a radio contact is commonly used in just about every Ham radio band and mode of transmission except for FM repeaters.  VHF and UHF repeaters are always ON and almost always monitored by someone so calling "CQ" on these bands is not the accepted practice.  Mind you it is not illegal to call "CQ" on local repeaters, however, most seasoned Hams would equate this procedure to calling "Breaker Breaker 19" on the 11 meter Citizen Band, and most likely would not answer your call. 

The accepted method when looking for a contact on FM repeaters is to:

  • Listen for at least 15 seconds to see if the repeater is in use
  • If the repeater is quiet, key your MIC and say "This is AF9W listening", or "AF9W monitoring", or "AF9W standing by" or just “AF9W”.
  • If there are others using the repeater and you wish to join the conversation, wait for a pause between the other station's transmissions, and quickly announce your call sign "AF9W", then un-key.  Assuming the others heard your call they will invite you into the conversation.  If you do not get a response, repeat the process until you do.

During the QSO

While operating on a repeater you will notice a "Beep" signal after each station un-keys their MIC.  This is called a courtesy beep and it has two purposes:

1.The "Beep" is there to let everyone know that the current transmitting station has finished talking.

2.The "Beep" indicates that the 2-minute timer on each repeater has reset, and it is OK for the next station to begin transmitting.  The 2-minute timer is there to prevent damage to the repeater transmitter from extended "ON" time caused by station operators that don't know when to take a break.  It is also necessary to comply with FCC rules governing interference.

Unfortunately, some folks forget about the timers, talk over the limit, and then time-out the repeaters which causes them all to shut down until the received station stops transmitting.  Since all four OVARC repeaters are linked for simulcast via the Internet, inherent ISP latency combined with the individual repeater timers creates chaos when someone times out a repeater.  It takes a long time for everyone and everything to reset and get back to normal.  Operators should be cognizant of these problems and avoid timing out the repeaters. 

Remember to leave a pause between transmissions so that other stations may break in to join the conversation.  Without this pause it is frustrating for an operator trying to join the conversation and not being able because the other stations are "Too fast on the Key".  Please leave a 5 second pause after a station stops transmitting and before you start transmitting.

Another point of proper operation when using linked simulcast repeaters is handling of the transmission delay caused by both RF and the Internet.  If operators don’t consider this delay it is most likely that the first few syllables of their transmissions will be lost and not heard on the linked repeaters.  This could equate to the first two or three letters of an operators call sign, or the entire message if the reply was for example "OK".  For general "Rag Chew" communications, missing these first few seconds of a transmission is annoying to everyone because they have to ask, "What did you say"?  However, in emergency or Priority situations repeats required by missing information can cost valuable time. 

Proper operation on linked repeaters means waiting a few seconds between the time the PPT button is pressed and when the operator starts speaking.  During a QSO on the OVARC system:

  • Press your PTT button to key your transmitter
  • Wait at least 2 seconds before speaking your message

This should prevent messages from being garbled by the linking delays.

Final thoughts

Remember that when you are using a repeater system there are many people listening to your conversation.  Maintain the proper social graces while operating.  Also, don’t monopolize the repeater.  If you want to have a long private conversation with someone think about whether you can make contact via a simplex frequency.  If so, move off of the repeater.  If you don’t mind others joining the conversation then stay on the repeater.  If another operator needs to use the repeater for another short conversation then please be courteous and relinquish the repeater to them.  Conversely, don’t break into another conversation only to start a long-winded conversation of your own. 

 

The OVARC repeater system is a shared resource for the use and enjoyment of any amateur operator that can access the system.  If we all operate in a proper and courteous fashion it will make the system more enjoyable for everyone. 

Tucson VHF/UHF Codeplug

Here is an example .csv file that can be imported into CHIRP to provide a beginning codeplug for the Tucson area.  This is not a comprehensive list of repeaters in the Tucson area but is a start for a user created codeplug.

SoAZ_Repeaters_and_Simplex_Frequencies.csv

Additional information