"Roger Barker" wrote in message
...
snip
Callsign substitution when using RELAY and WIDE is probably not the
norm.

Though not yet universal, callsign substitution is _quite_ common in my
area, where many are using Kantronics or PacComm TNCs.

K6HG-9*WIDE2-1S7RURP:'2]1l sk/]"3q}
K6HG-9WIDE2*S7RURP:'2]1l sk/]"3q}

What station is repeating this packet? I can't tell. What's supposed
to happen here?

These two packets were sent by a couple of high-elevation WIDEn-N
digipeaters on mountaintops ringing the SF Bay area.

There are two implementations of WIDEn-N -
snip
Mixing the two can result in misleading information.

NOID is far better for determining network topology, and is recommended.
This recommendation is by, not least of all, the Father of APRS, Bob WB4APR,
who worked with Kantronics to enable the WIDEn-N protocol in the first
place, and the guy whose idea WIDEn-N was.
http://www.dididahdahdidit.com/text/digis.txt (explanation)
http://www.dididahdahdidit.com/ (general APRS info)
Hope this helps.
73, Cap KE6AFE

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Cap" =3D=3D Cap Pennell writes:

Roger Callsign substitution when using RELAY and WIDE is probably not
Roger the norm.

Cap Though not yet universal, callsign substitution is _quite_ common
Cap in my area, where many are using Kantronics or PacComm TNCs.

[...]

Can you explain this behavior? I'm pretty sure the mobile station
doesn't have a WIDE alias.

KB5WIA*WIDE2-1APRS:$GPGLL,3759.519,N,12218.458,W,232104,A*3A
KB5WIA*WIDE2APRS:$GPGLL,3759.519,N,12218.458,W,2 32104,A*3A

Roger There are two implementations of WIDEn-N -

[...]

Roger Mixing the two can result in misleading information.

Cap NOID is far better for determining network topology, and is
Cap recommended. This recommendation is by, not least of all, the
Cap Father of APRS, Bob WB4APR, who worked with Kantronics to enable
Cap the WIDEn-N protocol in the first place, and the guy whose idea
Cap WIDEn-N was.

Bob asserts that it's more important to know where the station entered
the network in order to estimate the station's position. I'm not sure
I agree. However, I can get what I want by using TRACEn-N instead of
WIDEn-N, so all is good.

I have another question for you, Cap, which is slightly related to a
message you sent to a mailing list but which also probably interests
people outside that list. I would like to change my fixed home
station's routing from RELAY,WIDE (which is bad but works) to specific
stations. What is the best way to identify a good path? I'm hoping
for something more sophisticated than "listen for stations that
identify themselves as WIDE and that you can hear directly", but if
that's the right answer, that's good to know.

Jack.
=2D --=20
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/DQT5GPFSfAB/ezgRAurZAKDNBsCtEBbu3/8mXwJ4XyAzeCiMkgCfW9ui
LPI46wCJEgqmG36xQUMAdvM=3D
=3DRmFw
=2D----END PGP SIGNATURE-----

Uh... Is there an Idiots Guide to APRS? I recently got a Knwd D700, it's
really slick and I'm interested in learning more. I downloaded the spec and
looked over the digi paper referenced on Jeff's site @
http://www.dididahdahdidit.com/text/digis.txt over in Woodstock (I'm
nearby), but there is still many details assumed. It's all still over my
head except for hooking up the GPS and using it. I'd like to gain an
understanding of the basics. Should I understand packet first? A simple
glossary of terms would be a good thing. I may just try to corner Jeff.
--
'guards
..Steve K
.. ga 9
.. rb D
.. ag C
.. e I

--
[please clip quoted postings down to the relevant parts, thank you]

Steve N...Pardon my paranoia, but my email has no U's in it:






Cap Pennell wrote in message
...
"Roger Barker" wrote in message
...
snip
Callsign substitution when using RELAY and WIDE is probably not the
norm.

Though not yet universal, callsign substitution is _quite_ common in my
area, where many are using Kantronics or PacComm TNCs.

K6HG-9*WIDE2-1S7RURP:'2]1l sk/]"3q}
K6HG-9WIDE2*S7RURP:'2]1l sk/]"3q}

What station is repeating this packet? I can't tell. What's supposed
to happen here?

These two packets were sent by a couple of high-elevation WIDEn-N
digipeaters on mountaintops ringing the SF Bay area.

