Order Tray | Contact Us | Home | SIG Lists

[aprssig] Funny path admission WAS:Why use this path?

Richard Montgomery kb4ytm at gmail.com
Tue Aug 30 23:30:59 UTC 2005


Something funny that I shouldnt admit to, but I will just for kicks. I 
sometimes see stations that are totally setup wrong like this for example:

callsign>WIDE4-4,APRS  text goes here

Part of me wants to send the guy a msg and say hey, you got the path 
setup wrong. But then part of me wants to let a sleeping dog lay because 
sure as the world I send the msg, it then starts going out like:

callsign>APRS,WIDE4-4   text goes here

So, its a dilemma. Correct the person and then live with a WIDE4-4 
(because it seems most users that I msg about paths never reduce, they 
just correct) or do I just keep it to myself?

Thought someone might relate to that,
Richard



Stephen H. Smith wrote:
> I have been monitoring 30 HF APRS for some time now from my QTH in 
> Pasadena, CA.  
>      http://wa8lmf.dyndns.org:14439    
> 
> is a UIview-generated display of what I am hearing using a horizontal 
> dipole made from two  30M  Hamstick mobile whips at about 20 feet AGL 
> connected to a Kenwood TS-50 and KAM-E TNC.    I have watching symbols 
> appear on the map for about a year now.  but just recently added 
> AGWmonitor to the setup so that I could see the raw packets behind the 
> symbols.  I was shocked at the percentage of clueless packets being 
> transmitted.
> 
> The strings below are as monitored in just the last few hours here. All 
> are cut and pasted from the AGWmonitor log for my KAM HF port :
> 
> 
> 
> 2:Fm K1PIG To ECHO Via N5NGN*,WIDE3-3,ECHO,GATE,WIDE3-3 <UI pid=F0 
> Len=30 >[18:48:35]
> <IGATE,MSG_CNT=218,LOC_CNT=92
> 
>     [[ The station discussed earlier monitored clear out on the west 
> coast!  An even more totally insane useless path!  At least the 
> incorrect use of WIDE3-3 on the HF side guarantees this packet will only 
> go one hop and never get a chance to abuse the VHF side....   ]]
> 
> 
> 
> 
> 2:Fm K7PW To APU25N Via APU25N,GATE,WIDE2-2,WIDE2-2 <UI pid=F0 Len=54 
>  >[18:53:56]
> =3301.96N/09708.77W&Flower Mound, TX Gateway {UIV32N}
> 
>       [[A digi with the call APU25N????    Fortunately this path is dead 
> on arrival and will never get a chance to abuse 4 hops on VHF!  This 
> stupid path just makes the packet longer and less likely to be received 
> at all.... ]]
> 
> 
> 
> 
>  2:Fm W1UP To APR867 Via WIDE,WIDE <UI pid=F0 Len=64 >[18:58:43]
> =4245.07n/07145.88W-PHG5230 Jim-Mason, N.H. - FN42cr - Icom 718
> 
>        [[ Another DOA packet with a totally useless path! ]]
> 
> 
>  
>  2:Fm VE4GN To APW272 Via ECHO <UI pid=F0 Len=21 >[19:03:03]
>  >210912 ve4gn at rac.ca
> 
>  2:Fm VE4GN To APW272 Via ECHO* <UI pid=F0 Len=21 >[19:03:07]
>  >210912 ve4gn at rac.ca
> 
>       [[ I heard this guy from central Canada direct here in southern 
> California, and then again moments later via a totally unneccessary HF 
> "ECHO" ]]
> 
> 
> 
> 
> 2:Fm WA9AWG To APU25H <UI pid=F0 Len=48 >[19:09:23]
>  >271207zwa9awg at hotmail.com Patronville, Indiana
> 
>        [[ At last someone with a clue about HF settings! ]]
> 
> 
> 
> 2:Fm K5RAV To ID Via GATE,WIDE <UI pid=F0 Len=42 >[19:57:04]
> K5RAV/R ECHO/D GATE/G K5RAV-1/B K5RAV-7/N
> 
>       [[ Huh???   ]]
> 
> 
> 
> 
> 
> 2:Fm KM5HG To APU24 Via ECHO,GATE,WIDE1-1 <UI pid=F0 Len=62 >[20:17:40]
> @300316z3615.56N/09542.20W_010/000g000t072r000p000P000b10093\
> 
>  2:Fm KM5HG To APU24 Via ECHO*,GATE,WIDE1-1 <UI pid=F0 Len=62 >[20:17:43]
> @300316z3615.56N/09542.20W_010/000g000t072r000p000P000b10093\
> 
>  2:Fm KM5HG To APU24 Via ECHO*,GATE,WIDE1-1 <UI pid=F0 Len=62 >[20:17:45]
> @300316z3615.56N/09542.20W_010/000g000t071r000p000P000b10093\
> 
>       [[ A demonstration of  HF channel abuse through unneccessary 
> digipeating!  The original beacon was heard direct over a path of 1000 
> miles!  Apparently two different HF "ECHO" digis repeated this packet 
> after the original direct transmission wasting THREE  time slots on the 
> low-capacity 300 baud HF channel.  ]]
> 
> 
> 
> 
> 2:Fm KF5ET-4 To APU25N Via WIDE1-1,WIDE2-2 <UI pid=F0 Len=30 >[23:30:09]
> <IGATE,MSG_CNT=218,LOC_CNT=78
> 
>        [[ Perfect compliance with the New Paradigm VHF path settings. 
> However it won't do squat on HF! ]]   
> 
> 
> 
> 2:Fm MISION To APN390 Via WIDE,GATE*,WIDE <UI pid=F0 Len=65 >[15:01:00]
> !4716.44NN12024.38W#PHG6860/WR7ADX WA MISSION RIDGE WX APRS WIDE
> 
> 
>        [[ I see this station from central Washington all the time on HF 
> producing a N-n green digi star on my HF map.  Apparently someone one 
> hop away on VHF is reverse-gating MISION's  VHF beacon onto HF where the 
> second WIDE then does nothing.   ]]
> 
> 
> 
> 
> 
> 
> 
> 
> Stephen H. Smith    wa8lmf (at) aol.com
> EchoLink Node:      14400    [Think bottom of the 2M band]
> Home Page:          http://wa8lmf.com
> 
> "APRS 101"  Explanation of APRS Path Selection & Digipeating
>   http://webs.lanset.com/wa8lmf/DigiPaths
> 
> Updated APRS Symbol Chart
>   http://webs.lanset.com/wa8lmf/miscinfo/APRS_Symbol_Chart.pdf   
> 
> New/Updated "Rev G" APRS     http://webs.lanset.com/wa8lmf/aprs
> Symbols Set for UI-View,
> UIpoint and APRSplus:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

-- 

APRS Traffic heard on 144.390 in Lexington, TN
http://richdea5.no-ip.org

Archived APRS traffic
http://richdea5.no-ip.org/usagehistory




More information about the aprssig mailing list