Anyone Using an Asus DSL-AC68U

It's taken me up to a month before I saw the first positive change, however I believe I was delaying DLM due to severe swings in the SNRM as a result of me playing with the downstream parameters. Recently it has made two positive changes within a week. I'm now on 60M/20M, INP 5/0, Delay 16/1 as of this morning. I'm not currently fiddling with anything at this time.

I believe DLM considers the following:
- Error Seconds
- Severe Error Seconds
- Re-synchronisations
- SNR Margin Delta

I no longer believe DLM considers the following:
- FEC errors/seconds, I've had millions and DLM has been making positive changes

Regarding the Opmode post, yes I believe you're on G.INP (lucky sod). Assuming you're on a Huawei cabinet. ECI cabinets are apparently not getting G.INP at the moment from all information I've seen so far - though nothing official to verify that. If it's true then it sucks for me and many others, G.INP would also most likely mask the problems that users of this device tend to be suffering on VDSL2 fastpath.
 
12 hours and first DSL disconnect. Not just a PPP disconnect, as the DSL GUI page has reset. Doesn't appear to be DLM (not early hours and no change to pings).

This is on an interleaved line - I wouldn't have thought I'd have seen this.

Logs submitted but I'm not going to up my SNR to 10dB if that's suggested.
 
Modem as well as router. All the other stats are there, just not the Opmode........ (SNIP)

fwVer= FwVer:5.5.1.127_B_A60901 HwVer:T14.F7_0.1

lineState=up
Opmode=
SNRMarginDown=5.9 dB
AttenDown=11.5 dB
SNRMarginUp=8.9 dB
AttenUp=1.6 dB
DataRateDown=66817 kbps
DataRateUp=19999 kbps
WanListMode=1
FECDown=1854368
FECUp=6754
CRCDown=114
CRCUp=6
HECDown=0
HECUp=0
ADSLUpTime=3 days, 6:38, 14 secs
ADSLActiveTime=0 min, 13 secs
PowerDown=13.1 dbm
PowerUp=6.8 dbm
ATURID=26005443434e0000
ATUCID=b5004244434da44f
AttainUp=25969
AttainDown=84500
ShowtimeStart=13
TotalStart=27
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus

Not sure I can bothered to reflash - I may just plug my HG612 in briefly to verify.

