SIOC "IF" Question

Hiya everyone,

Quick SIOC Question here:

If I want to have two "IFs" in a scipt (ie only light LED 5 if switch 1 is ON AND switch 2 is ON) how would I do it?

as always, I had a little try... But it doesn't work. The problem lies obvious in line 9:

Code:

---

Var 9888, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate
{
  L0 = V9888 // FSUIPC L0 = v9888
  L0 = ABS L0    // L0 not signed
  L2 = L0   
  IF L0 >= 3    // First sector
  {
    &Chain1 = 1    // 1 selected
  {
    &REF = 1
  }
  }
  ELSE    // Is a greater value
  {
    &REF = 0 //  Off
  }
}

Var 7675, name REF, Link IOCARD_OUT, Output 4 // REF LED

Var 7645, name Chain1, Link IOCARD_SW, Input 23

---

Could someone please tell me how to do it?

Cheers,

Jack:D

Jack

But you do not have 2 IF`s in your attempt. There are two ways in SIOC to make something happen on the value of two variables

IF Variable one = 1
{
IF Variable two = 1
{
LED = 1
}
}

OR

C0 = variable 1
C1 = variable 2
IF C0 AND C1
{
LED = 1
}


David

Hi all,

Davids first suggestion will work and is a good way to do it.
Suggestion 2 is ever better but be carefull with it , I would write it like this to be more clear

C0 = variable one = 1
C1 = variable two = 1
IF C0 AND C1
{
LED = 1
}

so when variable one equals 1 the C0 will become one, same for C1, then the AND function will see that both C0 and C1 are true (1) and if thats the case the led will turn on

Greetings Peter

Very sorry Lads, I figured this out for myself but not before I switched of the PC last night!

Thanks for your suggestions anyway, especially suggestion 2 as it looks interesting.

However! Please don't disregard this thread, I am designing a SIoc script and I'd like to ask (once complete) if it achieves what i want it to do.

Jack:)

I am far from an expert on SIOC as I am just starting to use it with IOCards but shouldn't the last line not have the ampersand (ie. the & symbol) removed so that it reads

Var 7645, name Chain1, Link IOCARD_SW, Input 23

Cheers, Dave

Hi Dave,

that's correct, but the symbol is no logner there (it was removed when I figured out the IF ELSE constructs).

Okay, I now need you guys to do another favour for me. I have engineered my own weather radar system using SIOC and FSUIPC Offsets. The System is designed to work with an IOCard interafced "DECCA" Panel. You won't understand unless you see a photo of the panel:

http://i822.photobucket.com/albums/z...c/100_0118.jpg

Before you read the script, note the following:

- The "LI" (Lights) Switch is NOT interfaced

- The "Chain" (Rotary) Switch has numbers running from 1-5

- The "OFF/REF/OP" Switch is a three-way rotary switch, with OFF position not being wired (so just 2 terminals wired)

- REF (Orange) and OP (Green) Are two LEDs

- This has come from a real aircraft

I would like the SIOC Script to do the following:

- If Precipitation Rate is more than 3, REF Light illumnates

- If Turbulence Rate is more than 3, OP Light Illuminates

- REF Light ONLY illuminates if the above condition is met and the Knob is set to "REF" or "OP"

- OP Light ONLY illuminates if the above condition is met and the Knob is set to "OP"

- The "Chain" Knob controls the cloud level. For example, if it is turned to 2, precipitation and turbulence reports will ONLY be given for cloud level 2 (this is controlled using appropriate Offsets)

- If the Mode Knob is set to OFF, then nothing happens (nothing lights up)

Thanks for reading, and please tell me if the script will do what I want:

Code:

---

Var 7675, name REF, Link IOCARD_OUT, Output 4 // REF LED
Var 7002, name OP, Link IOCARD_OUT, Output 5 // OP LED
Var 9991, name OPSW, Link IOCARD_SW, Input 29, Type I // OP SW
Var 8881, name REFSW, Link IOCARD_SW, Input 28, Type I // REF SW
Var 9090, name Chain5, Link IOCARD_SW, Input 20 // Chain 5 Selector
Var 7890, name Chain4, Link IOCARD_SW, Input 26 // Chain 4 Selector
Var 7665, name Chain3, Link IOCARD_SW, Input 25 // Chain 3 Selector
Var 7605, name Chain2, Link IOCARD_SW, Input 24 // Chain 2 Selector
Var 7645, name Chain1, Link IOCARD_SW, Input 23 // Chain 1 Selector
Var 9888, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (1)
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 9889, Link FSUIPC_IN, Offset $CE9D, Length 4 // Cloud Precipitation Rate (2)

{
  L0 = V9889 // FSUIPC L0 = v9889 
  IF L0 >= 3    // First sector
  {
    IF &Chain2 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 9819, Link FSUIPC_IN, Offset $CEAD, Length 4 // Cloud Precipitation Rate (3)

{
  L0 = V9819 // FSUIPC L0 = v9819 
  IF L0 >= 3    // First sector
  {
    IF &Chain3 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 9829, Link FSUIPC_IN, Offset $CEBD, Length 4 // Cloud Precipitation Rate (4)

{
  L0 = V9829 // FSUIPC L0 = v9829 
  IF L0 >= 3    // First sector
  {
    IF &Chain4 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 3829, Link FSUIPC_IN, Offset $CECD, Length 4 // Cloud Precipitation Rate (5)

{
 L0 = V3829 // FSUIPC L0 = v3829 
  IF L0 >= 3    // First sector
  {
    IF &Chain5 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}
}

Var 1746, Link FSUIPC_IN, Offset $CE88, Length 4 // Cloud Turbulence Rate (1)

{
  L0 = V1746 // FSUIPC L0 = v1746 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
 {
    IF &OPSW = 1
{
&OP = 1
  }
 }
  ELSE    // Otherwise
  {
    &OP = 0 //  Off
  }
}
}

Var 3889, Link FSUIPC_IN, Offset $CE98, Length 4 // Cloud Turbulence Rate (2)

{
  L0 = v3889 // FSUIPC L0 = v3889 
  IF L0 >= 3    // First sector
  {
    IF &Chain2 = 1    // 2 selected
 {
    IF &OPSW = 1
{
&OP = 1
  }
 }
  ELSE    // Otherwise
  {
    &OP = 0 //  Off
  }
}
}

Var 3391, Link FSUIPC_IN, Offset $CEA8, Length 4 // Cloud Turbulence Rate (3)

{
  L0 = V3391 // FSUIPC L0 = v3391 
  IF L0 >= 3    // First sector
  {
    IF &Chain3 = 1    // 3 selected
 {
    IF &OPSW
{
    &OP = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &OP = 0 //  Off
  }
}

Var 9716, Link FSUIPC_IN, Offset $CEB8, Length 4 // Cloud Turbulence Rate (4)

{
  L0 = V9716 // FSUIPC L0 = v9716 
  IF L0 >= 3    // First sector
  {
    IF &Chain4 = 1    // 4 selected
 {
    IF &OPSW = 1
{
&OP = 1   
  }
 }
}
  ELSE    // Otherwise
  {
    &OP = 0 //  Off
  }
}

Var 1019, Link FSUIPC_IN, Offset $CEC8, Length 4 // Cloud Turbulence Rate (5)

{
  L0 = V1019 // FSUIPC L0 = v1019 
  IF L0 >= 3    // First sector
  {
    IF &Chain5 = 1    // 5 selected
 {
    IF &OPSW = 1
{
    &OP = 1
  }
 }
  ELSE    // Otherwise
  {
    &OP = 0 //  Off
  }
}
}

Var 5678, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (1)

{
  L0 = V5678 // FSUIPC L0 = v5678 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
 {
    IF &OPSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 5679, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (2)

{
  L0 = V5679 // FSUIPC L0 = v5679 
  IF L0 >= 3    // First sector
  {
    IF &Chain2 = 1    // 2 selected
 {
    IF &OPSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 5680, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (3)

{
  L0 = V5680 // FSUIPC L0 = v5680 
  IF L0 >= 3    // First sector
  {
    IF &Chain3 = 1    // 3 selected
 {
    IF &OPSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 5681, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (4)

{
  L0 = V5681 // FSUIPC L0 = v5681 
  IF L0 >= 3    // First sector
  {
    IF &Chain4 = 1    // 4 selected
 {
    IF &OPSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

Var 5682, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (5)
{
  L0 = V5682 // FSUIPC L0 = v5682 
  IF L0 >= 3    // First sector
  {
    IF &Chain5 = 1    // 5 selected
 {
    IF &OPSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

---

Thank you so much if you managed to stay awake during all that!:p

Jack

For a script of this size and with so many conditions you would be better advised to run it and track what happens using IOCPConsole etc. You know how you programmed it !

Regards

David

Hi David,

If it helps I'd like to "chop up" the script a bit then. this is because I'd rather get it sorted before my Master card arrives, giving me maximum time for testing.

First question: I've put the structure:

Code:

---

{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
 {
    IF &REFSW = 1
 {
    &REF = 1
  }
 }
}
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

---

Twice, the only difference the second time being that switch &OPSW is used to control LED &REF instead.

The question is, have I created a "contradictary paradox" here? I have used the same script for &REFSW and &OPSW to control the same LED (ie EITHER switch can control the LED). However, I have put at the end of each script ELSE &REF (LED) = 0 (OFF). This is contradictary because, for example, if the switch &OPSW was on, the LED should be lit. However, the script also says that if Switch &REF is off, the LED should be off. So, in short, the LED should in theory be ON and OFF at the same time.

How do I rectify this problem?

Jack

If I understand you correctly, then if either of two switches is on then the led should be on subject to further tests - else the led should be off
If you amend the example I and pdpo gave earlier in this thread then you can test if either switch is on

C0 = variable one = 1
C1 = variable two = 1
IF C0 OR C1
{
Insert here your further tests for conditions to turn on the LED
}

ELSE
{
LED = off
}

I cannot emphasise more strongly about using IOCPConsole to troubleshoot your code. That way you can see what is happening and recode accordingly

David

Hi David,

How does this look (basic example):

Code:

---

Var 7675, name REF, Link IOCARD_OUT, Output 4 // REF LED
Var 9991, name OPSW, Link IOCARD_SW, Input 29, Type I // OP SW
Var 8881, name REFSW, Link IOCARD_SW, Input 28, Type I // REF SW
Var 7645, name Chain1, Link IOCARD_SW, Input 23 // Chain 1 Selector
Var 9888, Link FSUIPC_IN, Offset $CE8D, Length 4 // Cloud Precipitation Rate (1)
{
  C0 = V9991 = 1
  C1 = V8881 = 1
    IF C0 OR C1
  {
    L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
    {
    &REF = 1
    }
  }
  }
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
}

---

It compiles okay, can't test with IOCPConsole atm because my MasterCard hasn't arrived!

Jack

Sorry for the delayed reply - the Mycockpit server fell out with me and I could not logon. Your code looks ok to me. Two suggestions - always use names not numbers when referencing variables and use lower numbers ie start from 10 - you will see why when using IOCPConsole ( when your mastercard comes:))

David

Hi David,

I have had to amend my script very slightly since the last post, just Offset changes, nothing major.

Anyway, I have a new question.

I want the LEDs to work like this:

If the precipitation is above a certain level, the LED lights up (it already does this). However, if the precipitation is above yet another level, I want it to blink/flash.

Nicos site does give advice on this but it is unfortunately timed. I want the LED to keep flashing until the precipitation has cleared (a "permenent" blink).

Any ideas?

Jack

Nico`s site does indeed have the answer! Look at the coding for "Stop a Blinking Led".

