Hi!

Thanks for the reply. 

1. Of course, I checked the bandwidth as the first element! Internal CPE220 Speed Test tool shows stable 60-80 Mbps between AP and Client. Bandwidth from the camera with H.265+ codec in calm not more 1 Mbps, in dynamic picture 3-4 Mbps. 4 Cams dynamic online by DDWRT statistic from LAN port direct connection from the switch with cameras or from AP connection shows the same maximum 15-16 Mbps heavy bandwidth load. So this is not a bandwidth issue. 

2. I tested the access availability to the Pharos menu - and when the one camera connected it is not loaded or loaded with 2-3 min delays. 

3. I created a demo copy of the local infrastructure with two other CPE220 units and other same 4 cameras, used brand new Cat6 factory made cables and got the same bugs, but with Client CPE220. I switch settings between AP and Client and the problem moved with the same CPE220 device. 

4. I downgrade both CPE220 firmware from 2.1.14 to 2.1.11 and problem disappear in the local demo. No delays with Pharos menu access at full load, no issues with traffic. Tomorrow will do the same at the site installed CPEs to test and check the difference. 

Thanks for the idea and info. Will try make changes with TX and reply.

So the final solution: 

TP-Link CPE220 v3 has real bugs in the firmware.

With the firmware 2.1.14 

All possible settings, changes in power TX, auto/ manual 0.1 distance, QoS, WMM on/off, fixed channel, fixed n-mode, fixed bandwidth, a brand manufactured cables changes, laser point alignments, fine-tuning, voodoo magic and a black cat did not help. 

One camera works with 83-87% packet loss, ping time average to AP 2050 ms.

Two cameras work with 45-67% packet loss, ping time average to AP 2900 ms.

With the firmware 2.1.11 

All the same possible settings tested: changes in power TX, auto/ manual 0.1 distance, QoS, WMM on/off, fixed channel, fixed n-mode, fixed bandwidth, a brand manufactured cables changes, laser point alignments, fine-tuning, voodoo magic and a black cat did not help. 

One camera works with 81-93% packet loss, ping time average to AP 2380 ms.

Two cameras work with 67-72% packet loss, ping time average to AP 3150 ms.

In addition, the firmware 2.1.11 has official known bugs:  (https://www.tp-link.com/ca/download/CPE220.html#Firmware)

So, I can't install 2.1.11 with known bugs and 2.1.14 doesn't work stable. 

Pros: nothing. 

Cons: lost 3 work days of the project time playing with TPLink FW headache, lost time and money to return and refund. 

Do not recommend and will never buy again.  

Solution: used another equipment. 

Sorry, but can't post survey, because already returned APs. I'm sure that there is not the frequency problem, I make two network structure copies in two different places at client's site and in the office. Both results are the same. 

R1D2 wrote

XaleX wrote

All possible settings, changes in power TX, auto/ manual 0.1 distance, QoS, WMM on/off, fixed channel, fixed n-mode, fixed bandwidth, a brand manufactured cables changes, laser point alignments, fine-tuning, voodoo magic and a black cat did not help. 

 

Ah, that's it. Take the black cat out of the directional link, it causes interferences in the frequency band. 

 

Seriously, post a WiFi survey and a spectrum analysis (use the CPE's Tools menu) and we can judge whether it was a wise decision to use the 2.4 GHz frequency band for a directional link and whether you can expect similar results with other equipment, too.

Jameslite wrote

what is the approximate bandwidth consumed by your IP cameras?
liteblue USPS Tracking USPS Liteblue

I use 265+ codec - in static mode near 1Mb/s,  4 cams with active pictures - 16-20 Mb/s. The same data at dirict cable connection to the router and NVR and through the other brand APs. 

The best firmware version is 2.1.13... try this!