I'd like to get an MCP/EFIS for the NGX.  Can anyone comment on their experience with either of these companies equipment and how well it works(or doesn't) with the NGX?

 

I use Opus and I know they include the CPFlight driver so that would probably be the "easiest" solution as far as set up goes from what I can tell.  No dealing with SIOC.  But, it's also another $300 more(CPFlight EL version) than OC.

I'd like to get an MCP/EFIS for the NGX.  Can anyone comment on their experience with either of these companies equipment and how well it works(or doesn't) with the NGX?

 

I use Opus and I know they include the CPFlight driver so that would probably be the "easiest" solution as far as set up goes from what I can tell.  No dealing with SIOC.  But, it's also another $300 more(CPFlight EL version) than OC.

Hi,

 

Have a look here http://www.flightsim4fun.com

 

 

Both MCP and EFIS work as plug&Play devices with the OC4BA software ( freeware). No need to understand SIOC scripting. The OpenCockpits MCP and EFIS ( together with other modules) are of good quality and have all features as the origninal ones.

 

They can also be used with the new T7 when the SDK is released.

 

rgs

I'd add my recommendation to roarkr's. I have the OC EFIS, MCP and CDU, all work well and accurately and roarkr's software makes the whole deal pretty easy ... very easy after the setup phase.

Thanks for your replies.  I was pretty sure there wouldn't be any problems.  I've seen a couple videos on youtube and it looks to work fine.  So, I just went ahead and ordered them! 

I'd add my recommendation to roarkr's. I have the OC EFIS, MCP and CDU, all work well and accurately and roarkr's software makes the whole deal pretty easy ... very easy after the setup phase.

John, can you provide any info on how you got the MCP/EFIS working with the NGX? I have followed the "tutorial" as best I can for the OC4BA but I can't get these modules to work. The OCP4B737 Manager shows them both active but I power up the NGX and nothing. I"m sure I must be missing something but not sure what.

 

Any help from anyone would be much appreciated...I'll continue searching the web in the mean time.

 

Thanks!

John, can you provide any info on how you got the MCP/EFIS working with the NGX? I have followed the "tutorial" as best I can for the OC4BA but I can't get these modules to work. The OCP4B737 Manager shows them both active but I power up the NGX and nothing. I"m sure I must be missing something but not sure what.

 

Any help from anyone would be much appreciated...I'll continue searching the web in the mean time.

 

Thanks!

 

Hi klamal

 

Good on you, you made the right choice for the hardware

Now, what might be wrong - could be a number of things, I'll mention some that tripped me along the way.

And Roar has his own support forum now at http://www.flightsim4fun.com/Forum/

 

Both MCP and EFIS each need their own 5v power supply.

 

For me the automatic setup never gets the text of the [MASTER] section of the sioc.ini correct, for me it should read as ;

MASTER=5,5,1,84

MASTER=7,7,1,86

Those last numbers of each line will be different for you.

 

Sioc.ini file must be in the main SIOC folder wherever it is and whatever it's called. Near the top of the sioc.ini file there's an entry

 CONFIG_FILE=   , for me it's CONFIG_FILE=.\OCP4NGX_V2.ssi   it needs to be a 'relative path' to your '.ssi' file.

 

Last but not least, with everything turned on, when you load into the NGX wait until the NGX initialisation countdown has completed then on the MCP hardware press the C/O button (near the A/T ARM switch). If you are 'cold and dark' not much may appear to happen until you power up the aircraft. 

 

One or more of those thing may have given you an 'aaah ha' moment, which would be good, but maybe not, getting it all to work the first time is bit of a juggling act, but once you start to understand how all the bits of software and hardware work together it's a synch.

 

If you are still getting no joy, go to Roar's support forum , he is very helpful and will 'get it working' for you probably by writing your sioc.ini for you.

 

In desperation I could lead you though it on TeamSpeak3 or such.

 

Good Luck

John   

Hi klamal

 

Good on you, you made the right choice for the hardware

