Transcription

1 Library Motion Control SINAMICS - SIMATIC S / S Siemens Industry Online Support

2 Legal information Legal information Use of application examples Application examples illustrate the solution of automation tasks through an interaction of several components in the form of text, graphics and/or software modules. The application examples are a free service by Siemens AG and/or a subsidiary of Siemens AG ( Siemens ). They are nonbinding and make no claim to completeness or functionality regarding configuration and equipment. The application examples merely offer help with typical tasks; they do not constitute customer-specific solutions. You yourself are responsible for the proper and safe operation of the products in accordance with applicable regulations and must also check the function of the respective application example and customize it for your system. Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the application examples used by technically trained personnel. Any change to the application examples is your responsibility. Sharing the application examples with third parties or copying the application examples or excerpts thereof is permitted only in combination with your own products. The application examples are not required to undergo the customary tests and quality inspections of a chargeable product; they may have functional and performance defects as well as errors. It is your responsibility to use them in such a manner that any malfunctions that may occur do not result in property damage or injury to persons. Disclaimer of liability Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for the usability, availability, completeness and freedom from defects of the application examples as well as for related information, configuration and performance data and any damage caused thereby. This shall not apply in cases of mandatory liability, for example under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for damages arising from a breach of material contractual obligations shall however be limited to the foreseeable damage typical of the type of agreement, unless liability arises from intent or gross negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens against existing or future claims of third parties in this connection except where Siemens is mandatorily liable. By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond the liability provisions described. Other information Siemens reserves the right to make changes to the application examples at any time without notice. In case of discrepancies between the suggestions in the application examples and other Siemens publications such as catalogs, the content of the other documentation shall have precedence. The Siemens terms of use ( shall also apply. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions constitute one element of such a concept. Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place. For additional information on industrial security measures that may be implemented, please visit Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed at: Beitrags-ID: , V3.0, 03/2018 2

3 Table of contents Table of contents Legal information Introduction General structure of the library Content of the application folders Synchronism applications Cross Cutter Flying Saw Line Tension Control Winder Traverser Configuration in STARTER Configuring the drive functionality Configuring the communication Preparation and telegram selection Creating the telegram interconnections Setting the user-defined GSDML for the TIA Portal synchronism FBs Preparation Commissioning steps Interfaces Interfaces of _BasicSync FB Interface of _BasicVirtualMaster FB Operation of blocks Operation of _BasicSync FB Operation of _BasicVirtualMaster FB _CrossCutterFB in TIA Portal Preparation Commissioning TIA Portal _CrossCutterFB interfaces Block inputs Block outputs Value overview for the output status Operation Enabling the block Reading configuration data _FlyingSawFB in TIA Portal Preparation Commissioning TIA Portal _FlyingSawFB interfaces Block inputs Block outputs Value overview for the output status Operation Enabling the block Reading configuration data _WinderFB in TIA Portal _LineTensionControlFB in TIA Portal _TraversingDriveFB im TIA Portal Appendix Beitrags-ID: , V3.0, 03/2018 3

4 Table of contents 9.1 Service and Support Application Support Links and Literature Change documentation Beitrags-ID: , V3.0, 03/2018 4

5 1 Introduction 1 Introduction 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 applications based on DCC / DCB-Extension for the SINAMICS S120 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: BasicGear synchronism (from V5.1) BasicCam synchronism (from V5.1) ExtendedGear synchronism (from V5.1) ExtendedCam synchronism (from V5.1) Positioning (from V5.1) Linear flying saws with DCB-Extension Cross-cutters with DCB-Extension DCC Winder DCC Line Tension Control Traversing with DCB-Extension Note The former versions of library (< V3.0) include the former application versions for drive based synchronism (synchronism applications <= V4.x). The library >= V3.0 includes only the control blocks for the innovated synchronism applications (from synchronism application version >= V5.1) and the technological applications. 1.1 General structure of the library The library is separated in the different drive based applications. Each application / each application type has a separate folder in the master copies of the library. Entry-ID: , V3.0, 03/2018 5

6 1 Introduction Figure Content of the application folders Synchronism applications The folder "01_Synchronism Applications" contains all blocks, that are relevant for the control of the synchronism applications (>= V5.1). Figure 1-2 The blocks are only used to control the drive based functions. There are no interlocks and logics implemented inside the blocks. This makes sure to have a consistent axis state in the drive. The blocks directly send all commands to the drive. All axis states are handled by the drive itself. The separate blocks realize the following tasks: _BasicSync: This FB is used for controlling per one following axis in synchronism or for a positioning leading axis. For each axis one instance of this block is needed. The block can handle all axes with the following applications: Basic Gearing, Basic Cam, Extended Gearing, Extended Cam and Positioning. Included are functions like axis enable, homing, stopping, jogging, positioning, leading value switchover, synchronization, etc. _BasicMeasuringWheel: This FB is optional and therefore not mandatory to realize the synchronism. It is used to control certain homing functions on a measuring wheel as leading axis. Entry-ID: , V3.0, 03/2018 6

7 1 Introduction _BasicVirtualMaster: This FB is optional and therefore not mandatory to realize the synchronism. It is used to control the virtual master (virtual leading axis), which is calculated on a following axis and should be controlled by the PLC. The virtual leading axis includes functions like setting, positioning and continuous motion. _ExtendedCamFunctions: This FB is optional and therefore not mandatory to realize the synchronism. It can be called additionally to the _BasicSync FB. It is only valid for the application "Extended Cam" and controls additional camming functions. _ExtendedCoupleFunctions: This FB is optional and therefore not mandatory to realize the synchronism. It can be called additionally to the _BasicSync FB. It is only valid for the application "Extended Gear" and "Extended Cam" and controls additional coupling functions. _ExtendedOffsetFunctions: This FB is optional and therefore not mandatory to realize the synchronism. It can be called additionally to the _BasicSync FB. It is only valid for the application "Extended Gear" and "Extended Cam" and controls additional offset functions. _SpeedAxis: This FB is optional and therefore not mandatory to realize the synchronism. It is used to control several homing functions when using a speed leading axis as leading value. It does not control the speed of the axis Cross Cutter The folder "02_CrossCutter" contains all files that are necessary for the drive based cross cutter application. Figure 1-3 The subfolder "Necessary components from LAcycCom" contains some mandatory variables and datatypes from another library for compiling the block correctly. If the library "LAcycCom" not used in the project so far, those files always have to be copied completely to the PLC. The subfolder " components" contains the necessary datatypes for compiling and the control function block. Entry-ID: , V3.0, 03/2018 7

8 1 Introduction Flying Saw The folder "03_FlyingSaw" contains all files that are necessary for the drive based flying saw application. Figure 1-4 The subfolder "Necessary components from LAcycCom" contains some mandatory variables and datatypes from another library for compiling the block correctly. If the library "LAcycCom" not used in the project so far, those files always have to be copied completely to the PLC. The subfolder " components" contains the necessary datatypes for compiling and the control function block Line Tension Control The folder "04_LineTensionControl" contains all files that are necessary for the drive based application line tension control. Figure 1-5 The subfolder "Necessary components from LAcycCom" contains some mandatory variables and datatypes from another library for compiling the block correctly. If the Entry-ID: , V3.0, 03/2018 8

9 1 Introduction library "LAcycCom" not used in the project so far, those files always have to be copied completely to the PLC. The subfolder " components" contains the necessary datatypes for compiling, the control function block and the configuration data block Winder The folder "05_Winder" contains all files that are necessary for the drive based winder application. Figure 1-6 The subfolder "Necessary components from LAcycCom" contains some mandatory variables and datatypes from another library for compiling the block correctly. If the library "LAcycCom" not used in the project so far, those files always have to be copied completely to the PLC. The subfolder " components" contains the necessary datatypes for compiling, the control function block and the configuration data block Traverser The folder "06_Traverser" contains the block for controlling the drive based application traverser (with DCB Extension). Figure 1-7 Entry-ID: , V3.0, 03/2018 9

10 2 Configuration in STARTER 2 Configuration in STARTER 2.1 Configuring the drive functionality The drives must be configured and parameterized in Starter, as the motion control functionality, for the synchronous applications as well as for the other technological applications, 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 or read them by automatic configuration 3. Activate the position controller on the axes (only for position controlled axes) 4. Import the appropriate DCC charts (and save/compile) 5. Parameterize the mechanical system of the axes 6. Parameterize the basic motion control functionality, geometry of the system etc. 7. If required, configure the communication (see Chapter Fehler! Verweisquelle konnte nicht gefunden werden.) Entry-ID: , V3.0, 03/

11 2 Configuration in STARTER 2.2 Configuring the communication Preparation and telegram selection Telegrams for position controlled axes This chapter is valid for the following applications / axes: Synchronism axes: Basic Gearing Basic Camming Extended Gearing Extended Camming Positioning Cross cutter Flying saw Winder Traverser Line tension control The configuration of speed-controlled leading axes is different and is described in the next chapter Communication for speed-controlled leading axes. 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 be set to the following lengths: For all synchronism axes: Input data = 28; Output data = 20 Cross cutter: Input data = 20; Output data = 20 Flying saw: Input data = 20; Output data = 20 Winder: Input data = 20; Output data = 20 Line tension control: Input data = 20; Output data = 20 Traverser: Input data = 28; Output data = 20 Entry-ID: , V3.0, 03/

12 2 Configuration in STARTER Figure 2-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. Telegram for speed-controlled leading axes This chapter is valid for the following applications / axes: Speed-controlled leading axes for synchronism applications The general speed control of the drive is done by the user. Therefore there are function blocks in TIA Portal like the SINA_SPEED function block of the DriveLib. For this kind of control the user can select any telegram. In order to use the SINA_SPEED FB for example the standard telegram 1 is used. Independent of this general drive control there are several position related functions like homing available for these speed controlled leading axes in synchronism operation. To control these functions, supplementary data of 1 (word) in send and receive direction is added. The communication script is adding the supplementary data automatically to the drive object. There must not be other supplementary data configured by the user for that drive object. If the user needs additional data transfer for a standard telegram, this needs to be handled by telegram extension. The telegram length must not exceed the maximum limit. The script fails when the limit is exceeded. Configuration steps: First just configure the send and receive data to do the user defined speed control (e.g. by selecting a standard telegram and optional telegram extension) Execute the communication script for the synchronism applications When executing the script select the communication for your speed controlled leading drive By running the script supplementary data with the length of 1 word in send and receive direction is added and the technology control and status word is interconnected to it. Entry-ID: , V3.0, 03/

13 2 Configuration in STARTER An example configuration could look as follows: Figure 2-2 In this example the user would use Standard telegram 1 for speed control. Additionally 4 words in send and receive direction for other user data is added by the user. The script added the supplementary data automatically. Entry-ID: , V3.0, 03/

14 2 Configuration in STARTER 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 2-1 Application used Synchronous applications: Basic Gearing Basic Camming Extended Gearing Extended Camming Positioning with DCC / EPOS Measuring Wheel (as Leading axis) Speed Axis (as Leading axis) Cross cutter Flying saw Script file required _Synchronism_CommunicationScript (.txt/.xml) _Technology_CommunicationScript (.txt/.xml) _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. Entry-ID: , V3.0, 03/

15 2 Configuration in STARTER 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.8\sinamics_s120" The saved scripts can now be selected in the configuration screen form of the drive via "Configuration scripts": Fig. 2-3 Entry-ID: , V3.0, 03/

16 2 Configuration in STARTER In the dialog that opens, select the appropriate script, and click on "Execute". Fig. 2-4 Follow the instructions of the script Entry-ID: , V3.0, 03/

17 2 Configuration in STARTER 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. 2-5 Entry-ID: , V3.0, 03/

18 2 Configuration in STARTER Import the interconnection script (*.xml) Fig. 2-6 "Accept and execute" the script Figure 2-7 Follow the instructions of the script Please refer to the documentation of the particular application for additional parameter settings Entry-ID: , V3.0, 03/

19 2 Configuration in STARTER 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 or 20/28 telegram; however it 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 2-2 Application used Synchronous applications: Basic Gearing Basic Camming Extended Gearing Extended Camming Positioning with DCC / EPOS Measuring Wheel (as Leading axis) Speed Axis (as Leading axis) Cross cutter Flying saw Winder Line tension control Traverser continue with commissioning Chapter number Chapter xxx Chapter xxx Chapter xxx Commissioning and description see manual of winder Commissioning and description see manual of line tension control Commissioning and description see manual of traverser Entry-ID: , V3.0, 03/

20 3 synchronism FBs 3 synchronism FBs This chapter includes the description of the following synchronism function blocks: _BasicSync _BasicVirtualMaster _SpeedAxis _BasicMeasuringWheel After you have configured the drive according to chapter 2, then the communication to the higher-level control is configured in the TIA Portal. 3.1 Preparation If you wish to configure a PROFIBUS a device, then you can continue with Chapter 3.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. 3-1 Fig. 3-2 Entry-ID: , V3.0, 03/

21 3 synchronism FBs 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. 3-3 Entry-ID: , V3.0, 03/

22 3 synchronism FBs 3.2 Commissioning steps 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. 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 Connect the drive to the control system Fig. 3-4 Integrating the library Fig. 3-5 Dearchive the global library by right clicking in the global libraries. Entry-ID: , V3.0, 03/

23 3 synchronism FBs Copy all necessary control blocks from the folder "01_Synchronism Applications" to the program blocks of the PLC. The block _BasicSync is mandatory and controls the following axes. All other blocks are optional. Figure 3-6 Calling the block _BasicSync Call the FB "_BasicSync" with an instance for each synchronous axes in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 (can be found under PLC tags -> system constants) Entry-ID: , V3.0, 03/

24 3 synchronism FBs Figure 3-7 Calling the block _BasicVirtualMaster Call the FB "_BasicVirtualMaster" with an instance for each virtual leading axes in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 of the following axis on which the virtual leading axis is calculated (can be found under PLC tags -> system constants) Entry-ID: , V3.0, 03/

25 3 synchronism FBs Figure 3-8 Calling the block _BasicMeasuringWheel Call the FB "_BasicMeasuringWheel" with an instance for each measuring wheel axes in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 of the following axis on which the measuring wheel is calculated (can be found under PLC tags -> system constants) Entry-ID: , V3.0, 03/

26 3 synchronism FBs Figure 3-9 Calling the block _SpeedAxis Call the FB "_SpeedAxis" with an instance for each speed leading axis in your user program Each FB _SpeedAxis is communicating on his own with the connected drive object. Therefore the inputs HWID_STW and HWID_ZSW need to be set to the corresponding Hardware-ID of the projected supplementary data of the length 1/1 (word) Interconnect all needed 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) HWID_STW Here the hardware ID of the supplementary telegram data in send direction (from the PLCs point of view) needs to be given HWID_ZSW Here the hardware ID of the supplementary telegram data in receive direction (from the PLCs point of view) needs to be given The block itself can now be compiled. Entry-ID: , V3.0, 03/

