Transcription

1 Management Record I-device Siemens Industry Online Support

2 Siemens AG 2018 All rights reserved 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: Entry ID: , V1.0, 05/2018 2

3 Siemens AG 2018 All rights reserved Table of contents Table of contents Legal information Introduction Overview Mode of operation management Application Components used Engineering Hardware configuration Configuration User program Data types Data blocks Function block "Management" Operation Error handling Useful information Information about asset management Management Record management block How the " Management" block works Appendix Service and Support Links and Literature Change documentation Entry ID: , V1.0, 05/2018 3

4 Siemens AG 2018 All rights reserved 1 Introduction 1 Introduction 1.1 Overview Initial situation Requirement Identification and maintenance data (in short: I&M) are stored internal component (firmware and / or hardware) of a device with PROFINET interface. The I & M data sets can be read out via an acyclic data exchange with "Read/Write Record". The I & M data enable the unique identification of the devices and modules and their versions. Any device that can be replaced or updated for maintenance and repair needs to be uniquely identifiable online. Problem Solution A machine, e.g. a complete machine tool or a laser welding machine, usually consists of substations with dedicated automation components. Some of these automation components are not part of the PROFINET system and therefore cannot be addressed via PROFINET. These lower-level automation components cannot be uniquely identified because the I & M data is only available for devices or modules that can be addressed via PROFINET. To solve this problem, Management (short: AM)" has been introduced. In addition to I & M, asset management is an additional concept for providing information such as via firmware or hardware versions, from locally connected devices or driver versions outside the PROFINET address space. management is based on I & M and works with a standardized data set, the Management Record (short: AMR)". Applicative implementation This application example shows you how to use the identification and maintenance functions I&M and AM. On the hardware side, a SIMATIC S is operated as an I-device. The SIMATIC S is equipped with several central I/O and communication modules. Other devices that are not located in the PROFINET address space, e.g. sensors, actuators and motors, are subordinated to these central modules. The software includes the function block "Management", which is loaded into the I-device and which you can find in the application example. The function block creates an asset management record from all calculated (I&M) and individual (AM) information and makes this data record available to the IO controller. Entry ID: , V1.0, 05/2018 4

5 Siemens AG 2018 All rights reserved 1 Introduction Figure 1-1 I-device with central modules I&M AMR S Non-PROFINET component Non-PROFINET component AM Advantage The use of the identification and maintenance functions I&M and AM has the following advantages: All components in an automation system are completely recorded: I&M for PROFINET devices AM for hardware and software outside the PROFINET address space Every item of hardware or software is clearly identifiable. You always have an overview of all the hardware and software installed in your network. Conclusions can be drawn about a possible malfunction or unsupported functionality in a field device. Entry ID: , V1.0, 05/2018 5

6 Siemens AG 2018 All rights reserved 1 Introduction 1.2 Mode of operation management Terminology The following terms are used in connection with the asset management function: Table 1-1 Term management block Management Record Explanation A component or object in an automation network. This can be a module, a device, the firmware or a driver, for example. The information about the asset is stored in an asset management block. The asset management block contains all the identification and recognition data for an asset. All asset management blocks are combined in one asset management record. The asset management record is a data record with the index 16#F880. Description With asset management it is possible to provide identification and recognition data for assets that are not part of the PROFINET network. The user creates an asset management block for each non-profinet component and stores the identification and recognition data of the asset here. The asset management blocks are then combined into an asset management record. The asset management information for assets that cannot be addressed via PROFINET is managed and stored by the PROFINET device to which these assets are connected (in the case of an intelligent PROFINET device) or a higher-level PROFINET CPU Application Procedure The application in the I-device uses I&M and AM to provide the information about the assets to an IO controller. To identify the individual assets, the following procedure applies: The I&M data of all modules inserted centrally in the I-device are automatically read and processed for asset management. You specify the information about the assets outside the PROFINET address space, e.g. sensors and actuators, individually and enter this information in pre-built asset management block structures. The application creates an asset management record from all determined and individual information and makes it available to the IO controller. Entry ID: , V1.0, 05/2018 6

7 Siemens AG 2018 All rights reserved 1 Introduction Schematic representation Figure 1-2 IO-controller The following figure shows the most important relationships between the components involved and steps required for the procedure described. RDREC 5 Read data record 4 PVRREC Provide AMR Management 2 AM I&M Create AMR Management Record 3 Data 1 AM AM I-device Store asset information Commissioning engineer Entry ID: , V1.0, 05/2018 7

