Cockpitbuilders.com

Hi all.

I need some help and/or advice please.

I am not sure if anyone else here runs the OC 737 flaps gauge but having had it sitting in the box for ages, I thought it was about time to start getting some movement on the MIP.
To cut to the end of the story first, I can't get the gauge to work with FSX.

Testing the servo, it works fine using the test.exe programme. I have noted the values required at the appropriate flap settings and I have modified the script (which was copied from the OC site) by changing the values of the variables, imported the script into the config_sioc.exe programme and saved as sioc.ssi

I will attach a copy of my script but the only things I have changed are the value of the variables.

One thing to note how ever is that unlike the installation manual, my values when the flaps are 'up' are high and start at 1008 (as oppsed to 153 in the manual) and at flaps '40', the value is 200 (as oppsed to 709 in the manual). I can't find a way to reverse the servo. Whether the higher settings at the flaps up in the script have any bearing on the issue I don't know.

Any help would be greatly appreciated.

Script is below.

Gary

************************************************************************
Var 0000, Value 0
{
&ind_le_extend = 0
&ind_le_trans = 0
}
Var 0001, name servo_flaps, Link USB_SERVOS, Output 1, PosL 0, PosC 511, PosR 1023
Var 0002, name flaps_fsuipc, Link FSUIPC_IN, Offset $0BE0, Length 4
{
L0 = &flaps_fsuipc
L0 = ABS L0
IF L0 = 0
{
&ind_le_extend = 0
&ind_le_trans = 0
}
ELSE
{
L1 = 0
&ind_le_trans = 1
IF L0 = 409
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 819
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 2047
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 4095
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 6143
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 10239
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 12287
{
L1 = 1
&ind_le_trans = 0
}
IF L0 = 16383
{
L1 = 1
&ind_le_trans = 0
}
&ind_le_extend = L1
}
L2 = L0
C0 = L0 >= 0
C1 = L0 <= 409
IF C0 AND C1
{
&flaps_low_val = 0
&flaps_high_val = 409
&servo_high_val = 1008
&servo_low_val = 891 // 0 and 1
}
C0 = L0 >= 409
C1 = L0 <= 819
IF C0 AND C1
{
&flaps_low_val = 409
&flaps_high_val = 819
&servo_high_val = 891
&servo_low_val = 775 // 1 and 2
}
C0 = L0 >= 819
C1 = L0 <= 2047
IF C0 AND C1
{
&flaps_low_val = 819
&flaps_high_val = 2047
&servo_high_val = 775
&servo_low_val = 618 // 2 and 5
}
C0 = L0 >= 2047
C1 = L0 <= 4095
IF C0 AND C1
{
&flaps_low_val = 2047
&flaps_high_val = 4095
&servo_high_val = 618
&servo_low_val = 481 // 5 and 10
}
C0 = L0 >= 4095
C1 = L0 <= 6143
IF C0 AND C1
{
&flaps_low_val = 4095
&flaps_high_val = 6143
&servo_high_val = 481
&servo_low_val = 390 // 10 and 15
}
C0 = L0 >= 6143
C1 = L0 <= 10239
IF C0 AND C1
{
&flaps_low_val = 6143
&flaps_high_val = 10239
&servo_high_val = 390
&servo_low_val = 289 // 15 and 25
}
C0 = L0 >= 10239
C1 = L0 <= 12287
IF C0 AND C1
{
&flaps_low_val = 10239
&flaps_high_val = 12287
&servo_high_val = 289
&servo_low_val = 213 // 25 and 30
}
C0 = L0 >= 12287
C1 = L0 <= 16383
IF C0 AND C1
{
&flaps_low_val = 12287
&flaps_high_val = 16383
&servo_high_val = 213
&servo_low_val = 200 // 30 and 40
}
&servo_calc = &servo_low_val - &servo_high_val
&flaps_calc = &flaps_high_val - &flaps_low_val
&flaps_val = L0 - &flaps_low_val
&servo_val = &servo_calc * &flaps_val
&servo_val = &servo_val / &flaps_calc
L1 = &servo_high_val + &servo_val
&servo_flaps = L1
}
Var 0003, name servo_val
Var 0004, name flaps_calc
Var 0005, name servo_calc
Var 0006, name flaps_val
Var 0007, name flaps_low_val
Var 0008, name flaps_high_val
Var 0009, name servo_high_val
Var 0010, name servo_low_val
Var 0011, name ind_le_extend, Link IOCARD_OUT, Output 22
Var 0012, name ind_le_trans, Link IOCARD_OUT, Output 21

When you say it does not work with FSX, do you mean that it does not move at all or moves to the wrong positions?
If the first, ie no response, have you edited your sioc.in files to tell sioc that you have this card installed.

If not, find the entry line that says

USBServos=0,46 ( 46 or whatever)
Run SIOC and make a note of the device number that appears in the top right of the sign on screen, if for example it is 32, then change the sioc.ini line as above  to

USBServos=0,32

