Library Motion Control SINAMICS LMCSINA

Transcription

1 Application example 04/2016 Library Motion Control SINAMICS LMCSINA SIMATIC S / SIMATIC S

2 Warranty and liability Warranty and liability Note The application examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these application examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications e.g. catalogs the contents of the other documentation have priority. We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this application example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these application examples or excerpts hereof is prohibited without the expressed consent of the Siemens AG. Security informati on Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions undergo continuous development. Siemens recommends that you keep yourself regularly informed about product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered. For further information about industrial security, visit To stay informed about product updates as they occur, sign up for a productspecific newsletter. For further information, visit LMCSINA Library Entry ID: , V2.3, 04/2016 2

3 Table of contents Warranty and liability Preface Control blocks that are available Interfacing the synchronous applications to SIMATIC using LMCSINA_AxisFB... 6 Hardware and software requirements Interfacing the cross-cutter to the SIMATIC with LMCSINA_CrossCutterFB... 8 Hardware and software requirements Connecting the flying saw to the SIMATIC with LMCSINA_FlyingSawFB Hardware and software requirements Configuring in STARTER Configuring the drive functionality Configuring the communication Preparation and telegram selection Creating the telegram interconnections Script integrated in Starter Using the script integrated in the project Setting the user-defined GSDML for the TIA Portal Continuing commissioning LMCSINA_AxisFB in the TIA Portal Preparation Installing the GSDML file generated in the TIA Portal Finding the GSDML in the hardware catalog Commissioningsteps Integrating the acyclic communication Interfaces Block interfaces LMCSina_AxisFB LMCSina_VirtualMaster block interfaces Overview of values for the output status Configuration data Operation Enabling blocks Selecting functions Switching between functions Post triggering Reading and writing configuration data Checking the entry ID LMCSINA_CrossCutterFB in the TIA Portal Preparation Installing the GSDML file generated in the TIA Portal Finding the GSDML in the hardware catalog Commissioning TIA Portal Integrating the acyclic communication LMCSINA_CrossCutterFB interfaces Block inputs Block outputs Value overview for the output status Operation Enabling the block LMCSINA Library Entry ID: , V2.3, 04/2016 3

4 5.4.2 Reading configuration data LMCSINA_FlyingSawFB in the TIA Portal Preparation Installing the GSDML file generated in the TIA Portal Finding the GSDML in the hardware catalog Commissioning TIA Portal Integrating the acyclic communication LMCSINA_FlyingSawFB interfaces Block inputs Block outputs Value overview for the output status Operation Enabling the block Reading configuration data LMCSINA_WinderFB in the TIA Portal References History Contact partner LMCSINA Library Entry ID: , V2.3, 04/2016 4

5 1 Preface The SIMATIC library "Library Motion Control SINAMICS" allows the comprehensive motion control functions in the SINAMICS S120 to be controlled in a user-friendly and convenient fashion. The synchronous applications of the SINAMICS S120 and the technological applications for flying saws and cross-cutters based on DCB- Extension are supported. The library can be used with a SIMATIC S as well as with a SIMATIC S Control is possible via PROFINET or PROFIBUS- DP. The following applications are supported: Camming with gearbox and positioning Gearing and positioning Gearing 1:1 synchronous operation Positioning without synchronous operation Linear flying saws with DCB-Extension Cross-cutters with DCB-Extension V2.3 04/2016 5/77

6 2 Control blocks that are available 2.1 Interfacing the synchronous applications to SIMATIC using LMCSINA_AxisFB The Library Motion Control SINAMICS abbreviated LMCSINA includes the control of the synchronous applications for SINAMICS S120 based on DCB- Extension. Synchronous operation technology is implemented in the drive using a DCB library and appropriately programmed and configured DCB blocks. The synchronous axis also called slave in the following from a SIMATIC S7-1x00 is controlled by a user-defined block: LMCSINA_AxisFB. In conjunction with the LMCSINA_AxisFB block, there is also an additional function block to control a virtual master axis: LMCSINA_VirtualMaster. As it is necessary to acyclically transfer application parameters due to the inherent system features, in the LMCSINA_AxisFB block, acyclic tasks are externally integrated and executed. The integration is realized using UDT LacycCom_typeSilentOperation and allows the LMCSINA_AxisFB block to execute acyclic communications using the LacycCom_ReadDriveParam, LacycCom_WriteDriveParam and the LacycCom_Buffermanager blocks. Data is exchanged via IN/OUT data areas of the global axis data block to be generated based on the UDT LMCSINA_TypeAxisData. As a result of this interaction, when necessary the application can be operated with or without acyclic services. In the case that there is no acyclic communication, the user must make the appropriate changes in the application or the global data block. V2.3 04/2016 6/77

7 Hardware and software requirements Table 2-1 SIMATIC S7-15xx SIMATIC S7-12xx TIA Portal Step7 Component TIA Portal Step7 professional license SINAMICS S120 drive lineup with CU320-2 control module Starter commissioning tool with installed DCC (Optional with DCC engineering license to adapt the DCC charts) SINAMICS DCB Extension runtime license for each CU Block library for motion control Block library for extended mathematical functions DCC chart for synchronous functionality in the drive (camming/gearing/ ) From V1.6 and higher From V4.1 and higher Note From V13 SP1 and higher From V13 SP1 and higher From firmware 4.7 and higher From V4.4 and higher MLFB 6SL3077-0AA00-0AB0 (RT license for CU, licensing, see the following note) From GMCV3_1_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device From math_extendedv1_0_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device The matching DCC charts are available as XML export under the particular application in SIOS _LIB_v2.1.zip The library and the script files to support commissioning are provided in this zip file. Note The Web License Manager is used to subsequently license the "SINAMICS DCB Extension" runtime license to run the new DCC libraries on the CU. You can find a description in the Function Manual FH1 under "Basic information about the drive system -> Licensing -> Creating or displaying license keys via the WEB License Manager". V2.3 04/2016 7/77

8 2.2 Interfacing the cross-cutter to the SIMATIC with LMCSINA_CrossCutterFB The Library Motion Control SINAMICS abbreviated LMCSINA includes the control of the GMC technological applications, which are based on DCC. The technology is implemented in the drive using a DCB library and appropriately programmed and configured DCB blocks. The cross-cutter drive from a SIMATIC S7-1200/1500 is controlled by a userdefined block: LMCSINA_CrossCutterFB. As it is necessary to acyclically transfer application parameters due to the inherent system features, in the LMCSINA_ CrossCutterFB block, acyclic tasks are externally integrated and executed. The integration is realized using UDT LAcycCom_typeSilentOperation and allows the LMSINA_ CrossCutterFB block to acyclically read data using the LAcycCom_ReadDriveParam and the LAcycCom_Buffermanager blocks. Data is exchanged via the statacyclicdata data area of the instance data block of LMCSINA_CrossCutterFB. As a result of this interaction, when necessary the application can be operated with or without acyclic services. In the case that there is no acyclic communication, the user must manually make the appropriate changes in the application or the global data block. V2.3 04/2016 8/77

