Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[burakkucat]

Walter's wheelbarrow seems to have worked minor miracles now with the HH5 connected directly to the master skt complete with a MK III integral filter faceplate.

The above sentence has been giving me some trouble.    Perhaps I have forgotten the "what's what" of the HH5, so perhaps it is now possible to obtain the "full spectrum" of data from such CPEs . . . 

[waltergmw]

@ BKK,

Sadly (as far as I know) that's only possible with the HG612 port 1 connected to the HH5 via the red RJ45 socket.

I also observe that DLM is still sulking after 48 hours with the sync apparently locked to 18 Mbps. Patience is a virtue as otherwise, I'm afraid, I have some significant potential arguments with BT Retail requesting a retrain; unless leaving the modem off for an hour might do the trick. Has anybody any other tricks to hasten matters ?

Kind regards,
Walter

[burakkucat]

As far as I am aware, watch and wait are the relevant words. 

[waltergmw]

Gentlefolk,

Just to confirm to all that, as of the early hours this morning with a resync, we've now reached the dizzy heights of 22.42 Mbps Sync speed.

We live in hope that DLM remains in a benevolent mood and will eventually reward Walter's wheelbarrow with further improvements.

Kind regards,
Walter

[burakkucat]

. . . now reached the dizzy heights of 22.42 Mbps Sync speed.

Getting close to the upper limit of the synchronisation speed for ADSL2+ (24 Mbps)! 

[Weaver]

Congrats on your sync speed.

Sniff.

No, seriously, congrats.

[WWWombat]

Does anyone know what banding ranges exist nowadays?

Some of the speeds on this thread look like banding caps, but aren't listed here:
https://community.plus.net/library/browsing/fttc-dlm-what-it-is-how-it-works/

[waltergmw]

@ WWWombat,

We think the modest improvements are probably due to the rather conservative DLM logic as we've had a series of re-syncs.
However we've now reached the 25 Mbps sync which I believe is sometimes a cap, but there's a good chance more improvements could happen over time.

Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 7612 Kbps, Downstream rate = 39432 Kbps
Bearer:   0, Upstream rate = 6000 Kbps, Downstream rate = 25000 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):    16.8       15.4
Attn(dB):    25.4       0.0
Pwr(dBm):    11.2       2.4
         VDSL2 framing
         Bearer 0
MSGc:      26      118
B:      237      174
M:      1      1
T:      57      18
R:      16      16
S:      0.3027      0.9259
L:      6712      1659
D:      1      1
I:      254      96
N:      254      192
         Counters
         Bearer 0
OHF:      21963943      674451
OHFErr:      99      26
RS:      1251931641      2918906
RSCorr:      446      221
RSUnCorr:   475      0

         Bearer 0
HEC:      451      0
OCD:      35      0
LCD:      35      0
Total Cells:   277045888      0
Data Cells:   4075757      0
Drop Cells:   0
Bit Errors:   0      0

[WWWombat]

Thanks Walter - that does indeed look like another cap (and another one not in Plusnet's list).

What is interesting with those statistics is that interleaving seems to have turned off, in both upstream and down (I'd hope that you can see the difference in latency and ping times). The interest is purely technical though - because I'm not sure I've seen DLM turn off the interleaving before it has turned off the caps. I wonder how G.INP will play here!

FEC is turned on for both upstream and downstream; I suspect the modems just see enough spare capacity (between the cap and the attainable) that they turn it on even if DLM hasn't asked.

Even with FEC turned on, there aren't many errors being detected, either corrected ones or otherwise. So there's still hope that DLM will relent further...

[Bald_Eagle1]

We unfortunately don't have the ongoing stats for the first few days i.e. from when DS sync speed was 9999 Kbps against an attainable rate of only 25208 Kbps, but I have attached the montage for the ongoing data collected since 24th January along with an animated gif file including today's snapshot data to show how the connection's speed is gradually improving.

I'm not 100% sure that G.INP will be implemented.

The DSLAM is Huawei:-
ChipSet Vendor Id:   BDCM:0xa48c
ChipSet VersionNumber:   0xa48c


However, I have seen a couple of other connections using chipset version 0xa48c where G.INP didn't seem to be implemented.

FWIW, this particular chipset has fewer tones available at Discovery phase when compared against the 'usual/older' chipset version.

0xa48c:-

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)



Older version 0xa459 (as per my own connection):-

Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)

[Dray]

I think the G.INP problem is because a HH5 has been in use. It should come on now once the cabinet detects the HG612 is in use.

[gt94sss2]

I think the G.INP problem is because a HH5 has been in use. It should come on now once the cabinet detects the HG612 is in use.

G.INP is only implemented if DLM thinks a line needs it - its not automatically applied.

As in the main G.INP thread, the evidence points to the HH5A supporting downstream G.INP (though difficult to be conclusive)

[Dray]

I can't see how you come to that conclusion as from the available stats, G.INP is off in both directions

[burakkucat]

Just making a comment upon the animated "Differences-3" file that B*Eagle1 has provided.

Notice that when the bridging tap(s) (there was a possibility of two taps on that circuit, before Walter's Wheelbarrow performed the wiring optimisation) were present, the circuit was sufficiently out of balance for noticeable RFI to be seen on the QLN plot. 

[waltergmw]

Gentlefolk,

Two small points, though not of major significance.

This service has only beeen operational for around a month so it had a HH5B provided for the self install.

The line length is expected to be around 800 m through the a well established possibly 1960s estate and has had some cable replacements. I'd guess it was pre-aluminium alloy dates.

It would be nice to think that further improvements may be observed but local experience suggests somewhere around 30 Mbps is the best to be expected.

Kind regards,
Walter