Hello guys,
I have a mANTbox ax 15s installed with default parameters at a friend of mine. The country is set to Netherlands and left the other fields blank.
The problem is that my friend is complaining about low reception at approximately 50meters from the access point.
I saw that tx-power is set to 7 for 2.4Ghz and 15 for 5Ghz.
According to ETSI rules the maximum on the 5540 frequency is 27dbm.
Is it possible to increase the tx-power a little bit without creating more problems?
Antenna gain dBi for 2.4 GHz 12
…
Antenna gain dBi for 5 GHz 15
So, not really.
But low reception at 50 meters is definitely not normal, the mantbox Ax 15 s is (should be) capable of km links.
A couple of (good?) questions are:
But low reception at 50 meters is definitely not normal, the mantbox Ax 15 s is (should be) capable of km links.
Indeed, but probably I am doing something wrong.
My friend is using an Android phone. He wasn’t able to see the WIFI network from that point. The Antenna is at 3 meters high under a vertical angle of 10 degrees below.
I left the tx-power and antenna-gain unset, because according to the documentation it should be sending max allowed.
Do you know where I can find out what the values antenna-gain and min_antenna_gain(is blank in CAPSMAN) are currently set to, so I can verify it is set correctly?
It’s correct when following the standards. Max allowed power in your country minus the antenna gain (around 12 db on 2.4G and 15 db on 5G).
No idea, but are you using CAP/CAPSMAN for a single access point?
3 access points in total.
on 2.4 GHz they have the channels 1,6 and 11.
on 5 GHz they have the frequencies 5180, 5500 and 5540.
I see 
, you are right on the convenience border between using or not using capsman:
http://forum.mikrotik.com/t/help-to-configure/173761/1
Nice SSID in that post. NoPain-NoGain 
It looks like he is using Capsman v1 which will not work on AX access points right?
My friends setup is working fine, but need some tweaking. I just want to verify the antenna_gain and min_antenna_gain is set correctly, but don’t know where to find it. Also /interface wifi print detail won’t show me.
Hi,
I have the same problem, radio power of mANTBox ax 15s est very poor, in comparison to what Mikrotik claims.
My old year 2016 indoor WiFi router Asus RT AC66U with 3 small antennas, from inside, transmits outdoor almost as far as the mANTBox ax 15s. See the tree http://forum.mikrotik.com/t/new-in-routeros-v7-15-3-especially-on-mantbox-ax-15s-i-have-troubles/177708/1
I wonder, if there are users who have purchased this product and can use it at distances of 100, 200,… 500m?
I echo these statements. Deployed mANTBox 15 ax to replace an existing “AC” Wifi5 Access point that took a lightning hit. The mANTBOx 15 AX is poor replacement.
Appears antenna-gain related issue with RouterOS
hello I have the same problem. Did you solve the problem?
Same issue here, 3 mantbox ax on a mast. Around the mast there is no ssid seen on devices. Only at longer distance (like 100m) you can see the ssid.
The mantboxes are managed by capsman. Annoying too is that you can’t even use channels without DFS, like 5180, it’s not accepted.
Compared to the old mantboxes, it’s a major disapointment…
Did anyone get it to work for like in a field on a campsite, or a citysquare. In other words, not only used with long distance routeros client devices?
Still issues here as well. Open ticket with MIkroTik. I have a SUP and they finally responded with some bullshit reply. There is an issue and they refuse to take it seriously.
For one of my customers in upstate NY I used these settings:
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:XX auto-mac=no comment=defconf name=bridge
/interface wifi
set [ find default-name=wifi1 ] channel.band=2ghz-ax .skip-dfs-channels=
10min-cac .width=20/40mhz configuration.country="United States" .mode=ap
.ssid=my-wifi .tx-chains=0,1 .tx-power=27 disabled=no
security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes
.passphrase=my-password
set [ find default-name=wifi2 ] channel.band=5ghz-ax .skip-dfs-channels=
10min-cac .width=20/40/80mhz configuration.country="United States" .mode=
ap .ssid=my-wifi .tx-chains=0,1 .tx-power=28 disabled=no
security.authentication-types=wpa2-psk,wpa3-psk .ft=yes .ft-over-ds=yes
.passphrase=my-password
I'm also in Upstate NY, lol =P.
per your config export, I do not use 20/40Mhz channel configuration on my setups. Only 20Mhz for 2Ghz frequency, and I'm not manually setting tx power.
With you manually setting Tx power, have you had better success with the mantbox ax acting as an access point?
As you know I have been forced to work with caps-man for about a month now.
Here is what has been working the best so far.
You have to go into the interfaces and tell the 2.4 radio to use the 2.4 profile and like wise for the 5.
/interface wifi channel
add band=2ghz-ax disabled=no frequency=2412,2437,2462 name="USA 2.4" width=20mhz
add band=5ghz-ax disabled=no frequency=5180,5745 name="USA 5.0" width=20/40/80mhz
This forces the radios to scan and then pick from the listed channels.
Good to see you post @gotsprings. We've been slowly joining you and transitioning to "greener" [less trouble] pastures over to the 'Bium' side.
Interesting that you're manually specifying channel frequencies at the provisioned CAP interface from the CAPsMAN server level. Are you noticing the frequencies are NOT being applied from the provisioning profiles?
I have these frequencies defined for the customers provisioning profiles. We have CAPsMAN deployed for a few customers, but chomping at the opportunities to migrate away....
This mANTBox AX that replaced a failed AC from a lightning hit - and the performance & range has been poor. I will mess with setting manual frequencies. Although, this customer [campground] we're working on project to replace all the 'Tiks for another vendor.
I set the channels that it could pick. I don't go in and set the specific channels anymore. Those 2 profiles let the APs pick USEABLE channels and I have not seen them overlap in the last few weeks.
In reality, this integrated antenna or sector model is designed for multipoints, but with CPE client equipment, not for end devices. I see more benefits and advantages in using it for CP multipoints. A clear example is that your friend is below the sector and has a poor signal, and that is a response to the technology you have implemented.