Anyone Using an Asus DSL-AC68U

Just a few moments ago I've updated to the most recent firmware posted on this thread (at the ASUS web storage).

I'll update in a couple of hours as to whether I get CRC's or if the FEC goes through the roof.
 
So far so good. Although my current connection is interleaved, I usually still get some ES/SES over the course of 24 hours, and usually at least a few ES in the first hour of uptime. FEC is also is good health too at the moment.

DSL-AC68U_3.0.0.4_376_2144-ga120ce8_DSL_1.0.1.9_1124.trx
Code: 
>tcapi get Info_Adsl lineState;tcapi show Info_Adsl;wan vdsl2 show mgcnt
up
near-end path0 fec: 5851(5851)
near-end path0 crc:   0(0)
near-end fec sec:       68(68)
near-end err sec:       0(0)
near-end ses sec:       0(0)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      85(207439)
far-end path0 crc:      0(1160)
far-end fec sec:        2(4714)
far-end err sec:        0(969)
far-end ses sec:        0(0)
far-end los sec:        0(328)
far-end ua  sec:        0(14579)

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

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=11.7 dB
AttenDown=10.4 dB
SNRMarginUp=12.6 dB
AttenUp=0.1 dB
DataRateDown=48999 kbps
DataRateUp=19999 kbps
WanListMode=0
FECDown=5851
FECUp=85
CRCDown=0
CRCUp=0
HECDown=0
HECUp=0
ADSLUpTime= 1:06, 18 secs
ADSLActiveTime=0 min, 18 secs
PowerDown=11.9 dbm
PowerUp=8.4 dbm
AttainUp=33488
AttainDown=106944
ShowtimeStart=18
TotalStart=18
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1517
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus

UPBO is off at the moment, I forgot to set it back to auto (note I haven't done a factory reset either at the moment).
 
Last edited:
Will do :).

Even with the HG612 I had some CRC and ES, and usually a lot more FEC by now. So far I'm impressed (if the stats are really what they say they are). If by 6pm the FEC count and CRC is still extremely lower than usual then I will override the downstream DSLAM parameters (fastpath with up to 80Mbps sync rate) and test that. So far things are looking very good though, ASUS might have solved this at long last.
 
Firmware 2144

Have just upgraded so still early days.

FEC still at 1500 per second 919,878 in 9min 34sec
Link is being reported as Fastpath with interleave Depth of 1033
No CRC up or down yet

Settings below:
TP3Oh6m.png
 
Using the beta, from the asuswebstorage link above, and it seems to be incorrectly reporting I'm on FastPath on the log page - my ping times are still 8ms higher than they should be due to DLM a week or so ago so I'm definitely still interleaved.

Will see how the CRCs pan out over time - 15 mins so far with 0 and I'd normally have a handful by now.
 
Ixel said:
Will do :).

Even with the HG612 I had some CRC and ES, and usually a lot more FEC by now. So far I'm impressed (if the stats are really what they say they are). If by 6pm the FEC count and CRC is still extremely lower than usual then I will override the downstream DSLAM parameters (fastpath with up to 80Mbps sync rate) and test that. So far things are looking very good though, ASUS might have solved this at long last.
Click to expand...

I'll have to give this new firmware a go....the one emailed out by ASUS hasn't given me much joy so far.

The thing that's bugging me about this whole issue is that if the negative DLMing is FEC related, why is it negging the download speed? Surely the FECDown error correction is done in the Mediatek modem, so the modem must be sending some data back to the DSLAM for it to know that the FEC correction rate is out of control?

Is it possible that the Mediatek modem is mis-reporting the number of corrections or sending the wrong data back to the DSLAM? On my setup the modem has given me consistently high upload speeds and the DLM has not made any real adjustments to them. My FECup corrections are very low in comparison to the FECdown corrections, but surely the FECup corrections have to be done in the DSLAM and reported back to the modem?

