[aprssig] TT4 Config for High Altitude Balloon
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Sun Apr 8 21:48:01 CDT 2012
There's a bug apparently in the Tracker2 (IIRC) digipeater code that
will do as you describe with a WIDE2, but in fact, if you think of the
WIDEN-n as the "n" meaning how many hops are "left", then a -0 (implied
by WIDE2) should in fact have been marked used by whatever created it.
WIDE2-1 requests a single hop from a WIDE2 digipeater by what I've seen
described. If WIDE2 works, then I'd personally call it a bug, not a feature.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 4/8/2012 9:04 PM, John Gorkos wrote:
> I may have a fundamental misunderstanding of the WIDEN-n paradigm, then.
> I thought that a digi configured for WIDEN-n would see a WIDE2 packet as
> an undigipeated WIDE2-0, and would then digipeat it and either mark the
> WIDE2 as used (WIDE2*) or insert its own call in the digi path, and remove
> WIDE2 altogether. Is the SSID of 1 essential to having a WIDEN-n digi
> pick it up, or is it enough that the WIDE2 with an SSID of 0 be there? Do
> different DIGIs treat this differently (I.e. Do soft digis like APRSX and
> DigiNED act differently than KPC3?
> John Gorkos
> On 4/8/12 8:42 PM, "Lynn W. Deffenbaugh (Mr)"<ldeffenb at homeside.to> wrote:
>> On 4/8/2012 8:27 PM, John Gorkos wrote:
>>> Digi path should just be WIDE2 (next flight, we'll have a more
>>> intelligent controller with altitude-variable digi paths).
>> In most areas, WIDE2 isn't going to get you any digipeats, not that a
>> balloon above N,000 feet needs it. At most by popular recommendations,
>> the path should be WIDE2-1.
>> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig