@RR_NDB:
Unfortunately ADR 2 (RH PFD) is not recorded.
As mentioned in PAR 1.11.3 Interim report #3 the non-volatile memory in the salvaged computers
could give some more information.
From the FD engagement FDR traces and the information mentioned by HN39 (Page 44),
a little information about the status of ADR2 can be extracted.
(as far as I understand the sytems)
Before that one should know that a FMGEC needs at leats 2 valid ADR inputs to engage the FD.
-besides other AP/FD Common conditions -
Before @02:10:05 AP2 was engaged, this means (by engament logic)
FMGEC #2 was master, #1 was slave.
@02:10:05 AP drops off, Air speed of ADR 1 and ISIS(#3) are normal; FMGEC switchover is visible at the peak in FDR trace (FD2).
Suspect ADR 2 was the median speed at this time and lost (also due to other events at this time)
~02:10:10: Both FD (FMGEC) not available, also ADR#1 60Kts and ISIS(#3) 140Kts are to far apart.
~02:10:20: FD's available because ADR#1 and ISIS(#3) are nearly the same (but wrong) value 90Kts.
~02:10:25: FD's for a brief moment unavailable (although ADR#1 and ISIS(#3) are nearly equal (but wrong) at 110/100 Kts.
~02:10:30: FD's available, ADR#1 and ISIS(#3) in agreement (still wrong). Status ADR#2 (RH PFD unknown untill:
@02:10:40: There's a peak in both FD FDR traces, meaning they both switch over to
the other FMGEC, ADR#1 and ISIS(#3) are far apart, this means ADR(#2) must have been available again and its value in agreement with ADR(#1) = 215 Kts OR ISIS(#3) 120 Kts,
to become the 2 valid sources for FMGEC.
Unfortunally at that time they switch over to ADR#3 as faulty source for RH PFD!
From 02:10:47 untill 02:11:35 ADR#2 must have been available but not displayed on the RH PFD.
~02:11:45 the captain is entering the cockpit and would have seen 35 Kts on the LH PFD, 0 Kts on ISIS and SPEED FLAG on RH PFD.
After that all the speed indications where going up and down, FLAGS etc.