How are we going there? Pretty good by the way! Heavy porn!

We are having installed link for 1200m, pretty good and clear link, I hadn't believed it, but this piece of metal really kicks ass!!

Ok this is CLI of 6.43, so you need not to ask, WTH is that..

connected: yes
frequency: 58320
remote-address: 30:07:4D:XX:XX:XX
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -59
tx-sector: 15
tx-sector-info: right 1.4 degrees, down 1 degrees
rx-sector: 96


How about you?

How were you able to obtain it? AFAIK it is not in sale anywhere in europe yet...
Your comment is highly expected

Nice comments, thanks! I'm glad to see it works as expected.

Ok this is CLI of 6.43, so you need not to ask, WTH is that..

6.43???

Simply we posses those without any comments,

Ok this is CLI of 6.43, so you need not to ask, WTH is that..

6.43???

Ooops?

I am very jealous.

Our distributors have no idea when they are getting. Damn

That's awesome! Love the PHY rate and alignment info. How does it handle the rain?

Hope to have soon a feedback in a rainy day

Hope to have soon a feedback in a rainy day

Rain rain rain.. We need more real live testing. But.. Todays situation about 40-45mm/h link was down for 4 minutes going from -56 to -70 in few seconds. The wet antenna takes -4dB!! Link length 1300m.
The link nearby with WAP for 400m was doing well all the time loosing approxiamtely 1-2 on RSSI scale looding from -66 to -68, and already working as before the rain. LHG is 15 minutes after rain still -59 and once dry has to come up to -56.

Thank you for the feedback

Where did you buy them?

Where did you buy them?

Sorry, no comment

400m link, ROS 6.42.4:

1st side:
[admin@MikroTik] > /interface w60g monitor 0
connected: yes
frequency: 58320
remote-address: XX:XX:XX:XX:XX:XX
mcs: 8
phy-rate: 2.3Gbps
signal: 95
rssi: -53
tx-sector: 45
tx-sector-info: right 0.6 degrees, up 0.6 degrees
rx-sector: 96

2nd side:
[admin@MikroTik] > /interface w60g monitor 0
connected: yes
frequency: 58320
remote-address: XX:XX:XX:XX:XX:XX
mcs: 8
phy-rate: 2.3Gbps
signal: 70
rssi: -64
tx-sector: 58
tx-sector-info: left 0.6 degrees, up 1.4 degrees
rx-sector: 96

MCS and also signal is VERY unstable when link is under load, signal is jumping between 20 to 100 approx. each second, same as MCS - between 1 up to 8
Also, after a load, MCS will remain at low values 1-2 same as signal - from 80 before load to only 20 after a load

@mlenhart

try 6.43 RC there are a lot of improvements

Here our results on first long link

Hello ,

our first long link. Great !!! firmware 6.42.5

Hello ,

our first long link. Great !!! firmware 6.42.5

Try to set channel to 64800 in CLI, the attenuation in O2 is smaller in higher frequency

Wow, this looks promising for my future 2100 meters link


Sent from my iPhone using Tapatalk

Mistry7 remember report us from rainy days

Here our results on first long link

Hello ,

our first long link. Great !!! firmware 6.42.5

Try to set channel to 64800 in CLI, the attenuation in O2 is smaller in higher frequency

Hi ,
How I can do that ? manually ?



thanks

brasileottanta

Hello ,

our first long link. Great !!! firmware 6.42.5

Try to set channel to 64800 in CLI, the attenuation in O2 is smaller in higher frequency

Hi ,
How I can do that ? manually ?



thanks

brasileottanta

@brasileottanta
open terminal in winbox
go to

interface w60g
set 0 frequency=64800

Mistry7 remember report us from rainy days

Here our results on first long link

the next 20 days no rain

Now during heavy downpour our 1491m link gained from 2 to 5 db both side, frequency 64800, WOW

I have to correct partially myself it's no rained on the link but very very close, the strange think that this morning we gained a lot of db before rain start, and now with light rain the signal is from slightly better than normal to 4 db worst

Now light rain stopped signal gained around 2/3db

frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -57
tx-sector: 48
tx-sector-info: left 1.4 degrees, up 1 degrees
rx-sector: 96
distance: 1491.42m

frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -57
tx-sector: 48
tx-sector-info: left 1 degrees, up 1.4 degrees
rx-sector: 96
distance: 1491.42m

I hope Mikrotik update there Site Survey Tool,
the wireless wire dish is choosable, but there is no 60Ghz Band to choose.
Hopefully we are able to calculate rssi , that i think is best way to know what finally alignment
gives us.

We don´t know LHG gain, we don´t know Output Power, we know nothing....
How to probably do alignment if we don´t know the goal rssi?

I hope Mikrotik update there Site Survey Tool,
the wireless wire dish is choosable, but there is no 60Ghz Band to choose.
Hopefully we are able to calculate rssi , that i think is best way to know what finally alignment
gives us.

We don´t know LHG gain, we don´t know Output Power, we know nothing....
How to probably do alignment if we don´t know the goal rssi?

You don't need to calculate anything. The distance limit is specifically indicated. If you have clear line of sight, link will work. 60GHz is completely different from 2GHz, so the traditional calculators will not be useful.

You don't need to calculate anything. The distance limit is specifically indicated. If you have clear line of sight, link will work. 60GHz is completely different from 2GHz, so the traditional calculators will not be useful.

Over a few hundred meters, 60Ghz links are heavily dependent of rain condition. So yes, a link calculator based on ITU rain zone calculator is really needed. It's not perfect but it will still give an indication if you can expect the link to stay-up nearly always or if it will drop as soon as there is some rain.



You rate them for 1.5Km but under which condition? Perfect clear weather with little humidity in the air? Will it works with a reduced speed when raining or will it stop working all together because there is simply no margin at this distance? With other devices, I saw drop of 15-20dB on links over 1Km during storm. Those links stayed up but because there was a lot of margin. There is just no way to know if it will be the same for LHG60 without testing because we don't have any information about the expected signal level at a given distance under clear weather. If you say that a 1.5Km link should work with a rssi of -50 under clear weather, that's not at all the same as if you say it should have a rssi of -65. In the first case, you know that it should continue working even with some rain. In the second case, the link is probably going to drop.

A link calculator is also usefull to know if a new link is working more or less as expected or if there is really a problem with the installation.

You don't need to calculate anything. The distance limit is specifically indicated. If you have clear line of sight, link will work. 60GHz is completely different from 2GHz, so the traditional calculators will not be useful.

Over a few hundred meters, 60Ghz links are heavily dependent of rain condition. So yes, a link calculator based on ITU rain zone calculator is really needed. It's not perfect but it will still give an indication if you can expect the link to stay-up nearly always or if it will drop as soon as there is some rain.



You rate them for 1.5Km but under which condition? Perfect clear weather with little humidity in the air? Will it works with a reduced speed when raining or will it stop working all together because there is simply no margin at this distance? With other devices, I saw drop of 15-20dB on links over 1Km during storm. Those links stayed up but because there was a lot of margin. There is just no way to know if it will be the same for LHG60 without testing because we don't have any information about the expected signal level at a given distance under clear weather. If you say that a 1.5Km link should work with a rssi of -50 under clear weather, that's not at all the same as if you say it should have a rssi of -65. In the first case, you know that it should continue working even with some rain. In the second case, the link is probably going to drop.

A link calculator is also usefull to know if a new link is working more or less as expected or if there is really a problem with the installation.

With this kind of gear and this pricing it is best to do some labour and test it for yourself. Do a testlink and see how it behaves and how the signals fluctuate with rain/snow.

With this kind of gear and this pricing it is best to do some labour and test it for yourself. Do a testlink and see how it behaves and how the signals fluctuate with rain/snow.

Sorry but that's not a good enough excuse not to provide any information. Depending where you are located, it's not that easy to set-up a test link. I agree those devices are very cheap but I would rather avoid wasting time if I could know in advance that there is no hope to get a stable link in a given situation.

