Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: shaun1264 on August 22, 2017, 08:05:50 PM
-
Back in late May I changed Fibre supplier from BT to Plusnet with a view of getting faster speeds. I was on the upto 40 service with BT and with Plusnet 20/80 service. When I changed over I suffered quite a few errored seconds which resulted in interleaving being switched on on the downstream. Things settled down and I was put on fast path about 4 weeks ago now. Then large amount of errors happened again and back to interleaving.
Ive changed the Router to a VMG8924-B10A from a 8800Nl R2, changed router/modem cable to a short Cat6e, moved any electrical device away from router, changed face plate to a openreach mark 4, installed ferrite beads on electrical appliances cables. Currently im trialing a ADSL Nation xf-1e connected to test plug which ive seen a small improvement in ES and higher snyc. The upstream ES still happen (upstream on fast path and stuck around 7mbps. Perhaps capped) Snr seems to drop around 5.5db in the evenings.
Ive been uploading my stats on and off to mydslwebstats for a few days now. Username is shaun1264
Current Modem stats:
====================================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Disable
Traffic Type: PTM Mode
Link Uptime: 0 day: 7 hours: 42 minutes
====================================================================================
VDSL Port Details Upstream Downstream
Line Rate: 7.273 Mbps 42.293 Mbps
Actual Net Data Rate: 7.246 Mbps 42.217 Mbps
Trellis Coding: ON ON
SNR Margin: 6.1 dB 5.9 dB
Actual Delay: 0 ms 8 ms
Transmit Power: 4.3 dBm 12.5 dBm
Receive Power: -6.7 dBm -9.2 dBm
Actual INP: 0.0 symbols 3.0 symbols
Total Attenuation: 0.0 dB 21.8 dB
Attainable Net Data Rate: 7.242 Mbps 49.050 Mbps
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 6.8 35.6 54.6 N/A N/A 16.6 43.4 67.8
Signal Attenuation(dB): 6.8 34.8 52.0 N/A N/A 18.4 43.1 68.4
SNR Margin(dB): 6.1 6.2 6.1 N/A N/A 5.9 5.9 5.9
TX Power(dBm): 0.0 -7.1 1.5 N/A N/A 9.1 7.9 5.6
====================================================================================
VDSL Counters
Downstream Upstream
Since Link time = 42 min 35 sec
FEC: 267398 347
CRC: 58 62
ES: 17 54
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 54 sec
FEC: 6895 260
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 11630 7
CRC: 5 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 7 hours 42 min 54 sec
FEC: 267398 347
CRC: 58 62
ES: 17 54
SES: 0 0
UAS: 19 19
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Total time = 7 hours 42 min 54 sec
FEC: 267398 347
CRC: 58 62
ES: 17 54
SES: 0 0
UAS: 19 19
LOS: 0 0
LOF: 0 0
LOM: 0 0
===========================================================================
-
Why is there no G.INP on this circuit ?
-
Good question how long does it take for first G.INP to be applied. In the order of weeks, I think.
-
From reading on here anything from 5-8 weeks.
-
Depends what date in May it was enabled.
-
Yep no G.IMP. Its never been on .
Sometimes I think Openreach are slow to enable G.IMP on cabinets round my area.
ive tried everthing to increase the speed too.
I did notice before I moved to Plusnet SNR went down to 3dB
-
I have seen instances of people migrating ISP and they start again wrt to 3db and G.INP Shaun.
-
Back in late May I changed Fibre supplier from BT to Plusnet with a view of getting faster speeds.
Yeap 7- 8 weeks but three months is taking the pee, or the DLM has got confused and needs reset
-
I have seen instances of people migrating ISP and they start again wrt to 3db and G.INP Shaun.
Thats interesting. Maybe G.INP was switched on soon after migrating but for whatever reason went off and not come back. I always thought I saw the 3db SNR just before the switch over.
-
We had a new line and service. 10 days from activation g.inp was enabled (cab1, combe down)
-
Would an TV antenna cable running parallel to the drop wire on the other side of the window cause ES? In the past the aerial wire has had static electric running through it.
-
No, it shouldn't.
Total time = 7 hours 42 min 54 sec
ES: 17 54
54 ES in almost 8 hours while on fastpath is absolutely nothing to worry about. In my opinion it's a very low amount of errors, nowhere near the DLM limits.
High ES should be expected on fastpath, and there's nothing you can do to stop them. Optimizing the internal wiring can only reduce them by a small amount, but your ES count is already low.
edit: I got the downstream/upstream mixed. still not a high amount of ES though. Nothing to worry about
-
The errored seconds should be low John as he/she is on interleaving INT:831 INP:3.00 DLY:8 but not on fastpath
-
I've been playing around a bit making sure the cable connectors are in firmly into sockets (which caused a resync and SES) and i've disconnected the phone which has a 3m RJ10 wire. This has resulted in no ES on the US and DS for 30mins now. Fingers crossed...
-
Don't see much you can now do at your end (internally) to improve your line, G.INP would help with ES and give you big boost of sync and also X target margin from 6dB to 3dB would give you a small boost if your line can hold on with a lower SNRM without starting to spew out unwanted ES.
-
Ok, things have been on the up. DLM seems to be making changes to SNR target. After three DLM resyncs I'm on a 4.0dB target profile. Speed increases to around 45mb currently. ES increasing slightly now but still within limits.
Still no G.IMP
-
Quick question on ES?
I randomly had a spike at 5pm yesterday evening which tool the ES too over 100. I've tried searching as to what causes ES but there doesn't seem to be a definitive answer.
Could a faulty house-hold appliance cause ES?
I turned off and unplugged all appliances in the house to see if anything was causing issues at 5pm. As the SNR and sync didnt increase I plugged everything back in.
Could this have caused the spike or something else?
spike can be seen on MDWS around 17.13pm yesterday (31st)
Thank in advance.
-
ES = Errored Second
1 ES means there was a second-long period of time where errors were counted on the line. It is more of a statistical construct than anything else, and helpful for constructing a "mean time between errors" (MTBE) value.
The errors themselves are identified by failures in the CRC checksum process, and are counted in the CRC counter, and there can be many more CRC than ESs. A big burst of CRCs within one single second period is still only considered as 1 ES.
CRC errors are almost invariably caused by some noise/interference on the line. Which can indeed be caused by faulty appliances, or even just the act of turning things on or off.
-
Just a little update. DLM has been going crazy making positive changes. On one day I had two resyncs. G.INP is now on upstream aswell as downstream. SNR margins have been in the 4-5dB regions and speeds are around 51Mb currently. I did have 54Mb at one point when I was on the 4dB margin. After the rsync for G.INP to be added on upstream the snr went back to 5dB with a lower actual speed rate. Im sure that will drop back down soon.
It seems the DLM is reacting faster to line conditions these days.
Data is under shaun1264 in Mydslstats