I’m planning a portable P2P system for a customer. The point is to make a connection between some customer hardware. The customer hardware will be moved monthly.
They do not need high bandwidth, just stable and low latency.
Some times there will we LOS directly between the customer hardware. That is easy - one SXT AC on each end, connected to customer hardware.
Some times there will be a need for a “repeater” in the middle.
Customer -ethernet- SXT 1–WIFI P2P – SXT2–ethernet—SXT3–WIFI P2P–SXT4–customer. Still easy.
The problem is that all hardware will be (semi) portable and customer will only place out the repeater site if not LOS between SXT1 and SXT4.
To be sure that SXT1 won’t make a bad connection to SXT4 instead of SXT2 when they need the repeater, I cannot set it to have both SXT2 (“repeater”) and SXT4 (customer) in connect list.
Is there a better way? WDS/MESH, could that be used in this setup (still with two radios on the “repeater” site wired together) ?
You can also set the signal levels in connect list to avoid bad connections. If the throughput is not a concern, do not use ac but pure n type only. Even maybe 2.4g could be better to handle obstacles if the distance is not so high.
Aha, hadn’t though about signal level.
So Connect list from SXT 1 to SXT 2 and SXT 4 with signal threshold set to something viable so it will always take the nearest one,
and a connect list from sxt 3 to sxt 4 and that should be enough? might be easier than I anticipated then!
Good tips about ac/n. I guess also 20 or even just 10 MHz channel width would be best.
Exactly. The higher signal density with 10 or 5 MHz channel will help a lot also. But you cannot use these narrow bands on ac devices as their chips simply do not support them… Again a reason against the ac in your case.
I don’t know the exact parameters, the customer should be able to connect two nearby work sites, and when they are done working on one site they move the stuff to new location.
