Unimodem Diagnostics & Windows 2000/XP modemlog
Franc Zabkar
(AT#UD). Furthermore, Windows 2000 and XP both support automatic
logging of #UD reports in the modemlog file after hangup.
Unfortunately, few, if any, modem vendors supply properly coded INF
files for their modems, resulting in either no diagnostic report at
all, or a corrupted one containing unrecognised responses such as the
following from a Dynalink/Lucent log:
02-25-2004 18:15:43.953 - Recv: DIAG <2A4D3263 00 = 09><cr><lf>DIAG
<2A4D3263 01 = 07><cr><lf>DIAG <2A4D3263 02 = 00><cr><lf>DIAG
<2A4D3263 03 = 00><cr><lf>DIAG <2A4D3263 04 =
"6517942A0D27B6"><cr><lf>DIAG <2A4D3263 05 =
"C16513942A8D4710"><cr><lf>DIAG <2A4D3263 10 = 08><cr><lf>DIAG
<2A4D3263 11 = 0E><cr><lf>DIAG <2A4D32
02-25-2004 18:15:43.953 - Unknown Response
To enable such a report, users can either edit their registry or
modify their INF file. The second method necessitates a reinstallation
of the modem, while the first does not.
To modify the INF file, add the following entries:
HKR, Responses, "DIAG ", 1, 9e, 00, 00,00,00,00, 00,00,00,00
HKR, Responses, "<cr><lf>DIAG ", 1, 9e, 00, 00,00,00,00, 00,00,00,00
Also edit the Properties key if necessary by setting bit 11 of the 6th
double word to 1, as in the following example.
Original:
HKR,, Properties, 1, 80,01,00,00, FF,00,00,00, FF,00,00,00,
07,00,00,00, 0F,00,00,00, F7,07,00,00, 00,C2,01,00, C0,DA,00,00
Modified:
HKR,, Properties, 1, 80,01,00,00, FF,00,00,00, FF,00,00,00,
07,00,00,00, 0F,00,00,00, F7,0F,00,00, 00,C2,01,00, C0,DA,00,00
Note that in the original key the 1st double word is "80,01,00,00",
and the 6th is "F7,07,00,00".
Bit 11 is identified as follows:
F7,07,00,00
^^
0000 0111
^
bit 11
After these changes are made, and the modem is reinstalled, the
modemlog will produce a list of correctly parsed DIAG responses
together with a decoded diagnostic report.
The following excerpt is reproduced from logeng.txt in this archive:
http://www.connect.kiev.ua/files/mltr020.rar
08-14-2001 13:41:41.512 - Send: at#ud<cr>
08-14-2001 13:41:41.602 - Recv: <cr><lf>DIAG
08-14-2001 13:41:41.602 - Interpreted response: Diagnostic Info
08-14-2001 13:41:41.612 - Recv: <2A4D3263 0=10 1=7 2=0 3=0
4="C1651310270D" 5="C16513108
08-14-2001 13:41:41.612 - Recv: <cr><lf>DIAG
08-14-2001 13:41:41.612 - Interpreted response: Diagnostic Info
08-14-2001 13:41:41.612 - Recv: <2A4D3263 10=39 11=11 12=E0 13=00
14=06 15=00><cr><lf>
<more DIAG lines snipped>
08-14-2001 13:41:41.932 - Diagnostics
08-14-2001 13:41:41.932 - Modem Diagnostics:
08-14-2001 13:41:41.932 - Connect Response: ..CONNECT
40000/ARQ/V90/LAPM/V42BIS..
08-14-2001 13:41:41.932 - Version 1.0
08-14-2001 13:41:41.932 - Call Setup Result: Data Answering signal
detected
08-14-2001 13:41:41.932 - Multi-media mode: Data Only
08-14-2001 13:41:41.932 - DTE-DCE interface mode: Async data
08-14-2001 13:41:41.932 - V.8 CM octet string: "C1651310270D"
08-14-2001 13:41:41.932 - V.8 JM octet string: "C16513108D47658D"
08-14-2001 13:41:41.932 - Received signal power level (in -dBm): 57
08-14-2001 13:41:41.932 - Transmit signal power level (in -dBm): 17
08-14-2001 13:41:41.932 - Estimated noise level (in -dBm): 224
08-14-2001 13:41:41.932 - Normalized Mean Squared error: 0
08-14-2001 13:41:41.932 - Near echo loss: 6 dB
08-14-2001 13:41:41.932 - Far echo loss: 0 dB
08-14-2001 13:41:41.932 - Far echo delay: 9 ms
08-14-2001 13:41:41.932 - Round Trip delay: 9 ms
08-14-2001 13:41:41.932 - V.34 INFO bit map: 0x00fcab38
08-14-2001 13:41:41.932 - Transmit Carrier Negotiation Result: V.34
08-14-2001 13:41:41.932 - Receive Carrier Negotiation Result: V.pcm
(asymmetric)
08-14-2001 13:41:41.932 - Transmit Carrier symbol rate: 3200
08-14-2001 13:41:41.932 - Receive Carrier symbol rate: 8000
08-14-2001 13:41:41.932 - Transmit Carrier frequency: 1920
08-14-2001 13:41:41.952 - Receive Carrier frequency: 1920
08-14-2001 13:41:41.952 - Initial transmit carrier data rate: 31200
08-14-2001 13:41:41.952 - Initial receive carrier data rate: 40000
08-14-2001 13:41:41.952 - Temporary carrier loss event count: 0
08-14-2001 13:41:41.952 - Carrier Rate re-negotiation event count: 3
08-14-2001 13:41:41.952 - Carrier Retrains requested: 0
08-14-2001 13:41:41.952 - Carrier Retrain requests granted: 1
08-14-2001 13:41:41.952 - Final transmit carrier rate: 26400
08-14-2001 13:41:41.952 - Final receive carrier rate: 34666
08-14-2001 13:41:41.952 - Don't know to format (0x00000040,
0x00000003) for tag 0x2a4d3263
08-14-2001 13:41:41.952 - Error control frame size: 128
08-14-2001 13:41:41.952 - Error control link timeouts: 1
08-14-2001 13:41:41.952 - Error control link NAKs: 0
08-14-2001 13:41:41.952 - Compression Negotiation Result: V.42bis
08-14-2001 13:41:41.952 - Compression dictionary size: 1024
08-14-2001 13:41:41.952 - Transmit flow control: V.24 ckt 106/133
08-14-2001 13:41:41.952 - Receive flow control: V.24 ckt 106/133
08-14-2001 13:41:41.952 - Transmit characters sent from DTE: 4506
08-14-2001 13:41:41.952 - Received characters sent to DTE: 26050
08-14-2001 13:41:41.952 - Transmit characters lost (data overrun
errors from DTE): 0
08-14-2001 13:41:41.952 - Received characters lost (data overrun
errors to DTE): 0
08-14-2001 13:41:41.952 - Transmit Frame count: 328
08-14-2001 13:41:41.952 - Received Frame count: 291
08-14-2001 13:41:41.952 - Transmit Frame error count: 8
08-14-2001 13:41:41.952 - Received Frame error count: 76
08-14-2001 13:41:41.952 - Termination Cause: CCT108 Turned Off
- Franc Zabkar
--
Please remove one 's' from my address when replying by email.
William Scott
>Most modern modems support Microsoft's Unimodem Diagnostics command
>(AT#UD). Furthermore, Windows 2000 and XP both support automatic
>logging of #UD reports in the modemlog file after hangup.
>
>
>- Franc Zabkar
>
>
Where can I get a program to decode the DIAG lines.
William.
Franc Zabkar
<mwi...@optusnot.com.au> put finger to keyboard and composed:
http://www.rampitec.spb.ru/getfile.php?fnm=ud-1101.zip
I don't know about Win2K, but Win XP automatically decodes the DIAG
lines at the end of the modem log.
Franc Zabkar
<mwi...@optusnot.com.au> put finger to keyboard and composed:
>Franc Zabkar wrote:
http://www.rampitec.spb.ru/index.htm?modem
See "Windows XP® log Rockwell statistics recovery, v1.0"
http://www.rampitec.spb.ru/getfile.php?fnm=s1xplg10.zip
Bill Carson
http://www.modemsite.com/56k/diag.asp#ud
This page indicates some modems may be able to use the #UG command to
give a human readable report, but I have no experience with it, as my
modem's firmware doesn't support the AT#UG command.
My Windows XP log contains a human readable diagnostics report appended
to the modem log after each session. I have found that using the
Unimodem Diagnostics/W32 program by Stanislav Mekhanoshin at
http://www.rampitec.spb.ru/getfile.php?fnm=ud-1101.zip doesn't give
me as complete a diagnostics report as XP does, but I may not be using
it right.
You might also be interested in Microsoft's Unimodem Diagnostics info
at this page: http://www.microsoft.com/whdc/hwdev/tech/network/modem/unimodem.mspx
That page contains a link to the Unimodem Diagnostics Command Draft
Reference Specification which you can download from here:
http://www.microsoft.com/whdc/hwdev/resources/specs/commspec.mspx
It may help you interpret your log output.
Bill
William Scott <mwi...@optusnot.com.au> wrote in message news:<405194a5$0$8355$afc3...@news.optusnet.com.au>...
William Scott
William.