I’m currently testing the hAP ac² and I’m having the same issues as described here with the cAP ac. It uses the same chipset.
TX throughput is under 10 Mbit/s, wAP ac is working fine in the same environment. Client is an Intel AC 8265. RouterOS 6.42rc41 seems to fix the issues with 2.4 Ghz but crashes when I test with 5 Ghz.
Configman and 3x wAP - all great. TX up 100mbit/s depending on the quality signal
This same config in configman and connected only new 3x cAP (tyhsi same metod, vlan for capsman) - Tx under 10mbit/s when -49dB quality.
Not good.
Support whats going one ?
Capsman, wAP and cAP in version 6.41.2 and this same firmware version.
I’m buy full product, and used original current software. This product should not be allowed to sell before specific tests
I often test(6.42rc43) that DOWNLOAD is less than UPLOAD (about 5 meters in distance) on IPHONE 6. Is the TX POWER of CAP AC smaller than IPHONE 6?
What is the cap ac TX POWER?
If compared with WAP AC, the CAP AC coverage is much smaller.
It should be evident from this thread that there are serious issues with CAP AC right now, I would advise not purchasing until stable firmware and RouterOS are released that fixes everything. In theory CAP AC should be about the same performance-wise (or better) as the WAP AC due to the newer high speed IPQ4018 chipset and Wave2 wireless support (even if not yet enabled). It does have one less chain on 5 GHz, but devices that can make use of all three spatial streams are very rare (often only Macbooks).
This is one of the first devices Mikrotik have made using the IPQ4018 so it’s expected that there are some issues moving to a completely new platform. I expect they can all be fixed with software as the IPQ4018 is a popular chipset already in use by many other devices such as ASUS and Neatgear consumer routers. The IPQ4018 chipset itself is from 2016 so it should be well-established in terms of hardware and Linux kernel driver support.
cAP AC arrived last night. Dropped it right in place where the wAP AC has been sitting for the past week. Updated to CURRENT packages. Set it to Caps-Man, matched the channels to what I had used on the other WAPs. Looks like I am getting an average of 189M using local forwarding.
100M SLOWER than the wAP AC (289M).
220M slower than the UniF–k AC Pro (420M)
400M slower than the Ruckus R510 (605M)
So bummed right now.
Interestingly… I am noticing a bunch of disconnects from a 2.4 device when connected to the cAP AC. Switched back to the wAP AC and its now solid again. Will run it over night and look at the log.
I have a Macbook Pro right here, and can get 500Mbit easy. Please send your Supout.rif file to support@mikrotik.com, make the file during the Speedtest