OpenCockpit EFIS software issue

[Gordon Turner]

Hello everybody,
I may be terminally stupid but I cannot get a recently purchased EFIS from Open Cockpits to interface with FSX. I have the MCP up and running, but when I plug in the EFIS it doesn't appear under the device heading as recognised. I have been in contact with the supplier but unfortunately his explanation has not been much help. I was advised to modify the SIOC.ini file (which I did) by adding a second line to identify the EFIS. This did not work. I am at then end of my tether on this. My programming skills are limited (but improving by the hour) and unfortunately the Open Cockpit manual leaves a lot to be desired in its interpretation to English.. Anybody else have a similar experience? and if so can you help. Cheers::(

Finally got it recognised (more by accident than design) but now have a similar probelm to an earlier thread - I can adjust the barometric pressure setting but nothing else. Any help?

[paulj]

Hi Gordon,

I had the same problems last week and managed to fix them by downloading SIOC version 3.52. If you are using version 3.5 it will not work.

Easist way to find the download is go to the Opencockpit's on-line shop and look up the details on their EFIS plug and play module.

When it loads up you will see some tabs on the details page and one of them is called downloads.

In there you will find a link to the correct version of SIOC.
Also, remember that's important to setup the SIOC configuration file correctly with the Master definitions.

Mine are as follows
MASTER=0,5,1,17
MASTER=1,7,1,19
the number 5 on the first line denotes the MCP and the number 7 on the second denotes the EFIS module.

If you are using Project Magenta you will find an EFIS SIOC script at the same place as the SIOC 3.52 link.
Just download and append that to your MCP script and you should be good to go.

cheers
Paul

[Gordon Turner]

Thanks Paul, That gets me started. I now see both devices but the MCP is no longer operative while I can only adjust the baro setting on the EFIS. I'll keep going and see what turns out. Seems one thing gets fixed and then another problem pops up. I will let you know how it goes. Thanks, Gordon

[paulj]

Are you using Project Magenta?

If so, I can send you my MCP-EFIS script and you can try that.

The EFIS part of the script is for both capt and FO efis but I've only got the one unit as I am only building the capt side of the cockpit.

It doesn't matter though as SIOC will only look for whatever changes are made in the hardware and respond accordingly.

Paul

[Gordon Turner]

I'm just using FSX at the moment as I didn't want to complicate matters. Does that affect the function of the modules? One thing I've noticed since changing the master definitions is that the MCP no longer illuminates or works. I think I'll take a step back, delete all existing OC software and start from scratch. I'll let you know how I go. cheers, Gordon

[paulj]

Ok then just make sure that you are using a SIOC script that is intended for use with the default aircraft otherwise that might be your problem.
It's a bit of trial and error but I'm sure that you'll get there.

Paul

[barkay]

Gordon,

Please check this thread

http://www.mycockpit.org/forums/showthread.php?t=13084&page=2

This is for FS9 and PMDG, and not tested in FSX

Things to do

1 - Makes ure that you are supplying electric to these modles. I use a USB HUB with its own power supply as some systems do not provide enough power to these modules.

2- Use SIOC 3.52b

3 - As paul explained modify the lines that start with MASTER, last digits MUST be device numbers recognized by your SIOC once activated.

4 - In the sioc.ini file there is a line that says;

window =Microsoft Flight Simulator 2004 - A Century of flight with WideServer.waiting for clients

CHANGE THIS TO YOU WINDOW TITLE AS FSX EXACTLY AS IT SHOWS THERE


Finally,

Since I really did not try this with FSX I have no idea if any of the offsets read there is different in FSUIPC4 version. Normally HDG, ALT, COURSE ara always the same offsets. Peter Dowson cna answer this.

Meanwhile I am gonna start working on FSX son.

Best Regards,

barkay

[Gordon Turner]

Hello Barkay, thanks for the additional advice.

I have been following Pauls directions with no success. The following shows my actions to date:

a. I removed all OC software and started from scratch.
b. I downloaded and installed the MCP software which gave me a IOCards folder with an MCP folder.
c. I used an addon USB hub with its own power and plugged in the MCP module.
d. I opened FSX and the MCP SIOC. The MCP lights up and works perfectly in FSX using Boeing 737-800 aircraft.
e. This is what is in the SIOC.ini file shown in the MCP folder:

[ fichero de configuracion para el SIOC ver. 3.41 ]
[ Configuration file for SIOC ]


[************** SIOC ***************]

[ Puerto del servidor IOCP ]
[ IOCP port ]
IOCP_port=8092

[ Tiempo de respuesta máximo de los paquetes IOCP ]
[ IOCP Timeout ]
IOCP_timeout=4000

[ Arranque minimizado en la barra ]
[ Start minimized in tray ]
Minimized=No

[ Retraso necesario para las variables toggles (Project Magenta)]
[ Deley needed for var. toggles (Project Magenta) ]
toggle_delay=20

[ Fichero de configuracion ]
[ Configuration File ]
CONFIG_FILE=.\sioc.ssi


[************** IOCARDS MODULE ***************]

[ Desactivar el módulo de las IOCards ]
[ Disable IOCards module ]
IOCard_disable=No

[------------- CARDS CONFIG -------------]

[ IOCard Master ]
[...............]

[ Spanish : ]

[ MASTER=(Indice device),(Tipo),(Número de tarjetas),(Número device) ]

[ Indice Device: Índice usado en la variable SIOC como device, para indicar a que tarjeta se hace referencia ]
[ Se usa 0 en el caso de que sólo haya una tarjeta y no se tenga en cuenta el número de device, por defecto un script en SIOC cuando no se pone parámetro DEVICE, se hace referencia al índice 0]

[ tipo = 0 : Emulador de Master Card ]
[ tipo = 1 : Tarjeta Master conectada al puerto paralelo directamente ]
[ tipo = 2 : Tarjeta Master conectada al puerto paralelo mediante cable de compatibilidad ]
[ tipo = 3 : Placa de expansión por puerto paralelo ]
[ tipo = 4 : Tarjeta USBExpansion usada ]
[ tipo = 5 : Modulo MCP de Opencockpits ]

[ Número de tarjetas = Número de placas Master usadas, 1 a 4 para uso de placas de expansión, 1 para conexión de placa Master directa o del Emulador ]

[ Número de device = 0 en el caso del Emulador o primera tarjeta USB detectada, Dirección del puerto paralelo (por ejemplo $0378), o número de dispositivo USB ]

[ Por ejemplo para una Master conectada al puerto paralelo : ]
[ MASTER=0,1,1,$0378 ]

[ Un ejemplo de 2 USBExpansion conectadas con 3 y 2 placas Master ]
[ MASTER=0,4,3,22 ]
[ MASTER=1,4,2,24 ]

[ Un ejemplo de conexión a simulador ]
[ MASTER=0,0,1,0 ]


[ English : ]

[ MASTER=(Device index),(Type),(Number of cards),(Device number) ]

[ Device index : Index used in SIOC variable like device, this is the card used for SIOC sentence ]
[ Use 0 for only one card, for this value you not need specify Device number. If you not use DEVICE parameter in a definition in SIOC script, the default index used is 0]

[ type = 0 : Master Card Emulator ]
[ type = 1 : Master Card connected directly to parallel port ]
[ type = 2 : Master Card connected throught compatibility cable to parallel port ]
[ type = 3 : Expansion Card connected throught parallel port ]
[ type = 4 : USBExpansion Card used ]
[ type = 5 : Opencockpits MCP module ]

[ Number of Cards = Master cards connecteds, 1 to 4 for expansion cards, 1 for a Master card directly connected or Emulator ]

[ Number of device = 0 for Emulator or first USB card detected, parallel port address, device number for specifies USBexpansion card ]

[ For example, a Master Card connected directly to parallel port : ]
[ MASTER=0,1,1,$0378 ]

[ For example, two USBExpansion cards connected with 3 and 2 Master cards used ]
[ MASTER=0,4,3,22 ]
[ MASTER=1,4,2,24 ]

[ For example, use of Master card emulator ]
[ MASTER=0,0,1,0 ]

[ Use the first USBExpansion card connected with only one Master Card attached ]
[ Esta definición es para usar la primera tarjeta USBExpansion que se encuentre instalada que además llevará conectada una placa Master ]
MASTER=0,5,1,0


[ Others Cards / Otras tarjetas ]
[...............................]