27 3 synchronism FBs Calling the addon block _ExtendedCamFunctions Optionally call the FB "_ExtendedCamFunctions" with an instance for each following axis in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 (can be found under PLC tags -> system constants) Calling the addon block _ExtendedCoupleFunctions Optionally call the FB "_ExtendedCoupleFunctions" with an instance for each following axis in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 (can be found under PLC tags -> system constants) Calling the addon block _ExtendedOffsetFunctions Optionally call the FB "_ExtendedOffsetFunctions" with an instance for each following axis in your user program Interconnect all needed inputs and outputs Note The following inputs are mandatory to interconnect: enable (the block is only calculated if it is TRUE) HardwareID of the free telegram 28/20 (can be found under PLC tags -> system constants) Entry-ID: , V3.0, 03/

28 3 synchronism FBs 3.3 Interfaces Interfaces of _BasicSync FB Table 3-1 Designation Type Data type Description enable IN BOOL Block enable TRUE: block is calculated cyclically FALSE: block is not calculated ackerror IN BOOL Acknowledge drive fault TRUE: acknowledge drive fault enableaxis IN BOOL Drive enable TRUE: axis enable (OFF1 enable oft he drive) FALSE: deletion of OFF1 command (OFF2, OFF3 keep set) enablepositioncontrol IN BOOL Position control(ler) enable TRUE: enable position control of the axis FALSE: disable position control homing IN BOOL Enable homing TRUE: enable homing (depending on mode) homingmode IN INT Homing mode 1: Set reference point 2: Start absolute encoder adjustment 3: Enable flying homing 4: Enable and start active homing procedure referencecoordinate IN DINT Reference coordinate for homing functions interruptmethod IN BOOL Selection of Interrupt for active homing TRUE: Measuring input as interrupt FALSE: encoder zero mark as interrupt homingonlyoninterrupt IN BOOL Selection of type for active homing TRUE: active homing only on interrupt, without proximity switch FALSE: active homing with proximity switch and interrupt homingdirection IN BOOL Selection of active homing direction TRUE: negative starting direction FALSE: positive starting direction homingedge IN BOOL Selection of edge detection proximity switch for active homing TRUE: negative edge detection FALSE: positive edge detection stopdrive IN BOOL Stop drive TRUE: Axis ramps down with given dynamics and stays in standstill as long as this input is enabled (level detection) FALSE: Move axis with next highest mode jogpositive IN BOOL Jog forward TRUE: Move axis forward with given jog velocity as long as the input is enabled (level detection) FALSE: Move axis with next highest mode jognegative IN BOOL Jog backward TRUE: Move axis backward with given jog Entry-ID: , V3.0, 03/

