USR Sportster V.90 (00178602) connecting to Livingston PM3's Problem
Mark Knipfer
[Messaged directed to comp.dcom.modems newsgroups and CC'd to
onenet.help newsgroup.]
I am using a (being a secondary modem) USR Sportster 56K Faxmodem
external that has been upgraded to V.90 from X2. The USR Sportster 56k
model is a 00178602. The USR Modem Update Wizard states there are no
more updates/upgrades available for the modem. Here is the
configuration profile for the modem:
-----
U.S. Robotics 56K FAX EXT V4.9.1
Configuration Profile...
Product type US/Canada
Product ID: 00178602
Options V32bis,V.34+,x2,V.90
Fax Options Class 1/Class 2.0
Line Options Caller ID, Distinctive Ring
Clock Freq 92.0Mhz
EPROM 256k
RAM 32k
FLASH date 2/24/98
FLASH rev 4.9.1
DSP date 2/24/98
DSP rev 4.9.1
Serial Number: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Device ID: 00178602
-----
After the initial V.90 upgrade through the USR Modem Update Wizard, the
serial number change to all Z's.
The ISP (OneNet Communications, Inc. -- http://www.one.net) I am trying
to connect to uses Livingston/Lucent Portmaster 3's with using the V.90
code on them, more likely the code is beta due to V.90 code not being
finalized. There are some of us using Motorola ModemSUFR 56K Internal
and External modems connecting fine, between 44k to 52k, with no
problems. The K56Flex connections have been good, fast and reliable
connnections.
When OneNet flashed their Livingston/Lucent PortMaster 3's to V.90, I
flashed the USR Sportster 56K modem to V.90 from X2. I have not been
able to establish a solid and stable V.90 connection at all. The
connection rates have been between 53,333 bos to 56,666 bps. However,
these good high speed connections have only lasted less than three to
five minues or less than thirty seconds. The V.90 connections at
OneNet, at first, seem to be very fast. Suddenly the throughput on the
connections seem to halt and either disconnect me immediately or the
connection becomes idle without able to access any servers or the web
and become disconnected.
I have contacted the ISP's technical support group regarding this
problem. They have stated the problem exists on my end as they have
many users connecting with V.90 modems successfully. They can never
tell me if these "V.90 modems" are USR modems or not, just "V.90 modem
users are connecting with great success over K56Flex." I have yet see a
user state in the OneNet support newsgroups they have a good established
V.90 connection to OneNet. Mostly see users complaining about the
horrible connections with V.90 and they are becoming disconnected.
I have connected to OneNet several times using the USR Sportster 56K
V.90 upgraded external modem (Model 00178602) with the modem being
configured to the following:
ati4
U.S. Robotics 56K FAX EXT Settings...
B0 E1 F1 M1 Q0 V1 X4 Y0
BAUD=115200 PARITY=N WORDLEN=8
DIAL=TONE ON HOOK CID=0
&A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1
&M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002
S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=000
S41=000 S42=000
LAST DIALED #:
ati5
U.S. Robotics 56K FAX EXT NVRAM Settings...
Template Y0
DIAL=TONE B0 F1 M1 X4
BAUD=38400 PARITY=N WORDLEN=8
&A3 &B1 &G0 &H1 &I0 &K1 &M4 &N0
&P0 &R2 &S0 &T5 &U0 &Y1
S00=001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060
S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000
S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008
S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000
S36=014 S38=000 S39=000 S40=000 S41=000 S42=000
Template Y1
DIAL=TONE B0 F1 M1 X4
BAUD=38400 PARITY=N WORDLEN=8
&A3 &B1 &G0 &H2 &I2 &K1 &M4 &N0
&P0 &R1 &S0 &T5 &U0 &Y1
S00=001 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060
S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000
S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008
S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000
S36=014 S38=000 S39=000 S40=000 S41=000 S42=000
ati7
Configuration Profile...
Product type US/Canada External
Product ID: 00178602
Options V32bis,V.34+,x2,V.90
Fax Options Class 1/Class 2.0
Line Options Caller ID, Distinctive Ring
Clock Freq 92.0Mhz
EPROM 256k
RAM 32k
FLASH date 2/24/98
FLASH rev 4.9.1
DSP date 2/24/98
DSP rev 4.9.1
After several disconnections, I use Windows 95/98 Hyperterminal for
doing an ATI6 command and here are the results:
ATI6
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 765 Chars Received 240151
Chars lost 0
Octets sent 1868 Octets Received 72140
Blocks sent 341 Blocks Received 911
Blocks resent 19
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 21
Link Timeouts 8 Link Naks 4
Data Compression V42BIS 1024/32
Equalization Long
Fallback Enabled
Protocol LAPM
Speed 54666/28800
V.90 Peak Speed 54666
Last Call 00:06:25
Disconnect Reason is Unable to Retrain
-----
ATI6
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 479 Chars Received 118379
Chars lost 0
Octets sent 735 Octets Received 118936
Blocks sent 437 Blocks Received 1133
Blocks resent 7
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 14
Link Timeouts 3 Link Naks 1
Data Compression NONE
Equalization Long
Fallback Enabled
Protocol LAPM
Speed 54666/31200
V.90 Peak Speed 54666
Last Call 00:03:01
Disconnect Reason is Unable to Retrain
-----
Why is the modem constantly retraining on OneNet V.90 connections?
These V.90 connections to OneNet are horrible and hoping someone in this
newsgroup can shed some light on this problem. Is this a USR or a
Livingston/Lucent PortMaster problem with the current [beta] V.90 code
being used?
Hooda Gest
Mark Knipfer wrote in message <3583ACA4...@one.net>...
>[Messaged directed to comp.dcom.modems newsgroups and CC'd to
>onenet.help newsgroup.]
>
>I am using a (being a secondary modem) USR Sportster 56K Faxmodem
>external that has been upgraded to V.90 from X2. The USR Sportster 56k
>model is a 00178602. The USR Modem Update Wizard states there are no
>more updates/upgrades available for the modem. Here is the
>configuration profile for the modem:
[I trimmed out lots of very good info]
>
>Why is the modem constantly retraining on OneNet V.90 connections?
>These V.90 connections to OneNet are horrible and hoping someone in
this
>newsgroup can shed some light on this problem. Is this a USR or a
>Livingston/Lucent PortMaster problem with the current [beta] V.90 code
>being used?
It appears to be more related to the line conditions than the modem or
PM. You have a very "hot" line, it appears. I would have liked to see
both an ati11 and an aty11 to get a little better idea of what the
conditions are. My bet is that your aty11 will shown a lot of figures in
the teens and a very flat curve.
I have a suggestion for you and that is to limit your connect speed to
either 53333 or 52000 (try each of these and compare throughput). You
can do this through the use of the &Nn and &Un commands.
To determine the "n" values, go into a terminal program and enter at&$
to get a display of all the & type commands. Find the values for 53333
and 52000, use one of those for the &N value. Use a nominal low speed
value for the &U (I'd suggest 10 which is for 19200). Place the two
commands in your Extra settings for the connectoid. Then make some
calls into your ISP and see if the overall performance isn't much
better.
To prove the problem to be a local one, call the USR BBS at
847-982-5092. Make sure the &Nn and &Un are set to zero when you do
this. See if the connection is the same or better than when calling your
ISP. If it's better than it's something in the local routing that
causing the problem.
Mark Knipfer
> >onenet.help newsgroup.]
> >
> >I am using a (being a secondary modem) USR Sportster 56K Faxmodem
> >external that has been upgraded to V.90 from X2. The USR Sportster 56k
> >model is a 00178602. The USR Modem Update Wizard states there are no
> >more updates/upgrades available for the modem. Here is the
> >configuration profile for the modem:
>
> >
> >These V.90 connections to OneNet are horrible and hoping someone in
> this
> >newsgroup can shed some light on this problem. Is this a USR or a
> >Livingston/Lucent PortMaster problem with the current [beta] V.90 code
> >being used?
>
> PM. You have a very "hot" line, it appears. I would have liked to see
> both an ati11 and an aty11 to get a little better idea of what the
> conditions are. My bet is that your aty11 will shown a lot of figures in
> the teens and a very flat curve.
What exactly do you mean by "..a very hot line?" I was not aware about
the ati11 and aty11 command. I will use these commands later today when
testing the V.90 connections to the ISP.
> I have a suggestion for you and that is to limit your connect speed to
> either 53333 or 52000 (try each of these and compare throughput). You
> can do this through the use of the &Nn and &Un commands.
I have already tried the &U## and &N## parameters with no success.
There have been 40k connection acting exhibiting the same behavior with
higher speed V.90 connections.
> To prove the problem to be a local one, call the USR BBS at
> 847-982-5092. Make sure the &Nn and &Un are set to zero when you do
> this. See if the connection is the same or better than when calling your
> ISP. If it's better than it's something in the local routing that
> causing the problem.
I have not tested the modem with the USR BBS line, yet. I will jot this
number down and give it a test.
Thanks.
Ed Schulz
Hooda Gest wrote in message <6m0f8u$17q6$1...@news.gate.net>...
>>external that has been upgraded to V.90 from X2. The USR Sportster 56k
>>model is a 00178602. The USR Modem Update Wizard states there are no
>>more updates/upgrades available for the modem. Here is the
>>configuration profile for the modem:
>PM
I agree that you have an exceptionally good line if the modem is connecting
at 54666/31200. In addition to the good suggestion to limit your downstream
rate, you might try limiting the V.34 upstream rate. Sorry, I don't have
the 3Com command at my fingertips.
Tweaks like this should not be necessary, but as you noted, you are
connecting to beta PM3 code. I'd be interested to know whether one option
or the other results in more stable connections for you.
--
Ed Schulz
edsc...@lucent.com
Hooda Gest
Mark Knipfer wrote in message <3583CD28...@one.net>...
>Hooda Gest wrote:
>>
[more trimming]
>>
>> It appears to be more related to the line conditions than the modem
or
>> PM. You have a very "hot" line, it appears. I would have liked to see
>> both an ati11 and an aty11 to get a little better idea of what the
>> conditions are. My bet is that your aty11 will shown a lot of figures
in
>> the teens and a very flat curve.
>
>What exactly do you mean by "..a very hot line?" I was not aware about
>the ati11 and aty11 command. I will use these commands later today
when
>testing the V.90 connections to the ISP.
A "hot" line is one that has low -db levels. Let's say a line would be
designed for minimal distortion of signal at -18db. If that line had
readings of -13db then the line would be "hot". For voice, that
sometimes means a hollow sound. For data, it can mean the modem thinks
the line is better than it actually is. Don't ask me why, that's for an
engineer to explain. :) This applies mostly to analog connections but it
also has an effect on digital circuits. by contrast, a "long circuit" is
one that whose db levels are beyond the designed optimum; a -23db on
that 18db circuit, for example. A quieter, or muffled, circuit results.
I wanted to call into your ISP but I couldn't find an access numbers to
test against. It's an LD call for me but it would tell me whether the
problem is more toward them or toward you (eliminates local routing
problems). If it's not against their policy, let me have a number I can
try.
>> I have a suggestion for you and that is to limit your connect speed
to
>> either 53333 or 52000 (try each of these and compare throughput). You
>> can do this through the use of the &Nn and &Un commands.
>
>I have already tried the &U## and &N## parameters with no success.
>There have been 40k connection acting exhibiting the same behavior with
>higher speed V.90 connections.
That tends to make me wonder what else is going on and whether the fault
is not really at their end. They are reporting that connections are
exceeding the "FCC's maximum permitted speed" (this is not true, the
FCC mandates power levels which may result in speeds above 53333 being
impossible). My take is that there is something not quite right about
all this and those reports may be real but they may also be in the same
context as yours; you get them but performance sticks.
>> To prove the problem to be a local one, call the USR BBS at
>> 847-982-5092. Make sure the &Nn and &Un are set to zero when you do
>> this. See if the connection is the same or better than when calling
your
>> ISP. If it's better than it's something in the local routing that
>> causing the problem.
>
>I have not tested the modem with the USR BBS line, yet. I will jot
this
>number down and give it a test.
Let us know what you get. It might be useful to see ati6i11 displays
from a call to the USR BBS and the ISP also.
Incidently, while onlie to USR's BBS, you can enter USRSTATS at the Main
command prompt and get a "picture" of what their modem "sees" in the
connection. This can sometimes be useful. It uses data from the ati6,
ati11, and ati7 displays that it runs while you are online.
Keep us posted.
Mark Knipfer
Hooda Gest wrote:
>
> >What exactly do you mean by "..a very hot line?" I was not aware about
> >the ati11 and aty11 command. I will use these commands later today
> when
> >testing the V.90 connections to the ISP.
>
> A "hot" line is one that has low -db levels. Let's say a line would be
> designed for minimal distortion of signal at -18db. If that line had
> readings of -13db then the line would be "hot". For voice, that
> sometimes means a hollow sound. For data, it can mean the modem thinks
> the line is better than it actually is. Don't ask me why, that's for an
> engineer to explain. :) This applies mostly to analog connections but it
> also has an effect on digital circuits. by contrast, a "long circuit" is
> one that whose db levels are beyond the designed optimum; a -23db on
> that 18db circuit, for example. A quieter, or muffled, circuit results.
I guess the ATY11 command displays this information. Right?
> I wanted to call into your ISP but I couldn't find an access numbers to
> test against. It's an LD call for me but it would tell me whether the
> problem is more toward them or toward you (eliminates local routing
> problems). If it's not against their policy, let me have a number I can
> try.
OneNet Communication dial up number is 513-618-1111.
> >I have already tried the &U## and &N## parameters with no success.
> >There have been 40k connection acting exhibiting the same behavior with
> >higher speed V.90 connections.
>
> That tends to make me wonder what else is going on and whether the fault
> is not really at their end. They are reporting that connections are
> exceeding the "FCC's maximum permitted speed" (this is not true, the
> FCC mandates power levels which may result in speeds above 53333 being
> impossible). My take is that there is something not quite right about
> all this and those reports may be real but they may also be in the same
> context as yours; you get them but performance sticks.
To let you know, I am not pointing the finger really at anyone. I am a
person who is seeking a solutions with some answers possibly. :)
There are many variables to this problem. However I may have found a
solution by someone else reading my e-mail message and known my
experiences regarding this ongoing V.90 modem-connection problem.
> >> To prove the problem to be a local one, call the USR BBS at
> >> 847-982-5092. Make sure the &Nn and &Un are set to zero when you do
> >> this. See if the connection is the same or better than when calling
> your
> >> ISP. If it's better than it's something in the local routing that
> >> causing the problem.
> >
> >I have not tested the modem with the USR BBS line, yet. I will jot
> this
> >number down and give it a test.
>
> Let us know what you get. It might be useful to see ati6i11 displays
> from a call to the USR BBS and the ISP also.
I used 3Com/USR's 888 number for accessing the BBS. The number is
1-888-877-9248. Why pay for long distance when you don't need to!
> Incidently, while onlie to USR's BBS, you can enter USRSTATS at the Main
> command prompt and get a "picture" of what their modem "sees" in the
> connection. This can sometimes be useful. It uses data from the ati6,
> ati11, and ati7 displays that it runs while you are online.
There was no opportunity for entering USRSTATS on the main menu.
> Keep us posted.
Here is the USR results from connecting to OneNet (ISP) and the USR BBS
on the 888 number:
Test results from ISP:
======================
ATI4
U.S. Robotics 56K FAX EXT Settings...
B0 E0 F1 M1 Q0 V1 X4 Y1
BAUD=115200 PARITY=N WORDLEN=8
DIAL=TONE ON HOOK CID=0
&A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1
&M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1
S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002
S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001
S41=000 S42=000
LAST DIALED #: T6181111
OK
ATI6
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 290870 Chars Received 2099520
Chars lost 0
Octets sent 290870 Octets Received 2103309
Blocks sent 10914 Blocks Received 17078
Blocks resent 20
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 65
Link Timeouts 0 Link Naks 1
Data Compression NONE
Equalization Long
Fallback Enabled
Protocol LAPM
Speed 50666/31200
V.90 Peak Speed 50666
Last Call 00:29:28
Disconnect Reason is DTR dropped
ATI11
ERROR
ATY11
Freq Level (dB)
150 24
300 23
450 22
600 22
750 22
900 22
1050 23
1200 23
1350 23
1500 23
1650 24
1800 24
1950 24
2100 24
2250 25
2400 25
2550 25
2700 25
2850 25
3000 26
3150 26
3300 26
3450 27
3600 30
3750 35
OK
ATZ
OK
ATI11
U.S. Robotics 56K FAX EXT Link Diagnostics...
Modulation Unknown Speed
Carrier Freq (Hz)
Symbol Rate
Trellis Code
Nonlinear Encoding
Precoding
Shaping
Preemphasis (-dB)
Recv/Xmit Level (-dBm)
Near Echo Loss (dB)
Far Echo Loss (dB)
Carrier Offset (Hz)
Round Trip Delay (msec)
Timing Offset (ppm)
SNR (dB)
Speed Shifts Up/Down 0/0
Status :
OK
---
Connection #2:
ATI6
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 65336 Chars Received 532803
Chars lost 0
Octets sent 65336 Octets Received 532954
Blocks sent 2297 Blocks Received 4240
Blocks resent 13
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 3
Link Timeouts 2 Link Naks 0
Data Compression NONE
Equalization Long
Fallback Enabled
Protocol LAPM
Speed 50666/31200
V.90 Peak Speed 50666
Last Call 00:02:58
Disconnect Reason is DTR dropped
OK
ATI11
U.S. Robotics 56K FAX EXT Link Diagnostics...
Modulation V.90
Carrier Freq (Hz) None/1920
Symbol Rate 8000/3200
Trellis Code None/64S-4D
Nonlinear Encoding None/ON
Precoding None/ON
Shaping ON/ON
Preemphasis (-dB) 2/8
Recv/Xmit Level (-dBm) 67/9
Near Echo Loss (dB) 7
Far Echo Loss (dB) 0
Carrier Offset (Hz) NONE
Round Trip Delay (msec) 20
Timing Offset (ppm) -3120
SNR (dB) 42.1
Speed Shifts Up/Down 0/0
Status : uu,5,12N,12.3,-15,0N,0,51.1,10.4
OK
ATY11
Freq Level (dB)
150 24
300 23
450 22
600 22
750 22
900 22
1050 23
1200 23
1350 23
1500 23
1650 24
1800 24
1950 24
2100 24
2250 25
2400 25
2550 25
2700 25
2850 25
3000 26
3150 26
3300 26
3450 27
3600 30
3750 35
OK
********************************************************************
Test Results from USR BBS:
atdt 18888779248
CONNECT 50666/ARQ/V90/LAPM
CONNECT 50666/ARQ/V90/LAPM
CONNECT 115200 / 06-14-98 (11:04:24)
(Error Correcting Modem Detected)
USR Support BBS - Node 30 - Total Control Rack
PCBoard (R) v15.3/250 - Node 30
Testing your system capability...
[...]
What is your first name? line test
Test returned code 1
[graphic border removed]
* C O N G R A T U L A T I O N S *
You are currently connected at 56K. No further testing is required.
Minutes Used: 0
Thank you for calling the U.S. Robotics BBS
NO CARRIER
ATI6
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 25 Chars Received 2976
Chars lost 0
Octets sent 25 Octets Received 2976
Blocks sent 15 Blocks Received 71
Blocks resent 0
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 0
Link Timeouts 0 Link Naks 0
Data Compression NONE
Equalization Long
Fallback Enabled
Protocol LAPM/SREJ
Speed 50666/28800
V.90 Peak Speed 50666
Last Call 00:00:20
Disconnect Reason is DISC Received
OK
ATI11
U.S. Robotics 56K FAX EXT Link Diagnostics...
Modulation V.90
Carrier Freq (Hz) None/1920
Symbol Rate 8000/3200
Trellis Code None/64S-4D
Nonlinear Encoding None/ON
Precoding None/ON
Shaping ON/ON
Preemphasis (-dB) 8/2
Recv/Xmit Level (-dBm) 14/10
Near Echo Loss (dB) 7
Far Echo Loss (dB) 0
Carrier Offset (Hz) NONE
Round Trip Delay (msec) 22
Timing Offset (ppm) -3017
SNR (dB) 51.4
Speed Shifts Up/Down 0/0
Status : uu,5,12N,12.2,-15,1N,0,52.4,12.1
OK
ATY11
Freq Level (dB)
150 20
300 19
450 19
600 19
750 19
900 19
1050 19
1200 19
1350 19
1500 20
1650 20
1800 20
1950 20
2100 21
2250 21
2400 21
2550 21
2700 22
2850 22
3000 23
3150 24
3300 25
3450 27
3600 32
3750 39
OK
Hooda Gest
Mark Knipfer wrote in message <3583FA6A...@one.net>...
>Hooda Gest wrote:
>>
>> A "hot" line is one that has low -db levels. Let's say a line would
be
>
>I guess the ATY11 command displays this information. Right?
In a sense. It displays a curve showing db levels for various
frequencies. Outside of levels that are extreme, you are mostly looking
for quick shifts in the numerical values. Most clean lines with mostly
digital makeup are fairly flat until the very upper frequencies and
sometimes even there it remains fairly flat.
>> impossible). My take is that there is something not quite right about
>> all this and those reports may be real but they may also be in the
same
>> context as yours; you get them but performance sticks.
>
>To let you know, I am not pointing the finger really at anyone. I am a
>person who is seeking a solutions with some answers possibly. :)
I understand. I am not trying to point fingers either, just trying to
determine if there is something someone has control over or is part of
the fact of life in your situation.
Incidently, that ISP's pricing scheme looks pretty good. I wish I had
the same deal here...
>
>There are many variables to this problem. However I may have found a
>solution by someone else reading my e-mail message and known my
>experiences regarding this ongoing V.90 modem-connection problem.
And his suggestion is????
>> Let us know what you get. It might be useful to see ati6i11 displays
>> from a call to the USR BBS and the ISP also.
>
>I used 3Com/USR's 888 number for accessing the BBS. The number is
>1-888-877-9248. Why pay for long distance when you don't need to!
Well, using the regular number allows you to run the USRSTATS command.
:) It only takes a minute or so (about 15 or 30 cents for me).
>
>Here is the USR results from connecting to OneNet (ISP) and the USR BBS
>on the 888 number:
>
>Test results from ISP:
>======================
>ATI11
>ERROR
Don't understand why you got this error...
>
>ATY11
>Freq Level (dB)
>
That was nice and flat and not as hot as I expected. You'll see at the
bottom where I am posting mine...
>ATI11
>U.S. Robotics 56K FAX EXT Link Diagnostics...
>
>
>Modulation V.90
>Carrier Freq (Hz) None/1920
>Symbol Rate 8000/3200
>Trellis Code None/64S-4D
>Nonlinear Encoding None/ON
>Precoding None/ON
>Shaping ON/ON
>Preemphasis (-dB) 2/8
>Recv/Xmit Level (-dBm) 67/9
>Near Echo Loss (dB) 7
>Far Echo Loss (dB) 0
>Carrier Offset (Hz) NONE
>Round Trip Delay (msec) 20
>Timing Offset (ppm) -3120
>SNR (dB) 42.1
>Speed Shifts Up/Down 0/0
>Status : uu,5,12N,12.3,-15,0N,0,51.1,10.4
>OK
I am not impressed with your SNR. It seems a bit poor. Above 45.0 would
be better and 50 is even more desireable.
>Test Results from USR BBS:
Note the SNR on this connection. Much better. Also, there was quite a
difference with the Rcv/Xmit levels in the two calls....
>
>ATI11
>
>U.S. Robotics 56K FAX EXT Link Diagnostics...
>
>Modulation V.90
>Carrier Freq (Hz) None/1920
>Symbol Rate 8000/3200
>Trellis Code None/64S-4D
>Nonlinear Encoding None/ON
>Precoding None/ON
>Shaping ON/ON
>Preemphasis (-dB) 8/2
>Recv/Xmit Level (-dBm) 14/10
>Near Echo Loss (dB) 7
>Far Echo Loss (dB) 0
>Carrier Offset (Hz) NONE
>Round Trip Delay (msec) 22
>Timing Offset (ppm) -3017
>SNR (dB) 51.4
>Speed Shifts Up/Down 0/0
>Status : uu,5,12N,12.2,-15,1N,0,52.4,12.1
>OK
>
>ATY11
>Freq Level (dB)
This freq run was hotter but still nice and flat.
Here's what I get to my ISP...
ati6
USRobotics Courier V.Everything Link Diagnostics...
Chars sent 35431 Chars Received 281222
Chars lost 0
Octets sent 35228 Octets Received 281015
Blocks sent 2138 Blocks Received 2602
Blocks resent 5
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 64
Link Timeouts 0 Link Naks 1
Data Compression V42BIS 2048/32
Equalization Long
Fallback Enabled
Protocol LAPM 128/15
Speed 48000/28800
Last Call 01:04:49
Disconnect Reason is DTR dropped
OK
ati11
USRobotics Courier V.Everything Link Diagnostics...
Modulation V.90/V.34+
Carrier Freq ( Hz ) NONE/1829
Symbol Rate 8000/3200
Trellis Code NONE/64S-4D
Nonlinear Encoding NONE/ON
Precoding NONE/OFF
Shaping OFF/ON
Preemphasis Index NONE/6
Recv/Xmit Level (-dBm) 12.2/17.1
SNR ( dB ) 50.2
Near Echo Loss ( dB ) 15.5
Far Echo Loss ( dB )
Roundtrip Delay (msec) 5
Timing Offset ( ppm) -2858
Carrier Offset ( ppm) 74
RX Upshifts 0
RX Downshifts 0
TX Speedshifts 0
V.90 Status uu,5,0N,7.0,-7,2N,0,44.2,22.9
OK
aty11
Freq Level
150 20
300 17
450 16
600 15
750 15
900 15
1050 15
1200 15
1350 15
1500 15
1650 15
1800 15
1950 15
2100 16
2250 16
2400 16
2550 16
2700 16
2850 16
3000 17
3150 17
3300 19
3450 21
3600 26
3750 33
OK
And here is what I got at OneNet...
ati6
USRobotics Courier V.Everything Link Diagnostics...
Chars sent 10 Chars Received 773
Chars lost 0
Octets sent 10 Octets Received 561
Blocks sent 10 Blocks Received 17
Blocks resent 2
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 1
Link Timeouts 0 Link Naks 1
Data Compression V42BIS 1024/32
Equalization Long
Fallback Enabled
Protocol LAPM 128/8
Speed 48000/28800
Last Call 00:00:53
Disconnect Reason is DTR dropped
OK
ati11
USRobotics Courier V.Everything Link Diagnostics...
Modulation V.90/V.34+
Carrier Freq ( Hz ) NONE/1920
Symbol Rate 8000/3200
Trellis Code NONE/16S-4D
Nonlinear Encoding NONE/OFF
Precoding NONE/OFF
Shaping OFF/OFF
Preemphasis Index NONE/6
Recv/Xmit Level (-dBm) 17.5/17.2
SNR ( dB ) 51.0
Near Echo Loss ( dB ) 15.3
Far Echo Loss ( dB )
Roundtrip Delay (msec) 50
Timing Offset ( ppm) -2829
Carrier Offset ( ppm) 55
RX Upshifts 0
RX Downshifts 0
TX Speedshifts 0
V.90 Status uu,5,12N,12.2,-15,2N,0,48.2,25.7
OK
aty11
Freq Level
150 26
300 23
450 22
600 22
750 22
900 22
1050 21
1200 21
1350 21
1500 22
1650 22
1800 22
1950 22
2100 22
2250 22
2400 22
2550 22
2700 22
2850 22
3000 23
3150 23
3300 23
3450 24
3600 26
3750 30
Now let's let the "engineers" among us decipjer the results... :)
Mark Knipfer
Hooda Gest wrote:
>
> Incidently, that ISP's pricing scheme looks pretty good. I wish I had
> the same deal here...
How much do you pay your ISP for per month?
> >There are many variables to this problem. However I may have found a
> >solution by someone else reading my e-mail message and known my
> >experiences regarding this ongoing V.90 modem-connection problem.
>
> And his suggestion is????
Oh, I forgot to include to see next message. This is the message I have
forwarded over from the onenet.help newsgroup to the comp.dcom.modems
newsgroup. Sorry about the misdirection in the message.
> >> Let us know what you get. It might be useful to see ati6i11 displays
> >> from a call to the USR BBS and the ISP also.
> >
> >I used 3Com/USR's 888 number for accessing the BBS. The number is
> >1-888-877-9248. Why pay for long distance when you don't need to!
>
> Well, using the regular number allows you to run the USRSTATS command.
> :) It only takes a minute or so (about 15 or 30 cents for me).
I will try the USR BBS number 1-847-982-5092 later.
> ati6
> USRobotics Courier V.Everything Link Diagnostics...
>
> Chars sent 35431 Chars Received 281222
> Chars lost 0
> Octets sent 35228 Octets Received 281015
> Blocks sent 2138 Blocks Received 2602
> Blocks resent 5
>
> Retrains Requested 0 Retrains Granted 0
> Line Reversals 0 Blers 64
> Link Timeouts 0 Link Naks 1
What are "Blers?"
> USRobotics Courier V.Everything Link Diagnostics...
>
> Modulation V.90/V.34+
I noticed there is no X2 protocol in your USR Courier modem.
The connection did not seem to be bad at all for the 53 second
connection. However, the modems data compression is disabled (&K0)
during my previous connections and you Courier is using V42BIS
compression. Just wondering if the modems data compression make any
real differences.
Hooda Gest
Mark Knipfer wrote in message <358470BB...@one.net>...
>Hooda Gest wrote:
>>
>> Incidently, that ISP's pricing scheme looks pretty good. I wish I had
>> the same deal here...
>
>How much do you pay your ISP for per month?
$24.95 for combined shell and PPP logins, no web page (anymore... used
to be available). 7 Meg max storage.
>>
>> And his suggestion is????
>
>Oh, I forgot to include to see next message. This is the message I
have
>forwarded over from the onenet.help newsgroup to the comp.dcom.modems
>newsgroup. Sorry about the misdirection in the message.
Oh, that was the one about cables and such? I read that and didn't see
anything very useful. Maybe I missed something.
>
>> >> Let us know what you get. It might be useful to see ati6i11
displays
>> >> from a call to the USR BBS and the ISP also.
>> >
>> >I used 3Com/USR's 888 number for accessing the BBS. The number is
>> >1-888-877-9248. Why pay for long distance when you don't need to!
>>
>> Well, using the regular number allows you to run the USRSTATS
command.
>> :) It only takes a minute or so (about 15 or 30 cents for me).
>
>I will try the USR BBS number 1-847-982-5092 later.
>
>
>What are "Blers?"
Block Errors. The "blocks" (I believe 128 bits each) that the modems
actually communicate in. Sometimes called data packets. Something wrong
with a block triggers a "Bler" incrementation.
Large amounts of these indicate line impairment (analog noise,
execessive slip or frame loss in a digital part of the circuit, etc).
>
>> USRobotics Courier V.Everything Link Diagnostics...
>>
>> Modulation V.90/V.34+
>
>I noticed there is no X2 protocol in your USR Courier modem.
No, that is the ati11. It shows the modulations used in that connection.
My Courier has all of these....
V.22bis, V.32, V.32bis, V.32terbo, V.FC, HST, X2, V.90 plus a few
more...
>
>> And here is what I got at OneNet...
>>
>> ati6
>> Line Reversals 0 Blers 1
>> Link Timeouts 0 Link Naks 1
>
>The connection did not seem to be bad at all for the 53 second
>connection. However, the modems data compression is disabled (&K0)
>during my previous connections and you Courier is using V42BIS
>compression. Just wondering if the modems data compression make any
>real differences.
The data compression being off can make a difference in throughput on
non-compressed files or when playing Quake and some other online games.
I leave compression on because I don't play online games and I think it
speeds up some web pages (probably wrong about that but it doesn't slow
them down anyway).
I left the Bler and Link nak count because that seemed odd for a 53
second connection. the Bler is not iunexpected but the Link Nak is...
unless it came about as a result of the Disconnect which was done by my
dropping DTR (and even that seems odd).
See my other post regarding the modem info on USR modems from OneNet...
Robert A. Clarke
I have a stupid question (Please note that I am NOT a technical person re:
modems or computers in general). I have been in contact with 3Comm and USR
for the past couple of weeks. I connect at 46,ooo-42,000 however I cannot
read newsgroups, mail or get anywhere on the net without timing out or
getting cut off (No connection to the server). I posted a message on this
newsgroup approx. 1 week ago (Mr. Knipfer gave me some info.). I have been
on USR/3COMM and will not let up until my problem is solved or I get a
refund for my V.90 upgrade. USR/3COMM asked me for the info. that you are
displaying on this post. How do I get this while I am connected to OneNet ?
I was trying to use Rapid Comm (USR software) and It wouldn't let me type in
the ATI2, ATI4, etc. (Are these commands ?) Thanks !!!
Bob
John C. Buschmann
Try typing +++ first. Your modem should answer back OK. Then type ati6 or
ati11 to get your status.
Robert A. Clarke <rcl...@one.net> wrote in article
<3585a...@news.one.net>...
Hooda Gest
Robert A. Clarke wrote in message <3585a...@news.one.net>...
>I have a stupid question (Please note that I am NOT a technical person
re:
You actually have two questions, one is disguised as a problem...
>modems or computers in general). I have been in contact with 3Comm and
USR
>for the past couple of weeks. I connect at 46,ooo-42,000 however I
cannot
>read newsgroups, mail or get anywhere on the net without timing out or
>getting cut off (No connection to the server).
That is a problem with server configuration with your ISP *unless* you
mean the modem is getting disconnected from the ISP rather than "No
connection to the server."
If you are using *any* of the init strings for USR/3Com provided by
One.Net, you are not helping yourself. Fall back to AT&F1 or let the
.INF file dictate the string (it's perfectly fine). OneNet is using a
beta firmware for its server, you must expect some problems from time to
time. It is not USR's fault if there is some compatibility problems with
PM3 firmware, they do not make that unit nor provide the firmware. There
may be some line problems on the server side but that isn't clear yet.
> I posted a message on this
>newsgroup approx. 1 week ago (Mr. Knipfer gave me some info.). I have
been
>on USR/3COMM and will not let up until my problem is solved or I get a
>refund for my V.90 upgrade. USR/3COMM asked me for the info. that you
are
>displaying on this post. How do I get this while I am connected to
OneNet ?
>I was trying to use Rapid Comm (USR software) and It wouldn't let me
type in
>the ATI2, ATI4, etc. (Are these commands ?) Thanks !!!
As Richard said, you need to use the escape code (three pluses) to go
into command mode. This should have been explained in your modem manual
in regard to switching between online and command modes. Once you are in
command mode, you will get an "OK". At that point you can begin entering
commands and capturing the displays. Make sure you get all the displays
that USR requested. I am sure they want ati4, ati5, ati6, ati7, ati11
along with one or two more.
You also ought to consider going online in your normal way and when you
get dropped off (assuming you meant disconnects from the ISP above) then
enter the commands right after calling up Rapidcomm. that will give you,
in the ati6 display, the reason for disconnect which will be important
information.