Hi sir, I am sorry I haven’t responded due to not knowing you responded. I have a happy conclusion to our issue.
The problem ended up being multiple LRUs failing at the same time. This is why no box swap or mock up change out helped us narrow it down.
We found that we had a bad Acceleration sensor, mode coupler, and mode selector. The acceleration sensor was causing the rising command bars AND a computer flag only on the pilots ADI (odd). The #1 mode selector was also causing a intermittent computer flag. On top of all of that, the pilots mode selector Altitude hold would disengage intermittently causing vertical monitor signal errors.
The herk is at Youngstown Air Reserve station. To answer your other questions because you took the time out of your day to write me, our swaps were including supply parts, aircraft parts, parts from other aircraft, and back shop mock ups. This particular plane has had FD109 demons for roughly 20 years (usually involving the #1 side of the system. The altitude hold information does come from the Air Data Controllers, and there is one for each side of flight director. This issue started while I was with the plane in a deployed location early this year after the plane had AC bus issues. The 34GS is basically worthless. I used the WDs (formally known as the 13s) to finally figure this one out. It was especially difficult due to how many parts of flight director receive or input the vertical monitor, and vertical fail signals.
I appreciate you looking into TOs, and using all the right verbiage obviously showing you know your stuff. We were on the same track the whole time.