ISPSoft User Manual

ISPSoft User Manual ISPSoft User Manual

02.09.2014 Views

Chapter 12 Sequential Function Chart transitions. Users can declare the step or the transition which is the destination of a jump in the global symbol table. When the condition of the jump is met, the step or the transition declared is set to ON. The condition of the jump can be created in an action. The figure below shows that SFC_A is executed first. SFC_B will be executed after SFC_A is executed, and SFC_A will be executed after SFC_B is executed. User can achieve the jumps by means of the characteristics of transitions. The steps SP_A and SP_B in the example below are used to express the sequential function chart which will be executed. They are preceded and followed by steps. Besides, the transitions RUN_A and RUN_B are declared in the global symbol table. When the program is executed, the step WAIT in SFC_A and the step WAIT in SFC_B are activated, and the action INITIALIZE associated with WAIT in SFC_A and the action INITIALIZE associated with WAIT in SFC_B are executed. INITIALIZE in SFC_A sets the transition RUN_A to ON during the first scan cycle, and therefore control is passed to SP_A. INITIALIZE in SFC_B sets the transition RUN_ B to OFF during the first scan cycle, and therefore control is not passed to SP_B. When the step JUMP in SFC_A is activated, the action associated with JUMP sets the transition RUN_B to ON, and resets RUN_A to OFF. When RUN_B is set to ON, control is passed to the step SP_B. Besides, the transition following JUMP in SFC_A is a special relay which is always ON, and therefore control is passed to the step WAIT. Owing to the fact that RUN_A is set to OFF, control is not passed to SP_A. RUN_A will not be set to ON until the action associated with JUMP in SFC_B is executed. The use of WAIT and JUMP in SFC_A serves to set RUN_B to ON, and the use of WAIT and JUMP in SFC_B serves to set RUN_A to ON. WAIT and JUMP in SFC_A and WAIT and JUMP in SFC_B actually have little significance. If the program is applied to an AH500 series CPU module, users can assign the qualifier P or P1 to the actions associated these steps. Please refer to section 12.2.6 for more information. 12-11

ISPSoft User Manual 12.2.6 Qualifier of an Action In ISPSoft, users can define the execution of an action by qualifying the action. However, users can not qualify the actions in the program in a DVP series PLC. Consequently, the actions in the program in a DVP series PLC are N actions. 12-12

<strong>ISPSoft</strong> <strong>User</strong> <strong>Manual</strong><br />

12.2.6 Qualifier of an Action<br />

In <strong>ISPSoft</strong>, users can define the execution of an action by qualifying the action. However, users can<br />

not qualify the actions in the program in a DVP series PLC. Consequently, the actions in the<br />

program in a DVP series PLC are N actions.<br />

12-12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!