@val_andrio mine is the EU version not the UK one so I should get the latest EU v1 version right? Do you have a direct link for that like the one you posted for the UK one please ?

I have the PA8030P v1 (bought in Switzerland). The current firmware is 2.0.0.382-05_803111_160328_914.

I have no instability issues, but since the firmware is more than four years old, I was wondering if I would potentially gain any speed advantage from flashing a newer firmware, either some beta or something cooked up by the good folks in this thread. At the moment, the TPPLC utility reports 85-100 Mbps between my two adapters.

Is there any point of trying a newer firmware, or am I best off staying with what I have got?

Binger wrote

@val_andrio mine is the EU version not the UK one so I should get the latest EU v1 version right? Do you have a direct link for that like the one you posted for the UK one please ?

@Binger 

Although I don't think there will be any difference between the EU and UK version, here is a link to an EU firmware for V1.

https://static.tp-link.com/res/down/soft/TL-PA8030P(EU)_V1_160328.zip

You can also go to https://www.tp-link.com/ change the country to your preference and then search for 8030P on the top search.

In that product page there is a "Support" link that will list all the available firmwares.

Some more long-term experience with firmware MAC-QCA7500-2.8.0.30-01-20190705-CS:

This firmware is much better than before, but (still) reacts very strange to distortions or noise, especially it reacts persistently after a single glitch!
 

• A station exposed to noise does seems to see it's CCO thus not creation a network on it's own by assuming CCO role, but the CCO seems to not allow the station to (re-)join the network. This happens regularly after glitches... Workaround: reset from attached router... not nice and not working at all times, as a single CCO reset makes the CCO role wander and sometimes the new CCO also refuses to let the device join.

# plcstat -t
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 002 18:A6:F7:A2:27:4E 18:A6:F7:A2:27:4C n/a n/a QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS

• A station is still seen in the network, but no details shown eg in the topology map, neither any user data communication possible:

# plcstat -t
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 002 98:DE:D0:9D:78:7F 98:DE:D0:9D:78:7D n/a n/a QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS
 REM CCO 001 F4:06:8D:50:2E:BC 30:B5:C2:86:42:9E 165 211 QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS
 REM STA 003 18:A6:F7:A2:03:F6 A4:14:37:2C:6A:F4 141 128
 REM STA 004 98:DE:D0:9D:6D:7B 98:DE:D0:9D:6D:79 036 082 QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS
 REM STA 005 30:D3:2D:0A:40:8E 24:62:AB:35:11:E7 045 113 QCA7500 MAC-QCA7500-2.8.0.30-01-20190705-CS

• In this (persisting) state, the other side also sees no user data nor mgmt info

# plcstat -t
 P/L NET TEI ------ MAC ------ ------ BDA ------  TX  RX CHIPSET FIRMWARE
 LOC STA 003 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
 REM CCO 001 F4:06:8D:50:2E:BC FF:FF:FF:FF:FF:FF 562 707
 REM STA 002 98:DE:D0:9D:78:7F FF:FF:FF:FF:FF:FF 128 143
 REM STA 004 98:DE:D0:9D:6D:7B FF:FF:FF:FF:FF:FF 057 052
 REM STA 005 30:D3:2D:0A:40:8E FF:FF:FF:FF:FF:FF 019 037

• Other and more symptoms I wasn't able to catch in detail so far ...

So is anyone anywhere working on this? Or would it be feasible to get a SDK from somewhere and work on it?

G.hn is not an alternative in highly noisy sites either, I'm afraid... but it has an SDK available at least!

Hi,

Does anyone know if the last TL-PA9020P (or TL-PA9025P for france), has the same issue of connection problem between 2 CPL with the last frimware? I have the TL-WPA8635P connected to a TL-PA8015P with custom firmwares found on this forum to solve connection problem (connection was lost every week) and I want to change for the TL-PA9025P but I don't want to have same connection problem as before.

@PeterM. No, you have to update incrementally. See this thread. Post #71-75 describes this. The pib file changes (in size) with some firmware updates.

@Ariek Thanks for your advice. I did not need to step through incremental updates, for the unit already was on 2.2 and PIBs are still compatible for 2.10. I went straight from 2.2 to 2.10, unit is fine. My first attempt probably failed due to the ancient Windows XP laptop I was using, successful attempt ran from a modern Windows 10 desktop.

So now I've got one TL-PA8030P V2, german version, reporting firmware 2.10.0.32-01_803112_170704_905.