Oi4FS support

[mac228809]

Hi Roar,

I am trying to get my 3 modules running... MCPv3, EFISv2 and Airbus Radio.
On first install of Oi4FS I had my MCP up and running great, it did not have the EFIS or Airbus radio at that stage. I have had no luck with all 3 items connected
so I reverted back to The MCP only which I cannot get working now. I have attached a jpeg of my SIOC main screen and sioc.ini. Any help would be appreaciated.

Thank you, Brian.

[mvr1918]

Looking at your image and the configuration file(Sioc.ini) tells me that you have not configured your OC modules correctly.

Did you ever run the Configuration setup in Oi4FS?
The FS_MS Default.ini's MASTER lines should read as follows after a correct configuration

MASTER=15,15,1,84
MASTER=7,7,1,80
MASTER=8,12,1,82


It could be that you have the Airbus radio that creates your problem.

If you do not succeed in making a configuration file, make it manually with the MASTER lines above.

[mac228809]

I ran the Configuration setup as I did when I had the MCP working ok before but with no luck.
I also manually made changes to the Default.ini adding MASTER=15,15,1,84 and
MASTER=7,7,1,80 unfortunately no go!
I'm sure it's something simple however I just can't see what I am doing wrong.

[mvr1918]

If you have the same text in FS_MS default.ini as you have SIOC.ini you attached, the config is OK.


So what is the problem? What do you do next and what is not working?

[Splitpin]

Hello Roar again after many years.
Using MSFS, currently flying the default C208 in New Guinea which can be pretty challenging weather wise, which has motivated me to get my old OC MCPv2 hooked up again as chasing knobs and switches all over the VC with the mouse is awkward to say the least when they won't stay still long enough.
I bought Oi4FS months ago but only got motivated yesterday to set up and install hardware and Oi4FS. I passed those tests and it's mostly working fine. The only issue I'm having is with the Vert Speed readout. The up/down wheel is functioning and communicating with the sim but the readout mostly just shows ---- , sometimes numbers show but usually not what's happening in the sim - it'll say 400 or some random number when I'm climbing at 900fpm. So it's communicating but 'flakey'. Any ideas / suggestions.

Thanks
John

[mvr1918]

I just had a flight in the C208 and the MCP VS readouts are OK and sync'd to the Virtual VS.

You have the latest OiMS version v1.4.0.0 installed?

If you can provide me with a log output from SIOC's IOCPConsole when the VS issue occurs, I can look into it.

[Splitpin]

Re my VS issues

Yes OiMS 1.4.0 Mon Nov 9 07:59:42 2020 confirmed from top of OiMS.log

On the MCP I dialed up the ALT to 5000. Pressed the VS button. Rotated the VS wheel to show 400 up in the sim but hardware showed 00, pressed the VS button (off) hardware showed ----, pressed the VS button (on), now the hardware showed 400 (matching the sim).
I can now consistently replicate the behavior, the Vert Speed readout is not showing the value seen in the sim, pressing the V/S button off then on, forces a refresh of the Vert Speed readout and it then matches.
A possible difference between my setup and yours is I'm not running FSUIPC.

VS2.jpg (243.08 KiB) Viewed 2932 times

[mvr1918]

The IOCPConsole log data shows clearly that the output from the airplane to SIOC and the MCP is correct

Here button is pressed and confirmed by airplane
2064=1 - bVS
1264=1 - aVS

Here is output to MCP VS display
211=-999999 - D_VS4
210=-999999 - D_VS3
209=0 - D_VS
2064=0 - bVS
Should show 00

Here is changes to 100 fps
2044=-1 - ROTATOR_VS
2044=0 - ROTATOR_VS
210=1 - D_VS3
VS display should be updated

and so on

2044=-1 - ROTATOR_VS
2044=0 - ROTATOR_VS
210=2 - D_VS3
2044=-1 - ROTATOR_VS
2044=0 - ROTATOR_VS
210=3 - D_VS3
2044=-1 - ROTATOR_VS
2044=0 - ROTATOR_VS
210=4 - D_VS3

What causes your specific MCP not to respond to the data it gets from SIOC and driver I really do not know.

The only difference is that your MCP is an older model than the one I have, but I see no reasons for different behavior.



The FSUIPC has nothing to do with this.

Is there any other MCPv2 users that have the same issue?

[Splitpin]

Thanks for your reply mvr1918

My work around of flicking the V/S button off/on is not too onerous so it's not a big issue, just a little disappointing given that everything else seems to be working perfectly. Glad to hear that FSUIPC is not required.
Is there nothing I can do in the SIOC script (or elsewhere) to force that refresh? As that seems to be all that's required.

[mvr1918]

I looked into some MCPv2 issue topics in the forum here that were discussed some years ago and found out that are some issues with MCPv2 and the 3rd VS digit.

In MCPv2 modules, it looks like the 3rd VS digit will not update if it is the only digit that is changed. The reason for this, I believe is a hardware issue.

The way to try to solve this is to do the following:

Decompile the script and make a modification in the script so that when the 3rd digit(V210) is changed

- make the bVS(V2064) go on/off.

This will refresh all digits and the 3rd digit will be correct.