29 3 synchronism FBs Designation Type Data type Description velocity as long as the input is enabled (level detection) FALSE: Move axis with next highest mode enablemdi IN BOOL Enable positioning mode TRUE: Change axis mode to positioning. When enabling the input the axis ramps down and waits for the starting command for positioning. As long as the axis should stay in positioning mode, the input needs to be enabled (level detection). FALSE: Move axis with next highest mode startpositioning IN BOOL Starting command for new positioning motion (edge triggered) positive edge: Start a new positioning motion positioningtype IN BOOL Selection of positioning type TRUE: absolute positioning FALSE: relative positioning mdicontinuous IN BOOL Enable continuous setpopint change trigger (only valid for absolute positioning) TRUE: a new positioning motion is started by just changing the position setpoint ("positionsetpoint") There is no need of starting the motion by the input "startpositioning" FALSE: Positioning motions always need tob e started by the input "startpositioning" positionsetpoint IN DINT Setting of the positioning setpoint for positioning motions in [LU] syncabsolute IN BOOL Absolute synchronization for synchronism mode - edge triggered behavior: With positive edge during relative synchronism a synchronisation motion is started and the axis changes over to absolute synchronism - level depending behavior: TRUE: When leaving a higher priority mode it is preselected that the axis directly synchronizes absolutely to the leading valued FALSE: For each changeover to synchronism mode the axis synchronizes relatively to the leading value selectchannel IN BOOL Selection of leading value channel for synchronism mode TRUE: leading value channel 1 is active FALSE: leading value channel 2 is active - Change: By changing the input in synchronism mode the axis synchronizes to the other leading value channel. This can be done relatively ("syncabsolute" = 0) or absolutely ("syncabsolute" = 1) compensationfwd IN BOOL Enable compensation motions always in forward direction (only valid for modulo axes) TRUE: compensation motions always forward FALSE: compnesation motions backward or on shortest way (depending on input "compensationbwd") Truth table for the inputs compensationfwd (here Fwd) and compensationbwd (here Bwd): Entry-ID: , V3.0, 03/

