Main Panel DU

[mvr1918]

Looks like a SIOC issue and not a Oi4FS issue. Probably a timing issue that causes it.

SIOC Monitor gives correct data, but the script "sees" something else, based on data from the SIOC server.


If not already done:

Try to change the Oi4Fs.ini line MIP,IDX31m2 to MIP,IDX31m1
and also the line
MASTER=31,4,2,xx to MASTER=31,4,1,xx( xx should not be changed)

[biggstuff]

Hello Roar
Sorry for the delay in responding. I was away for a bit.
I made the changes suggested in the Oi4Fs.ini [MIP,IDX31m1] and the PMDG B737.ini [MASTER=31,4,1,70] and the results did not change.
I start the software and the virtual cockpit knobs move and doesn't match the actual MIP positions.
Also I reliased after a did a figt that the CAPT MAIN PANEL DU kept moving from NORM to MFD any time the power conditions changes. Like if I change BUSS from STANDBY to APU it would change etc. Cut power from ENGINE BUSS to APU would change and vice versa.
Any other suggestions to try?

[biggstuff]

So something interesting happened today.
Took a flight and before I turned Oi4FS on, I turned my MIP CAPT MAIN DU to MFD.
I proceeded like I always do, turn on Oi4FS and power on the aircraft etc.
Guess what the virtual cockpit Capt. DU remained on NORM as well as every DU knob for CAPT and F/O stayed on NORM
It did not move about like it did previously when I initialize my flight with the MIP DUs on NORM.
However immediately I moved the MIP CAPT MAIN DU from MFD to NORM, the virtual cockpit DUs started misbehaving again anytime I change buss power feed.
Could that help someone to help me.
I need help please!!

[mvr1918]

If you have a OC.log or OiPMDG737.log file in SIOC, delete the file.

Then start MSFS and Oi4FS as you normally do with the DU switches set to NORM.

After 30 secs, check the log file.
What is the text in the log file?

[biggstuff]

Hello Roar
I searched everywhere for the log file and I do not see it in the SIOC folder.

[mvr1918]

There should be a OC.log or OiPMDG737.log in SIOC folder if you search for it after the driver has started.

The file is deleted if you close the driver.

[biggstuff]

Hello Roar
Thanks for your response and help. Below is the log text after I put power to the aircraft. No log was generated before I put power.
Also worth noting that, this time after putting power, the knobs on the virtual cockpit stayed in the NORM position matching the MIP positon.

Edit- So after many attempts I found out this does not happen everytime. Not sure what condition is different to cause it to happen and other times not happen.
What is common though is that power buss changes causes the mismatch if it does happen.

OiPMDG737 1.2.0 Mon Oct 16 18:05:59 2023

18:05:59 Initialisation ...

18:05:59 Connecting to SIOC ...
18:05:59 Timed asynchronous connection attempt started...
18:05:59 Link established to SIOC server, HostAddress:127.0.0.1, port:8092
18:05:59 Winsock ready for write
18:05:59 Registering needed Control Vars at SIOC Server ...
18:06:09 Initial values of Control Vars received from SIOC Server.
18:06:09 SIOC Connected!

18:06:09 Running ...

[biggstuff]

Captured this today while the problem occurred seems to be the same as previously when the problem did not occur,
This happened when I turne ground power ON

OiPMDG737 1.2.0 Fri Oct 27 16:14:58 2023

16:14:58 Initialisation ...

16:14:58 Connecting to SIOC ...
16:14:58 Timed asynchronous connection attempt started...
16:14:58 Link established to SIOC server, HostAddress:127.0.0.1, port:8092
16:14:58 Winsock ready for write
16:14:58 Registering needed Control Vars at SIOC Server ...
16:15:02 Initial values of Control Vars received from SIOC Server.
16:15:02 SIOC Connected!

16:15:02 Running ...

[ronnev]

Hi.
I have the same problem.
CPT + FO Main DU and ND changes and my N1 goes to "2".

Dual MIP here as well.

[biggstuff]

Does your mismatch also only happen when your BUSS condition changes?
Mine always seems to match perfectly untill I say turn Ground Power on BUSS or APU BUSS etc.
What N1 are you refering to that changes to 2?