Interface problems

Quote from Dafke

It only goes on when I press the button en then push the emergency button(??).

What does this mean exactly?

Push buttons on Kawasaki interface panels, unless they are allocated a dedicated signal (system controlled), then they need to be monitored and controlled independently.

This is just standard programming using AS Language and simple condition and argument evaluations.

Quote from Dafke

I have been trying to fix this with an Autostartprogram but this makes the light goes on and off in a very rapid time.

Below shows a very crude 'one shot' example:

    si.ifp.ip[1] = 2001;
    mi.ifp.ip[1] = FALSE;

again:
    IF (SIG(si.ifp.ip[1])==TRUE) AND (mi.ifp.ip[1]==FALSE)) THEN; Register press
      mi.ifp.ip[1] = TRUE; Set scan condition during press
    END;
    IF (SIG(si.ifp.ip[1])==FALSE) THEN; Register release
      mi.ifp.ip[1] = FALSE; Reset scan condition upon release
    END;
GOTO again:

Try the following in a PC Task.

place_a = 2100;
pallet_place_a = 2120;
mi.ifp.ip[1] = FALSE;

again:
    IF (SIG(place_a)==TRUE) AND (mi.ifp.ip[1]==FALSE)) THEN; Register press
      SIGNAL pallet_place_a;
      mi.ifp.ip[1] = TRUE; Set scan condition during press
    END;
    IF (SIG(place_a)==FALSE) THEN; Register release
      mi.ifp.ip[1] = FALSE; Reset scan condition upon release
    END;
GOTO again:

Signal 2120 will be turned on with a press of the place_a button and turn on the lamp of the button.

mi.ifp.ip[1] will be true for as long as you press the button (no flashing on/off during scan).

Signal 2120 would need to be turned off at some point in your main program.

Quote from Dafke

Alright I get it little by little. I understand what you doing in your code, but I cannot load it, it keeps saying that it needs the full spelling of the command.

You cannot load it in as it is as I have included a 'spelling mistake' on purpose.

Yes, sounds sneaky but just copying and pasting code without knowing what it is, is half the battle.

What in the above code is causing the error - hint is the last line.

mi.ifp.ip[1] is just a real variable array element used as a 'flag'......the name means something to me as that is how I use flags in my coding.

You could call it monkey, pineapple, pickle or whatever you want.

I am just using it as a flag (TRUE or FALSE) that I am monitoring for as a condition of the button press.

Then setting/resetting the flag state when the button is released to prevent on/off during cycle time.

This is why I call it a one shot.

I train people and program Kawasaki for a living, so I have an underlying purpose not to provide solutions for free, but to provide some guidance and direction so that others can develop their own solutions.

Kawasaki AS Language is extremely powerful and flexible and due to this, creating your own solutions bespoke to your application is what you get paid for.........I don't when posting code, so I will only ever provide examples that can be viewed and may be offer some initial direction.

With AS Language, there are many ways to produce the same results, that's the flexibility and power of AS.

GOTO again

Lol.......Parentheses, now that was not intentional at all.......... good spot.......

I think you could build on what I've provided at least.

Attached is a full blown interface panel example which uses PC Tasks to manage and control.

So many possibilities available to 'make your own' and provide some nice bespoke functions.

Most of the push button operations use the above as a foundation for the operation they carry out.

The IFP is locked until a passcode is entered, along with interrupts, EAOT and cell peripheral operations as well as auto starting and out of position/step mismatch protection features.

In which conditions the lamps will go off?

Do you still have problem with the lamps?