Today I had a 2 hour remote session with TP-Link senior engineer and their RD department testing the Routers communication with the Quest 3 headset...

Here is what they found...

--------------------

Hi there,

We just managed to change the wireless negotiation rate and try to contrast with turning off the potential related Wi-Fi 6e function like MU-MIMO or txbf, and it seems not helped a lot.

It's the case with Quest3's negotiation MCS. It only reaches MCS7 when receiving signals from the router, then for sending signals, it reaches MCS5 only.

After trying to change channel and adjust wireless function, it still only randomly gets MCS9 negotiation, even in a short distance, at which it should have full speed and MCS 11 without any issue.

So what we can push from our side next is that our RD team will manage to communicate together to see if we have more methods to change the wireless parameter from the router side for the Quest3 later, then they will come back later if they have more clue about it.

Then we also need to check with the Meta like you already did. You can add my email to the contact with Meta/Oculus, I will help check what they are replying to and tell them what we found here.
From what we got here, either it's the Quest3's wireless adapter unstable, or it's the case that the quest3 is having compatibility issues with the AXE75's BCM wireless chipset .

The BCM wireless chipset is the most common one in the world for routers, and the one used in AXE75 is also used with a lot of different routers... So far we've tested with phones like Samsung S21U, S22U, S23U, Oppo find, xiaomi 13, for the phone which support 6G, they are working fine with the AXE75 according to our test.

The Quest3 are using XR2 Gen2, which is basically the Snapdragon 8 Gen2, they should be all using the Qualcomm FastConnect wireless chipset. We will also try to check deeper to see if we can find out which wireless chipset that they are using on the Quest3,so we can find a similar one for repeating first. and contrast the wireless negotiation status to see if we can find further clues.

BTW, if our RD got a new idea about the quest3's negotiation rate, we will need to have remote access again to double check it. and I will let you know by email.

so that should be all for today and what we got, and what we are going to do next

-------------

(To be clear I am still running version 57 as 59 still has not been pushed to my unit)