opencockpits cdu script

[dazchad]

IOCP_port=8092
IOCPclient0_disable=No
IOCPclient0_port=8092
that port is for my mcp

[dazchad]

this is the only part that im not happy with what is the source file

PMDG 737-NG Driver Manual CDU B737
OpenCockpits CDU Driver for PMDG 737 NG Written by Michael Delvos
Copyright © 2010 OpenCockpits – http://www.opencockpits.com
Now, paste them into your SIOC source file below the section called ‘Inicialización
variables’
..
// __________________________________________________ ________________
// Inicialización variables
//__________________________________________________ __________________
Var 1010, name CDUKey, Link USB_KEYS, Device 2
{
IF &CDUKey > 0
{
V1011 = &CDUKey
}
}
Var 1011, name LastCDUKey, LINK IOCP, OFFSET 9999, Value 0
..
These inserted lines define two variables; by default they are numbered 1010 and 1011.
Check out whether these numbers are used elsewhere in your script. If so, you’ll have to
change the numbers because they must be unique! The last edit you have to do is to enter
the correct device number (.., Device 2). Now, save your SIOC script, compile it and start
SIOC.
Firewall

[fordgt40]

Daz

I assume Michael is talking about inserting his USBkeys code into another sioc script so that it all works together. Provided that your filename, which includes this code, matches the one in sioc.ini then there should not be a problem

One thing I have noticed is that he is using Device 2 in his definition for the CDUKey variable. If you have only one USBKeys card, then try removing the Device argument and also change your sioc.ini line to USBKeys=0,whatever your device number is

Edit: the last para may not work, if his .dll code is referencing a DEVICE 2 somewhere. So if it does not work then change it back again

I assume that your firewall is not blocking the port

David

[dazchad]

yes my device number is 119 in usbcheck.
i can not see the SIOC source file to put in
// __________________________________________________ ________________
// Inicialización variables
//__________________________________________________ __________________
Var 1010, name CDUKey, Link USB_KEYS, Device 2
{
IF &CDUKey > 0
{
V1011 = &CDUKey
}
}
Var 1011, name LastCDUKey, LINK IOCP, OFFSET 9999, Value 0

[enela]

hi Dazchad if it's for the PMDG FS9 version look at this:
http://www.opencockpits.com/modules....=print&sid=365
hope this helps you.
regards
rakouth

[fordgt40]

Rakouth

Daz has that Devlos file and is trying to make it work

Daz

Either add the above sioc lines to an exisiting source file eg your MCP one, or just create a new one with only the above lines. Make certain if you are adding this code to an existing sioc file that you are not already using var 1010 or 1011 The filename must match the name in your sioc.ini file eg CONFIG_FILE = ./???????

For the time being change the your SIOC.ini line saying USBKeys=??? to USBKeys=2,119 (ignore my previous post re device numbers)

Now check that you have precisely followed the manual, (have you now included the missing sioc.ini lines mentioned in a previous post) and check the Manual SIOC screen printout and advise whether yours exactly matches, if not please advise where and the details

David

[enela]

Daz, an alternative is to use something like Prosim737.
I have used it as Prosim beta, it works fine for both FS9 and FSX,PMDG NGX no problem...
The script is provided with the software, setup very easy.
You can use all OC modules:MCP,EFIS,CDU (FMC) ,Throttle with it.
rakouth

[fordgt40]

Daz, an alternative is to use something like Prosim737.
I have used it as Prosim beta, it works fine for both FS9 and FSX,PMDG NGX no problem...
The script is provided with the software, setup very easy.
You can use all OC modules:MCP,EFIS,CDU (FMC) ,Throttle with it.
rakouth

I think that a bit of effort in trying to solve this is better than spending 357 euros!!!

[dazchad]

what is the source file there is it?

[fordgt40]

Daz

I cannot put it any simpler. Either

1) Use the above script, call it whatever you like, put it in your sioc directory and amend your sioc.ini file to match the name

or

2) add the script to an existing sioc script and proceed as per post #16

Also read the link I posted earlier where Michael Devlos gave some advice about where to put files

David