Save the sioc.ini file and rerun sioc. I also assume that you have changed the config file line to reflect the name of your flap .ssi file

Apologies if you have already done these things - it is always best to try the simple ones first

David

Hi David.

Sorry should have clarified. There is no response when operating the flaps.

sioc.ini files show
USBServos=0,57
device=2132

I have named the .ssi file as sioc.ssi which is what the manual said.

When I open the SIOC exe short cut on my desktop which I use for the radios, MCP and EFIS, the sevos card - device 57, shows and shows that it is connected.

Don't apologise as a second pair of eyes is always welcome.

Gary

Gary

Another possibly stupid question - have you connected a 5v volt supply to the servo card? If so, have you tried opening the IOCPConsole within the SIOC main window and used the LOG function, or checked the values of your servo variables to see if they are changing?

David

David, there is never a stupid question.

Yes I have a seperate 5v supply.

As you suggested, I opened the IOCP Console and the figures in the log kept changing to higher numbers one digit at a time. I do not know if I should have seen anything else as this is the first time I have tried this. Whilst in the IOCP, I used the test.exe programme and saw no difference. The numbers just kept increasing by one digit at a time. I got to 4000 before I decided to X out as I really didn't understand what I should have been looking at.

What puzzles me, is the variables that OC have got in their manual show lower figures (153) when the gauge is set to the up position and increase until flaps 40 is achieved. Mine are opposite (ie lower number of 200 at Flaps 40 increasing to 1008 when the flaps are in the up position).

I can find no way of reversing the servo so I can achieve similar results. Whether this may have some bearing on the problem, I don't know.

According to their flaps manual and that of the servo card (which tells you what to write in sioc.ini), it should work.

The card, servo, power supply and usb connection are fine as the gauge works when testing either using the slider or inputting known variables and pressing send when using the test.exe

Gary

Gary

My questions were prompted by need to try to isolate the area of the problem. The variables you see changing in the IOCPConsole are your servo variables eg



If so then that tells us that sioc is working and we just then need to establish why the servo does not move - I am not worried at this stage about the values being opposite.

I should check that the variable  no 2 "flaps_fsuipc" changes value within the IOCPConsole when you change your fs flap settings. That will then tell us that all the info is getting to the sioc programme. I assume that the above script is the only SIOC programme running

David

Thanks for the explanation David.

The good lady has just called me out for tea so I will have another look either tonight or tomorrow.

Cheers for bearing with me on this.

Gary

Gary,
Im not sure what the Device number you are using as i believe for just the USBservos card
as im using my device number is 0.
I dont have any device number in my sioc.ini file with such a high number. Im not to familiar
with sioc and David has helped me so if changing it to 0 doesnt help im sure David will get you sorted. Good Luck.
For curiosity sake Hitec and Futaba servo operate opposite to each other.

Les
P.S Have a look at Var 0001 in iocp console while operating the flaps, does it change. If so then
program is working and has to be elsewhere. Maybe ini file not right.

David,

No, the variables weren't changing, it was the line of increasing numbers in the log that were changing. I thought they were the ones you meant.

Var0002 does not change when operating the flaps.

iwik,

The device number 2132 is that shown when opening the test.exe programme. It is actually the same as shown in the manual.

Var0001 does not change when operating the flaps.

The servo is a Hitec HS-55 which is supplied by OC.

I have attached my sioc.ini file for you - just in case you can find an error there.

Thanks guys.
Gary

Gary

You have two entries for USBservos!!

Delete
USBSERVOS=0,57
deviceUSB=2132

Then change the line USBservos =0,0 to USBservos=0,57

Not closely checked the rest, but try this and see if the flaps_fsuipc variable changes

David

David.

Entry

USBSERVOS=0,57
deviceUSB=2132

deleted and the other now reads

USBservos=0,57

I didn't realise there was already a servo entry in the file. I take it I do not need the device number 2132 as it stipulates in the manual.

VAR0002 does not change.

I am begining to see what you mean about the changes. The MCP is shown in the IOCP Console and when I altered the speed/mach knob, I could see that things were happening. I get nothing like that when the flaps are operated.

Gary

Gary

