CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-05-27 12:53:46
Model : CPE510

Hardware Version :

Firmware Version : CPE510(US)_V2_180117

ISP : AT&T Uverse DSL

Hello All,I have deployed two CPE510 devices, one as the AP and the other as a Client device. I am trying to connect to buildings that are about 50 feet away from each other.The AP CPE510 is configured with a static-IP and is plugged into a LAN that encompasses the DSL router to the Internet. The CLIENT CPE510 is also configured with a static-IP plugged into a switch that provide a small network of computes that use it to access the other LAN to get access to both other systems (file server and printer) and the Internet.I have installed the two CPE's with the latest revision of firmware (CPE510(US)_V2_180117) and I have been experiencing a very frustrating thing...The two CPE510's will sync up with extremely good signal level and then for no good/known reason the connection will be lost, the client CPE510 shows no signal and the AP CPE510 shows no connected devices!I had the opportunity to play around with the setup and tried to run a constant "ping" of Google's DNS machines (8.8.8.8) to attempt keep traffic flowing across the RF link between the two CPE510's, however, the units would still sync for about 1-to-3 minutes and then loos signal!I did get a little better reliability (CPE's connected for almost an hour) when I started the download of a Debian Linux ISO image (approx 4.1GB in size) and the link stayed active long enough to transfer about 3.9GB of the file before the link died and aborted the transfer.I looked around these forums ans saw mention of a fix for a similar issue in the "beta firmware" area, but no mention of this problem/issue with the CPE510!!!!Please advise what I should do to fix this link reliability issue, it is making things unbearable and very unusable!Thanks, in advance!
  0      
  0      
#1
Options
7 Reply
Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-05-28 00:58:43
Update:I found the thread in "Beta Firmware": https://forum.tp-link.com/showthread.php?101999-WBS510_V2_171026_Beta-Fix-the-problem-that-WBS510-as-AP-will-disconnect-with-all-stations-after-running-for-a-whileAnd I am now trying this version in the CPE510 configured as the AP!Will update this thread when I get some time on this revision of firmware...Thanks.
  0  
  0  
#2
Options
Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-05-29 01:19:27

tplink_cpe510_user wrote

Update:I found the thread in "Beta Firmware": https://forum.tp-link.com/showthread.php?101999-WBS510_V2_171026_Beta-Fix-the-problem-that-WBS510-as-AP-will-disconnect-with-all-stations-after-running-for-a-whileAnd I am now trying this version in the CPE510 configured as the AP!Will update this thread when I get some time on this revision of firmware...Thanks.
Latest version for CPE510 is v2.1.12 of 2018-03-07, which includes the fixes in the beta version. But support sites are not always up-to-date, so you can download v2.1.12 from the WBS510 page: https://static.tp-link.com/2018/201803/20180307/WBS510(UN)_v2.0_20180202.zip

However, you have to try wether CPE510v2 accepts it - I installed this firmware on all my Pharos devices (CPE210v1, CPE510v1.2, WBS201 and WBS510). Only CPE210v2/v3 uses a different image. Also EU and US versions of the firmware are the same, albeit different setting ranges will be enabled on EU devices vs. US devices.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#3
Options
Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-05-29 23:05:38

R1D2 wrote

Latest version for CPE510 is v2.1.12 of 2018-03-07, which includes the fixes in the beta version. But support sites are not always up-to-date, so you can download v2.1.12 from the WBS510 page: https://static.tp-link.com/2018/201803/20180307/WBS510(UN)_v2.0_20180202.zipHowever, you have to try wether CPE510v2 accepts it - I installed this firmware on all my Pharos devices (CPE210v1, CPE510v1.2, WBS201 and WBS510). Only CPE210v2/v3 uses a different image. Also EU and US versions of the firmware are the same, albeit different setting ranges will be enabled on EU devices vs. US devices.
Thanks for the response...The last statement in your reply has me concerned, the CPE510 I have is v2 hardware version which, according to my understanding, is equivalent to the v2 version of the CPE210, etc.So, is the v2 hardware version of the WBS510 exactly like the v2 version of the CPE510???? As you are aware, the WBS510 v2 firmware is here: https://static.tp-link.com/2018/201803/20180307/WBS510(UN)_v2.0_20180202.zip
  0  
  0  
#4
Options
Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-05-30 02:40:50

tplink_cpe510_user wrote

The last statement in your reply has me concerned, the CPE510 I have is v2 hardware version which, according to my understanding, is equivalent to the v2 version of the CPE210, etc.
As far as I know, CPE210 v2 was the only exception from the common Pharos platform, but I have no v2 here to test (sent them back in exchange for v1 because of the missing PoE pass-through), so standard Pharos firmware for WBS510 should install on CPE510, WBS210 and even CPE210 v1.x.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#5
Options
Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-06-11 02:08:03
I have tried every combination of CPE510, WBS510 and Beta firmware and I still experience the problem of the AP and CLIENT CPE510 devices rebooting and loosing the point-to-point connection between the two CPE510's that I am using.

This is very frustrating, does anyone have any further suggestions?

It would be helpful if the system log showed more than just the device has booted and assigned its static IP address!!!!! I would like to have detailed about why the device thinks it rebooted, for example, power loss, watchdog fired or some other reason....

If I can salve this I will have no choice but to find another reliable alternative!

In the past, I have had great success using TP-Link WiFi products but this has been very disappointing!!!!
  0  
  0  
#6
Options
Re:Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-08-21 22:19:08 - last edited 2018-08-21 22:43:41

hi tplink_cpe510_

read my post here

https://community.tp-link.com/en/business/forum/topic/109402?replyId=300459

 

I'm sure that has to be your problem simply change the POE cable for a good CAT 7 cable

or use a short CAT 5 or 6 cable and lower the unit power

 

 

then after you lower the power you can change the short cable for a long one and the unit won't restart anymore

or simply just connect the good cat 7 cable from the beginning and you don't have to lower the unit power or use a short cable

 

I have 4 wbs units, two wbs 210 and 2 wbs 510 and all four of them do the same thing

right now I just finished installing the firmware from CPE610 thanks to a post from R1D2 and all my units are working perfectly fine.

 

 

if the cable is not a premium cable

then you have to use a short cable like 10 ft or less on the power adapter POE connector port

if you need to use a long cable in the POE connector

it has to be a good cable something like cat 7

to use a long cat 5 in the power adapter POE conector you have to lower the unit power first 

 

technically speaking get the best cat 7 cable you can find or you can afford

don't use a cheap cable or an old cat cable

 

The funny part is this

If you use the same cable that has the problem connecting the POE from the power adapter to the POE conector in the unit

 

and you use that same cable in the lan port

then you will notice that the cable will connect without any problem

that’s why I’m sure that the problem is cause by the "voltage" or the electrical power in the POE port

between the power adapter and the wbs unit

 

it seems like the cheap cable can't handle too much power

 

to close this up

you can use a cheap cat 5 cable in the power adapter lan port

but you can't use a cheap long cat 5 cable in the POE port

unless you lower the dbi first

 

good luck

  0  
  0  
#7
Options
Re:Re:Re:CPE510 (client) -to- CPE510 (AP) Connection (LInk) Reliability Issue!
2018-08-21 23:48:22

just I case not all cables are all the same

There re different brands, lengths and category

a cat 5 patch or cat 5e might work depending on the cable length and cable quality

but to be sure I rather go with the best

being cat 7 and not just any cheap cat 7

but a good cat 7 to avoid any problem

 

I ran a test and converted a premium cat 7 cable to a cat 5 cable

and guess what

I had the reboot loop

So that made think that the problem is just the category and not really the cable brand or quality

  0  
  0  
#8
Options