I have links I know will work with Metrolinq devices but, if some of the values posted here with LHG60 are the best that can be done, there is nearly no hope to achieve the same results with the LHG60. Based on those data only, I am rather doubtful about spending the time (and money) to do a test that will probably fail. I may rather go directly with a solution that I know will work. If Mikrotik was publishing some data, we would at least have an idea if there is a point in making a test or if it's hopeless.

Based on Ignitenet information, the Metrolinq need a RSSI of -60 for 2Gbps and -65 for 1Gbps. Still based on their data, you can expect (with ML-60-35) a RSSI of -50 at 1.5Km without rain. It's easy to see that you have some margin left. Now, if -65 is really what you can expect of a LHG60 at 1.5Km when not raining, that mean there is nearly no margin at all. If that's the case, it's just not worth to even make a test for that distance

Even if you do a test, without any data there is no way to know if the results you are getting are what is expected or if there is a problem with the setup. There is a reason why people are making threads asking people to post results of their installations.

On a side note, Ignitenet claims 2.2Km for 2Gbps and 2.6Km for 1Gbps when no rain.

PS: Those values are for channel 4. For channel 1, the expected RSSI of ML-60-35 is -63. The maximum distance for 2Gbps drop at 1350m without rain and the distance for 1Gbps to 1620m. That's quite a difference between the 2 channels.

With this kind of gear and this pricing it is best to do some labour and test it for yourself. Do a testlink and see how it behaves and how the signals fluctuate with rain/snow.

Sorry but that's not a good enough excuse not to provide any information. Depending where you are located, it's not that easy to set-up a test link. I agree those devices are very cheap but I would rather avoid wasting time if I could know in advance that there is no hope to get a stable link in a given situation.

I have links I know will work with Metrolinq devices but, if some of the values posted here with LHG60 are the best that can be done, there is nearly no hope to achieve the same results with the LHG60. Based on those data only, I am rather doubtful about spending the time (and money) to do a test that will probably fail. I may rather go directly with a solution that I know will work. If Mikrotik was publishing some data, we would at least have an idea if there is a point in making a test or if it's hopeless.

Based on Ignitenet information, the Metrolinq need a RSSI of -60 for 2Gbps and -65 for 1Gbps. Still based on their data, you can expect (with ML-60-35) a RSSI of -50 at 1.5Km without rain. It's easy to see that you have some margin left. Now, if -65 is really what you can expect of a LHG60 at 1.5Km when not raining, that mean there is nearly no margin at all. If that's the case, it's just not worth to even make a test for that distance

Even if you do a test, without any data there is no way to know if the results you are getting are what is expected or if there is a problem with the setup. There is a reason why people are making threads asking people to post results of their installations.

On a side note, Ignitenet claims 2.2Km for 2Gbps and 2.6Km for 1Gbps when no rain.

PS: Those values are for channel 4. For channel 1, the expected RSSI of ML-60-35 is -63. The maximum distance for 2Gbps drop at 1350m without rain and the distance for 1Gbps to 1620m. That's quite a difference between the 2 channels.

I have some Ignite links. I never get calculates values. Often they fluctuate or are far off. Their scope is crap (enough for a first shot but far from beeing exact) and a lot of their gear need to be replaced. So dont expect from wifi-based cheap gear to match the calculations (as you get with expensive licensed gear). Even the production tolerance might kill your calculations (Just see an open ignitenet and you know why. Clipped in USB-Stick ... ).

This Ignitenet claims are ... puh. Just do it ... This is why I say what you test is what you get.

I have some Ignite links. I never get calculates values. Often they fluctuate or are far off. Their scope is crap (enough for a first shot but far from beeing exact) and a lot of their gear need to be replaced. So dont expect from wifi-based cheap gear to match the calculations (as you get with expensive licensed gear). Even the production tolerance might kill your calculations (Just see an open ignitenet and you know why. Clipped in USB-Stick ... ).

This Ignitenet claims are ... puh. Just do it ... This is why I say what you test is what you get.

Nobody ever claimed that the scope is good enough for alignement. It's only useful to point the antenna at each others so they will at least establish a link that will let you do alignement. You can do without but, imho, at 1km+ it makes things easier.

I am not expecting to get the exact theoretical values but a rough idea is a lot better than nothing. I have several Metrolinq lines and the values aren't that far off. Perhaps they are cheap gear, as you say, but I haven't got a single one that failed yet and the links, all between 1Km and 1.3Km never droped even during storm. But I did saw them go from 2.5Mbps to 1Mbps for a few minutes in the worse cases. As it is, I am perfectly happy with those devices which is why I am doubtful into investing money and time into something that seems to have nearly no chance of working (based on the few results that people posted as there is nothing official from Mikrotik).

How hard is it to list the signal needed for a few speed rates and what RSSI you "may" expect based on the distance? Answering "they are rated for 1.5Km so they will work at this distance" is just plain false: we all know that it heavily depend of weather condition, whatever the gear you are using.

Just installed a LHG 60G link:

Distance: 1160m
Alignment based on RSSI and not on led or TX sector info: I could systematically gain 4-5 dbm over a "center" TX sector value. As some people pointed out, we really need to be able to disable beam forming for alignement: Sure, beam forming can compensate for some poor alignment but a correctly aligned link with beam forming beats a poorly aligned link with beam forming.

Side A:
frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 85
rssi: -55
tx-sector: 55
tx-sector-info: right 1.4 degrees, up 1 degrees
rx-sector: 96
distance: 1166.34m

Side B:
frequency: 64800
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -58
tx-sector: 56
tx-sector-info: left 1.4 degrees, up 1.4 degrees
rx-sector: 96
distance: 1166.36m

I am now waiting on the predicted storm this week-end to see how the link behave.

Comment:
- It was a lot easier to get a working link "by sight" than with Metrolinq 60-35. (Metrolinq have a much narrower beam)

- Fine alignement still need to be done based on signal, like with the Metrolinq.

- The LHG60 "mast bracket" is pretty crappy for 60Ghz. Even with the beam width of the LHG60, half a degree can make a difference of several dbm. We really need a bracket that let do fine adjustment once it's firmly fixed to the mast.

- The RSSI (and the tx-sector info) can vary quite a lot from one moment to another even with good weather and even with the link running since several hours, without touching the antenna. (The above data shows "left 1.4 degrees, up 1.4 degrees" but sometime it shows "center". The RSSI can vary from -57 to -61 on that link. -61 is when tx-sector shows "center")

- For a slightly longer link (1290m), at the same location, using the same frequency (64800), Metrolinq 60-35 reports a RSSI of -45 with nearly no variation (+/- 1dBm)

I will check how the link compare to the Metrolinq one during the upcoming thunderstorm.

PS: Can't people resize their pictures, before posting them, so they don't mess the whole page?

Just installed a LHG 60G link:

[...]
Comment:
- It was a lot easier to get a working link "by sight" than with Metrolinq 60-35. (Metrolinq have a much narrower beam)

- Fine alignement still need to be done based on signal, like with the Metrolinq.

- The LHG60 "mast bracket" is pretty crappy for 60Ghz. Even with the beam width of the LHG60, half a degree can make a difference of several dbm. We really need a bracket that let do fine adjustment once it's firmly fixed to the mast.

- The RSSI (and the tx-sector info) can vary quite a lot from one moment to another even with good weather and even with the link running since several hours, without touching the antenna. (The above data shows "left 1.4 degrees, up 1.4 degrees" but sometime it shows "center". The RSSI can vary from -57 to -61 on that link. -61 is when tx-sector shows "center")

- For a slightly longer link (1290m), at the same location, using the same frequency (64800), Metrolinq 60-35 reports a RSSI of -45 with nearly no variation (+/- 1dBm)

I will check how the link compare to the Metrolinq one during the upcoming thunderstorm.

PS: Can't people resize their pictures, before posting them, so they don't mess the whole page?

The dish sizes of Metrolinq 35 and LHG60 are quite the same. LHG is a bit wider. So I guess the RSSI difference is due to different TX power or different measurement of the chipset. The mesh antenna might be a factor but not that big. Would be interesting to compare how both modulate down with distance/weather.