Are you running FSUIPC?. It might help if you listed all your pc`s and what software is running on each  :)

Off to bed soon - stayed up late last night watching the US Golf to see Rory win

I will look again at your .ini file tomorrow - it appears that your sioc prog is not linking with FS

David

David,

Yes running a registered copy of FSUIPC.

I have a stand alone PC purely for FSX (which can be connected to the internet for registering software when needed).

The PC is running Vista 64 home.
Software is FSX, FSUIPC, FSXpand (networked to FSClient on a second PC for EICAS display only) and various aircraft and traffic add ons for FSX.

All other OpenCockpit devices are working - MCP, Comm, Nav, TCAS and EFIS. The CDU isn't connected just yet as I am only using the default 737 as like many others I am waiting for the release of the PMDG NGX.

Great result for Rory by the way - top man.

I too will be off to bed - just approaching mid night here.

Cheers again David.

Gary

Gary,
Had a look at your .ini file. The only thing i can see is that you have the following listed:

CONFIG_FILE=ServoVSI.ssi

But you say you saved  the flap file as sioc.ssi.
The  above file should read   CONFIG_FILE=sioc.ssi
The two named files have to be the same. Something doesnt add up as SIOC should give an error like "file not found".
Please make sure in the SIOC.ini file that you are using is named the same as what appears
in CONFIG_FILE=

Hope this helps.
Les 

Gary

Like Les, I could see nothing wrong with your .ini file, other than the comment made  that your config file entry does not match what you said in an earlier post. I assumed that was an error, as you said you found the variable flaps_fsuipc in the variables list of the IOCPconsole. From your .ini file it says that you are using 2 mastercards connected to an expansio card, I assume this is correct. Please check that your opening SIOC window shows the following:

IOCards Module = status running
FSUIPC Module = ok followed by version and fsx or fs9
IOCP Server = Clients connected 0
IOCP Client Module # 0= Disabled
IOCP Client Module # 1= Disabled

In the black box underneath the line will show your path to the selected .ssi file which should equal the one you want
Lastly the window should show top right the device number of your card and in the log box it should say File Compiles

If anything varies from this then please say.

I have never found it necessary to use the deviceUSB=2132, however, reinstate this if you want.

I am a little unclear where all your software lies - am I right in assuming that the OC stuff is on  a different machine to the pc with FSX, if correct, are you running Widefs on the OC machine?

David

Hi Les.

CONFIG_FILE=ServoVSI.ssi - is what was already in the ini file before I started but it has now been changed to CONFIG_FILE=sioc.ssi

David,

The SIOC window shows

IOCards Module = status running
FSUIPC Module = ok    version 4.600a
Simulator FSX
IOCP Server = Clients connected 0
IOCP Client Module # 0= Disabled
IOCP Client Module # 1= Disabled

The Log box shows this

Welcome to SIOC by Manuel Vélez
Starting SIOC
Loading SIOC config .INI :
C:\Program Files (x86)\IOCards\SIOC\sioc.ini
Initializing IOcard Module
Loading SIOC Script :
sioc.ssi
Launch IOCPConsole
Launch IOCPConsole

Still nothing works. It appears that it is telling me to launch the IOPC console.

As to my software, when I look at the SIOC windows for the MCP, EFIS etc, the black box at the bottom tells me the roots for the devices are in my documents folder. I think the reason for this must lie in the fact that the scripts and manuals from OC were downloaded onto a stick on this computer and then copied onto the FSX machine. They obviously copied to my documents folder by default. Is this a problem and should I move them to the SIOC folder.

In relation to your software querie, I very rarely have the second computer running with FSClient as I still need to set it up so all software is on the FSX machine. I do have WideFS along with FSUIPC but WideFS is not set up either yet. I assume there must be an issue with the location of the OC software as you can't see it but apart from the flaps gauge everything else works.

Gary

Hi Gary
What about switching for a USB Simkit flaps gauge?

:D

(just 4 fun as I know how frustrating a non working "shouldwork" item can be!!)

Gary

Your connection to FSX is fine from your log. However, I am now seriously wondering whether you have the right filename and in the right directory for SIOC to read!!!

If SIOC found the filename defined in the config_file =xxx then you would have the message "file compiled" or a syntax error message in the SIOC log box.

Please make absolutely certain about the correct filename that you want to use, make certain that is in the sioc.ini file. Then make certain that this file is in the same root folder as sioc and sioc.ini

Then run it, open up IOCPconsole and make certain that var 2 does have the correct variable name 

If no luck then disconnect all other OC hardware and try again

I see Jack has just woken up and is trying to get his own back for the golf - at least for his colleagues south of the border :)

David

I'm watching this thread with interest, as i have my OC flaps gauge still in the box waiting to be installed.

Hopefully i get a free ride and mine works straight away!!
:laugh:

How do you think we all learnt :)
Its the best way to learn from the misfortunes of others and I have had my fair share - misfortunes that is

David

David I keep admiring your science of SIOC!! really as you always come up with a way to do it!
Ancient Chinese to me!!

Ancient chinese to me too Jack!!

Jack

Thanks but lets reserve any plaudits until we get Gary sorted :)

SIOC is a dark art and you will often need a padded cell to take refuge in

Seriously, once the greater part of it has been learnt, it is very powerful and I have all my cockpit h/w linked through it to SA, that is complete OH, MIP. Pedestal, MCP, EFIS,and CDU all working ok.

David

Hi Jack.

Simkits flap gauge - nah - too simple, I like a challange - 'he' says when someone else is doing all the work.

Hi sas541 - welcome on board. Lets hope we can both learn from David.

David.
Right.
Just to make sure I have the right files in the right places - Drive 'C'/Programme Files(X86)/IOCards/SIOC. Within the SIOC folder, I have sioc.ini and sioc.ssi 

I have re-checked the sioc.ini and it states - CONFIG_FILE=sioc.ssi which as suggested earlier was changed from CONFIG_FILE=ServoVSI.ssi

The IOCPCONSOLE shows Var 2 as flaps_fsuipc

I have tried the flaps and still nothing. I have disconnected the the MCP,EFIS TCAS and radios and tried again - still nothing. I can open up the test.exe programme and manually make the servo move - that is all it will do at the moment.

Question - I take it there is no need to reboot the computer to save any changes I have done in the .ini file ?

Rory deserved the win. He was so close last time.

Gary

Hi all.

I am going to sit down and re-read the servo card and flaps gauge manuals just to be sure I haven't done anything that I shouldn't.

Thank goodness I have 3 screens to spread all the open windows on !!!

Just as an aside. We have another problem. The pool temperature has hit 28 degC and with no clouds in the sky it is exposed to full sun. The problem - well the water has now gone a beautiful shade of emerald green. So - if anyone here knows about pools, input welcome  >:(

Gary

Gary

Keep at it! At least we now kbow that SIOC is talking to FSx and that the flaps file is being compiled even though SIOC is not saying so!
As someone once said if you eliminate all other possibilities, whatever remains, however unlikely, must be the answer. So try this file and name it  sioc.ssi and replace the other file. This file works fine on my machine - the outputs will not work but that is still not an issue.

Though, I still do not understand why the flaps_fsuipc variable is not changing value when you alter the flap position - btw hoe are you changing the flap position via FSX F6 or F7 ?

David

Following "avidly" the flaps saga...   :P

For the pool, no sweat, all Canadians here will get together and Fedex an Iceberg

Gary

I have just loaded your original flaps file into my machine. Run SIOC and entered IOCPconsole. When I press F6 or F7 the majority of the variables change value as they should. Thinking again now :)

David

Gary

Been doing some more testing by setting up sioc and your prog on my fsx machine so there is no network - which matches your setup. When I press F6 or F7 the value of flaps_fsuioc does change, however, it can rarely be seen since you cannot have both FSX and IOCPConsole windows active at the same time. You need to make a note of the value, change the flaps and reread the value again. Could you check this.

So we now turn to your servo card and ask which port do you have your lead plugged into - it is output 1?
Sorry to doubt but we are into questioning everything now :)

David

David,
You can have both windows active, to see what is changing. Just checked on my machine.
Make sure that fSX window is the one active.
Les

Les

Of course your right - I had not minimised the fsx screen enough :-[

David

David,
Hope i didnt come across as sharp with my statement. as just trying to be helpful. I know how useful the iocp console can be when trouble shooting. Many times ive had to have fsx and
the console side by side to see what was happening.

Gary,
Try and understand whats is happening in the IOCP Console as it is  a very useful tool when
developing and testing code for SIOC.
Les

Quote from: iwik on June 21, 2011, 10:43:18 PM
David,
Hope i didnt come across as sharp with my statement. as just trying to be helpful.

Les, not at all - no probs :)  As you say the IOCP console will help a lot. I am still concerned about why the file is not being shown as compiled.

Gary, we are  desperately seeking the golden nugget still, what version of SIOC are you using?

David

David/Les.

Sorry, I checked the forum earlier this morning and left my self logged on. I haven't been ignoring you but I needed to get some more courses of bricks laid on my workshop before it got too hot - as it is now.

To answer an earlier question, I normally use a switch on my yoke to operate the flaps but because of the issues I'm having, I have also been trying with F6 and F7.

I have just sat down with a cold glass of water and will turn on the FSX machine shortly and get back to you with the further details you requested.

I take it from what you said earlier David that I should not load on the script you sent just yet?

I really do appreciate your efforts guys. I have read many threads on this forum regarding SIOC and it does appear to be a bit of a handful to get your head around it.

Be back soon.

Gary

Hi Gary

No worries, I have a sim to complete as well, so your silence was not a problem :)

I would not load a new script yet, as there seems to be a fundamental problem elswhere as I have run your script without a problem on two computers, one networked and the other standalone. The key exercise is to run your script with both iocpconsole and fsx windows open (thanks Les!) and to see if the flaps_fsuipc and other variables change value when F6/F7 are pressed. You may if you wish reinsert that .ini line  "deviceUSB=2132" , though I have never used it with USBservo cards.

David

Edit

"To answer an earlier question, I normally use a switch on my yoke to operate the flaps but because of the issues I'm having, I have also been trying with F6 and F7. "

You do not still have the flaps command assigned to the yoke switch within FSX do you, ie the flaps on the fsx screen do move when you press F6/7 or your yoke switch :)

Good afternoon David.

You have my full attention again - but I must fit in my Spanish home work sometime today !!!!!

Right.

Sioc is version 3.7B1

The servo lead is plugged into number 1 output on the servo card.

I can now for some reason get the Var 2 value to change in IOCPConsole whether using F6/F7 or the switch on the yoke. In fact, which ever Var number I select, they all now change values. Perhaps the overnight rest did it some good !!!

Gary

BINGO

David/Les.

It is working.

For your info, all I did was re-insert 'device=USB2132' again directly underneath 'USBservos=0,57' in the .ini folder in Sioc.

I can now install the gauge into it's proper place instead of having it and the card on top of the glareshield.

Thank you so much for your assistance both of you.

Kindest regards

Gary

Methinks the Spanish homework and the green pool can take a back seat for a while, I am just going to have to have a fly to try it out once I have put the gauge back into the panel.

I would be interested for your feed back on what happened because for the life of me, I have no idea - unless it was just a case of re-inserting the device number again.

Gary

Celebrations were short lived I am afraid.

Yes the flaps gauge still works but -- I cannot use the flaps gauge and MCP at the same time.

I open up the SIOC window for the flaps gauge and all is ok.
If I open up the SIOC window for the MCP, I get the message - 'Could not bind socket. Address and port are already in use'.

If I close both SIOC windows and open the MCP SIOC window on it's own, it works ok but with the MCP window open I get the same message 'Could not bind socket. Address and port are already in use' when I try to open the SIOC window for the flaps gauge.

There is obviously a conflict somewhere. I will have a look but wondered if you could shed some light on this first before I start to tinker.

Gary

Gary

Great news indeed. It is difficult to know exactly what solved it - there were too many variables at play here and no real reference point other than it would not work. All I know is that I have never needed that extra .ini line, but  who cares now :)

Does the servo move to the correct positions or is it still reveresed. If the latter I can give you some code to correct that

Well done

David

David I think we both posted at the same time as you have not commented on the conflict I seem to have.

Yes the gauge moves correctly.

Gary

Gary

That is because you cannot run two instances of sioc on the same machine. You have two options:-

1) Install sioc and wideFS on the other network machine and run your flaps script from there

2) Combine your MCP script and Flaps script into one. You can do this by cutting and pasting one into the other, however, you must check that you do not have the same var numbers  ie duplicated. Alternatively, you can get sioc to do this for you - it is too difficult to explain here but see this link

http://www.lekseecon.nl/configsioc.html#multiplefiles

David

Thanks David.

I will have a look.

Gary

Gary

This help function goes off line late tonight as I am off in the moring to La Coruna for a wedding  till Sunday evening - will wave to you from NW Spain  :)

Good luck

David

Cheers mate.

Enjoy your long weekend. To quote a well known bloke on here, 'the beers in the fridge' if you ever find yourself down Alicante way.

Gary

Gary,
Great news and well done. Davids input is valuable, anyone like that is worth his weightin gold.
Thanks David for your willingness to help all.
Gary, combining your scripts into one is quite easy,just follow the link David gave you. I had to do it a week or so back and all worked fine first time.
Like david said i to have never added the line Device=  only used what was default for the .ini file. But who cares as long as it works.
Now enjoy your added hardware.
Les

Cheers Les.

Now thinking back, I was wondering to myself, - as habit, before starting FSX, I open up the SIOC windows for the MCP, EFIS and radios. If, as David suggests, Sioc will only allow one .ssi file at a time, then was this why the flaps gauge wasn't working in the first place. I did try initially just opening the flaps gauge on it's own but that was before we did any alterations to the .ini file.
So I think to myself why then does the MCP work with EFIS, Comm, Nav and TCAS with no problems ?
Is it perhaps that these are plug and play devices and will work together where as the Servo card/flaps gauge has to be programmed.

The plot thickens but I will let you know how I get on - after my Spanish lesson - when I will be free to have another play.

Thank you for your advice and encouragement also.
You are right, Davids willingness to help is brilliant just like others on here, which is why I spend so much time reading the threads.

I am sure the good lady thinks I am looking at things I shouldn't whilst spending so much time on the computer - or perhaps in her eyes I am !!!!!!

I will venture into the 'group run' in the SIOC config tomorrow and see how I get on.

Gary

Quote from: bussgarfield on June 22, 2011, 10:57:16 AMSo I think to myself why then does the MCP work with EFIS, Comm, Nav and TCAS with no problems ?
Is it perhaps that these are plug and play devices and will work together where as the Servo card/flaps gauge has to be programmed.

I do not know the answer to that, as I have no stand alone OC other than a MCP and have not tried to run them together. However, I have had your error message many times - always when running another version of SIOC having forgotten that one was already running. There may be another fix, but that is beyond my knowledge.

Thanks for the kind words guys, I`m just paying back the help received in the past - notably the guy with beer in his fridge :)