8 Siemens AG 2018 All rights reserved 1 Introduction Explanation Table 1-2 Step The following table describes the individual steps from the schematic diagram: Description 1. You specify the information about the assets that are outside the PROFINET address space individually. You store the information in ready-made asset management block structures and transfer it to the "Management" function block as the input parameter. The function block "Management" reads the blocks and processes them. 2. The information about the assets that is stored centrally in the SIMATIC station is automatically determined by the "Management" function block using the "Get_IM_Data" application and converted into individual asset management blocks. 3. The asset management function block generates an asset management record from all asset management blocks. This record therefore contains this information: Information about the assets outside of the PROFINET address space (individually determined by you). Information on the centrally plugged modules in the I-device (automatically determined by I&M). 4. The asset management record is made available to the higher-level IO controller via the system application "PRVREC" and the index 16#F The higher-level IO controller reads the record via the system application "RDREC". Delimitation This application example only contains the configuration for the I-device. If you want to read and receive the asset management record in the higher-level IO controller, you must request the data record in the IO controller with the system application "RDREC" and the index 16#F880 from the I-device. Entry ID: , V1.0, 05/2018 8

9 Siemens AG 2018 All rights reserved 1 Introduction 1.3 Components used The Application Example was created with these hardware and software components: Table 1-3 Component Numbe r Article number Note SIMATIC S ES7516-3FN01-0AB0 I-device; requires Firmware V2.5.2 or higher CM GK7542-1AX00-0XE0 DI 32x24VDC HF 1 6ES7521-1BL00-0AB0 DO 16x24VDC/0.5A ST 2 6ES7522-1BH00-0AB0 SIMATIC S ES7513-1AL01-0AB0 IO controller; the firmware of the controller is not relevant. STEP 7 Professional V15 1 6ES This application example consists of the following components: Table 1-4 Component File name Note This document _Mgmt_DOKU_V10_en.pdf TIA Portal project _Mgmt_TIA_V15_PROJ.zip Unpack the file and open the TIA project file "Management.a p15". Entry ID: , V1.0, 05/2018 9

10 Siemens AG 2018 All rights reserved 2 Engineering 2 Engineering 2.1 Hardware configuration Hardware configuration The following figure shows the hardware configuration of the application example: Figure 2-1 S (IO-controller) S (IO-device) CM DI DO DO PROFINET IE (not on PROFINET) s Hardware adaptation If you do not have the hardware used in the application example, replace the devices.. Note The controller for the IO device must have at least firmware Configuration For the I-device to react to the asset management, you must activate the asset management in the I-device. You will find the corresponding check box in the menu item "Operating mode" in the properties of the CPU. The "Operating mode" dialog has been extended by another entry "Activate asset management via the user program". If you select this check box, you signal that the application program responds to requests when retrieving asset management data. Entry ID: , V1.0, 05/

11 Siemens AG 2018 All rights reserved 2 Engineering Figure 2-2 Note The check box can only be activated if you have set the operating mode to "IO device". 2.3 User program This section gives you an overview and description of the blocks in the user program Data types Description Each asset management block describes an asset. To describe the asset, there are three different formats of the asset management block: Complete information (consisting of hardware and firmware information) Only hardware information Only firmware information The organization and the structure are each firmly defined and may not be changed. To assist you in entering the asset information, the application example provides a separate data type for each asset management block format. The following table shows you which data type corresponds to which asset management block format: Table 2-1 management block Full information Only hardware information Only firmware information Data type typemanagementfullinformation typemanagementonlyhw typemanagementonlysw Entry ID: , V1.0, 05/

12 Siemens AG 2018 All rights reserved 2 Engineering The figure below shows you as an example the data type "typemanagementfullinformation". This data type reflects the asset management block format "Full Information". Figure 2-3 Note You can find further information on the asset management block in Section Entry ID: , V1.0, 05/

