script

Hello

I got this piece of script that im trying to get working...

i want is when sensor A detects movement AND sensor B(IN THIS ORDER A FIRST THEN B SECOND) then it going to plus 1...

and then also vice versa to minus 1...

So this is what my code looks like...

Once (GetLightingState("A")=ON) AND (GetLightingState("B") THEN
Begin

Trigger := Trigger +1;

End;


Once Once (GetLightingState("B")=ON) AND (GetLightingState("A") THEN
Begin

Trigger := Trigger -1;
End;

I know the counter is working, but i dont know how to get to logic to look at A first then at B, and then at B then at A...

Thanks You

 

I think what you are trying to do might be destined to fail, but without giving more info you could try something like this

ONCE A = ON THEN
ONCE B = ON THEN
COUNTER +1
END
END

ONCE B = ON THEN
ONCE A = ON THEN
COUNTER -1
END
END

This code above may or may not work depending on how u have your inputs configured..

OR

ONCE A = ON AND B = OFF THEN
ONCE B = ON THEN
COUNTER +1
END
END

ONCE B = ON AND A = OFFTHEN
ONCE A = ON THEN
COUNTER -1
END
END

Not really sure if either will work..

If you feel like sharing what you are trying to achieve in real world terms we might be able to help with a better solution..

Cheers.

 

Try

Once GetLightingState("B") then
if GetLightingState("A") then
begin
trigger := trigger + 1;
setLightingState("A", OFF);
setLightingState("B", OFF);
end;

Once GetLightingState("A") then
if GetLightingState("B") then
begin
trigger := trigger - 1;
setLightingState("A", OFF);
setLightingState("B", OFF);
end;

The idea is to wait on the second sensor, then see if the first one is already on.
Set the timer for each sensor to be the maximum time you want between passing each sensor.

The nested ONCE statements are interesting. I'm surprised it compiles. Not really sure what the logic engine would even do with it.

 

This is the correct way to solve the problem. It may not be necessary to switch off A and B though, as they are probably controlled by the sensor.

You are correct in that nested once statements should never be used. There is a warning in the help file about it.

 

The reason I included the code to reset A and B was to ensure only one of the ONCE statements were ever executed in a scan. If both sensors were triggered between scans (although unlikely) both ONCE statements would be fired and cancel each other out. This may, of course, be desirable depending upon the actual requirments. Also it re-enables the ONCE statements. If the sensor timer is set to a long value the ONCE statements will not be executed again untl the sensors time-out. Resetting the groups will allow the ONCE statements to trigger immediately again if someone walks through then straight back agian.

I don't think the HELP specifically mentions nested ONCE statements. I could only find a reference to ONCE inside loops and ONCE inside IF statements.

 

i have tried using if statement, but i kept getting scan errors..

Im trying to say that when Sensor A and maybe within 3sec B also senses movement, you are going to have a +1 on your trigger count, which then from there if my trigger count is higher than 0 then the lights is going to go on..

And this must just keep addind and subtracting depending in which order the sensors are going to be triggered..So if the count is higher than 0 then switch on when 0 switch off..

 

If you need to consider the delay between the two events, the it will need to be done slightly differently. This should work:

Code:

once GetLightingState("A") then
begin
  TimeA := time;
  if (time > TimeB) and (time - TimeB < 3) then
    Trigger := Trigger - 1;
end;

once GetLightingState("B") then
begin
  TimeB := time;
  if (time > TimeA) and (time - TimeA < 3) then
    Trigger := Trigger + 1;
end;

 

Alternatively just set to timer on the sensors to 3 seconds. If you don't pass the second sensor within that time it will have expired and the IF statment will not be triggered and the count left unchanged.