450v 4x4 AP - EIRP when using 1carrier/2component vs 2carrier/1component

Hi,

We’ve noticed that, even when both component carries are authorized for 36dBm EIRP by the AFC, when using the single carrier / 2 component configuration the AP EIRP is limited to 33dBm. When switching back to 2 carriers with a single component each, it transmits at full 36dBm. Is this expected behavior? We are on release 24.2

Here is the ap in question:

Here’s the afc page, showing 36dBm transmit allowed

Why tho?

Hello,
In the 1 carrier/2CC case, that 33 dBm display actually means that each component carrier is transmitting at 33 dBm, for a combined power of 36 dBm in this carrier. I can see how this could be confusing, and I’ll admit our existing documentation is not entirely clear on this. So I’m going to go ahead and submit some clarifications to our PMP Configuration Guide. We posted a new version just today with our 24.2.1 release, but look for another version with these clarifications in the “Viewing General Status” section of that guide either tomorrow or Monday. Sorry we hadn’t made that clear before.

In regards to your observation that when switching to 2 carriers with a single component carrier each you see 36, you must have had those 2 carriers in seperate subbands, correct? I mean to say, you must have had 1 carrier in 5.8GHz, and another in UNI-7, or maybe 1 carrier, in UNI-5 and another in UNI-7, etc, then you could potentially see 36 dBm / 36 dBm. If instead you had both carriers configured in the same subband, then you would have seen at most 33 dBm / 33 dBm to restrict you to a total of 36 dBm for the subband.

3 Likes

Thank you, this is very informative

I realize I had a typo in the first line of my response. It should have read “In the 1 carrier/2CC case, that 33 dBm…” Notice I have corrected that just now in my old response. Looks like you read between the lines and understood what I was trying to say anyways. Note also that some discussion about some actual code changes to better handle/display this particular scenario to avoid such confusion - still under discussion. But we will update the documentation if/when that happens - and I’ll try to update this post as well at that time.

2 Likes

Yes, we understood what you meant :smiley:. Thank you for getting this pushed up the line to clear up potential confusion!