30 3 synchronism FBs Designation Type Data type Description Fwd = 0; Bwd = 0: compensation on shortest way Fwd = 1; Bwd = 0: compensation always forward Fwd = 1; Bwd = 1: compensation always forward Fwd = 0; Bwd = 1: compensation always backward compensatiobwd IN BOOL Enable compensation motions always in backward direction (only valid for modulo axes) Truth table see input "compensationfwd" autosyncafterhoming IN BOOL Enable automatic synchronization of following axis after homing of leading axis TRUE: Offset caused by homing of the leading axis is automatically synchronized FALSE: Offset caused by homing of the leading axis keeps stored on following axis -> relative synchronism Note: - is set for example when using print mark correction or flying homing on leading axis side - manual synchronization is possible via "syncabsolute" interpolatecam IN BOOL Trigger for recalculating the cam (edge triggered) positive edge: recalculate cam Note: only valid for application "Basic Cam" Attention: Cams should only be recalculated in case the axis is not in synchronism operation, as position jumps could occur depending on the cam itself! camabsolute IN BOOL Enable absolute cam output TRUE: cam output absolute FALSE: cam output relative Note: Only valid for application "Basic Cam" For details see application manual enableprintmarkcorrection IN BOOL Enable print mark correction on following axis TRUE: Print mark correction enabled FALSE: Print mark correction disabled velocityoverride IN REAL Velocity override for axis dynamics valid values: % Normalization value for maximum relative velocity: p21551 For details see application manual -> axis dynamics accelerationoverride IN REAL Acceleration override for axis dynamics valid values: % Normalization value for maximum relative acceleration: p21553 For details see application manual -> axis dynamics mdivelocityoverride IN REAL Velocity override for positioning motions valid values: % Entry-ID: , V3.0, 03/

