<html>
<body>
The "extra" tx delay is not cumulative unless the TX delay is
on each station.<br>
Example(Yours) has an extra 300ms, but each of the digi's only have 5ms,
the 27 hops are (27 x 5) + 300<br><br>
BUT,<br>
I do believe long term if we did "compressed bunching" we could
save a LOT of time!!!!!<br><br>
Couple this with digi's that only transmit based upon DISTANCE / change
in information and available bandwidth, and then
"bunch/compress" all the output into one burst would be much
more efficient..<br><br>
Mark Cheavens<br>
KC5EVE<br><br>
At 04:19 PM 12/7/2010, you wrote:<br>
<blockquote type=cite class=cite cite="">Hallelujah!!! <br><br>
It's bad enough that the average appliance operator never set's his TXD,
but the digi owners sure should. Think about it this way.... I tx a
packet with a bad TXD. Let's say it costs an extra 300ms. Now
my packet goes out 3 hops, potentially hitting 27 digipeaters (yeah, it's
a worst/best case). 300ms x 27 is 8.1 seconds of on air time wasted
just with the digipeaters. It may not sound like much, but think
how many times your local digipeater TX's every day.<br><br>
Is it time to start talking about queueing packets for 10 or 20 seconds
again??? <ducking> Seriously, it can be done with a simple
timer on the ext-CD input. You just hold that input active for
10/20 seconds and let it drop for one second. Rinse Lather
Repeat. The digi then uses ONE txdelay to transmit several
packets. It's a good time saver if we can live with the bunching
effect.<br><br>
Wes<br>
---<br>
God help those who do not help themselves.<br><br>
<br>
On Tue, Dec 7, 2010 at 16:43, Robert Bruninga
<<a href="mailto:bruninga@usna.edu">bruninga@usna.edu</a>>
wrote:<br>
<dl>
<dd>>> I'm interested to know how much of the capacity<br>
<dd>>> of the 9k6 is taken up with message content<br>
<dd>>> and how much with TxDelay's?<br><br>
<dd>On a tangential item, the new TH-D72 HT defaults to 200ms at<br>
<dd>1200 baud and Kenwood did not recommend going shorter. It
has<br>
<dd>settings for 150 and 100 ms.. Lemme do a test. Hold
on.<br><br>
<dd>Here is what I got Transmitting from D72 to an old D700 with<br>
<dd>external KPC-9612:<br><br>
<dd>1200 baud to KPC-9612 *not* 100% at 150 ms and below<br>
<dd>1200 baud to D700 internal 100% at 100ms<br>
<dd>9600 baud to KPC-9612 got 100% at 100 ms<br>
<dd>9600 baud to D700 internal 100% at 100ms<br><br>
<dd>Test was HT in basement on 0.05 watts through industrial<br>
<dd>building to sat antenna on roof. More testing with
other<br>
<dd>combinatinos would be warranted, including how fast the D72 can<br>
<dd>receive.<br><br>
<dd>TOO MANY APRS DIGIS have absurd 300 and 500 ms delays!<br><br>
<dd>Bob, Wb4APR<br><br>
<br>
<dd>_______________________________________________<br>
<dd>aprssig mailing list<br>
<dd><a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<dd>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" eudora="autourl">
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br><br>
</dl><br>
_______________________________________________<br>
aprssig mailing list<br>
aprssig@tapr.org<br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" eudora="autourl">
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a></blockquote>
</body>
</html>