13 Siemens AG 2018 All rights reserved 2 Engineering Data blocks " Data" The "Data" data block is the location for the asset management blocks that you store for your assets. As required, you define your own array tag for each asset management block format in the data block and assign the associated data type to this tag as a type. The array size of the arrays depends on the number of assets you want to describe in this format. The following figure shows an example of how the data block can be declared with array tags. Figure 2-4 For the example shown, the following statements are correct: Two different asset management block formats are used "Full information" (referenced by the data type "typemanagementfullinformation") "Only hardware information" (referenced by data type "typemanagementonlyhw") Three assets are described in the "Complete Information" format. One asset is described in the "Only hardware information" format. No asset is described by the Management block "Only firmware information". " Management Record" The "ManagementRecord" data block consists of a single tag, which is declared as a byte array. The "Management" function block generates the asset management record in this byte array. Note The byte array is declared with a size of 20 kbytes. You can change the size using the user constant "#MAXDATA". Entry ID: , V1.0, 05/

14 Siemens AG 2018 All rights reserved 2 Engineering Function block "Management" Core task The core task of the " Management" function block is to create an asset management record from all information (I&M data, AM) and to make this data record available to the IO controller. Note You will find a detailed description of how the block works in in Section 3.2. Interface description The following figure shows you the how the function block "Management" is called. Figure 2-5 Bool CentralManagement makedatar ecord dataconsist ent busy error Bool Bool Bool status DWord Version Version Version statusid arrayforblockfulinform ation arrayforblockonlysw arrayforblockonlyhw Int Version Version Version The table below shows you the parameters of the function block "Management". Table 2-2 Name P type Data type Comment makedatarecord IN Bool On a positive edge, the asset management record is compiled. dataconsistent OUT Bool True, if the asset management record is complete and consistent. busy OUT Bool True, if the block is being processed. error OUT Bool True if an error has occurred. status OUT DWord Displays the error information (see also Section 2.5). statusid OUT Int State that caused the error. arrayforblock FulInformation IN_OUT Version Reference to the array for the asset management block "Full Information". The referenced array must be of the type "typemanagamentfullinformation" (see Section 2.3.2). If no array exists, NULL must be parameterized. Entry ID: , V1.0, 05/

15 Siemens AG 2018 All rights reserved 2 Engineering Name P type Data type Comment arrayforblock OnlySW arrayforblock OnlyHW IN_OUT Version Reference to the array for the asset management block "Only firmware information". The referenced array must be of the type "typemanagamentonlysw" (see Section 2.3.2). If no array exists, NULL must be parameterized. IN_OUT Version Reference to the array for the asset management block "Only hardware information". The referenced array must be of the type typemanagamentonlyhw" (see Section 2.3.2). If no array exists, NULL must be parameterized. Note If the block detects a discrepancy in the parameter checking or if a system application detects an error, the block issues an error. You can recognize the cause of the error by the parameter "status" (see Section 2.5). Entry ID: , V1.0, 05/

16 Siemens AG 2018 All rights reserved 2 Engineering 2.4 Operation This Section shows you how to use the asset management feature. Storing asset information To store information about the non-profinet components, proceed as follows: 1. Open the data block "Data". 2. Declare an array tag for each asset management block format and specify the associated data type as the data type, for example, typemanagementfullinformation for the "Full information" format. The array size of the arrays depends on the number of assets you want to describe in this format. Note: Tags have already been created in the data block. You can change, delete or add these as you like. Example: 3. Open the array fields and fill in the data type with information about the asset. Each asset is represented by its own array field element. Note For a description and information on the wiring of the tags of the asset management block, see Section Entry ID: , V1.0, 05/

17 Siemens AG 2018 All rights reserved 2 Engineering Connect " Management" block Interconnect the array tags from the data block "Data" with the function block "Management". Follow these steps: 1. Open the "OB1". The function block "Management" is called here. 2. Interconnect the IN and OUT parameters, e.g. with a flag. 3. Interconnect the following IN-OUT parameters of the function block with the array tags from the "Data" data block: Table 2-3 IN-OUT parameters arrayforblockfulinformation arrayforblockonlysw arrayforblockonlyhw Array tag from "Data" Array tag of data type "typemanagementfullinformation". Array tag of data type "typemanagementonlysw". Array tag of data type "typemanagementonlyhw". Note If you do not use an IN-OUT parameter of the function block, you reference a NULL pointer (value "NULL"). Final steps 1. Save and compile the project. If there are errors during compilation, fix them. 2. Download the project to the CPU. All modules must be in a faultless condition. Test application example To test the application example, proceed as follows: 1. Trigger the IN parameter of the "Management" function block with a positive edge. 2. If the function block has read in all the information (I&M data, AM) without errors and has converted it to an asset management record, the OUT parameter "dataconsistent" is set. The asset management record is made available to the higher-level IO controller with the system application "PRVREC". 3. Implement a call to the system application "RDREC" in the IO controller and read the data record with the index 16#F880 from the I-device. The IO controller can now process the information about the assets and the centrally plugged modules of the I-device. Entry ID: , V1.0, 05/