Gary

Something was niggling at the back of my mind and I checked the OC site. Good news, you can run two scripts on the same machine provided the ports are different. See this link, found by a search on "run two sioc". There may be better answers with more info

http://www.opencockpits.com/modules.php?op=modload&name=Forums&file=viewtopic&topic=4724&forum=13

That is probably how they get around running multiple modules

David

Thanks David - you are a diamond geezer.

I will let you know how I get on.

Enjoy the wedding.

Gary

Hi all, and David (did you enjoy the wedding?)

I must be missing something here as I have tried to change the number of the port but cannot find the place to do this.

I left a message on the OpenCockpit forums asking for help on the 26th but like many of the questions on the forum, I had no replies.

Would one of you good fellows point me in the right direction please.

Gary

Hi Gary

Great  wedding, finished at 6am :)

I have never tried changing ports, but logic tells me that the answer lies in the sioc.ini file. I would install a second version of sioc to a completely different directory. Then change the sioc.ini line IOCP_port=8092 to a different value on your second version of sioc.

Tell me how you get on

Regards

David

Hi David.

Sorry for not replying sooner but I haven't been on the flight sim computer for a few days.

Before I install a second version of sioc, I have a couple of questions in relation to ports and their values.

Before I start, I do know that I have some house keeping to do as I seem to have sioc bits and pieces all over the place, some in my documents and some in the IOcards folder.