David

Sorry David, I don't know how I could interpose that. (It's for stopping not setting a Blinking LED?)

I want it to light up if Turbulence is more than 3, but blink instead of staying continuously lit.

Jack

Perhaps I am being dim, or too much beer (quite likely), but what part of the below quote does not contribute or provide direction to what you want?

"In this example a led starts blinking at the start of the SIOC program, but you can ofcourse also take other events to start the blinking of a led. The blinking is done with a TIMER, just as in the previous example. The difference is that we now program the Timer for a very long period, it counts down from 500.000 to 0 in steps of .4 seconds, long enough for a long haul flight ;-).

As soon as you push the button, the code attached to the button will force the Timer value to 1 step before the end value. In the next Timer operation the Timer will end and the blinking will stop"

David

Hi David,

Really sorry, but I think I don't physically understand Nico's statement. How could I adapt his code for my needs? I am confused because his script is focused on stopping an LED rather than making it blink continously.

Jack

The first part of the code under Var0 shows how to start a led blinking almost indefinately. The remainder of the code shows how to stop it under the control of a switch. So for your needs you only need to determine the logic to start the led blinking, then use Nico`s example, followed by using the "stop code" to suit your "trigger"

Look at the code , not the "title"

David

Hi David,

I've had a go and the script I've made looks & compiles okay. However, everything is far from complete. Basically, I do not know how to "join" the blink script and the standard LED light-up scripts together. This is because, whilst I probably could do the scripting, I just can't work it out in my head.

I'm wondering if you could have a little go for me? I would like the script to do the following:

- IF &Chain1 SW is ON, REF/OP SW is ON, and Turbulence is less than three, the LED illuminates. Otherwise, it is OFF if any one of those conditions are broken.

- Same as above, but if Turbulence is EQUAL OR MORE than three, then the LED Blinks instead of being lit. Otherwise, it is OFF/ON (but not blinking) if conditions are broken.

The current LED Lighting script:

Code:

---

Var 7675, name REF, Link IOCARD_OUT, Output 4 // REF LED
Var 7002, name OP, Link IOCARD_OUT, Output 5 // OP LED
Var 9991, name OPSW, Link IOCARD_SW, Input 29, Type I // OP SW
Var 8881, name REFSW, Link IOCARD_SW, Input 28, Type I // REF SW
Var 9090, name Chain5, Link IOCARD_SW, Input 20 // Chain 5 Selector
Var 7890, name Chain4, Link IOCARD_SW, Input 26 // Chain 4 Selector
Var 7665, name Chain3, Link IOCARD_SW, Input 25 // Chain 3 Selector
Var 7605, name Chain2, Link IOCARD_SW, Input 24 // Chain 2 Selector
Var 7645, name Chain1, Link IOCARD_SW, Input 23 // Chain 1 Selector
Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  C0 = V9991 = 1
  C1 = V8881 = 1
    IF C0 OR C1
 {
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 <= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
    {
    &REF = 1
    }
  }
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }
 }
}

---

The Blinking LED script:

Code:

---

Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  C0 = V9991 = 1
  C1 = V8881 = 1
    IF C0 OR C1
 {
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
    IF &Chain1 = 1    // 1 selected
  {
  &REF = 0 OR 1
  &BlinkLed = 500000 // begin value of timer
  &BlinkLed = TIMER 0 -1 40
  }
  }
 }
}

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REF = 0
  }
  ELSE
  {
    &REF = 1
  }
}

---

How could I join them together whilst still achieving what I originally wanted? Could you try?

Thanks very much,

Jack

Jack

Sorry, but the best way is for you to persevere ( like many who have gone before you ), and when you get your Mastercard, to check what is happening (or not happening) - all as advised on previous threads. If you do not fully grasp this nettle, then you will not make progress and largely be reliant on others goodwill. I am happy to give advice on some specific issues, but do not have the time to provide a bespoke SIOC service

I do need to build my own cockpit!

David

Hi David,

I'm now facing a new, unrelated problem.

Whenever I try and import a .txt file to SIOC using the "Config" interface, I get the following error message:

http://i822.photobucket.com/albums/z...Untitled-5.jpg

I'm using the following SIOC Script, just for testing purposes:

Code:

---

// *****************************************************************************
// * Config_SIOC ver 3.7B1  -    By Manolo Vélez    -    www.opencockpits.com
// *****************************************************************************
// * FileName : Weather Radar System.txt
// * Date : 14/08/2010



Var 7675, name REF, Link IOCARD_OUT, Output 4    // REF LED

Var 7002, name OP, Link IOCARD_OUT, Output 5    // OP LED

Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 < 3    // First sector
  {
    &REF = 1
    }
  }
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
  &REF = 0 OR 1
  &BlinkLed = 500000 // begin value of timer
  &BlinkLed = TIMER 0 -1 40
  }
  }
 }
}

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REF = 0
  }
  ELSE
  {
    &REF = 0 OR 1
  }
}

---

This problem is very annoying. I've tried renaming the txt file, making other copies of it in a different name (you can even see "yy.txt" file in background, this is a clone), stil lno luck. FSX/FSUIPC is not running, and the txt file I'm acessing is NOT open at the time of compiling. Any ideas?

Jack

Sorry no idea:-(

Why not just change your sioc.ini file to the new .txt file and see what happens. My sioc.ini file has at least 6 lines of potential .txt files - all bracketed out except the one I am using at that time

David

Hiya David,

I tried that, and I got the exact same message, except this time BEFORE SIOC started up.

Jack

A long shot! Edit your sioc.txt to remove all // and comments plus any spaces on each line after the end of the code. Then try again, SIOC can be very funny about things especially // without any comments added. If no joy try the opencockpits forum to see if they know this one

David

Hi Daiv,d

Unfortunately it's the exact same problem, same message. I wil ltry and contact Nico Kaan, maybe he will know?

Jack

I am wondering if this error arises because you are not running fsx or fsuipc and have no mastercard installed. Also, what do you mean by saying that you get this error before sioc runs in post #22?

David

I mean that I double click SIOC, and I get the error, THEN the SIOC interface opens (ie error before SIOC).

It cannot surely be tha tno mastercard is installed, because you can still make scripts with or without IOCards (I have done in the past).

I wil ltry running FSX and FSUIPC.

Jack

If all else fails then re-install SIOC, but keeping a copy of your .ini file etc:)

David

Hi David,

I re-installed SIOC but still the same error. I have contacted Opencockpits.

__________________________

Quote:

---

Originally Posted by Boeing 747 Flyer

Code:

---

// *****************************************************************************
// * Config_SIOC ver 3.7B1  -    By Manolo Vélez    -    www.opencockpits.com
// *****************************************************************************
// * FileName : Weather Radar System.txt
// * Date : 14/08/2010



Var 7675, name REF, Link IOCARD_OUT, Output 4    // REF LED

Var 7002, name OP, Link IOCARD_OUT, Output 5    // OP LED

Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 < 3    // First sector
  {
    &REF = 1
    }
  }
  ELSE    // Otherwise
  {
    &REF = 0 //  Off
  }

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 >= 3    // First sector
  {
  &REF = 0 OR 1
  &BlinkLed = 500000 // begin value of timer
  &BlinkLed = TIMER 0 -1 40
  }
  }
 }
}

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REF = 0
  }
  ELSE
  {
    &REF = 0 OR 1
  }
}

---

This problem is very annoying. I've tried renaming the txt file, making other copies of it in a different name (you can even see "yy.txt" file in background, this is a clone), stil lno luck. FSX/FSUIPC is not running, and the txt file I'm acessing is NOT open at the time of compiling. Any ideas?

---

Hi Jack,
Well it's very easy to see what is wrong.
You made several mistakes with your opening and closing curly brackets (in 9888 first IF one closing bracket too many, and in 9881 two closing brackets too many...). Do remember that you have to match each open curly bracket with a closing curly bracket. This is SIOC for beginners .. ;-)

I have made some changes and now it compiles fine:

Code:

---

Var 7675, name REF, Link IOCARD_OUT, Output 4

Var 7002, name OP, Link IOCARD_OUT, Output 5

Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 < 3    // First sector
  {
    &REF = 1
  }
  ELSE
  {
    &REF = 0
  }
}

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9888 
  IF L0 >= 3
  {
  &REF = 0 OR 1
  &BlinkLed = 500000
  &BlinkLed = TIMER 0 -1 40
  }
}

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REF = 0
  }
  ELSE
  {
    &REF = 0 OR 1
  }
}

---

regards
Nico

Jack

I wrongly assumed that you had done the basic syntax checking:roll:

David

Hi guys,

I know you think I didn't do the basic checks, but I did. The script I posted here was the wrong one, you are correct, but I can guarentee that I tried to compile WITHOUT those brackets (I made two versions of that script, I posted the earlier one here by mistake). PLEASE do not assume I don't do basic checks, I do.

And Nico, Thanks very much. That script does compile fine.

The previous problem was very strange... It wouldn't compile because windows has injected random segments of TIME in to notepad!!! The script looks okay... but check first ELSE statement:

Code:

---

Var 7675, name REF, Link IOCARD_OUT, Output 4 // REF LED
Var 7002, name OP, Link IOCARD_OUT, Output 5 // OP LED
Var 9991, name OPSW, Link IOCARD_SW, Input 29, Type I // OP SW
Var 8881, name REFSW, Link IOCARD_SW, Input 28, Type I // REF SW
Var 9090, name Chain5, Link IOCARD_SW, Input 20 // Chain 5 Selector
Var 7890, name Chain4, Link IOCARD_SW, Input 26 // Chain 4 Selector
Var 7665, name Chain3, Link IOCARD_SW, Input 25 // Chain 3 Selector
Var 7605, name Chain2, Link IOCARD_SW, Input 24 // Chain 2 Selector
Var 7645, name Chain1, Link IOCARD_SW, Input 23 // Chain 1 Selector
Var 9998, Link FSUIPC_IN, Offset $C28D, Length 1 // Cloud Precipitation Rate (1)
{
  L0 = V9998 // FSUIPC L0 = v9998 
  IF L0 < 3    // First sector
  {
    &REF = 1
    }
  }
  ELSE
  {15:34 15/08/2010
    &REF = 0
  }

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9881 
  IF L0 >= 3
  {
  &REF = 0 OR 1
  &BlinkLed = 500000
  &BlinkLed = TIMER 0 -1 40
  }
  }

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REFE = 0
  }
  ELSE
  {
    &REFE = 0 OR 1
  }
}

Var 9889, Link FSUIPC_IN, Offset $C29D, Length 1 // Cloud Precipitation Rate (2)
{
  L0 = V9889 // FSUIPC L0 = v9889
  IF L0 < 3    // First sector
  {
    &REF = 1
    }
  }
  ELSE
  {
    &REF = 0
  }

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9881 
  IF L0 >= 3
  {
  &REF = 0 OR 1
  &BlinkLed = 500000
  &BlinkLed = TIMER 0 -1 40
  }
  }

---

Why did this happen?

I know everyone thinks I'm the SIOC Dunce, but I'm more thoughtful than you think.

Jack

We can only call on what we see!!!!
If you press key F5 in Notepad, it automatically inserts a time and date stamp into your text, it obviously missed your qa check:)

David

Quote:

---

Originally Posted by Boeing 747 Flyer

The script I posted here was the wrong one

---

So please pay atttention to what you post, you're waisting my time...
Nico

Quote:

---

Originally Posted by kiek

So please pay atttention to what you post, you're waisting my time...
Nico

---

E:???:verybody makes mistakes...

_____________________________

Hiya everyone,

Now I have a working SIOC Script, I tested in IOCPConsole. Now, whilst elements of it do work (ie above level three turbulence the LED Does flash), parts of it don't.

However, I did say in the script to light the LED (NOT flash) if below level three turbulence. This didn't happen. Also, the LED never stopped flashing, even though my "stop" was the ELSE command if the turbulence dropped below three.

I wil ltry and sort myself, but, can anyone see any obvious problems? It should work if <3, then LED Lights, of =>3, then LED FLashes. If turbulence is 0, then LED is not lit.

Script:

Code:

---

ar 7675, name REF, Link IOCARD_OUT, Output 4

Var 7002, name OP, Link IOCARD_OUT, Output 5

Var 9888, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9888 // FSUIPC L0 = v9888 
  IF L0 < 3    // First sector
  {
    IF L0 > 0
{
    &REF = 1
  }
  ELSE
  {
    &REF = 0
  }
}
}

Var 9881, Link FSUIPC_IN, Offset $C28D, Length 1
{
  L0 = V9888 
  IF L0 >= 3
  {
  &REF = 0 OR 1
  &BlinkLed = 500000
  &BlinkLed = TIMER 0 -1 40
  }
}

Var 9077, name BlinkLed
{
  L0 = MOD &BlinkLed 2
  IF L0 = 0
  {
    &REF = 0
  }
  ELSE
  {
    &REF = 0 OR 1
  }
}

---

___________________________

- what does

Code:

---

                    &REF = 0 OR 1

---

do?

Jim[/QUOTE]

I implemented that small snippe of code for one reason: If the Turbulence drops below three, the LED could either be On OR Off, depending on certain conditions (if turbulence is less than three, illuminate LED, if there is NO tubulence, LED is OFF).

_____________________________