Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2] 3

Author Topic: DSLStats input needed  (Read 1247 times)

siofjofj

  • Member
  • **
  • Posts: 96
Re: DSLStats input needed
« Reply #15 on: October 28, 2020, 01:08:37 PM »

Thanks for the update. Hopefully the DLM will apply G.INP then gradually lower the SNR margin to 3dB, giving you a much faster connection.
Logged

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #16 on: October 30, 2020, 11:53:13 AM »

Thanks for the update. Hopefully the DLM will apply G.INP then gradually lower the SNR margin to 3dB, giving you a much faster connection.

Hopefully, although over 48hrs later and no DLM change yet. Engineer said up to 72hrs so will wait before contacting them.
Logged

sof006

  • Reg Member
  • ***
  • Posts: 125
Re: DSLStats input needed
« Reply #17 on: October 30, 2020, 01:52:25 PM »

Hopefully, although over 48hrs later and no DLM change yet. Engineer said up to 72hrs so will wait before contacting them.

I find DLM can take up to a week to make any changes, it depends if your line is interleaved and how far interleaved it is. If interleaving is quite low it usually only takes a couple days. Although as the saying goes, every line is different and DLM is weird.
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: DSLStats input needed
« Reply #18 on: October 30, 2020, 03:31:42 PM »

Thanks for the update. Hopefully the DLM will apply G.INP then gradually lower the SNR margin to 3dB, giving you a much faster connection.

The last couple recent examples of DLM resets have seen the lines retain G.INP throughout. Hopefully this is a much wider change that will happen on all lines.
Logged
BT FTTP 160/30 - BQM - speed test

neil

  • Reg Member
  • ***
  • Posts: 225
Re: DSLStats input needed
« Reply #19 on: October 30, 2020, 05:18:25 PM »

Regarding the Hlog and QLN plots . . . What you have shown is truncated. You will need to adjust the configuration of DSLstats, to allow for the full width of 4096 sub-carriers of a VDSL2 circuit.
how to change it?
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: DSLStats input needed
« Reply #20 on: October 30, 2020, 06:04:41 PM »

how to change it?

By clicking on "Change Tone Range" under an Hlog/QLN graph in dslstats.
Then expanding to show all the tones in use.
Logged
BT FTTP 160/30 - BQM - speed test

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #21 on: October 30, 2020, 07:48:16 PM »

I find DLM can take up to a week to make any changes, it depends if your line is interleaved and how far interleaved it is. If interleaving is quite low it usually only takes a couple days. Although as the saying goes, every line is different and DLM is weird.

I had thought though that as the engineer requested a DLM reset that when that request went through it would resync without the banding and then DLM would do it's thing over the next few days to settle down.

Had this a good few years ago at another house and the DLM reset was done later that day, resync'd to a higher speed and removed banding.
Logged

siofjofj

  • Member
  • **
  • Posts: 96
Re: DSLStats input needed
« Reply #22 on: October 30, 2020, 08:49:40 PM »

I think sof006 may have missed the part of the thread where you confirmed an Openreach engineer had requested a DLM reset.

Have you had any resyncs since the engineer visit? As you say, I would normally expect an initial resync overnight after the visit. I notice now you said it was a Sky engineer. Do you mean Openreach? Sky do have their own engineers who's remit is little more than 'is it plugged in correctly', but I doubt they are able to carry out DLM resets without involving Openreach.
Logged

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #23 on: October 30, 2020, 09:02:19 PM »

I think sof006 may have missed the part of the thread where you confirmed an Openreach engineer had requested a DLM reset.

Have you had any resyncs since the engineer visit? As you say, I would normally expect an initial resync overnight after the visit. I notice now you said it was a Sky engineer. Do you mean Openreach? Sky do have their own engineers who's remit is little more than 'is it plugged in correctly', but I doubt they are able to carry out DLM resets without involving Openreach.

No resyncs since the visit. It was a Sky BB engineer not OR, he had to ring through to request the DLM reset.
Logged

siofjofj

  • Member
  • **
  • Posts: 96
Re: DSLStats input needed
« Reply #24 on: October 30, 2020, 09:42:32 PM »

Interesting. The lack of resyncs says to me the process hasn't even been started yet. It is possible nowadays for ISPs to request DLM resets on VDSL, but I don't know anything about how this process works or how long it takes. The last paragraph in this article https://www.ispreview.co.uk/index.php/2018/02/ability-reset-openreach-fttc-broadband-dlm-profiles-arrives.html suggests it should occur overnight though, so I'm wondering if the request got lost somewhere in the communication chain. Not sure what to suggest other than waiting a little bit longer and then chasing it up with Sky if nothing happens. Perhaps other forum members know what is meant to happen here?
Logged