If the modem is just counting the corrections wrong or is reporting the wrong number back to the DSLAM (surely it needs to report the uncorrectable errors not the correctable ones), could this whole problem just be caused by someone at Mediatek misunderstanding the BT spec for error reporting?

Anyway I hope the latest firmware fixes the problem, the fact that it can successfully connect at higher speeds before being DLMed is a good indication that the basic performance of the modem should be good if they can knock out the bugs.
 
Evil Shubunkin said:
Using the beta, from the asuswebstorage link above, and it seems to be incorrectly reporting I'm on FastPath on the log page - my ping times are still 8ms higher than they should be due to DLM a week or so ago so I'm definitely still interleaved.

Will see how the CRCs pan out over time - 15 mins so far with 0 and I'd normally have a handful by now.
Click to expand...

Since interleaving can be applied in both directions, is it possible that your interleaved in one direction but not the other? The status page doesn't make any distinction between up and down interleaving.
 
IronRod said:
Since interleaving can be applied in both directions, is it possible that your interleaved in one direction but not the other? The status page doesn't make any distinction between up and down interleaving.
Click to expand...

Possible I suppose. Definitely interleaved downstream since my sync rate reduced by about 10%, which is in line with DLM interfering. Upstream not affected, so that could be why it's showing FastPath right enough.
 
Evil Shubunkin said:
Possible I suppose. Definitely interleaved downstream since my sync rate reduced by about 10%, which is in line with DLM interfering. Upstream not affected, so that could be why it's showing FastPath right enough.
Click to expand...

I'm not quite on the very latest firmware release yet, but my connection is displayed a being on Fastpath despite quite high ping times (30ms). Also telnetting in gives quite a large number for the interleaving depth.....I'm definitely interleaved at least one direction.
 
So far all is well. Only one observation is that the FEC seconds are now incrementing every second (20-25 FEC a second on average), but the FEC is still WAY lower than it has been, even comparing to the HG612 so far. Absolutely no ES or CRC, would've had some certainly within the first hour usually, and certainly get some on the HG612. Provided the average rate of FEC is maintained it's still a bit lower than the HG612.

Code: 
>tcapi get Info_Adsl lineState;sleep 1;wan vdsl2 show mgcnt;sleep 1;tcapi show  Info_Adsl
up
near-end path0 fec:     47867(47851)
near-end path0 crc:     0(0)
near-end fec sec:       1217(1217)
near-end err sec:       0(0)
near-end ses sec:       0(0)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      1123(208477)
far-end path0 crc:      0(1160)
far-end fec sec:        12(4724)
far-end err sec:        0(969)
far-end ses sec:        0(0)
far-end los sec:        0(328)
far-end ua  sec:        0(14579)
outDiscards=410
inDiscards=7
outBytes=267953896
inBytes=962813393
outPkts=902789
inPkts=1009486
fwVer= FwVer:5.5.1.125_B_A60901 HwVer:T14.F7_0.1

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=11.4 dB
AttenDown=10.4 dB
SNRMarginUp=12.6 dB
AttenUp=0.1 dB
DataRateDown=48999 kbps
DataRateUp=19999 kbps
WanListMode=0
FECDown=47843
FECUp=1123
CRCDown=0
CRCUp=0
HECDown=0
HECUp=0
ADSLUpTime= 3:45, 54 secs
ADSLActiveTime=0 min, 18 secs
PowerDown=11.9 dbm
PowerUp=8.4 dbm
AttainUp=33488
AttainDown=105996
ShowtimeStart=18
TotalStart=18
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1517
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus

EDIT 1: Interesting, a few minutes later the FEC continous counting has stopped (that has never happened on previous firmware) after a big spike. Now it's static at the moment.
Code: 
near-end path0 fec:     90186(90186)
near-end path0 crc:     0(0)
near-end fec sec:       1582(1582)
near-end err sec:       0(0)
near-end ses sec:       0(0)
near-end los sec:       0(0)
near-end ua  sec:       0(0)
far-end path0 fec:      1123(208477)
far-end path0 crc:      0(1160)
far-end fec sec:        12(4724)
far-end err sec:        0(969)
far-end ses sec:        0(0)
far-end los sec:        0(328)
far-end ua  sec:        0(14579)
 