Looks like another firmware bug then :(

Yeah I was on the HG612 lately, and yesterday seemed to have some troubled time in the evening which has eventually led to DLM intervening. No idea why as the HG612 normally holds up quite well.

I'll see what happens with the DSL over the next few days, not too fussed about the additional 16ms as it doesn't appear to stop me winning matches on CoD but would be nice for it to be removed. If after a week there's no change, I'll go back to the HG612 or maybe ECI for complete comptaibility and wait patiently.

I doubt the Asus will improve things, infact with DLM already interfering it will more than likely get worse
Sorry for the slight off-topic question but how long does it normally take for DLM to increase speed to full potential?

I had a problem on my line which resulted in 4 consecutive days of re-syncs and my speed dropping from 75Mb to 48Mb and pings increased from 24ms to 49ms.
I left it for 4 weeks so far and it appears my pings are stable at 24ms now but speed is sitting at 62Mb. Zen confirmed that there is still a banding on my line and if I want I can get an engineer out to reset the line but if it stays at 62Mb then I get charged £165+VAT for the privilege.
Should I leave it another month to see if it recovers or take the chance?

Go back to openreach modem/isp supplied gear if you havent and give it a week, if no improvement book an BT appointment, then monitor things closly between the time you book the appointment and the appointment date. This could be upto another week or 2, hopefully by then it shifts and then you can just cancel the appointment penalty free.

It's taken me up to a month before I saw the first positive change, however I believe I was delaying DLM due to severe swings in the SNRM as a result of me playing with the downstream parameters. Recently it has made two positive changes within a week. I'm now on 60M/20M, INP 5/0, Delay 16/1 as of this morning. I'm not currently fiddling with anything at this time.

I believe DLM considers the following:
- Error Seconds
- Severe Error Seconds
- Re-synchronisations
- SNR Margin Delta

I no longer believe DLM considers the following:
- FEC errors/seconds, I've had millions and DLM has been making positive changes

Regarding the Opmode post, yes I believe you're on G.INP (lucky sod). Assuming you're on a Huawei cabinet. ECI cabinets are apparently not getting G.INP at the moment from all information I've seen so far - though nothing official to verify that. If it's true then it sucks for me and many others, G.INP would also most likely mask the problems that users of this device tend to be suffering on VDSL2 fastpath.

Agree with all that especially the upto 4 weeks if you have a serious loss of speed to recover from and the thing about errors. Only thing im not sure on is the G.INP post, unless for others under OPMODE something is still displayed, in that case then yeah i guess its possible he is G.INP, still poor for it to not recognise it though.
 
Yeah I was on the HG612 lately, and yesterday seemed to have some troubled time in the evening which has eventually led to DLM intervening. No idea why as the HG612 normally holds up quite well.

I'll see what happens with the DSL over the next few days, not too fussed about the additional 16ms as it doesn't appear to stop me winning matches on CoD but would be nice for it to be removed. If after a week there's no change, I'll go back to the HG612 or maybe ECI for complete comptaibility and wait patiently.

Are you able to read the stats on your hg612, if so how? I am aware it is possible to unlock, is that by flashing it with a different firmware, if so do you know how?
Cheers....
 
Are you able to read the stats on your hg612, if so how? I am aware it is possible to unlock, is that by flashing it with a different firmware, if so do you know how?
Cheers....

If you take a look over on Kitz site you'll find links to the firmware and instructions, but it's a very straightforward process.

http://forum.kitz.co.uk/index.php/board,5.0.html - includes threads on the firmwares

https://huaweihg612hacking.files.wordpress.com/2011/11/hg612_unlock_instructions_v1-3.pdf
 
Looks like another firmware bug then :(

Only thing im not sure on is the G.INP post, unless for others under OPMODE something is still displayed, in that case then yeah i guess its possible he is G.INP, still poor for it to not recognise it though.

FYI - Have reconnected my HG612 and can confirm that I definitely am on G.INP.

Looks like the latest Asus firmware doesn't report G.INP (And possibly other modes too) correctly in the UI.

I guess this is a step in the right direction - The Asus now seems to give me a stable connection (With G.INP enabled) at pretty much the same sync as the BT Modem gives me (without G.INP). I think I might stick with the HG612 for a while and see if BT wants t keep me on G.INP even with that.
 
Last edited:
G.INP will most likely mask the problem. I've read this morning over on that forum that ECI cabinets are due to get G.INP after the Huawei cabinets are done (should be finished in roughly a week from now). So hopefully within the next 3 months a majority of ECI cabinets will have G.INP although the problem with the ASUS device still ideally needs to be solved.

@andyfitter2: From what I've read, once G.INP is on your circuit then it will stay on permanently.
 
FYI - Have reconnected my HG612 and can confirm that I definitely am on G.INP.

Looks like the latest Asus firmware doesn't report G.INP (And possibly other modes too) correctly in the UI.

I guess this is a step in the right direction - The Asus now seems to give me a stable connection (With G.INP enabled) at pretty much the same sync as the BT Modem gives me (without G.INP). I think I might stick with the HG612 for a while and see if BT wants t keep me on G.INP even with that.

Well thats weird then because the DSL-AC68U DOES support G.INP (or G.998.4 to give its proper name) as it has been seen on the administration settings pages as one of the options in various screenshots an example being here...
http://forums.overclockers.co.uk/showpost.php?p=27564420&postcount=1227

I can only imagine its a firmware bug if it is not showing it as enabled in the log files. HO hum another thing for them to look at..... Buggy driver more than likely.

G.INP will most likely mask the problem. I've read this morning over on that forum that ECI cabinets are due to get G.INP after the Huawei cabinets are done (should be finished in roughly a week from now). So hopefully within the next 3 months a majority of ECI cabinets will have G.INP although the problem with the ASUS device still ideally needs to be solved.

@andyfitter2: From what I've read, once G.INP is on your circuit then it will stay on permanently.

Im not sure if ECI cabinets in their current state support G.998.4. Huawei cabinets always had it as an option but for some reason until about the beginning of this year BT never enabled it. ECI cabinets i suspect are going to be more tricky, requiring software upgrades or worse hardware.

You are also right it will basically mask any issues, it will basically only interleave (although its not really interleaving but behaves in a similar manner) when it has to rather than every site. Its also a good thing if you live in an area that has power fluctuations as it should in theory adapt to those and keep your line speed up.

Finally yep once enabled i think it stays enabled, though you may be able to force it off on other devices. Its basically only an extension to a modulation type.
 
Last edited:
Well thats weird then because the DSL-AC68U DOES support G.INP (or G.998.4 to give its proper name) as it has been seen on the administration settings pages as one of the options in various screenshots an example being here...
http://forums.overclockers.co.uk/showpost.php?p=27564420&postcount=1227

I can only imagine its a firmware bug if it is not showing it as enabled in the log files. HO hum another thing for them to look at..... Buggy driver more than likely.



Im not sure if ECI cabinets in their current state support G.998.4. Huawei cabinets always had it as an option but for some reason until about the beginning of this year BT never enabled it. ECI cabinets i suspect are going to be more tricky, requiring software upgrades or worse hardware.

You are also right it will basically mask any issues, it will basically only interleave (although its not really interleaving but behaves in a similar manner) when it has to rather than every site. Its also a good thing if you live in an area that has power fluctuations as it should in theory adapt to those and keep your line speed up.

Finally yep once enabled i think it stays enabled, though you may be able to force it off on other devices. Its basically only an extension to a modulation type.

Regarding ECI cabinets and G.INP, I quote a BT Openreach engineer's post on the kitz forum.

Let me put folks minds at rest .......... G.INP is scheduled to be completed on all Huwaei Cabs by Q4 end. Then, work will begin on adding G.INP to ECI DSLAMS in Q1 of the new fiscal year. No links, no references ..... you'll just have to take my word for it.

From http://forum.kitz.co.uk/index.php/topic,15190.msg282655.html#msg282655

BT's fiscal year begins in April, this means we're a week or so away from Q1. I imagine it will take up to three months or so to roll out the changes.
 
Last edited:
Once enabled i think it stays enabled, though you may be able to force it off on other devices. Its basically only an extension to a modulation type.

Sure, I realise that, but now I'm back on the HG612 I wondered if DLM will detect that I don't need it any more - I read that DLM only adds it if it thinks that your line would benefit from it.
 
Regarding ECI cabinets and G.INP, I quote a BT Openreach engineer's post on the kitz forum.

From http://forum.kitz.co.uk/index.php/topic,15190.msg282655.html#msg282655

BT's fiscal year begins in April, this means we're a week or so away from Q1. I imagine it will take up to three months or so to roll out the changes.
I guess the key words in that statement are "work" "begin "adding" which to me at least indicates there is more than just enabling it involved as with Huawei cabinets... PS How do you know he is an Engineer? (I wanted to phrase that question better as it almost sounds like im saying liar, which im not, im just curious how you know he is a BT engineer, i do not read kitz forum that much so do not know enough about individual posters).

Sure, I realise that, but now I'm back on the HG612 I wondered if DLM will detect that I don't need it any more - I read that DLM only adds it if it thinks that your line would benefit from it.

Unlikely DLM will touch things unless with G.INP the line is significantly slower or performs significantly worse than it did when G.INP was not there.

If your speed is the same or similar (around 5(ish)Mb either way) of what it was then i doubt even if DLM can turn G.INP off once enabled it will do. There would be no need. G.INP both in terms of connection speed and latency (most of the time) should perform similar to what you had when the line was stable at its normal best. In fact the connection speed can possibly improve.

So short answer is NO i doubt it will be removed, unless you are seeing significant poorer performance.

If it is performing the same or similar speed etc wise it would not make sense to remove it as with it the line would/should be more stable, which if combined with similar speed etc you had before is a good thing (or that is how a computer system will/should see things.)
 
Last edited:
Ask on there yourself, I'm sure everyone (including kitz herself, the website owner) would say that he works for BT Openreach.

Fair enough, was not disbelieving you :) I freely admit you have more experience of that site and its users :) I rarely visit it. I wonder why Kitz does not have an ISP or similar tag for users, there must be loads of staff from various ISPs on there which often help out. I may fire off an email with that suggestion as that site has became quite a good resource.
 