9 Hardware and software requirements Table 2-2 SIMATIC S7-15xx SIMATIC S7-12xx TIA Portal Step7 Component TIA Portal Step7 professional license SINAMICS S120 drive lineup with CU320-2 control module Starter commissioning tool with installed DCC (Optional with DCC engineering license to adapt the DCC charts) SINAMICS DCB Extension runtime license for each CU Block library for motion control Block library for extended mathematical functions DCC chart for the cross-cutter drive and its leading value source (measuring wheel/leading axis) From V1.6 and higher From V4.1 and higher Note From V13 SP1 and higher From V13 SP1 and higher From firmware 4.7 and higher From V4.4 and higher MLFB 6SL3077-0AA00-0AB0 (RT license for CU, licensing, see the following note) From GMCV3_1_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device From math_extendedv1_0_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device The matching DCC charts are available as XML export under the particular application in SIOS _LIB_v2.1.zip The library and the script files to support commissioning are provided in this zip file. Note The Web License Manager is used to subsequently license the "SINAMICS DCB Extension" runtime license to run the new DCC libraries on the CU. You can find a description in the Function Manual FH1 under "Basic information about the drive system -> Licensing -> Creating or displaying license keys via the WEB License Manager". V2.3 04/2016 9/77

10 2.3 Connecting the flying saw to the SIMATIC with LMCSINA_FlyingSawFB The Library Motion Control SINAMICS abbreviated LMCSINA includes the control of the GMC technological applications, which are based on DCC. The technology is implemented in the drive using a DCB library and appropriately programmed and configured DCB blocks. A user-defined user block controls the saw drive from a SIMATIC S7-1200/1500: LMCSINA_FlyingSawFB. As a result of the system-related necessity to transfer application parameters acyclically, in the LMCSINA_ FlyingSawFB block, execution of acyclic tasks is externally integrated and implemented. The integration is realized using UDT LAcycCom_typeSilentOperation and allows the block LMCSINA_ FlyingSawFB to acyclically read using blocks LAcycCom_ReadDriveParam and LAcycCom_Buffermanager. Data exchange is realized via the data area statacyclicdata of the instance data block of LMCSINA_FlyingSawFB. As a result of this interaction, when necessary the application can be operated with or without acyclic services. In the case that there is no acyclic communication, the user must manually make the appropriate changes in the application or the global data block. V2.3 04/ /77

11 Hardware and software requirements Table 2-3 SIMATIC S7-15xx SIMATIC S7-12xx TIA Portal Step7 Component TIA Portal Step7 professional license SINAMICS S120 drive lineup with CU320-2 control module Starter commissioning tool with installed DCC (Optional with DCC engineering license to adapt the DCC charts) SINAMICS DCB Extension runtime license for each CU Block library for motion control Block library for extended mathematical functions DCC chart for the saw drive and its leading value source (measuring wheel/leading axis) From V1.6 and higher From V4.1 and higher Note From V13 SP1 and higher From V13 SP1 and higher From firmware 4.7 and higher From V4.4 and higher MLFB 6SL3077-0AA00-0AB0 (RT license for CU, licensing, see the following note) From GMCV3_1_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device From math_extendedv1_0_sinamics4_7.zip This library should be installed in Starter and then loaded to the drive device The matching DCC charts are available as XML export under the particular application in SIOS _LIB_v2.1.zip The library and the script files to support commissioning are provided in this zip file. Note The Web License Manager is used to subsequently license the "SINAMICS DCB Extension" runtime license to run the new DCC libraries on the CU. You can find a description in the Function Manual FH1 under "Basic information about the drive system -> Licensing -> Creating or displaying license keys via the WEB License Manager". V2.3 04/ /77

12 3 Configuring in STARTER 3.1 Configuring the drive functionality The drives must be configured and parameterized in Starter, as the actual motion control functionality, both for the synchronous applications as well as for crosscutter and flying saw, are directly realized in the drive. Detailed step-by-step instructions are provided in the commissioning chapter of the application itself. The basic steps are again shown in the following. Basic configuration steps 1. Install the necessary DCB libraries in STARTER/SCOUT, and load to the drive device 2. Create the drives as usual (without EPOS function module!) 3. Activate the position controllers on the axes 4. Parameterize the mechanical system of the axes 5. Import the appropriate DCC charts (and save/compile) 6. Parameterize the basic motion control functionality, geometry of the system etc. 7. If required, configure the communication (see Chapter 3.2) V2.3 04/ /77

13 3.2 Configuring the communication Preparation and telegram selection When selecting the telegram of the axes to be controlled, "[999] Free telegram configuring with BICO" must be selected. If a standard telegram was active beforehand, reset the parameters on the axis by setting p10 = 30. The length of the input data/actual values and output values/setpoints should both be set to 20: Fig. 3-1 NOTICE Undesirable axis motion as a result of incorrect telegram settings If a telegram configuration other than "[999] Free telegram configuring with BICO" is set, even after running the commissioning script, incorrect BICO interconnections will continue to exist. Depending on the previous telegram selection, this can result in incorrect and undesirable axis motion. The synchronous application is linked to the higher-level SIMATIC control using a user-defined telegram with a 20/20 length for the send and receive areas. V2.3 04/ /77

14 3.2.2 Creating the telegram interconnections Executable script files are supplied for the particular applications to create the telegram interconnection. You will find the script that matches the particular application in the following table. Table 3-1 Application used Synchronous applications: - Camming - Gearing with positioning - Gearing - 1:1 synchronous operation - Positioning Cross cutter Flying saw Script file required LMCSINA_Synchronism_CommunicationScript (.txt/.xml) LMCSINA_Technology_CommunicationScript (.txt/.xml) LMCSINA_Technology_CommunicationScript (.txt/.xml) The script files supplied for the applications to establish the appropriate telegram interconnection can either be incorporated in Starter (from Starter version V ) or in the project itself. For all of the scripts mentioned above, the integration and execution is identical. The two versions for possible integration and execution are described in the following. V2.3 04/ /77

15 Script integrated in Starter With this version, the script is available in all drive projects with the matching device versions. However, in this case, the script is not archived with the project. This version makes sense if you frequently wish to commission similar projects with an unchanged script. To do this, proceed as follows: Copy the script file provided (*.txt) to the installation directory of Starter in the following file structure (in this case, with "C:\Program Files" as installation folder, for example): "C:\Program Files (x86)\siemens\step7\u7umc\data\scripts\device_configurations\v4.7\sinamic S_S120" The saved scripts can now be selected in the configuration screen form of the drive via "Configuration scripts": Fig. 3-2 V2.3 04/ /77

16 In the dialog that opens, select the appropriate script, and click on "Execute". Fig. 3-3 Follow the instructions of the script V2.3 04/ /77

17 Using the script integrated in the project With this version, you must import the script into every project where you wish to use it. However, the script remains integrated, even when archiving and transferring the project. This version especially makes sense if you wish to make your own project-specific modifications to the script. To do this, proceed as follows: Insert a script folder at the project level Fig. 3-4 V2.3 04/ /77

18 Import the interconnection script (*.xml) Fig. 3-5 "Accept and execute" the script Figure 3-6 Follow the instructions of the script Please refer to the documentation of the particular application for additional parameter settings V2.3 04/ /77

