Data Acquisition Configuration

After configuring telnet / HTTP options and successfully connect to your router you can run a trial data acquisition test by pressing the Test Connection push button. The file named preview.txt will be created in the root directory. You can use this file to find the line number and word position of the data you want to monitor. Line numbers and word positions start at 0.

ADSLMonitor defines words as a sequence of alphanumeric characters separated by any number of spaces and defines lines as strings separated by a carriage return linefeed pair or a blank line that contains only a carriage return linefeed pair (0xd / 0xa).

The following preview.txt is from a cisco 837 adsl router:

cisco837
dsl int a0
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
ITU STD NUM: 0x01 0x01
Vendor ID: 'ALCB' 'ALCB'
Vendor Specific: 0x0000 0x0000
Vendor Country: 0x00 0x0F
Capacity Used: 43% 49%
Noise Margin: 23.5 dB 16.0 dB
Output Power: 17.5 dBm 4.5 dBm
Attenuation: 49.0 dB 29.0 dB
Defect Status: None None
Last Fail Code: None
Selftest Result: 0x00
Subfunction: 0x15
Interrupts: 680 (1 spurious)
Activations: 6
Init FW: embedded
Operartion FW: embedded
SW Version: 3.9.220
FW Version: 0x1A04

Interleave Fast Interleave Fast
Speed (kbps): 0 3008 0 416
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 224 0 3
Header Errors: 0 120 1 2
Bit Errors: 0 108
BER Valid sec: 0 69688
BER Invalid sec: 0 149

LOM Monitoring : Disabled

DMT Bits Per Bin
00: 0 0 0 0 0 0 0 2 2 3 5 5 6 7 7 7
10: 8 7 7 7 7 7 6 7 6 5 5 4 4 4 0 0
20: 0 0 0 0 0 0 0 2 2 2 2 3 4 4 4 3
30: 4 4 5 7 7 7 7 8 7 7 4 6 7 8 8 9
40: 9 9 9 9 9 9 9 6 9 9 2 9 9 9 9 9
50: 9 9 9 8 8 8 8 8 8 8 9 9 9 9 9 8
60: 9 9 9 8 8 8 8 8 8 8 8 8 8 8 8 8
70: 7 7 7 6 5 4 2 5 6 6 7 7 6 6 6 6
80: 6 6 6 6 5 5 5 4 4 2 4 4 5 4 2 4
90: 2 4 4 5 4 5 5 4 5 3 4 4 4 4 4 4
A0: 4 4 4 3 3 2 2 3 4 2 2 3 2 2 2 2
B0: 2 3 2 3 2 2 3 2 2 2 0 0 0 0 0 2
C0: 2 2 0 0 2 2 2 0 0 0 0 0 0 0 0 0
D0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
E0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
F0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Training log buffer capability is not enabled yet.
cisco837
Listing1

From Listing 1.
We know that the noise margin information starts at line 9, the downstream value is word 2 and the upstream value is word 4. Power information starts at line 10, the downstream value is at word 2 and the upstream value is at word 4 and so on.

DMT matrices require careful inspection. Unlike the Cisco 837 some routers use byte format to display this information. Listing 2 is an example of this format.

tone 1  - 32 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 33 - 64 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 65 - 96 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 97 -128 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 129-160 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 161-192 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 193-224 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
tone 225-256 01 23 45 67 89 AB CD EF 01 23 45 67 89 AB CD EF
Listing2

From Listing 2.
We know that tones 1 trough 32 are located in the first line. Tone 1 and 2 occupy word 3, tone 3 and 4 occupy word 4 and so on. When it comes to tones 129 to 255 the format changes a little. Tones 129 and 130 occupy word 2, tone 131 and 132 occupy word 3.

The format for the DMT matrix can be customized by setting the correct values in the DMT Data is in byte format and the 32 tones per line checkboxes and entering the correct values in the coordinate fields.

The frame surrounding the Test Connection pushbutton will flicker blue and green when collecting statistical data. If there is a problem in this process it will change to red. The most common reasons for problems are:

• Conflicts with the telnet connection. ie Router only being able to handle one telnet client or timeouts.
• Out of bound words. ie Referencing the word n+1 in a string containing only n words.

If You are having out of bound word problems ADSL Monitor will report the problem in the Connection / Events log tab.


feedback Copyright © 2000-2017 by Dohrenburg Systems' Web Development Team.
Legal Stuff. Viewing of this website signifies your agreement.
Dohrenburg Systems Privacy Policy.
Please report any problems with this website to the Webmaster.
Last Update: December 2, 2014