Yeah, that lasted about 4 hours, with lots of errors and the noise margin jumping around all over the place. It's re-synced at 10966kbps now and noise margin appears to be rock solid at 6dB. Curiously, attenuation has dropped to 38dB too. I wonder if 'someone' was doing something in the exchange or cabinet this morning. A couple of houses are very near completion on the estate now so it's feasable.

The Billion also arrived today so, that's configured and ready to go in. I just need to decide whether to do that tonight or put it in first thing tomorrow morning. That will get me the best sync and mean I'm not taking the link down unnecessarily...

Paul

*Edit* Looks like I've been switched over to FastPath. I wonder if that could be the reason for the resync and drop in attenuation?

Could be bursts of noise on the line - I generally have a really good connection but possibly occasional bursts of noise on the line cause lots of errors, hence the advice by Matt to have it interleaved.

Do you have RouterStatsLite running?

*Edit* Looks like I've been switched over to FastPath. I wonder if that could be the reason for the resync and drop in attenuation?

A change of path status from interleaved to fast (or the opposite) will, by necessity, cause a link re-sync.

I have a feeling that the errors were due to the line (and router) not being able to support that sync speed. I could be wrong though.
I do have RouterStatsLite but, it wasn't running at the time.

I've now got the Billion hooked up and unfortunately, it's showing an attenuation of 40dB. It's also onlt syncing at 8554kbps but, I expect that's down to the 8.9dB SNRM. So, I've raised a ticket with Vivaciti to set the target SNR at 6dB.

I'm definitely on FastPath too as a round trip to the BBC now takes 20ms, down from over 40ms.

The saga continues...

Paul

Reckon you'll just let it settle down now that you have the Billion on-line...

BTW. what are your upstream numbers like?

I think so. I just want it to settle down now so I can see how stable it is. I can always fiddle with the SNR at a later date.

With regards to upstream numbers, attenuation has more than doubled with 10dB being reported by the Netgear and 22.6dB being reported by the Billion. I guess it shows how (very) differently they report the figures...
Noise margin is currently 10.7dB (6dB with the Netgear) and it's syncing at 1023kbps. Throughput is static at 870kbps. That's comfortably double what my ADSL1 connection mustered.

I have RouterStatsLite running now and the downstream noise margin has very slowly reduced to 7.0dB. It's also still very slowly dropping.

Paul

Upstream numbers look perfect with the Billion - maybe the Netgear is a little confused by adsl2+ LOL!

Ha ha, yes, I think the Netgear was just confused full stop with the new connection.

Paul

If the Billion works with DMT (?) and you still feel that after a couple of days the downstream sync isn't optimised you may like to check for tone gaps. This is my DMT result done at 11pm this evening (05-07-12): http://farm9.staticflickr.com/8162/7510765556_cb458e...

Yes, DMT does work with the Billion. There's a 'special' version available.

A small update.

Vivaciti kindly lowered my target SNR this morning to 6dB. I checked and the router was sat at 6.1dB. Rather interestingly, attenuation has dropped by 0.5dB on the downstream and it's down to 20.9 on the upstream.
The sync with the 6.1dB SNR was 9915kbps which, is still a little 'slow' according to the various utilities around the web. So, I couldn't resist and dropped the SNR to 66% of original and thats now showing as 4.4 to 4.3dB. Sync has climbed to 10803kbps. Still a little 'slow' but, the resync was at around 10.55am where as in the past, I've seen optimum sync time as between 9am and 10am. I also think I need to give the line a chance to settle and not have a resync every 24 hours or less.
So that's what I'm going to do now. I'll monitor the SNRM and check the errors seen and see how the connection holds up.

Paul