Almost immediately, I got a (Obs avoidance failed. Error). I know the H920+ doesn’t have obstacle avoidance, so I wasn’t concerned.
I tend to agree. I don't have an H920+ to compare, so I selected an H920 model and a CG04 on an ST16, then bound the ST16 to a Q500 (which also does not have OBS). I got the same OBS failure indications. Not 100% conclusive, but it tends to agree with your opinion that the indication is normal.
But there is an interesting caveat to that. When the drone is not powered on, the OBS alarm is not present. This seems important. It suggests (that at least at some level) your controller is actually already bound to the H920. Or at least somehow communicating with the OBS. YOU CAN TEST THIS THEORY BY OBSERVING IF THE OBS FAILURE IS ONLY PRESENT WHEN THE H920 IS POWERED ON. A contradiction to this line of thought is that your screenshots are not showing any telemetry. If it were bound, the telemetry should be there. (Yeah, I'm confused.)
View attachment 28117
When I verified the Hardware Monitor, all of the switches and dials worked except the T1 & T2 (They didn’t have full range, only the little I photographed.)
I think that's normal. Mine's the same way.
View attachment 28118
The CGO4 spun in a 360 circle, as if it was initializing, sometimes it would say it was binding, other times not.
Do you mean the actual camera was spinning? If the actual camera was spinning, it might mean something. Some clarification. If the actual CGo4 is spinning, it's from the gimbal part of the CGo4, not from the camera part of the CGo4. The CGo4 Gimbal is part of the SR24xxx binding, not the camera binding. But no, it's probably not supposed to be spinning. At least it doesn't on the other H series models I'm familiar with. We might need to look at that in more detail later. If you meant something else was spinning, none of this applies.
Checked the SR24 to see if the yellow light flashed faster after the tipping… it did.
Sometimes the SR24xxxx would appear, other times not.
Another clarification might be in order. We tend to think of the binding as being between the ST16 and the drone. I'm pretty sure that's not exactly accurate. I believe the control signal (2.4Ghz) binding is actually between the ST16 and the SR24xxx itself. In turn, the SR24xxx is bound to the drone via two of the four wires and requires no additional action from us. This is important because if I am correct, it may mean the problem is either in the SR24xxx or in the ST16. (Which contradicts another possible line of thought I will discuss later. Bummer.)
Even when the SR24xxxx and CGO4 were on the screen, and I initiated a BIND, the Status Lights still flashed white, red, blue, green.
The "White" you mention worries me. There is no white as part of any of the Red/Green/Blue sequences listed in the manual. Is the "white" a part of the same consistent sequence as the other three colors or does it flash somewhat out of step with the other three?
Also, the sequence (according to the manual), should be RED-GREEN-BLUE. Not RED-BLUE-GREEN.
Are you certain of the order of the colors?
The manual says the H920+ uses Red/Green/Blue to indicate low battery level, and it is also associated with accelerometer calibration. The H920 manual does NOT mention Red/Green/Blue during FC0 initialization, but earlier models, such as Q500, did. Which brings up another question. Way back in Post #5 you said, "
The top needed to have the three wires for each arm removed for the top to come off (plus the GPS cable.)". I believe you have assembled the H920+ again. Are ALL motor wires/GPS, and everything else correctly connected now?
Back to the "line of thought I will discuss later"; I think you currently have the new FC0 module installed. Is there any difference in LED (W/R/G/B) light sequence between the old and new FC0? Is there any chance the two FC0s got mixed up on the work bench, and you inadvertently reinstalled the original? (Don't laugh. I've done that.)