<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Echolink is just voice. D-Star supports data. If you buy the high
end priced 1.2Ghz radio, it has an ethernet plug on it, and if you
have it linked to another 1.2ghz radio, you get a 128kb data link
with ethernet as your "pluggable" interface. That's pretty easy to
use. There are lots of things that could be done with echolink.
But even echolink is tied down as a "proprietary" closed standard.
Sure, we've reverse engineered how it works so that my Javecho, and
other echolink clients can "work" with it. But, the servers are
privately operated, and there is no apparent interest in enhancing
the protocol to allow "data", multiple UDP port use so that a single
NAT'd home connection could host multiple echolink instances.<br>
<br>
Choice is nice, and "open" can be good, but in the end, there are
always limitations, and you can either live with them, deal with
them with disgust or roll your own. It's easy, and emotionally
rewarding, to feel like you are doing the right thing by "being
disgusted" with what you can use, how you want. But, in the end,
you are deciding to miss out on what you can do now, while you wait
for what might be possible later. It's okay to make that choice,
it's your right to do just that. But, standing around, calling
names, bad mouthing others choices and in general, throwing a fit
about what you can't or choose not to participate in, is just a
waste of time.<br>
<br>
Gregg Wonderly<br>
W5GGW<br>
<br>
On 1/9/2012 3:19 PM, Bradley Haney wrote:
<blockquote
cite="mid:CAPg-ThQd+BXp_jKn6_+x8o5N4n6arCoo3ShWJBLHcH_=ip9ZyQ@mail.gmail.com"
type="cite">Why not use already what we have.. ECHOLINK.. put as
many repeaters as we can on Echolink or (Allstar if it was more
user friendly to set up) and then with the use of APRS and AVRS ?
Seems to work very well from what I played with it. What
happens when the 1 dstar repeater in your area goes down? Lets
work on the technology that uses the equipment we have now.
<div>
<br>
<div>just my 1 cent worth.</div>
<div><br>
</div>
<div>kc9gqr<br>
<br>
<div class="gmail_quote">On Sun, Jan 8, 2012 at 11:25 PM,
Steve Kostecke <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:k0stk@arrl.net">k0stk@arrl.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Tom
Azlin N4ZPT said:<br>
<br>
>Make that IMBE for first generation P25. Still a DVSI
product.<br>
><br>
>Royalties - seems like a bunch of urban myths here.
The DVSI site says<br>
>no royalties or licensing fees for buying their
vocoders chips and<br>
>putting them in radios. see <a moz-do-not-send="true"
href="http://www.dvsinc.com/products/a2020.htm"
target="_blank">http://www.dvsinc.com/products/a2020.htm</a>
for<br>
>an example. I did not have to pay any royalty to buy
the AMBE vocoder<br>
>chips. something like $8 for surface mount and $18 for
DIP in volume. I<br>
>got mine for $23 each.<br>
><br>
>Might be royalties to build to APCO Project 25, DMR,
etc. standards. But<br>
>no royalties to build to the JARL standard or use an
AMBE vocoder seems<br>
>to me.<br>
<br>
What if DVSI decides to multiply the price per DIP by a
factor of 10?<br>
<br>
What if DVSI decides to not provide backwards compatibilty
in the next<br>
generation of AMBE?<br>
<br>
This mania for a mode which is hostage to one company
tells me that far<br>
to many people have not learned from our collective
experience with<br>
Microsoft. It's like watching moths circling a flame.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
73, Steve, K0STK // <a moz-do-not-send="true"
href="mailto:k0stk@arrl.net">k0stk@arrl.net</a><br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a moz-do-not-send="true"
href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<a moz-do-not-send="true"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig"
target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>