Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: hucknallred on September 28, 2017, 11:17:10 AM
-
Hi
Long time lurker on here, now registered :)
This site is a great source of info so I thought I'd post my experiences of going from ADSL to VDSL.
I've had ADSL for years, switching annually to take advantage of cashback etc. I was with O2 who became Sky, then I went Plusnet>EE>Sky & now BT infinity. About 2Km from the exchange I got between 18500 & 21000 down, depending on supplier & router, although I have used a Billion 8800DN for the last few years.
With a good combination of prepaid card & cashback I decided to switch to BT, which came in around £12 a month after all the perks. My cabinet is a fair distance away, I estimated 1Km. Based on ADSL speeds I thought I'd get around 30000 down. An OR engineer who came to troubleshoot an incoming call fault after the switch (turns out VM who own the number hadn't released it) got the details on his app & told me it was 1150m to the cabinet.
So it went live a week last Tuesday, initially around 30 down & 7 up it's gradually dropped & seems to have settled on a specific 24999 down & just over 6000 up has crept up to 6500 today.
From the info on here I deduce it's an ECI cabinet, cabling is all underground from 1995 when the house was built.
So I'm wondering if I can hope for more speed, I'll post my router stats below. One thing I've noticed is downstream SNR was at 6dB at the start, went down a bit & has now crept up to 6.7dB. G.INP does not look to be active yet?
xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.7 6.2
Attenuation (dB) 28.6 0.0
Output Power (dBm) 6.4 6.3
Attainable Rate (Kbps) 32480 6624
Rate (Kbps) 24999 6537
B (# of bytes in Mux Data Frame) 31 204
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 62 5
R (# of redundancy bytes in the RS codeword) 10 16
S (# of data symbols over which the RS code word spans) 0.0407 0.9966
L (# of bits transmitted in each data symbol) 8264 1774
D (interleaver depth) 803 1
I (interleaver block size in bytes) 42 221
N (RS codeword size) 42 221
Delay (msec) 8 0
INP (DMT symbol) 3.50 0.00
OH Frames 37965583 8296660
OH Frame Errors 2550 5
RS Words 527132030 119337
RS Correctable Errors 12110 11
RS Uncorrectable Errors 14 0
HEC Errors 235 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 258643099 0
Data Cells 191536155 0
Bit Errors 0 0
Total ES 28 5
Total SES 11 0
Total UAS 57 46
From Telnet:
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 6634 Kbps, Downstream rate = 32477 Kbps
Bearer: 0, Upstream rate = 6537 Kbps, Downstream rate = 24999 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.7 6.2
Attn(dB): 28.6 0.0
Pwr(dBm): 6.4 6.3
VDSL2 framing
Bearer 0
MSGc: 36 33
B: 31 204
M: 1 1
T: 62 5
R: 10 16
S: 0.0407 0.9966
L: 8264 1774
D: 803 1
I: 42 221
N: 42 221
Counters
Bearer 0
OHF: 1519232 356214
OHFErr: 3 5
RS: 565057321 1670570
RSCorr: 14931 11
RSUnCorr: 14 0
Bearer 0
HEC: 2 0
OCD: 0 0
LCD: 0 0
Total Cells: 277248136 0
Data Cells: 197205743 0
Drop Cells: 0
Bit Errors: 0 0
ES: 28 5
SES: 11 0
UAS: 57 46
AS: 5768
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 3.79 16.25
OR: 88.51 19.19
AgR: 25087.52 6556.65
Bitswap: 12/12 0/0
Total time = 1 days 16 hours 9 min 35 sec
FEC: 739488 9158
CRC: 2550 5
ES: 28 5
SES: 11 0
UAS: 57 46
LOS: 1 0
LOF: 8 0
LOM: 0 0
Latest 15 minutes time = 9 min 35 sec
FEC: 3619 0
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: 1897 3
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 16 hours 9 min 35 sec
FEC: 269618 3309
CRC: 2525 5
ES: 15 5
SES: 11 0
UAS: 34 23
LOS: 1 0
LOF: 8 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 469870 5849
CRC: 25 0
ES: 13 0
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 hours 36 min 7 sec
FEC: 14931 11
CRC: 3 5
ES: 1 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
Looks like you’ve been banded to 25meg, have you noticed any instability?
If you’re on an ECI cab then G.INP is currently not available. There are murmurs of a trial going to to try and get it working but they’ve tried and failed before.
-
Looks like your line has been banded presumably due to a lot of disconnections. Have you been rebooting or disconnecting often?
Is your home phone wiring optimal - is the router connected to a NTE5A/B/C master socket and all extension wiring connected to a SSFP? Something like this https://www.diynot.com/diy/media/untitled.30844/full
You may want to consider running DSLstats 24*7 if possible and maybe signing up to mydslwebstats to capture and share your connection statistics to allow some analysis of your connection.
-
Looks like your line has been banded presumably due to a lot of disconnections. Have you been rebooting or disconnecting often?
Is your home phone wiring optimal - is the router connected to a NTE5A/B/C master socket and all extension wiring connected to a SSFP? Something like this https://www.diynot.com/diy/media/untitled.30844/full
You may want to consider running DSLstats 24*7 if possible and maybe signing up to mydslwebstats to capture and share your connection statistics to allow some analysis of your connection.
I was doing some messing with the billion settings, trying to get IPV6 working etc. So yes, a few reboots. I'm now leaving it alone. Wiring is all fine, a new VDSL faceplate was fitted a couple of years ago by OR (another routing issue on supplier switch). Router is in the garage connected to the faceplate with Cat 5e cable.
So will this banding go if I now leave it alone?
-
It should do but DLM is quick to apply it and s l o w to remove it.
-
Interleaving is also turned on quite high; the framing parameters show it to be using 10 bytes out of every 42 for FEC overheads ... nearly 25%.
With both heavy interleaving and banding, it is likely that DLM was seeing a lot of errors, not just the resyncs. The highish FEC counts say that, even at the capped speed, there is still interference being felt on the line.
The ES counts are now low enough to show that the interference is "contained", but I wouldn't hold out high hopes for a huge improvement. Not, at least, until G.INP arrives.
-
I have a similar experience - just under 1km from cabinet, Originally I had a Cisco 897VAW router and was using homeplugs also. The home plugs generated a load of FECs - hundreds per second. The line ended up banded at 24999 just like this one appears to be. I removed the home plugs and found interference and FECs stopped. Banding lifted after about 6 weeks to 29999 and then 34999 but has been stuck at 34999 for about 8 months. Upstream banded at 4999
Router reports max attainable down of 39000 and up of 7995. Banding is my problem and can't be reset by the ISP, but won't seem to budge this last bit. G.INP is on for me. So hopefully banding will lift for you, but it could take a long time.
[Moderator edited to correct a typo.]
-
Thanks for the insight so far. Just to be 100% sure I'm looking at the FEC numbers from running "ADSL info --stats" via telnet?
I do have a smart dialler box wired in that you'd class as an extension, I'll remove this & have a look at the stats again, provided I'm looking at them correctly.
-
It's no use looking at FEC numbers. These are generally error corrections.
You should really track ES (Error seconds) and disconnections which is what DLM is interested in.
See http://www.kitz.co.uk/adsl/DLM_calculator.php
-
Thanks for the insight so far. Just to be 100% sure I'm looking at the FEC numbers from running "ADSL info --stats" via telnet?
That's right. For errors, I normally take a look at the different groups at the end - latest 1 day, previous 1 day, since link time.
As Dray says FECs are corrected. The count tells us simultaneously that noise exists, but is being handled. The ES count tells us how much noise is not being fixed - which DLM pays more attention to.
-
ES doesn't seem that high downstream, but more upstream:
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 6654 Kbps, Downstream rate = 32392 Kbps
Bearer: 0, Upstream rate = 6537 Kbps, Downstream rate = 24999 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.6 6.2
Attn(dB): 28.6 0.0
Pwr(dBm): 6.4 6.3
VDSL2 framing
Bearer 0
MSGc: 36 33
B: 31 204
M: 1 1
T: 62 5
R: 10 16
S: 0.0407 0.9966
L: 8264 1774
D: 803 1
I: 42 221
N: 42 221
Counters
Bearer 0
OHF: 33116787 512172
OHFErr: 43 372
RS: 3729510491 2056595
RSCorr: 741883 1131
RSUnCorr: 2219 0
Bearer 0
HEC: 376 0
OCD: 0 0
LCD: 0 0
Total Cells: 1748590998 0
Data Cells: 467720458 0
Drop Cells: 0
Bit Errors: 0 0
ES: 10 270
SES: 0 0
UAS: 0 0
AS: 125733
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 3.79 16.25
OR: 88.51 19.19
AgR: 25087.52 6556.65
Bitswap: 4168/4184 462/463
Total time = 1 days 10 hours 55 min 33 sec
FEC: 741883 1131
CRC: 43 372
ES: 10 270
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 10 min 33 sec
FEC: 3800 11
CRC: 0 4
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 3839 15
CRC: 0 4
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 10 hours 55 min 33 sec
FEC: 236883 236
CRC: 2 93
ES: 1 80
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 505000 895
CRC: 41 279
ES: 9 190
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 10 hours 55 min 33 sec
FEC: 741883 1131
CRC: 43 372
ES: 10 270
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
> adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 6671 Kbps, Downstream rate = 32408 Kbps
Bearer: 0, Upstream rate = 6537 Kbps, Downstream rate = 24999 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.6 6.3
Attn(dB): 28.6 0.0
Pwr(dBm): 6.4 6.3
VDSL2 framing
Bearer 0
MSGc: 36 33
B: 31 204
M: 1 1
T: 62 5
R: 10 16
S: 0.0407 0.9966
L: 8264 1774
D: 803 1
I: 42 221
N: 42 221
Counters
Bearer 0
OHF: 33134965 516367
OHFErr: 43 372
RS: 3736272362 2329170
RSCorr: 742150 1131
RSUnCorr: 2219 0
Bearer 0
HEC: 376 0
OCD: 0 0
LCD: 0 0
Total Cells: 1751908150 0
Data Cells: 467894972 0
Drop Cells: 0
Bit Errors: 0 0
ES: 10 270
SES: 0 0
UAS: 0 0
AS: 125801
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 3.79 16.25
OR: 88.51 19.19
AgR: 25087.52 6556.65
Bitswap: 4168/4184 462/463
Total time = 1 days 10 hours 56 min 41 sec
FEC: 742150 1131
CRC: 43 372
ES: 10 270
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 11 min 41 sec
FEC: 4067 11
CRC: 0 4
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 3839 15
CRC: 0 4
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 10 hours 56 min 41 sec
FEC: 237150 236
CRC: 2 93
ES: 1 80
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 505000 895
CRC: 41 279
ES: 9 190
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 10 hours 56 min 41 sec
FEC: 742150 1131
CRC: 43 372
ES: 10 270
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
Does anyone know what (if any) effect the PWR has on the line?
Example above - Pwr(dBm): 6.4 6.3
My line is about 11.1 on down and 3.1 on up, my snr is basically the same as above 6.1-6.6
Just curious.
Ta.
-
The 2 cabinet vendors show power totally different.
Yours will be Huawei, the OPs will be ECI
My ECI cabinet showed my power as 6dBm down 6dBm up.
My Huawei shows 13.5dBm down 3.5dBm up.
Very similar sync speeds.
Most lines show similar.
-
PWR is the transmission power.
In VDSL2, the power is limited twice: once per tone, to quite a low value, and once as an aggregate value, when added across all tones.
When restricting "per-tone", there are special restrictions put in place downstream, to prevent interference to ADSL from the exchange. There is also a restriction upstream if you are close to the cabinet.
When the modem displays a value, it is likely to be the current aggregate transmission power, at least for Huawei's.
Mine isn't much different from @j0hn's downstream, but wildly different upstream: currently 13.1dBm down, -8.9dBm up.
I'm very close to the cabinet.
-
After reading all manner of threads here & elsewhere, I decided to tidy things up in my garage where the router lives.
I have the newest type NTE socket with the RJ45 socket at the top for router connection, I did have some extension wiring that I've now removed.
I have a home made Cat5e cable that plugs into the NTE outlet & runs to the garage into the router, probably a 10m run. Where the NTE socket is isn't the best location for a router, hence this setup.
In the garage I have all manner of stuff, a PC acting as TV server, a couple of NAS boxes & a Gigabit switch which the router goes into along with all the other stuff in the house. The Billion router lives amongst all this, I also had the BT supplied HH there which was still plugged in from when I used it on day 1.
So 2 routers & a switch almost on top of each other. I first removed the HH & then untangled the Billion, managing to move it a good foot or so away from any other devices, tidying the cables in the process, whilst maintaining sync.
I've had DSLstats running since last night which showed an immediate drop on downstream SNR margin of around 1dB to 5.8dB. Could I get some DLM intervention here & a bit more speed?
(https://preview.ibb.co/m9sY0b/Capture.jpg) (https://ibb.co/kj0xRG)
-
But the drop in SNRM indicates it's now worse than it was before.
-
But the drop in SNRM indicates it's now worse than it was before.
OK, I suspect I have to live with this due to the sheer length of my line to the cab, would have preferred more than a 25% increase for switching to FTTC.
I do want to categorically rule out my wiring including my DIY cable to the router, so I'm going to rejig things, I've ordered proper 3m cables for the router & phone so I can locate them in the living room plugged direct into the master socket & remove all extension wiring.
So, my question is, can the VDSL connection be gracefully shut down without any more DLM malarkey kicking in? Should I select disconnect from the router then power down? Just power off the router?
From doing this I should know what I can expect going forward. For the record these are my stats from the BTW DSL checker, I presume I'm in the expected range so no engineer checks
High Low High Low
VDSL Range A (Clean) 36.5 27.4 7.6 5.7
VDSL Range B (Impacted) 28 15 6.9 2.7
WBC ADSL 2+ Up to 15.5 -- 8.5 to 18.5 << ADSL was always higher than 18.5.
-
If you disconnect or power down the DSL connection, remember to leave 30 minutes before you reconnect it. This will stop DLM counting a disconnection
-
But the drop in SNRM indicates it's now worse than it was before.
Thanks for pointing out my lack of knowledge :o
I have now discarded my dodgy internal wiring for proper manufactured cables. The downstream SNRM has now gone up to 8.4/8.6dB max attainable is now around 35700, still stuck at the banded 24999 though, fingers crossed DLM ups this now :-\
-
still stuck at the banded 24999 though, fingers crossed DLM ups this now :-\
Success! Had a resync at 12:04, now at 29999 down ;D SNRM has dropped & is hovering at +/- 6dB.
Didn't expect anything to happen that quick, anything else speedwise will be a bonus now.
Hopefully the errors are manageable & it won't drop again.
new stats below
> adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 7248 Kbps, Downstream rate = 35465 Kbps
Bearer: 0, Upstream rate = 7175 Kbps, Downstream rate = 29999 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.1 6.2
Attn(dB): 25.8 0.0
Pwr(dBm): 6.4 6.3
VDSL2 framing
Bearer 0
MSGc: 24 33
B: 34 224
M: 1 1
T: 60 5
R: 8 16
S: 0.0371 0.9969
L: 9272 1934
D: 880 1
I: 43 241
N: 43 241
Counters
Bearer 0
OHF: 5527828 108400
OHFErr: 338 74
RS: 1989911654 1340810
RSCorr: 1168078 199
RSUnCorr: 57984 0
Bearer 0
HEC: 11457 0
OCD: 26 0
LCD: 26 0
Total Cells: 1068983193 0
Data Cells: 288786833 0
Drop Cells: 511
Bit Errors: 0 0
ES: 78 649
SES: 11 0
UAS: 33 22
AS: 18534
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 3.35 16.26
OR: 71.59 19.18
AgR: 30070.44 7194.30
Bitswap: 1044/1045 8/8
Total time = 1 days 22 hours 16 min 7 sec
FEC: 164618529 2005
CRC: 3073 743
ES: 78 649
SES: 11 0
UAS: 33 22
LOS: 1 0
LOF: 8 0
LOM: 0 0
Latest 15 minutes time = 1 min 7 sec
FEC: 1795 1
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 49857 13
CRC: 2 3
ES: 1 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 22 hours 16 min 7 sec
FEC: 163975675 982
CRC: 2929 330
ES: 49 287
SES: 11 0
UAS: 33 22
LOS: 1 0
LOF: 8 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 642854 1023
CRC: 144 413
ES: 29 362
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 5 hours 8 min 53 sec
FEC: 1168078 199
CRC: 338 74
ES: 29 59
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
It looks like it both altered the banding to 30Mbps, and reduced the FEC+interleaving to a lower level (INP is now 3 instead of 3.5; delay still 8ms; FEC overhead now 8/43 instead of 10/42).
With the increase in speed, it looks like the ES rate has increased a little. That'll be the thing to watch now.
-
Probably the INP_min is the same at 3, but with the lower banding, there was a lot of spare bandwidth which could be used to carry FEC data, which was used to produce an actual INP value above the minimum required. The DLM has changed the banding, but the error protection has remained the same on the "Interleaving Low" profile.
-
That makes sense - I can buy that.
-
Thanks for taking the time to look at my stats. I have since moved the router away from the electric socket & DECT base station - very carefully without powering off, & got bout an extra 0.5dB on the SNRM. I had no idea VDSL was so sensitive to interference.
Hopefully this may eek out a little more speed, we shall see.
I think I have successfully set up MDWS - user Gedpie if anyone cares to take a look.
-
I think I have successfully set up MDWS - user Gedpie if anyone cares to take a look.
I can see eight users whose names begin with "G" or "g" but no "Gedpie". :no:
-
hucknailred: could you also attach your Hlog?
-
I can see eight users whose names begin with "G" or "g" but no "Gedpie". :no:
I did say "I think". Registration was succesful, but I need to revisit MDWS another time...
-
hucknailred: could you also attach your Hlog?
That I can manage...
-
That I can manage...
Unfortunately it is truncated. A Profile 17a, G.993.2 (a.k.a. VDSL2) circuit has a total of 4096 sub-carriers (numbered from 0 to 4095). So you will need to adjust the X-axis scale with the controls at the bottom of the relevant screen.
-
Unfortunately it is truncated. A Profile 17a, G.993.2 (a.k.a. VDSL2) circuit has a total of 4096 sub-carriers (numbered from 0 to 4095). So you will need to adjust the X-axis scale with the controls at the bottom of the relevant screen.
Sorted, it was set for ADSL.
Have also ticked the box to get MDSW uploading too :blush:
-
Unfortunately it is truncated.
For me fortunately. :) I've more interested in ADSL2+ band Hlog. VDSL2 Hlog is too inaccurate for this band.
-
OK, have had an interesting couple of days. Stats are on MDSW user Gedpie, there is a gap that I'll explain.
Looking at Tuesday's stats there is a jump in SNRM to over 7dB, which was unusual. When I got home I discovered my media PC in the garage had powered down about 10 minutes before the SNRM jump, I switched it back on & saw that the PSU fan was seized. You'll then see a gap in the stats, as said PSU decided to expire very loudly tripping all the sockets in the house as it did so.
Now the media PC had an important job at 8PM (recording GBBO) so a PSU was culled from another PC, which resulted in the SNRM going back to 6ish & then plummeting to under 2. Drastic action was needed so the PSU was pulled from the PC doing the MDWS stats, hence the gap in data whilst I sourced a new PSU, which went in yesterday & stats resumed.
So it looks like the dying PSU was causing interference, but I didn't get that increased SNRM when the dead PSU was out of the equation. I think I'll tinker at the weekend unplugging stuff in the house & checking the effects.
My latest stats are below, FEC did go off the scale after the PSU fun, up in the 1,000,000 scale, but things seem to have settled now, ES look almost none existent, attainable is over 38000, still banded at just under 30000 though.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 6741 Kbps, Downstream rate = 38014 Kbps
Bearer: 0, Upstream rate = 6658 Kbps, Downstream rate = 29998 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.6 6.1
Attn(dB): 25.8 0.0
Pwr(dBm): 6.3 6.3
VDSL2 framing
Bearer 0
MSGc: 15 33
B: 57 208
M: 1 1
T: 64 5
R: 16 16
S: 0.0615 0.9978
L: 9624 1804
D: 525 1
I: 74 225
N: 74 225
Counters
Bearer 0
OHF: 47773186 457179
OHFErr: 5213 608
RS: 582452966 713477
RSCorr: 244135920 9302
RSUnCorr: 421663 0
Bearer 0
HEC: 133047 0
OCD: 312 0
LCD: 312 0
Total Cells: 3874086871 0
Data Cells: 307869295 0
Drop Cells: 0
Bit Errors: 0 0
ES: 215 329
SES: 14 10
UAS: 23 23
AS: 141630
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.96 16.27
OR: 56.67 19.16
AgR: 30055.13 6676.78
Bitswap: 31683/31703 573/589
Total time = 1 days 15 hours 20 min 53 sec
FEC: 244135920 9302
CRC: 5213 608
ES: 215 329
SES: 14 10
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 1 0
Latest 15 minutes time = 5 min 53 sec
FEC: 961 0
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: 2229 1
CRC: 3 1
ES: 1 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 15 hours 20 min 53 sec
FEC: 497209 254
CRC: 226 87
ES: 31 68
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 243638711 9048
CRC: 4987 521
ES: 184 261
SES: 14 10
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 1 0
Since Link time = 1 days 15 hours 20 min 29 sec
FEC: 244135920 9302
CRC: 5213 608
ES: 215 329
SES: 14 10
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 1 0
-
Ah, now I understand the "happenings" that were recorded and viable via MDWS. I'm waiting for a continuous 24 hours set of data but from what is currently present nothing seems to be out of the ordinary.
Looking at the Hlog plot I can see that there is no gross physical abnormality to the metallic pathway, it is just a longish line.
Moving to the QLN plot I can see that the cabinet containing the DSLAM is a significant distance from the serving telephony exchange. The RFI spikes in the DS2 band are probably nothing more than the result of your local topography.
A quick look at the SNRM plot shows that you do not experience a diurnal rise and fall in the margin as a result of long distance radio signals pick-up during the hours of darkness.
-
Looking at the Hlog plot I can see that there is no gross physical abnormality to the metallic pathway, it is just a longish line.
Moving to the QLN plot I can see that the cabinet containing the DSLAM is a significant distance from the serving telephony exchange. The RFI spikes in the DS2 band are probably nothing more than the result of your local topography.
Exchange to cabinet is only about 500m, cabinet to house is 1150m (From OR engineers app).
Just after 6PM tonight FEC has jumped up to a steady 1,000,000, what's that all about?
-
Hi folks, I've donated to MDWS so there's over a week of steady connection & stats to look at. Just wondering if there's any potential for more speed? I live in hope that DLM will remove the banding & G.INP comes to my ECI cabinet.
User = Gedpie
Thanks
-
OK, there's plenty of history on MDWS for my connection now. Had a resync a week ago taking me to 31591 down. Would I be correct that I'm no longer banded? Interleaving is still on though, ES very low on DS & no resyncs, another does show on MDWS but this was just me resetting stats in the router interface, I don't think it actually happened :fingers:
Is there a likelihood of interleaving going too?
Thanks