Outdated Drivers
Can cause hardware related Errors. Check your PC Drivers now.

Motorola



  • Go to Start > Program > Accessories > Hyperterminal. (You can install Hyperterminal through Add/Remove Programs if you do not have it).


  • Click on the Hyperterm program.


  • Name the connection "Test" and click OK.


  • Enter the phone number for your ISP connection.


  • Ensure that it is set to be using your Motorola modem, and click OK.


  • Click Dial.


  • After the handshaking is done, you should see on the screen the word: "Login", though this does vary from ISP to ISP.


  • Wait a little while, say 15-60 seconds so you are connected for a bit.


  • Disconnect by using the pulldown menu under Call, then select Disconnect.


  • After you are disconnected, type AT#UD, press ENTER, and the following should appear with the 0's filled in:


DIAG <2A4D3263 0=0>
DIAG <2A4D3263 1=0 2=0 3=0>
DIAG <2A4D3263 4="0000000000000000" 5="0000000000000000">
DIAG <2A4D3263 10=0 11=0 12=0 13=0>
DIAG <2A4D3263 14=0 15=0 16=0 17=0>
DIAG <2A4D3263 18=00000000>
DIAG <2A4D3263 20=0 22=0 24=0 26=0>
DIAG <2A4D3263 21=0 23=0 25=0 27=0>
DIAG <2A4D3263 30=0 31=0 32=0 33=0>
DIAG <2A4D3263 34=0 35=0>
DIAG <2A4D3263 40=0 41=0>
DIAG <2A4D3263 42=0 43=0>
DIAG <2A4D3263 44=0 45=0>
DIAG <2A4D3263 50=0 51=0>
DIAG <2A4D3263 52=0 54=0>
DIAG <2A4D3263 53=0 55=0>
DIAG <2A4D3263 56=0 58=0>
DIAG <2A4D3263 57=0 59=0>
DIAG <2A4D3263 60=0>


Basic Analysis of AT#UD:

The AT#UD command was created by Microsoft as an attempt for a standard diagnostic screen. Unfortunately they did it in Hex, and most modems now support it, but for some modems it is one of the only ways to look for noise. The keys that we want to concentrate on are keys 10, 11, 14, and 12. Convert these numbers to decimal by using the following table:

           |
           |
           |
2nd digit->| 0   1   2   3   4   5   6   7   8   9   A   B   C   D   E   F
1st digit  |
     |     |
    \|/    |
----------------------------------------------------------------------------
     0     |  0   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15
     1     | 16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31
     2     | 32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47
     3     | 48  49  50  51  52  53  54  55  56  57  58  59  60  61  62  63
     4     | 64  65  66  67  68  69  70  71  72  73  74  75  76  77  78  79
     5     | 80  81  82  83  84  85  86  87  88  89  90  91  92  93  94  95
     6     | 96  97  98  99 100 101 102 103 104 105 106 107 108 109 110 111
     7     |112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
     8     |128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
     9     |144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
     A     |160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
     B     |176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
     C     |192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
     D     |208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
     E     |224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
     F     |240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
Key 10 is the Received signal power level, in -dBm. If the value represented displays over 30, then there may be signal problems with the phone line, however I have seen "impossible" values that are out of range from this field, so use caution if this is the only key that shows that there may be noise. The range for this field should be between 0 and 43.

Key 11 is the Transmit signal power level, in -dBm. This value should be between 6 and 16. If it is above or below this range there may be signal problems with the phone line.

Key 14 is the Near echo loss, in units of dB. This field indicates the transmit level that is being reflected at the telco hybrid. A normal value is around 30. If this value is in the 200's or higher there could a line problem.

Key 12 has been difficult for me to determine. It represents the Estimated noise level, in -dBm, however after testing a line with it a value of 50 was indicated. Lucent's Estimated noise level report would tell us that this is a very poor quality line as you would normally be dropped when 50 is reached, however this was done on a VERY clean line. I then took a USR and tested the line, getting an SNR of about 49.3. Thus it would be reasonable to assume that the Estimated noise level that is represented in this command displays the Signal to Noise Ratio, but this is not necessarily a FACT, but just a hypothesis. This may not be correct however, as what I believe was a noisy line tested with this modem showed a number between 40-50. It may or may not be SNR and requires more research. So unfortunately this modem does not seem to have very positive/useful diagnostics at this point. If this is the case, the following table will help in determining what shape the line is in:


SNR Range (Note: SNR = Signal to Noise Ratio) Expected "Stable" Speed
40+ 33,600 - 56,000
37-40 33,600-56,000 (a little unstable at high speeds)
34-37 31,200-33,600
31-34 28,800-31,200
29-31 26,400-28,800
28-29 24,000-26,400
25-28 16,800-24,000
23-25 14,400-16,800 (NOTE: If your SNR is around this level or lower the FCC may step in if your telco won't fix it, this level is not required to be supported, but often is by local teclos and must be upheld if in their charter.)
21-23 12,000-14,400
18-21 9600-12,000 (NOTE: If your SNR is around this level or lower the FCC will step in if your telco won't fix it, this level is REQUIRED, BARE MINIMUM support.)
14-18 7200-9600
13-14 4800-7200
6-13 2400-4800
1-6 300-2400 if you are lucky enough to connect.







This page was last modified on Saturday, 05-Feb-2011 15:13:38 EST.




 
This website is ©1999-Present Bradford Liedel DBA ModemHelp Networks and Web Services. Mason, MI 48854 USA. All rights reserved.