Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!samsung!uunet!edsews!einstein!cirian
From: cirian@einstein.eds.com (Steve Cirian)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit ATJ6J0?
Summary: decipher atj6j0 output
Message-ID: <247@einstein.eds.com>
Date: 10 Jan 91 18:56:52 GMT
References: <1991Jan9.090037@mathcs.emory.edu>
Organization: EDS/TSD - Troy, MI
Lines: 77

In article <1991Jan9.090037@mathcs.emory.edu>, km@mathcs.emory.edu (Ken Mandelberg) writes:
> There has been some reference in this group to the undocumented status
> info extracted by ATJ6J0 on a trailblazer. Does anyone have documentation?

I saved the following from this newsgroup a while ago:

<<From dnb@chaos.cs.brandeis.edu Tue Apr  3 13:14:28 1990
<<Path: einstein!edsews!uunet!ogicse!mintaka!chaos.cs.brandeis.edu!chaos!dnb
<<From: dnb@chaos.cs.brandeis.edu (David N. Blank)
<<Organization: Brandeis University Computer Science Dept
<<Posted: Tue Apr  3 10:14:28 1990
<<
<<The second, and perhaps less "put your ear on the modem and listen for
<<the train coming, Paleface" advice I got was to use the following
<<(undocumented, hooray!) command: ATJ6J0.  This gives a result of the
<<form:
<<   Raaaaaa Rbbbb Rccc
<<   Tdddddd Feeeeee Rffffff Mgggggg Ehhhhhh
<<   jjj lll mmm
<<   nnn
<<   ooo ppp
<<   Mqqqq
<<  
<< where:
<<    a - count of number of times modem has retrained
<<    b - reason for last retrain:
<<       0) never retrained
<<       1) modem saw too many quiet packets
<<       2) packet error rate too high
<<       3) same packet was retransmitted too often
<<       4) &R command was issued
<<    c - reason for the last "NO CARRIER" message:
<<       0) never reported "NO CARRIER"
<<       1) failed during synch
<<       2) packet size too small
<<       3) carrier lost
<<       4) H0 command issued
<<       5) Illegal switch to 212/v22bis
<<       6) DTR dropped
<<       7) talk/data switch pushed
<<       8) negotiation failed
<<       9) received disconnect packet
<<    d - the number of packets thrown out
<<    e - the number of packets received while full
<<    f - the number of packets retransmitted
<<    g - the number of times the modem missed a line turnaround
<<    h - the number of times the modem didn't have a packet ready to
<<        transmit when it was its trun to send
<<    i - the number of framing errors
<<    j - the number of overrun errors
<<    k/l/m - the 2/4/6 bit S/N ratios
<<    n - the attenuator setting
<<    o - the number of bytes per transmitted packet
<<    p - the number of bytes per received packet
<<    q - the MNP class the modem is operating at
<<
<<Please don't ask me to interpret any of the above for you, I typed it
<<straight from the information Tech support gave me (a nice set of
<<people, BTW). If the above display indicates a problem, I understand
<<you can up the amount of tone used for PEP and twiddle a bit with its
<<operating paramters.  For that info, you should see Tech support.
<<Hope this stuff is useful.
<<         Peace,
<<           dNb
<<        dnb@chaos.cs.brandeis.edu
<<
<<P.S. as a last resort you could try spattering sheep's blood on your
<<modem or conducting a small sacrifice.  It may not help the modem
<<problem, but it does wonders for stress.
<<
<<

-- 
Steve Cirian		~  local girl:  What does BRMC stand for?
750 Tower Drive		~  Johnny:      Black Rebels Motorcycle Club
Troy, MI 48007		~  local girl:  What are you rebelling against?
(313) 265-5738		~  Johnny:      Whattya got?