Cube 60Pro ac Max Distance on 60Ghz?

Hi.

Can’t find anyone stating what the max distance is on the 60Ghz frequency.

Mikrotik says 2.4km but is it running on 5Ghz or 60Ghz?

/Patricio

For my experience 600 max 700m is the real limit under normal rain (<20mm/hour)

Old link based on LHG 60 Ghz up to 1500m but with rain more than 30mm/hour rain the link goes down.

If you need stable link under heavy rain (>50mm/hour) up to 1500m max 2000m Ubqiuti Wave LR is the only solution using higher channels >66GHz

Thanks for answering!

I was thinking about max distance during perfect clear line of sight conditions, is it 2.4km as they promote them?

I accept decrease in performance due to weather (failing over to 5Ghz).

Is it still max 6-700m in 60Ghz?

/Patricio

Try to use 66960 As far as I Know, cube pro supports it. It can be used at far large distant

The farthest I have gone with MikroTik 60GHz radios is 800m (LHG to Cube). A pair of Cube Pros might work on 66960 around the 1km mark, but I haven’t tried that. I’d consider something larger with higher frequencies if you need more than 1km. nRay would be a good bet between 1-2km.

I have deployed a number of Ubiquiti Gigabeam (Plus & LR) and AF60 links between 1-2km. Beyond 2km, I’ve been deploying AF60-LR radios, and have the longest link record for those radios at 27km (it worked for a little while).

With Ubiquiti’s new Wave LR radios gaining PTP support (3.2.0b), you get both long range 60GHz and 5GHz failover, and they’re cheaper than AF60-LR with better gain.

Are you sure Wave -client supports a “Bridge-mode”?
66960 is a huge step to a long-distant link.
I think that a pair of a cube pro devices is able to connect at least at 2km. It would be really profitable to have 1Ghz channel-width, it may also extend the range.
6.48.2 lets setting nRay 66960, also LHG probably support it, Cube 60G AC also lets set this frequency, but is unstable
The_nRay.PNG

Yes, Wave Nano, LR, and AF60-LR can operate in PTP mode with 3.2.0b2. I have a pair of Wave LR’s going 6.23km doing 1Gbps one way or 650/650 bidirectional (radio-to-radio tests).

I have a pair of Gigabeam LR’s doing 2km on 64800, so LHG 60 probably could. As mentioned, I’ve not tried Cubes that far.

My longest link with cube60pro ac is 1287.21 m
distancecube60pro.PNG

The problem with the Cube’s (and every 60ghz product on the market to date) is the 5ghz radio is so low powered and gimped that its entirely self defeating. The 60ghz vastly exceeds the 5ghz output power over distance. So where the 5ghz kinda sorta works ok enough (200m) its stupid because the 60ghz will not ever go down in any weather condition at that distance, unless there’s something physically in the way
But at say 1km where you really want the 5ghz, its so utterly pathetic (expect around -72dbm single chain, so about 25mbit/s if that) it just doesn’t do anything useful. The 60ghz will work in rain but it will get interrupted and periodically drop. It’s moreso as the conditions change quite quickly. If it’s a constant stream of rain it’ll usually bring itself back up and stabilize over a few seconds/minutes
Any further and the 5ghz just doesn’t work at all

The only purpose for the 5ghz is
A) Marketing wank to sell more units
B) Management traffic backup

B can be ever so slightly useful if the 60ghz link goes down and you need to mac-telnet in etc. But don’t for a second believe its actually useful for actual traffic failure, its total rubbish and not even remotely close to a substitute for a dedicated 5ghz radio for failover
Personally i’d much rather they scrap the 5ghz and just put a 2nd ethernet port with PoE passthrough. That way you can power a nanobeam/powerbeam/force300/whatever AND have the Cube radio do its own private OSPF/BFD failover and treated as a single un-interrupted ethernet port by the routers or switches on each end, far far far more practical and beneficial

Hi All,

I have the following use case with outdoor devices only :

  • site is in Palma de Majorque with 3 buildings and one gate, max distance is ~500m
  • i want to have in the middle an internet access with LTE/5G router and provide internet to the other building
  • on each building local Access Points using 2.4G/5G provides user access

