[aprssig] Fw: The final word on Shizzle
Robbie - WA9INF mwrobertson at comcast.netWed Apr 13 00:04:36 UTC 2005
- Previous message: [aprssig] Fw: The final word on Shizzle
- Next message: [aprssig] n1iic-3 IGate traffic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wes es group, I have always wondered how we can put any credence in analyzing what this path and that path does when you have to rely on "your" receiver to hear all the packets, and not know what was and was not involved in collisions and not decoded by you, but was decoded further out without any difficulty. These packets heard and decoded by others we have to assume and how do we know what was good or bad to say this worked, and this doesn't.. I've been amazed to hear some of the figures various people lay on us when trying to state a case in their favor, <G> There must be some way besides assumption? Sorry if above is not too clear to understand, sure some will... Hi Robbie Wes Johnston wrote: > Hmmm.... WIDE2-2 (2 hops) generated 172 packets, while W1-1,W2-2 (3 > hops) generated 121 packets. Perhaps fracticide played a role in this? > (ie all the home stations transmitted at once) or perhaps the packets > got out of range of the reciever sooner? > > Wes > > Tim Schall wrote: > >> >> >> WIDE2-2 172 PACKETS >> >> RELAY,WIDE2-1 217 PACKETS >> >> WIDE1-1,WIDE2-1 116 PACKETS >> >> RELAY,WIDE2-2 242 PACKETS >> >> WIDE1-1,WIDE2-2 121 PACKETS >> >> >> >> Clearly, preemptive digipeating and WIDE1-1 in the first slot help. A >> lot. Don’t know what we’ll do with this data but WHOOP! There it is! >> >> >> >> Tim Schall >> >> KA7PBI
- Previous message: [aprssig] Fw: The final word on Shizzle
- Next message: [aprssig] n1iic-3 IGate traffic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
