Home

About Us

Field Days

Hamfests

Members

Past Meetings

Photo Gallery

Repeaters

Silent Keys

Weblinks

For Sale

VE Testing

EchoLink

Some of the frequently used area echolink node numbers are:

IMPORTANT CONTROLS FOR THE W3MIE ECHOLINK 
(some removed at AB3I's request):

Link info (repeater callsign): *
System status (connected status, link status): **
Disconnect last station to connect : #
Disconnect all stations: ##
Listen only mode (Will not forward audio): *20
Disable listen only: *21
Connect to any random node: 00
Connect to random link (repeaters primarily): 01
Connect to random conference (more than one station): 02
Connect to specific station, enter 4 or 6 digit Node ID See notes
below.

Skywarn/ARES/
RACES capable repeaters in this region should all be a 2 digit number starting with 1. 

If necessary we have up to 70 two digit numbers that can be used for favorite nodes.

If any one knows of any repeaters in northern Ohio or NW Pa that have
echolink and serve as skywarn repeaters in their areas, please speak up.

FAVORITE NODES thus far are:
WR4MG repeater (Dave's home repeater): 20
WA4ORT repeater (via N4CI link): 21
KD4YDC repeater (major Ga. skywarn hub:) 22
KB8WLW repeater system (Cleveland) 23
Echo-link Test server (record/playback audio): 99

You can look up nodes by going to 
http://www.echolink.org/links.jsp
and search by any number of criteria, including geographical location,
city name, etc. The one search function that seems to be strangely
absent is a call sign search. The echolink software itself provides
such a function though. Once you've found the node number you want,
simply enter it directly via DTMF.

If you enter tones and it gives no response, it typically means it
dropped one or two and doesn't see a complete command. If you get a
"not found" error, try the number a couple of more times to be sure it
didn't misinterpret, but links drop and come on-line frequently. Try
the node again later and you'll likely have better luck. If you get a
"not found" error when entering a two digit favorite command, e-mail
Dave, AB3I.

When entering tones, the software is pretty good about picking them
up, even with a bit of noise. However, if you've got a really
scratchy link to the repeater, or less than ideal audio, give it nice
long tones with a distinct break between tones to help it pick them
out accurately. Common echolink courtesy is to identify by callsign
and location when connecting to a node outside the local area.

Remember that capture effect applies with tones. If the link radio is
transmitting, it can't hear incoming tones, and if someone else is on
the repeater, you'll have to overpower them to shut it off. Apparent
dropped tones are often because you're transmitting over the tail end
of one of echolink's voice announcements or a station on the link,
cutting off the first tone.

Some echolink nodes are capable of extremely advanced features,
including, but not limited to, fully functional HF remote
transceivers, satellite transceivers with auto tracking antennas, and
other similarly cool experimental systems. I'd encourage you to poke
around and see what's out there. The state of Georgia uses echolink
for its Skywarn backbone with fantastic results. The NWS office has
the entire state at its finger tips with the push of a button, without
the need for complex RF links, or 6m/HF backbone frequencies. When
you see storms rolling through Georgia, connect to KD4YDC (favorite
22) to listen in.

Enjoy the link!
Dave, AB3I