Technicolor TG582n

What would one make of the following.

Output Power (Up/Down) [dBm] : 12,3 / 0,0

In isolation nothing

Depends on the rest of the stats (although I suspect the 0.0 down is a firmware error in displaying the stats).

Sorry for delay in replying.
The router stats as follows

DSL Connection 29/01/2015 16.55

Link Information

Uptime: 0 days, 19:18:42

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 888 / 4,800

Data Transferred (Sent/Received) [GB/GB]: 2.39 / 55.75

Output Power (Up/Down) [dBm]: 12.9 / 0.0

Line Attenuation (Up/Down) [dB]: 19.6 / 35.0

SN Margin (Up/Down) [dB]: 15.0 / 7.0

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / IFTN

Loss of Framing (Local/Remote): 990 / 0

Loss of Signal (Local/Remote): 113 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote):

Error Seconds (Local/Remote): 918,569 / 288

FEC Errors (Up/Down): 2,614 / 38,895,496

CRC Errors (Up/Down): 21 / 4,259,090

HEC Errors (Up/Down): 25 / 36,957,252

PlusNet have reset this connection and it now seems to be ok but these are the stats yesterday. By the way this is not my broadband but my niece's. I am with Sky.

DSL Connection 06/02/2015 20.55


Link Information

Uptime: 5 days, 12:49:57

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 888 / 3,431

Data Transferred (Sent/Received) [MB/GB]: 87.75 / 1.56

Output Power (Up/Down) [dBm]: 12.3 / 0.0

Line Attenuation (Up/Down) [dB]: 19.6 / 35.0

SN Margin (Up/Down) [dB]: 12.3 / 11.6

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / IFTN

Loss of Framing (Local/Remote): 18 / 0

Loss of Signal (Local/Remote): 2 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 139,051 / 0

FEC Errors (Up/Down): 26,948 / 1,408,387

CRC Errors (Up/Down): 212 / 149

HEC Errors (Up/Down): 223 / 379

A faulty router maybe ?

John

You hadn't suggested earlier that there was any problem.

Something is badly wrong with the speed. On ADSL2+ (G.992.5) at 35dB attenuation you expect more like 12Mbps or more.

Part of the slowdown in the new stats is the high downstream noise margin of 11.6dB. 6dB is more normal. We could do with seeing stats taken immediately after a reboot of the router.

The local error seconds are horrendous in the new ones and utterly ludicrous in the old ones.

Is it convenient to get to her premises to check a couple of things? Alternatively is she reasonably happy with minor electrical work like changing a fuse? Which isn't what I am thinking about, but is indicative of the difficulty of one of the checks - the ring wire at the master.

Then there are the questions of everything being filtered and so on. See Miscellaneous Nasties on the menu of that link.

Edited by RobertoS (Sat 07-Feb-15 11:41:03)

The old Be analysis page will work with those stats ...

http://be.nfshost.com/

It had this to say about them....

2 Loss of Signal Local errors. These are okay as rare one-offs, but should not occur regularly.

Expected download speed at your current sync rate: 365.00 KB per second (or 2920 kbit)

Expected upload speed at your current sync rate: 94.47 KB per second (or 756 kbit)

Problem: Downstream sync speed of 3431 kbit is 7034 kbit slower or 33 percent of the average for connections with the same downstream attenuation of 35dB.

Problem: Error Seconds are occurring with very high regularity (0.29/sec).

Problem: Output power down (0.0dBm) is very low. Most common values are 17 to 19.5dBm.

Problem: Signal Noise Margin Down (11.5dB) is extremely high. Be* may have put you on this profile to compensate for a high error rate. If you know that your line is actually reliable, lowering the value to the average of 6dB should give a sync speed increase. Call Be* to change it (3dB steps only).

Problem: Signal Noise Margin Up (12.5dB) is higher than average and may be this high in order to compensate for current/previous high error rates.

Problem: There are some FEC Up errors. FEC errors are *corrected* errors, so these are probably nothing to worry about. Speedtouch routers have a habit of misreporting FEC errors anyway.

Problem: Zillions (18) of Loss of Framing errors, which should ideally never or rarely occur. There must be (or have briefly been) a problem with your line.

I'd guess that the output power is just incorrectly reported for some reason. With those stats it's proably the least of your worries...