Opencockpits USB servo card

[737NUT]

737NUT

Thanks for joining the help line and I hope you can sort this out. One point, however, is that you are incorrect in your assertion that SIOC will not load a .txt file and compile it. I have been doing this for years

David

Thanks for setting me straight on that.

[fordgt40]

737NUT

The pitch file was only included as a simple test file to see if the servo card was working. The original file that Rockeyes had for the VSI was incomplete and would not work

David

[737NUT]

737NUT

The pitch file was only included as a simple test file to see if the servo card was working. The original file that Rockeyes had for the VSI was incomplete and would not work

David

I understand completely. He had a few errors going on there so hopefully we got them sorted out.

[737NUT]

Mke sure you are ONLY running SIOC and FSX nothing else! no usb servos or any other OC software.

[Rockeyes]

Beginning to think the odds are stacked. That's the third time the forum has crashed on me. Anyway back to the saga:


Getting this message if I try the import method. Same as I had when I tried to change David'S file


CONFIG_FILE=.\sioc.ssi

to

CONFIG_FILE=.\pitch.txt

Config_SIOC ver 3.7B1 - By Manolo Vélez - www.opencockpits.com
Open file "C:\Users\Bill\Desktop\sioc.txt"
17:54:21
Phase 1
.OK.

Phase 2
ERROR! - Unknow command
Line: 1 [ fichero de configuracion para el SIOC ver. 3.7 ]

==> [

How do you suggest changing the file names for sioc.txt and VS-Tramosi.txt?

It's late now so I will check back in the morning.

[737NUT]

right click on file, select change name, delete the .txt extension and change to sioc.ini and VS_Tramos.ssi

You are getting an error because there is a syntext error in the pitch file. Use the ones i gave you and see what you happens.

[fordgt40]

Bill

There was no syntax error in the pitch file I uploaded, indeed I checked it before posting. Have you introduced an error when cutting and pasting? I assume that you are using a low level text editor like notepad etc for both the pitch file and .ini file, else you can introduce formatting commands which sioc will not like.

I suggest that we try to narrow down the problem and temporarily ignore the servos by seeing if there is a working connection between sioc and fsx. I will post some code shortly to read various fsuipc offets then you can check if they are being read

David

[Rockeyes]

Good morning David,

I'm determined to get to the bottom off this today as I have work commitments starting tomorrow until next week. Reinstalling SIOC so I can start fresh now.

Yes currently using notepad as the text editor, can you suggest an alternative?

The plan on working on the connection between SIOC and FSX sounds a smart move.

Bill

The other thing at the moment is I feel i'm using a hit and miss method of installing theses files and where and how they should go. So I will try and find some instructions on that.

Bill

[fordgt40]

Bill

There is an auto config programme for SIOC modules on their website link is:-

http://www.opencockpits.com/modules....tle=Autoconfig

I have not used it and do not want to alter my config files but you have nothing to lose! I would save/rename your sioc.ini file first. Notepad is fine for editing the sioc files, perhaps you missed something when cutting and pasting, though I would try again to see if this is symptomatic of something else. I have sometimes found that cutting and pasting text files from other sources can introduce syntax errors that cannot be seen! I have since learnt that when this happens to delete all comments, and empty lines -usually solves it

I also attach some simple code for you to compile. Then open IOCPconsole and see if the values change when running FSX, the offsets are self explanatory


Var 0001, Name Gearstate Link FSUIPC_OUT, Offset $0BE8, Length 4 // Gear Offset, 0=up, 16383=dwn

Var 0002, Name Nsestate Link FSUIPC_IN, Offset $0BEC, Length 4 // Nose Gear Green Offset, 0=up, 16383=dwn

Var 0003, Name Lftstate Link FSUIPC_IN, Offset $0BF4, Length 4 // Left Gear Position Offset, 0=up, 16383=d

Var 0004, Name Rgtstate Link FSUIPC_IN, Offset $0BF0, Length 4 // Right Gear Position Offset, 0=up, 16383=

Var 0005, name AP_Active, Link FSUIPC_IN, Offset $07BC, Length 1 // Auto pilot active

Var 0006, name AT_Active, Link FSUIPC_IN, Offset $0810, Length 1 // Auto throttle active

Var 0007, name FLAPS_IN, Link FSUIPC_INOUT, Offset $0BE0, Length 4

[Rockeyes]

No joy with that software from Opencockpits,

Ran a quick test with FSX running and the IOCPCONSOLE looks like its not receiving the data although its states its connected.

Getting in a pickle so starting again. I have your files you kindly posted up and pasted them into a text file.

Now how should I import/compile them?

I appreciate your time and patience David and would fully understand if you wish to take a break from my posting. If so I will use the time on a read up.