On Feb 28, 1996 at 08:50, Bob Lawrence of 3:711/934.12 wrote:

 BL>  Data                        NetComm     TML      Jabberwocky
 BG>> Recv/Xmit Level (-dB)       33/14       35/12    23/12
 BG>> Roundtrip Delay (msec)      15mA        19mS     3mS
 BL>
 BL> For the dB levels, the lower the number the better. The Xmit level
 BL> is what Bill is sending. The Rcv level is what he gets up his line
 BL> from you. It is clear that the local Jabberwocky is 12dB stronger
 BL> (4-times), but that you and the NetComm BBS are about the same.

FWIW, I can't get the same detailed stats as the USR, but I did *finally*
manage to get "AfterConn" working.

    Site    Xmit Level  Rcv Level   EQM     Connect

    TML     -9dBm       -33dBm      027     28800/LAP-M/V.42bis/V.34
    Jabba   -9dBm       -26dBm      020     28800/LAP-M/V.42bis/V.34

Lemme see - I have a higher quality connection to Queensland than I do to
Wollstonecraft here in Sydney?

As I understand it, the M34F is back on-line at the moment;  if Bill took
his stats while the Viper was in place, then that means that Paul's lines
*are* stuffed - yes?  If Bill took his stats whilst the M34F was in place,
then perhaps Paul can just play with his NVRAM settings as I've done.

BTW, Paul - I've found a genuine M34F bug in the V2.61L EPROM that I'm
going to report, and would appreciate it if you would *also* report it.

The "%L0" command is documented as reporting the current receive level:

%L   View Receive Level or Set Transmit Level
       = 0     Display current receive level (-dBm)
       = 11-19 Set transmit level -11dBm to -19dBm

Check this out (calling TML):

> 29 Feb 00:50:09.19   running afterconn
> 29 Feb 00:50:09.19   string is ~~+++~~AT %L0 %Q|~~AT \\V9 O|
# 29 Feb 00:50:15.41   OK
> 29 Feb 00:50:15.44   AT%L0%Q
# 29 Feb 00:50:15.47   050
# 29 Feb 00:50:15.47   023
# 29 Feb 00:50:15.50   OK
> 29 Feb 00:50:15.53   AT\V9O
# 29 Feb 00:50:15.53   Terminal      : 57600  8 data bits  No Parity
# 29 Feb 00:50:15.56   Line          : 28800  V.34
# 29 Feb 00:50:15.59   Error Correct : LAPM
# 29 Feb 00:50:15.62   Compression   : V.42bis tx/rx
# 29 Feb 00:50:15.66   Encryption    : None
# 29 Feb 00:50:15.66   Current EQM   : 027
# 29 Feb 00:50:15.69   EQM Retrain at: 036
# 29 Feb 00:50:15.72   Rx Level(-dBm): 033
# 29 Feb 00:50:15.75   CONNECT 28800/LAP-M/V.42bis/V.34

I can accept the small jump from 023 to 027 on the EQM, but 050 down to
033?  That's bullshit.  Especially when I get exactly the same %L0 output
(050) for David Drummond's system, but a different "Rx Level". 
Definitely an EPROM bug.

Jeff!  Your M7F should also support the "\V9" command, so you
might like to create an "AfterConn" command in your BTPE setup
and see if you get similar EQM/Rx values from TML.

Paul!  We might also ask NetComm to add extra informtion to the \V9 output
(or add an extra command) so that we can try and get nearly (or the same)
as much output as the USR provides - wadda ya say?

 BL> I would be inclined to FAX this data to NetComm, and ask them why
 BL> their transmit levels are so much lower than a Courier.

Because Austel "said so"?

    - dave
    d.begley{at}ieee.org

---