Originally Posted by
groundbum
as an IT engineer this changing from flip-flop to dual reduandancy is massive, and unless work started years ago will NOT be ready for September. And if it has been rushed then it needs full end to end testing as it's such a fundamental change. There's a philosophy in coding that for every 2 things you fix, you break something else. It's the nature of the beast.
G
Agreed.
The big unknown is, if there is a code baseline which incorporates this feature (e.g. from other projects) and does only need to be configured for the 737 and built. Sill can't see when the validation should take place. Certification must not replace validation .
Highly dubious schedule.
Edit:
From the originial fault description - AP disconnect sluggish after one of two uC faulted in a FCC, this does not sound like a fix to the actual problem ... now they let the second FCC take over. I'm not so much impressed. Not that I think that architecture change is not a leap forward but for the specific problem it seems like curing symptoms.