@dunxd 

Try this tool:

https://mega.nz/file/dZMwzajS#riNyIhCJHBxuqk6oCKBODehymMMQzZPrnZB7ETZ3gFA

@PowerlineFW 

2.8 worked beautifully on my PA8030.  Thanks so much for your help.

@PowerlineFW 

In my exp with TL-PA8030P I've found the 2.6 a little instable (but way better that the orginal firmware) but with higher reported speed.

On the other hand, the 2.7 and 2.8 gives lower bandwidth (+/- 10%) but are very stable.

Thanks again for sharing.

@PowerlineFW That tool (which looks to be for Zyxel powerline devices) seems designed to work on Windows XP.  On Windows 10 it renders really badly, so I can't really see how to use it.  Prompted by this, I took a look at more recent Zyxel PowerLine utilities.  These couldn't see any of my TP-Link devices, or wouldn't run.  Maybe someone else has had more success than me.

@dunxd

I tried the utility just to see if I can observe the same issue as you.

the utility runs fine on my windows 10 and it finds the device connected to lan.

My GFX is from nvidia.

@turboleak maybe the problem was installing the 64 bit version.  I installed the 32 bit, and it seems to start.  However, I get an error message immediately saying Error[1]: Get NIC Info.  Perhaps it is because my Windows 10 computer is a laptop with only a WiFi NIC.

However, the tpPLC Utility, which also relies on WinPCAP, manages to detect all my PowerLine devices.

Anyway, since you managed to get it working, can you say whether it allows update of firmware on WiFi enabled TP-Link Powerline devices such as TL-WPA8630P V2?  Does it allow firmware update using NVM and PIB files, or only BIN as in tpPLC?

I don't own a 8630P v2, only have two 8630 V1. They are detected by the zyxel utility only if they are connected via lan cable to the network. My pc is also connected via lan cable. I installed the 64bit version and it works with no problems on my windows 10 X64 ( latest release ). Regarding flashing, at least on my devices, it asks for the .pib and .nvm.

@turboleak does tpPLC require the BIN file or NVM and PIB for updating firmware on the WPA8630s that you have?

For me tpPLC only allows BIN for upgrading firmware on WPA8630P V2 and WPA7510 V2.  I think @PowerlineFW suggested the Zyxel tool as a way of upgrading the WPA8630 V2 models using NVM and PIB but they didn't go into detail.  I have no idea if the Zyxel tool offers any benefit over tpPLC.

@dunxd

In my case, V1, it asks for the nvm and pib.

Yes, I believe that  @PowerlineFW suggestion for you to use the zyxel utility was to indeed allow you to use a nvm+pib method. If you can find a way of sucessfully lauching the zyxel utility on a pc whose lan port is directly connected to lan1 port of your 8630 v2 then it will probably find it and allow you to use a nvm+pib.

As there are no publicaly available .pib's for the 8630p v2, if you are sucessfull in lauching the zyxel utitly and it discovers your device, you face two options:

 - flash your device with the .pib of a v1 model.

 - backup your device .pib with the utility on my dropbox folder and then flash it using that same .pib. ( I think this is the safe method. worst case yo still have your original pib to recover the device. )

I have flashed a number of devices (8010, 8030, 8630) with the 2.8 firmware and yes, they run much more stable than with the original fw. Also, some Devolos with 2.8.0 are in the network as well.

However, from time to time now, instead of an adapter locking up completely (ie power cycle necessary as with the old fw), the adapter leaves the plc network and fails to re-join the exiting powerline network.

The CCO (either on any of the tp-link or devolo adapters) just rejects the adapter and any adapter trying to re-join, the freshly started adapter even after power-cycle or reset stays in STA mode.

root@xxxx:~/bin# plcstat -t
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 000 18:A6:F7:A2:03:F6 18:A6:F7:A2:03:F4 n/a n/a QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS
root@xxx:~/bin#

In this case, also resetting the CCO won't work, as the CCO role switches to another adapter which will also reject any re-join.

So each and every power line adapter will need to be reset or power-cycled for everthing work properly again.

Any ideas what could cause this? Is it just another firmware bug?