FWIW: I replaced my constantly-rebooting-HH5 with a new DSL-AC68U this afternoon. Fiddly to setup - and not sure if I've got everything perfect yet. Slower than HH5 (27Mb download, vs only 20Mb on the Asus, but the Asus has been connected for two hours, the HH5 never managed to stay connected for even one hour since it was installed 2 weeks ago.

I am a happy customer, but in need of a tuning guide now...

R
 
After Jims request to get new feedback reports on the later firmware and seeing that after 6 weeks I managed to get back to pretty much where I was regarding sync rate before DLM kicked in after the last test, I decided to brave the 2187 firmware.

I've been running about a week now with only a couple of brief 30 second disconnects after a few days of uptime. Neither of these disconnects caused DLM to lower my sync rate and I used to see the same behaviour occasionally with the HH5 too so Im not too worried.

On previous firmwares this modem couldn't stay connected for more than 30 mins-2 hours so whatever changes they did in the recent firmware seem to have fixed it for me.

My stats and configuration are below. I enabled G.INP even though it appears the cab doesn't support it at the moment in the thought that if it does get rolled out soon and my line requires it, I don't need to modify the settings again. The ADSL settings I left to whatever they were set to initially as I figured they shouldn't have any bearing on the VDSL connection anyway.

Tdvs7eo.jpg
 