31 3 synchronism FBs Designation Type Data type Description Normalization value for positioning velocity: p22015 freesendword20 IN WORD Free communication word for the user to send additional data to the drive Note: Destination in drive is parameter r2050[19] HardwareID IN HW_IO Setting of ID of the free telegram 20/28 to the following axis Note: The Hardware ID is automatically assigned by the PLC when interconnecting the drive to it. A list of all Hardware IDs can be found under PLC tags -> system constants. Always use the ID of the telegram to the drive (not the ID of the drive itself). valid OUT BOOL TRUE: Block outputs valid busy OUT BOOL TRUE: Block is calculated error OUT BOOL TRUE: Block fault status OUT WORD Block state warncode OUT WORD Actual warncode (r2132) of the drive faultcode OUT WORD Actual faultcode (r2131) of the drive axisenabled OUT BOOL TRUE: Axis enabled (OFF1 enabled axis in operation) axiserror OUT BOOL TRUE: Axis fault positioncontrolactive OUT BOOL TRUE: Position control enabled axishomed OUT BOOL TRUE: Axis homed axisstandstill OUT BOOL TRUE: Axis in standstill (v = 0) axisstops OUT BOOL TRUE: Axis stops (velocity is ramped down to standstill) jogfwdactive OUT BOOL TRUE: Jog forward active jogbwdactive OUT BOOL TRUE: Jog backward active homingactive OUT BOOL TRUE: Active homing activated mdiactive OUT BOOL TRUE: Positioning mode active followupactive OUT BOOL TRUE: Follow up mode active (Position control disabled) position setpoint is set to actual position value encadjactive OUT BOOL TRUE: Absolute encoder adjustment active Note: Do not switch on the axis as long as the adjustment is active encadjerror OUT BOOL TRUE: Fault in absolute encoder adjustment (Cause: see parameter r23921) encadjdone OUT BOOL TRUE: Absolute encoder adjustment successfully done dynamicsnotvalid OUT BOOL TRUE: Axis dynamics not valid Note: Set valid values for velocity and acceleration and acknowledge the error by the input "ackerror" For details see application manual -> axis dynamics axismovesfwd OUT BOOL TRUE: Axis moves forward (v > 0) axismovesbwd OUT BOOL TRUE: Axis moves backward (v < 0) Entry-ID: , V3.0, 03/

