<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
Greeting Jay and all others interested in collisions...<BR>
<BR>
I wish to report that Jay's feedback was good "dog food".<BR>
This "dog" ate it up and solved the problem at hand.<BR>
<BR>
On Thu, 2006-08-10 at 23:08 -0400, Jay Nugent wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Greetings Skip,</FONT>
<FONT COLOR="#000000">On Thu, 10 Aug 2006, George (Skip) VerDuin wrote:</FONT>
<FONT COLOR="#000000">> As I go deeper into jnos operation, I am now beginning to look in detail</FONT>
<FONT COLOR="#000000">> at signals on vhf radio. Not by any means the best, but I find</FONT>
<FONT COLOR="#000000">> "Baudline" fairly useful for that purpose.</FONT>
</PRE>
</BLOCKQUOTE>
Using the tool, I charted a segment of about 5 minutes of air time and 28 transmissions on my part at 1200B.<BR>
The other issue of the moment for me was that jnos was in "recovery" mode on ax.25 and had a significant packet count in queue.<BR>
What I found is that my collision issue is gone after applying parameters per: slottime=7, persist=85, fulldup=off, etc<BR>
100%-no collision / 60%-long wait / 40%-apply formula / 14%-shortest, / 14%-tier#2 / ...<BR>
Just like the text book - jnos and Kan 9612 are working together just fine...<BR>
And I guess I'm no longer the "bad guy" in the neighborhood at least for the signals I can hear...<BR>
<BR>
Other things I found are:
<>
<LI>Other stations do step on my signal (collide) as seen in the signal immediately after transmission and in lost packets.
<LI>Other stations do step on other stations - sometimes garbling & sometimes overriding signals.
<LI>Other stations do have a variety of drive levels.
</UL>
None of this can be a surprise....<BR>
As for restoring "connected" mode from "recovery" mode - that is for another thread.<BR>
>SNIP<<BR>
<BR>
As a postscript, I find Baudline useful in measuring to about 1ms, plus the signal analysis is pretty illuminating.<BR>
On the other hand the time scale is a bear, and so useful results do not come easily.<BR>
There must be a better way?<BR>
<BR>
There were also some other important points made in this thread - THANKS TO EVERYONE.<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>