I'm trying to use a TP-Link CPE510 to connect to a node on a hilltop that's about 4 miles away. When I initially powered up the CPE510, it connected to the hilltop node with no problem. The NLQ was variable (as the mesh status periodically updated) but stayed in the range of 60% to 70%. After about 10 minutes, the connection dropped and the NLQ went to 0%. I've rebooted multiple times, power cycled, tried different power settings, etc. Can't get it to work again.
The CPE510 seems to be working OK. If I set up another node at my house the CPE510 sees it and links to it with no problem.
Trying to troubleshoot the problem, I've replaced the CPE510 with a Ubiquiti Nanostation M5 and then a Ubiquiti Powerbeam M5 300. Both of those units exhibited the same behavior (connecting for 5 to 10 minutes and then dropping the connection with NLQ at 0%).
I tried to search the forum but I did not see this behavior (connecting for a short period and then disconnecting) described.
The software version on the CPE510 is 3.22.12.0 (the current version). The Powerbeam M5 was also on the current version. The Nanostation M5 is on a version from about 6 months ago.
Has anyone else seen this behavior and/or suggest the next troubleshooting steps.
Thanks for any suggestions.
John, KM6ZJT
The CPE510 seems to be working OK. If I set up another node at my house the CPE510 sees it and links to it with no problem.
Trying to troubleshoot the problem, I've replaced the CPE510 with a Ubiquiti Nanostation M5 and then a Ubiquiti Powerbeam M5 300. Both of those units exhibited the same behavior (connecting for 5 to 10 minutes and then dropping the connection with NLQ at 0%).
I tried to search the forum but I did not see this behavior (connecting for a short period and then disconnecting) described.
The software version on the CPE510 is 3.22.12.0 (the current version). The Powerbeam M5 was also on the current version. The Nanostation M5 is on a version from about 6 months ago.
Has anyone else seen this behavior and/or suggest the next troubleshooting steps.
Thanks for any suggestions.
John, KM6ZJT
For starters.
I don't know if anyone else has been able to establish a stable link to the hilltop. I'm in an area in the SF East Bay that has very few nodes at the moment. I think I'm one of the first (if not THE first) AREDN user to try establishing a connection to it. But I will pursue that possibility with my Ham club.
I've tried it with the LQM both on and off.
For the distance setting, I've tried to set it to "0" (auto). I've also experimented with various distance settings and power settings from 5 dBm to 24 dBm. (Sorry I didn't say all that in my original post but I thought it was getting too long.)
Again, thanks for the suggestions.
If anyone in my Ham club has an answer, I'll post it here.
73,
John, KM6ZJT
Hi, John:
+1 with Tom that the trouble may not be at your end.
Try this and report:
Navigate to the hill top node.
Click the 'Charts' button.
Using the 'Selected Device:' drop down menu, select your active home node.
Click the 'Archive' button. Watch for 2 days...just kidding. Image updates each minute.
'Realtime' updates each second, but consumes 60x network resources.
I am especially interested in the SNR value and that the SNR is flat or nearly so.
73, Chuck
Hi, Chuck.
After some further troubleshooting with another local Ham, it looks like my connection problem comes down to a simple power problem. I had the power level on my CPE-510 set to 21 dBm. Increasing the power level on my node to maximum enabled me to connect again to the hilltop node. The connection is still somewhat unstable but definitely better than I had been experiencing before. I think that once I replace the CPE510 with my Ubiquiti Powerbeam I should be able to get a reasonably stable connection. (That will require getting out a ladder and a trip to the roof.)
I'm guessing that if I set the power on my Ubiquiti Nanostation to maximum, it too will have a more stable connection. Still have to try that.
The screen capture below is the Neighbor Status page from the hilltop node I was trying to reach (Wiedemann Hill, SW of San Ramon, CA). Still not a great SNR (11 dB) but at least the connection is working.
Here is the current SNR chart (I think this is the chart you asked to see.)
Thanks again to everyone.
73,
John, KM6ZJT
Hi, John:
IMHO 15 dB SNR is minimum for a poor but 'working' link, but this has no fade margin.
20 dB SNR is 'good'.
I consider a great SNR to be 30 dB.
Let us do some arithmetic.
You have 11 SNR and need 20.
The CPE510 has 13 dBi gain and 26 dBm power: 39
You need at least 9 more "dB"s.
Now choose your device.
73, Chuck
Your summary makes sense. I think it captures the central problem in a straightforward way.
I plan to replace the CPE510 with a Ubiquiti Powerbeam M5 300. If I'm reading the data sheet correctly, that will give me 22dbi of gain vs 13 dBi with the CPE510. That may give me the 9 dB that you describe if I can get the Powerbeam aligned properly.
Thanks again for your help and for all your responses you've provided to many other posters in the past.
73,
John, KM6ZJT
Hi, John:
Before Mikrotik was known to me (~2018) I bought a Ubiquiti PowerBeam M5-400.
It was hard to aim/adjust as there is one U-bolt that holds the unit in place both
horizontally and vertically. While adjusting the azimuth, the device might slip in elevation
and visa versa.
I now have a LHG-HP5-XL in service for the same link.
The LHG-HP5-XL is lighter, has more power, has more gain, and is cheaper.
This link is 2.6 miles through the tree tops and getting TxMbps 130.0 to a LHG-HP5-XL on the other end.
I hope this helps,
Chuck
Looking online for a vendor there's a wide range of prices. Using the link on the AREDN list of supported devices takes me to Amazon, there's only one vendor and they want $350. I don't know if it's acceptable on this forum to recommend a vendor and I understand is that can't be done. With non-Amazon vendors I find on line I see prices like $90 with $30 shipping. Let me know if that is in the ballpark or if I should shop further.
Once again, thanks for all your help and suggestions.
John, KM6ZJT
Thanks, again.
I don't know if that's correct but I just wanted to add that in case it might be helpful to others seeing similar symptoms.
John, KM6ZJt