Last edited:
Firmware 2144
No relief for the FEC count woes here - same rate as previous firmware at approx. 1950 per second.

Code: 
outDiscards=432
inDiscards=2
outBytes=61264397
inBytes=407330866
outPkts=211379
inPkts=319062
fwVer= FwVer:5.5.1.125_B_A60901 HwVer:T14.F7_0.1

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=5.9 dB
AttenDown=9.3 dB
SNRMarginUp=6.2 dB
AttenUp=0.1 dB
DataRateDown=69347 kbps
DataRateUp=20000 kbps
WanListMode=1
FECDown=17404895
FECUp=30
CRCDown=0
CRCUp=3
HECDown=0
HECUp=0
ADSLUpTime= 2:28, 15 secs
ADSLActiveTime=0 min, 19 secs
PowerDown=13.3 dbm
PowerUp=4.4 dbm

AttainUp=21267
AttainDown=101252
ShowtimeStart=19
TotalStart=19
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=1033
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus (Annex L)
 
2144 beta firmware

Still something not quite right, but I have to bear in mind it's gone dark now and there could be interference somewhere.

2 1/2 hours uptime and the stats look like this:

Code: 
outDiscards=251
inDiscards=32
outBytes=99011126
inBytes=247274578
outPkts=348994
inPkts=327671
fwVer= FwVer:5.5.1.125_B_A60901 HwVer:T14.F7_0.1

lineState=up
Opmode=ITU G.993.2(VDSL2)
SNRMarginDown=6.1 dB
AttenDown=11.6 dB
SNRMarginUp=6.2 dB
AttenUp=0.1 dB
DataRateDown=63119 kbps
DataRateUp=16994 kbps
WanListMode=1
FECDown=14961
FECUp=10
CRCDown=551
CRCUp=2
HECDown=0
HECUp=0
ADSLUpTime= 2:37, 50 secs
ADSLActiveTime=0 min, 19 secs
PowerDown=14.2 dbm
PowerUp=6.5 dbm
ATURID=26005443434e0000
ATUCID=b5004946544eb204
AttainUp=18639
AttainDown=93472
ShowtimeStart=19
TotalStart=19
ATURANSIRev=0
ATUCANSIRev=0
ATURANSIStd=0
ATUCANSIStd=0
InterleaveDepth=913
AdslStandard=VDSL2
AdslType=ANNEX_B
mtenStandard=G.dmt.bisplus (Annex L)

The burst of 551 downstream CRC were within a 10 - 15 minute window as I had checked the log, went off and did some other stuff, and happened to look back at the log page and went from 0 to that.
 
sumowesley said:
Firmware 2144
No relief for the FEC count woes here - same rate as previous firmware at approx. 1950 per second.
Click to expand...

FEC is spiralling upwards here now. Will post stats before I change to fastpath soon. CRC's still remain 0 though.

Evil Shubunkin said:
2144 beta firmware

Still something not quite right, but I have to bear in mind it's gone dark now and there could be interference somewhere.

The burst of 551 downstream CRC were within a 10 - 15 minute window as I had checked the log, went off and did some other stuff, and happened to look back at the log page and went from 0 to that.
Click to expand...

At least we know the CRC counter is still working from that.
 
Last edited:
Ixel said:
FEC is spiralling upwards here now. Will post stats before I change to fastpath soon. CRC's still remain 0 though.



At least we know the CRC counter is still working from that.
Click to expand...

Can I ask what DSL settings you're on as my CRC's have just spiked again in the thousands?

Cheers
 
You must log in or register to reply here.
Back
Top Bottom