32 3 synchronism FBs Designation Type Data type Description relativesync OUT BOOL TRUE: Relative synchronism active absolutesync OUT BOOL TRUE: Absolute synchronism active camnotvalid OUT BOOL TRUE: parameterized cam points do not result in a valid cam Note: Adjust the cam points and recalculate the cam by the input "interpolatecam" actualposition OUT DINT Actual position of the axis (r2521[0]) in [LU] actualvelocity OUT DINT Actual velocity of the axis (r2522[0]) in [1000 LU/min] load OUT Real Actual torque value of the axis (r80) Note: normalized to p hex = 16384dec = 100% of p2003 7FFFhex = 32767dec = 199% of p2003 FFFFhex = dec = -200% of p2003 axisstate OUT UDINT Actual state / mode of the axis (r23900) cyclicreadstate OUT DWORD Actual state / fault of the cyclic reading command (for diagnosis in case of faulty communication -> see help of block DPRD_DAT in TIA Portal) Note: in many cases a wrong HardwareID was set cyclicwritestate OUT DWORD Actual state / fault of the cyclic writing command (for diagnosis in case of faulty communication -> see help of block DPRD_DAT in TIA Portal) Note: in many cases a wrong HardwareID was set freereceiveword25 OUT WORD Word for free usage for the user to read additional data from the drive Note: Value needs to be interconnected to parameter p2051[24] in the drive freereceiveword26 OUT WORD Word for free usage for the user to read additional data from the drive Note: Value needs to be interconnected to parameter p2051[25] in the drive freereceiveword27 OUT WORD Word for free usage for the user to read additional data from the drive Note: Value needs to be interconnected to parameter p2051[26] in the drive freereceiveword28 OUT WORD Word for free usage for the user to read additional data from the drive Note: Value needs to be interconnected to parameter p2051[27] in the drive Interface of _BasicVirtualMaster FB Table 3-2 Designation Type Data type Description enable IN BOOL Block enable TRUE: Block is calculated cyclically FALSE: Block is not calculated setvirtualaxis IN BOOL Set the output position of the virtual leading axis TRUE: Set output position to setting value movefwdvirtualaxis IN BOOL Move virtual leading axis continuously forward TRUE: Move continuously forward Entry-ID: , V3.0, 03/

33 3 synchronism FBs Designation Type Data type Description movebwdvirtualaxis IN BOOL Move virtual leading axis continuously backward TRUE: Move continuously backward velocityovdvirtualaxis IN REAL Velocity override for virtual leading axis valid values: % Normalization value for velocity: p25004 positioningtypevirtualaxis IN BOOL Selection of positioning type TRUE: Absolute positioning FALSE: Relative positioning positioningfwdvirtualaxis IN BOOL Selection of positioning direction (only valid for modulo axes and absolute positioning) TRUE: Positioning only forward Truth table for the inputs positioningfwdvirtualaxis (here Fwd) and positioningbwdvirtualaxis (here Bwd): Fwd = 0; Bwd = 0: Positioning motions on shortest way Fwd = 1; Bwd = 0: Positioning motions always forward Fwd = 1; Bwd = 1: Positioning motions always forward Fwd = 0; Bwd = 1: Positioning motions always backward positioningbwdvirtualaxis IN BOOL Selection of positioning direction (only valid for modulo axes and absolute positioning) TRUE: Positioning only bakcward Truth table see input "positioningfwdvirtualaxis" startpositioningvirtualaxis IN BOOL Starting command for a new positioning motion (edge triggered) positive edge: Starting a new positioning motion stoppositioningvirtualaxis IN BOOL Stop and reject a positioning motion (edge triggered) positive edge: active positioning motion is stopped and rejected positionsetpointvirtualaxis IN BOOL Position setpoint for positioning motion in [LU] HardwareID IN HW_IO Setting of Hardware ID of the free telegram 20/28 to the following axis, on which the virtual axis is calculated Note: The Hardware ID is automatically assigned by the PLC when interconnecting the drive to it. A list of all Hardware IDs can be found under PLC tags -> system constants. Always use the ID of the telegram to the drive (not the ID of the drive itself). valid OUT BOOL TRUE: Block outputs valid busy OUT BOOL TRUE: Block is calculated error OUT BOOL TRUE: Block error status OUT WORD Block state actualposvirtualaxis OUT DINT Actual position of virtual leading axis in [LU] actualvelvirtualaxis OUT DINT Actual velocity of virtual leading axis in [1000 Entry-ID: , V3.0, 03/

34 3 synchronism FBs Designation Type Data type Description LU/min] continuousopvirtualaxis OUT BOOL TRUE: Continuous mode active positioningactivevirtualaxis OUT BOOL TRUE: Positioning motion active positioningdonevirtualaxis OUT BOOL TRUE: Positioning motion done / not active 3.4 Operation of blocks Operation of _BasicSync FB Block enable The blocks must be enabled with "Enable". Status 7000H means that the block is not computed. Status 7001H is output at the first call. When it is in cyclic mode the status changes to 7002h. Only if the block is enabled there is a cyclic communication to the drive. If the block enable signal is disabled during operation the OFF1 command of the drive is taken first before the cyclic communication is stopped. Axis enable The axis is enabled by the input "enableaxis". By that the OFF1 command of the drive is set. The commands for OFF2 and OFF3 are permanently enabled and are not taken in case the block is enabled. When the axis is automatically switched off by an axis fault, the fault has to be acknowledged first and then a new rising edge needs to be created at the "enableaxis" input to switch on the axis again. After that the input needs to stay enabled as long as the axis should be enabled. So the input has an edge detection and a level detection. For switching on always a positive edge is required. Switch on after fault After an axis fault, which switched off the axis, the fault first needs to be acknowledged by "ackerror" and then a new rising edge at the input "enableaxis" needs to be created. So only acknowledging the fault is not sufficient to switch on the axis again. The following diagram shows the switching on procedure Entry-ID: , V3.0, 03/

