OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRS     29.10.00 15:47l 199 Lines 7389 Bytes #999 (0) @ WW
BID : 34173_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 26, 2/9
Path: DB0MRW<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<HI8GN<KP4IG<7M3TJZ<IK1ZNW<
      VE1DRG<WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/1110Z @:ZL3VML.#80.NZL.OC #:45153 [Chch-NZ] FBB7.00g25 $:34173_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRS@WW


intermittent after two Socal summers of smog, ozone and baking in the car. 
Normally not a problem since the machine (which is my dedicated GPS map 
machine) boots and autoruns Street Atlas from a cold start. Mostly I use the 
touch pad. 

Actually the 3000 works better than some of the newer laptops I have tried. 
The power management system on it actually works!  When the display blanks 
from inactivity or closing the lid and the machine throttles down to low 
power mode, the machine actually wakes up again properly when you lift the 
lid.  I frequently close the lid when I park and lift it again when I return. 
 A single boot of Win98SE and SA8 has been running continously for over two 
weeks with numerous suspensions and wake ups. (I have a 20A 12 VDC switching 
power supply bridged across the battery. When I park at home or the office I 
plug it in and keep all the mobile gear including the D700 beacons running 
all day and all night.)

The machine is velcroed to a steel table top mounted to the floor of the car. 
See my ham page at:
   http://members.aol.com/wa8lmf/ham 

for pics of the assembly.

Stephen H. Smith         
Email:            wa8lmf@aol.com      
Homepage:        http://members.aol.com/wa8lmf
------------------------------------------------------------------------------

----------
|    Radio Communications Systems       Personal Computers
|                Consulting and Systems Integration
|    GPS Custom Mapping    &     Radio Coverage Surveys
|    File Conversions       MS-Windows Setups   
|-----------------------------------------------------------------------------

------------

----------------------------------------------------------------------

Subject: Re: Not-so-smart Digipeating?
From: "Valentino Sarro, VE6SZR" <sarrov@home.com>
Date: Thu, 26 Oct 2000 02:12:43 -0600
X-Message-Number: 7



Ralph Milnes wrote:

>
> So with a WIDE,WIDE, the packet from A would be digid by B and C (dupes),
> and then D and E (via C). Stations within range of D and E WILL hear A's
> packet.
>
> But with WIDE2-2, the packet is digid by B, then C, and then dies. Stations
> within range of  D and E WON'T hear A's packet.
>
> Wrong?
>

I'd say that on paper you've got the right idea.....however sometimes the real
world can produce something different......there is one more scenario......

You mentioned that A can reach B and C, and in your example you make the
suggestion
that B digipeats first... a WIDE2-1 (which was decremented from our original
WIDE2-2)......however it stands to reason that C is also hearing station A's
original packet, therefore sure it may wait for B to digi first, but it may
stillact on that original signal from A and duplicate B's WIDE2-1.....and
therefore pass
the same packet on to the rest of the network.

Therefore to summarize....the smart (WIDEn-n) digis merely prevent duplicating a
packet THEY ALREADY  DIGIed ONCE BEFORE......we cannot make assumptions that
theywill follow a set order. Does this make sense?

73, Tino.
Calgary, Alberta



>
> 73,
>
> Ralph, KC2RLM
>
> ---
> You are currently subscribed to aprssig as: sarrov@home.com
> To unsubscribe send a blank email to leave-aprssig-18700I@lists.tapr.org
> Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org


----------------------------------------------------------------------

Subject: Re: [Fwd: RE: Next Layer of Standards]
From: Alex <kg4ecv@amsat.org>
Date: Thu, 26 Oct 2000 09:27:22 -0400
X-Message-Number: 8

Hi Bill,

Bill Diaz wrote:
>
> Alex,
>
> I believe that propagation delays < 1 minute would be acceptable and would
> result in a big improvement in Time accuarcy. This would eliminate or greatly
> reduce the timestamp problem experienced with Mic-E packets.

I guess it depends on what coverage we have in mind. Personally I would
like to concentrate on local areas, say a 1 or 2 digi coverage, mostly
because the chances drop pretty dramatically with every digi in the path
which makes the issue of dropped packets greater than the propagation
delay. 

What I'm trying to say I guess is that one can easely cover an area of
10+ digis within a minute, but the chances that that particular packet
makes it is very slim. So perhaps propagation delay is not that much of
an issue. I'm just thinking out loud here, so if it sounds like garbage
what I'm saying, it probably is. :)

> A mechanism must be put in place to ensure that only current time records
would> be accepted.

That's probably the hard part. Perhaps we could include something like a
packet lifetime in the time sync message? Say a counter that represents
a maximum acceptable delay and at every digi/hop the counter gets
subtracted with a value representing the delay this particular hop
introduces. If the counter would reach zero, the packet gets dropped.
This way a client application would also be able to set a value
representing the maximum delay it accepts and compares the counter value
in the packet against it to see wether or not to accept the time sync
packet.

> If any APRS station could send a time message/record we could not rely on the
> accuracy.

Perhaps one could define in the client application from which source you
are willing to accept these time sync packets. For instance, if you know
that your local digi transmits a reliable time sync signal, set your
client application so to only accept these packets from that source.

> Time messages or record transmissions could be generated periodically, and
only> after successfully obtaining a time update from a time server.
>  Consideration
> could also be given to including a timestamp record when an APRS client
> application logs onto a server.

Perhaps this would go a bit far what I'm saying.....but maybe one could
include a flag in any packet containing time information (I don't mean
just the time sync packet but any packet carrying a time value)
indicating wether or not the originator syncs its time to a time server.
This way the recipient of a packet with time information would at least
have some indication about the reliability of the included time
information.

>
> Bill KC9XG


73s,
Alex

----------------------------------------------------------------------

Subject: Re: [Fwd: RE: Next Layer of Standards]
From: Alex <kg4ecv@amsat.org>
Date: Thu, 26 Oct 2000 09:43:46 -0400
X-Message-Number: 9

Hi Bob,

Bob Bruninga wrote:
>
> Huhh?  The 144.39 channel abounds with NMEA GPS data.  Its there for the
> taking.  All APRS programs are capable of synchrnoizing to these existing
> signals.  Yes, the software must be smart enough to filter out the BAD
> data, but this is easy to do.  This will get to within a second or so.

I thought I read on here before that there was an application already
doing this, though I might be confused with some mapping software.

> Even better timing is possible with smarter software.  THe minimum delay
> through a TNC direct is X+T+D+R where X is the delay throgh the TNC, T is
> the TXD delay, D is the unknown CD delay due to a busy channel and R is
> the delay in your receiving/decoding system.
>
> Through one hop is X+T+D+R+X+T+D+R etc...

In an earlier message I was thinking of some counter within the time
sync packet that takes these delays into account. I just realized that
one could also lower the counter if a digi does not hear the packet





Read previous mail | Read next mail


 17.11.2026 08:12:31lGo back Go up