[nos-bbs] Unanswered emails & tracking REJ, FRMR, RNR, RR, AX25 performance

Michael Fox - N6MEF n6mef at mefox.org
Mon Oct 18 17:17:13 EDT 2010

Hi Maiko,

Excellent idea.  I wouldn't say we "track" those counts but we sure do look
at those frames when diagnosing a problem.  Of course, often, we're told
about a problem after the fact, such as, "I was trying to check-in last
Tuesday and I had this or that problem".  So if we had stats we could look
at, in addition to the trace files, I think that would be an excellent tool
for overall performance management and optimization.

If the stats of an individual user were available to that user, not just the
sysop, that would also be a win.  The user could make their adjustments,
clear the counters, and then look at the results again.

I still want to put in a plug for eliminating the delay in the write of
trace info to a file.  With the current delay, it's just impossible to do
any real-time troubleshooting.  Output to the screen scrolls by too quickly
and output to the file doesn't happen in real-time.

I should think that the decoding of the trace info is what uses CPU
resources, and once that's done, it should be no more burden on JNOS to hand
the decoded text to the file system for writing than it currently is to
display it to the screen.


-----Original Message-----
From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of Maiko Langelaar
Sent: Monday, October 18, 2010 10:19 AM
To: NOS BBS Mailing List
Subject: [nos-bbs] Unanswered emails & tracking REJ, FRMR, RNR, RR, AX25

Good day to all,

First of all, I must apologize for my extreme slowness in
answering (or yet to answer) outstanding emails. Been a bit
burnt out lately, and unfortunately when this happens my desire
to attend to outstanding emails (about packet radio) withers.

It's not intentional, it's just a human's way of automatically
defending against overheating of the brain and nervous system,
and I will get to them shortly.

The main reason for this post has to do with me getting my baycom
board fixed and working again. One of the things I noticed in the
traces got me thinking. There really is no way to track RR, RNR,
REJ, FRMR, and other packet statistics in NOS, is there ? If I
could collect those stats on a per station basis, perhaps it
would help me in optimizing the parameters (like drive levels,
volume control, etc, etc). The reason I bring in 'per station'
as a basis is many times there are problems specific to only
my station and someone else.

Any comments ? Has anyone ever tracked this stuff ? It would
take very little to add statistics code to JNOS to collect
this information, so that it could be graphed. I would like
to do it, so that I can better fine tune my baycom board
for instance.

Or perhaps I am being too presumptious in saying that drive
and volume levels have a direct correlation to the number of
FRMR packets received ? In the end I just to be able to get
more information to help me optimize my links.

73 Maiko Langelaar / VE4KLM

nos-bbs mailing list
nos-bbs at tapr.org

More information about the nos-bbs mailing list