Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: adslmax on January 29, 2019, 08:26:58 AM
-
I have noticed that my FTTC drop to low SNR but getting more errored seconds on downstream rather than upstream which it rather seem strange and odd. SNR keep drop to low 4.7dB and went back up to 6.2dB every minutes for 46 minutes now. Should I concerning that DLM might act overnight due to downstream errored seconds as it never happen before as my modem still ongoing connection for 123 days without no issues with no DLM.
xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 4.7 10.7
Attenuation (dB) 11.6 0.0
Output Power (dBm) 12.5 0.0
Attainable Rate (Kbps) 77437 23018
Rate (Kbps) 80000 19999
Interleave depth: 8 1
INP: 49.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 3.0741 63.7808
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 8.83 0
Signal attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
29 Jan 2019 08:00:33 2.7 13.0 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:00:52 2.7 14.7 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:01:12 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:01:32 2.7 13.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:02:12 2.7 14.1 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:02:32 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:02:51 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:03:12 2.7 14.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:03:32 2.7 14.2 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:03:52 2.7 14.6 19.5 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:04:12 2.7 14.2 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:04:32 2.7 13.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:04:52 2.7 13.9 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:05:12 2.7 13.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:05:32 2.7 14.1 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:05:52 2.7 13.8 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:06:12 2.7 13.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:06:32 2.7 13.7 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:06:52 2.7 13.8 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:07:12 2.7 13.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:07:32 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:07:52 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:08:12 2.7 14.3 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:08:32 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:08:52 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:09:12 2.7 13.8 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:09:32 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:09:52 2.7 13.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:10:12 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:10:32 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:11:12 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:11:32 2.7 13.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:11:52 2.7 13.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:12:12 2.7 14.3 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:12:32 2.7 13.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:12:52 2.7 14.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:13:12 2.7 14.1 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:13:31 2.7 13.8 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:13:52 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:14:12 2.7 14.4 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:14:32 2.7 13.4 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:14:52 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:15:12 2.7 13.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:15:32 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:15:51 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:16:12 2.7 13.8 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:16:52 2.7 13.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:17:12 2.7 13.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:17:32 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:17:52 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:18:12 2.7 13.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:18:32 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:18:52 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:19:12 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:19:31 2.7 14.5 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:19:51 2.7 13.3 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:20:11 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:20:32 2.7 14.4 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:20:52 2.7 14.8 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:21:12 2.7 14.3 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:21:31 2.7 13.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:21:52 2.7 14.2 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:22:12 2.7 13.8 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:22:32 2.7 13.3 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:22:52 2.7 14.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:23:32 2.7 14.5 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:23:52 2.7 14.8 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:24:12 2.7 13.7 19.5 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:24:32 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:24:52 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:25:12 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:25:32 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:25:52 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:26:12 2.7 13.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:26:32 2.7 13.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:26:52 2.7 13.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:27:12 2.7 14.3 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:27:32 2.7 14.4 19.5 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:27:52 2.7 14.1 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:28:12 2.7 14.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:28:32 2.7 13.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:28:52 2.7 15.0 19.5 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:29:12 2.7 14.0 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:29:32 2.7 13.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:29:52 2.7 14.2 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:30:12 2.7 14.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:30:32 2.7 14.3 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:30:52 2.7 14.1 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:31:32 2.7 13.6 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:31:52 2.7 14.4 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:32:12 2.7 13.2 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:32:31 2.7 13.7 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:32:52 2.7 13.9 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:33:12 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:33:32 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:33:51 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:34:12 2.7 14.3 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:34:32 2.7 14.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:34:52 2.7 13.9 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:35:12 2.7 14.2 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:35:32 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:35:52 2.7 14.8 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:36:12 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:36:32 2.7 14.2 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:36:52 2.7 14.5 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:37:12 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:37:32 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:37:52 2.7 15.0 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:38:12 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:38:32 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:38:52 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:39:12 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:39:32 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:39:52 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:40:12 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:40:31 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:40:52 2.7 13.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:41:12 2.7 14.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:41:32 2.7 14.1 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:41:52 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:42:32 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:42:52 2.7 14.4 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:43:12 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:43:32 2.7 14.2 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:43:52 2.7 13.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:44:12 2.7 14.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:44:32 2.7 14.6 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:44:51 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:45:32 2.7 15.2 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:45:52 2.7 13.5 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:46:12 2.7 14.7 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:46:32 2.7 14.0 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:46:52 2.7 14.7 19.5 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:47:11 2.7 14.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:47:32 2.7 13.3 19.4 N/A N/A 9.0 15.7 26.4
29 Jan 2019 08:47:52 2.7 13.2 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:48:12 2.7 13.9 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:48:32 2.7 13.3 19.4 N/A N/A 8.9 15.7 26.4
29 Jan 2019 08:48:52 2.7 14.3 19.4 N/A N/A 8.9 15.7 26.4
Since 59 min 49 sec
FEC: 5432696 5325
CRC: 83 0
ES: 9 0
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
No need to worry about DLM intervention with those error rates - you'd need to be up at 60-120 ES/hour (depending on your ISP) to be in the red.
-
No. That's perfectly normal.
-
I can't remember what are the maximum FEC, CRC, ES, SES are allow per hour without DLM might trigger?
-
You are miles short. A one-off burst of ES isn't going to trigger anything so don't worry about it: you're fine.
-
Since Link time = 5 hours 11 min 51 sec
FEC: 26707274 34896
CRC: 448 1
ES: 54 1
SES: 9 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
FEC & CRC is getting very high but very strange as Errored seconds used be loads on upload but not today as it revert to downstream ES as 54 count in 5 hours today. As Downstream usually have no ES before today.
[attachment deleted by admin]
[attachment deleted by admin]
-
Agree that those numbers aren't as good as your line used to be, but they are still a long way short of being anything to worry about.
My line runs at anything between 400 and 900 ES per day, and has done for a long time. DLM is quite happy with those numbers and takes no action.
I would ignore the FEC number as they are errors that have been fixed - ie didn't happen.
:)
-
24 hours are 324 errored seconds and 39 serverly errored seconds on downstream. So far no DLM act. But, I do think my FTTC cabinet are now target SNR 3dB in place? I am not sure.
-
I'm not too sure, Max. It might still be on a 4 dB target SNRM and the DLM process is still considering the various counters & errors that your circuit is accumulating.
When it does react, it will either be down to a 3 dB target or back up to a 5 dB target. Perfectly logical. ;)
I seem to remember you saying that there was some work occurring at the cabinet . . . Hence I wonder if that work has moved the tie-cable bundles somewhat and, in doing so, the pair that your service is using has ended up closer to some other circuit which is now causing the disturbance. If that is the case, nothing can be done about it . . . it's the luck of the draw!
-
burakkucat - it appear that errored seconds has slowly fade away just after 2pm today. SNR now varies from 6.2dB and 5.2dB.
[attachment deleted by admin]
-
Ah yes, so they have. It looks as if they were the effect of some external disturber . . . which was then turned off.
Other than by looking at the various plots, do you actually notice any degradation in the quality of the service you are receiving? Does it stop you doing "things" via your connection? If the answers are "no" and "no" then don't worry too much about it.
I can manage with the following --
[bcat ~]$ speedtest-cli --simple
Ping: 60.456 ms
Download: 4.23 Mbit/s
Upload: 1.10 Mbit/s
[bcat ~]$
-
There is no degradation in the quality of the service for 125 days now still on 80/20.
-
That is an excellent achievement! :)
-
Okay I'm curious: how did you know the SNR had dropped if there were no changes to the service you were receiving? :)
-
Not for long thought. Because the max rate has dropped below 77Meg if it was re-sync then it probably drop to around 74Meg unless SNR target 3dB if this happens sooner or later due to crosstalk.
-
Okay I'm curious: how did you know the SNR had dropped if there were no changes to the service you were receiving? :)
The graphic telling me plus it alert me in email that snr has dropped below 4dB warning.
My parents line is already on SNR 2dB for the last 10 days since 3dB target SNR on their line to increasing sync rate to 69Meg but their FTTC cabinet is different to mine. Their is PCP 9 and mine is PCP 8 both on same exchange Cuckoo Oak.
-
The errored seconds has suddenly disappear overnight with ZERO on both downstream and upstream but SNR now varies between 6.3dB and 5.2dB. Still no change to the G.INP, Interleaved and INP with very low retx and no DLM so far. :) Still at 80/20.
-
DLM has made a change to my line this afternoon after 1pm - but why is both interleaved ON?
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 8.1 15.9
Attenuation (dB) 11.4 0.0
Output Power (dBm) 12.5 -0.1
Attainable Rate (Kbps) 87144 28714
Rate (Kbps) 80000 20000
Interleave depth: 8 8
INP: 49.00 49.00
G.INP: Enabled Enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0000 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Since Link time = 6 hours 30 min 59 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
-
Because retransmission is now enabled on both the downstream and upstream, and that's how the Huawei cabinets do retransmission (with D=Q).
-
I thought fttc only enabled interleave on Downstream only?
-
You thought wrong, and I don't know why you're still concerned about the interleave. You've got retransmission (G.998.4 / G.INP).
-
I always flavour in fast path rather than interleave but I ain't complaint as long it still 80/20 with no errors on the line
-
My line has resync this morning
Downstream Upstream
Line attenuation (dB): 11.6 0.0
Signal attenuation (dB): Not available on VDSL2
Attainable Rate (Kbps) 80044 26907
Connection speed (kbps): 74000 19999
SNR margin (dB): 6.0 15.0
Power (dBm): 12.5 -0.1
Interleave depth: 16 1
INP: 48.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
Why is my line capped at 74Meg?
-
Because you keep resyncing it to get a slightly higher sync?
No idea why you were complaining about "interleaving" on the upstream.
That was G.INP on the upstream.
I can only wish my line would apply G.INP to the upstream.
-
Maybe I will ask PN to get openreach out and get it DLM resetted. I feared now that it will be cappd at 74Meg for a long while now. My own fault for re-apply higher by putty adsl configure --maxDataRate 90000 20000 100000 and now end up at 74Meg capped by DLM. Bras IP Profile are now reduced from 77.35Mbps to 71.55Mbps. Getting throughput speed of 68Meg now.
Because I thought interleave at upstream are bad could leads to reduced SNR target 3dB?
PN send me GEA Test result for my line last Monday below:
Estimated Line Length In Metres 257.9
Upstream Rate Assessment Very Good
Downstream Rate Assessment Very Good
Interference Pattern Regular Interference Observed on Week Days
Service Impact No Impact Observed
Interference Duration Longest Occurrence From 10:45 to 12:30
Interference Location Customer Premise
Interference Observed In Days 2
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Profile Name 0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2019-01-16T15:45:00
Parameters MIN MAX AVG
Down Stream Line Rate 80.0 Mbps 80.0 Mbps 80.0 Mbps
Up Stream Line Rate 19.9 Mbps 19.9 Mbps 19.9 Mbps
Up Time 899.0 Sec 900.0 Sec 899.9 Sec
Retrains 0.0 0.0 0.0
Current and Last 15 Minute Bin Performance
Parameters Last Traffic Count(Upto 15 mins) Current Traffic Count(Upto 15 mins)
Start Time Stamp 2019-01-29T15:23:39Z 2019-01-29T15:38:39Z
Ingress Code Violation 1 0
Egress Code Violation 18 2
Errored Seconds 6 2
Severely Errored Seconds 0 0
Unavailable Seconds 0 0
Got email from follow the pages:
Changed:
- Max Observed Downstream Speed (Mbps) 80.00
... into:
+ Max Observed Downstream Speed (Mbps) 74.00
Changed:
- Observed Date 2019-01-29
... into:
+ Observed Date 2019-02-03
-
What's the low end of your estimated speed? Well I suppose if 74Mb isn't below the low end of the estimate, you could just temporarily cap the speed to below the estimate for Plusnet to book the openreach visit.
Maybe Plusnet could try the remote DLM reset trial, although I wouldn't know if the line being banded for however many hours it will have been banded for by the time you ask would be enough.
-
Here is my DSL Checker below
-
Then I expect you'll have difficulty getting plusnet to send out Openreach while the speed is within the estimate.
-
If I set this capped by putty - adsl configure --maxDataRate 60000 15000 60000 to get the line sync rate of 60Meg then maybe PN will send out engineer out to resetted DLM?
-
Yes, pick some nice round numbers to make it blatantly obvious what you've done. Perhaps Plusnet should send you a Hub One if you don't already have one, and insist that you use it.
-
I used to have Hub One I hate it and I binned it last year. Worse Hub ever! I prefer my own VDSL for modem only the Billion 8800NL and connect to TP Link for wireless only.
I did try putty to get higher rate eg: adsl configure --maxDataRate 100000 20000 100000 and it didn't work as it still at 74Meg capped sound like DLM is locked 74Meg banded at the exchange. :(
Is there any tweak to get the banded removed?
-
I'm sure I read somewhere that the third number in that command has to be equal or greater than the first two numbers together.
adsl configure --maxDataRate 100000 20000 100000.
You should have just left it as is. DLM probably wouldn't have touched you with the low errors you were getting anyway.
-
:no:
No
Stop resyncing the line. Every time you resync DLM is likely to make the banding worse.
Why why why would you at a cap of 90Mb.
The cap is already 80Mb so setting 90Mb simply resyncs your line while doing NOTHING.
I don't think you should be setting a cap to trick your ISP in to sending an engineer. The engineer will simply plug his own device in (which doesn't have the cap you set) and you will get a £130 charge because your equipment is at fault.
If Plusnet won't request a remote DLM reset then you're stuck with it.
Your banding won't show on a GEA test till 16th February.
You have nobody but yourself to blame.
You continued to fiddle with your perfectly operating line simply because DLM enabled G.INP on the upstream.
I wish I had 74/20
I get 45/7 on a good sync.
-
It's my own fault and myself to blame! Ah well I shall leave it alone now and see how long it take to get back to 80/20. Probably in 6 months time or never will be. :( :(
I kicked myself to the wall.
But, I just wish Openreach DLM should scrap unfair banded on the line because it too cruel to have lower speed.
-
I would love g.inp to go active on my upstream.
Hopefully it relents quickly for you and can go back to normal.
-
Next time if G.INP enabled on both downstream and upstream at 80/20 I shall leave it alone and stop messing with putty sent to exchange to cap the line at 90Meg. (Maybe I don't know what I am doing or fiddle around with putty thing)
I feel guilty now :( :-[
-
Hopefully it relents quickly for you and can go back to normal.
I do hope so! But I don't think so cos last year I have my line capped at 74Meg and it took 3 months to get it removed by PN DLM Resetted by remotely trial.
-
Next time if G.INP enabled on both downstream and upstream at 80/20 I shall leave it alone and stop messing with putty sent to exchange to cap the line at 90Meg. (Maybe I don't know what I am doing or fiddle around with putty thing)
I feel guilty now :( :-[
That's why i don't really do anything with equipment unless I fully understand what is going on and what the outcome will be.
-
Quick fix will be placed a new order for 2nd line with 80/20 if I placed the order tomorrow but not with PN thought. Different ISP.
-
Max – a few questions
Which ISP are you thinking of placing this order with?
How much time do you have left on your Plusnet contract?
Can you afford to pay 2 lots of line rental and 2 VDSL connections?
Kevin
-
My contract with PN end in this October but PN got billing issues and got no bills since last September 2018 and PN haven't resolved the biling yet and still unknown how long it will take PN to sort out the billing issues. So, I paying no bill for five months with PN. Cos PN has suspended my direct debit on my account.
The new ISP I am thinking will be Aquiss because of six months 50% off for fibre 80/20 on offer.
I just saw on other forum that BT has warned the FTTC line will drop if u mess with your modem tweak. BT say to keep your modem on all the time, in order to stop complaints of fluctuating speeds.
-
I do hope that you’ve set the money aside to pay them. They have provided you with a service and you’ve been using it. I’m no legal expert but I would imagine that they could ask you for full or discounted payment when they realise they haven’t billed you.
My advice would be to pester and pay them unless you can afford to pay up when the bill eventually comes in otherwise you could have debt collectors at your door.
As for the second line don’t do it unless you can actually afford it, I’ve seen too many people begging for overtime because they’ve had a few good weeks and over-stretched themselves.
Kevin
-
These are bloody very good https://communityfibre.co.uk
Basic
£20/month
download & Upload40 Mbps
Average speed: 40 Mbps download and upload
UltraFast
£35/month
download & Upload200 Mbps
Average speed: 200 Mbps download and upload
GigaFast
£50/month
download & Upload1,000 Mbps
Average speed: 920 Mbps download and upload
I wish my area have that unless I get myself involved and do a door to door everywhere in my area with a leaflet to register interest to get away from virgin media cable, sky, talktalk, bt, plusnet fttc. Why pay more for less speed with virgin & openreach rip off?
-
Max, do your remember, some months ago you agreed to stop obsessing over your broadband connection to the Internet and, instead, just use the service for normal purposes? :-\
If you continue with this current obsession, I fear that you will make yourself ill, once again. :(
-
I am going to put a cease order on the line tomorrow. Had enough now. I don't need broadband anymore.
-
That is also a bit extreme . . . :o
Do something else, by all means. Then, tomorrow, having "slept on it" review your latest decision.
-
This month will be my fibre cabinet 'happy birthday' 5 years old FTTC since my fibre went live by PN in February 2014.
Below is my 1st day of FTTC back five years ago.
I off to bed now cos I haven't been well enough in the last few weeks severe depression again with mental illness hits me again. I hate my life!
-
This month will be my fibre cabinet 'happy birthday' 5 years old FTTC since my fibre went live by PN in February 2014.
Below is my 1st day of FTTC back five years ago.
That's interesting to know. :)
I off to bed now cos I haven't been well enough in the last few weeks . . .
It is already tomorrow and I, too, should really find my bed.
. . . severe depression again with mental illness hits me again. I hate my life!
I appreciate that everything just appears either black or white, without any intermediate shade. However there is a mid-point between those two extremes. (Yes, I have also been "there".)
This month of the year, the weather, etc, all contribute to that negative feeling. However if you go out for a walk and take note of other people's front-gardens, you will notice the tips of bulbs already beginning to show. That is nature's way of telling you that things will slowly improve.
So no impulsive decisions, please.
-
I am eating fish and chips at my local area chippy shop and suddenly email alert me of my fttc has changed make me happy now :)
Changed:
- Observed Date 2019-02-03
... into:
+ Observed Date 2019-02-04
But I can't see my router stats until I get home to check what speed now
-
Grrr come home to check the router stats still no change in sync rate. Still bloody capped at 74Meg. :(
-
Max - please please just leave it alone.
74Meg is a great speed, and one that many (most?) can only wish for.
If it's working ok for day to day use - ie surfing the net, gaming etc then just use it and be happy that you've got a faster connection than the vast majority.
Try to focus your energy on something else, as this really isn't worth getting worried about.
:)
-
:) :) Yes finally at last DLM hasd just resync my line just a minute ago itself
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039g1.d24m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 0 min 45 sec
Resyncs: 1 (since 03 Feb 2019 07:29:50)
Downstream Upstream
Line attenuation (dB): 11.6 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 80000 19999
SNR margin (dB): 6.3 15.2
Power (dBm): 12.5 0.0
Interleave depth: 8 1
INP: 49.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0000 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Attainable Rate (Kbps) 81583 28026
-
Good stuff max!
Now just no fiddling!!
How was your fish and chips? You made me hungry speaking about that!!
-
To be honest I am so shocked as never expected that DLM put me back on 80/20. Removed capped. Thought it could be waiting game for 3 months or never will be removed off.
I better LEAVE IT ALONE! The putty now uninstalled from my laptop.
Yep I did enjoyed fish & chips with lovely curry sauce. :)
[attachment deleted by admin]
-
That sounds like a good idea!
Great! Guess I'll be going for something similar when I get home later in the week.
-
:) :) Yes finally at last DLM hasd just resync my line just a minute ago itself
. . .
Connection speed (kbps): 80000 19999
. . .
Attainable Rate (Kbps) 81583 28026
What a difference a day makes. :)
-
I know I am shocked can't believe it. Once it banded capped the line I thought I have to wait for at least 3 months or much longer. But I think DLM knew it wasn't 20 retrains like last year what it did banded my line for 64 days before PN have requested via BTw to resetted DLM remotely.