The dish sizes of Metrolinq 35 and LHG60 are quite the same. LHG is a bit wider. So I guess the RSSI difference is due to different TX power or different measurement of the chipset. The mesh antenna might be a factor but not that big. Would be interesting to compare how both modulate down with distance/weather.

The size is about the same but the geometry is different. As I said, the Metrolinq have a much more focused beam. Getting 2 Metrolinq to link at 1km just by more or less pointing them at each others by sight is nearly impossible. I really doubt that both antenna have the same gain.

I will post the results after this weekend's storm. Both LHG60 and Metrolinq links are in the same area, with about the same length and on the same channel so it will be easy to compare them (in fact, both links are back to back).

Edit: I think the Metrolinq 60-35 have an antenna gain of 42 dBi and a max TX power of 14 dBm
Edit: I think that, in Europa, the max EIRP for 60Ghz is +55 dBmi with a minimum antenna gain of +30 dBi. In USA, it's a lot higher (+82 dBmi)

Here is my results from a 700m connection in good weather. It seems the rssi improved and the link was more balanced after putting load on the link. I also expected more throughput at that distance.

Here is my results from a 700m connection in good weather. It seems the rssi improved and the link was more balanced after putting load on the link. I also expected more throughput at that distance.

LinkTest700m.png

Currently You are testing one core performance - Use Traffic generator or generate traffic externally.

Thanks Anton, I was looking at the Hawaii link and realized that. Thanks, this is much better

Here is a second link we have put up at 1km

First thunderstorm of the weekend. Here is the results:

LHG60 link:
Length: 1166m
Frequency: 64800
RSSI no rain: -55 to -58 dBm
Rate no rain: 2.3Gbps

Metrolinq 2.5 60-35 link:
Length: 1290m
Frequency: 64800
RSSI no rain: -45 dBm
Rate no rain: 2.5Gbps

Both links are in the same area so have the same weather conditions (they both end-up at the same location).

Results:
LHG60:
RSSI during "normal" rain: around -63 dBm
Rate during "normal" rain: 2.3Gbps. Sometime drop to 1.9Gbps
RSSI during "heavy" rain: Minimal recorded -71 dBm
Rate during "heavy" rain: Often around 1Gbps. Sometime as low as 390Mbps

Metrolinq:
RSSI during "normal" rain: -47 dBm
Rate during "normal" rain: 2.5Gbps
RSSI during "heavy" rain: Minimal recorded -57 dBm
Rate during "heavy" rain: 2.5Gbps

The good thing is that during this storm neither links disconnected (which is better than I expected). But the LHG60 rate dropped a lot for most of the storm while the Metrolinq rate stayed at a full 2.5Gbps during the whole time.

In nearly 1 year, I saw the Metrolinq RSSI drop down to as low as -65 dBm which resulted in some very brief rate drop (to 1.9Gbps or even 1Gbps for a few seconds). That's about 8 dBm less than during this storm. It's very probable that the LHG60 link would disconnect under the same condition as the RSSI would be around -79 dBm...

Imho, I wouldn't use LHG60 for links above 1Km except if you are in an area with very little rain or if you don't care about losing the connection from time to time...

Something weird I noticed: It stopped raining since around 30 mins and suddenly the LHG60 link dropped to MCS 1 even with a good RSSI (-55 dBm):
frequency: 64800
mcs: 1
phy-rate: 385.0Mbps
signal: 20
rssi: -55
tx-sector: 41
tx-sector-info: left 1 degrees, up 0.6 degrees
rx-sector: 96
distance: 1166.37m

The link stayed like that until I passed some heavy traffic through it and then it when back to more normal values:
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -55
tx-sector: 47
tx-sector-info: right 1.4 degrees, up 0.6 degrees
rx-sector: 96
distance: 1166.36m

No idea what is causing that...

First thunderstorm of the weekend. Here is the results:

LHG60 link:
Length: 1166m
Frequency: 64800
RSSI no rain: -55 to -58 dBm
Rate no rain: 2.3Gbps

Metrolinq 2.5 60-35 link:
Length: 1290m
Frequency: 64800
RSSI no rain: -45 dBm
Rate no rain: 2.5Gbps

Both links are in the same area so have the same weather conditions (they both end-up at the same location).

Results:
LHG60:
RSSI during "normal" rain: around -63 dBm
Rate during "normal" rain: 2.3Gbps. Sometime drop to 1.9Gbps
RSSI during "heavy" rain: Minimal recorded -71 dBm
Rate during "heavy" rain: Often around 1Gbps. Sometime as low as 390Mbps

Metrolinq:
RSSI during "normal" rain: -47 dBm
Rate during "normal" rain: 2.5Gbps
RSSI during "heavy" rain: Minimal recorded -57 dBm
Rate during "heavy" rain: 2.5Gbps

The good thing is that during this storm neither links disconnected (which is better than I expected). But the LHG60 rate dropped a lot for most of the storm while the Metrolinq rate stayed at a full 2.5Gbps during the whole time.

In nearly 1 year, I saw the Metrolinq RSSI drop down to as low as -65 dBm which resulted in some very brief rate drop (to 1.9Gbps or even 1Gbps for a few seconds). That's about 8 dBm less than during this storm. It's very probable that the LHG60 link would disconnect under the same condition as the RSSI would be around -79 dBm...

Imho, I wouldn't use LHG60 for links above 1Km except if you are in an area with very little rain or if you don't care about losing the connection from time to time...

What is your tx-power setting for lhg60? I guess this makes the signal difference.

What is your tx-power setting for lhg60? I guess this makes the signal difference.

How should I know? Mikrotik didn't gave any information about those devices. In Europa, the max EIRP authorized is 55 dBmi with an antenna gain that need to be at least +30 dBi. Metrolinq has a TX power of 14 dBm. Any reason to believe that the LHG60 are set to less than that 14 dBm by default and that the default isn't the maximum they can do?

Nobody reported a better RSSI for LHG60 links at 1Km+ yet...

I am not sure why you say the only difference can only be the TX power when those antenna don't have at all the same geometry. Imho, the Metrolinq have a much higher gain, that's all.

Also, I am not sure the grid design is a good idea: As others reported, even when it stops raining, the RSSI stay much lower until the antenna dry. I don't have at all this problem with the Metrolinq radom.

Edit: I tried to set the tx-power manually instead of "default". The maximal value accepted is 15. I didn't noticed any change in RSSI so I guess the default must already be 15 or, perhaps, 14 (Which is the same as Metrolinq).

What is your tx-power setting for lhg60? I guess this makes the signal difference.

How should I know? Mikrotik didn't gave any information about those devices. In Europa, the max EIRP authorized is 55 dBmi with an antenna gain that need to be at least +30 dBi. Metrolinq has a TX power of 14 dBm. Any reason to believe that the LHG60 are set to less than that 14 dBm by default and that the default isn't the maximum they can do?

Nobody reported a better RSSI for LHG60 links at 1Km+ yet...

I am not sure why you say the only difference can only be the TX power when those antenna don't have at all the same geometry. Imho, the Metrolinq have a much higher gain, that's all.

Also, I am not sure the grid design is a good idea: As others reported, even when it stops raining, the RSSI stay much lower until the antenna dry. I don't have at all this problem with the Metrolinq radom.

Edit: I tried to set the tx-power manually instead of "default". The maximal value accepted is 15. I didn't noticed any change in RSSI so I guess the default must already be 15 or, perhaps, 14 (Which is the same as Metrolinq).

I cant believe the LHG Antenna is so much lower gain. I would expect no more than 3db difference which would be huge. But I dont have any data.
@MT could you please step in with some facts/data on Antenna Gain / TX Power.

I cant believe the LHG Antenna is so much lower gain. I would expect no more than 3db difference which would be huge. But I dont have any data.
@MT could you please step in with some facts/data on Antenna Gain / TX Power.

Considering how easy it is to set-up a LHG link "by sight", I am not really surprised. Also, the antenna shape/size can result is a much bigger gain difference in the 60Ghz than it would in the 5 or 2.4Ghz.

