My experimental co-locate.
Each wAP 60Gx3 AP works on its own frequency with auto beamfroming.
Clients are connected to the first and third, according to compatibility (regardless of the distance, others prefer 64800, others 60480).
All links work perfectly.
For the average wAP60Gx3, no one is connected, but tends to disconnect by itself (warranty option possible).
Maybe someone has their own co-locate experience?
but tends to disconnect by itself
What do you mean by that ?
So you have 3 WAP APs, what about the Clients ? Models ?
Electricity is supplied but the ping does not go.
There were reports from the customer of a complains, I turned off the electricity (probably the wireless worked, at least the power consumption was the same).
I replaced the cable and PSE (power sourcing equipment), it also doesn’t work all day and shuts down.
I am currently testing without wlan60-1 turned on.
So you have 3 WAP APs, what about the Clients ? Models ?
Cube Lite60, Cube 60G ac, Wireless Wire nRAY.
RouterOS ad BIOS version?
There are FM radio or other high power TX device ont the same site?
Uniform all to long-term 6.47.9 or stable 6.48.2, client included, (order do not matter) and also upgrade BIOS, and reboot after upgrade BIOS.
Other TX device can interfere with armonics or with power, the wAP are plastic…
Licensed TX usually have more power than device with free license…
How is it related to the problematic wAP?
If there is no problem with the radio and everything is working fine, I don't make updates (with the exception of critical risk notifications from MT).
If I do an update, I try long-term.
P.S.
There are probably people who will always want to upgrade or do a charity helping MT test beta versions. It's not about me. My social mission is to share practical experiences between users and send suggestions to MT.
Electricity is supplied but the ping does not go.
You can not ping the device from the APs side or the clients side ?
It’s common best practice to update all the software at same version…
Cambium, Ceragon, SIAE, Ubiquiti, etc.
All suggest this.
But, read all changelog between version and you find than between some version something is changed…
P.S.: I use 6.47.9 on near 200 new devices and 6.46.8 on the other 4000…
Same software on all AP+client. I’ts obvious…
mah…
The first wAP 60G has 6.43.6 for factory and you have update to 6.45.9
The second wAP 60G has 6.44.6 as factory and you have updated first to 6.45.9 then to 6.46.8
The third wAP 60G has 6.44.6 as factory and you have updated first to 6.45.9 then to last 6.48.2 “stable” not long term
You can not ping the device from the APs side or the clients side ?
It’s common best practice to update all the software at same version…
But, read all changelog between version and you find than between some version something is changed…
The third wAP 60G has 6.44.6 as factory and you have updated first to 6.45.9 then to last 6.48.2 “stable” not long term
Thanks for have not misunderstand my poor english for a blame 
You can not ping the device from the APs side or the clients side ?
- PSE Omni side.
I would test the device for a couple of days at home and see how it behaves…
Just update and maybe reset-configure again…