19 Note Valid for synchronous applications (not for cross-cutters/flying saws): The µm/lu resolution is defined in parameter p This is necessary in order that the setpoint can be entered in SIMATIC in [mm] / [m ]. The value is 1µm = 1LU as default setting. V2.3 04/ /77

20 3.2.3 Setting the user-defined GSDML for the TIA Portal If you are using a PROFIBUS drive, then a GSDML file does not have to be created in STARTER. The standard GSDs for PROFIBUS can be subsequently used in the TIA Portal. Proceed as follows if you wish to use a PROFINET drive: Note When using PROFINET when integrating into the TIA portal it is necessary to create a user-defined GSDML for the TIA Portal. The standard GSDML of the SINAMICS S120 does not include a 20/20 telegram; however this is required for creating the user-defined GSDML file. Create the user-defined GSDML file for your drive device using the following Starter script (script and detailed description are available at the following link): When executed, the script automatically creates the user-defined GSDML file, which can be subsequently installed in the TIA Portal. Continuing commissioning The next steps involve commissioning the communication and control in the TIA Portal. Proceed with the following chapter depending on the application being used: Table 3-2 Application used Synchronous applications: - Camming - Gearing with positioning - Gearing - 1:1 synchronous operation - Positioning Cross cutter Flying saw continue with commissioning Chapter number Chapter4 Chapter5 Chapter6 V2.3 04/ /77

21 4 LMCSINA_AxisFB in the TIA Portal After you have configured the drive according to Chapter 3, then the communication to the higher-level control is configured in the TIA Portal. 4.1 Preparation If you wish to configure a PROFIBUS a device, then you can continue with Chapter 4.2. If you wish to configure a PROFINET device, then this is done using the userdefined GSDML file. How you can install this GSDML file is described in the following, and where you can then find it in the hardware catalog. Installing the GSDML file generated in the TIA Portal Install the user-defined GSDML file that you generated in the TIA Portal as follows: Fig. 4-1 Fig. 4-2 V2.3 04/ /77

22 Finding the GSDML in the hardware catalog The GSDML file can now be found in the folder structure of the hardware catalog as shown in the following diagram. Fig. 4-3 V2.3 04/ /77

23 4.2 Commissioningsteps Configuring the control Create a SIMATIC S7-1200/1500 control, and then configure it as usual. Note A minimum firmware release of 4.0 is required for the SIMATIC S This is necessary to use the blocks from "LAcycCom" for acyclic communication. Integrating the drive The following's steps describe the procedure when creating the drives and the control blocks. 1. Integrating the SINAMICS drive into the network view a. PROFIBUS: Use the existing GSD files b. PROFINET: Use the user-defined GSDML file that has been installed 2. Connect the drive to the control system Fig. 4-4 V2.3 04/ /77

24 Integrating the LMCSINA library 3. Dearchive the global LMCSINA library by right clicking in the global libraries. Fig. 4-5 Copy all of the required library elements into the folder of the control system Now copy all of the required library files into the appropriate folder of the created control system (carefully observe the sequence of steps!) 4. Copy "LAcycCom_Drives" from "01_Necessary components" to the PLC variables folder 5. Copy "LAcycCom_typeSilentOperation" from "01_Necessary components" to the PLC data types folder 6. Copy "LMCSINA_TypeAxisData"- including all additional LMCSINA types from "LMCSINA_02_Synchronism" "LMCSINA_Types" to the PLC data types 7. Copy function blocks "LMCSINA_AxisFB", "LMCSINA_VirtualMasterFB" (when using the virtual leading axis in the drive) to the PLC program blocks. Further, the block folder contains two data block examples, type "LMCSINA_TypeAxisData", which can also be used. Note The reason for the different block folder for S and S is as follows: The blocks for the S are set to "optimized access", the blocks for the S7-1200, are set to "not optimized". As far as the program code is concerned, both blocks are identical. V2.3 04/ /77

25 Fig NOTICE Avoid creating an invalid array of structs! Problem: If a data type/block is transferred into the PLC, and is compiled before accepting the PLC variables/user constants provided, then an invalid array with "0" structures is created. Remedy: The PLC variables must be completely accepted before compiling the PLC/program. This is necessary, as in the data types/blocks used, array limits are defined based on constants. V2.3 04/ /77

26 Calling block LMCSINA_AxisFB Calling axisfb "LMCSINA_AxisFB" with an instance for each synchronous axes (with or without a virtual leading axis). Interconnecting inputs and outputs. Note The following inputs must (mandatory) be interconnected in order to call the function block: enable (the block is only calculated for TRUE) hardwareid (can be found under PLC variables system constants) driveobjectno (can be found in the properties of the drive object in STARTER) axisdata (at this location, either the global data block, type LMCSINA_TypeAxisData or a variable, type LMCSINA_TypeAxisData is interconnected) The block itself can now be simply compiled. Additional steps are required to use acyclic communication (see the next chapter) V2.3 04/ /77

27 Fig. 4-7 V2.3 04/ /77

28 Creating a global axis data block A global data block is required for each instance of an LMCSINA_AxisFB Create a global data block, either type "LMCSINA_TypeAxisData" or with a variable, type "LMCSINA_TypeAxisData". For the first version, the DB structure is fixed; for the second version, date can be added to the DB. Calling block LMCSINA_VirtualMaster Calling FB "LMCSINA_VirtualMaster" with an instance for each virtual leading axis Each FB LMCSINA_VirtualMaster requires a corresponding axis FB, as this in turn, executes the cyclic/acyclic communication. Data is exchanged between these 2 FBs using global data block/variable, type "LMCSINA_TypeAxisData" Interconnecting inputs and outputs. Note The following inputs must (mandatory) be interconnected in order to call the function block: enable (the block is only calculated for TRUE) axisdata (at this location, either the global data block, type LMCSINA_TypeAxisData or a variable, type LMCSINA_TypeAxisData is interconnected) The global data block/variable, type LMCSINA_TypeAxisData must be assigned a LMCSINA_AxisFB block The block itself can now be simply compiled. Additional steps are required to use acyclic communication (see the next chapter) V2.3 04/ /77

29 Fig. 4-8 Integrating the acyclic communication Note The function block can also be used without acyclic communication. The default values in the FB correspond to the default values in the drive parameters. 1. Opening/dearchiving the global "LAcycCom" block 2. Copy all data types from LAcycCom 00 Common Resources Management LAcycCom_Types to the PLC data types 3. (Depending on the particular control system) copy the PLC variables LAcycCom 00 Common Resources Management to the PLC folder 4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 00 Common Resources Management to the folder of the control system used to the program blocks 5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 00 Common Resources Management to the PLC folder V2.3 04/ /77

30 Fig Copy function block "LAcycCom_ ReadDriveParams", "LAcycCom_ WriteDriveParams" from LAcycCom 01 Drives LAcycCom_Blocks PROFIDrive to the PLC folder 7. Copy all data types except "LAcycCom_typeSilentOperation" from LAcycCom 01 Drives LAcycCom_Types to PLC data types Note Data type "LAcycCom_typeSilentOperation", as a result of the use in the LMCSINA environment, is also supplied there and must therefore be integrated into the project ONCE. When not complied with, the TIA portal changes the comments of a data type, which can result in problems when compiling. PLC variables "LAcycCom_Drives" should also exist in the project, and should therefore not be integrated another time. V2.3 04/ /77