[ Spanish : ]

[ Nombre_de_tarjeta=(Indice device),(Número device) ]

[ Indice Device: Índice usado en la variable SIOC como device, para indicar a que tarjeta se hace referencia ]
[ Se usa 0 en el caso de que sólo haya una tarjeta y no se tenga en cuenta el número de device, por defecto un script en SIOC cuando no se pone parámetro DEVICE, se hace referencia al índice 0]

[ Número de device = 0 para usar primera tarjeta USB de este tipo detectada ó número de dispositivo USB ]


[ English : ]

[ Name_of_card=(Device index),(Device number) ]

[ Device index : Index used in SIOC variable like device, this is the card used for SIOC sentence ]
[ Use 0 for only one card, for this value you not need specify Device number. If you not use DEVICE parameter in a definition in SIOC script, the default index used is 0]

[ Number of device = 0 for first USB card of this type detected, or device number for a specifies device ]

[ Ejemplo de dos USBServos en indices 0 y 1, y números de devices 17 y 23 ]
[ Example of two USBServos for index 0 and 1, and device number 17 and 23 ]

[ USBServos=0,17 ]
[ USBServos=1,23 ]


USBStepper=0,0
USBKeys=0,0
USBServos=0,0
USBRelays=0,0
USBDCmotor=0,0

[ Para los ejes analógicos se usan los números de devices de las tarjetas donde están alojados ]
[ For analogic axles, you use the device number of cards what allow the axles ]

USBAnalogic=0,0


[************** FSUIPC MODULE ***************]

[ Desabilitar lectura de las FSUIPC ]
[ FSUIPC disable mode yes/no ]
FSUipcdisable=No

[ Refresco recepción FSUIPC ]
[ FSUIPC refresh ]
FSUipcRefresh=50


[************** IOCP CLIENTS MODULES ***************]

[ Retraso para inicializacion una vez conectado el cliente en milisegundos ]
[ Delay for initialization when client has been connected in mseconds ]
IOCPini_delay=3000

