<html>
<body>
Good point on having everything at one site. Its convenient,
though, because its a nice site where we could get the antenna up
high.<br><br>
<br>
At 09:39 PM 08/24/08, you wrote:<br>
<blockquote type=cite class=cite cite=""><font size=2>I wonder about
putting all our eggs into one "KAGE" basket. If we lose the
KAGE site, we would then lose all of our infrastructure. Seems a bit
fragile to me, if a storm takes down that tower. I think the digital and
analog infrastructures should be independent and should be linked only
through the internet or the "ether."<br>
</font> <br>
<font size=2>I think we can develop our own server software. It's our
call as to whether we use what ICOM has to offer. There doesn't seem to
be the same licensing issue...That is, if we want to write our own we can
do so in accordance with the D-Star specification. I don't know what
routines are available from ICOM and what or how we might duplicate them.
Those are questions that we might want to answer, however.<br>
</font> <br>
<font size=2>Then it might simply be a case of where we want to invest
our time rather than what legal constraints there might be.<br>
</font> <br>
<font size=2>-Les<br>
</font> <br>
<dl>
<dd>----- Original Message ----- <br>
<dd>From:</b> <a href="mailto:ewbrom@hbci.com">Erik Brom</a> <br>
<dd>To:</b> <a href="mailto:warc@lists.w0ne.org">warc@lists.w0ne.org</a>
<br>
<dd>Sent:</b> Saturday, August 23, 2008 10:12 PM<br>
<dd>Subject:</b> [WARC] D-Star<br><br>
<dd><font size=2>After Les's presentation Thursday, and remembering back
to an early D-Star ad, I wondered if we could put a 1296 D-Star digital
node at the KAGE site, and then interconnect it with D-Star Analog
repeater modules (which I thought I remembered seeing). So we
could continue to run our existing FM systems, but interconnect them with
the digital network.<br><br>
<dd>Doing some surfing now, I was unable to turn up any D-Star analog
repeater hardware, so its apparently not possible.<br><br>
<dd>I came across some other things though, such as references to
proprietary software available (only) from Icom, the codec issue of
course, and a single central server system that manages the linking
between systems. <br><br>
<dd>All of this really bothers me, as not being "The Amateur
Way". It sounds to me more like we are buying a commercial
system from a single manufacturer. Contrast this to APRS. The
*protocol* is published, and there are a bunch of manufactures of
hardware and software that support it, and lots of ways hams can set up
new ways of using it. <br><br>
<dd>Although the technology and capabilities of D-star sound cool,
something just isn't sitting right with me. Am I right or
wrong? Can someone give me a better "warm & fuzzy"
feeling about this?<br><br>
<dd>Erik<br>
</font><br>
<dd><pre>No virus found in this incoming message.
<dd>Checked by AVG -
<a href="http://www.avg.com/" eudora="autourl">http://www.avg.com</a>
<dd>Version: 8.0.138 / Virus Database: 270.6.7/1631 - Release Date:
8/24/2008 12:15 PM
</pre><font face="Courier New, Courier"><hr>
</font>
<dd>_______________________________________________<br>
<dd>WARC mailing list<br>
<dd>WARC@lists.w0ne.org<br>
<dd>
<a href="http://lists.w0ne.org/cgi-bin/mailman/listinfo/warc" eudora="autourl">
http://lists.w0ne.org/cgi-bin/mailman/listinfo/warc</a><br><br>
</dl>_______________________________________________<br>
WARC mailing list<br>
WARC@lists.w0ne.org<br>
<a href="http://lists.w0ne.org/cgi-bin/mailman/listinfo/warc" eudora="autourl">
http://lists.w0ne.org/cgi-bin/mailman/listinfo/warc</a></blockquote>
</body>
</html>