March 11, 20206 yr Hi, I just noticed in SOP1, when 2nd engine (normally ENG1) started, FO will select SYS on Lower DU and start overhead flow Right after the starter cutout, meanwhile engine is still accelerating to idle. In our company (And boeing's FCOM), engine start is ended after the start limit EGT line (725C) disappear (We will call "Engine stable", but not by FCOM). It's about 5 second after start cutout. So I still need to monitor the OIL PRESS on lower DU at that time, thus the current setting is a little bit annoying. Not a big deal, but if it could be fixed.
March 11, 20206 yr Commercial Member We can't control the lower screen very well. That's the problem. We're hoping PMDG updates the SDK so we can control it better. Right now the FO is very "blind" when it comes to the lower screen. Best, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
March 12, 20206 yr Author In this case, the lower DU control is not the problem, the sequence of event is correct, just the timing is too soon. While it's best to "see" if the EGT start line is gone, if that can't be done, wait 5 second after starter cutout is good enogh for normal opreation. BTW I found that even PMDG itself is "blindly" cycle through the lower DU, when a lower DU warning event occur (IRL, the lower DU will come on when somthing going on with engine parameter, but in PMDG now, it will shut off when it's already on), I've already submit ticket to PMDG, wait how they'll fix that then.... Edited March 12, 20206 yr by C2615
March 12, 20206 yr Commercial Member Thanks for the feedback 🙂 We'll see what we can do. But what really need is PMDG to allow us to directly set the Lower Screen... then we can do anything 🙂 B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Archived
This topic is now archived and is closed to further replies.