31 Figure Call function blocks "LAcycCom_ResourceManager" and "LAcycCom_ReadDriveParams" in the (same) program block 9. Interconnect LAcycCom_RequestBuffer to input "globalbuffer" of "LAcycCom_ResourceManager" block 10. Activation of LAcycCom_ResourceManager at input "enable" 11. Interconnect LAcycCom_RequestBuffer at input "globalbuffer" of block "LAcycCom_ReadDriveParams" as well as "LAcycCom_WriteDriveParams" 12. Interconnect data area "statacyclicdata" from the global data block of the synchronous axes to input "dataset" of block "LAcycCom_ReadDriveParams" as well as "LAcycCom_WriteDriveParams" V2.3 04/ /77

32 Table 4-1 Fig V2.3 04/ /77

33 Note Block LAcycCom_ResourceManager must be released at input "enable". Blocks LAcycCom_ReadDriveParams, LAcycCom_WriteDriveParams are exclusively controlled via input "dataset". V2.3 04/ /77

34 4.3 Interfaces Block interfaces LMCSina_AxisFB Table 4-2 Designation Type Data type Description Enable IN BOOL TRUE: Activation of the FB ackerror IN BOOL TRUE: Acknowledging errors of the FB and the drive enableaxis IN BOOL TRUE: Set axis enable FALSE: Remove axis enable jogpositive IN BOOL TRUE: jog forward FALSE: stop jog jognegative IN BOOL TRUE: jog backward FALSE: stop jog Pos IN BOOL rising edge: position axis Homing IN BOOL rising edge: Home/reference axis Stop IN BOOL TRUE: stop axis, axis is blocked for other commands gearin IN BOOL rising edge: synchronize gearing gearout IN BOOL rising edge: Synchronize gearing camin IN BOOL rising edge: synchronize camming camout IN BOOL rising edge: desynchronize camming Phasing IN BOOL rising edge: Insert an offset between master and slave or delete the existing offset printmarkcorrection IN BOOL TRUE: Enable print mark correction FALSE: Deselect print mark correction openbrake IN BOOL TRUE: Only open the brake if the axis is not enabled V2.3 04/ /77

35 Designation Type Data type Description FALSE: Close brake readwriteconfigdata IN USInt 0: No read or write; 0->1: read out the drive configuration data (for the drive that has not been released) 0->2: write the configuration data to drive (for the drive that has not been released) valid OUT BOOL TRUE: outputs valid at the block busy OUT BOOL TRUE: block is being processed error OUT BOOL TRUE: block error axiserror OUT BOOL TRUE: drive or application fault commandbusy OUT BOOL TRUE: blocks for processing off commanddone OUT BOOL TRUE: processing completed resetactive OUT BOOL TRUE: rising edge for ackerror occurred ReadWriteSelected OUT BOOL TRUE: reading or writing configuration data active or completed axisenabled OUT BOOL TRUE: the axis is enabled FALSE: axis is not enabled jogpositiveselected OUT BOOL TRUE: axis jogs in positive direction jognegativeselected OUT BOOL TRUE: axis jogs in negative direction posselected OUT BOOL TRUE: axis positioned, or positioning completed homingselected OUT BOOL TRUE: homing/referencing active or completed stopselected OUT BOOL TRUE: stop active or completed gearinselected OUT BOOL TRUE: synchronize gearing active or completed V2.3 04/ /77

36 Designation Type Data type Description gearoutselected OUT BOOL TRUE: desynchronize gearing active or completed caminselected OUT BOOL TRUE: synchronize camming active or completed gearoutselected OUT BOOL TRUE: desynchronize camming active or completed phasingselected OUT BOOL TRUE: phasing active or completed printmarkcorrectionactive OUT BOOL TRUE: print mark correction selected in the drive axishomed OUT BOOL TRUE: axis homed/referenced axisinposition OUT BOOL TRUE: axis is located within the positioning window axisstandstill OUT BOOL TRUE: axis stationery (speed low threshold value) axisinsync OUT BOOL TRUE: the axis is in synchronism FALSE: axis is not in synchronism offsetactive OUT BOOL TRUE: offset available axisinvelocity OUT BOOL TRUE: positioning or jog velocity reached brakeopen OUT BOOL TRUE: brake is open MasterValue OUT USINT 1: leading value 1 active 2: leading value 2 active actualposition OUT REAL actual position [mm] actualvelocity OUT REAL actual velocity [mm/s] status OUT WORD actual status of the FB axisdata IN/OUT LMCSINA_ AxisDataTy Structure for configuration data of the axis V2.3 04/ /77

37 Designation Type Data type Description pe LMCSina_VirtualMaster block interfaces Table 4-3 Designation Type Data type Description enable IN BOOL TRUE: Activation of the FB jogpositive IN BOOL jognegative IN BOOL TRUE: jog forward FALSE: stop jog TRUE: jog backward FALSE: stop jog pos IN BOOL rising edge: position axis stop IN BOOL TRUE: stop axis, axis is blocked for other commands set IN BOOL rising edge: enable setting value valid OUT BOOL TRUE: outputs valid at the block busy OUT BOOL TRUE: block is being processed error OUT BOOL TRUE: block error commandbusy OUT BOOL TRUE: blocks for processing off commanddone OUT BOOL TRUE: processing completed jogpositiveselected OUT BOOL TRUE: axis jogs in positive direction jognegativeselected OUT BOOL TRUE: axis jogs in negative direction posselected OUT BOOL TRUE: axis positioned, or positioning completed setselected OUT BOOL TRUE: setting value activated stopselected OUT BOOL TRUE: stop active or completed axisinposition OUT BOOL Structure for configuration data of the axis actualposition OUT REAL actual position [mm] actualvelocity OUT REAL actual velocity [mm/s] Status OUT WORD actual status of the FB axisdata IN/OUT LMCSINA _AxisData Type Structure for configuration data of the axis V2.3 04/ /77

38 4.3.3 Overview of values for the output status Incorrect operation of the function block 8101 Axis not homed 8102 Command is not possible: 8103 Incorrect entry ID or entry ID is "0" Error in the parameter assignment 8200 Pos direction not valid 8201 Pos velocity at limit 8210 homingmode not valid 8211 homingconfig not valid 8220 gearinmode not valid 8221 gearin syncmode not valid 8230 caminmode 8231 camin syncmode 8232 camnumber 8240 phasing motiondirection 8250 leadingvalue 8251 leadingvalue motiondirection 8260 Resolution µm/lu <= acyclic communication not available Faults when executing from outside 8400 Drive alarm 8401 Drive fault 8402 Fault DCC Faults when executing from the inside 8600 DPRD_DAT fault 8610 DPWR_DAT fault 8620 no connection LMCSinaVirtualMaster to LMCSinaAxisFB LDPV1_WRITE_PARAMETERS_UPPER_LIM as constant has a value that is not equal to Set this value to 18 for compatibility reasons. V2.3 04/ /77

