Choosing SOI (Sensor of Interest)

[yonyz]

Hi,

 

I've tried different ways to removing the "NOT SOI" message on both MFCDs.

I long-pressed H, K too, and I pressed the different MFCD buttons, including TAD and TGP, and which both show the "NOT SOI" message. So how do I REALLY choose a SOI?

[Zenra]

Without HOTAS, press the desired mode button, or its keyboard equivalent, a second time to make it the SOI.

[AlphaOneSix]

I'd go into the controls config and double check that H and K are really set to Coolie Hat Left and Coolie Hat Right. Also, for your long press, make sure it's at least 1 second, although I'm sure you're already doing that.

 

When using the buttons along the MFCD to make SOI, press the corresponding button on the MFCD a second time. That is, if you want TGP to be SOI, press TGP along the bottom of the MFCD to put the TGP page on that MFCD, then press the TGP button again to make it SOI.

 

If none of that works for you, then there are other problems. ;)

[rob10]

Your long H or K press should set the sensor currently active in that MFCD as SOI. Realize that you can only set one sensor as SOI at once, so you will always have at least one MFCD with that message unless you have the same sensor up on both of them. If you still can't get it to show 1st thing would be to check your binding in the options menu and make sure you have H and K set up properly.

[yonyz]

I didn't check the controls options, but I can see the Coolie Hat moving when I use the aforementioned keys. Those keys do change the page on the MFCDs, but they don't set either as the SOI.

 

Also, pressing the TGP again after it's shown only flashes the video.

[nomdeplume]

You say it flashes the video so I guess you've already set it to A-G or A-A mode, but I figure I'll double-check just in case ... it won't be able to be set as SOI if it's in standby or off.

 

Maybe try swapping the displays (coolie hat down short) - I've had that fix some really weird problem I was having with one of the MFCDs once.

 

If you could post a track then we can narrow it down to either a strange aircraft configuration or a problem with it reacting to your particular controls configuration.

[Frostiken]

You can't set anything as an SOI if you're not aligned and in NAV mode (because the A/C doesn't know how to correlate anything).

[yonyz]

I think you're onto something, Frostiken. "INS NAV RDY" is flashing on that small green screen on the right console (CDU?). Does it say anything to you?

[159th_Viper]

Does it say anything to you?

 

It means that you must now press the NAV LSK to place the INS out of alignment mode and into navigation mode.

[Frostiken]

As I suspected :)

 

I found this out myself when I was trying to whirl my TPod around and test a few things. Was wondering why it wouldn't work, but since SOIs are typically to correlate nav data between sensors, it makes sense that in absence of even knowing where your own aircraft is, there wouldn't be a point in having an SOI.

 

So yes, as mentioned, you have to be in Nav mode. I doubt you have to have aligned all the way, but always, always make sure it's reading 4.0 0.8 before you go into nav mode, as that's the best alignment you can do. Don't move your aircraft until then! Many newbies have problems because they jump the gun and skip through alignment, and then wonder why they can't engage EAC :p