The coding scheme is available through : MCS
Look at the published MIB variables: https://wiki.mikrotik.com/wiki/Manual:Interface/W60G#SNMP_OIDs_for_monitoring
sofar I am happy with 60ghz dishes, hopefully there would not be any bugs with them to run on production : )
still under big question, will they beat 2.7-3km range or not, so far as I calculated should be on the limits, with fail-over to existing 5ghz could be a good improvement.
@strods: does this apply to all units, since the beginning of product distributions or is it limited only to some HW version? I know it has been reached by SW modification and phase array patterns, just want to be sure it is not HW dependent.
Thank you.
@strods: > does this apply to all units, since the beginning of product distributions or is it limited only to some HW version? I know it has been reached by SW modification and phase array patterns, just want to be sure it is not HW dependent.
Thank you.
Topic is clearly about software improvements
Topic is clearly about software improvements
It is OK, that it is about SW improvements, but this SW improvements improves HW specifications. Maybe I was not clear enough, so once again (hope you will not consider it as spamming…)
Does the improvement for 200 meters apply for all WAP60G units which have been produced (regardless of license level) or is it valid only for some HW revisions (if there are any…) of WAP60G?
Thank you.
Improvements in SW many times improve overall functionality. Therefore one can not say what’s HW specification… better to refer to it as “system” specification.
In my company (I work for mobile division of incumbent telco) we have an internal joke about vendors: “yet again they managed to speed-up execution of infinite loop”. And that particular (world-class) vendor officially changes capacity figures in their documentation … or better yet, the specification explicitly states the SW version it’s valid for.
So yes, SW improvements can considerably improve performance and capacity without any HW change.
Remember that a phased array is the antenna rough equivalent of a FPGA chip. So, just reconfiguring it can be equivalent to installing a new antenna.
In my case (units purchased in February) the change was so dramatic that it caused overload problems (my link is short, 20 - 30 m across a street). I had to reduce power, go figure! 
For all WAP60g users please Mikrotik to explain the TX-sector numbers. For use of PtMP or colocation, it would be very useful to know the angles and directions of radiation. Please also add the option to modify the RX sector or turn off the beamforming routine. Thanks
Explanation is already available in monitor:
for example:
tx-sector: 29
tx-sector-info:
right 0.6 degrees, down 0.2 degrees
So, tx-sector=29 means radiations angle 29 degrees, really??
No, tx-sector 29 means +0.6 degrees azimuth, -0.2 degrees elevation. tx-sector is just a sector (beam configuration) identifier that translates to some predefined azimuth/elevation combination, as output to the console.
I have a pair of WAP-60G and have modified some reflectors to increase range up to 1-mile, is there still any distance LIMIT in the software that would prevent them from even registering if they could see each other at 1600 meters? Do I need the latest RC firmware?
As said a few times in other topics, this will not work well. The devices are precisely calibrated so that the beamforming antenna array knows exactly how to adjust itself. If you put that into a reflector, it gets really confused. It may work sometimes, but most likely it will not work.
For a reflector to work properly you really need to “flood” it with radiation.
If the antenna main lobe is more like a sharp pencil the reflector won’t be so effective.
https://en.wikipedia.org/wiki/Parabolic_antenna#Feed_pattern
here my data (6.43rc19) - hope this helps; I am willing to perform other tests…
frequency: 58320
remote-address: 30:07:xx
mcs: 8
phy-rate: 2.3Gbps
signal: 95
rssi: -51
tx-sector: 27
tx-sector-info: right 3.8 degrees, down 3.8 degrees
rx-sector: 96
distance: 15.12m (it’s an “over the street” scenario, having not 100% clear sight)
regards, Stephan
As I just read about new chipsets for Smartphones with 802.11ad Support.
Think about a new room with 200 students.
- In the ceiling there will 9 double sockets with RJ45
- I’ll add 9x cAP AC to those with lowered sending power…
- I will also have some RJ45 sockets.
Ist WAP 60G meant to work like cAP AC with CAPSMAN enabled, multiple concurrent SSIDs enabled and support for 20/30 smartphones connected?
currently other vendors are not supported, as well as CAPsMAN.
This will be added in future releases of RouterOS
How did you reduce power?
/interface w60g set 0 tx-power=[1..15] or default.
In my case set 0 tx-power=10 works great, it links fine with 5 as well.
However, be careful with this setting when updating firmware. If they make changes to the antenna patterns you may need to change/remove it.
The correct answer should sound, Mikrotik does not want it, unfortunately. There is no technical reason why the WAP60g does not work well in the focus of the parabola. When receiving (RX) everything is OK, unfortunately the transmission angle (TX) is set to a much smaller angle, so the parabols are not very bright. If it was possible to set the beam angle (TX) fixed or much larger, it would be after the problem. Well, maybe we’ll get a special version of FW, WAP60g in the focus of the parabola …