39 4.3.4 Configuration data The individual functions are parameterized in the configuration data. In some instances, the elements are pure setting values for the FB. These can always be changed. The values are accepted with the next "Execute". The setting values, which are based on the parameters of the DCC synchronous application, cannot be changed in operation. Using "readwriteconfigdata", they can be read from the drive, or written to the drive if the drive has not been enabled. These values are marked in the comment with "n.c.". Marking "r.o." means that this value is only read, but not written to. LMCSina_AxisDataType elements Table 4-4 Elements of LMCSina_AxisDataType Designation Data type Description posdata PosDataType Structure for parameterizing positioning functionality homingdata HomingDataType Structure for parameterizing homing functionality jogdata JogDataType Structure for parameterizing jogging functionality stopdata StopDataType Structure for parameterizing stopping functionality gearingdata GearingDataType Structure for parameterizing gearing functionality cammingdata CammingDataType Structure for parameterizing camming functionality phasingdata PhasingDataType Structure for parameterizing the offset input to a synchronized operation diagnosticdata DiagnosticDataType Structure to output diagnostic values drivedata DriveDataType Structure for parameterizing general drive parameters leadingvaluedata LeadingValueDataType Structure for parameterizing leading value switchover printmarkcorrectiondata PrintMarkCorrectionDataType Structure for parameterizing print mark correction virtualmasterdatatype VirtualMasterDataType Structure for parameterizing virtual leading axis silentoperationdata LDPV1_SilentOperationType Structure to connect LDPV1 functions V2.3 04/ /77

40 PosDataType elements Table 4-5 PosDataType elements Designation Data type Default Description Position Real 0.0 position / distance [mm] velocity Real 0.0 velocity [mm/s] acceleration Real n.c. max. acceleration [mm/s²] p21932 jerk Real n.c. max. jerk [mm/s³] / 0.0 = trapezial p21934 direction USInt 3 NEGATIVE (1) / POSITIVE (2) / SHORTEST_WAY (3) posabsolute Bool false select absolute positioning HomingDataType elements Table 4-6 HomingDataType elements Designation Data type Default Description homingmode USInt 1 ACTIVE (1), ACTIVE_WITHOUT_BERO(2), PASSIVE (3), ADJUST_ABSOLUTE_ENCODER (4) homingconfig USInt 1 PosDir_PosEdge(1), PosDir_NegEdge(2), NegDir_NegEdge(3), NegDir_PosEdge(4), homeposition Real 0.0 n.c. p21639 positionafterhoming Real 0.0 n.c. position after active homing p21641 velocitytobero Real 50.0 n.c. Velocity homing up to the Bero proximity switch p21637 velocityafterbero Real 25.0 n.c. Velocity homing after the Bero proximity switch p21638 JogDataType elements Table 4-7 JogDataType elements Designation Data type Default Description velocity Real n.c. p21950 StopDataType elements Table 4-8 StopDataType elements Designation Data type Default Description deceleration Real n.c. p23711 jerk Real n.c. p23712 V2.3 04/ /77

41 GearingDataType elements Table 4-9 GearingDataType elements Designation Data type Default Description gearinmode USInt 0 CATCH_UP_WITH_STOP_IMMEDIATELY: (0); CATCH_UP_WITH_STOP_AT_POSITION: (1); ENGAGE_FIXED_LENGTH_TRIGGER: (2); ENGAGE_FIXED_LENGTH_CONTINUOUS:(3); DISENGAGE_FIXED_LENGTH_TRIGGER: (4); DISENGAGE_FIXED_LENGTH_CONTINUOUS:(5) absolute Bool false (0-1) sync on Master absolute maxvelocity Real n.c. (0-1) max. sync. velocity [mm/s] p22101 maxacceleration Real n.c. (0-1) max. sync. acceleration/deceleration [mm/s²] p22102 maxjerk Real n.c. (0-1) max. sync. jerk [mm/s³] / 0.0 = trapezial p22103 syncmode USInt 4 (0-1) POSITIVE: (1); NEGATIVE: (2); SHORTEST_WAY: (3); OVERRIDE: (4) phaseshift Real 0.0 n.c. (0-1) Sets a fixed offset setpoint between the leading axis and following axis for catching up with synchronization. p22140 stopposition Real 0.0 n.c. (0-1) Sets the fixed stopping position for stopping with specified engaging position. p22150 coupleposition Real 0.0 n.c. (2-5) Sets the fixed coupling position for engaging/disengaging. p22210 length Real 10.0 n.c. (2-5) Sets the fixed engaging/disengaging length. p22220 ramplength Real 0.0 n.c. (2-5) Sets the acceleration ramp for engaging/disengaging. p22230 percentageacceleratingramp Real 10.0 n.c. (2-5) Sets the rounding. p22231 V2.3 04/ /77

42 CammingDataType elements Table 4-10 CammingDataType elements Designation Data type Default Description camnumber USInt 1 1: Cam1 / 2: Cam2 caminmode USInt 0 CATCH_UP_WITH_STOP_IMMEDIATELY: (0); CATCH_UP_WITH_STOP_AT_POSITION: (1) velocity Real n.c. Value in gearingdata active acceleration Real 50.0 n.c. Value in gearingdata active jerk Real n.c. Value in gearingdata active syncmode USInt 4 POSITIVE: (1); NEGATIVE: (2); SHORTEST_WAY: (3); OVERRIDE: (4) phaseshift Real 0.0 n.c. Value in gearingdata active stopposition Real 0.0 n.c. Value in gearingdata active masterabsolute Bool true sync on Master absolute camabsolute Bool true cam absolute/relative output PhasingDataType elements Table 4-11 PhasingDataType elements Designation Data type Default Description offset Real 0.0 n.c. offset [mm] p23401 absolute Bool false offset absolute/relative (true = absolute) deleteoffset Bool false true = delete offset motiondirection USInt 3 NEGATIVE (1) / POSITIVE (2) / SHORTEST_WAY (3) velocity Real n.c. max. sync. velocity [mm/s] p23740 acceleration Real n.c. max. sync. acceleration/deceleration [mm/s²] p23741 jerk Real n.c. max. sync. jerk [mm/s³] / 0.0 = trapezial p23742 DiagnosticDataType elements Table 4-12 DiagnosticDataType elements Designation Data type Default Description ActualAlarmCode UInt 0 c.c. - r2132 actual drive warn code ActualFaultCode UInt 0 c.c. - r2131 actual drive fault code DPRD_DAT_RET_VAL Word 16#0 return value for function block DPRD_DAT DPWR_DAT_RET_VAL Word 16#0 return value for function block DPWR_DAT HWIDact UInt 0 actual used hardware ID for cyclic / acyclic operation V2.3 04/ /77

