Order Tray | Contact Us | Home | SIG Lists

[aprssig] Danger Will Robinson!

Wes Johnston, AI4PX wes at ai4px.com
Thu Jul 23 00:11:35 UTC 2009


After reading all of this, I have to ask.... Why are we doing this?  What's
wrong with letting the echolink operator send his own ID onto 144.39 with
his own TNC?   As much as I like neat / cool things, this seems like we are
going around our elbow to get to our nose.

Wes
---
Hitler gave great speeches too!


On Wed, Jul 22, 2009 at 17:56, Keith VE7GDH <ve7gdh at rac.ca> wrote:

> Jason KG4WSV wrote...
>
> IMO, this is something that should be handled at the local level, maybe
>> between the echolink node operator and the local Igate operator.
>>
>
> If the IGate operator (or anyone else close to the EchoLink node) generated
> a static object, it could go out on RF with a path of RFONLY and it wouldn't
> even make it to the APRS-IS. However, it would be a static object showing
> only the location, frequency, tone etc. and would not include the actual
> status of the node.
>
> In the case of IRLP nodes, the APRS status script (if installed by the
> owner) runs right on the node itself. It goes out every X minutes via a cron
> job, and whenever the node status changes. It's TCPIP only and up to someone
> (usually but not necessarily the IGate operator) to gate it to RF.
>
> 73 es cul - Keith VE7GDH
> --
> "I may be lost, but I know exactly where I am!"
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20090722/405ecbd1/attachment.htm>


More information about the aprssig mailing list