cancel
Showing results for 
Search instead for 
Did you mean: 

The TP-Link W9980 and G.INP

JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

The TP-Link W9980 and G.INP

Hi all, I just wanted to write a quick post to advise on a positive update with regards to the TP-Link W9980 and g.inp.
As has been previously reported by myself and others, the W9980 was incompatible with g.inp, and owing to it using the same chipset as the OR ECI modem, displayed the exact same symptoms / problems, i.e. higher latency and lower connected speed.
I'd pretty much given up on the W9980, and have been using a Huawei OR modem, unlocked with HW's SP08 firmware, which had cured the 'problem'.
That said I thought I'd persevere for the fun of it, and have been in touch with TP-Link's tech support for the last few weeks. There was considerable tooing and froing with much disbelief on their part and much convincing on mine, but we now appear to be getting somewhere.
After a variety of tests, different firmwares, Lantiq data capture tools, and another beta firmware which I upgraded to this morning, the W9980 is now connected with g.inp enabled. It's still very early days, but so far it's looking very promising. The latency has remained at the same level it was with the Huawei, as has my speed (I'm currently connected at 79913/19999). You can see in the below TBB graph where I switched over just before 11am.

The only slight difference is that my BT line profile has dropped a smidge from 77.3 to 77.26.
Like I said it's still very early days and I do think there's still work for TP-Link to do, for example I'm not sure that the d/s snr is being reported correctly, but it's definitely a step in the right direction. It also bodes well for users of the OR ECI modem, and shows that a software update may well be able to fix the problem.

Edit - TBB graph was live not a snapshot.
23 REPLIES
Community Veteran
Posts: 6,773
Thanks: 257
Fixes: 20
Registered: 16-02-2009

Re: The TP-Link W9980 and G.INP

could you pm me the new f/w I want to try it out.
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

Done. As mentioned, it's a beta so the normal caveats apply. Please don't blame me if it knackers anything.
Community Veteran
Posts: 6,773
Thanks: 257
Fixes: 20
Registered: 16-02-2009

Re: The TP-Link W9980 and G.INP

Cheers running fine (so far anyway)
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

Excellent, let me know how you get on. No doubt I'll be in touch with TP-Link again soon, so I can always pass any feedback on to them.
Community Veteran
Posts: 6,773
Thanks: 257
Fixes: 20
Registered: 16-02-2009

Re: The TP-Link W9980 and G.INP

As I said in my pm it appears to be syncing a lot better now. Have asked PN to reset my profile so will see if the speedtests catch up.
Wonder when they will release this f/w.
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

I'll be sure to ask them. When I first started talking to them they mentioned about adding vectoring compatibility later in the year, so I'll nudge them about that again as well.
I seem to be getting some packet loss at the moment, which I'll have to keep an eye on. 
Community Veteran
Posts: 6,773
Thanks: 257
Fixes: 20
Registered: 16-02-2009

Re: The TP-Link W9980 and G.INP

Last time I spoke to them they said they were going to introduce a network diagram (like the HH5 has) but that hasn't appeared in the past 6 months. I also asked for a local dns server but they haven't implemented that either. Currently running pdns on my "server" pc.
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

I'll make a note and add those requests to my next reply to them.  Smiley
Community Veteran
Posts: 6,824
Thanks: 1
Registered: 27-10-2012

Re: The TP-Link W9980 and G.INP

Quote from: JHewess
I seem to be getting some packet loss at the moment, which I'll have to keep an eye on. 

This is probably a local issue - I am also seeing low level at peak times now. Which exchange are you on?
kitz
Rising Star
Posts: 817
Thanks: 46
Registered: 08-06-2007

Re: The TP-Link W9980 and G.INP

Hi JHewess
Thanks for that info, I was awaiting further info from TP-link expected early next week so this is good news that the beta is working.  I also have the Lantiq tool but as Im on an ECI cab I wasnt able to assist with any testing.
>>> Last time I spoke to them they said they were going to introduce a network diagram
Ive been pushing for decent stats and made a pretty good case for it..  then they decided that customers wouldnt be interested, despite it being the only consumer vdsl router that doesnt  (note consumer routers exclude the likes of telco suplied HHs etc)
Now that you have the Lantiq tool, you should be able to see that all the information is available from the router, and its just a case of TP-Link actually making it available via telnet.
The more that ask, then the more chance it could be available.  btw, the lantiq tool doesnt work on any non-beta f/w.
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

@ AndyH, SDESTBR. Tho I personally suspect the packet loss may be from my currently ott sync, as I've rarely, if ever, experienced any until switching to the 9980 with the test firmware. With any luck it'll stabilise in the next couple of days, will keep an eye on it.
@ Kitz,  I've been hammering them for decent stats too, and will continue to do so.
While telnet now works from all lan ports (like u say most likely because of the beta firmware) the stats reported are still stunted. I've yet to really have a play with the Lantiq software, but will do now the 9980 is going to be connected for more than an hour or so at a time while testing etc.
Thanks,
Justin
kitz
Rising Star
Posts: 817
Thanks: 46
Registered: 08-06-2007

Re: The TP-Link W9980 and G.INP

TP-Link have released a beta version that they are hoping will fix this issue.  Its available for download via my forums and they would also please like some feed back to see if it is working correctly.
Download available and how to get linestats can be found here
http://forum.kitz.co.uk/index.php/topic,15322.0.html

I'll try also monitor this thread if HairyBiker would like to post his stats too so I can send the info back to TP-link
I'm assuming the version they sent me last night is the same one that JHewess also has TD-W9980v1_0.6.0_1.10_up_boot(150409)_2015-04-09_11.19.29
TIA
Community Veteran
Posts: 6,773
Thanks: 257
Fixes: 20
Registered: 16-02-2009

Re: The TP-Link W9980 and G.INP

/usr/sbin # ./dslLineStatusCheck.sh 
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=0 bReTxEnable=0 bVirtualNoiseSupport=0 b20BitSupport=0
nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0
nReturn=0 nChannel=0 nDirection=0 nNFEC=96 nRFEC=16 nLSYMB=6053 nINTLVDEPTH=253 nINTLVBLOCK=96 nLPATH=0
nReturn=0 nChannel=0 nDirection=1 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0
nReturn=0 nChannel=0 nDirection=0 nTp=5 nMp=1 nSEQ=70 nBP=79 nMSGC=64 nMSGLP=0
nReturn=0 nChannel=0 nDirection=1 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0
nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=176458 bValid=1 nEftrMin=166528 nErrorFreeBits=175691880 nLeftr=64218
nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=176458 bValid=1 nEftrMin=4294967295 nErrorFreeBits=0 nLeftr=0
nReturn=0 nData="5008 0000 0001 0102 "
nReturn=0 nChannel=0 nDirection=0 ActualDataRate=19997000 PreviousDataRate=0 ActualInterleaveDelay=800 ActualImpulseNoiseProtection=20 ActualNetDataRate=19997000 ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=20
nReturn=0 nChannel=0 nDirection=1 ActualDataRate=62018000 PreviousDataRate=64961000 ActualInterleaveDelay=15 ActualImpulseNoiseProtection=420 ActualNetDataRate=64961000 ActualImpulseNoiseProtectionRein=10 ActualImpulseNoiseProtectionNoErasure=40

Here's my stats. Version is the same.

Firmware Version:
0.6.0 1.10 v0021.0 Build 150409 Rel.40749
JHewess
Grafter
Posts: 81
Thanks: 4
Registered: 20-11-2014

Re: The TP-Link W9980 and G.INP

Hi Kitz, yes, that's the same version.  Smiley
I've just emailed my contact back about the random downstream SNR. In fact, while writing the email to him it changed several times from 2.5 to 2.1 to 1.8, and as I type this is currently at 3. It's very odd as it doesn't appear to be effecting my connection speed which has stayed steady around the 79.9 mark since Saturday. That said, it does look like my connection (according to my TBB graph) has dropped twice since I started using this firmware. I'm just going by gateway switches here, the dropped connection doesn't appear to be indicated by the router in any way.
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0
nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=0 b20BitSupport=0
nReturn=0 nChannel=0 nDirection=0 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0
nReturn=0 nChannel=0 nDirection=1 nNFEC=32 nRFEC=16 nLSYMB=16 nINTLVDEPTH=1 nINTLVBLOCK=32 nLPATH=0
nReturn=0 nChannel=0 nDirection=0 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0
nReturn=0 nChannel=0 nDirection=1 nTp=2 nMp=2 nSEQ=64 nBP=0 nMSGC=58 nMSGLP=0
nReturn=0 nDirection=0 nHistoryInterval=0 nElapsedTime=27093 bValid=1 nEftrMin=60928 nErrorFreeBits=4159510911 nLeftr=4294967261
nReturn=0 nDirection=1 nHistoryInterval=0 nElapsedTime=27094 bValid=1 nEftrMin=4294967295 nErrorFreeBits=8264771 nLeftr=0
nReturn=0 nData="5008 0000 0001 0102 "
nReturn=0 nChannel=0 nDirection=0 ActualDataRate=19978000 PreviousDataRate=0 ActualInterleaveDelay=0 ActualImpulseNoiseProtection=470 ActualNetDataRate=19999000
ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=40
nReturn=0 nChannel=0 nDirection=1 ActualDataRate=79899000 PreviousDataRate=79993000 ActualInterleaveDelay=16 ActualImpulseNoiseProtection=440 ActualNetDataRate=79993000
ActualImpulseNoiseProtectionRein=0 ActualImpulseNoiseProtectionNoErasure=40

I've also asked him again about the possibility of implementing better stats into the router's web gui.