Now, what might be wrong - could be a number of things, I'll mention some that tripped me along the way.

And Roar has his own support forum now at http://www.flightsim4fun.com/Forum/

 

Both MCP and EFIS each need their own 5v power supply.

 

For me the automatic setup never gets the text of the [MASTER] section of the sioc.ini correct, for me it should read as ;

MASTER=5,5,1,84

MASTER=7,7,1,86

Those last numbers of each line will be different for you.

 

Sioc.ini file must be in the main SIOC folder wherever it is and whatever it's called. Near the top of the sioc.ini file there's an entry

 CONFIG_FILE=   , for me it's CONFIG_FILE=.\OCP4NGX_V2.ssi   it needs to be a 'relative path' to your '.ssi' file.

 

Last but not least, with everything turned on, when you load into the NGX wait until the NGX initialisation countdown has completed then on the MCP hardware press the C/O button (near the A/T ARM switch). If you are 'cold and dark' not much may appear to happen until you power up the aircraft. 

 

One or more of those thing may have given you an 'aaah ha' moment, which would be good, but maybe not, getting it all to work the first time is bit of a juggling act, but once you start to understand how all the bits of software and hardware work together it's a synch.

 

If you are still getting no joy, go to Roar's support forum , he is very helpful and will 'get it working' for you probably by writing your sioc.ini for you.

 

In desperation I could lead you though it on TeamSpeak3 or such.

 

Good Luck

John

Thanks, John!! Do you have the v3 MCP? I haven't gotten it to work with the OCP4NGX stuff. When I run the AutoConfig, it totally messes up my sioc.ini file. There's nothing in it when I'm done but the two MASTER lines for my MCP and EFIS and a line above that containing [** and that's it. Needless to say, that doesn't work. I'm not sure why.

 

I actually did manage to get it working though using LUA scripts from the opencockpits website and compiling my own ssi from their NGX txt script provided. However, they must be for v2 as the SPD/ALT INTV buttons do not work. Everything else that I've tried so far does though so it's at least a good start.

 

I'm debating now if I should give the OCP4NGX stuff another shot or just go with what I got and edit the LUA stuff to get those buttons working.

 

One thing I do notice that is different in my current sioc.ini is the MASTER line for my MCP is different than yours. I have 15,15,1,23. I know the last number(23 in my case) will be different based on the USB port the PC is using for it. But, I wonder if 7,7 means v3? Or, maybe it won't make a difference unless I run it with OCP4NGX?

 

I'm going to head off to the forum link you provided too and see what I can find there...

One thing I do notice that is different in my current sioc.ini is the MASTER line for my MCP is different than yours. I have 15,15,1,23. I know the last number(23 in my case) will be different based on the USB port the PC is using for it. But, I wonder if 7,7 means v3? Or, maybe it won't make a difference unless I run it with OCP4NGX?

 

I'm going to head off to the forum link you provided too and see what I can find there...

Hi klamal

 

I have the MCP v2 which is the difference in the MASTER line.