sof006

  • Reg Member
  • ***
  • Posts: 125
Re: DSLStats input needed
« Reply #25 on: October 31, 2020, 01:07:53 AM »

I'm fairly sure an OR engineer is meant to do any kind of DLM resets. I'd definitely ring back up and ask them whats going on.
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 3155
Re: DSLStats input needed
« Reply #26 on: October 31, 2020, 06:17:11 AM »

I'm fairly sure an OR engineer is meant to do any kind of DLM resets.

They can and do.
They are no longer the only ones who can request this now though.

Sky, Talktalk and possibly BT send their own "non OpenReach" tech staff to customers homes if they think the issue is within the end users premises.

These "engineers" (i use that term loosely) can ask their employers (the ISP) to request a DLM reset.

This will only be actioned if deemed necessary though.

The ISP can of course request a DLM reset without sending anyone to the property.
Logged
BT FTTP 160/30 - BQM - speed test

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #27 on: October 31, 2020, 12:43:50 PM »

So rang Sky this morning as it had been over 72hrs, spoke to nice support guy however it seems there were no notes about a DLM reset from the sky engineer and so he said the quickest way to resolve is to arrange a OR engineer (not Sky) to attend on Monday.

I asked whether it could be stated in notes the history so a remote DLM reset could be done so as not to waste his time, support guy said he would but I get the impression it will be a new visit and somewhat from scratch. Although if he does come to house I can ask him about FTTP progress here  ;D

Logged

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #28 on: November 02, 2020, 12:10:06 PM »

Just to close this off, OR engineer came over this morning and did some quick checks before instigating a profile reset and it has sync'd up at 65/20 now  :cool:

Thanks for all the help :)
Logged

jimmyca69

  • Member
  • **
  • Posts: 56
Re: DSLStats input needed
« Reply #29 on: November 09, 2020, 09:41:32 PM »

Thought i would post up some stats after a week after the DLM reset. DLM has kicked in again but this time in a positive way! Two resync's in the past week has seen the d/l stats increase and the SNR drop on DL to current 4.5dB.
 
Code: [Select]
xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 22961 Kbps, Downstream rate = 73784 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 71563 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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):        4.5             7.4
Attn(dB):        17.6            0.0
Pwr(dBm):        12.4            7.3

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              26
B:              243             237
M:              1               1
T:              0               42
R:              10              16
S:              0.0000          0.3781
L:              18716           5374
D:              8               1
I:              254             127
N:              254             254
Q:              8               0
V:              0               0
RxQueue:                80              0
TxQueue:                20              0
G.INP Framing:          18              0
G.INP lookback:         20              0
RRC bits:               0               24
                        Bearer 1
MSGc:           154             -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              6.4000          0.0000
L:              40              0
D:              3               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0

                        Counters
                        Bearer 0
OHF:            0               1293688
OHFErr:         0               51
RS:             1433111552              2267997
RSCorr:         43236070                400
RSUnCorr:       0               0
                        Bearer 1
OHF:            9717229         0
OHFErr:         0               0
RS:             97171673                0
RSCorr:         132             0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         479950933               0
rtx_c:          734478          0
rtx_uc:         82664           0

                        G.INP Counters
LEFTRS:         56              0
minEFTR:        71552           0
errFreeBits:    1425218436              0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    4278945154              0
Data Cells:     1027118684              0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             22              202
SES:            22              0
UAS:            112             90
AS:             156130

                        Bearer 0
INP:            51.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            3.98
OR:             0.01            64.22
AgR:            71636.76        20063.54

                        Bearer 1
INP:            4.50            0.00
INPRein:        4.50            0.00
delay:          3               0
PER:            16.06           0.01
OR:             79.68           0.01
AgR:            79.68   0.01

Bitswap:        4375/4375               59/59

Total time = 7 days 8 hours 52 min 46 sec
FEC:            69450496                1662
CRC:            1147            231
ES:             22              202
SES:            22              0
UAS:            112             90
LOS:            2               0
LOF:            15              0
LOM:            0               0
Latest 15 minutes time = 7 min 46 sec
FEC:            140428          3
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:            250846          1
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 8 hours 52 min 46 sec
FEC:            9663061         92
CRC:            0               11
ES:             0               9
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            24948171                189
CRC:            0               23
ES:             0               20
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 1 days 19 hours 22 min 9 sec
FEC:            43236070                400
CRC:            0               51
ES:             0               43
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >
Logged
Pages: 1 [2] 3