We really don't have any info about the max EIRP of the LHG so it's hard to say. Based on their spec, Metrolinq 60-35 max EIRP is 55-56 dBmi. Based on their link calculator, with those antenna, you should get a RSSI of -42 dBm at 1Km and -50dBm at 1.5km +/- 10% error margin (for channel 4 and no rain). From my experience, this is doable in practice. Nobody reported anything near those values with the LHG (yet).

New Link only aligned by sight. Needs fine adjustment:

> interface w60g monitor wlan60-1 once
connected: yes
frequency: 58320
remote-address: 04:D6:AA:XX:XX:XX
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -58
tx-sector: 52
tx-sector-info: right 0.2 degrees, up 1 degrees
rx-sector: 96
distance: 1296.07m

> interface w60g monitor wlan60-1 once
connected: yes
frequency: 58320
remote-address: 04:D6:AA:XX:XX:XX
mcs: 8
phy-rate: 2.3Gbps
signal: 50
rssi: -69
tx-sector: 35
tx-sector-info: center
rx-sector: 96
distance: 1296.06m

What is strange: How could the RSSI on both sides differ that much. Misalignment on one side should affect both rssi values. LOS is free. No reflections. Is Beamsteering doing some magic here which works only in one direction?

Did you measure with traffic on link?

Did you measure with traffic on link?

Yes. No difference.

ROs v.6.42.6 , link up with low rain and wind 28 kts.

Notice no Tx-sector info in master device using winbox window, I must use monitor via terminal.
If I tryed to center the devices , RSSI value increses. I have a good RSSI without center the devices.

ROs v.6.42.6 , link up with low rain and wind 28 kts.

Notice no Tx-sector info in master device using winbox window, I must use monitor via terminal.
If I tryed to center the devices , RSSI value increses. I have a good RSSI without center the devices.

Please show the other side.

Hi guys

what version of firmware is ok for LHG60? I 'm not sure but with 6.42.6 the RSSI level is worst than 6.42.5 and I read on the forum that 6.42.4 is better than 6.42.5

Any advice?

Thank you

We’re sticking with 6.42.3. We never tried 6.42.4 before we tried 6.42.5 and .6, but .4 should be OK as the only w60g change was “improved RAM memoy allocation processes”

Something weird I noticed: It stopped raining since around 30 mins and suddenly the LHG60 link dropped to MCS 1 even with a good RSSI (-55 dBm):
frequency: 64800
mcs: 1
phy-rate: 385.0Mbps
signal: 20
rssi: -55
tx-sector: 41
tx-sector-info: left 1 degrees, up 0.6 degrees
rx-sector: 96
distance: 1166.37m

The link stayed like that until I passed some heavy traffic through it and then it when back to more normal values:
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -55
tx-sector: 47
tx-sector-info: right 1.4 degrees, up 0.6 degrees
rx-sector: 96
distance: 1166.36m

No idea what is causing that...

I'm seeing this as well in 6.42.6 with no rain and full LOS. I'm not sure why on first boot and install the MCS, signal, and phy-rate is pretty stable but over time it jumps around for no apparent reason.

Distance: 1166.37m
Frequency: 64800
RSSI without rain: -56

Just had a thunderstorm: lost the connection 5-6 times in 20 minutes.

Did you aligned based on the tx sector info or the rssi? Imho, result is better when using rssi. The sector info randomly vary from "center" to +/- 2 degree in my case. With the wAP60, it's a lot worse: over 50m, the sector info vary by +/- 20 degree or so.

I am running on 6.42.6, frequency is set to auto. Disconnects are too often - 230x for 4 days uptime is insane... Distance about 340m.
Clear LoS, no rain for 4 days... any idea what else should I check?

1950 meters link


rrssi sta/ap / chanel

-63/-64 chanel 58g
-68/-68 chanel 60g
-68/-66 chanel 62g
-58/-57 chanel 64g

Heavy Rain comparision lgh60 1950m (58ghz), lhg60 650m (auto), siae 17g, airfiber 24g

LHG 60 left/right alligment tool

size of clamping is 90-110 cm

It helps a lot

remember correct alligment requre
- set 58ghz (not auto)
- do bandwith test UDP 500Mbit symmetric between two lHG 60
- monitor via terminal interface w60g monitor interval=1s numbers=0
on both sides
- you should have same rssi on both side (eg 1950meter link has ~~ -62 rssi on 58Ghz and -57 on 64Ghz)

RSSI is only one real information to correct link alligment

differrent link rssi to frequency on 1950m link
-63/-64 chanel 58g
-68/-68 chanel 60g
-68/-66 chanel 62g
-58/-57 chanel 64g


And its my simple clever helper to left/right allign ( its fu... u... in original mounting)

I am running on 6.42.6, frequency is set to auto. Disconnects are too often - 230x for 4 days uptime is insane... Distance about 340m.
Clear LoS, no rain for 4 days... any idea what else should I check?

Hi you should make correct alligment,
i had same problem on 1950m., after correct alligment link works stable

http://www.cdr.pl/p6418,uchwyt-precyzyj ... adkit.html

precision alignment bracket

We aligned it based on tx-sector-info (more specifically, one device was aligned by the LEDs indicators on the device, the other was aligned from the terminal because the LEDs drove me crazy).

Try to align based on the RSSI. You should be able to get a much better signal.

we are having loads of disconnects. Up and down constantly signal is solid at -53.

If we load 6.43rc5 no disconnects at all.

All the newer versions constant disconnects. Any ideas on how to solve this?

We are currently on 6.43rc45

Try 6.42.4 seems to be stable

we are having loads of disconnects. Up and down constantly signal is solid at -53.

If we load 6.43rc5 no disconnects at all.

All the newer versions constant disconnects. Any ideas on how to solve this?

We are currently on 6.43rc45

Same here. 6.43rc40 and 6.43rc44 both have constant disconnects on links that are definitely not overlimit - one is only 25 metres!!

FYI 6.43rc51:

*) w60g - added distance measurement feature;
*) w60g - fixed random disconnects;
*) w60g - improved MCS rate detection process;
*) w60g - improved MTU change handling;
*) w60g - properly close connection with station on disconnect;

rc51 seems OK (so far) for point-to-point. Still seeing a lot of disconnects on multipoint.
6.42.3 continues to be my favorite firmware for these radios.

FYI 6.43rc51:

*) w60g - added distance measurement feature;
*) w60g - fixed random disconnects;
*) w60g - improved MCS rate detection process;
*) w60g - improved MTU change handling;
*) w60g - properly close connection with station on disconnect;

Greetings all! Couple of questions straight away:
How does LHG 60 act with interference? As soon as it was announced in the shops, I see them almost on every tower now (We have A LOT of competitors). Taking into account that it has 2Ghz bandwidth I can only imagine what is going to happen. And no one knows exact antenna pattern, how wide it is. If it is flashing all around, for sure it will affect link across op opposite or even...somewhere. Ok, it is well known that on this freq there is a lot of attenuation, but locally it may cause (or not?) problems.

Ok, we have siklu 60G band relays, and those guys all around started to mount LHGs, how they co-exist? Taking into account that they like to overpower radios, I am very worried that a 200 bucks toy can affect an expensive piece of hardware, which is a bint unfair first of all.

Anyways, I have ordered 3 pairs of them, because it is sure a good value for the money to replace or backup overloaded 5Ghz links, but still..To me it seems like I bomb in monkeys hands.

