Print

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

[lcl00]

Is the standard procedure for G.INP to disconnect me in the middle of the night and automatically apply it, like how DLM applies interleaving?

[Ronski]

Hopefully once G.INP goes live that interleaving level will drop off.  Is G.INP capable of handling error correction as well as the interleaving that is currently being used on my line; or is that one of those other questions that's much more complicated to ask than it is to answer?   

Thanks for the replies!

It certainly seems to be with the added benefit that it doesn't constantly reduce your sync, and increase latency

Is the standard procedure for G.INP to disconnect me in the middle of the night and automatically apply it, like how DLM applies interleaving?

Yes.

[lcl00]

Right... now to wait on that!  I suppose even at 42mbits, I'm particularly lucky.  The line is 1250m from the cabinet.

Does G.INP have any impact on crosstalk?  I have a few other lines in my house and I was considering putting FTTC on them, but pretty conscious of the fact that the crosstalk could decimate the sync that's currently on that line! 

I had read a few conflicting posts regarding whether or not it does make any difference, but I'm sure someone here can provide a conclusive answer.

[roseway]

Yes, G.Inp can to some extent recover speed lost by crosstalk. My connection started at the full 80/20, and over the months it progressively fell to about 73/20 (almost certainly due to crosstalk). When G.Inp was applied my speed recovered to 80/20 (just) and has since fallen a little to about 78/20.

[lcl00]

That's good to know at least.  My optimism is hoping for something a bit higher than I started with!

However, I don't think crosstalk is having that much of an effect on my connection.  Almost all of the lines that run the same direction as mine are substantially longer and therefore aren't actually using the higher upstream and downstream bands.  Most of the neighbours further away are being given estimates in and around 20mbits and with very long drop wires, it's unlikely that they're even getting that.  The ones closer are running on totally different spans of copper - lucky me, I suppose!

[lcl00]

And looks like DLM has intervened again... still with no G.INP!  For some reason as time went on the errors on the upstream began to rack up considerably.  My theory is the bitloading in U2 looked a bit sparse with a low SNR and was probably riddled with errors.  I'm wondering if there's some way to tell it not to use that particular band.

However, interleave depth on the downstream looks to have went up even though the number of ES after interleaving had been applied were negligible, or am I misreading?


xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 7948 Kbps, Downstream rate = 48308 Kbps
Bearer:   0, Upstream rate = 6647 Kbps, Downstream rate = 41638 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.4       6.0
Attn(dB):    21.8       0.0
Pwr(dBm):    12.7       3.1
         VDSL2 framing
         Bearer 0
MSGc:      14      42
B:      43      47
M:      1      1
T:      64      64
R:      10      16
S:      0.0336      0.2293
L:      12848      2233
D:      965      141
I:      54      64
N:      54      64
         Counters
         Bearer 0
OHF:      11792604      592820
OHFErr:      7      0
RS:      3018789337      2029917
RSCorr:      50412      472653
RSUnCorr:   21      0

         Bearer 0
HEC:      2      0
OCD:      0      0
LCD:      0      0
Total Cells:   2039584651      0
Data Cells:   5584314      0
Drop Cells:   0
Bit Errors:   0      0

ES:      9667      11537
SES:      430      0
UAS:      4246      4203
AS:      25477

         Bearer 0
INP:      3.00      4.00
INPRein:   0.00      0.00
delay:      8      8
PER:      2.16      14.73
OR:      74.06      26.06
AgR:      41712.02   6672.93

Bitswap:   19332/19332      44/44

Total time = 1 days 14 hours 38 min 18 sec
FEC:      6055499      474992
CRC:      12542      11064
ES:      9667      11537
SES:      430      0
UAS:      4246      4203
LOS:      4      0
LOF:      35      0
LOM:      0      0
Latest 15 minutes time = 8 min 18 sec
FEC:      1458      8013
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:      1318      17320
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 = 14 hours 38 min 18 sec
FEC:      1401436      473024
CRC:      3953      1886
ES:      19      1795
SES:      11      0
UAS:      32      21
LOS:      1      0
LOF:      10      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      930599      675
CRC:      88      3207
ES:      29      3101
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 7 hours 4 min 35 sec
FEC:      50412      472653
CRC:      7      0
ES:      2      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

[NewtronStar]

However, interleave depth on the downstream looks to have went up even though the number of ES after interleaving had been applied were negligible, or am I misreading?

If you had resync and then sync rate was higher than before the interleaving depth will also increase.

[lcl00]

The sync actually dropped, it was 42346 now it's 41638.  Obviously a relatively minor drop and entirely understandable given how line conditions move around during the course of the day... just wasn't sure why the interleaving depth went from 829 to 965.  Although realistically, this may not actually make any difference.  I'm pretty new to all of this.