I was thinking to take one or two CubeSA 60 Pro ac to cover remote buildings and on each remote building a Cube 60Pro ac, is it something working ?
Multiple CubeSA 60 Pro to have a complete 360° coverage for remote building or it’s better to have a PtP for each remote building to cover instead PtMP ?

One more thing, on a such distance 60Ghz is needed but what is the goal for 5GHz ?

Thanks in d’avance for your advice.
Regards

Nicolas

Hi,
any another experience with 60 Ghz for long distances?

Thank you

That’s kind of a generic question for a year-old post. What exactly are you needing?

MikroTik’s 60GHz distance limitations have been discussed in several threads. For close-range (<500m for PTMP, <800m for PTP, Cubes don’t go as far as LHG60, beyond 600m expect rain fade), MikroTik’s radios work well and are great low-cost solutions. If you need distance and/or density, Ubiquiti Wave and Tachyon Networks go further, handle more clients per AP, and have better back up options. (Essentially MikroTik short range/low density, Tachyon less-short range/high density, Ubiquiti Wave long range/med-high density).

As for 60GHz itself: I have some Wave LR and Wave Pro links ranging from 9km (7mi) to 22km (14mi). They do fade in rain, and their 5GHz backup is weak beyond 10km, but they work for my purposes.

Hi. What frequantcy is that? 66960?

The maximum throughput of Cube 60G ac devices (500 meters) is significantly higher at frequencies 58320, 60480 and 62640 MHz - both with unidirectional and bidirectional reception - than at frequencies 64800 and 66000 MHz, and is directly proportional to the obtained maximum channel speeds. Thus, with a maximum channel speed of 2.3 Gbit/s at a frequency of 60480 MHz, the maximum throughput was 1773 Mbit/s with one-way reception. In turn, obtaining maximum channel speeds precisely at the frequencies 58320, 60480 and 62640 MHz is most likely due to the design features of the antenna or, less likely, with software limitations on the transmitter power at frequencies 64800 and 66000 MHz.

The maximum burst performance is approximately the same for frequencies 58320, 60480, 62640, 64800 and 66000 MHz. This is due to the fact that the CPU resources of the Cube 60G ac themselves were used to generate traffic. The same can be said about the average throughput of TCP traffic.

In general, the fact that we used the processor resources of the devices under study to generate traffic allows us to say that the absolute values of the obtained values of throughput and packet performance are the minimum possible. Of course, with the proper level of adjustment between devices.

Are you shure about that? nRay works muuuuuuch better at 66960. Cube should be the same

Since Cube 60G ac and Cube 60Pro ac are different devices.
Cube 60Pro ac = 802.11ay
Cube 60G ac = 802.11ad
Perhaps 66960 is a more efficient frequency

66960 is not more efficient it has less atmosphere signal loss. Oxigen makes signal hard to pass bellow 66960

I have them bridging a road on an industrial estate - approx. 25 meters apart. Sometimes an unusually tall lorry might get in the way. The 5GHz backup is pretty useful IMO, better than nothing. I think I saw about 400mbps throughput when I last tested it. That’s good enough for what we’re doing for now anyway.

When it is not raining this works stable using pairs of Cube 60Pro ac

             frequency: 66960
                tx-mcs: 5
           tx-phy-rate: 1251.0Mbps
                signal: 40
                  rssi: -59
             tx-sector: 34
        tx-sector-info: left 2.2 degrees, up 0.8 degrees
              distance: 2331.45m
  tx-packet-error-rate: 0%

as well as this

             frequency: 66960
                tx-mcs: 5
           tx-phy-rate: 1251.0Mbps
                signal: 40
                  rssi: -67
             tx-sector: 35
        tx-sector-info: left 0.8 degrees, up 0.8 degrees
              distance: 2324.99m
  tx-packet-error-rate: 2%

Another even longer link

             frequency: 66960
                tx-mcs: 5
           tx-phy-rate: 1251.0Mbps
                signal: 40
                  rssi: -70
             tx-sector: 35
        tx-sector-info: left 0.8 degrees, up 0.8 degrees
              distance: 2603.67m
  tx-packet-error-rate: 0%