60Ghz signal drop very fast with distance because it's absorbed by oxygen so even links that are very near to each others don't interfere much. I didn't try with LHG60 but I didn't had any problem running 2 Metrolinq back to back on the same channel (and they don't have gps synch).

v6.42.3 is indeed much more stable than 6.42.6. I had fluctuating signal quality and MCS and many 8s linkdows. With 6.42.3 the signal quality is stable 80-95, MCS mosty 8, and only one 1s linkdown a day. Link length 386m.

Nice work, thanks Mikrotik, update from RC51 to RC56

Is this the distance record?
Link is working perfect! I am hitting 1gbps on Ethernet interface with iperf!

Testing a point to multipoint setup. 4 clients all under 240 meters. Speed is great but disconnections are very often. In my experience if one link has poor signal -70dbm and it disconnects it caused all the other stations to disconnect just after the poor signal station disconnects. This behaviour is repeatable. I think once MT can perfect the software it will be very good but right now seems a little unstable.

Hi,

connected: yes
frequency: 58320
remote-address: 04:D6:AA:A7:MN:S7
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -60
tx-sector: 22
tx-sector-info: right 1 degrees, down 0.6 degrees
distance: 539.35m

with rc56 random disconnections gone.

Hi

I can also confirm random disconnects have gone in RC56 thanks guys. Here is our link it drops out instantly in heavy rain yet our MetroLinq 2.5 of same distance carry's on working fine.

connected: yes
frequency: 64800
remote-address: 04:D6:AA:AF:D5:0E
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -55
tx-sector: 36
tx-sector-info: center
distance: 1088.42m

Hi

I can also confirm random disconnects have gone in RC56 thanks guys. Here is our link it drops out instantly in heavy rain yet our MetroLinq 2.5 of same distance carry's on working fine.

connected: yes
frequency: 64800
remote-address: 04:D6:AA:AF:D5:0E
mcs: 8
phy-rate: 2.3Gbps
signal: 80
rssi: -55
tx-sector: 36
tx-sector-info: center
distance: 1088.42m

Sure the ML is within allowed EIRP ...

Sure the ML is within allowed EIRP ...

The Metrolinq has certification.

Testing a point to multipoint setup. 4 clients all under 240 meters. Speed is great but disconnections are very often. In my experience if one link has poor signal -70dbm and it disconnects it caused all the other stations to disconnect just after the poor signal station disconnects. This behaviour is repeatable. I think once MT can perfect the software it will be very good but right now seems a little unstable.

We have the same setup with several PTMP tests, clients all under 200m:
- when one client reboots or loses a connection, all clients drop connection for a few seconds
- latency / jitter doubles every time a client is added
- RC56 has not made much of a difference
We also have several PTP test links under 1000m:
- RC56 seems to have helped a lot with random disconnects
- Struggling to get good RSSI reading which also seems worse after upgrading firmware
- Still dropping in heavy rain

We found that the installation location is more important than one would assume on a building or roof (was expecting the narrow beam pattern to do the work)

as my experience when rain is started its always going down , Pls looking and support

Hope to have soon a feedback in a rainy day

Rain rain rain.. We need more real live testing. But.. Todays situation about 40-45mm/h link was down for 4 minutes going from -56 to -70 in few seconds. The wet antenna takes -4dB!! Link length 1300m.
The link nearby with WAP for 400m was doing well all the time loosing approxiamtely 1-2 on RSSI scale looding from -66 to -68, and already working as before the rain. LHG is 15 minutes after rain still -59 and once dry has to come up to -56.

We have a 1.2km link with LHG 60G's, properly aligned, with signal around -68dB. Link drops immediately with the slightest rain. Since we're using BFD and have a 5GHz link as a backup it's not an issue, but I wonder where the signal difference with some others (e.g. @cohprog) in this topic comes from. It seems most people have signals in the -50's at the same distance.

Code: Select all

       connected: yes
       frequency: 64800
  remote-address: 04:D6:AA:BC:98:29
             mcs: 8
        phy-rate: 2.3Gbps
          signal: 80
            rssi: -68
       tx-sector: 20
  tx-sector-info: right 0.2 degrees, down 0.6 degrees
       rx-sector: 96
        distance: 1188.2m
        
       connected: yes
       frequency: 64800
  remote-address: 04:D6:AA:BC:98:75
             mcs: 8
        phy-rate: 2.3Gbps
          signal: 80
            rssi: -66
       tx-sector: 44
  tx-sector-info: right 0.2 degrees, up 0.6 degrees
       rx-sector: 96
        distance: 1188.21m

Hi, How did you configure the 5ghz back up? Im hoping to do the same with a pair of powerboxes and a pair of powerbeams to back up the LHGs. Im not familiar with BFD.

Cheers,

GT

We found that the installation location is more important than one would assume on a building or roof (was expecting the narrow beam pattern to do the work)

Multiple reflections can be a problem I guess.

I've seen max distance specs on the products and testing for WAP60 to WAP60 and LHG to LHG, but what about WAP60 to LHG 60? I assume that would cut the 1500m limit down to what, 1000m?

With rain fade I wouldn’t go any more than 800m on the LHG to LHG

Our 1000m is dead as soon as you get a downpour

I've seen max distance specs on the products and testing for WAP60 to WAP60 and LHG to LHG, but what about WAP60 to LHG 60? I assume that would cut the 1500m limit down to what, 1000m?

Distance: 1166.37m
Frequency: 64800
RSSI without rain: -56

Just had a thunderstorm: lost the connection 5-6 times in 20 minutes.

cohprog,

What monitoring software is that?

1950 meters link


rrssi sta/ap / chanel

-63/-64 chanel 58g
-68/-68 chanel 60g
-68/-66 chanel 62g
-58/-57 chanel 64g

Heavy Rain comparision lgh60 1950m (58ghz), lhg60 650m (auto), siae 17g, airfiber 24g

deszcze.PNG

venthyl ,
What monitoring software is that?

1950 meters link


rrssi sta/ap / chanel

-63/-64 chanel 58g
-68/-68 chanel 60g
-68/-66 chanel 62g
-58/-57 chanel 64g

Heavy Rain comparision lgh60 1950m (58ghz), lhg60 650m (auto), siae 17g, airfiber 24g

deszcze.PNG

venthyl ,
What monitoring software is that?

So looks like channel 64g is best in the rain?

We have found that if you lock the tx-sector using the cli and do the alignment, once you unlock the tx sector, the rssi gets better by 2-5 db. Not sure if it would get there without this procedure tho. Since there are 64 sectors, we lock it to the middle. We don't bother with the arrows, we look at rssi only.

The problem we have is the feedback loop is to long. When you make an adjustment, the rssi won't update for seconds. I assume this is because the chipset is evaluating all the sectors rx signal. If we could lock the tx and rx for alignment mode and have more frequent rssi updates it would help to get a proper alignment. In my opinion the process should start with aligning the radios for dead center with locked tx/rx. Once it's dialed in then turn on the beam forming.

Me also lost a lot of time trying to get my 2,2km link working. Info from cli and winbox is very slow. From time to time i had to wait for 15-20 seconds for information to settle down. Hope that we will get some more precise alignment tool. I hope that 802.11ad don't end up like spectral scan on 802.11ac.

BR...

Me also lost a lot of time trying to get my 2,2km link working. Info from cli and winbox is very slow. From time to time i had to wait for 15-20 seconds for information to settle down. Hope that we will get some more precise alignment tool. I hope that 802.11ad don't end up like spectral scan on 802.11ac.

BR...

Did you set channel to 64800?

Yes. Other channels don't work on such a long distance.

Yes. Other channels don't work on such a long distance.

Right.....

I hope for some more features in 802.11ad

- Smaller channel width

But the hope is gone almost for 802.11ac

cohprog,

What monitoring software is that?

Zabbix. There is no pre-made template for LHG60 but it's easy to do one. (there is a script that will do a snmpwalk and generate a Zabbix template based on it)

We have found that if you lock the tx-sector using the cli and do the alignment, once you unlock the tx sector, the rssi gets better by 2-5 db. Not sure if it would get there without this procedure tho. Since there are 64 sectors, we lock it to the middle. We don't bother with the arrows, we look at rssi only.

6.42.7 and 6.43rc64 have very important enhancements to the tx-sector selection.

I have been following the betas and the stability has improved a lot since rc56.

The original bracket is not convenient for smooth adjustment. I use this one : http://www.cdr.pl/p6418,uchwyt-precyzyj ... adkit.html but with the addition tool from Metrolinq.

Is the new channel still only available in CLI or did they finally add it to winbox in the latest RC?

Is the new channel still only available in CLI or did they finally add it to winbox in the latest RC?

You can choose 4 channels in winbox

I am running on 6.42.6, frequency is set to auto. Disconnects are too often - 230x for 4 days uptime is insane... Distance about 340m.
Clear LoS, no rain for 4 days... any idea what else should I check?

Hi you should make correct alligment,
i had same problem on 1950m., after correct alligment link works stable

Nice dude 1950m stable link good news, I've done 1560m link works very stable, I was sceptic about 1750m but now I m going for it.

1750m LHG60 ROS 6.43 Freq:
58320 -59
60480 -63
62640 -62

The LHG 60G pointing to proper direction is impressively imprecise, which is strange with that beam forming and all. The link signal will cut off by only minor adjustments thus these "0.2 degrees left or right" are almost funny. What is the antenna pattern and how that device is using it?

Just to make a quick experiment: unsoldered LDF patch antenna and put it in the centre of the LHG60, The loss is high 8 to 10 dB compared to the LHG 5AC but easy solutions to make a cheap 5GHz backup using the same antenna

The copper on the bottom is the reflector for the patch I don't make any calcultions only I just made it.

any suggestions?

1750m LHG60 ROS 6.43
lhg60 1750m.png

Freq:
58320 -59
60480 -63
62640 -62

Dang! I think you won a certain type of silicon lottery! We have 750m link at ~-50dBm signal. Yours at 1km more should see an additional ~-22dBm fade over ours so expected would be -72. I wonder, if you found the magical beamforming TX sector. Because in reality we took down an ML2.5 link which was connected at calculated RSSI of -33dBm, replaced with this one and now only -49 at best.

1750m LHG60 ROS 6.43
lhg60 1750m.png

Freq:
58320 -59
60480 -63
62640 -62

We are suprised also with results (Signal) from Lakis ? Can you please share procedure to align, we have difficulties with proper aligning LHG 60G...

Dang! I think you won a certain type of silicon lottery! We have 750m link at ~-50dBm signal. Yours at 1km more should see an additional ~-22dBm fade over ours so expected would be -72. I wonder, if you found the magical beamforming TX sector. Because in reality we took down an ML2.5 link which was connected at calculated RSSI of -33dBm, replaced with this one and now only -49 at best.

Don't trust RSSI readings too much. You should be able to get same distances with ease - upgrade to latest versions, there a lot of changes that affect receive sensitivity

Dang! I think you won a certain type of silicon lottery! We have 750m link at ~-50dBm signal. Yours at 1km more should see an additional ~-22dBm fade over ours so expected would be -72. I wonder, if you found the magical beamforming TX sector. Because in reality we took down an ML2.5 link which was connected at calculated RSSI of -33dBm, replaced with this one and now only -49 at best.

Don't trust RSSI readings too much. You should be able to get same distances with ease - upgrade to latest versions, there a lot of changes that affect receive sensitivity

So what exactly do we trust? What are we aiming for, centre? If so, I have seen centre on different tx-sector. 36, 26/27, etc

Don't trust RSSI readings too much. You should be able to get same distances with ease - upgrade to latest versions, there a lot of changes that affect receive sensitivity

So what exactly do we trust? What are we aiming for, centre? If so, I have seen centre on different tx-sector. 36, 26/27, etc

I have asked this exact question in another thread. I have had answers about my radios being too close etc. I thought it was an alignment problem but we have tweaked and tweaked and cannot get any better results. We are seeing a lot of Link Downs on the Station side of our 60Ghz Mikrotik links.

draguzet wrote

We are suprised also with results (Signal) from Lakis ? Can you please share procedure to align, we have difficulties with proper aligning LHG 60G...

Dude its very hard.
------------------------
DynStatic
-When you make an adjustment, the rssi won't update for seconds.
blue
-From time to time i had to wait for 15-20 seconds for information to settle down.
------------------------ Thats why!!!

muldeegg
- when one client reboots or loses a connection, all clients drop connection for a few seconds
Jokes aside I hate this problem Mikrotik please fix this

I am as well having issues getting these things aligned...

1) Using the LED method absolutely won't work. If I use this my dish is physically aligned 20 degrees off of the remote dish.
2) MT provides few definitions on what we are seeing on the monitor/status menus. Signal, what is this exactly? Is this is db? What are the TX-SECTOR and RX-SECTOR numbers referring to?
3) RSSI stops responding after a while and is not reliable.
4) How do I turn beam forming off? I cannot figure out the nomenclature in terminal mode to do this and again there is no documentation on this. I think if I add a number to TX-SECTOR to set it as NOT auto, that turns of beam forming, but I can't figure out what to type to get that to happen.

