![]() ![]() ![]() ![]() |
|
Wait for DLM to work on the line so don't power off / reset modem
John
Linux:
Wait for DLM to work on the line so don't power off / reset modem
Out of interest how quickly does DLM work?
jurgensp99:
Linux:
Wait for DLM to work on the line so don't power off / reset modem
Out of interest how quickly does DLM work?
it's not static it's always checking the line
John
Linux:
jurgensp99:
Linux:
Wait for DLM to work on the line so don't power off / reset modem
Out of interest how quickly does DLM work?
it's not static it's always checking the line
John
I found this chorus document diagnosis_driven_DLM_FAQs v2
Demystified a bit for me however Ill rephrase my question.
How long after the tech has repaired the battery fault will I see changes in my SNR numbers?
The document states to wait at least 10 days for the DLM to settle, will a fault case stay open this long?
ddDLM is always working, but will be more aggressive with changes in the first few days. If the fault is fixed, there should be a noticeable increase in sync rate straight away, probably followed some days later by another increase that corresponds with a decrease in noise margin from12dB to 6dB
There is a massive post i've been meaning to do at some point to hopefully explain that question better..
Truth be told, it's a beast that many at chorus don't even understand.
biggest misconception (which even i'm guilty of) is looking at the wrong metrics for how it calculates MTBE (Mean time between errors)
It's basically black magic the more you poke and prod it, the worse it can be for you.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Edit Note - I cant seem to work out why this post formatting is all crooked :/
We're getting there, apparently a massive waterlogged cable in a pit.
Still have the same noise however.
I didn't restart the modem this time.
So that's picked up a bit of sync rate, which is to be expected. Just leave the modem connected, and ddDLM will do it's thing. You'll probably see the noise margin from from 12dB to 6dB, and get a corresponding sync increase at the same time.
Quick test call, not hearing any noise - nor does your end report any.
So it looks good.
Testing is still off, but they often fix the problem not the test results.
ddDLM will take a little to get into shape. i've given it a little tap so it should profile a little more rapidly..
Really you are probably looking at 3-5 days before the sync rate restores.
What is really interesting to me is your user experience, one of the few times someone has picked up errors causing dips in service level.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:[snip]
What is really interesting to me is your user experience, one of the few times someone has picked up errors causing dips in service level.
I'd expect this is because even if it's performing optimally this is a fairly slow ADSL connection, so any degradation will be more prominent.
RunningMan:
hio77:[snip]
What is really interesting to me is your user experience, one of the few times someone has picked up errors causing dips in service level.
I'd expect this is because even if it's performing optimally this is a fairly slow ADSL connection, so any degradation will be more prominent.
My thoughts exactly plus I get growled at when Hartbreak island starts buffering or dropping out.
I also notice the issues while gaming, any extra lag or desync during shooters are noticeable right away ie you get shot.
hio77:[snip]
Quick test call, not hearing any noise - nor does your end report any.
So it looks good.
Testing is still off, but they often fix the problem not the test results.
ddDLM will take a little to get into shape. i've given it a little tap so it should profile a little more rapidly..
I did notice the modem reset.
As for noise, no popping or crackles as such but still a background static type fuzz. Don't know if that's normal...Might try and get a recording of it to post.
It's just the internet's way of telling you not to watch Heartbreak Island ;-)
As for gaming, the high error rate on the line would have caused dropped and resent packets which is a bad thing for real time applications
RunningMan:
It's just the internet's way of telling you not to watch Heartbreak Island ;-)
As for gaming, the high error rate on the line would have caused dropped and resent packets which is a bad thing for real time applications
but i must have no interleavings man! packets don't drop, don't be silly.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Here is a link to the Buzz I hear on the line
And the numbers 2 days in, seems the going the other way :/
|
![]() ![]() ![]() ![]() |