Thanks for the knowledge. From what you say, it sounds like anything I set up in the bridge should be deselected in xplane so there are no conflicts. Those not selected in the bridge can be set in Xplane. I agree that probably the best is to start clean again. I do have lua scripts for the radios and I did have a script for the autopilot. Then I used some of the profiles for honeycomb so I see how it might be a mix now.
(Which is why I'm not sure what "no 8 and 9 levers (T. Reverse)" means.) On the xplane settings for the honeycomb throttle quadrant, the thrust reverse levers are labeled spot 8 and spot 9. I set those for full on thrust reverse when the levers are pulled to the on position. They both perform this action now so the only issue is the jiggle at low n1 which is easy to avoid for now.
One new question if I may? Flying into John Wayne today, I found my course on final showed up as 360 instead of 196 degrees. What I found out the hard way was the left selector switch on my honeycomb autopilot when set to CRS does not change the course setting. All the other options work great. I duplicated on my next flight to be sure. I can change the course with the mouse using the knob in the simulator but not using the button on my honeycomb. Xplane doesn't even address that button at all. Can that be assigned in the configurator?
My guess is a reset from a clean start may fix all these. Just trying to understand which codes take priority so I can avoid conflicts. You have been a big help. Sometimes it can be frustrating but I am having a ball learning how to integrate all the systems. I am even starting to feel comfortable flying around. Flew KPSP to KSNA and back today on PilotEdge. Thanks.