After Jims request to get new feedback reports on the later firmware and seeing that after 6 weeks I managed to get back to pretty much where I was regarding sync rate before DLM kicked in after the last test, I decided to brave the 2187 firmware.

I've been running about a week now with only a couple of brief 30 second disconnects after a few days of uptime. Neither of these disconnects caused DLM to lower my sync rate and I used to see the same behaviour occasionally with the HH5 too so Im not too worried.

On previous firmwares this modem couldn't stay connected for more than 30 mins-2 hours so whatever changes they did in the recent firmware seem to have fixed it for me.

My stats and configuration are below. I enabled G.INP even though it appears the cab doesn't support it at the moment in the thought that if it does get rolled out soon and my line requires it, I don't need to modify the settings again. The ADSL settings I left to whatever they were set to initially as I figured they shouldn't have any bearing on the VDSL connection anyway.

Looking at your attainable rate I'd say you're interleaved (despite the stats wrongly reporting fastpath), this might be masking some problems.
 
It was interesting to me it said Fastpath, I always used to be on Interleaved, even when i had the mass disconnects on previous firmwares. I assumed that 6-8 weeks back on the HH5 had moved me back to Fastpath, but it could just be reporting wrong :)
 
Looking at your attainable rate I'd say you're interleaved (despite the stats wrongly reporting fastpath), this might be masking some problems.

Could be right, i would not trust anything 100% what the device reports, HOWEVER it is possible his line will not manage fastpath effectively and 100% reliably, he has a pretty close attainable (8.9db) and noise margin (6.3db) so there is not much wriggle room there. His line is probably on the edge of doing about 70Mb and low to mid 60's typical (could easily do more but by typical i mean what DLM would think is best). I could be wrong as those attainable and noise margin figures from the Asus may also not be (to be polite) that accurate. If they are correct though i would not be shocked if every few (probably something like 4) weeks DLM ping pongs him back and forth between interleave and fastpath, unable to make up its mind which would be best for his line. STupid system does that to me now and again after 5 weeks just gone of 74Mb syncs ive now been interleaved and lost my 8Mb that always brings and thus now im down to 66Mb. Another 2-4 weeks and it will likely shove me back on fastpath for another 4(ish) weeks before it decides to have a mental fit and do something stupid again.

BT based DLM is useless im wondering what sub-unbundled Talk Talk, Sky and and couple of others would perform like on my linee as from those providers it is apparently a different system and algorithm which does not take weeks but rather days to make up its mind.
 
Last edited:
Back
Top Bottom