I have not been running the graphs sadly, only because when I show them to OR Engineers or my ISP, they just tell me, they can see all these stats already because they have similar tools running and monitoring my connection, basically they take no interest in them.
So, everyone can see the same stats, yet supposedly nothing is wrong?
Assuming there are no outstanding physical line problems, is the REIN investigation still a possibility, or has that been cancelled now?
Just to ask how long does it take for DLM to make changes to you profile? And is an Engineer visit always required when you have been capped?
Following repair works, some users (not many at all) have seen DLM take positive action within a few days, speeds increasing bit by bit in "capped" increments until the highest stable speed has been found.
Others have seen DLM stuck at low sync speeds with high attainable rates for weeks/months & some have simply requested & actually received a DLM reset - via their ISP, but BT OR have to do it.
I believe BT OR are now a little more relaxed in not INSISTING an engineer must be present, although in your case it may be helpful for witness/evidence purposes of what your line CAN achieve (as a belt & braces approach as obviously your own graphs/stats are just ignored).
Worst case scenario for you would be that the line is physically in "good" condition & any "problems" are caused by external means, outside BT's direct control.
Wasn't the REIN issue more or less tracked down at one point?
I'll start running the stats again though, so I can compare the stats now the work has been done in the PCP.
Your current error counts are probably only low due to the really low sync speed cap i.e. the connection isn't being pushed to its max.
However, prolonged monitoring may still help to determine the sources of interference/noise/abrupt disconnections etc.
It's a shame you didn't continue monitoring your stats as you may now be back to square one again.
PS. How can I update my stats so they look like yours, and give me more information?
That will all be in the next release. I am still testing/attempting to resolve an occasional issue of a few minutes of missing stats that only seems to occur during overnight virus scanning when the scanning program seems to hog all the PC's resources, spanning over a few minutes at a time.
I could email test versions for you to try if you were willing to provide detailed feedback as & when necessary.
(An couple of error / information log files are also created alongside the ongoing modem_stats.log)