I have installed on my system the following OC products,
MCP - port 8092
EFIS - port 8095
Radio COM, Radio NAV and Transpoder - all working from port 8090
CDU - port 8095 - not running yet as only using default 737 but will probably conflict with EFIS
USB Servo card - port 8092 - conflicting with MCP.

First question I have is this. Do I really need to have a second version of sioc installed as this will surely only give me more conflict issues.

Second question. Where will I find a list of available ports that I can use because I am blowed if I can find them.

On the sioc windows I have shown <IOCP> Client Module #0 and <IOCP> Client Module #1.
#0 is shown as port 8090 and the status is active- Not connected and #1 is port 8099 with a status of disabled. I have enabled both ports in the sioc ini file by changing the 'disable=Yes to disable=No -  but nothing has changed.

In any case, this would suggest that I certainly have the option of using ports 8090 - 8099 if only I could locate them.

I hope this makes sense - I am learning more as I go along but I certainly need a gentle hand to guide me at the moment.

If I really need to, I will install another sioc programme but I just have reservations about that at the moment when all devices should surely be running of the same programme.

Still no replies on the OC forums by the way to my question about ports either.

Glad the wedding was a succes and you were able to get an early night !!

Gary

Gary

I am no expert in this operation or indeed OC modules.

Before I try to answer your questions, could you please tell me what software you have to run to enable the MCP, EFIS, Radios and CDU. Also did you have to configure anything, if so , what?

