PoE in itself is a nightmare, due to the complexity of the “standard” and the (slightly) different way each device manufacturer/vendor implements them (differently if not wrongly).
PoE in Mikrotik is a worse nightmare, as different models have different characteristics (active 802.3af or at or passive) and for some reasons they use mode B while many other vendors use mode A, then there are current (in the sense of Ampere) limitations, you need to study a lot before being able to have a working solution unless all devices are Mikrotik (and even then …).
The Ax2 and Ax3, namely, are low voltage (max 28 V) and passive only.
The allowed output current is limited to 600 or 625 mA, which at 24V are 14-15W, enough only for a camera or a simple access point.
This isn’t limited to Mikrotik - Ubquiti was in the same boat with older Unifi devices. Passive PoE was introduced to reduce complexity and therefore cost. That cost saving might not stack up these days.
Noone said that it was exclusively Mikrotik, as a matter of fact the passive, low voltage, approach - when suitable - is (IMHO) easier to deal with than having to fight against the different implementations of 802.3af and at by different vendors.
Isn’t that always the case I had a very weird problem with a CSS106-1G-4P-1S (SwOS) recently. It was supplying PoE to a UISP Nanostation Loco 5AC, part of a short P2P bridge. It had worked flawlessly for several years until about two weeks ago when the access point end (hard wired to RB40111 router via that switch) started dropping packets randomly. EMCO Ping Monitor showed fine for 10 minutes then big packet loss. It’s currently bypassing the CSS106 and is working fine. But it took me hours to pin it down to the switch as, you know, switches just work Lesson learnt! I digress..
In my case I use HP or Aruba switches and I use them to power all kinds of devices (telephones, APs of different make including MikroTik) and I
have never seen issues. So it looks like the problems are limited to MikroTik switches powering other things, not the reverse.
I activated both the 2GHZ and the 5 GHZ on my AX2, when watching videos etc, seems that everyone is always only activating the 2 GHZ wifi ? probabaly just for demo reasons?
In any case if the 5GHZ can pump out 700 MB why have both active and not just leave this one?
Because as you move in your place or as obstacles come in the way between your client and AP, that 5GHz signal might quite fast become unstable.
And then 2.4GHz might still be used perfectly.
To sum it up:
2.4 GHz sucks (because it is slow and - in densely populated areas - polluted by countless conflicting radios).
5 GHz sucks even more because it won’t go through walls (or any other thing thicker than a sheet of paper) and let’s not forget the real or fake radar interferences, 10 minutes cac’s, etc., so it will work (fast enough) or not work.
A candle (in the wind) vs. a blinking light, compare with the light of the sun (a good ethernet cabled connection).
Since you are Italian, “Se sei bello ti tirano le pietre, se sei brutto ti tirano le pletre”. (for non-italian readers, this was an old song, translatable to “they throw stones at you, no matter if you are ugly or beautiful”).
did some more testing in the room behind where the AX2 is sitting seemed to get full signal on both 2GHZ and 5 GHZright now 2 GHZ is pushing about 150 MB 5 GHZ is pushing 350 MB
2.4 GHz sucks (because it is slow and - in densely populated areas - polluted by countless conflicting radios).
This depends upon your definition of slow. Many UK consumers are still on fibre-to-the-cabinet where the maximum you’ll ever get is 80Mbps. My hAP ax2 with Wi-Fi 6 devices can get ~120Mbps which isn’t bad. Office use is a different beast though.
Slow is defined (in my personal dictionary) as something that makes something else underperform, everything Is relative.
I see your many UK users and.raise with many italian users that get with FTTC “target” 30 MB, actual 20-25MB.
Meanwhile, in many cities there is available FTTH with 300/500/1000 guaranteed bandwidth (in download).
Now, if you have an ethernet cabling at 10 MB and have a 20 MB internet connections your network Is slow.
But as well an ethernet cabling at 100 MB with a 500 or 1000 MB internet connections is slow.
If you have a GB ethernet cabling, a 1000 MB FTTH and you use WiFi capable of 100/120, your WiFi Is slow.
The fact that is fast enough for facebook, lolcats and porn doesn’t change its classification as “slow”.
I had a very weird problem with a CSS106-1G-4P-1S (SwOS) recently. It was supplying PoE to a UISP Nanostation Loco 5AC, part of a short P2P bridge. It had worked flawlessly for several years until about two weeks ago when the access point end (hard wired to RB40111 router via that switch) started dropping packets randomly. EMCO Ping Monitor showed fine for 10 minutes then big packet loss. It’s currently bypassing the CSS106 and is working fine. But it took me hours to pin it down to the switch as, you know, switches just work 
Lesson learnt! I digress..
doesn’t change its classification as “slow”.
