Document Outline

• PLC Designer
  • Contents
  • 1 About this documentation
    • 1.1 Document history
    • 1.2 Conventions used
    • 1.3 Notes used
    • 1.4 Terminology used (presented according to the order in the device view)
  • 2 Safety instructions
  • 3 Requirements
    • 3.1 System requirements
    • 3.2 Establishing communication with the controller
  • 4 What is the ApplicationTemplate?
    • 4.1 Objective of the ApplicationTemplate
    • 4.2 Features of the ApplicationTemplate at a glance
    • 4.3 Elements of the ApplicationTemplate
      • 4.3.1 Machine Module Tree - MMT
      • 4.3.2 Machine modules (MM)
      • 4.3.3 Addressing the machine modules
      • 4.3.4 Module application (MAP)
      • 4.3.5 Communication between the machine modules
      • 4.3.6 State machine
      • 4.3.7 Error handling
  • 5 Structuring the automation system: Standard procedure
    • 5.1 Assign the relative address to the machine modules.
    • 5.2 Structuring within a machine module
      • 5.2.1 Assigning the MAP subfunctions to individual tasks
      • 5.2.2 Programming recommendations for structuring
  • 6 Overview - the structure of the ApplicationTemplate
  • 7 Opening the ApplicationTemplate
    • 7.1 Create a new project - open the ApplicationTemplate
    • 7.2 Update the controller in the project (optional)
    • 7.3 Going online
      • 7.3.1 Compiling the project data
      • 7.3.2 Transferring the project to the control - "Log in"
    • 7.4 Loading and starting the PLC program
    • 7.5 Simulation (valid for the ApplicationTemplateCounter)
    • 7.6 Getting started - operating the ApplicationTemplate
    • 7.7 Visualisation of the machine modules
  • 8 Working with the ApplicationTemplate
    • 8.1 Mapping the actual machine structure in the »PLC Designer«
      • 8.1.1 Adding devices - EtherCAT bus system
      • 8.1.2 Adding devices - CANopen bus system (optional)
    • 8.2 Creating your own machine modules: Copy/insertMM_EmptyModule
    • 8.3 Integrating a machine module into the MMT
    • 8.4 Assigning the module application (MAP) to the task
    • 8.5 Remove the instances of a machine module
    • 8.6 Removing machine modules
    • 8.7 Module ID
    • 8.8 Inserting an axis
    • 8.9 Integrating I/O modules of the I/O system 1000 with a machine module
    • 8.10 Creating module applications
      • 8.10.1 Adapting the function of the module application inserted - overview
      • 8.10.2 Frequently asked question: Connection between MFB and MAP
      • 8.10.3 Programming with the module application
      • 8.10.4 Integrating a module application
    • 8.11 Online change
      • 8.11.1 When can an "Online change" be used in the ApplicationTemplate?
      • 8.11.2 When is it not possible to use an "Online change" in the ApplicationTemplate?
      • 8.11.3 General programming recommendations which enable an "Online change"
  • 9 Architecture: The ApplicationTemplate in detail
    • 9.1 Accessing structure variables of machine modules
      • 9.1.1 Accessing module's intrinsic structure variables
      • 9.1.2 Accessing structures of other machine modules
    • 9.2 The AppChannelData structure(ACD)
      • 9.2.1 Declaring/recording the ACD structure in the MFB
      • 9.2.2 Accessing the ACD structure - by means of the MFB module application
      • 9.2.3 Accessing an ACD structure - by means of the module application of the MFB master module
    • 9.3 State machine
      • 9.3.1 State transitions and conditions - overview
      • 9.3.2 Initial state of the state transitions
      • 9.3.3 The state transitions in detail
      • 9.3.4 Mapping of the states - Enum L_EATP_SMStates
      • 9.3.5 Activating the states - baseChannelSetNominalState method
    • 9.4 Default coupling
      • 9.4.1 Standard mechanisms of the ApplicationTemplate
      • 9.4.2 The "DisableDefaultCouplingMaster" function
      • 9.4.3 The "DisableDefaultCouplingSlave" function
    • 9.5 Influencing state transitions
    • 9.6 Displaying the states of the state machine - FB L_EATP_SMAccess
    • 9.7 Stater machine: Query examples
    • 9.8 Where can the response of a machine module be programmed?
      • 9.8.1 State transition (state entry/state exit)
    • 9.9 Error handling
      • 9.9.1 Defining errors
      • 9.9.2 Configuring an error response
      • 9.9.3 Acknowledging errors
      • 9.9.4 Acknowledging errors: Response in the machine module
    • 9.10 Triggering errors
    • 9.11 Central error management in the ApplicationTemplate
    • 9.12 Export error overview of all machine modules: CSV file
    • 9.13 Logbook
    • 9.14 Module diagnostics
    • 9.15 Multitasking
    • 9.16 Consistent data transfer
    • 9.17 Internal Control
      • 9.17.1 Exiting the Internal Control
      • 9.17.2 What does the Internal Control do?
  • 10 Visualising in the ApplicationTemplate
    • 10.1 Extending the visualization
    • 10.2 Defining the properties of buttons
    • 10.3 Adding a visualization: Standard procedure
  • 11 The L_EATP_ApplicationTemplate library
    • 11.1 Automatically generated functions
      • 11.1.1 GetBooleanProperty (automatically generated by »PLC Designer«)
      • 11.1.2 GetCompany (automatically generated by »PLC Designer«)
      • 11.1.3 GetNumberProperty (automatically generated by »PLC Designer«)
      • 11.1.4 GetTextProperty (automatically generated by »PLC Designer«)
      • 11.1.5 GetTitle (automatically generated by »PLC Designer«)
      • 11.1.6 GetVersion (automatically generated by »PLC Designer«)
      • 11.1.7 GetVersionProperty (automatically generated by »PLC Designer«)
    • 11.2 1_POUs - Program Organization Units
      • 11.2.1 L_EATP_Application
      • 11.2.2 L_EATP_CriticalSection
      • 11.2.3 L_EATP_ErrorListHandler
      • 11.2.4 L_EATP_ErrorSet
        • 11.2.4.1 Adapting the error handling system
        • 11.2.4.2 Acknowledging errors
      • 11.2.5 L_EATP_Module
        • 11.2.5.1 Base()
      • 11.2.6 RegisterACD()
      • 11.2.7 setCompIDAndVersion()
      • 11.2.8 L_EATP_ModuleDiag
      • 11.2.9 L_EATP_ModuleErrorHandler
      • 11.2.10 L_EATP_ModulRelations
      • 11.2.11 L_EATP_SMAccess
    • 11.3 2_Structs_Types
      • 11.3.1 L_EATP_ACD_Base
      • 11.3.2 L_EATP_BaseChannel
      • 11.3.3 L_EATP_ErrorList
      • 11.3.4 L_EATP_ErrorListEntry
      • 11.3.5 L_EATP_MM_Address
      • 11.3.6 L_EATP_MVis
      • 11.3.7 L_EATP_scBase
    • 11.4 3_Enums
      • 11.4.1 L_EATP_ErrorReactionType
      • 11.4.2 L_EATP_SMStates
  • 12 Appendix
    • 12.1 Method overview - ApplicationTemplate
      • 12.1.1 Accessing the state machine - the methods of the BaseChannel
      • 12.1.2 Inhibiting/enabling module-specific state transitions
      • 12.1.3 Activate / deactivate quick stop response of the state machine
      • 12.1.4 Activating/deactivating default coupling
    • 12.2 The sample program in the ApplicationTemplateCounter
      • 12.2.1 Sample programs in the machine module MM_Module1/MM_Module2
        • 12.2.1.1 "Automatic" status
        • 12.2.1.2 "Mode1" status
        • 12.2.1.3 "Mode2" status
        • 12.2.1.4 "Service" status
        • 12.2.1.5 "Fault"/"System fault" status
      • 12.2.2 Sample program MM_Machine machine module
    • 12.3 Tips&tricks
      • 12.3.1 Renaming a machine module
      • 12.3.2 Next steps: Renaming the visualization buttons
    • 12.4 Recipe manager
      • 12.4.1 Precondition
      • 12.4.2 Creating the recipe definition
      • 12.4.3 Recipe definition - assigning variables
      • 12.4.4 Inserting recipes into a recipe definition
      • 12.4.5 Managing recipes with RecipeManCommands
        • 12.4.5.1 Create Recipe
        • 12.4.5.2 ReadAndSaveRecipeAs
        • 12.4.5.3 LoadFromAndWriteRecipe
        • 12.4.5.4 WriteRecipe
        • 12.4.5.5 ReadRecipe
        • 12.4.5.6 GetRecipeCount
  • 13 Application example: Flying saw
    • 13.1 Preparation: Modularising the automation system into subfunctions
      • 13.1.1 Identifying subfunctions of the machine structure
      • 13.1.2 Representing subfunctions of the machine structure as machine modules
      • 13.1.3 Representing machine modules in a tree structure
    • 13.2 Mapping the actual machine structure in the »PLC Designer«
      • 13.2.1 Device structure: Adding master and slave
      • 13.2.2 Setting the cycle time
    • 13.3 Creating and integrating machine modules
      • 13.3.1 Creating machine modules
      • 13.3.2 Integrating machine modules in the machine structure tree
      • 13.3.3 Managing module applications of the machine modules
      • 13.3.4 Inserting an axis into the module application
      • 13.3.5 Assigning the module application to the tasks
    • 13.4 Setting up communication between master modules and slave modules
    • 13.5 Application example: Extending the visualization
    • 13.6 State machine
      • 13.6.1 Controlling the state transition in the machine control module
      • 13.6.2 Controlling state transitions in the slave modules
    • 13.7 Manual jog of the axes
    • 13.8 Error handling: Configuring the error handling
  • Index
  • Your opinion is important to us