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:

Author Topic: Graph Interpretation / FTTC Line Issue  (Read 2381 times)

Magsy

  • Just arrived
  • *
  • Posts: 4
Graph Interpretation / FTTC Line Issue
« on: March 05, 2013, 09:26:11 AM »

About a month in on 80/20, ECI /r modem and ECI cab, 450-550m distance.

Tried to unlock on day 1 but my usb > ttl cable was bust however no speedtest was less than 60/20 with 15ms ping. Day 4 interleaving came on at a shallow depth, pushed ping to 21ms. Still had 59.9mbps downloads for next few weeks.

Cam home yesterday to find I have 30ms ping and can't break 49.9mbps. Unlocked the modem and found I'm synced at 50/15.

So I don't have original stats and I'm willing to accept a drop off but the start of this graph looks broken...Discovered had no dial tone and BT have just text to say that is resolved, however the connection is still the same. I've resynced it but the hole is still there.

Anyone care to suggest if this is normal / what has happened?

Thanks
 
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5722
Re: Graph Interpretation / FTTC Line Issue
« Reply #1 on: March 05, 2013, 07:06:05 PM »

I'm no expert on graphing, but there's plenty of folk on here who are. What I can say, is that most circuits require a manual reset of the FTTC port once an issue has been resolved. Rebooting the Modem/Hub will not be enough. :)
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: Graph Interpretation / FTTC Line Issue
« Reply #2 on: March 05, 2013, 08:13:49 PM »

The attachment is from a Huawei HG612 connected to an ECI DSLAM, so if by 'hole' you mean the 'V' shape at the left of the graphs, then yes, it's quite normal.

Logged

Magsy

  • Just arrived
  • *
  • Posts: 4
Re: Graph Interpretation / FTTC Line Issue
« Reply #3 on: March 06, 2013, 11:50:46 AM »

Thanks, I should have looked around first but in my horror I saw the v' notch and just thought surely that is broken?! :D

I can now see that is a normal exclusion zone for VDSL.

BT fixed the no dial tone issue and I resynced a few times, had 6db margins but 50/15 sync same as during the line fault. Had a DLM forced resync at 4am and I'm back to 60/17, the big suprise is not just a return to lower (8ms) interleaving but I'm back on fast path woo! Graph looks the same lol..


Logged

asbokid

  • Kitizen
  • ****
  • Posts: 1286
    • Hacking the 2Wire
Re: Graph Interpretation / FTTC Line Issue
« Reply #4 on: March 06, 2013, 12:23:29 PM »

Glad you got it sorted, Magsy  :)

The  original author of eDMT,, that is ben1066 of this very forum, kindly released the source code for his tool.

See:  [1]

Do we have the sourcecode for DrSox's patches for the newer /r ("Arcadyan") model of the ECI modem?

Now that the method for obtaining Hlog and QLN are understood [2], eDMT could be updated some more.

cheers, a

[1] http://forum.kitz.co.uk/index.php/topic,10635.msg225981.html#msg225981
[2] http://forum.kitz.co.uk/index.php/topic,11818.msg231617.html#msg231617

« Last Edit: March 06, 2013, 09:38:55 PM by asbokid »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: Graph Interpretation / FTTC Line Issue
« Reply #5 on: March 06, 2013, 04:23:56 PM »

the big suprise is not just a return to lower (8ms) interleaving but I'm back on fast path woo! Graph looks the same lol..

If your connection is now near 'perfect' condition-wise, hopefully you will stay on fastpath (interleaving off).

However, following various engineer repairs, DLM for my connection has been reset on a wide open profile a few times (on fastpath).

After a few days, interleaving has always been switched back on again by DLM.
This has taken between the next day and up to 8 days.

AFAIK, none of us know how DLM determines interleaving is required for stability reasons, but it is no doubt based upom a combination of errored seconds, serious errored seconds & various other cumulative error counts over a period of time.

See the attached graphs (not from my own connection).
We can see the effect of interleaving eventually being switched on after 13 days from installation.

Once forward error connection has been applied via the interleaving process (Reed Solomon - RSCorr), see how the errored seconds, CRC errors & HEC errors more or less disappear, to be replaced by RS Corrected errors with the expense of lowered sync speed.

There had been other resyncs within the 13 days before interleaving was applied.
« Last Edit: March 06, 2013, 04:27:26 PM by Bald_Eagle1 »
Logged