How do we get these objects out on 2m? (from the perspective of igate operator) I certainly don't want to igate all echolink nodes onto my local lan, and I can't possibly know the number(s) of all the echolink nodes that may pop up in my vicinity<br clear="all">
Wes<br>---<br>Hitler gave great speeches too!<br><br><br>
<div class="gmail_quote">On Wed, Jul 22, 2009 at 16:23, Robert Bruninga <span dir="ltr"><<a href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Lynn,<br><br>Great work!<br>I have only been trying to get this for the last half dozen<br>years or so.<br>
I have been badgering Jonathan (Echolink author) for years, but<br>apparently I had not realized that he had finished his half<br>(getting Posit data centralized). It is so great that you have<br>jumped in with the missing link.<br>
<div class="im"><br>> Done. Check out the current proposed objects at<br>> <a href="http://ldeffenb.dnsalias.net/EchoLink.txt" target="_blank">http://ldeffenb.dnsalias.net/EchoLink.txt</a>.<br><br></div>1) However, I agree with Steve, that you should not use the<br>
EchoLink callsign as the AX.25 FROM address, since it will<br>conflict with that same station's HOME or other APRS station -0<br>and violate the principle of ownership or common expectations.<br>Besides it will also be wasting space in the APRS radio display<br>
by having the Echolink callsign in TWO places on the display<br>when this is actually a minor bit of info.<br><br>I recommend that you make ALL of these objects be originated by<br>your callsign... Something like KE4ERJ-EL. Notice that a non<br>
1-15 SSID can be used, since this is being directly injected and<br>does not have to go through a TNC. Then everything works as<br>desired, plus we get to see the real source of this data<br>KE4ERJ-EL and not some person's call who has no idea how it got<br>
to APRS.<br><br><br>2) PHG data:<br>
<div class="im">> It only uses PHG if the frequency doesn't<br>> adhere to the valid ones listed in<br></div>> <a href="http://aprs.org/info/freqspec.txt." target="_blank">http://aprs.org/info/freqspec.txt.</a>..<br>
<br>PHG should not be included in these objects in any case. As I<br>explained before, when displayed on a D700 (the primary target<br>screen for these objects) the PHG data will not be parsed, but<br>will show up as TEXT "PHGxxxx" pushing the other useful<br>
information another 8 characters off the screen. SO do not<br>include PHG in any case.<br><br>3)<br>
<div class="im">> Any "invalid" frequency will still be included in<br>> the status text, but only in its owner-specified<br>> format, not in a normalized FREQ object.<br><br></div>Actually, I would rather see all non-standard entries DUMPED to<br>
a NEEDS-FIXING file that we can send to Echolink and get the<br>originators to fix the problems at the source.<br><br>4) I see lots of these showing [offline] in the text, yet they<br>all show a different % status byte. And none of the ones listed<br>
showed the . Offline status?<br><br><br>5) Do you see anything that we need to feedback to the Echolink<br>Author as a global change that would help force his users into<br>entering correct data?<br><br>Thanks<br>Bob, WB4APR<br>
<div class="im"><br>>>> The only mod I'd make is that the source<br>>>> call be the station's call.<br><br></div>No, as per above.<br>Bob<br>
<div>
<div></div>
<div class="h5"><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br>