43 DriveDataType elements Table 4-13 DriveDataType elements Designation Data type Default Description HW-ID Word 16#0 Hardware identifier (PLC) DO-Number USInt 0 drive object number (DRIVE) App-ID DInt 0 r.o. App-ID of the application r21502 resolution [µm/lu] Real 1.0 n.c. p21660 ACL_leadingAxis Real n.c.sets the axis cycle length of the leading axis. p21650 ACL_camInput Real n.c.sets the axis cycle length at the cam input. p21651 ACL_camOutput Real n.c. Sets the axis cycle length at the cam output. p21652 ACL_followingAxis Real n.c.sets the axis cycle length of the following axis. p21653 maxspeedpos Real n.c. p21930 [mm/s] numeratorgear1 DInt 1 n.c. p22301 denominatorgear1 DInt 1 n.c. p22302 numeratorgear2 DInt 1 n.c. p22311 denominatorgear2 DInt 1 n.c. p22312 encoderidentification USInt 0 LeadingValueDataType elements Table 4-14 LeadingValueDataType elements r.o. "UNKNOWN (0): ABSOLUTE_ENCODER (1): INCREMENTAL_ENCODER (2): p404[0].1 Designation Data type Default Description leadingvalue USInt 1 leadingvalue_1: 1/ leadingvalue_2: 2 motiondirection USInt 3 NEGATIVE (1) / POSITIVE (2) / SHORTEST_WAY (3) maxvelocity Real n.c. p22020 maxacceleration Real n.c. p22021 maxjerk Real n.c. p22022 PrintMarkCorrectionDataType elements Table 4-15 PrintMarkCorrectionDataType elements Designation Data type Default Description loweroutputcam Real 0.0 n.c. p23601 upperoutputcam Real 0.0 n.c printmarkcoordinate Real 0.0 n.c V2.3 04/ /77

44 VirtualMasterDataType elements Table 4-16 VirtualMasterDataType elements Designation Data type Default Description posdata Struct possetpoint Real 0.0 [mm] posvelocity Real 0.0 [mm/s] posabsolut Bool false true = absolute posdirection USInt 3 NEGATIVE (1) / POSITIVE (2) / SHORTEST_WAY (3) maxacceleration Real n.c. [mm/s²] p21832 maxjerk Real n.c. [mm/s³] p21834 maxspeedpos Real n.c. p21830 movedata Struct SpeedMoveJog Real 0.0 maxspeedjog Real WR Struct controlword Struct setvla Bool false jogfwd_vla Bool false jogbwd_vla Bool false pos_absolutvla Bool false posfwd_vla Bool false posbwd_vla Bool false start_positioningvla Bool false stopvla Bool false velocity_override Int 0 positionsetpoint DInt 0 RD Struct actposition Real 0.0 [mm] r21864 actvelocity Real 0.0 [mm/s] r21865 StatusWord Struct positioning_activevla Bool false jog_activevla Bool false in_positionvla Bool false LifeSignCounter USInt 0 n.c. Speed setpoint move and jog [mm/s]p21806 SettingValue Real 0.0 n.c. [mm] p21803 V2.3 04/ /77

45 4.4 Operation Enabling blocks The blocks must be enabled with "Enable". Status 7000H means that the block is not computed. Status 7001H is output at the first call Selecting functions If a function is selected with an input, then output "CommandBusy" and the " Selected" output belonging to the function are TRUE. After processing has been completed, "CommandBusy" is FALSE and "CommandDone" TRUE. "CommandDone" and " Selected" remain TRUE as long as the input remains selected. If, after processing has been completed, the input is no longer TRUE, then "CommandDone" comes to for one cycle. Only one function can be simultaneously selected Switching between functions Switching between various functions is only possible at standstill. The only exception is switching from jogging to positioning Post triggering Post triggering is possible for all function; after post triggering, CommandBusy is FALSE for one cycle Reading and writing configuration data Reading and writing configuration data is only possible if the drive is switched off. Input "readwriteconfigdata" must be set to 1 to readout configuration data from the drive. The task is started when the status at the input changes. Input "readwriteconfigdata" must be set to 2 to write configuration data to the drive. The task is started when the status at the input changes Checking the entry ID Entry ID (r21502) is read out to check the functionality. If the configuration data are not read out, the entry ID must be manually entered into the configuration data. V2.3 04/ /77

46 5 LMCSINA_CrossCutterFB in the TIA Portal 5 LMCSINA_CrossCutterFB in the TIA Portal 5.1 Preparation If you wish to configure a PROFIBUS a device, then you can continue with Chapter 5.2. If you wish to configure a PROFINET device, then this is done using the userdefined GSDML file. How you can install this GSDML file is described in the following, and where you can then find it in the hardware catalog. Installing the GSDML file generated in the TIA Portal Install the user-defined GSDML file that you generated in the TIA Portal as follows: Fig. 5-1 Fig. 5-2 V2.3 04/ /77

47 5 LMCSINA_CrossCutterFB in the TIA Portal Finding the GSDML in the hardware catalog The GSDML file can now be found in the folder structure of the hardware catalog as shown in the following diagram. Fig. 5-3 V2.3 04/ /77

48 5 LMCSINA_CrossCutterFB in the TIA Portal 5.2 Commissioning TIA Portal Configuring the control Create a SIMATIC S7-1200/1500 control, and then configure it as usual. Note A minimum firmware release of 4.0 is required for the SIMATIC S This is necessary to use the blocks from "LAcycCom" for acyclic communication. Integrating the drive The following's steps describe the procedure when creating the drives and the control blocks. 1. Integrating the SINAMICS drive into the network view a. PROFIBUS: Use the existing GSD files b. PROFINET: Use the user-defined GSDML file that has been installed 2. Connect the drive to the control system Fig. 5-4 V2.3 04/ /77

49 5 LMCSINA_CrossCutterFB in the TIA Portal Integrating the LMCSINA library 3. Dearchive the global LMCSINA library by right clicking in the global libraries. Fig. 5-5 Copy all of the required library elements into the folder of the control system Now copy all of the required library files into the appropriate folder of the created control system (carefully observe the sequence of steps!) 4. Copy "LAcycCom_Drives" from "01_Necessary components" to the PLC variables folder 5. Copy "LAcycCom_typeSilentOperation" from "01_Necessary components" to the PLC data types folder 6. "LMCSINA_TypeCrossCutter" from "LMCSINA_03_Technology" "LMCSINA_CrossCutter" to the PLC data types 7. Copy function block "LMCSina_CrossCutterFB" to the program blocks. V2.3 04/ /77

50 5 LMCSINA_CrossCutterFB in the TIA Portal Fig NOTICE Avoid creating an invalid array of structs! Problem: If a data type/block is transferred into the PLC, and is compiled before accepting the PLC variables/user constants provided, then an invalid array with "0" structures is created. Remedy: The PLC variables must be completely accepted before compiling the PLC/program. This is necessary, as in the data types/blocks used, array limits are defined based on constants. Calling block LMCSINA_CrossCutterFB Calling the axixfb "LMCSina_CrossCutterFB" with an instance for each crosscutter. Interconnecting inputs and outputs. Note The following inputs must (mandatory) be interconnected in order to call the function block: enable (the block is only calculated for TRUE) hardwareid (can be found under PLC variables system constants) driveobjectno (can be found in the properties of the drive object in STARTER) The block itself can now be simply compiled. Additional steps are required to use acyclic communication (see the next chapter) V2.3 04/ /77

51 5 LMCSINA_CrossCutterFB in the TIA Portal Fig. 5-7 Integrating the acyclic communication Note The function block can also be used without acyclic communication. The default values in the FB correspond to the default values in the drive parameters. 1. Opening/dearchiving the global "LAcycCom" library 2. Copy all data types from LAcycCom 00 Common Resources Management LAcycCom_Types to the PLC data types 3. (Depending on the particular control system) copy the PLC variables LAcycCom 00 Common Resources Management to the PLC folder 4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 00 Common Resources Management to the folder of the control system used to the program blocks V2.3 04/ /77

