<!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.3">
</HEAD>
<BODY>
If it ain't broke - don't fix it.<BR>
That's what my dad tried to teach me Bill.<BR>
<BR>
On Sun, 2006-09-17 at 10:30 -0700, wa7nwp wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Everything was working great -- then I tried to fix it.</FONT>
<FONT COLOR="#000000">Went to add the "COMM" commands to automatically put my KPC3 into KISS </FONT>
<FONT COLOR="#000000">mode for JNOS. I had the param 255 setting in onexit.nos to take it out </FONT>
<FONT COLOR="#000000">when JNOS shut down so it was only naturally that JNOS should start it up.</FONT>
</PRE>
</BLOCKQUOTE>
You might want to rethink this process?<BR>
On the normal operation scene your work could be slick for a mixed use of the KPC-3.<BR>
But for jnos, this means a complex startup to determine if the former session left the TNC in:<BR>
terminal mode from a normal jnos exit<BR>
kiss mode from an abort exit - like power failure?<BR>
maybe other modes from crashes of other software?<BR>
The simplifying rule of "in kiss before initializing jnos" addresses the difficulty of scripting the unknown?<BR>
If you have been able to script jnos to query and direct TNC setup, I'd really like to see you work.<BR>
Even if you develop a pre-jnos bash script to configure the TNC it might be quite valuable to many of us?<BR>
And if jnos is a service on your station, then system reboot or respawn brings jnos back to life reliably...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Of course I started out following the settings in "help comm" and that's </FONT>
<FONT COLOR="#000000">apparently for the AEA or older KPC TNCS. A few more bogus param </FONT>
<FONT COLOR="#000000">commands later and my KPC3 is acting weird. An outgoing ax25 connect </FONT>
<FONT COLOR="#000000">transmits ok -- but the received packets coming back from the KPC3 to </FONT>
<FONT COLOR="#000000">JNOS are apparently in some polled kiss mode. JNOS trace shows a </FONT>
<FONT COLOR="#000000"><polled> flag and 8 or so "." bytes before the data. If tried the tnc </FONT>
<FONT COLOR="#000000">commands for polled xkiss and checksummed xkiss but nothing seems to </FONT>
<FONT COLOR="#000000">work. I'm about to pop the case and do a hard reset -- pretty sure </FONT>
<FONT COLOR="#000000">that will fix it. Still I'm curious about what mode this is and if </FONT>
<FONT COLOR="#000000">there is a way to fix it from the TNC command prompt.</FONT>
<FONT COLOR="#000000">It's strange there's no hard reset (that I can find) anymore from the </FONT>
<FONT COLOR="#000000">command prompt.</FONT>
</PRE>
</BLOCKQUOTE>
The KPC-9612 takes a screwdriver too. Seems like a product design criteria?<BR>
<BR>
You have a neat concept in hand, you consider publishing it when you are done?
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Anybody have any suggestions here?</FONT>
<FONT COLOR="#000000">Thanks,</FONT>
<FONT COLOR="#000000">Bill - WA7NWP</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>