USBServos Software not working?

[737NUT]

Good to hear.

What's the event that's going to cause:

&servo4 = 250

to be executed?

SIOC runs V0000 at start up one time only so whatever is under that V0000 gets done.

[737NUT]

EDIT:

Thank god, progress. The following script *seems* to be okay and compiles well, it is a long way off I know but here's what I've got so far:

Var 0000
{
&servo4 = 250
}
var 9000, name Servo4, Link USB_SERVOS, Output 1, PosL 198, PosC 446, PosR 693, Type 2 // Servo Motor
Var 9003, name IAS, Link FSUIPC_INOUT, Offset $02BC, Length 4 // Indicated Air Speed * 128
{
L0 = &IAS / 1.5
&Servo4 = L0 + 213
}

Next major step is setting up the SIOC.ini file to handle the Servo3 for ASI and USBServos Card.

Good job, question. Are you using Notepad or the SIOC config software to make your code?

[737NUT]

You also have another issue to deal with. Is the gauge linear? Boeing Airspeed gauges are not! That complicates your program tremendously as you have different scales for the servo to follow the true airspeed. I sent you an example by email how to that. I'll send you another for the limits. What gauge are you using?
Rob

[deering]

SIOC runs V0000 at start up one time only so whatever is under that V0000 gets done.

I hoped that Jack would have thought that through ...and come up with a different answer.

[737NUT]

Here you go, i attached a config file for you based on the info you gave me.
Rob

[Boeing 747 Flyer]

You also have another issue to deal with. Is the gauge linear? Boeing Airspeed gauges are not! That complicates your program tremendously as you have different scales for the servo to follow the true airspeed. I sent you an example by email how to that. I'll send you another for the limits. What gauge are you using?
Rob

If you're referring to the real-life gague, it IS linear (ie the separation between speed integers is always the same). The gague is some ex-military instrument, ranging from 50Knots to 500Knots. Thanks alot for your efforts in producing the SIOC script, I will try it ASAP once I've had a go at configuring SIOC.ini

And Dave and Deering... Could you gloss over your recent comments once more and check that they're necessary? DO they really add to the thread?Do they assist me, or potential readers of the thread?

Good to hear.

What's the event that's going to cause:

&servo4 = 250

to be executed?

According to the SIOC manual, it will be the associated Variable (no var change = NO action), in this case V0000.

EDIT: As usual, Opencockpits have a dead link (regarding sioc.ini config tool)

[fordgt40]

Jack

If you read the manual for the USBServos card you will notice on page 6, that it explains how to edit sioc.ini accordingly

I will let other "brave" readers of this thread to draw their own conclusions re "unnecessary comments"

David

[Boeing 747 Flyer]

I will let other "brave" readers of this thread to draw their own conclusions re "unnecessary comments"

David

"Ho Hum
You can take a horse to water and it will not drink
You can hold its nose and it will not drink
You can hold its nose, dunk its head under water and it will still not drink
Ho Hum"

I rest my case.

If anyone's interested, SIOC.ini (not working):

[SIOC]
IOCP_port=8092
IOCP_timeout=4000
Minimized=Yes
toggle_delay=20
CONFIG_FILE=ServoT.ssi

[IOCARDS MODULE]
IOCard_disable=No
IOCard_LPT=No

[MASTERS]

[USBSERVOS]
USBSERVOS=1,77

[FSUIPC MODULE]
FSUipcdisable=No
FSUipcRefresh=50

[IOCP CLIENTS MODULES]
IOCPini_delay=3000
IOCPclient0_disable=Yes
IOCPclient0_host=localhost
IOCPclient0_port=8090
IOCPclient1_disable=Yes
IOCPclient1_host=localhost
IOCPclient1_port=8099

[SOUND MODULE]
Sound_disable=Yes
Volume=100

And ServoT.ssi file, the one I'm using for FSX -> ASI interfacing:

// *****************************************************************************
// * Config_SIOC ver 3.7B1   -     By Manolo Vélez    -    www.opencockpits.com
// *****************************************************************************
// * FileName : ASIgauge.txt
// * Date : 7/3/2010



Var 0000, name Intialization     // Set servo positions
{
  &Servo4 = 367   
}

Var 9000, name Servo4, Link USB_SERVOS, Output 1, PosL 367, PosC 637, PosR 907, Type 2     // ASI gauge

Var 9003, name IAS, Link FSUIPC_INOUT, Offset $02BC, Length 4     // IAS from SIm
{
  L0 = &IAS / 1.5
  &Servo4 = L0 + 213
  IF L0 < 50
  {
    &Servo4 = 367    
  }
  IF L0 > 350
  {
    &Servo4 = 907    
  }
}

Best regards,

Jack

[deering]

..and Deering... Could you gloss over your recent comments once more and check that they're necessary? DO they really add to the thread?Do they assist me, or potential readers of the thread?



According to the SIOC manual, it will be the associated Variable (no var change = NO action), in this case V0000.....

Jack, with my comments and questions, I've been trying to help you learn SIOC. Others reading them and thinking them through, might be helped. So one more step along the path. When will &servo4 be set to 250 in your script?

Jim

[Boeing 747 Flyer]

When will &servo4 be set to 250 in your script?

Jim

As I said, when Var0000 event occurs, which runs at startup.