You may give a try to switching the communications to manual, select a particular band and pick a channel that is relatively quiet at the of takeoff. Then fly out and see if it maintains that connection.
It looks like the
M3 folks have even more issues with the
SC Pro connection. I am not sure exactly what the "+" stands for in Ocusync 3+ but that is presumably the main difference between using the Pro with the
A2s vs the
M3. It may well be that the "+" stands for the extra band or whatever. If that is so, it simply may exacerbate the band switching issues between controller and aircraft. There has to be either some type of interactive handoff to synchronize (would require connection of course) or some arbitrary "independent rotate frequencies and bands and try selecting quiet bands (carefully since quiescence would be different for controller and aircraft at distance)" executed on both sides and stop when the connection is re-established. Maybe there is some "master/slave" aspect to this too. I remember a couple of years ago with the
M2P and the
DJI Goggles where the
M2P required to maintain 2 independent connections with different communication issues. That was a real mess until they finally fixed it. Most likely by coordinating with a master (aircraft possibly). Until DJI fixed that problem I simply forced one band with manual selection. That worked pretty well.