[aprssig] KPC2 like a fill in digi

[Lynn W. Deffenbaugh (Mr)]

You might want to join the TinyTrak4 Yahoo group 
(http://groups.yahoo.com/group/TinyTrak4/) and ask over there.

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

On 3/28/2012 3:01 PM, Eduardo Gomez López wrote:
> Thanks again, so what is the best configuration of the tiny4 for the
> new paradigm widen-N? We have two tiny4 and we want to put as wide
> digi. Right now we have a wide digi with digi_ned running and now we
> want put this new digis to help it. Is very important for us, our
> group is starting in the design of the net here in Bogota, Colombia,
> so is very important to us your help. Thank you very much and see you
> soon at APRS.fi
>
> 73,
> HK3PQI
> Ex- HK6PQI
>
>
> Eduardo Gómez L.
> Editor conceptual de entretenimiento
> Caracol Televisión
>
> El 27/03/2012, a las 12:50 p.m., Tom Hayward<esarfl at gmail.com>  escribió:
>
>> I am not very familiar with the TinyTrak4, but yes, it does advertise
>> callsign substitution. It can be programmed as a WIDEn-N digi. I do
>> not know how to program it as a WIDE1-1 fill-in.
>>
>> I am more familiar with the Tracker2 (recently replaced by Tracker3).
>> The Tracker2 also supports WIDEn-N and callsign substitution. To
>> program it as a WIDE1-1 fill-in, set the digipeat alias to WIDE1 and
>> hop-limit to 1.
>>
>> The KPC3+, D700, and D710 also support callsign substitution
>> (depending on how they are programmed).
>>
>> This article describes how different TNCs may be programmed as fill-in
>> digipeaters:
>> http://www.aprs.org/newN/WIDE1-1settings.txt
>>
>>
>> Tom KD7LXL
>>
>> On Tue, Mar 27, 2012 at 11:16, Eduardo Gomez Lopez<edogl78 at gmail.com>  wrote:
>>> Thank you so much, this is a grate answer, lol, in this case is more
>>> "smart" the tinytrak4 because it has alias substitution? But only
>>> works like a fill in digi right? Never like a wide digi. I'm in the
>>> correct way?
>>>
>>> Thanks a lot
>>>
>>> HK6PQI
>>>
>>>
>>> Eduardo Gómez L.
>>> Editor conceptual de entretenimiento
>>> Caracol Televisión
>>>
>>> El 27/03/2012, a las 12:04 p.m., Tom Hayward<esarfl at gmail.com>  escribió:
>>>
>>>> For aprs.fi to accurately determine the path of a packet, each
>>>> digipeater must support callsign substitution. When you use the UIDIGI
>>>> command found in more sophisticated digipeater software, the
>>>> digipeater callsign is inserted into the path when it digipeats the
>>>> packet.
>>>>
>>>> If your TNC supports UIDIGI, you would program it like this:
>>>> UIDIGI ON WIDE1-1
>>>>
>>>> And then it would mark packets like this:
>>>> in: KD7LXL>APRS,WIDE1-1:
>>>> out: KD7LXL>APRS,5K3PRS-3,WIDE1*:
>>>>
>>>> The KPC2 does not have the UIDIGI command. The alternative is to use
>>>> the MYALIAS command instead. When the above packet is digipeated with
>>>> the MYALIAS function, it will look like this:
>>>>
>>>> KD7LXL>APRS,WIDE1-1*:
>>>>
>>>> Your KPC2 does not leave any information that 5K3PRS-3 digipeated the
>>>> packet! aprs.fi does not know who digipeated the packet, so it does
>>>> not draw a line.
>>>>
>>>>
>>>> Tom KD7LXL
>>>>
>>>> On Tue, Mar 27, 2012 at 09:51, Eduardo Gomez Lopez<edogl78 at gmail.com>  wrote:
>>>>> Yes, my digi is configured like that:
>>>>>
>>>>> Mycall 5K3PRS-3 (is the unique)
>>>>> Myalias WIDE1-1
>>>>> Digi on
>>>>> Btext !0000.00N/00000.00W#W1-1 APRS HK (with the correct location)
>>>>> Beacon every 30
>>>>> Unproto APNK80 (like kantronics kam 8.0) without via
>>>>>
>>>>> What setup I need more?
>>>>>
>>>>>
>>>>> Eduardo Gómez L.
>>>>> Editor conceptual de entretenimiento
>>>>> Caracol Televisión
>>>>>
>>>>> El 27/03/2012, a las 10:46 a.m., Lawrence LaBranche
>>>>> <Capdiamont at yahoo.com>  escribió:
>>>>>
>>>>>> Did you use different SSID on all your devices? Is your digi sending a position report?
>>>>>>
>>>>>> KI6ZQY
>>>>>>
>>>>>> Sent from my iPod
>>>>>>
>>>>>> On Mar 27, 2012, at 8:36 AM, Eduardo Gomez Lopez<edogl78 at gmail.com>  wrote:
>>>>>>
>>>>>>> Hi, I have some problem with a KPC2 TNC because I want to put it as a
>>>>>>> fill in digi WIDE1-1. It is working very well but in APRS.fi does not
>>>>>>> "draw" the Path that this digi is retransmitting.
>>>>>>>
>>>>>>> In APRS.fi shows like my car send the frame direct to the igate, not
>>>>>>> through the digi. Why happen that? Can i do something to exist in the
>>>>>>> graphics? Right now my digi is like a ghost
>>>>>>>
>>>>>>> Sorry about my English. Speak Spanish
>>>>>>>
>>>>>>>
>>>>>>> Eduardo Gómez L.
>>>>>>> Editor conceptual de entretenimiento
>>>>>>> Caracol Televisión
>>>>>>> HK6PQI
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aprssig mailing list
>>>>>>> aprssig at tapr.org
>>>>>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>>>>> _______________________________________________
>>>>>> aprssig mailing list
>>>>>> aprssig at tapr.org
>>>>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>>>> _______________________________________________
>>>>> aprssig mailing list
>>>>> aprssig at tapr.org
>>>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>>> _______________________________________________
>>>> aprssig mailing list
>>>> aprssig at tapr.org
>>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>> _______________________________________________
>>> aprssig mailing list
>>> aprssig at tapr.org
>>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>