52 5 LMCSINA_CrossCutterFB in the TIA Portal 5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 00 Common Resources Management to the PLC folder Fig Note 6. Copy function block "LAcycCom_ ReadDriveParams" from LAcycCom 01 Drives LAcycCom_Blocks PROFIDrive to the PLC folder 7. Copy all data types except "LAcycCom_typeSilentOperation" from LAcycCom 01 Drives LAcycCom_Types to PLC data types Data type "LAcycCom_typeSilentOperation", as a result of the use in the LMCSINA environment, is also supplied there and must therefore be integrated into the project ONCE. When not complied with, the TIA portal changes the comments of a data type, which can result in problems when compiling. PLC variables "LAcycCom_Drives" should also exist in the project, and should therefore not be integrated another time. V2.3 04/ /77

53 5 LMCSINA_CrossCutterFB in the TIA Portal Fig Call function blocks "LAcycCom_ResourceManager" and "LAcycCom_ReadDriveParams" in the (same) program block 9. Interconnect LAcycCom_RequestBuffer to input "globalbuffer" of "LAcycCom_ResourceManager" block 10. Activation of LAcycCom_ResourceManager at input "enable" 11. Interconnect LAcycCom_RequestBuffer at input "globalbuffer" of block "LAcycCom_ReadDriveParams" 12. Interconnect the data area "statacyclicdata" from the instance DB of the crosscutter at input "dataset" of block "LAcycCom_ReadDriveParams" V2.3 04/ /77

54 5 LMCSINA_CrossCutterFB in the TIA Portal Fig V2.3 04/ /77

55 5 LMCSINA_CrossCutterFB in the TIA Portal Fig Note Block LDPV1_Buffermanager must be released at input "enable". Block LDPV1_ReadParameters is exclusively controlled here using input "dataset". V2.3 04/ /77

56 5 LMCSINA_CrossCutterFB in the TIA Portal 5.3 LMCSINA_CrossCutterFB interfaces Block inputs Table 5-1 Designation Data type Default value Description enable Bool FALSE TRUE: Enable FB functionality FALSE: FB deactivated ackerror Bool FALSE Rising edge: Acknowledge drive fault enableaxis Bool FALSE Rising edge: Switch-on axis Falling edge: Switch-off axis axisacceleration Real Acceleration, positioning/jogging [ /s²] jogpositive Bool FALSE TRUE: Jog forward jognegative Bool FALSE TRUE: Jog backward jogvelocity Real Jogging velocity [ /min] traversetomaintenance Bool FALSE TRUE: Traverse to start position maintenanceposition Real 0.0 Maintenance position [ ] positioningvelocity Real Positioning velocity [ /min] approachdirection USInt 1 Defining the approach direction for the initial position and wait position: 0: shortest path 1: only positive 2: only negative homing Bool FALSE TRUE: Activate reference point approach homingmode UInt 1 Type of reference point approach: 0: no reference point approach/homing 1: Active reference point approach active, 2: Active reference point approach active, without BERO 3: Active reference point approach, backward 4: Active reference point approach, backward, without BERO 5: Active reference point approach, falling edge 6: Active reference point approach, falling edge without BERO 7: Active reference point approach, falling edge, backward 8: Active reference point approach, rising edge, backward, without BERO 10: Flying referencing/homing enablecuttingoperation Bool FALSE TRUE: Enable cutting operation traverse to start position enablecut Bool FALSE TRUE or rising edge: Start cutting cuttingmode USInt 2 Selecting the cutting mode: 0: no cut 1: continuous cutting, immediately 2: continuous cutting 3: Test cut, immediate 4: No cut 5: Single cut, immediate 6: Single cut formatlength Real Format length [mm] enableoscillation Bool FALSE TRUE: Enable oscillation for over-critical format lengths enablecuttingcurve Bool FALSE TRUE: Enable cut curve input enablecuttingtorque Bool FALSE TRUE: Enable cut torque input printmarkcorrection Bool FALSE TRUE: Enable print mark sensing compensationvelocity Real Velocity for print mark correction compensation [mm/min] V2.3 04/ /77

57 5 LMCSINA_CrossCutterFB in the TIA Portal Designation Data type Default value Description compensationacceleration Real Acceleration to compensate print mark correction [mm/s²] distanceprintmarkcut Real 0.0 Distance, print mark cut [mm] counterreset Bool FALSE Rising edge: Reset material counter readwriteconfigdata USInt 0 0: no reading or writing; 1: Reading the "configdata" from the drive hardwareid HW_IO 16#0 Hardware identification (as example, can be found in the system constants of the PLC) driveobjectno USInt 0 Drive object number (as example, can be found in the communication page in Starter) Values of the "homingmode" input Table 52 homing Mode Designation select homing p21630 using negative flag p21634 start direction BWD p21635 disable BERO p21636 select flying homing 0 no homing x 1 active homing x 2 active homing, without BERO x x 3 active homing, BWD x x 4 active homing, BWD, without BERO x x x 5 active homing, negative x x flag 6 active homing, negative flag, without BERO x x x 7 active homing, negative x x x flag, BWD 8 active homing, negative flag, BWD, without BERO x x x x 10 flying homing x p21643 Values of the "cuttingmode" input Table 5-3 cuttingmode Meaning 0 no cut 1 immediate continuous cutting 2 continuous cutting 3 immediate test cut 4 test cut 5 immediate single cut 6 single cut V2.3 04/ /77

58 5 LMCSINA_CrossCutterFB in the TIA Portal Block outputs Table 5-4 Designation Data type Default value Description busy Bool FALSE TRUE: FB is working and new output values can be expected valid Bool FALSE TRUE: Valid set of outputs available at the FB error Bool FALSE Rising edge informs that an error occurred during the execution. axiserror Bool FALSE TRUE: Drive error or application error axisenabled Bool FALSE TRUE: Axis is in operation axismovefwd Bool FALSE TRUE: Axis traverses forward axismovebwd Bool FALSE TRUE: Axis traverses backward targetreached Bool FALSE TRUE: Target position reached joggingactive Bool FALSE TRUE: Jogging active postomaintenanceactive Bool FALSE TRUE: Positioning to maintenance position active homingactive Bool FALSE TRUE: Homing active flyinghomingactive Bool FALSE TRUE: Flying referencing/homing active axishomed Bool FALSE TRUE: Axis is homed cuttingenabled Bool FALSE TRUE: Cutting operation enabled cutpossible Bool FALSE TRUE: Cut possible oscillatingdeactivated Bool FALSE TRUE: Oscillating deactivated format length too long actualposition Real 0.0 Actual position [ ] actualvelocity Real 0.0 Actual velocity [ /min] actualformatlength Real 0.0 Actual format length [mm] numberofcuts DInt 0 Number of cuts load Real 0.0 Actual torque in % of nominal torque actualalarmcode Word 16#0 Displays the code of the last alarm that occurred. actualfaultcode Word 16#0 Displays the code of the oldest active fault. status Word 16#7000 Current status of FB V2.3 04/ /77