35 3 synchronism FBs Figure 3-10 Acknowledge error (I: ackerror) Enable axis (I: enableaxis) Axis fault (Q: axiserror) Axis enabled (Q: axisenabled) Enable position control When the axis should be moved, the position controller needs to be enabled by the input "enablepositioncontrol". Additionally the axis needs to be switched on. The axis only changes to the wanted mode if it is switched on and the position control is enabled. The additional need to enable the position control shall avoid to directly changing the axis to synchronism mode after switching on. Axis modes All axis modes are prioritized and are handled by the application on the drive side. The synchronism mode is automatically active when the axis and the position control is enabled. So for that mode no explicit control bit is necessary to set. All other modes (Stop drive, jog, active homing and positioning) have a higher priority than synchronism mode and need to be enabled explicitly. If the axis should not directly go to synchronism mode after switching on and position controller enable another mode needs to be selected (e.g. "stopdrive"). In general more than one mode can be selected at the same time. The application prioritizes the modes and runs always the mode with the highest priority. The following modes are prioritized in the following order (first mode = highest priority; last mode = lowest priority): 1. Follow up mode (Axis disabled / position control disabled) 2. Stop drive 3. Jog forward 4. Jog backward 5. Active homing mode 6. Positioning mode 7. Absolute synchronism 8. Relative synchronism When the axis is switched on and the position controller is enabled, the mode "relative synchronism" is automatically active in case no other mode with higher priority is selected. The following functions are not prioritized and can in general be executed in parallel to the other modes: Flying homing Entry-ID: , V3.0, 03/

36 3 synchronism FBs Set reference point Print mark correction (only reasonable in synchronism mode!) Selecting a mode Deselecting a mode Modes need to be selected explicitly. The modes "follow up" and "relative synchronism" are an exception here. The follow up mode is getting active when the position controller is disabled or the axis is switched off. The relative synchronism mode is always getting active when the axis and the position controller are enabled and no other mode is selected. In case more than one mode is selected the axis always executes the mode with the highest priority. A mode can be left by deselecting it or by selecting a mode with higher priority. When the position controller is enabled and no other mode is selected, the axis changes always to "relative synchronism" mode and follows the leading value's velocity. Flying changeover of modes In general each mode can be switched over with a dynamic motion to another mode on the fly. Changing into a mode with higher priority By selecting a mode with higher priority than the actual one the axis always changes directly to that new mode - independent whether the old mode keeps selected or not. By that you could for example switch over on the fly from jogging backward to jogging forward by first selecting jog backward and then additionally select jog forward. Of course in the same moment jog backward could be deselected (but does not need to). Changing into a mode with lower priority For a flying changeover to a lower priority mode the old higher priority mode always needs to be deselected. Either the lower priority mode is then selected exactly at the same time or it is already preselected. A mode is preselected by selecting the higher priority mode as well as the lower priority mode. Then the higher priority mode just needs to be deselected and the axis changes to the lower priority mode. In the application manual you additionally find a schematic timing diagram for flying changeovers of modes and the list of all axis states for diagnosis and interpreting reasons. Information regarding the different axis functions and modes Detailed information to all axis functions and their configuration can be found in the application manual in the operation chapter. Entry-ID: , V3.0, 03/

37 3 synchronism FBs Operation of _BasicVirtualMaster FB Block enable The blocks must be enabled with "Enable". Status 7000H means that the block is not computed. Status 7001H is output at the first call. When it is in cyclic mode the status changes to 7002h. Only if the block is enabled there is a cyclic communication to the drive. Modes The virtual leading axis in general can be operated in the following modes: Continuous mode a position signal is continuously generated by the given velocity setpoint. Positioning mode the virtual leading axis by a starting command is moving absolutely to a defined position or moves on relatively by the defined distance. Setting function the output position of the virtual leading axis is set to a defined setting position. This is the priority of the modes: 1. Setting function (highest priority) 2. Continuous motion 3. Positioning (lowest priority) A changeover of modes works similar to the following axis. Modes with higher priority always first need to be deselected before the axis changes to a mode with lower priority. Changes to modes with higher priority are always directly done. CAUTION Unexpected position jumps on the following axes If the virtual axis is set while one or more following axes are synchronized (absolutely or relatively) to it, position jumps on the following axes can occur. Therefore only set the virtual axis in case the following axes are uncoupled from synchronism (e.g. by selecting the mode "stop drive" on the following axis). Detailed information to all functions of the virtual leading axis can be found in the application manual in chapter functions of the virtual leading axis. Entry-ID: , V3.0, 03/

38 4 _CrossCutterFB in TIA Portal 4 _CrossCutterFB in 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 Entry-ID: , V3.0, 03/

39 4 _CrossCutterFB in 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. 4-3 Entry-ID: , V3.0, 03/

40 4 _CrossCutterFB in TIA Portal 4.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. 4-4 Integrating the library 3. Dearchive the global library by right clicking in the global libraries. Fig. 4-5 Entry-ID: , V3.0, 03/

