wAP 60G experience

Multipath? What does the environment look like?

With the latest releases you can try to fix the “tx-sector” parameter.

djvolt1942 shields for what?
Bergante Multipath? - don’t get it!, What does the environment look like? ?!like moisture, LOS… ??

60ghz-6.41rc52vs6.42.1.jpg
not sure, should I tweak something after upgrade ?

How far is the link? Please provide CLI output from both ends:
/interface w60g monitor wlan60-1

/interface w60g monitor wlan60-1
connected: yes
frequency: 60480
remote-address: 30:07:4D:
mcs: 8
signal: 50
tx-sector: 63
rx-sector: 96

interface w60g monitor wlan60-1
connected: yes
frequency: 60480
remote-address: 30:07:4D:
mcs: 8
signal: 50
tx-sector: 24
rx-sector: 96

Link length is around 130m.
but I downgraded them to rc52 to have more stable link now.

Try to switch used frequency to 58320 and upgrade to 6.42.1

We use 58GHz for far link like 600, 800 meters :stuck_out_tongue:

Lakis - shields for far links up to 300meters or better stability in snowy/rainy day, also for reduce SNR from wap to wap or MultiPoint…

It’s a long shot, but depending on how you have installed the units you might be getting multiple reflections? One of my
units is installed on a window (outside of course) and it’s in a corner with three walls around. That’s a scenario
that can be troublesome in some cases.

In theory that might sometimes confuse the beam selection algorithm, and, if that was the case (sorry, it’s really
hypothetical but I haven’t seen your installation) selecting a fixed beam configuration might help.

Anyway the experiment is easy. If it’s just a point to point link look at the tx-sector values when the
link is performing best and configure them statically. if that solves the problem then you had something
disturbing the beam selection algorithm.

why should I change freq? It seems to work quite good with rc52. there is no noise or other 60ghz link visible under scan. besides if it works worse with newer routerOS
I doubt Your advice is to solve problem looks rather as a workaround.
Sad.

Are the tx-sector and rx-sector numbers changing often? If they are, fixing tx-sector could be beneficial.

My link (very short, around 30 metres crossing a street) actually worsened a lot when Mikrotik improved the antenna patterns. But the only reason was signal overload. Reducing power solved it.

Monitor tx-sector regularly and let’s see.

Different frequencies has different attenuation over air. Channel 2 isn’t picked up automatically on free spectrum if “frequency=auto”

I had the same problem with a ~30m link. New firmware was just too hot. Lowering tx-power to 10 on both sides helped tremendously

signal-weekly.png

And 6.43rc17 has vastly improved one of our longer links (~170m)
Waiting for a final release to upgrade to the rest.
signal-weekly.png

And 6.43rc17 has vastly improved one of our longer links (~170m)
Waiting for a final release to upgrade to the rest.

what FW was before upgrade to 43rc17 ?

@MonkeyDan
What software are you using for the grath visualization?

after upgrade from
6.42rc52 to 43rc17
i’ve got ERROR WRONG PASSWORD after trying to login into ( using winbox 3.11)
?!?!
is it some kind of very late aprilfool joke?
PLEASE mikrotik support help me solve my problem

Look http://forum.mikrotik.com/t/problem-with-mount-point/94/1 at the end of post say need to use new Winbox 3.14 in rc17.

new version will have distance measurement tool, it would be cool if we could get some feedback to support@mikrotik.com

@npero thanks, with this beta winbox and webbox password works ok.

@antonsb where Can I find dist. measurment tool ?

On the AP/master: /interface w60g station monitor 0

[admin@w60-master] /interface w60g station> monitor 0
       connected: yes
          remote: 30:07:4D::
             mcs: 8
        phy-rate: 2.3Gbps
          signal: 80
            rssi: -54
       tx-sector: 21
  tx-sector-info: left 11.4 degrees, down 11.4 degrees
       rx-sector: 96
        distance: 18.34m

And on the slave,

[admin@w60-slave] /interface w60g> monitor 0
       connected: yes
       frequency: 58320
  remote-address: 30:07:4D::
             mcs: 8
        phy-rate: 2.3Gbps
          signal: 80
            rssi: -53
       tx-sector: 20
  tx-sector-info: left 3.8 degrees, down 11.4 degrees
       rx-sector: 96
        distance: 18.33m
-- [Q quit|D dump|C-z pause]

Before someone gets nervous with the signal levels at a distance of 20 metres: I lowered tx-power to 10 for both units.