IRS messages with FS2Crew

[IanHarrison 522]

I am using FS2Crew with the QOTSII. 

Despite having all the latest updates for both, I repeatedly get the dreaded "Split IRS/No land 3" messages.

It seems to have no effect on the plane as it still auto lands perfectly with 3 A/P lights lit.

FS2Crew don't have an answer and have asked if PMDG can indicate what could give rise to this error.

Ian Harrison

[Olympic260 415]

2 hours ago, IanHarrison said:

I am using FS2Crew with the QOTSII. 

Despite having all the latest updates for both, I repeatedly get the dreaded "Split IRS/No land 3" messages.

It seems to have no effect on the plane as it still auto lands perfectly with 3 A/P lights lit.

FS2Crew don't have an answer and have asked if PMDG can indicate what could give rise to this error.

Ian Harrison

Ian,

 

If you fly the plane without Fs2Crew does it still happen?

[IanHarrison 522]

Will try and see what happens.

[scandinavian13 5,192]

6 hours ago, IanHarrison said:

It seems to have no effect on the plane as it still auto lands perfectly with 3 A/P lights lit.

For what it's worth, yes, it will still "work." It's not autolanding, though. It's simply flying the airplane into the ground. You can do the same thing in the default Cessna. That isn't an autoland. That's misusing the APP function.

6 hours ago, IanHarrison said:

Despite having all the latest updates for both, I repeatedly get the dreaded "Split IRS/No land 3" messages.

Willing to bet that you're using a particular FS2Crew flow/SOP/etc that asks you to do certain things that you are not doing.

That or your panel state is out of sorts.

[WotanUK 289]

I have noticed this myself today flying from EGLL to KDEN.  It seemed to occur as fs2crew switched from apu to gen, the center screen and right cdu switched off, i got an error saying "Rudder ratio" and the No Land 3 message.  I didn't chance the autoland and everything was fine.  I don't get this when i am doing everything myself...

Edited March 30, 2018 by WotanUK

[scandinavian13 5,192]

31 minutes ago, WotanUK said:

I don't get this when i am doing everything myself...

Again - look at their SOP and check for an action you think they're doing for you, but likely aren't. Something's out of position that you're overlooking because I think you're assuming they're taking care of it.

[IanHarrison 522]

Good suggestion! That does seem the most likely. Will try to monitor everything happening next week after Easter is past.

[WotanUK 289]

9 hours ago, scandinavian13 said:

Again - look at their SOP and check for an action you think they're doing for you, but likely aren't. Something's out of position that you're overlooking because I think you're assuming they're taking care of it.

Not sure you are correct...  I actually think it's because the FS2Crew application tries to transfer the load from the APU to the GEN before engines 1&2 are fully ready.  Either way, i am sure it's not a fault with the Aircraft.

[elButz 1]

I had this once because FS2Crew cut the ground power before the APU generator was available... make sure to start the APU at least 5min before the FS2Crew departure and activate at least one APU generator, handling between APU generators and engine generators should work fine if you follow the SOP specific manual.

[IanHarrison 522]

OK I think I have found it. After watching what happens, it is the APU being shut off while engines 1 and 2 are still starting. When the APU is turned on manually and left on, there is no problem. It seems as if the IRS's take their power from different sources.

I will put this on FS2Crew forum.