18 Siemens AG 2018 All rights reserved 2 Engineering 2.5 Error handling Error in the IO controller If the I-device makes the asset management record available to an IO controller, the I-device checks the asset management record for errors in advance. If the I- device detects a discrepancy in the parameterization, you will receive the error code 0xDE80AA00 at the system application "RDREC". In this case, check whether you have parameterized the tags of the Management Block according to the specifications. Please also note the information in the description of the tags (see Section 3.1.2). Error in the function block "Management" If an error occurs in the program, the current status of the state machines and the cause of the error are written to the output parameters "statusid" and "status". At the output "statusid", the number of the state in which the error occurred is output. The states are numbered and have the following meaning. Table 2-4 Value 0 IDLE Description 1 CHECK_ELEMENTS_ON_INOUT 2 SUM_BYTES_ELEMENTS_NEED 3 READ_SLOTS_IM_DATA 4 SUM_BYTES_SLOTS_NEED 5 BUILD_AM_RECORD 6 FILL_FULL_INFORMATION 7 FILL_SW_ONLY 8 FILL_HW_ONLY 9 FILL_IM_TO_AMR 11 AM_RECORD_READY_TO_USE 15 ERRORHANDLING 100 PROVIDE_MODE_0 101 PROVIDE_MODE_1 103 PROVIDE_MODE_3 104 PROVIDE_ERROR Entry ID: , V1.0, 05/

19 Siemens AG 2018 All rights reserved 2 Engineering "status" The output parameter "status" displays the error code: Table 2-5 statusid status Description Remedy 1 16#5001 At the IN_OUT parameter "arrayforblock FulInformation" no array is stored. 16#5002 At the IN_OUT parameter "arrayforblock OnlySW" no array is stored. 16#5003 At the IN_OUT parameter "arrayforblock OnlyHW" no array is stored. 3 Status message from the "GET_IM_Data" block. 5 Status message from the "Serialize" block. See TIA Online Help - See TIA Online Help - You must reference the associated array tag in the "Data" data block or use the NULL pointer. Entry ID: , V1.0, 05/

20 Siemens AG 2018 All rights reserved 3 Useful information 3 Useful information 3.1 Information about asset management Management Record The asset management record lists an asset management block for each local asset that is not part of the PROFINET system. The structure of the asset management record may not be changed and is defined in Management as follows: BlockHeader; consisting of: BlockType BlockLength BlockVersion ManagementBlock The asset management record can be accessed via the record index 16#F880. The following table shows the structure of the asset management record: Table 3-1 Tag Data type Note BlockType Word Identifies the asset management record. The value is 0x0035. BlockLength Word The length of the subsequent information content. BlockVersion Word Must have the value 0x0100. NumberOfEntries Word Number of following asset management blocks ManagementBlock 1 ManagementBlock 2 ManagementBlock ManagementBlock n "AM_FullInformation" "AM_HardwareOnlyInformation" "AM_FirmwareOnlyInformation" "AM_FullInformation" "AM_HardwareOnlyInformation" "AM_FirmwareOnlyInformation" "AM_FullInformation" "AM_HardwareOnlyInformation" "AM_FirmwareOnlyInformation" "AM_FullInformation" "AM_HardwareOnlyInformation" "AM_FirmwareOnlyInformation" Entry ID: , V1.0, 05/