There are two implementations of WIDEn-N -
snip
Mixing the two can result in misleading information.

NOID is far better for determining network topology, and is recommended.
This recommendation is by, not least of all, the Father of APRS, Bob
WB4APR,
who worked with Kantronics to enable the WIDEn-N protocol in the first
place, and the guy whose idea WIDEn-N was.
http://www.dididahdahdidit.com/text/digis.txt (explanation)
http://www.dididahdahdidit.com/ (general APRS info)
Hope this helps.
73, Cap KE6AFE

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Cap" =3D=3D Cap Pennell writes:

Roger Callsign substitution when using RELAY and WIDE is probably not
Roger the norm.

Cap Though not yet universal, callsign substitution is _quite_ common
Cap in my area, where many are using Kantronics or PacComm TNCs.

[...]

Can you explain this behavior? I'm pretty sure the mobile station
doesn't have a WIDE alias.

KB5WIA*WIDE2-1APRS:$GPGLL,3759.519,N,12218.458,W,232104,A*3A
KB5WIA*WIDE2APRS:$GPGLL,3759.519,N,12218.458,W,2 32104,A*3A

Roger There are two implementations of WIDEn-N -

[...]

Roger Mixing the two can result in misleading information.

Cap NOID is far better for determining network topology, and is
Cap recommended. This recommendation is by, not least of all, the
Cap Father of APRS, Bob WB4APR, who worked with Kantronics to enable
Cap the WIDEn-N protocol in the first place, and the guy whose idea
Cap WIDEn-N was.

Bob asserts that it's more important to know where the station entered
the network in order to estimate the station's position. I'm not sure
I agree. However, I can get what I want by using TRACEn-N instead of
WIDEn-N, so all is good.

I have another question for you, Cap, which is slightly related to a
message you sent to a mailing list but which also probably interests
people outside that list. I would like to change my fixed home
station's routing from RELAY,WIDE (which is bad but works) to specific
stations. What is the best way to identify a good path? I'm hoping
for something more sophisticated than "listen for stations that
identify themselves as WIDE and that you can hear directly", but if
that's the right answer, that's good to know.

Jack.
=2D --=20
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/DQT5GPFSfAB/ezgRAurZAKDNBsCtEBbu3/8mXwJ4XyAzeCiMkgCfW9ui
LPI46wCJEgqmG36xQUMAdvM=3D
=3DRmFw
=2D----END PGP SIGNATURE-----

Uh... Is there an Idiots Guide to APRS? I recently got a Knwd D700, it's
really slick and I'm interested in learning more. I downloaded the spec and
looked over the digi paper referenced on Jeff's site @
http://www.dididahdahdidit.com/text/digis.txt over in Woodstock (I'm
nearby), but there is still many details assumed. It's all still over my
head except for hooking up the GPS and using it. I'd like to gain an
understanding of the basics. Should I understand packet first? A simple
glossary of terms would be a good thing. I may just try to corner Jeff.
--
'guards
..Steve K
.. ga 9
.. rb D
.. ag C
.. e I

--
[please clip quoted postings down to the relevant parts, thank you]

Steve N...Pardon my paranoia, but my email has no U's in it:






Cap Pennell wrote in message
...
"Roger Barker" wrote in message
...
snip
Callsign substitution when using RELAY and WIDE is probably not the
norm.

Though not yet universal, callsign substitution is _quite_ common in my
area, where many are using Kantronics or PacComm TNCs.

K6HG-9*WIDE2-1S7RURP:'2]1l sk/]"3q}
K6HG-9WIDE2*S7RURP:'2]1l sk/]"3q}

What station is repeating this packet? I can't tell. What's supposed
to happen here?

These two packets were sent by a couple of high-elevation WIDEn-N
digipeaters on mountaintops ringing the SF Bay area.

There are two implementations of WIDEn-N -
snip
Mixing the two can result in misleading information.

NOID is far better for determining network topology, and is recommended.
This recommendation is by, not least of all, the Father of APRS, Bob
WB4APR,
who worked with Kantronics to enable the WIDEn-N protocol in the first
place, and the guy whose idea WIDEn-N was.
http://www.dididahdahdidit.com/text/digis.txt (explanation)
http://www.dididahdahdidit.com/ (general APRS info)
Hope this helps.
73, Cap KE6AFE