I ask because your sioc.ini file makes no reference to this hardware

Edit [ where does this software reside directory and drive - ditto your flaps version of sioc ]

Over three nights the earliest to bed was 2.30am :(

Regards

David

David,

2.30am seems reasonable to me but I think I would have to draw the line after a couple of nights (not getting any younger).

Back to this sioc thingy -

When I installed the MCP,EFIS and Radios, if I recall, all I did was to install sioc and then select the approprite script, which had been downloaded from OC's and copy the ssi. file into sioc. To get bthe modules to run, on start up (before starting FSX) I double click on the sioc short cuts which I duplicated from the sioc file and put onto my desk top for ease of use.

Actual software that I have associated with sioc is a registered version of FSUIPC. That is all I have done. Up until the conflict with the flaps gauge, everything was fine.
Whether I have actually installed the sioc software correctly, I don't know - the computer did that for me.

All of the ssi. files are in the sioc folder in any case.

Everything is on the 'C' drive and under Programme Files (X86)/Microsoft games/MSFSX.

I am wondering, would you advise deleting all sioc related files and starting again. The problem I have is that I download onto this computer and then save to memory stick and transfer over to the FS computer. That is why I seem to have things in different places - ie documents folder etc.

I am running Vista by the way.

Gary

Gary

Do you have one script for all your OC modules?
Is there not a different sioc.ini file for these modules ie to tell sioc to load the module scripts?

Coming back to your earlier questions, I do not see how you can have two sioc.exe programmes within the same directory - how will they know which sioc.ini file to load? How can you differenciate between the ports with only one sioc.ini file?

Unless someone else with more knowledge can chip in here, I still see that there are only two options - amalgamate your flaps script into an exisiting one, but I still do not understand where the modules sioc.ini file resides, as you will need to amend it to declare your servo hardware!

Or

Simply install another copy of sioc into a totally different directory and use the .ini file that drives the flap programme. There is nothing complicated about this. However, you need to change the port no line I gave you earlier (IOCP_port=xxxx), NOT the ones you have just changed  ;D I have no idea which port number to use - just try a number that looks free. You should reverse the port changes you made earlier

I am still in the dark about what files you are using to run your modules, hence the above is the best I can suggest at present.

Regards

David

Thanks David.

I will have a look at what you suggested tomorrow. It makes sense that all the modules should be in the same script, which they obviosly aren't - and I don't know why.

I had a look at the COMM/NAV/ and TCAS script and as it is provided, they are all covered in that same script but you have to activate the individual modules you need - simple.

I will save what I have in the ini.file so I can always revert back and then try to create a whole new script to incorporate the MCP/FLAPS/EFIS and CDU.

I will let you know how I get on - I do appreciate your time on this.

Gary

Gary

Happy to try to help, though my knowledge of OC modules is zero!

Off down the pub and then Indian takeaway

Regards

David

Nice. I do miss a good Indian take away.

Enjoy.

Gary

Quote from: bussgarfield on July 02, 2011, 11:01:05 AM
Nice. I do miss a good Indian take away.
Gary

So I assume you have the Pub!!  :laugh:

David/Gary,
I had a look at the sioc.ini file for sioc 3.7b1 which is supposed to support their modules and it seems to imply that the TYPE number defines their modules, a different one for each module they do. So may be this is how they get all running together without conflict.
Gary,
I would just use Config_sioc.exe to combine your flaps Txt code with the rest, very quick and easy.
Nico has it explained on his site.
Les

Jack,

We have bars over here - pubs are for the tourists on the coastal areas - the only Indian/take away in town was so cr_p it closed. The Chinese restaurants are to be recommended though.
For bars also read good food and tapas.

Hi Les.

Thanks for the info - very useful and I will have a look at Nico's site.

Gary

Les

I agree about the "Type" function for "modules" but have not yet seen a sioc.ini file that is properly configured for the modules. As you say, I think Gary needs to find that file and then combine his scripts and add the usbservo h/w entry into that sioc.ini file

Now back to the beer and then the curry :)

