Bad news... According to the DMT forum web site, Speedtouch are planning to disable the CLI commands in future versions of the firmware which the DMT tool uses to source its information and to set the the various tweak options. Already, some people have been trying to persuade them that this would be a spectacular "own goal" and would almost certainly hurt their sales.

See 4th post down for details within the discussion forum:

http://forum.mhilfe.de/viewtopic.php?t=1622&postdays=0&postorder=asc&start=320

DMT v7.20 is out

added: compatibility with older firmware-versions/commands (Menu Special --> Misc.Options --> FW spec.)

added: small improvements/bug fixes

JinxterX2 - thank you for all your help by way of your posts - I hope you can help me some more, please!

I've recently purchase a 546 after seeing what can be achieved with the DMT tool; however I'm struggling to maintain a stable line. I game and as such stability is most important (as is a low ping). I've seen syncs as high as 6400 approx, but I find most stability happens around 5126. Is there any way, with my current gear, that I can stay around that speed?

I

you might have the same problem as me that snr fluctuations mean that at one time of day you could tweak it to synch at 10snr and its the right sync but another time fo day it would be way too low and mess up your BRAS profile. This is why I had to stop forcing my router to synch at 9snr.

I would use the 'modify' checkbox instead of the slider and enter values directly into Register00 using only values like 08,10,18,20,28,30,38,40,48,50,58,60,68,70,78 etc. There is a slight flaw in the slider routine which can result in the wrong value being sent to Register00, I don't know if this has been fixed in the latest DMT but the author was made aware of the problem.

If you want to try and be stable at approx 5120kbps, you could try putting in various high values (during the daytime when the DSL signal should be strongest) until you sync near or at that speed, then pray it stays like that all the time, lol. A lot depends on if your SNR margin drops at night and what your Target SNR margin is set to in the DSLAM (higher the better if you have a noisy line).

I don't know what your 546 is like for generating heat but my 516v6 is like a mini heater, convinced this can't be good, I've put heatsinks on the 6338 chipset, RAM and Line Driver IC, plus cut a hole in the top of the case and inserted a small 12v fan Pretty sure it's helped stability and reduced CRC/HEC errors but I'll find out for sure over the next few days.

For true stability on MAX you'd need a router that did Tone Masking or allows you to set a maximum sync bitrate, there's a few around that do that kind of thing.

Hi JinxterX2

Could you provide a list of these routers?

Phil

For Tone Masking/Carrier Selection the Belkin 7633 (F5D7633uk4A) and US Robotics 9105 are two that I know of but haven't tested myself, for bitrate limiting, can't remember, but they have been talked about in this forum, so a search should reveal something.

Thank you JinxterX2 - I'll try the checkbox, as advised. My 546 is ok for heat although I would say it gets warm to the touch. I have mine wall-mounted (cables going down). Is the snr in the DSLAM something that can be quite easily changed? I've heard that some of the Draytek kit will allow you to set a max bitrate; however one of my reasons for going with the 546 was price! I'm kind of hoping that this whole mess will somehow be sorted by BT, at some point :-)

Chrysalis - yes, my snr does vary quite a bit although not quite as much as yours it's still a problem nonetheless. Certainly not good when 1/2 way though an Unreal ONS match!!

In reply to:

---

Is the snr in the DSLAM something that can be quite easily changed?

---

The BT line management system should change it automatically if it decides you have an unstable line.

DMT v7.21 is out

added: support for displaying "adsl info"-data during SNR-observation (Menu Special --> Misc.Options)

added: Information-Panel-width (right side) is automatically adapted to current DMT-Window-width

fixed: wrong Resync/Retrain-recognition (red line) during SNR-observation. (only under certain circumstances)

fixed: small SNR-Slider inaccuracies (modemoptions)

fixed: DMT could not connect to Router (after Reboot) if DNS-Names were used instead of IP-Addresses