My goal today was to change the TX-SECTOR to 32 thereby turning off beamforming and using RSSI while it responded to align our dishes. Is there a better TX-SECTOR number to use to get alignment handled than 32?

I don't like forums, but in the absence of decent wiki docs or online documentation I am forced to admit defeat and ask for input from those who have had better luck.

A better alignment procedure would be very helpful including CLI commands. We are using 6.43.2 presently.

Thanks to anyone who can help!

I think that the correct command to shut down beamforming is /interface w60g set 0 tx-sector=32... I have no idea what the "0" is in the set command however.

Updating my prior post...

I'm be putting up a LHG-60 PTP tomorrow at ~ 1300m, will I have fade? That's about 0.85 mi or so, which in my world is across the street.

Also, upon bench testing how do I see the PHY and other stats people posted on here? I even upgraded to the latest RC (development says N/A)

Pretty annoying actually, not even the station displays ANY sort of signal, MCS rates, PHY, NOTHING all is blank, with the latest RC! How has nobody seen this yet??

Pretty annoying actually, not even the station displays ANY sort of signal, MCS rates, PHY, NOTHING all is blank, with the latest RC! How has nobody seen this yet??

The testing branch is in beta these days, not RC.
I recommend 6.42.9 for production deployment.

Pretty annoying actually, not even the station displays ANY sort of signal, MCS rates, PHY, NOTHING all is blank, with the latest RC! How has nobody seen this yet??

You are using the most recent beta. I get that too, I used montior 0 on the CLI to get around that.

"The testing branch is in beta these days, not RC.
I recommend 6.42.9 for production deployment."

I haven't tried 6.42.9 yet. I have been going between the current and testing versions and am neither having much luck keeping a stable link nor am I confident in my alignment.

Would you please provide an alignment procedure that works for you? Apparently we shouldn't use RSSI and the LED method has not worked for me; it sends me way off a bore sighted path.

Also, can anyone tell me the significance of what the SIGNAL, RX-SECTOR and TX-SECTOR data is and how this might help an alignment?

v6.43
connected: yes
frequency: 58320
remote-address: xx:xx:xx:xx:xx:xx
mcs: 4
phy-rate: 1155.0Mbps
signal: 40
rssi: -71
tx-sector: 30
tx-sector-info: right 1 degrees, down 0.2 degrees
distance: 1845.78m
Not tested in rain conditions yet.

v6.43
connected: yes
frequency: 58320
remote-address: xx:xx:xx:xx:xx:xx
mcs: 4
phy-rate: 1155.0Mbps
signal: 40
rssi: -71
tx-sector: 30
tx-sector-info: right 1 degrees, down 0.2 degrees
distance: 1845.78m
Not tested in rain conditions yet.

You will loose that in rain!

v6.43
connected: yes
frequency: 58320
remote-address: xx:xx:xx:xx:xx:xx
mcs: 4
phy-rate: 1155.0Mbps
signal: 40
rssi: -71
tx-sector: 30
tx-sector-info: right 1 degrees, down 0.2 degrees
distance: 1845.78m
Not tested in rain conditions yet.

You will loose that in rain!

will see

4th channel should be much better in this distance

i am still waiting from MT LHG60+5ghz in one unit, 5ghz for backup, price per unit should not go a lot even if add price of sxt lite into it.
setting kit with additional sxt unit, poe switch is kind of crazy..

Interesting experiences.
I have some test kit going up soon which is by Google mapping 2.63Km clear LOS tower to tower.
I'm not expecting full PHY rates but am wondering what it will reach and how any rain will affect the link. My hope is that it folds back and doesn't go off completely.