41 4 _CrossCutterFB in TIA Portal Copy all of the required library elements into the folder of the PLC Open the folder "02_CrossCutter" under the master copies and copy all necessary files of the library to the correct folders of your PLC (take care of the step order!) 4. Copy the folder "LAcycCom_Tags from "Necessary components from LAcycCom into the folder PLC tags 5. Copy the folder LAcycCom_Types" from "Necessary components from LAcycCom" into the folder PLC datatypes 6. Copy the folder _Types" from " components" into the folder PLC datatypes 7. Copy the function block "_CrossCutterFB" from " components" "_Blocks" to the PLC program blocks 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 _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) Entry-ID: , V3.0, 03/

42 4 _CrossCutterFB in TIA Portal Figure 4-6 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_ Resource Management LAcycCom_Types to the PLC data types 3. Copy the PLC variables LAcycCom 00_Resource Management to the PLC folder 4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 00_Resource Management to the folder of the control system used to the program blocks Entry-ID: , V3.0, 03/

43 4 _CrossCutterFB in TIA Portal 5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 00_Resource Management to the PLC folder Fig 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 Note Data type "LAcycCom_typeSilentOperation", as a result of the use in the 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. Entry-ID: , V3.0, 03/

44 4 _CrossCutterFB in 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" Entry-ID: , V3.0, 03/

45 4 _CrossCutterFB in TIA Portal Figure 4-9 Entry-ID: , V3.0, 03/

46 4 _CrossCutterFB in TIA Portal Fig Note Block LDPV1_Buffermanager must be released at input "enable". Block LDPV1_ReadParameters is exclusively controlled here using input "dataset". Beitrags-ID: , V3.0, 03/

47 4 _CrossCutterFB in TIA Portal 4.3 _CrossCutterFB interfaces Block inputs Table 4-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] compensationacceleration Real Acceleration to compensate print mark correction Entry-ID: , V3.0, 03/

48 4 _CrossCutterFB in TIA Portal Designation Data type Default value Description [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 42 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 4-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 Block outputs Table 4-4 Designation Data type Default value Description busy Bool FALSE TRUE: FB is working and new output values can be expected Entry-ID: , V3.0, 03/

49 4 _CrossCutterFB in TIA Portal Designation Data type Default value Description 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 Entry-ID: , V3.0, 03/

50 4 _CrossCutterFB in TIA Portal Value overview for the output status Table 4-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 Entry-ID: , V3.0, 03/

51 4 _CrossCutterFB in TIA Portal 4.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: Entry-ID: , V3.0, 03/

52 5 _FlyingSawFB in TIA Portal 5 _FlyingSawFB in TIA Portal _FlyingSawFB is commissioned in exactly the same way as _CrossCutterFB. This is the reason that in the following screenshots, the _CrossCutter elements are visible. 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 Entry-ID: , V3.0, 03/

53 5 _FlyingSawFB in 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 Entry-ID: , V3.0, 03/

54 5 _FlyingSawFB in 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. 8. 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 9. Connect the drive to the control system Fig. 5-4 Integrating the library 10. Dearchive the global library by right clicking in the global libraries. Fig. 5-5 Entry-ID: , V3.0, 03/

55 5 _FlyingSawFB in TIA Portal Copy all of the required library elements into the folder of the PLC Open the folder "03_FlyingSaw" under the master copies and copy all necessary files of the library to the correct folders of your PLC (take care of the step order!) 11. Copy the folder "LAcycCom_Tags from "Necessary components from LAcycCom into the folder PLC tags 12. Copy the folder LAcycCom_Types" from "Necessary components from LAcycCom" into the folder PLC datatypes 13. Copy the folder _Types" from " components" into the folder PLC datatypes 14. Copy the function block "_FlyingSawFB" from " components" "_Blocks" to the PLC program blocks 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 _FlyingSawFB Calling the axixfb "LMCSina_FlyingSawFB" with an instance for each flying saw. 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) Entry-ID: , V3.0, 03/

56 5 _FlyingSawFB in TIA Portal Figure 5-6 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_ Resource Management LAcycCom_Types to the PLC data types 3. Copy the PLC variables LAcycCom 00_Resource Management to the PLC folder 4. Copy function block "LAcycCom_ResourceManager" from LAcycCom 00_Resource Management to the folder of the control system used to the program blocks Entry-ID: , V3.0, 03/

57 5 _FlyingSawFB in TIA Portal 5. Copy the global data block "LAcycCom_RequestBuffer" from LAcycCom 00_Resource Management to the PLC folder Fig 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 Note Data type "LAcycCom_typeSilentOperation", as a result of the use in the 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. Entry-ID: , V3.0, 03/

58 5 _FlyingSawFB in 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" Entry-ID: , V3.0, 03/

59 5 _FlyingSawFB in TIA Portal Figure 5-9 Entry-ID: , V3.0, 03/

60 5 _FlyingSawFB in TIA Portal Fig Note Block LDPV1_Buffermanager must be released at input "enable". Block LDPV1_ReadParameters is exclusively controlled here using input "dataset". Beitrags-ID: , V3.0, 03/