Order Tray | Contact Us | Home | SIG Lists

[aprssig] objects not being released

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Sun Jan 1 23:56:00 UTC 2012

You'll find that many object originators and/or injectors are just as 
dumb as dumb trackers.  They transmit their objects without listening to 
any channel to see if anyone wants to change them.  This is true for 
WinLink, D-Star (I think), some IRLP/EchoLink status objects (local 
script generated) and certainly any and all objects coded into TNC 
settings at remote digipeater sites.

The object adoption portion of the spec is greatly targeted to manually 
initiated local objects like those created and moved around like 
checkers on a checker-board during APRS-supported events.  Long term 
and/or canned information objects are really hard to get changed unless 
you're already in control of the station originating them.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/1/2012 2:42 PM, Andre wrote:
> Op 1-1-2012 20:06, John Habbinga schreef:
>> I'm confused.  When you connect your gateway to a winlink.org server
>> it creates an object and sends it to the APRS-IS.  You believe that
>> the object contains incorrect information, so you adopt it with
>> UI-View32, change it and retransmit that object back to the APRS-IS,
>> or on the APRS channel?
>> I would expect that it would be overwritten the next time the
>> winlink.org server transmits another object.
> Per the specs the WINLINK station, nobody even knows for sure it is 
> actualy from winlink org, should stop transmitting the object untill 
> it gets updated with new information.
> Because the WINLINK station is connected to the APRS-IS it should not 
> even matter if it is transmitted on the aprs channel or APRS-IS.
> Apperatly the WINLINK station does not follow the specs or it does not 
> listen, maybe disconnects between transmitting the objects, who knows, 
> we don't even know who to contact to get the wrong info (wrong 
> software info in this case) corrected. We do know that the right info 
> is on the winlink.org site so it is not a configuration error.
> 73 Andre PE1RDW
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

More information about the aprssig mailing list