Regards

David

Gary,
I am an OC aficianado and recently did a flaps gauge software insert for another collegue on the VA i belong to (flyUK). anyway - am more than happy to help - I am using OC  (several scripts on several machines) and indeed joining with gauge composer on IOCP at the same time
best way is prob using teamviewer ( free Helpdesk software) so i can see your machine and something like teamspeak or windows live messengert for the speech channel
am avail most early eveings (uk) - let me know if i can help
Mike

Thanks Mike.

I am just about to turn the flight sim machine on and have a look at amalgamating some scripts and seeing how I can get on from there.

I will see how I get on after saving my originals first.

I do not normally use the flight sim machine on the internet but it set up to go once I switch my dongle over from this one so I will have a look at downloading teamviewer/teamspeak.

I may well be getting back to you.

Cheers
Gary

I have been busy getting frustrated this afternoon.

I have managed to create a multiple .ssi file which incorporates the EFIS, MCP and Flaps Gauge scripts, which I saved as mcpefisflaps.ssi, just to distinguish it from any other .ssi files. I then inserted 'mcpefisflaps.ssi' into the sioc.ini file next to the configure-sioc and I have still got nowhere.

Mike, I will send you a PM to arrange a 'meeting' with you via teamspeak/teamview as I have now got them on the FS computer and perhaps you can crawl your way through what appears to be a spiders web of files within SIOC and see if you can point me in the right direction.

This little/major issue of mine will be cracked - by hook or by crook. I haven't flown for nearly 2 weeks and the withdrawal symptoms are driving me to drink - without the curry !!!!

Cheers
Gary

Gary

Please post your sioc.ini file that you are using

Regards

David

Hi David - how was the take-away?

Below is my 'current' sioc.ini file with the latest mods.

Gary
************************************************************

[ fichero de configuracion para el SIOC ver. 3.7 ]
[ 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=mcpefisflaps.ssi

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

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

[ Usar puerto LPT en las IOCards ]
[ Use LPT port in IOCards ]
IOCard_LPT=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 ]
[ tipo = 6 : Tarjeta USBOutputs ]
[ tipo = 7 : Modulo EFIS de Opencockpits ]
[ tipo = 8 : Modulo Radio COM de Opencockpits ]
[ tipo = 9 : Modulo Radio NAV de Opencockpits ]
[ tipo = 10 : Modulo Radio ADF de Opencockpits ]
[ tipo = 11 : Modulo Radio ATC 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 ]
[ type = 6 : USBOutputs Card used ]
[ type = 7 : Opencockpits EFIS module ]
[ type = 8 : Opencockpits Radio COM module ]
[ type = 9 : Opencockpits Radio NAV module ]
[ type = 10 : Opencockpits Radio ADF module ]
[ type = 11 : Opencockpits Radio ATC 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=3,6,1,252]
[MASTER=0,4,1,0]
[MASTER=0,4,1,0]
MASTER=0,4,2,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 : ]

[DEVICE INFORMATION]


[ 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,57
deviceUSB=2132
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=No

[ 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=No

[ 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=B
#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=/0
#45=/1
#46=/A
#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 ]

Hi Gary

The takeaway was brilliant - meat vindaloo made extra hot, still have some left for tonight  :)

This .ini file does not reference any of your modules, so they will not work. I suspect that there is another sioc installation somewhere on your computer that enables all the modules.

Could you do a search for all sioc.ini files and tell me if you find any more, particularly one with a series of enabled (no square brackets) Master= statements with the third argument being 5, 7 or 8.

Regards

David

David, just before I do the search, I did insert the appropriate numbers next to the master (without brackets) to include the MCP, EFIS etc but that made no difference so I deleted them again. You will see that I left a comma after the last nought but that has been deleted now.

Stand by, I will do a search for for any sioc installations and get back to you.

You are a man after my own heart by the way. A good hot vindaloo or jalfrezi can't be beaten.

Gary

Gary

Ok, but I suggest you do not change anything else yet, or we will have no reference point to come back to  :)

I am willing to bet a curry that you will find another sioc installation and sioc.ini file - probably in the directory pointed to by your original desktop short cut :)

