<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you for the change! Although the closest node to me is still a
70cm IRLP node that I can't use yet. Any chance you could have the ?
query return the following 4 nodes for short term testing at least.<br>
<br>
1) Nearest EchoLink 2m node<br>
2) Nearest EchoLink 70cm node<br>
3) Nearest IRLP 2m node<br>
4) Nearest IRLP 70cm node<br>
<br>
The difference, as I understand it, is that an EchoLink -R repeater is
a full up normal repeater with a tie back to EchoLink. An EchoLink -L
link is a simplex node that has ties back to EchoLink. As far as the
EchoLink access goes, they're the same function. What they do for the
local surrounding area is what is different.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
John Gorkos wrote:
<blockquote
cite="mid:AANLkTinxCNDj6kqfZJnx0OqK2skZtzCbtXG2xuDRc_-g@mail.gmail.com"
type="cite">Fair enough, the masses have spoken. -L Echolink nodes
are now imported and listed in the AVRS DB. I don't really know enough
about echolink to understand the differentiation, so I didn't include
them.
<div><br>
</div>
<div>John Gorkos</div>
<div>AB0OO</div>
<div><br>
<div class="gmail_quote">On Sat, Jan 15, 2011 at 4:29 PM, Eric Hansen
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:skyssx@gmail.com">skyssx@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Another
reason to enable AVRS to echolink -L; one could easily be set up to run
APRStt concurrently, enabling D-STAR/APRS calls to his callsign when
checked in at the link.<br>
<br>
<div class="gmail_quote">
<div></div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div class="h5">
<div><br>
<br>
</div>
Any particular reason for not using -L nodes? In my location, all of
the -R EchoLinks are 440 and the sole 2m is a -L link. However, that
link is just as good as a repeater (IMHO) as the owner keeps it open
and supports up to 10 concurrent connections. He's also an IRLP node,
so I have the best of both networks available in my local area on 2m,
but you're currently skipping over the EchoLink capability.
<div><br>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>