ISPSoft User Manual
ISPSoft User Manual ISPSoft User Manual
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
- Page 332 and 333: Chapter 10 Instruction List The ope
- Page 334 and 335: Chapter 10 Instruction List • As
- Page 336 and 337: Chapter 10 Instruction List If user
- Page 338 and 339: Chapter 10 Instruction List Users
- Page 340 and 341: Chapter 10 Instruction List 10.2.4.
- Page 342 and 343: Chapter 11 Structured Text Table of
- Page 344 and 345: Chapter 11 Structured Text A comple
- Page 346 and 347: Chapter 11 Structured Text Data for
- Page 348 and 349: Chapter 11 Structured Text However,
- Page 350 and 351: Chapter 11 Structured Text Example
- Page 352 and 353: Chapter 11 Structured Text Example
- Page 354 and 355: Chapter 11 Structured Text Example
- Page 356 and 357: Chapter 11 Structured Text 11.2.5 L
- Page 358 and 359: Chapter 11 Structured Text 11.2.7 A
- Page 360 and 361: Chapter 11 Structured Text Example
- Page 362 and 363: Chapter 11 Structured Text larger t
- Page 364 and 365: Chapter 11 Structured Text 11.3.3 I
- Page 366 and 367: Chapter 11 Structured Text 11.4 Exa
- Page 368 and 369: Chapter 11 Structured Text Create t
- Page 370 and 371: Chapter 11 Structured Text which is
- Page 372 and 373: Chapter 12 Sequential Function Char
- Page 374 and 375: Chapter 12 Sequential Function Char
- Page 376 and 377: Chapter 12 Sequential Function Char
- Page 378 and 379: Chapter 12 Sequential Function Char
- Page 380 and 381: Chapter 12 Sequential Function Char
- Page 384 and 385: Chapter 12 Sequential Function Char
- Page 386 and 387: Chapter 12 Sequential Function Char
- Page 388 and 389: Chapter 12 Sequential Function Char
- Page 390 and 391: Chapter 12 Sequential Function Char
- Page 392 and 393: Chapter 12 Sequential Function Char
- Page 394 and 395: Chapter 12 Sequential Function Char
- Page 396 and 397: Chapter 12 Sequential Function Char
- Page 398 and 399: Chapter 12 Sequential Function Char
- Page 400 and 401: Chapter 12 Sequential Function Char
- Page 402 and 403: Chapter 12 Sequential Function Char
- Page 404 and 405: Chapter 12 Sequential Function Char
- Page 406 and 407: Chapter 12 Sequential Function Char
- Page 408 and 409: Chapter 12 Sequential Function Char
- Page 410 and 411: Chapter 12 Sequential Function Char
- Page 412 and 413: Chapter 13 Auxiliary Editing Tools
- Page 414 and 415: Chapter 13 Auxiliary Editing Tools
- Page 416 and 417: Chapter 13 Auxiliary Editing Tools
- Page 418 and 419: Chapter 13 Auxiliary Editing Tools
- Page 420 and 421: Chapter 13 Auxiliary Editing Tools
- Page 422 and 423: Chapter 13 Auxiliary Editing Tools
- Page 424 and 425: Chapter 13 Auxiliary Editing Tools
- Page 426 and 427: Chapter 13 Auxiliary Editing Tools
- Page 428 and 429: Chapter 13 Auxiliary Editing Tools
- Page 430 and 431: Chapter 13 Auxiliary Editing Tools
<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