USBServos Software not working?

[Boeing 747 Flyer]

Well, curly brackets do not seem to work, it just says command outside of place when I apply curly brackets over the code.

I keep getting rather frustrated at the fact that SIOC does not work for me, even AFTER consulting the manuals especially regarding the curly brackets.

If someone could show me what the scurly brackets should look like, I will be extremely interested, because I belive I've tried every combination under the sun.

I learn not through reading manuals, or being told how to do something, I learn by seeing (in this case) a complete example of SIOC script for my Servo, which I would then analyze and understand what each entry means.

I keep getting told what each little fragment of script means, but I think I need to look at the bigger picture. For example, I was told that I would have to insert a L0 entry into the script. I know what this is, but I can't understand what I would need to define with it.

I will try and obtain from somewhere a complete SIOC script for an ASI Servo, and then analyzw what each entry means.

[fordgt40]

Jack

One last try!

Curly brackets are { }

Please follow the advice you have previously received from Nico, Iwik and others to try some simple coding exercises first using Nico`s site.

There is no "big" picture with SIOC, only a series of little ones

SIOC is not working for you because you are not trying and succeeding with very simple exercises - just jumping into trying to solve a medium complexity issue without understanding the basics

You will not learn by only looking at examples, firstly, you need to understand the following:-

The various commands and what they do
The proper syntax to use the commands
The declaration of variables and associated syntax
The use of "internal" variables
The use of boolean/logical variables
Programme flow - SIOC is unusual insofaras it is an "event" driven language. Nothing happens until a variable changes value - then the code attached to that variable (within curly brackets) is exexcuted. Also any variables within that code, if changed, will prompt the running of their own associated code

Edit to add
Programme flow with the use of IF and ELSE etc

All this and more is within the manuals and Nico`s site. If you persist as per your last post, then you will have a very long journey - even if you find some ASI code, then how will you adapt it for your own use with the knowledge level currently being evidenced?

You ask for advice, please follow it

David

[Boeing 747 Flyer]

Hiya David,

I know what curly brackets are and how to use them, but they don't seem to work.

I have gotten this far, I've managed to create a semi-useable script but things like the V000 will not compile because they are unfinished/incomplete.

Var 0000
{
&servo4=250
}
var 9000, name Servo4, Link USB_SERVOS, Output 1, PosL 250, PosC 475, PosR 700, 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
}

Getting there?

P.S: Before you ask, I have read what you have said and I udnerstand this post re-glosses over previously posted information.

[deering]

See, computer are dumb. They need data in the formats they been programmed to handle. They can't take leaps of imagination to interpret what someone's personal way of writing things might mean. And SIOC is particularly rigid in its requirements. Do you see any difference between the statements you have written that don't compile as compared to those that do?

Find that, then you'll still have some learning to do about "event driven".

[iwik]

Jack,
&servo4=250 should read &servo4 = 250
Les

[deering]

Ah well, another spoonful.

[Boeing 747 Flyer]

Ah well, another spoonful.

Also, thanks Iwik for the advice. I now get the error "= is expected" but I will try and figure this out. One little step at a time.

I completely udnerstand how SIOC is event driven. Thankfully, this is one thing that IS well documented within SIOC and clearly labelled in the presentation in the form of a diagram. EG: No change in Var = No information supplied

[Boeing 747 Flyer]

Ah well, another spoonful.

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.

[deering]

.
I completely [understand] how SIOC is event driven.....

Good to hear.

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

&servo4 = 250

to be executed?

[fordgt40]

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