59 5 LMCSINA_CrossCutterFB in the TIA Portal Value overview for the output status Table 5-5 Value Meaning 16#7101 jog velocity at limit 16#7102 positioning velocity at limit 16#7103 compensation velocity at limit 16#7110 positioning acceleration at limit 16#7111 compensation acceleration at limit 16#7200 acyclic command busy 16#7201 acyclic command busy and drive fault active 16#7202 acyclic command done 16#7203 acyclic command done and drive fault active 16#8210 homing mode not valid 16#8213 cutting mode not valid 16#8214 format length not valid 16#8215 approach direction not valid 16#8400 drive alarm active 16#8401 drive fault active 16#8402 DCC group fault active 16#8410 fine resolution not valid 16#8600 DPRD_DAT fault active 16#8610 DPWR_DAT fault active 16#8621 acyclic command error 16#8622 acyclic command error and drive fault active V2.3 04/ /77

60 5 LMCSINA_CrossCutterFB in the TIA Portal 5.4 Operation Enabling the block The block must be enabled with "enable". Status 7000H means that the block is not computed. Status 7001H is output at the first call Reading configuration data Fig Input "readwriteconfigdata" must be set to 1 to readout configuration data from the drive. The task is started when the status at the input changes. The absolute and/or the maximum values of the dynamic data are read out. The values must be read out if the following parameters are changed in the drive. Alternatively, the values can be manually adapted in the instance DB. The following parameters are read out: V2.3 04/ /77

61 6 LMCSINA_FlyingSawFB in the TIA Portal 6 LMCSINA_FlyingSawFB in the TIA Portal LMCSINA_FlyingSawFB is commissioned in exactly the same way as LMCSINA_CrossCutterFB. This is the reason that in the following screenshots, the LMCSINA_CrossCutter elements are visible. 6.1 Preparation If you want to configure a PROFIBUS device, then you can continue with Chapter 6.2. If you wish to configure a PROFINET device, then this is done using the userdefined GSDML file. How you can install this GSDML file is described in the following, and where you can then find it in the hardware catalog. Installing the GSDML file generated in the TIA Portal Install the user-defined GSDML file that you generated in the TIA Portal as follows: Fig. 6-1 Fig. 6-2 V2.3 04/ /77

62 6 LMCSINA_FlyingSawFB in the TIA Portal Finding the GSDML in the hardware catalog The GSDML file can now be found in the folder structure of the hardware catalog as shown in the following diagram. Fig. 6-3 V2.3 04/ /77

63 6 LMCSINA_FlyingSawFB in the TIA Portal 6.2 Commissioning TIA Portal Configuring the control Create a SIMATIC S7-1200/1500 control, and then configure it as usual. Note A minimum firmware release of 4.0 is required for the SIMATIC S This is necessary to use the blocks from "LAcycCom" for acyclic communication. Integrating the drive The following's steps describe the procedure when creating the drives and the control blocks. 1. Integrating the SINAMICS drive into the network view a. PROFIBUS: Use the existing GSD files b. PROFINET: Use the user-defined GSDML file that has been installed 2. Connect the drive to the control system Fig. 6-4 V2.3 04/ /77

64 6 LMCSINA_FlyingSawFB in the TIA Portal Integrating the LMCSINA library 3. Dearchive the global LMCSINA library by right clicking in the global libraries. Fig. 6-5 Copy all of the required library elements into the folder of the control system Now copy all of the required library files into the appropriate folder of the created control system (carefully observe the sequence of steps!) 4. Copy "LAcycCom_Drives" from "01_Necessary components" to the PLC variables folder 5. Copy "LAcycCom_typeSilentOperation" from "01_Necessary components" to the PLC data types folder 6. "LMCSINA_TypeFlyingSaw" from "LMCSINA_03_Technology" "LMCSINA_FlyingSaw" to the PLC data types 7. Copy function block "LMCSina_FlyingSawFB" to the program blocks. V2.3 04/ /77

65 6 LMCSINA_FlyingSawFB in the TIA Portal Fig NOTICE Avoid creating an invalid array of structs! Problem: If a data type/block is transferred into the PLC, and is compiled before accepting the PLC variables/user constants provided, then an invalid array with "0" structures is created. Remedy: The PLC variables must be completely accepted before compiling the PLC/program. This is necessary, as in the data types/blocks used, array limits are defined based on constants. Calling block LMCSINA_FlyingSawFB Call the axisfb "LMCSina_FlyingSawFB" with an instance for each saw drive. Interconnecting inputs and outputs. Note The following inputs must (mandatory) be interconnected in order to call the function block: enable (the block is only calculated for TRUE) hardwareid (can be found under PLC variables system constants) driveobjectno (can be found in the properties of the drive object in STARTER) The block itself can now be simply compiled. Additional steps are required to use acyclic communication (see the next chapter) V2.3 04/ /77

66 6 LMCSINA_FlyingSawFB in the TIA Portal Fig. 6-7 Integrating the acyclic communication Note The function block can also be used without acyclic communication. The default values in the FB correspond to the default values in the drive parameters. 1. Opening/dearchiving the global "LAcycCom" library 2. Copy all data types from LAcycCom 00 Common Resources Management LAcycCom_Types to the PLC data types 3. (Depending on the particular control system) copy the PLC variables LAcycCom 00 Common Resources Management to the PLC folder 4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 00 Common Resources Management to the folder of the control system used to the program blocks V2.3 04/ /77

67 6 LMCSINA_FlyingSawFB in the TIA Portal 5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 00 Common Resources Management to the PLC folder Fig Note 6. Copy function block "LAcycCom_ ReadDriveParams" from LAcycCom 01 Drives LAcycCom_Blocks PROFIDrive to the PLC folder 7. Copy all data types except "LAcycCom_typeSilentOperation" from LAcycCom 01 Drives LAcycCom_Types to PLC data types Data type "LAcycCom_typeSilentOperation", as a result of the use in the LMCSINA environment, is also supplied there and must therefore be integrated into the project ONCE. When not complied with, the TIA portal changes the comments of a data type, which can result in problems when compiling. PLC variables "LAcycCom_Drives" should also exist in the project, and should therefore not be integrated another time. V2.3 04/ /77

68 6 LMCSINA_FlyingSawFB in the TIA Portal Figure Call function blocks "LAcycCom_ResourceManager" and "LAcycCom_ReadDriveParams" in the (same) program block 9. Interconnect LAcycCom_RequestBuffer to input "globalbuffer" of "LAcycCom_ResourceManager" block 10. Activation of LAcycCom_ResourceManager at input "enable" 11. Interconnect LAcycCom_RequestBuffer at input "globalbuffer" of block "LAcycCom_ReadDriveParams" 12. Interconnect the data area "statacyclicdata" from the instance DB of the crosscutter at input "dataset" of block "LAcycCom_ReadDriveParams" V2.3 04/ /77

69 6 LMCSINA_FlyingSawFB in the TIA Portal Fig V2.3 04/ /77

70 6 LMCSINA_FlyingSawFB in the TIA Portal Fig Note Block LDPV1_Buffermanager must be released at input "enable". Block LDPV1_ReadParameters is exclusively controlled here using input "dataset". V2.3 04/ /77