Interesting experiences.
I have some test kit going up soon which is by Google mapping 2.63Km clear LOS tower to tower.
I'm not expecting full PHY rates but am wondering what it will reach and how any rain will affect the link. My hope is that it folds back and doesn't go off completely.

Mikrotik is now claiming 4km (https://mum.mikrotik.com/presentations/ ... 743074.pdf) but I’m reluctant to try. Maybe with the new 66000 MHz channel?

Interesting experiences.
I have some test kit going up soon which is by Google mapping 2.63Km clear LOS tower to tower.
I'm not expecting full PHY rates but am wondering what it will reach and how any rain will affect the link. My hope is that it folds back and doesn't go off completely.

Mikrotik is now claiming 4km (https://mum.mikrotik.com/presentations/ ... 743074.pdf) but I’m reluctant to try. Maybe with the new 66000 MHz channel?

What is this: "Enabled 6GHz testing..." ??

typo of 66GHz

Much higher distances are available by using 64800 and 66000 MHz frequencies

Hi, Running 6.44Beta20

No tx-power setting for the 60Ghz interfaces.

I've got several links that are very close and I suspect we can improve the quality by turning down the TX power.

Any idea when it will be a configurable option again ??

I've checkd, WinBox, WebFIg and CLI

Thank you

66000 GHz is non standard freq for this band? Will You implement 66960 GHz and 69120 GHz?

woow grat news form mikrotik I am curios if someone has stable link over 1500+ during rain events, 4000m is very long link for 60ghz technology

66000 GHz is non standard freq for this band? Will You implement 66960 GHz and 69120 GHz?

it's not a standard channel

Without more data on stability in rain events @66000 it's not safe to pay a licensed link

66000 GHz is non standard freq for this band? Will You implement 66960 GHz and 69120 GHz?

it's not a standard channel, special permissions usually are required to operate at this frequency.

server8 I have very stable link at 1750m
From MUM UK
• Major received signal sensitivity improvements
• LHG60G can reach up to 4000 m distances (depending on
used frequency)
4 km what?
Is it like LHG60G signal reached 4000m but throughput was eh, than the rain start and we lost signal.

Can someone from Mikrotik give us more info.

What firmware version are you running on this link? Are you using 64800 or 66000?

server8 I have very stable link at 1750m

What firmware version are you running on this link? Are you using 64800 or 66000?

server8 I have very stable link at 1750m

OS 6.43.2 Freq:58320. On Freq:64800 I got best RSSI around -56dB
LHG60G does not support 66000.

What firmware version are you running on this link? Are you using 64800 or 66000?

server8 I have very stable link at 1750m

OS 6.43.2 Freq:58320. On Freq:64800 I got best RSSI around -56dB
LHG60G does not support 66000.

Yes it does with newest beta and only from CLI.

What firmware version are you running on this link? Are you using 64800 or 66000?

server8 I have very stable link at 1750m

OS 6.43.2 Freq:58320. On Freq:64800 I got best RSSI around -56dB
LHG60G does not support 66000.

Yes it does with newest beta and only from CLI.

but if 66Ghz is Central freq. its illegal to use.

Use it for testing purposes only!

Hi!

66GHz sounds great, but if I'm right, LHG60 uses 2000 MHz Channel bandwidth.
In this case, 65GHz would be perfect...

Hi!

66GHz sounds great, but if I'm right, LHG60 uses 2000 MHz Channel bandwidth.
In this case, 65GHz would be perfect...

Channel 64800 is near to 65000 so no need

Has anyone got OID values for RSSI? It would be nice to graph the signal during the rain, just to see how much it changes.
I've only got this from CLI:

mode=.1.3.6.1.4.1.14988.1.1.1.8.1.2.1
ssid=".1.3.6.1.4.1.14988.1.1.1.8.1.3.1"
frequency=.1.3.6.1.4.1.14988.1.1.1.8.1.6.1

This works for me.
SNMPv2-SMI::enterprises.14988.1.1.1.8.1.12.1 = INTEGER: -66

Has anyone got OID values for RSSI? It would be nice to graph the signal during the rain, just to see how much it changes.
I've only got this from CLI:

mode=.1.3.6.1.4.1.14988.1.1.1.8.1.2.1
ssid=".1.3.6.1.4.1.14988.1.1.1.8.1.3.1"
frequency=.1.3.6.1.4.1.14988.1.1.1.8.1.6.1

so it does, thank you!
the full value i've entered in PRTG is 1.3.6.1.4.1.14988.1.1.1.8.1.12.1

This works for me.
SNMPv2-SMI::enterprises.14988.1.1.1.8.1.12.1 = INTEGER: -66

Has anyone got OID values for RSSI? It would be nice to graph the signal during the rain, just to see how much it changes.
I've only got this from CLI:

mode=.1.3.6.1.4.1.14988.1.1.1.8.1.2.1
ssid=".1.3.6.1.4.1.14988.1.1.1.8.1.3.1"
frequency=.1.3.6.1.4.1.14988.1.1.1.8.1.6.1

Hi all

I'm starting in this world of 60Ghz .. And I'm quite surprised ... I have some doubts, since there is little information about mikrotik antennas at 60Ghz ..
For example:
The Mikrotik wAP 60G, the array says 60º. Vertical and Horizontal, or only Horizontal? . And if it were Horizontal, what is the Vertical Angle of the beam?
In the LH60G, what is the Beam?

If someone can answer me, I would like it
Thank you

Hi all

I'm starting in this world of 60Ghz .. And I'm quite surprised ... I have some doubts, since there is little information about mikrotik antennas at 60Ghz ..
For example:
The Mikrotik wAP 60G, the array says 60º. Vertical and Horizontal, or only Horizontal? . And if it were Horizontal, what is the Vertical Angle of the beam?
In the LH60G, what is the Beam?

If someone can answer me, I would like it
Thank you

Yes there is so little info about LHG60, I want to know that too. Last update was now LHG60 can do 4000m, they added 66Ghz channel so I m not sure if 4000m is only possible on 66Ghz or you can use all channels which I m sceptic about that.
Mikrotik is like '' Oh yes we made some signal improvements now you can go for 4km '' What about rain, what data rate should we expect, signal level and etc. there is so much lack of information.

The Mikrotik wAP 60G, the array says 60º. Vertical and Horizontal, or only Horizontal? . And if it were Horizontal, what is the Vertical Angle of the beam?
In the LH60G, what is the Beam?

https://www.youtube.com/results?search_ ... lin++video if you search you 'd find a video about wap 60g that explain that coverage angle vertical/horizontal is close to 180°

What are the commands to set 66000 and add 66000 in the scan list on the client and AP sides?

66000 GHz is non standard freq for this band? Will You implement 66960 GHz and 69120 GHz?

it's not a standard channel

This source mentions 6 channels (ch5 = 66960, ch6 = 69120 MHz):

https://en.wikipedia.org/wiki/Wireless_ ... e#Channels

"Regional spectrum allocations vary by region limiting the available number of channels in some regions. The US is the only region supporting all six channels. " - is this true?

On the other hand, I've seen some other standard (intended for China) with four 1.08 GHz wide channels numbered 5, 6, 7, 8 in the same frequency range as channels 2, 3 (allowed in China).
Any chance we will see support for narrower channels? Not everyone needs a full gigabit of throughput, often can't be fully used due to the max 8 stations per AP limit.

Any chance we will see support for narrower channels? Not everyone needs a full gigabit of throughput, often can't be fully used due to the max 8 stations per AP limit.

+100

Any chance we will see support for narrower channels? Not everyone needs a full gigabit of throughput, often can't be fully used due to the max 8 stations per AP limit.

+100

+100
without narrower channels, the devices with Fastethernet are not needed

Greetings
Does someone have this radios on a 2500 meter distance?
What is the bandwidth of link?

Greetings
Does someone have this radios on a 2500 meter distance?
What is the bandwidth of link?

with probably alignment you will see full gigabit bandwidth, but it will drop during rain/snow.

@server8 Have you tried this out yet? Great idea.
Could the patch be mounted on just above or below the aperture on the 60G feed? It wouldn't be the exact focal point but it might be close enough to get some gain back.
Worth a try?

LBNL

I have no time to make test on field just an idea, around 2 max 3 km the link loss of the solution is high but the signal is enough to have a good 5 ghz backup in rain events

Feel free to copy it

I am still waiting for a descent alignment procedure. This is the biggest downfall.

I am still waiting for a descent alignment procedure. This is the biggest downfall.

+1

What are the commands to set 66000 and add 66000 in the scan list on the client and AP sides?

Still need these Chris?

Mikrotik 60Ghz CLI commands
STA
/interface w60g set wlan60-1 frequency-list=58320,60480,62640,64800,66000

AP
/interface w60g set wlan60-1 frequency=66000

I'm just want to share my experience with PtP W60G link.
We've deployed this link about 45 days ago. Since then we have experience HEAVY rain (2 days non-stop) and light snowing. Link hasn't disconnected once and lowest MCM was 6.
I've read that people have problems with allignment but we all have because it's not easy and even 0.5 degree can make a difference. You should use terminal to see both sides and everytime you make change wait about 20-30s until information is updated. Also use ping to see if the link is table and once you feel like you got it just do BT Test.

on station side:
Freq: 64800
Signal:80
MCS:8
PHY Rate:2.3 Gbps
RSSI: -55
TX Sector: 16
RX Sector 96
Distance:399m

On bridge side
Freq: 64800
Signal: 80
MCS: 8
RSSI: -57
TX: Sector 36
RX: Sector 96
Dostance: 399

RouterOS 6.43.4 = very nice and stable

This link is in City with a clear view (from building to church)

New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1

New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1

Thanks guys.

Pictures and Specifications.... Please.

3.png

Pictures and Specifications.... Please.

https://www.ip-sa.com.pl/doc/datasheet/LHG_Lite60.pdf

We use LHG-60G on link ~900 meters. We have 1 gbit/sec in duplex mode bandwith-test. We try to establish link in 1.5km - fail.

Dear users, what is Your real world bandwidth usage?
Is lhg60 in short distance ptp scenario really able to push ~1gbps ?

I just put up a 370m link to feed few hundred users from 1gb/s fiber and I wonder if it's gonna work or should I look for more sophisticated FDX solution?

Dear users, what is Your real world bandwidth usage?
Is lhg60 in short distance ptp scenario really able to push ~1gbps ?

I just put up a 370m link to feed few hundred users from 1gb/s fiber and I wonder if it's gonna work or should I look for more sophisticated FDX solution?

At 370m with good alignment a couple of LHG 'd work close to gigabit FD due to alignment problem with the standard bracket I suggest to you to use this http://www.cdr.pl/p6418,uchwyt-precyzyj ... adkit.html

Thanks for reply, but I see it quite expensive bracket. And with my brick chimney 50m high, windload gives a lot of instability overall.
So i'm not sure if it will help.
1/As for now I see signal 90-105 and mcs 8 to 11, are higher mcs even possible?
2/And what about pps or tcp is this arm cpu capable of doing 1gbps TCP traffic? I've seen some iperf test to fill 950mbps of tcp but seen only tests.
3/Anybody use this gear in real world and achieves such bandwidth?

we have use lhg 60g on link 900 meters. All OK. throughput ~1 gbit/sec in duplex test.

We use LHG-60G on link ~900 meters. We have 1 gbit/sec in duplex mode bandwith-test. We try to establish link in 1.5km - fail.

artferrr
I m running link 1750m freq:64800 37days not a single ''link down'' If you have time please read all posts on this topic

Those are the top three records
1. venthyl 1950m
2. Tepelensi 1845m
3. mistry7 1812m

My working link is 2205m. Rain haven't fall in more than a month, so I don't know how it will behave. 5GHz is backup.

Please look at this post:
viewtopic.php?f=7&t=133374&start=50#p680529

My working link is 2205m. Rain haven't fall in more than a month, so I don't know how it will behave. 5GHz is backup.

Please look at this post:
viewtopic.php?f=7&t=133374&start=50#p680529

How did I miss that. Nice Blue nice alignment I was going to test 2000m next week.
With that signal moderate rain should not case any problems.

Top distance records
---------------------------
1. Blue 2205m
2. venthyl 1950m
3. Tepelensi 1845m
4. mistry7 1812m

3765m - https://ispforum.cz/download/file.php?id=8741
4173m - https://ispforum.cz/download/file.php?id=8742

For all of you that don't seem to be dropping, how are you aligning your LHG's and even WAP60G's if using those. My disconnects have to be coming from an alignment issue.

Are you using Signal, RSSI, sector info?

Few days ago I tested on around 6000 meters, but no luck. One side was fixed on tower, and other side was aligned from hand.

For all of you that don't seem to be dropping, how are you aligning your LHG's and even WAP60G's if using those. My disconnects have to be coming from an alignment issue.

Are you using Signal, RSSI, sector info?

I am looking at RSSI.

3765m - https://ispforum.cz/download/file.php?id=8741
4173m - https://ispforum.cz/download/file.php?id=8742

These long-range links use a non-standard and illegal 66000 frequency. Any chance for MT to implement 66960 and possibly 69120 too? Still illegal in many parts of the world, but at least standard (channels 5 and 6), doesn't interfere with 64800 which may need to work at the same location too. Or is this beyond the capabilities of current hardware?

Just an FYI, the bandwidth test tool doesn't max out the capacity of the link. For a full-speed test use the traffic generator.

New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1

Is the Left/Right - Up/Down - Center alignment working properly using this with latest 6.44Beta28 ?

New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1

Is the Left/Right - Up/Down - Center alignment working properly using this with latest 6.44Beta28 ?

I don't believe what it reports. I am looking only at RSSI. It is tricky to align it without precise alignment kit, but spend a little more time than usual since beam is very narrow (that is a good thing).

Thanks for reply, but I see it quite expensive bracket. And with my brick chimney 50m high, windload gives a lot of instability overall.
So i'm not sure if it will help.
1/As for now I see signal 90-105 and mcs 8 to 11, are higher mcs even possible?
2/And what about pps or tcp is this arm cpu capable of doing 1gbps TCP traffic? I've seen some iperf test to fill 950mbps of tcp but seen only tests.
3/Anybody use this gear in real world and achieves such bandwidth?

1/ not at the time
2/ it's capable of doing 1 Gbps in TCP
3/ we use this gear and it works fine. Clients (about 150 clients) don't fully utilize aggregation of this link. There's about 60kpps in TCP of traffic.

As with everything in networking the quality of your network depends on your needs. Are your Clients even capable to fully aggregate PtP 60G link ? I think you should deploy one PtP link (it's cheap af) and test it or just look at your switch and look how many pps and what size they are using.

Trying to work out if I should waste my time trying a 320 metre link with a pair of Wireless Wires?

Don't need 1Gbit - I'd be happy with 200 bit. Is this going to fly based on people's experience with latest firmware?

Yesterday we installed 1 New Link using the 60Ghz PTP Radios
Strange thing is the date it states its November and we still in October

This is the results:

New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1

Is the Left/Right - Up/Down - Center alignment working properly using this with latest 6.44Beta28 ?

This is what I am seeing when running the align test from the Bridge unit:

connected: yes
frequency: 64800
remote-address: xx:xx:xx:xx:xx:xx
tx-mcs: 8
tx-phy-rate: 2.3Gbps
signal: 90
rssi: -57
tx-sector: 36
tx-sector-info: center
distance: 1473.14m
tx-packet-error-rate: 0%

However, after I ran the align test, the Bridge unit defaulted back to Frequency 58320... Why does it change frequency?

connected: yes
frequency: 58320
remote-address: xx:xx:xx:xx:xx:xx
tx-mcs: 8
tx-phy-rate: 2.3Gbps
signal: 90
rssi: -54
tx-sector: 27
tx-sector-info: center
distance: 1473.19m
tx-packet-error-rate: 0%