Order Tray | Contact Us | Home | SIG Lists

[aprssig] I-80 Ohio/IN and D710 objects

Rich Garcia k4gpsc at gmail.com
Tue May 27 20:21:30 UTC 2008


I got to agree, a lot of wild ideas out there, some of them I do not believe
usefull and some are, this is one of them.
Drove 1200 miles the weekend before last with the D710 and testing out the
new firmware. A lot of objects out there, some would tune but most would
not. Some would key up but most would not so it was either a "paper
repeater" or the object did not include the proper, if any, tone code.

Over the entire trip I managed to have 2 QSO's both on repeaters that I was
aware of and pre-programed into the radio while my wife was driving earlyer
in the morning.

When it comes to repeater objects that can be probably the MOST useful thing
for visiting travelers but if it's a bogus repeater or not configured
correctly to use the TUNE feature don't even bother. I for one am not going
to be hunting down non-standard offsets or one of 32 PL tones while driving.
CTCSS decode is a nice feature but I find that most repeaters recently are
now blocking the input tone on the output. Shame..another useful feature out
the window and a nice feature to enable if you drive in an intermod plagued
area.

About 6 weeks ago I did a SC to NY/NJ run along the western portions of VA
and MD. I saw a lot of repeater objects but most of them were showing up to
200 miles away. During various parts of the trip I also heard a lot of
packets in some areas but was not digi'ed and the positions that I did
receive I could not figure out what alias the digi used. Dangerous work to
figure this out on a Kenwood while you are driving and unless you pull over
to figure it out by the time you do chances are you have left or will be
leaving the coverage area soon and need to hunt down the alias of the next
digi you reach. The two areas I remember right now that were difficult were
Blacksburg VA and Reading/Harrisburg PA. In the Blacksburg area one thing
that I noticed was one a few stations had a SUPER long TXDELAY, think one of
them had TXDIDDLE ON, probably a AEA TNC since I think only AEA had that
feature. It created for a really high traffic load for very little actual
traffic.

-----Original Message-----
From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Stephen H. Smith
Sent: Tuesday, May 27, 2008 3:48 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] I-80 Ohio/IN and D710 objects



This is just the digi announcing it's own presence.

What the discussion is about is having one of the beacon strings
announce the location of an open voice repeater repeater with coverage
approximately the same as the digipeater's.    Ideally this should be
beaconed on a direct path, or at maximum only one digi hop, and should
contain the repeater's location (coordinates so it will show on a map),
frequency and tone code (if any).


The idea to make travelers aware of the recommended voice repeater as
they pass through the coverage area of your digi,  when they are close
enough to actually hit it; not a hundred miles away.





--

Stephen H. Smith    wa8lmf (at) aol.com
EchoLink Node:      14400    [Think bottom of the 2M band]
Home Page:          http://wa8lmf.com  --OR--   http://wa8lmf.net

NEW!   World Digipeater Map
  http://wa8lmf.net/APRSmaps

JavAPRS Filter Port 14580 Guide
  http://wa8lmf.net/aprs/JAVaprsFilters.htm

"APRS 101"  Explanation of APRS Path Selection & Digipeating
  http://wa8lmf.net/DigiPaths

Updated "Rev H" APRS            http://wa8lmf.net/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





More information about the aprssig mailing list