I hate night shift!!! Anyways....
Good stuff Gram!!! I'm dealing with about the same thing trying to eliminate every connection possible. Just hadn't had time to fly working 12's on a shutdown, but....
I'm expecting more from the Omni's because on
this flight, I went 14,000+ completely stock... and that's with a low powered GL300C. I realize that you (Gram) had much more interference to deal with, and, I haven't actually done a distance test run yet with the L-coms, (again, shutdown) but the L-com 8.5 dB should out do the stock 5 dB by a long shot in the same area. The data shows some weirdness in the logs... I didn't lose video one time in the flight, I turned around at the first glitch, but that was the only glitch. The other problem, was the GPS Atti thing.. but won't discuss here due to irrelevant to this thread.. Just saying I'm going to expect more, flying in the same spot of coarse.
It's cool to know how to make something work, like swapping cables with each other, as in, rx to tx or visa versa, but I always want to know why it helps. Just a thougt, if I have my rx and tx right, rx is on the right on remote, (holding it) and if the p4 is flying away from you, the tx is on the right leg throwing video back to the remote, same if the bird is flying back to you, so, the signals are never crossed. Video is always on right in the air, and control on the left. Makes me wonder if this is the difference when you swap cables. Maybe your first run, the signals were having to cross each other. I could be wrong, just trying to understand the "why".