Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: dushami on August 28, 2017, 06:27:04 PM
-
[Moderator note: These posts have been split off to form a new thread with its own subject.]
If the equipment at both ends support it, should G.INP be automatically applied from day 1? My ADSL2+ service is supposed to be switched over to VDSL2 on Wednesday. I've had a Billion 8800NL for ages and Ive just configured it for VDSL and hope that it just connects! The BT HH is still in its brown box.
-
If the equipment at both ends support it, should G.INP be automatically applied from day 1? My
Definitely not on day one you will have two days on the open profile then the third day will either keep you on fastpath or send you to interleaving it all depends on those errored seconds and any retrains.
You keep us informed when G.INP becomes active on you circuit ;)
-
OK thanks, will do. Ive been given a range of 58 to 74 with minimum 52. Regardless of the speed I end up with, my kids will think Christmas has come early!
-
It's usually about 10-11 days after the line goes live.
It varies though. It took 7 weeks for 1 of the regs recently, then 11 weeks for myself
-
when i said 'regardless of the speed i get', i take that all back.
Line went live about 4pm yesterday. im getting 45MB down, 14 up (on vdsl2). i havent worked out how to put DSLSTATS on my Synology box yet, so cant run it 24/7. The stats from my 8800NL are copied below. Should I just wait until next week to moan at BT, since the minimum guarantee is 52Mb. I was getting 19500 on adsl2+ ! Its definetely faster, but im sure thats as much to do with the upload as download, but from what I see on this forum, everyone is keen to max out what they have. Me too!
Comments on the stats are most welcome :)
> adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14250 Kbps, Downstream rate = 46085 Kbps
Bearer: 0, Upstream rate = 14324 Kbps, Downstream rate = 45953 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): 20.4 0.0
Pwr(dBm): 12.1 7.6
VDSL2 framing
Bearer 0
MSGc: 19 26
B: 239 237
M: 1 1
T: 64 63
R: 0 16
S: 0.1662 0.5285
L: 11552 3845
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 38888362 381322
OHFErr: 2549 451
RS: 0 4146913
RSCorr: 0 1848
RSUnCorr: 0 0
Bearer 0
HEC: 7816 0
OCD: 395 0
LCD: 395 0
Total Cells: 584712423 0
Data Cells: 358295004 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1172 346
SES: 3 0
UAS: 0 0
AS: 103823
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 2.66 8.35
OR: 74.91 30.63
AgR: 46028.20 14355.10
Bitswap: 13285/13285 2074/2074
Total time = 1 days 4 hours 50 min 38 sec
FEC: 0 1848
CRC: 2549 451
ES: 1172 346
SES: 3 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 5 min 38 sec
FEC: 0 7
CRC: 6 0
ES: 4 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: 0 46
CRC: 15 22
ES: 13 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 4 hours 50 min 38 sec
FEC: 0 330
CRC: 358 90
ES: 228 56
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 1518
CRC: 2191 361
ES: 944 290
SES: 3 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 4 hours 50 min 36 sec
FEC: 0 1848
CRC: 2549 451
ES: 1172 346
SES: 3 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
-
Hard to tell from a small snapshot of stats.
I'd recommend setting up DslStats and uploading the data to MyDSLWebStats. This allows everyone to see things like Hlog/QLN graphs and watch SNRM graphs to see if they can spot problems with the line.
BT insist on repeating the nonsense that it takes 10 days for the line to settle but that's just not true. They may make you wait until then to send anyone out. What you're getting is what you'll get unless any issues that exist are fixed.
Try connecting straight into the test socket to rule out any internal wiring issues. Don't keep reconnecting the line though as DLM thinks the line is unstable and may slow you further.
-
With 994 ES on fastpath for 24 hours is middle of the road it wouldn't take to much noise to move that to 1440 Standard but as your with BT it will allow upto 2880 errored seconds in a 24 hour period
It's always handy to know the true distance from PCP cabinet to the premises even though it shows the attenuation as Attn(dB): 20.4 which is not a true indication of distance.
-
It's always handy to know the true distance from PCP cabinet to the premises even though it shows the attenuation as Attn(dB): 20.4 which is not a true indication of distance.
Hmmm .... not sure I agree with that, NS :-\ ........... IF the EU is connected to the test socket within the master socket, then attenuation is the true value of the 'distance' from DSLAM to router.
1km of copper cable, will have a lower attenuation of a similar 1km of aluminium cable.
Knowing the distance from the router to the DSLAM in metres, will only provide a rough idea of what connection speeds one will achieve, in the vast majority of situations the EU won't have a Scooby what their MPF (Metallic Path Facility) is composed of ??. :) :)
-
PS ............... Ronski, if you're looking in ...... see what I did there ??? ha ha, cheers. :)
-
PS ............... Ronski, if you're looking in ...... see what I did there ??? ha ha, cheers. :)
Sublime quote editing.
-
I'll spend some time getting dslstats setup over the weekend. The router isn't plugged into the master socket but there are no extensions & no phone plugged in. I thought I'd best leave it rather than disconnect.
I think I found my cabinet the other day and it's about 450m away, following the wires on the pole as much as I can to the cabinet (I used mapometer.com). For comparison, with ADSL2+ the same 8800NL synced at 19500 down 1024 up at snoring 3.1db. Not sure if any of that works out the likely distance.
BT gave me a range of 58-77 down, 16-20 up with a worst case /hand back FoC minimum of 52Mb.
Cabling - There is some sort of junction box on the wall outside. The cable comes off the pole, through a neighbours tree, onto a hook embedded in my wall. It then goes into a box & down my wall into my house. I'll take a look over the weekend, need ladders.
-
The router isn't plugged into the master socket but there are no extensions & no phone plugged in.
Could you please clarify how many phone sockets you have? Even sockets with nothing plugged in. If the modem/router is not plugged into the master socket, then you must have at least one extension socket?
-
Could you please clarify how many phone sockets you have? Even sockets with nothing plugged in. If the modem/router is not plugged into the master socket, then you must have at least one extension socket?
I'm guessing ..... but I think he meant he isn't plugged into the 'Test socket' ................ not 'Master socket'. :) :)
-
Haha, yes. I'm meant Test Socket. I also meant SNR rather than snoring :)
-
Lets go with 450 meters to PCP cabinet with full copper and no faults then 65-72 Mbps should be possible.
-
I've just passed 8 weeks with no sign of G.INP being applied to my line. :( Previously had it in my old home but moved on July 6th. 2 days on fast path with sync around 76000 with quite high ES (think there's a lot of crosstalk on my line) and then DLM enabled interleaving where I've stayed ever since.
Username on MDWS is 'bkehoe'.
Using a Zyxel 8924, and Huawei cabinet (area enabled in 2010).
-
Looks like the G.INP gods saw my last post as yesterday morning G.INP was enabled on my line. Now syncing at 77400, up from 67 with 6dB SNR target. :)
So 8 weeks and 3 days to get it enabled for me.
-
My brothers line just had G.INP applied 21 hours ago, this was a new connection on a Huawei twin to an ECI. Line was activated on the 19 July, so took 50 days. He started off on fast path then was interleaved for a while then back fast path for a while. Username is Jonski on MDWS.