I will give them a call again in a few days - but now I am back on the cisco kit, it seems to report more 'real' data. The TP-Link router showed no connection errors - but the Cisco does.

And just watching the d/l SNR is worrying me - it swings from 19dB to 13 dB (on the current connection) in seconds (and anywhere in between).

I am getting worried now, as I live in a small block of flats, it might be the neighbours fridge or something that is causing the issue as the wire seems to run down through the wall in the stairwell close to all the other 3 flats under me.

NIck

P.S as to my connection 'banded profile' - does that get auto-reset after 3 days?

Edited by deleted (Mon 04-Mar-13 17:36:25)

Guess the neighbour's fridge could be causing a noise issue...

Banded profile: all I know is that for lines which drop frequently, a banded profile can be applied, which will restrict a line's connection speed from connecting at a level which it can't maintain - and sorry, I don't know about an auto-reset after 3 days, others on this forum may know or check with your ISP.

Just had another disconnect at 14:33... and result is:

Download speedachieved during the test was - 1.99 Mbps
 For your connection, the acceptable range of speeds is 0.8 Mbps-2 Mbps.
 IP Profile for your line is - 2 Mbps

I really do give up.

Nick

Is the phone working OK in the test socket? If so can you hear any noise on the line when using a corded phone (quiet line test: dial 17070.)

Sometimes very slow speeds can be caused by poor conductivity along one of the wires which form the incoming copper pair. In some cases the broadband may just about work but the phone does not...

Yes, all is fine - remember I had a BT engineer around last weds. he found a fault and fixed it, plus I got a new filter face plate in the deal.

I have plenty of cat5 lying around. Time to hang myself

Nick

In reply to a post by Lethe:

remember I had a BT engineer around last weds. he found a fault and fixed it

Yes he fixed it, but things seem to have deteriorated again since then - definitely time to chase up the ISP and report that the problem has reoccurred. Voice line is OK so it's certainly a broadband issue of some sort...

OK, after a long call to Enta techies (who have been very good, can't praise enough), it turns out this is the issue:

My line was bad, which the BT engineer fixed - but even after this, on ADSL2+ the DLM was seeing 100's of errors on the line a day - at my end I didn't see many (if any) errors at all except the one disconnect/resync randomly about every 24 hours.

Now, due to the way the DLM management software works on ADSL2+, due to all the errors it saw, every time I got a disconnect, it upped my SNR and stuck me on a 'banded' profile (nothing to do with ip profile). Thus the DLM still saw all these errors every day, so subsquently every disconnect/resync/reboot it implimented a higher SNR lower 'banded' profile to try to make my line stable.

Well, of course, all the time the errors persisted, I got a slower, and slower connection. Chicken and the egg situation.

Now it is only ADSL2/2+ that the DLM uses 'banded' profile to try to stablise the line - so now we are trying bog standard ADSL - so even if I do get a disconnect, I should be able to resync at whatever the line can do at that precise time (or a reboot during the day to get the speed up, etc.).

To change over to ADSL is a 24 hour process, but it happened at 02:21 this morning. Current stats:

Modem Status:	 Showtime (DMTDSL_SHOWTIME)
DSL Mode:	 ITU G.992.1 (G.DMT) Annex A
~
Capacity Used:	 100%				 99%
Noise Margin:	  8.0 dB			 11.0 dB
Output Power:	 18.5 dBm			 12.5 dBm
Attenuation:	 38.0 dB			 21.0 dB
~
 		 Interleave		Fast	Interleave		Fast
Speed (kbps):	          0	        7392	         0	         960
Cells:		          0	     1025737	         0	    46447242
Reed-Solomon EC:          0	           0	         0	           0
CRC Errors:	          0	         251	         0	           0
Header Errors:	          0	         203	         0	           1

I am keeping my eye on the CRC/Header errors, but they don't look too bad since 02:21 hours.

Nick
EDIT - BTW, forgot to say, before I went to bed last night, I hard set the Cisco router to sync using ADSL (itu-d.gmt) and there is a dsl command 'dsl noise-margin n', when 'n' is the range 3 ~ -3. I set this to '3' so that forces the router to sync 3dB higher than normal. So far appears OK.

Edited by deleted (Wed 06-Mar-13 09:34:09)

It appears to be on Fast Path - interleaving is normally the first thing to do if it's clocking up errors. May be worth a try.

Well (we have been here before) all looks good at the moment, so I will not touch *anything* to see how it goes.

I am polling my router stats (I will post graph later), and SNR looks the best for ages - as to the errors, they are clocking up slowly, but nothing to worry about, I think:

Interleave		Fast	Interleave		Fast
Speed (kbps):	          0	        7392	         0	         960
Cells:		          0	     2694769	         0	    75566610
Reed-Solomon EC:          0	           0	         1	           0
CRC Errors:	          0	         819	         2	          22
Header Errors:	          0	         703	         5	          21

So that is about 650 CRC errors, and 580 Header errors in 4 hours since I have been monitoring.

Nick
EDIT - to be honest, just checking, the errors do not seem to affect my line at all - I am getting a good through-put:

~ $ wget http://ipv4.download.thinkbroadband.com/200MB.zip
--2013-03-06 11:53:48--  http://ipv4.download.thinkbroadband.com/200MB.zip
Resolving ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)... 
Connecting to ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)|...
HTTP request sent, awaiting response... 200 OK
Length: 209715200 (200M) [application/zip]
Saving to: `200MB.zip'

100%[======================================>] 209,715,200  782K/s   in 4m 24s 

2013-03-06 11:58:11 (777 KB/s) - `200MB.zip' saved [209715200/209715200]

Edited by deleted (Wed 06-Mar-13 12:02:32)

Looks like interleaving is still not being applied - possible error with the page formatting of the latest stats posted on this site.

Throughput does look good: 777KB/s (6216Kbps)

Probably a noise source affecting the ADSL2+ frequencies, but ADSL1 will hopefully be more stable with a downstream ~9dB SNRM