You are here

best hardware

9 posts / 0 new
Last post
k3la
best hardware

I have a chance to put new node or nodes on a local 200  foot tower to encourage local activity. Currently there is a bullet on 2.4 with an omni antenna. Tower work is being done which would allow new an additional nodes, possible 5 ghz to be installed. Currently no local activity but some interest. What hardware would be a good choice to install? Barney K3LA

AB4YY
I would use a 'MikroTik

I would use a 'MikroTik RouterBOARD LHG 5HPnD-XL'.

  • Antenna: 27 dBi 6.4° Dish
  • Tx power: 28 dBm

73 - Mike

K7EOK
Not enough information, and
Not enough information, and there is no "best hardware".

Where are the other stations who are interested relative to the tower?  What range of distances?  Is the tower out in the open, or is terrain blocked in one direction?

Most tower sites are best served by multiple 120 degree sectors with some downtilt, on different channels.  Folks close in can easily connect, and folks more than 5 miles away can connect fine to a sector with something a bit more powerful.

Answer ... it all depends.  Give more detail and get more out of the question.  BTW all 5ghz going forward, no point getting any 2.4

Ed
 
KN9U
Might not be the best, but it the setup we are using.
We "FLMesh" (https://worldmap.arednmesh.org/#9.82/27.9252/-80.5664) are using a 'Ubiquiti LiteAP 5AC' (N4TDX-PalmBay-Sector) for 'local' users with a 'Ubiquiti LiteBeam AC Gen2' (N4TDX-PalmBay-Melbourne-Link) for the link in to the backbone. We are still building out the Mesh and have a few nodes set up this way.
Both devices use a 'hose clamp' to connect to the tower so that makes it 'easy' and a huge pain if you did not bring the correct tools and are 180ish feet up the tower. Something you want to play with on the ground first.

73
Matthew KN9U
 
nc8q
nc8q's picture
Palm Bay - Melbourne link
Hi, Matthew:
Way to go! :-)
I think you could get better throughput with a wider bandwidth.
Your link is 12 miles and our link is 14 miles.
Your SNR is 27/29.
Our SNR is 24/27.
Your TxMbps is 6.5.
Our TxMbps is 104.
Your/our Iperfspeed tests are
7/23/24 7:28 AM N4TDX-PalmBay-Melbourne-Link  N4TDX-Melbourne-PalmBay-Link   3.04 Mbits/sec
7/23/24 7:29 AM NC8Q-HuberHeights-MVHS ...... NC8Q-MVHS-HuberHeights        29.1  Mbits/sec

Your/our profiles:

73, Chuck
 
Image Attachments: 
KD4WLE
Palm Bay - Melbourne link
Thanks for the comments, Chuck.

We installed the Melbourne side blind, and it sat for awhile before we got the Palm Bay side up. We had a slew of work to do on the Palm Bay tower and the AREDN gear was the last to go up. Wether was taking a turn and everything was rushed into place. We did not get the time to aim the gear, Got a signal and locked it down in a rush.

We are going back out to the site to re-aim the dish. Hopefully we can squeeze 20Mhz outta the link, and get the sector in a better position. It's a clear LOS with no fresnel issues.


Image Attachments: 
nc8q
nc8q's picture
Palm Bay to Melbourne in 3 steps
Hi, Gerard:
Awesome, guys!
Our longest link installation was similar:
1. Install the easier to access site first and aim the antenna in a best guess direction.
2. Install the harder to access site and aim the antenna for best SNR.
3. Revisit the easier to access site and aim the antenna for best SNR.

73, Chuck
p.s. Have you viewed the new UI scheduled for release this fall?
http://kn6plv-test-lhg-5nd.local.mesh:8080/a/status
http://kn6plv-test-sxt-lite5.local.mesh/a/status


 
KN9U
I have spoke with KD4WLE (he
I have spoke with KD4WLE (he is the architect)
So, steeping up to 10Mhz drops the SNR a bit. At 10Mhz it’s 24/25 I’ll let it sit and check back for errors. Re aiming the dishes may improve the SNR.
 
Client: N4TDX-PalmBay-Melbourne-Link
Server: N4TDX-Melbourne-PalmBay-Link

Connecting to host N4TDX-Melbourne-PalmBay-Link, port 5201
[  5] local 10.214.47.179 port 51952 connected to 10.214.55.29 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  1.00 MBytes  8.38 Mbits/sec    0    164 KBytes      
[  5]   1.00-2.00   sec   768 KBytes  6.29 Mbits/sec    0    164 KBytes      
[  5]   2.00-3.00   sec   768 KBytes  6.29 Mbits/sec    0    164 KBytes      
[  5]   3.00-4.00   sec   640 KBytes  5.25 Mbits/sec    0    164 KBytes      
[  5]   4.00-5.00   sec   768 KBytes  6.29 Mbits/sec    0    164 KBytes      
[  5]   5.00-6.00   sec   768 KBytes  6.29 Mbits/sec    0    164 KBytes      
[  5]   6.00-7.00   sec   384 KBytes  3.15 Mbits/sec    0    164 KBytes      
[  5]   7.00-8.00   sec   512 KBytes  4.19 Mbits/sec    0    164 KBytes      
[  5]   8.00-9.00   sec   384 KBytes  3.15 Mbits/sec    0    164 KBytes      
[  5]   9.00-10.00  sec   384 KBytes  3.14 Mbits/sec    0    164 KBytes      
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  6.25 MBytes  5.24 Mbits/sec    0             sender
[  5]   0.00-10.05  sec  6.00 MBytes  5.01 Mbits/sec                  receiver
 
We have been working on the n4tdx-parish-titusville-link backhaul and have it smokin at 144Megs with a SNR around 48/46, it’s much shorter than the Palm Bay link, of course, Both of them are direct LOS with no obstructions.
 
Client: N4TDX-Titusville-Parish-Link
Server: N4TDX-Parish-Titusville-Link
Connecting to host N4TDX-Parish-Titusville-Link, port 5201
[  5] local 10.172.170.174 port 38232 connected to 10.172.168.47 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  11.0 MBytes  92.1 Mbits/sec    0    229 KBytes       
[  5]   1.00-2.00   sec  11.8 MBytes  98.4 Mbits/sec    0    229 KBytes       
[  5]   2.00-3.00   sec  10.2 MBytes  86.0 Mbits/sec    0    229 KBytes       
[  5]   3.00-4.00   sec  10.6 MBytes  89.0 Mbits/sec    0    229 KBytes       
[  5]   4.00-5.00   sec  9.75 MBytes  82.0 Mbits/sec    0    229 KBytes       
[  5]   5.00-6.00   sec  10.2 MBytes  86.0 Mbits/sec    0    229 KBytes       
[  5]   6.00-7.00   sec  10.5 MBytes  88.1 Mbits/sec    0    229 KBytes       
[  5]   7.00-8.00   sec  10.9 MBytes  91.0 Mbits/sec    0    229 KBytes       
[  5]   8.00-9.00   sec  11.6 MBytes  97.8 Mbits/sec    0    229 KBytes       
[  5]   9.00-10.00  sec  11.2 MBytes  94.1 Mbits/sec    0    229 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   108 MBytes  90.8 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   108 MBytes  90.5 Mbits/sec                  receiver

 
nc8q
nc8q's picture
I’ll let it sit and check back for errors.
Hi, Matthew:
Awesome!
IMHO, LQ/NLQ is the best indicator of a link.
Aim for the wider bandwidth that still displays 100% LQ/NLQ.
The OLSR algorithm to choose MCS favors throughput as #1 priority, not error rates.
I feel that error rates are not a best metric.
73, Chuck

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer