CJ2 CPU Unit Software User's Manual - CIP ETI

Order of priority5 Understanding ProgrammingExample 1: Designing Tasks by Function and Personnel in Charge.Error processingCommunicationsMMIInitial processingMain processingConveyingInspectionAssemblyMachiningMaterials supplyPerson DPerson CPerson B part 2Person B part 1Person ABreak downby functionBreak downby processBreak down bypersonnel in chargeExample 2: Designing Tasks by Execution PriorityAllocate lower numbers to control tasks than to processing tasks.Break down by functionInterruptsExternal inputs• Break down and design programs to ensure autonomy. Keep the amount of data exchanged betweentasks to an absolute minimum.Organize the I/O memory used by all tasks and the I/O memory used only in individual tasks. Organizeand allocate a range of I/O memory for use only by each task.Used by All TasksInputprocessingOverallcontrol(mayincludeerrorprocessingin somecases)Break down by execution and non-execution conditionsD0 to D19999W0.0 to W199.15Error processingSequence controlAnalog controlMan-machine interfacingOutputprocessingExternal outputs55-2 Tasks5-2-4 Designing TasksTask 0 Task 1 Task 2D20000 to D24999W200.0 to W299.15D25000 to D29999W300.0 to W399.15D30000 to D31999W400.0 to W499.15DM AreaWork AreaD0 to D19999Used by all tasks.W0.0 to W199.15Used by all tasks.D20000 to D24999Task 0W200.0 to W299.15Task 0D25000 to D29999Task 1W300.0 to W399.15Task 1D30000 to D31999Task 2W400.0 to W499.15Task 2D32000 to D32767Not usedW500.0 to W511.15Not used• Use one task to start and stop other tasks and thus control the overall user program.Good Example: Define a master-slave relationship between tasks.Taskmanagement(master)Task 1 (slave)Task 2 (slave)Task 3 (slave)CJ2 CPU Unit Software User’s Manual5-29