Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: Bowdon on September 17, 2015, 10:25:17 AM
-
Well, after many months DLM finally removed interleaving from my line.
I'm not sure how things will go as I was always a bit borderline when it came to ES's.
What's the maximum allowed ES's per 24 hours before DLM kicks in and puts interleaving on?
I noticed that in 8 hours its got 196 ES's (so 25 per hour) on the download and 17 (2 per hour) on the upload. No other errors are happening.
-
There's no single answer to that question. You can read all about it here, (http://www.kitz.co.uk/adsl/DLM.htm#DLM_categorising_the_line) or if you use MyDSLWebStats the traffic lights in the top left corner summarise your situation.
-
I've got a question about MyDSLWebStats. Does the PC have to stay on all the time when using it?
-
MyDslWebStats is a website. You upload data from your modem to the website using a monitoring app running on a PC or Raspberry Pi. The monitoring app should be running on a PC or RPi that is always on.
-
Thanks for the info :)
Well, it just had another reconnection. It held the same speeds. I think its either the ES's that are going too high, or I've noticed there is quite a few HEC errors. I'll have to see how it goes. The recync reason was 0.
-
DLM kicked in again. I'm back to interleaved :(
Though I think it was expected as I was hitting around 2000 ES's on the downstream per day lol.
I think I'm on the maximum what this line can do at 800 metres from the cabinet.
So far its not interleaved me as bad as before.. I've got a couple of more mb's than my usual, so I'm all good :)
I wish though that they would make DLM more configurable on fibre like they do for adsl. I think unless I'm constantly disconnecting then or there is issues with through-put i.e. nothing going through for long periods.. then why not just let the connection stay up!? I guess its a tight balance on these things though. Lots of calculations.
-
There's one thing you can do to get a lower error rate at the expense of some speed. If you have a Broadcom based modem you can issue a command via telnet to cap the speed, which will result in a higher SNRM and (hopefully) lower error rates. I don't have a link at present, but it's been discussed on this forum several times. It was pioneered by les-70, who uses it himself for this purpose.
-
One of my scribblings shows the following:
xdslcmd configure --trellis on --bitswap on --sesdrop on --sra on --phyReXmt 0x3 --i24k on --maxDataRate 40000 20000 60000
xdslcmd configure1 --maxDataRate 40960 20480 61440
Your HG needs to be running the latest firmware before the maxdatarate syntax becomes valid.
--maxDataRate <desired downstream synch> <desired upstream synch> <the total of the former two>
-
And here's another link: http://forum.kitz.co.uk/index.php/topic,16002.msg299131.html#msg299131
-
Hi I'm randcom & new to this fourm,
I have found that setting a speed cap with maxDataRate disables PhyR UP & Dn?
-
Hi and welcome to the forums :)
Im not sure about the propitiatory BCM Phyr, but I've used maxDataRate to artificially cap my line without it affecting g.inp retranmission on the Openreach DLM.
Retransmission remained on both during the time of the cap and afterwards.
-
Hi Kitz, Thank you for the welcome.
Using the maxdatarate speed cap got INPRein down to 0 but
noticed ES's went up, upon checking found PhyR was off also
Trellis may have been off??
Enabling these remove the seedcap, which has worked out OK!
as with both PhyR & Trellis enabled, RS, when they occur, are below 9 per hour.
-
On the old DLM I think you looking good, but DLM did change if I remember right and can act on short bursts?
-
>> but DLM did change if I remember right
Yup they had some trials going where only certain times of the day counted towards the DLM targets. They were supposedly targetting peak hours when the user would more likely be using the connection and ignoring certain time frames when it would have less impact on the user.
My daily burst of shine usually happens between 10am-midday (off peak) but not quite sure what to make of it as it has been ignored twice that Im aware off, but still happened plenty of other times. Errors are still in about the same range, so I'm mot sure what made it ignore twice but still act about a handful of other times.
Capping the speed has caused the DLM to remove the banding thats been there for many long months.