21 Siemens AG 2018 All rights reserved 3 Useful information management block The identification and recognition data of an asset are stored in an asset management block. Depending on the size of the data, the following formats are available: Complex information ("AM_FullInformation") Only hardware information ("AM_HardwareOnlyInformation") Only software information ( AM_SoftwareOnlyInformation") The organization and the structure of the asset management block are firmly defined and may not be changed. Structure of the asset management block Since the format "AM_FullInformation" includes all possible elements, this format is suitable for demonstrating the organization and structure of an asset management block. The formats "AM_HardwareOnlyInformation" and "AM_FirmwareOnlyInformation" are almost identical. In each case, the unusable elements are missing here: Firmware information in the format "AM_HardwareOnlyInformation" Hardware information in the format "AM_FirmwareOnlyInformation" The following table shows you the format "AM_FullInformation". A description of the tags can be found in the table below. Table 3-2 BlockType BlockLength BlockVersion Padding Padding IM_UniqueIdentifier Tag Data type Note AM_Location Structure BeginSlotNumber BeginSubslotnumber EndSlotNumber EndSubslotnumber Word Word Word Byte Byte Array[16] of Byte Word Word Word Word Word IM_Annotation IM_OrderID AM_SoftwareRevision AM_HardwareRevision IM_Serial_Number IM_Software_Revision Array[64] of Char Array[64] of Char Array[64] of Char Array[64] of Char Array[16] of Char Array[4] of Byte Not available in the format "AM_HardwareOnlyInformation". Not available in the format "AM_FirmwareOnlyInformation". Not available in the format "AM_HardwareOnlyInformation". Entry ID: , V1.0, 05/

22 Siemens AG 2018 All rights reserved 3 Useful information Tag Data type Note AM_DeviceIdentification Bit 0-15: DeviceSubID Bit 16-31: DeviceID Bit 32-47: VendorID Bit 48-63: Organization AM_TypeIdentification UINT UINT Word UINT UINT IM_Hardware_Revision UINT Not available in the format "AM_FirmwareOnlyInformation". BlockType The BlockType identifies the asset management block. The following coding is performed: AM_FullInformation:0x0036 AM_HardwareOnlyInformation: 0x0037 AM_SoftwareOnlyInformation: 0x0038 Note The coding for BlockType must be adhered to. If you code BlockType incorrectly, the record is transferred to the IO controller with an error. BlockLength BlockLength stores the length of the subsequent information content. The following coding is performed: AM_FullInformation: 324 bytes AM_HardwareOnlyInformation: 256 bytes AM_SoftwareOnlyInformation: 260 bytes Note The coding for BlockLength must be adhered to. If you code BlockLength incorrectly, the record is transferred to the IO controller with an error. BlockVersion The BlockVersion must uniformly have the value 0x0100. Note If BlockVersion does not have the required value, then the data record is transferred to the IO controller with an error. Padding Note Padding is a filler byte and must be filled with 0. If padding has a value other than 0, then the data record is transferred to the IO controller with an error. Entry ID: , V1.0, 05/

23 Siemens AG 2018 All rights reserved 3 Useful information IM_UniqueIdentifier A reference key is stored in the IM_UniqueIdentifier. This key is intended to uniquely identify the asset. It may not have the value 0. Note If IM_UniqueIdentifier has the value 0, then the data record is transferred to the IO controller with an error. AM_Location The geographic location/deployment location of the asset is entered in AM_Location. The AM_Location is divided into several elements: Structure specifies the format used to encode AM_Location. It must have the value 0x02 (slot/subslot format). BeginSlotNumber is the initial geographical slot of the asset. Valid range: 0-0x7FFF. BeginSubslotnumber is the initial geographical subslot of the asset. Valid range: 0-0xFFFF. The value 0xFFFF means that the whole slot is included. EndSlotNumber is the final geographical slot of the asset. Valid range: 0-0x7FFF. EndSubslotnumber is the final geographical subslot of the asset. Valid range: 0-0xFFFF. The value 0xFFFF means that the whole slot is included. Note You must enter the value 0x02 as structure. Otherwise the data record will be transferred to the IO controller with an error. IM_Annotation IM_OrderID AM_SoftwareRevision AM_HardwareRevision IM_Serial_Number IM_Annotation is a comment field. The article number is stored in IM_OrderID. If the asset is a SIMATIC component, the article number is entered. The software version is entered at AM_SoftwareRevision. If the asset also supports the I&M data, AM_SoftwareRevision should be padded with spaces and IM_Software_Revision should be used instead. The hardware version is entered at AM_HardwareRevision. If the asset also supports the I&M data, AM_HardwareRevision should be padded with spaces, using IM_Hardware_Revision instead. The serial number of the asset is entered under IM_SerialNumber. Entry ID: , V1.0, 05/

24 Siemens AG 2018 All rights reserved 3 Useful information IM_Software_Revision If the asset supports I&M data, IM_Software_Revision will display the software version in the form <Prefix> <Functional expansion> <BugFix> <Internal change>, e.g. V 0x01 0x02 0x03. The following rule applies as coding for the >prefix>: "V" Official version "R" Revision "P" Prototype "U" in the test "T" test device IM_Hardware_Revision If the asset supports I&M data, the hardware version is noted in IM_Hardware_Revision. Valid range: 0x0000-0xFFFF. AM_DeviceIdentification The AM_DeviceIdentification field is used to identify the asset. The AM_DeviceIdentification is divided into several elements: Bit 0-15 DeviceSubID: Valid range: 0x0000-0xFFFF. If it is a PROFINET asset, 0x0000 is entered. Bit DeviceID: The device ID is entered here. This should be consistent with the manufacturer (VendorID). Valid range: 0-0xFFFF. If it is a PROFINET asset, the PROFINET device number is entered. Bit VendorID is the manufacturer's identification. Valid range: 0x0000-0xFFFF. If it is a PROFINET Siemens asset, the 0x002A is used. For external assets, the manufacturer identifier of the asset. Bit Organization. If it is a PROFINET asset, 0x0000 (PROFINET/PROFIBUS) must be used. For non-profinet assets, the range 0x0100-0xFFFF is valid, e.g. HART 0x0104. The range 0x0001-0x00FF && 0x0109-0xFFFF is reserved. AM_TypeIdentification AM_TypeIdentification describes the type of the asset. The following coding is performed: Table 3-3 0x0000 0x0001 0x0002 0x0003 0x0004 0x0005 0x0006 0x0007 Value 0x0100 0x7FFF 0x0000 Unspecified Meaning Standard controller e.g. PLC PC based station IO module or IO submodule Communication modules or communication submodules Communication modules or communication submodules Active network infrastructure component Media Attachment Unit Freely definable by manufacturer, e.g. carrier module, terminal block, server module Unspecified Entry ID: , V1.0, 05/

25 Siemens AG 2018 All rights reserved 3 Useful information Other Value reserved Meaning 3.2 How the " Management" block works The " Management" function block has the following tasks: 1. It checks the IN_OUT parameters for correctness. This includes the following queries: Is the referenced tag an array or a NULL pointer? Is the data type of the referenced array tag of the type "typemanagamentonlysw", "typemanagamentonlyhw" or "typemanagamentfullinformation"? 2. The block determines the number of elements of the transferred array tags and thus calculates the number of bytes that all transferred asset management blocks need. 3. With the system application "Get_IM_Data" it reads the I&M data from every centrally plugged module. The I&M data of the module converts the block into an asset management block of the "full information" format. 4. The block calculates the number of bytes required by the (converted) asset management blocks for the centrally plugged modules. 5. Using the "Serialize" system application, the block creates the data structure required for the data record in the byte array of the "ManagementRecord" data block. 6. The block then uses the "Serialize" and "Move_BLK_VARIANT" system applications to copy the asset management blocks to the byte array of the "ManagementRecord" data block. 7. When all data has been copied and the data record is complete, the block releases the system application "PRVREC". The system application "PRVREC" makes the data record available to the higher-level IO controller. The IO controller uses the system application "RDREC" to read and receive the data record with the index 16#F880. Entry ID: , V1.0, 05/

26 Siemens AG 2018 All rights reserved 4 Appendix 4 Appendix 4.1 Service and Support Industry Online Support Do you have any questions or need assistance? Siemens Industry Online Support offers round the clock access to our entire service and support know-how and portfolio. The Industry Online Support is the central address for information about our products, solutions and services. Product information, manuals, downloads, FAQs, application examples and videos all information is accessible with just a few mouse clicks: Technical Support The Technical Support of Siemens Industry provides you fast and competent support regarding all technical queries with numerous tailor-made offers ranging from basic support to individual support contracts. Please send queries to Technical Support via Web form: SITRAIN Training for Industry We support you with our globally available training courses for industry with practical experience, innovative learning methods and a concept that s tailored to the customer s specific needs. For more information on our offered trainings and courses, as well as their locations and dates, refer to our web page: Service offer Our range of services includes the following: Plant data services Spare parts services Repair services On-site and maintenance services Retrofitting and modernization services Service programs and contracts You can find detailed information on our range of services in the service catalog web page: Industry Online Support app You will receive optimum support wherever you are with the "Siemens Industry Online Support" app. The app is available for Apple ios, Android and Windows Phone: Entry ID: , V1.0, 05/

27 Siemens AG 2018 All rights reserved 4 Appendix 4.2 Links and Literature Table 4-1 No. \1\ Siemens Industry Online Support Topic \2\ Link to this entry Change documentation Table 4-2 Version Date Modifications V1.0 05/2018 First version Entry ID: , V1.0, 05/