Regards

David

David,

Jalfrezi please with extra chillies.

Sorry for the delay but the good lady took over the computer to check her facebook - cheek - can you believe it?

Nope, just the one Sioc installation.
I have not changed anything else apart from deleting that comma by the way.

I have just opened up sioc.exe and everything is shown on there but the MCP and EFIS have that horrible little asterisk against them. The mcpefisflaps.ssi is shown in the log.
I started up FSX and the flaps gauge works but thats all.

Gary

Gary

I think I need some extra chillies now!!

I just do not understand how your MCP modules etc  worked if that sioc.ini is the original - bar changing the config file line. Sorry to ask again, but I assume you did a search in Explorer under files option for sioc.ini on all drives?

Yours

Puzzled

David,

You must be psychic - I did a search 'everywhere' and found 50 sioc.ini notepad files. it appears that every time a change is made, it leaves the old file there despite just pressing save. Even the ones I teansferred onto a memory stick to put here are there (but they can't be opened as the stick is not plugged in).

So, do I need to start deleting some to leave just the one I have now or is this in order ?
They are all in the one SIOC folder.

Gary

Gary

Not psychic -  just old and cynical :) so you owe me some chillies :)

You need to get back to your original sioc.ini file the one where the modules worked ok and before your flaps "trial" Use explorer and set it in "View/list/details" mode and you could probably find the right sioc.ini from its date stamp.  I suggest you do not delete any - just move them out of the way  into a temp directory.

Next step is to see if the modules then work - if so we can then start again to get your flaps working

Regards

David

Gary

An afterthought please do a similar explorer search for sioc.exe. Just to make sure that there is not another installation  :)

Regards

David

Chillies in the post !!!!

Thanks David, I will do that tomorrow. This is all very educational stuff this - I have read so many other threads about other peoples sioc problems thinking to myself - thank goodness I'm running alright !!

It is now 11pm here and having had a long day building my workshop and working on the computer, I am bushed so I will start afresh tomorrow. Retirement was, I thought, for relaxing - never been so busy - and no I am not that old I was just able to retire a bit earlier than most.

O'h and just caught your last post about sioc.exe and will do.

Many thanks again
Gary

Hi Gary

You have earned a rest :)
Catch you tomorrow

Regards

David

Hi all.

Drastic times call for drastic measures I'm afraid. I had sioc.ini files all over the place within sioc and on the computer and most were duplicated or unable to be opened. I had no idea what was what or what I had done previously - so with a heavy heart and a clear head - I deleted all sioc related matters and re-installed sioc.

I now have a clean bill of health and we will all be singing from the same hymn sheet with no worries about why my SIOC folder is different to everyone elses.

I have saved and retained all scripts for the MCP/EFIS and flaps gauge.

So with some help I will hopefully be able to amalgamate all modules and scripts together, in the same place, so they will all be shown in the sioc.ini file which for some reason they weren't before.

I have not touched anything yet following the re-installation and wont until I speak with one of the guru's here first.

Gary

Gary

Good call. I suggest you do the following

1) Do whatever you did before to get the MCP,EFIS etc working properly - ignore the flaps script

If all works ok then

2) Amend  the USBServos= line to reflect your servo device number and add the  USBDevice= lines to the sioc.ini file, all as before

3) Hook up your servo card and run sioc. All should be ok with your MCP and EFIS working and your servo card recognised

4) Now amalgamate your scripts as per nico`s site to include the flaps file, change the config_file line in sioc.ini if necessary

5) Take a deep breath and run sioc - hopefully all will be ok

Please be very careful to make sure that your files are only being saved into the correct directory. I assume that you did the search in Explorer and there are no other sioc.exe`s anywhere else and that your desktop shortcuts are removed and/or confimed correct

Any probs, come back - I am around most of the time, working on the lathe/milling machine making a cradle to hold the drive and clutch mechanism for the throttle motor lever assemblies. Just spent 4 hours making something and realised too late that it was wrong  >:(

David

Hi David.

Everything SIOC related was removed so I have no surprises waiting for me.

Thanks for the run down on the procedures. Previously I was adding bits at a time as and when they were purchased, which is where I think I started going wrong. If at all possible, I would like to add the MCP/EFIS at the same time and then think about adding the flaps gauge.

Once my workshop is finished I too shall be able to work on my lathe again - in wood not metal. I have all manner of woodworking machinery in my store room just begging to be played with again.

I will have a play with the sioc file now and then have a quick swim before our Spanish friend arrives and then get back to the sim computer again.

Thanks again.
Gary