[nos-bbs] JNOS Connect Fail

[Michael Curry]

Hey Kurt,

I'm not smart enough to know how to enable tracing on the T2 interface.
>

Oh, pshaw! You just haven't gotten to that point in the documentation yet!
:-)


> I'll be happy to do it and post up the results if you can walk me
> through how to do it.
>

The command is "trace", and has the form:

trace [<iface> [off | <btio> [<outfile>]] [<flush-interval>]

where <iface> is the name of the ax25 interface to the TNC, <btio> is a
numeric representation of some control bits that select what information
the trace captures, <outfile> is the name of the trace output file, and
<flush-interval> is the number of milliseconds after which JNOS will flush
buffered data to <outfile>. I won't detail the meanings of the control bits
here (they're documented in the JNOS2-MAN.rtf file).

In my autoexec.nos file, the trace command looks like:

trace tnc1 4211 tnc1_trace 1000

which results in a pretty full dump of each packet sent or received on the
interface, and which flushes buffered output to the file after one second.

Like you, I'm kinda bummed about this.  I originally bought my T2 for
> APRS usage, but thought the KISS "ability" was a great value-added
> feature.
>

Yep. Pretty much my thinking when I bought my Tracker 2.

I really do want to encourage you to pester Scott somewhat about this, with
a reference to my post on the Tracker 2 forum from last year. We might be
able to get him to at least specifically identify the problem, if not to
actually bump up his priority on fixing it -- if it's fixable.

M
-- 
This cat is pushing a watermelon out of a lake. Your argument is invalid.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20120531/574cbbea/attachment.html>