[************** IOCP CLIENT MODULE #0 ***************]

[ Desactivar el módulo cliente IOCP ]
[ Disable IOCP client module ]
IOCPclient0_disable=Yes

[ IP del servidor donde debe de conectar el cliente ]
[ IOCP client host name ]
IOCPclient0_host=localhost

[ Puerto de envio del protocolo IOCP cliente ]
[ IOCP client port ]
IOCPclient0_port=8090


[************** IOCP CLIENT MODULE #1 ***************]

[ Desactivar el módulo cliente IOCP ]
[ Disable IOCP client module ]
IOCPclient1_disable=Yes

[ IP del servidor donde debe de conectar el cliente ]
[ IOCP client host name ]
IOCPclient1_host=localhost

[ Puerto de envio del protocolo IOCP cliente ]
[ IOCP client port ]
IOCPclient1_port=8099


[************** SOUND MODULE ***************]

[ Ficheros de sonido ]
[ Sound Files ]

[ Desactivar el módulo de sonido ]
[ Disable Sound module ]
Sound_disable=yes

[ Volumen general de los sonidos 0-100 ]
[ Master Volume 0-100 ]
Volume=100


[ put '*' first filename for loop Sound ]
[ anteponer '*' en el fichero para bucle continuo de sonido]

[ Sound=wav_file,frequency,volume,pan ]
[ frequency=100 to 100000 0=original -1=current ]
[ volume=0 to 100, -1=current ]
[ pan=-100 (left) to +100 (right) 0=center -1=current ]

[ Sound=Fichero_wav,frecuencia,volumen,balance ]
[ frecuencia=100 hasta 100000 0=original -1=Por defecto ]
[ volumen=0 hasta 100 -1=Volumen por defecto ]
[ balance=-100 (Izquierda) hasta +100 (Derecha) 0=centro -1=Por defecto ]

[ #1 ]
Sound=APDis.wav,-1,-1,-1

[ #2 ]
Sound=*outermk.wav,-1,-1,-1

[ #3 ]
Sound=*hello.wav

[************** KEYBOARD EMULATOR MODULE ***************]

[ Nombre exacto de la ventana donde se enviarán las teclas ]
[ Name of window for key send ]
[window = "Project Magenta Glass Cockpit - Build 396" ]

window =a.txt - Bloc de notas


[ Asignación de teclas ]
[ assign youe keys ]

#1=\B\A
#2=/
#3=C
#4=D
#5=E
#6=F
#7=G
#8=H
#9=I
#10=J
#11=K
#12=L
#13=M
#14=N
#15=O
#16=P
#17=Q
#18=R
#19=S
#20=T
#21=U
#22=V
#23=W
#24=X
#25=Y
#26=Z
#27=1
#28=2
#29=3
#30=4
#31=5
#32=6
#33=7
#34=8
#35=9
#36=0
#37=<
#38=,
#39=.
#40=-
#41=*
#42=+
#43=//
#44=
#45=
#46=
#47=
#48=
#49=
#50=
#51=
#52=
#53=
#54=
#55=
#56=
#57=
#58=
#59=
#60=
#61=
#62=
#63=
#64=
#65=
#66=
#67=
#68=
#69=
#70=
#71=
#72=
#73=
#74=
#75=
#76=
#77=
#78=
#79=
#80=
#81=
#82=
#83=
#84=
#85=
#86=
#87=
#88=<a
#200=<b

[ End of File ]

f. I contacted Open Cockpits with this response:

Hello Gordon
Please go to www.opencockpits.com, click in the image of the EFIS at the left hand row an go to the product description, there go to the "Downloads" tab and download the
New SIOC 3.52b ready for EFIS. Also PMagenta script
Install it separately from the MCP Sioc.
Copy in the new Sioc the SIOC.INI and SIOC.SSI files.
Now your EFIS should work in FSX.
Open both Sioc to have MCP and EFIS running.
Regards

Your Opencockpits Support Team

g. I downloaded the SIOC 3.52b and unzipped it. It contained updated sioc.exe, sioc.ini, sioc.ssi, sioc_efis.ini plus a couple of txt files.
h. I installed these files into the SIOC folder and overwrote the files already there.
i. I then opened the SIOC.exe and have both devices showing:
IOCard-MCP Devices=40, and
IOCard-EFIS Devices=39.
j. The new SIOC.ini file (in the SIOC folder) shows only one MASTER entry of 1,7,1,0.

Is this where I should enter another MASTER line to include the MCP? and should I include the device number to reflect what shows in the SIOC open window?

OC say I should open both SIOC. When I do this I no longer have control of the MCP (ie no lights) and can only change the baro reading via the EFIS.

My programming skills expired with the demise of DBaseII and Supercalc, so I am at a loss to activate what was sold as a plug and play device. I am sure OC have all good intentions at heart, but their manuals and explanations leave a lot to be desired.

Sorry for the length of this message but I wanted to ensure I gave all the information I could.

Regards, Gordon

[paulj]

Hi Gordon,
Still having problems I see :(

Let's see if we can sort it out.

First off I agree with Barkey's post and make sure that you are powering the EFIS and MCP panels. Did you by any chance purchase the recommended power adapters when you bought the units from Opencockpits?

I did, but ofcourse they came with a European style plug and I then had to purchase a couple of adapter from Bunnings to convert them for Australian use.
Anyway if you didn't, don't worry, as you can purchase suitable power supplies from Jaycar or **** Smith etc.
They say that you can run the MCP and EFIS from powered USB hubs but I thought that I would take the safe route and use seperate power supplies.
You still ofcourse need to plug them into a usb hub to connect to your computer.

Reading your last post I see that you have downloaded the correct version of SIOC and also the EFIS script.
Now here is where you may be going wrong. Are you trying to use the Project Magenta EFIS script? If you are only going to be using FSX and the default 737 aircraft don't use the PM script.
In your SIOC folder you should see a number of different scripts for the EFIS. I think that you should be trying to use the one called EFIS_737.

Also the SIOC config file that you listed in your last post is for SIOC version 3.41 you need to use the config file for version 3.52 which would have been included .

In that config you will see an example of where/how to show the MASTER definitions. Just add your details in there and save it.

Once you have that done you then need to join the 2 scripts for the MCP and EFIS together so that it becomes just 1 bigger script.
You will need to add the following to each line of the EFIS part of the script that refers to the inputs. " DEVICE 1" (without the quotes)

For example

Var 1301, Link IOCARD_SW, Input 20 // ROT1_VOR


Becomes

Var 1301, Link IOCARD_SW, Device 1, Input 20 //ROT1_VOR

Try doing that and let us know how it goes.

Good Luck:D

Paul

[paulj]

Just a couple of other things I've just thought of.
When you go to join the 2 scripts together I don't think that you can just take the compiled scripts and just merge them.( I may be wrong here.)

What I think you have to do and how I did mine was to merge the 2 text versions of the scripts (which should be in your SOIC folder) and rename the merge file to something like MCP_EFIS_737.(using notepad)

Then start config.sioc and import this new text file and compile it as a new sioc script.
That new compiled script is the one you need to use with SIOC.
If you call the script MCP_EFIS_737 then you will also need to change the
SIOC.config file to reflect the new script.

EXAMPLE
CONFIG_FILE=.\MCP_EFIS_737.ssi


Hope this helps

Paul

[barkay]

Hi guys,

So far I am with paul with a couple of additions

1 - When joining different SIOC scripts i.e MCP and EFIS make sure to use the .txt files. If you do not have them open them one by one in SIOC and from file menu choose export to txt file, give a name and save it. Then open them and make sure you do not mess with the variable numbers. I mean ifd you will copy EFIS underneath the MCP makse sure your variable numbers will not be duplicated.

2 - Hub with own power supply will do no other need for anything else.

3 - No, no, no you can not run two SIOC's with different configs at the same time. Will give you unbelievable problems so forget about it.

4 - For the EFIS my script uses mostly key sendings accept for rotary adjustments. Make sure that default 737 supports specific key settings for EFIS functions on FSX. As far as I know there is no such a thing.

5 - If there iis no such a thing then you have to create mouse macros. I am again not sure since I did not use it but FSX version of FSUIPC should support these macros. Read FSUIPC manual for MACRO CREATION and try creating these macros then assign them from within FSUIPC.

6 - Better yet as far as the current released airplanes are concerned either use level d which comes with own sdk and there is Nico to help or wait for PMDG to come up with NGX.

As I really didi not start wprking on it yet so far with limited assumpitons that is all I can say.

Best Regards,

barkay

[paulj]

Think you are correct Barkay,
Just had a quick look at the keys/buttons assignments in FSX and I don't see any EFIS functions there.
Gordon you may have to do what Barkay suggests and create some mouse macros for the modelled functions first.
I have never needed to do that as I'm using Project Magenta software so I'm not the best person to advise you on this.
Maybe some other members who are reading this can jump in and help you?
Once they are done we might then be able to get your EFIS hardware up and running.
You should be able to use your MCP however, how is that going?

Paul

[Gordon Turner]

Thanks Paul and Barkay,

I have just printed out both of your replies and will now sit down and try to implement your advice.

Just as an aside, I have spent thousands of dollars over the last three years in pursuit of my hobby. I have ourchased many software and hardware items from reputable seller such as Go Flight, Simkits, Flight Link and others.

At no time have I had this sort of issue. I have a fully functioning Cessna cockpit utilising the above suppliers in conjunction with Peter Dowsons FSUIPC. With only minor software corrections, I have had no problems.

My 737 build is in its inception (see my photos) and I am trying to cobble together the necessary deck hardware prior to installation. I test bed everything I build in my office where I have a three LCD monitors and a plethora of yokes and controls.

My annoyance in this instance is that OC are selling a product that purports to be "plug and play" when it is evidently not. If they had been honest and upfront in their product and informed prospective buyers of the issues they may encounter, then novices such as myself would probably not part with the "hard earned readies" and would look eslewhere. Each module they sell should be "stand alone" with all the neccessary software scripts and the programme should be able to seek out other hardware items and be able to update relevant files as needed.:mad:

I am an electronics technician of some thirty years experience but unfortunately my software programming skills do not match. Judging by the numerous pleas for assistance on this and other forums, I'm not the only one either.

I fully appreciate both your assistance in this case and I will dedicate another days effort in trying to decipher OC's instructions and your more helpful instructions.

In the event I am unable to succeed, I will send one more post to this thread and call it a day. Perhaps the Go Flight EFIS will be more successful.

Cheers fellas,:D

Gordon

PS the MCP is and has always worked perfectly in FSX, so no complains there.


Think you are correct Barkay,
Just had a quick look at the keys/buttons assignments in FSX and I don't see any EFIS functions there.
Gordon you may have to do what Barkay suggests and create some mouse macros for the modelled functions first.
I have never needed to do that as I'm using Project Magenta software so I'm not the best person to advise you on this.
Maybe some other members who are reading this can jump in and help you?
Once they are done we might then be able to get your EFIS hardware up and running.
You should be able to use your MCP however, how is that going?

Paul

[paulj]

That's what I thought, the default mcp has some offsets allocated in FSX and FS9 which your sioc script is using.

When you run your mouse over the default EFIS panel you can see that there are some functions modelled but no keypresses allocated for them.
There are some functions listed in the controls menu that don't have any keypresses allocated, perhaps you could try allocating some unused keys to them to see if you can get it going.

Even better would be if you could find the offsets which the defaut panel is using and maybe get the sioc script working by replacing the PM offsets with these.

I can understand how you feel about Opencockpits but they have some working scripts for the EFIS to be used with PM, PMDG and others.

It may be worthwhile you posting a question on the Opencockpits site asking if anyone has a script already written for use with the default panel.

Hope you have some luck

Paul

[kiek]

My annoyance in this instance is that OC are selling a product that purports to be "plug and play" when it is evidently not. If they had been honest and upfront in their product and informed prospective buyers of the issues they may encounter, then novices such as myself would probably not part with the "hard earned readies" and would look eslewhere. Each module they sell should be "stand alone" with all the neccessary software scripts and the programme should be able to seek out other hardware items and be able to update relevant files as needed.:mad:

Hi Gordon,

I understand your disappointment, however, in the sales information of OC about the EFIS module you could have read:

"The module admits any configuration defined by the user, and can link with any other software like ON-737, Project Magenta, Level-D 767..."

I do not see the default 737 of FSX listed ....

and they also state:

"This module is completely plug&play (no need of USB driver). Only needs SIOC with your favourite configuration file that will link with the simulator via FSUIPC or IOCP."

So it really says, that you need a SIOC file for your favourite configuration. You now have to find the SIOC script that can handle your aircraft (the default 737 in FSX, which is not an easiest one).

Like barkay posted you probably have to define mouse macro's in FSUIPC first and then call these macro's from the SIOC script (either via keys or via virtual buttons). This is certainly no plug and play work, but if you go to the OC Forum you will probably find another guy that has sorted this out already and you could copy his script...

You only have to learn how to merge your MCP and EFIS scripts and to adust your sioc.ini.

regards,
Nico Kaan

[Gordon Turner]

Thanks Nico,

Purely frustrated after spending an inordinate time on trying to get this up and running.

After I posted the last comment I did revisit OC (I'm there almost on a daily basis) and read exactly what you have written.

The hardware product is very professional and like I say, I'm annoyed that "I" don't have the skills or knowledge to make necessary adjustments to make it work.

I guess I will have to knuckle down and learn the programing skills to understand the system properly. Like I've said, the MCP works like a dream. I'ts a pity that FSX doesn't interface the EFIS in the same flawless manner.

I have PMDG 737 NG, but I don't want to go back to FS9 when FSX and its extra scenery upgrades looks so good.

I'd like to thank everybody for their help on this and to bring an end to this thread.

Good flying!

Regards,

Gordon

[mlscotti]

Gordon, i think i am in the same boat as you as my mcp works like a charm I am running fsx with default aircraft and feelthere erj aricraft with pm (glass cockpit) but flight simulator doesn't seem to recognize my efis.
I have absolutely no experience in programming and am completely lost and affraid to change anything. I am sure i will have to learn someday:(.
I am gonna continue to follow along with your progress to see if i can fix my issue. But to complicate the issue, does anyone know how to get the backlighting to work on the unit? I am assuming once the computer recognizes the unit then maybe the lighting will come one, but i am only guessing.

Mike

[Gordon Turner]

G'day Mike,

Sorry to hear you're having similar problems to mine.

I have revisited this issue over the last few days as I have built several new systems that will be incorporated into my 737 sim. I checked out the OC website and they now have a dedicated software install for FS9 ands FSX and I did have some modicum of success.

The underlying issue here is that FSX does not allow for an easy interface with the EFIS (only certain key functions are activated) and requires extensive script writing and software manipulation to get it running.

I have installed PMDG on a separate system and am in the process of bench testing everything before I install the hardware into my deck. I will let you know how it pans out.

There is currently a forum thread on the ideal software solution whereby all products would easily and seamlessly interface using the same flight sim package. Hopefully the manufacturers are starting to take notice as not all sim enthusiasts have extensive software writing skills nor computer knowhow to spend hours in trying to get what are, after all, very expensive hardware items going.

Let me know how you get on.

Regards,

Gordon

[Gordon Turner]

Sorry Mike, missed the last part of your question. The backlighting for the EFIS has to come from a separate 5V source plugged into the phono socket at the rear. Any suitable plug pack will do the job.

Gordon

[FlightSimulation-CY]

Hey people i couldnt made it up without ask any help from the experts here so,

I have some problems using my new EFIS from OpenCockpits. The FSUIPC is fully installed and registered as well in FSX, i downloaded the latest software from OpenCockpits and i made the steps exactly as they say but it doesn't work at all. When i test the EFIS with the EFIStest it works just fine with everythink. I also change the sioc.ini file to work with my FSX.
After this i run the ssetup.exe with FSX FSUIPC configuration chosen and i launch. After this i close it and run the flight but it doesn't work. I also run MCP Pro from GoFlight but this has its own software..

I gave up everything guys, my last hope is MyCockpit experts.
:roll:

[FlightSimulation-CY]

Does anyone knows if the OC EFIS supports FSX Acceleration?

[mlscotti]

Are you using Project Magenta?

If so, I can send you my MCP-EFIS script and you can try that.

The EFIS part of the script is for both capt and FO efis but I've only got the one unit as I am only building the capt side of the cockpit.

It doesn't matter though as SIOC will only look for whatever changes are made in the hardware and respond accordingly.

Paul
Paul I am have having the exact same issue, and since the configuration is partially in spanish I am having difficulty even configuring the sioc.ini file. I am using pm glass cockpit, could you send me your configuration to try.

[davemckee]

I fear I'm in for it. I have just purchased an OC EFIS, again thinking it was a plug-n-play unit. I'm also a computer illiterate, so if you get yours up and running properly please post. I should have known better since I gave up on their flaps gauge. It needs SIOC and the program downloadable from the OC site does NOT correspond to what OC sent me. I have made a personal decision NOT to purchase any more from them.

[Steve A]

I had all kinds of problems to begin with, sioc is totally over my head but if you grab hold of a tried and tested script from the o/c forums and install it correctly, the units work brilliantly. I have the efis and mcp working with pmdg 737 and couldn't be happier with the way everything works together.

Dont give up Dave ;-)

[mlscotti]

I had all kinds of problems to begin with, sioc is totally over my head but if you grab hold of a tried and tested script from the o/c forums and install it correctly, the units work brilliantly. I have the efis and mcp working with pmdg 737 and couldn't be happier with the way everything works together.

Dont give up Dave ;-)
Its such a shame that it is so complicated, the units that they produce really are 1st class. My problem is even when they try to give instructions to modify the sioc files its complicated for me because of the 1/2 spanish-1/2 english programing, and the instructions are difficult to follow.

My setup is fsx with acceleration, i run project magenta glass cockpit across a network , i have one oc efis and oc mcp and the oc multi-radio. The radio works great, the mcp works mostly except for alt hold and the efis dosn't work for crap. if someone has found a decent set of instructions or a working config file please post. i also downloaded iocp server but am really getting over my head i'm afraid. HELP! :(

[mlscotti]

Ok i'm just about at my wit's end. I'm trying to get my open cockpits efis and mcp to work with project magenta glass cockpit for use on default fsx aircraft. I 've tried compiling both mcp code and efis code into one, which didn't work. I've downloaded lekseecan's reccomendations and programs with no luck. And tried going to iocp and running both efis and mcp which hasn't worked across a network. Not sure exactly what to do next any suggestions.

[mlscotti]

Not to sure, I run acceleratio0n and all i know is i've tried a lot of the suggestions and directions and i still can't get it to work, however i'm not the greatest computer geek.