Put a close bracket ]  at the end of the [**  line, that'll help. or better, make it  [MASTERS] it's just the section name.

When you can get the roar stuff to work that will be better than the lua files overall, so pursue that.

The MASTER lines and the rest of the sioc.ini is needed using OCP4NGX or anything else.

 

My whole sioc.ini is below

 

[sIOC]

IOCP_port=8092

IOCP_timeout=4000

Minimized=Yes

toggle_delay=20

CONFIG_FILE=.\OCP4NGX_V2.ssi

[iOCARDS MODULE]

IOCard_disable=No

IOCard_LPT=No

 

[FSUIPC MODULE]

FSUipcdisable=No

FSUipcRefresh=60

[iOCP CLIENTS MODULES]

IOCPini_delay= 3000

IOCPclient0_disable=no

IOCPclient0_host=localhost

IOCPclient0_port=8099

IOCPclient1_disable=yes

IOCPclient1_host=localhost

IOCPclient1_port=8092

[sOUND MODULE]

Sound_disable=Yes

Volume=100

[MASTERS]

MASTER=5,5,1,84

MASTER=7,7,1,86

Thanks so much for your help, John. Really appreciate it. I managed to get it working with the OCP4NGX stuff. And, now, my SPD/ALT INTV buttons work. Plus, everything seems to be more responsive and in sync than it was just using the LUA scripts.

 

I think my problem was not having the correct files in the right directory. I saw a post on the forums that said to copy the sioc.ini from the OC4BA folder into the main SIOC folder along with the NGX ssi file and 737Config.exe(not sure it's exact file name). I did that and then ran the OCP4NGX manager and did the AutoConfig and it works now!

 

Thanks again.

 and it works now!

 

Thanks again.

 

Hey that's good klamal.

 

Yes the OC 'lua scripts' were just earlier iterations of Roar's development process which led in the end to OCP4NGX.

Having 'all' the files in one folder makes for simpler pathing in the config files ... but a messier main folder. Which is no issue if you only use the hardware for one aircraft - the NGX. If you use the hardware with multiple aircraft having the multiple sioc scripts, one for each aircraft, in a separate folder makes them easier to find and tinker with, that's the only difference.    

Hey that's good klamal.

 

Yes the OC 'lua scripts' were just earlier iterations of Roar's development process which led in the end to OCP4NGX.

Having 'all' the files in one folder makes for simpler pathing in the config files ... but a messier main folder. Which is no issue if you only use the hardware for one aircraft - the NGX. If you use the hardware with multiple aircraft having the multiple sioc scripts, one for each aircraft, in a separate folder makes them easier to find and tinker with, that's the only difference.

What other aircraft do you use this with? And, how well does it work for those other aircraft?

 

Oh, I'm guessing you mean you just use SIOC with other aircraft. I was thinking you use the OpenCockpits MCP/EFIS with other aircraft. That's not what you meant, right?

What other aircraft do you use this with? And, how well does it work for those other aircraft?

 

Oh, I'm guessing you mean you just use SIOC with other aircraft. I was thinking you use the OpenCockpits MCP/EFIS with other aircraft. That's not what you meant, right?

Oh no, I use the MCP especially, with all sorts of aircraft.

Basically you can use it to control the auto pilot functions of pretty much most aircraft. From my 2nd fav seat, the Flight1 BN2 to whatever. Most aircraft, in particular the default FSX planes and most freeware just use the generic FSX keycodes and there's a generic sioc script file that you'll have got with your hardware that you can use for them. It's simply a matter of changing the CONFIG_FILE = setting in sioc.ini to point to the 'generic' .ssi/txt sioc file before you fire up the hardware.

More sophisticated payware is a bit trickier simply because there are more functions and controls than the basic FSX auto pilot abilities, but with a bit of google, the OC forums, and getting to understand the concepts of sioc scripting it'll work at least to some extent with just about anything. 

Oh no, I use the MCP especially, with all sorts of aircraft.

Basically you can use it to control the auto pilot functions of pretty much most aircraft. From my 2nd fav seat, the Flight1 BN2 to whatever. Most aircraft, in particular the default FSX planes and most freeware just use the generic FSX keycodes and there's a generic sioc script file that you'll have got with your hardware that you can use for them. It's simply a matter of changing the CONFIG_FILE = setting in sioc.ini to point to the 'generic' .ssi/txt sioc file before you fire up the hardware.

More sophisticated payware is a bit trickier simply because there are more functions and controls than the basic FSX auto pilot abilities, but with a bit of google, the OC forums, and getting to understand the concepts of sioc scripting it'll work at least to some extent with just about anything.

Sure. That would make sense. Do you know if it's possible to get any of the MCP/EFIS stuff working with Majestic's Q400? What about the Aerosoft Airbus Extended X? I'm off to the forums to see what I can find. But, if you have answers or known scripts that work with either of these, please let me know.

 

Thanks again for your time and your help!!!

First place I'd look is OC's forums, how's your Spanish ?  But sry I don't own either of those so ummm.