| |
ZL3AI > APRDIG 23.10.03 19:16l 304 Lines 11775 Bytes #999 (0) @ WW
BID : 2184-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 21, 1/6
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<DB0RES<DB0EEO<DB0GOS<ON0AR<ON0AR<VE3FJB<
JN1ZPJ<7M3TJZ<SP7MGD<ZL2TZE<ZL3VML
Sent: 031023/1233Z @:ZL3VML.#80.NZL.OC #:11029 [Chch-NZ] FBB7.00i $:2184-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Tuesday, October 21, 2003.
1. RE: run time a car battery....
2. aprsworld.net time is now in UTC
3. Re: Smart DIgis and the new Paradigm
4. Re: Mic-E hardware
5. RE: Isabelle objects???
6. RE: Mic-E hardware
7. Re: Smart DIgis and the new Paradigm
8. Re: run time a car battery....
9. Re: run time a car battery....
10. Re: Smart DIgis and the new Paradigm
11. Re: run time a car battery....
12. Re: run time a car battery....
13. Re: run time a car battery....
14. Re: run time a car battery....
15. Re: run time a car battery....
16. Re: run time a car battery....
17. Re: run time a car battery....
18. Re: run time a car battery....
19. Re: run time a car battery....
20. Re: run time a car battery....
21. Re: run time a car battery....
22. Re: run time a car battery....
23. Re: run time a car battery....
24. Re: run time a car battery....
25. Re: run time a car battery....
26. Re: run time a car battery....
27. Re: Smart DIgis and the new Paradigm
28. Re: Smart DIgis and the new Paradigm
29. Re: Smart DIgis and the new Paradigm
30. APRS Aliases, their past usage and "Smart Digipeating"
31. D7 on alkaline Batteries
32. Re: Smart DIgis and the new Paradigm
33. Re: Re: Smart DIgis and the new Paradigm
34. Re: run time a car battery....
35. Re: run time a car battery....
36. Re: run time a car battery....
37. Re: Smart DIgis and the new Paradigm
38. Re: APRS Aliases, their past usage and "Smart Digipeating"
39. Re: run time a car battery....
40. Re: D7 on alkaline Batteries
41. Re: Smart DIgis and the new Paradigm
42. Re: Smart DIgis and the new Paradigm
43. Re: APRS Aliases, their past usage and "Smart Digipeating"
44. Re: Re: run time a car battery....
----------------------------------------------------------------------
Subject: RE: run time a car battery....
From: "Herb Gerhardt" <hgerhardt@charter.net>
Date: Mon, 20 Oct 2003 21:01:48 -0700
X-Message-Number: 1
Sounds to me like you need a new car battery. Yours might be a bit on the
weak side.
I drive a GMC Jimmy diesel which has dual batteries and I leave my tracker
running when I go backpacking for two to four days at a time. So far, knock
on wood, I have never had a battery problem on my return. I set my D700 to
transmit every 30 minutes and use the lowest power setting I can and still
hit a digi but I have left it for 3 days on High power and still not had a
problem. I also set my D700 to act as my personal digi by only responding
to UVC so I can use it from my camp with my D7 if I can't get out any other
way.
I also replace my batteries at the first sign of weakness. That means I
never run them for as long as the warranty is for and replace them as soon
as the starter sounds sluggish while starting the truck. Batteries are
cheap compared to not being able to start my truck at the locations where I
park at in the mountains. They are usually a long ways from anywhere and no
one around to give you a jump!
Herb, KB7UVC
NW APRS Group, West Sound Coordinator
Our WEB Site: www.nwaprs.org
>-----Original Message-----
>
>For those who may be interested, a kenwood d700 and garmin 162
>gps will run
>for 31 hours beaconing every 30 minutes before exhausting a car
>battery. Always fun to learn such things on a monday morning.
----------------------------------------------------------------------
Subject: aprsworld.net time is now in UTC
From: James Jefferson <jj@aprsworld.net>
Date: Mon, 20 Oct 2003 23:36:14 -0500
X-Message-Number: 2
Dear group,
I changed db.aprsworld.net and maps.aprsworld.net's clocks to UTC time. Good
ridance to CDT.
-Jim KB0THN
----------------------------------------------------------------------
Subject: Re: Smart DIgis and the new Paradigm
From: "Bill Vodall WA7NWP" <wa7nwp@jnos.org>
Date: Mon, 20 Oct 2003 21:52:02 -0700
X-Message-Number: 3
>I may want my packet to NOT use smartdigi paths and still get to the
>internet. You are right that 90% of the mobile trackers (the only ones
>who should be using RELAY) just wanna get to the internet.
>
>My concern all along was that we'd break the network and hem ourselves into
>a corner so that I couldn't get "from here to there" via RF in an
>emergency. I'm really surprised that no one else chimed in on this
>thread... I guess they're all "power poled out".
>
>Wes
Everybody is out in the garage replacing their power connectors... :)
This whole discussion seems to take the simple concept of pseudo
aliases and complicate it.
If you want to use the old system, use it.
If you want lots of "local" packets, send it to RELAY or RELAY,LOCAL
If you want to cover your region, send it to RELAY,REGION
If you want to cover the extended region (hopefully on an infrequent
basis), send it to RELAY,WORLD
If you want to get it to the get it to the IGATE, use RELAY,IGATE.
Smart digi's would handle the appropriate translations for the
local area. No need to ever change any, difficult to change, burned
in configuration. (I'd be using pseudo aliases personally right now
if it wasn't burned in and a bit of a hassle to change.)
The idea of an assumed path for a simple RELAY packet is new and
potentially very usefully, but it's certainly not something we want to
tie to APRS-IS. There's already too much dependency on Internet
functionality and not enough done with RF. Let's at least get things
working so digi's are smart enough to not resend the same packet
multiple times. That's not much to ask.
73,
Bill - WA7NWP
----------------------------------------------------------------------
Subject: Re: Mic-E hardware
From: WA8LMF2@aol.com
Date: Tue, 21 Oct 2003 01:22:22 EDT
X-Message-Number: 4
In a message dated 10/20/2003 12:29:53 PM Eastern Daylight Time,
scott@opentrac.org writes:
>When the TT3 is used for Mic-E (with external PTT input), does it still
>automatically beacon? I've never used it in this mode. Might be useful if
>a pilot went down and wasn't able to transmit manually.
It's one or the other (Mic-E or autobeaconing). Since you can setup two
configurations with totally different parameters for the two, you can have
Mic-E in one configuration and autobeaconing on the other. I have mine
setup with three-position center-off DPDT toggle switches. One pole turns
on power on either side of center, while the other pole selects Mode 1 or
Mode 2. One issue is that Mic-E is typically used on a non-APRS (voice)
chanel while autobeaconing is usually done on 144.39.
What radio would you be using with a TinyTrak on a glider. Of course the
THD7 already has Mic-E and automode beaconing built-in -- you wouldn't a TT
with it.
Stephen H. Smith wa8lmf (at) aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
Subject: RE: Isabelle objects???
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Tue, 21 Oct 2003 06:30:15 -0500
X-Message-Number: 5
VE2DWE>WIDE3-3,VE2REY-3*,TRACE3-2,qAr,VE2MGJ:;ISABE_upd*180222z3130.00N\
07336.00W@.../012/HC/091^.../0955>099&273%...{HNcA
Looks like VE2DWE is broadcasting this one to RF.
73,
Pete Loveall AE5PL
pete@ae5pl.net
>-----Original Message-----
>From: bounce-aprssig-19826@lists.tapr.org
>Jacob Tennant
>Posted At: Monday, October 20, 2003 10:42 PM
>Subject: [aprssig] Isabelle objects???
>
>Why is there still position objects for ISABELLE still floating around
>on the inet feed???
----------------------------------------------------------------------
Subject: RE: Mic-E hardware
From: "Scott Miller" <scott@3xf.com>
Date: Tue, 21 Oct 2003 07:10:36 -0700
X-Message-Number: 6
>What radio would you be using with a TinyTrak on a glider. Of course the
You see a little bit of everything in use... anything that's reasonably
compact. The point is that many of the pilots already have the radios, and
have them wired to PTTs in their flight helmet. They could have APRS
capability for very little investment in hardware.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Smart DIgis and the new Paradigm
From: Wes Johnston <wes@johnston.net>
Date: Tue, 21 Oct 2003 10:24:20 -0400
X-Message-Number: 7
Starting fresh.... I thought about this last night and assuming that we
do take off and run with use of RELAY implying that a smart digi can alter
my path to something specific to get to an igate.... Examples 1&2 work....
the nearest digipeater is a "smart digi". Examples 3&4 fail when the
nearest digi is a normal "WIDEn-n" digi.
---------------------------------------------------------------------
Example 1: There is a smart digi serving my local area and it can hear all
local relay stations.
kd4rdb>aprs v RELAY,WIDE2-2:$GPRMC.........
someone's RELAY station hears the packet and digipeats it for me.
kd4rdb>aprs v RELAY*,WIDE2-2:$GPRMC.........
The smart digi hears this packet and reroutes it to the local IGATE by
inserting a call-specific path...
kd4rdb>aprs v digi1,digi2,digi3,digi4:$GPRMC.........
---------------------------------------------------------------------
Example 2: There is a smart digi serving my local area and I happen to hit
it direct.
kd4rdb>aprs v RELAY,WIDE2-2:$GPRMC.........
The smart digi hears this packet and reroutes it to the local IGATE by
inserting a call-specific path...
kd4rdb>aprs v digi1,digi2,digi3,digi4:$GPRMC.........
---------------------------------------------------------------------
Example 3: Let's say that I am a mobile tracker and I send a packet as I
pass by a RELAY station. There is a smart digi in the next town, my local
wide digi is an ordinary WIDEn-n digi....(with noid of course)
kd4rdb>aprs v RELAY,WIDE2-2:$GPRMC.........
The relay station digipeats me
kd4rdb>aprs v RELAY*,WIDE2-2:$GPRMC.........
the local smart digi hears me and digipeats me - of course it also replaces
the word RELAY with it's callsign.
kd4rdb>aprs v n4digi,WIDE2-1:$GPRMC.........
Now a smart digi hears my packet, but does not alter my path because it
doesn't know the word RELAY was ever in the path.
---------------------------------------------------------------------
Example 4:I am a mobile tracker in the vicinity of a WIDEn-n digipeater and
hit it direct.... There is a smart digi in the next town, my local wide
digi is an ordinary WIDEn-n digi....(with noid of course)
kd4rdb>aprs v RELAY,WIDE2-2:$GPRMC.........
The relay station digipeats me
kd4rdb>aprs v digi1*,WIDE2-2:$GPRMC.........
Now a smart digi hears my packet, but does not alter my path because it
doesn't know the word RELAY was ever in the path.
---------------------------------------------------------------------
The new system is not compatible with our existing WIDEn-n digipeaters due
to callsign substitution issues. The problem were running into here is
that we are loosing consistency... sorry, but I'm back to thinking we're
breaking the system. 100% of these examples would work if we'd just added
the alias IGATE after the RELAY,WIDE instead of using RELAY as the litmus
test for a user's willingness to have his path altered by the network. Of
course that still leaves the issue of 90% of the people simply wanting to
get to an IGATE and making 90% of the people alter their paths to include
the word IGATE. :-( It's a shame that we will end up (likely) using an
extra callsign (7 bytes) to indicate our desire to have our packet
dynamically routed.... I guess there's always open trac.
Wes
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
