Download
Share
Print this page
  1. Manuals
  2. Brands
  3. HMS Networks Manuals
  4. Network Hardware
  5. Anybus CompactCom 40 POWERLINK
  6. Network manual

HMS Networks Anybus CompactCom 40 Network Manual

Profinet irt transparent ethernet
Hide thumbs Also See for Anybus CompactCom 40:

Advertisement

Quick Links

Download this manual
ENGLISH
®
™
Anybus
CompactCom
40 - PROFINET IRT Transparent
Ethernet
NETWORK GUIDE
SCM-1202-021
Version 2.6
Publication date 2023-06-29

Advertisement

loading
Need help?

Need help?

Do you have a question about the Anybus CompactCom 40 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for HMS Networks Anybus CompactCom 40

Summary of Contents for HMS Networks Anybus CompactCom 40

  • Page 1 ENGLISH ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet NETWORK GUIDE SCM-1202-021 Version 2.6 Publication date 2023-06-29...
  • Page 2 HMS Networks reserves the right to modify its products in line with its policy of continuous product development. The information in this document shall therefore not be construed as a commitment on the part of HMS Networks and is subject to change without notice.
  • Page 3 1.3. Document History ......................2 1.4. Document Conventions ..................... 2 1.5. Terminology ........................3 1.6. Trademarks ........................3 2. About the Anybus CompactCom 40 PROFINET IRT ................ 4 2.1. General .......................... 4 2.2. Features ......................... 4 2.3. Transparent Ethernet ......................4 3.
  • Page 4 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 5.1. General ......................... 28 5.2. Modular Device RI ......................28 5.3. Remap ........................... 28 5.4. Safety Module ........................ 29 5.5. Record Data ........................29 5.6. Modular Device Example ....................29 5.6.1.
  • Page 5 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.4.2. Object Description ....................44 10.4.3. Supported Commands .................... 44 10.4.4. Object Attributes (Instance #0) ................. 44 10.4.5. Instance Attributes (Instance #1) ................45 10.4.6. Command Details: Map_ADI_Write_Ext_Area ............. 46 10.4.7.
  • Page 6 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.9.2. Object Description ....................76 10.9.3. Supported Commands .................... 76 10.9.4. Object Attributes (Instance #0) ................. 76 10.9.5. Instance Attributes (Instance #1) ................77 10.9.6. Command Details: Error_Confirmation ............... 79 10.9.7.
  • Page 7 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.7.8. Command Details: AR_Check_Ind ................120 11.7.9. Command Details: Cfg_Mismatch_Ind ..............123 11.7.10. Command Details: Expected_Ident_Ind ..............124 11.7.11. Command Details: End_Of_Prm_Ind ..............127 11.7.12. Command Details: AR_Abort_Ind ................128 11.7.13.
  • Page 8 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 1. How to Design for AIDA LED Mode ..................148 2. Anybus CompactCom AIDA LED Mode ................. 148 2.1. Front View ......................148 2.2. Bus Failure LED ......................149 2.3. System Failure LED ....................149 2.4.
  • Page 9 Anybus CompactCom M40 Hardware Design Guide HMSI-216-126 Anybus CompactCom B40 Design Guide HMSI-27-230 Anybus CompactCom Host Application Implementation Guide HMSI-27-334 Anybus CompactCom 40 PROFINET IRT Network Guide SCM-1202-023 PROFINET IO specification Profibus International PROFIenergy Technical Specification Profibus International GSDML Technical Specification for PROFINET IO Profibus International SCM-1202-021 Version 2.6...
  • Page 10 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Document History Ethernet 1.3. Document History Version Date Description 2016-10-28 First public release 2016-11-23 Modular Device Minor Corrections 2017-01-18 Minor corrections 2017-03-15 PROFIenergy profile added Asset management and I&M5 added 2017-04-10 Updated to PROFIenergy 2 Minor corrections 2017-07-11...
  • Page 11 ® ™ Terminology Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Safety Symbols DANGER Instructions that must be followed to avoid an imminently hazardous situation which, if not avoided, will result in death or serious injury. WARNING Instructions that must be followed to avoid a potential hazardous situation that, if not avoided, could result in death or serious injury.
  • Page 12 This network guide covers the Transparent Ethernet version of the product. Transparent Ethernet has to be enabled during setup, or the device will appear as an Anybus CompactCom 40 with full IT functionality. The IT functionality is described in the network guide for the standard Anybus CompactCom 40.
  • Page 13 Ethernet. Also TCP/UDP ports may be reserved, and can, in that case, not be used for the transparent Ethernet communication. See also ... • Transparent Ethernet (page 35) • Anybus CompactCom 40 Hardware Design Guide • Anybus Object (01h) (page 40) SCM-1202-021 Version 2.6 Page 5 of 177...
  • Page 14 3.1. General Information 3.1.1. Software Requirements Generally, no additional network support code needs to be written to support the Anybus CompactCom 40 PROFINET IRT, however due to the nature of the PROFINET networking system certain things must be taken into account: •...
  • Page 15 – Network Components – Sensors • Replace the ProductFamily value “Anybus CompactCom 40 PIR” with a string which describes your device. In addition to the above, there are a few more places where identity related information is present in the GSD file.
  • Page 16 This service can be used at any time and will write data to a defined ADI. The initial record data is defined in the GSD file, and is specified for a submodule of a module. By default, the Anybus CompactCom 40 module will not make use of any initial record data, but that can be enabled if needed.
  • Page 17 These settings must be set in order for the module to be able to participate on the network. Normally set by the IO Controller. IP settings must be synchronized between the Anybus CompactCom 40 and the host application. PROFINET Station Name The module needs to be assigned a Station Name in order to participate on PROFINET.
  • Page 18 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Data Exchange Ethernet 3.4. Network Data Exchange 3.4.1. Application Data Instances (ADIs) ADIs can be accessed acyclically from the network by means of Record Data read/write services. If addressed through a given API and Index range, the module translates the service into standard object requests towards the Application Data Object.
  • Page 19 ® ™ Network Data Exchange Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 3.4.3. Caveats The length parameter in the Record Data request specifies the number of bytes to read/write. • When reading more data than the actual size of the ADI, the response will only contain the actual ADI data, i.e. no padding on the data is performed by the module.
  • Page 20 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET Implementation Details Ethernet 4. PROFINET Implementation Details 4.1. General Information This chapter covers PROFINET specific details in the Anybus implementation. Note that the use of such functionality may require in-depth knowledge in PROFINET networking internals and/or information from the official PROFINET specification.
  • Page 21 ® ™ Application Relationships (AR) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.3. Application Relationships (AR) On PROFINET, a connection between an IO Controller/Supervisor and an I/O device (in this case the Anybus) is called Application Relationship (AR). The Anybus module supports multiple simultaneous Application Relationships, allowing multiple IO Supervisors to access its data and functions.
  • Page 22 System redundancy for PROFINET is available in different setups. The S2 functionality, implemented in the Anybus CompactCom 40 PROFINET IRT, makes it possible for two PROFINET IO Controllers, one primary and one backup, to connect to the device. If the primary IO Controller fails, the backup IO Controller instantly takes over the communication without any disturbance on the network.
  • Page 23 4.5. Real Identification (RI) 4.5.1. General Information During the establishment of an IO Connection towards the Anybus CompactCom 40 PROFINET IRT, the configuration derived from the IO Controller (i.e. the Expected Identification) and the actual configuration in the Anybus CompactCom 40 PROFINET IRT (i.e. the Real Identification or RI) are compared.
  • Page 24 ADIs are represented on PROFINET by defining custom modules and submodules. These commands need to be sent after the process data is mapped, and before sending setup complete to the Anybus CompactCom 40 PROFINET IRT. See also...
  • Page 25 A configuration mismatch occurs when the Real Identification (RI) does not match the Expected Identification. Depending on how the RI configuration is established, the Anybus CompactCom 40 PROFINET IRT will first try to resolve the mismatch as described in the applicable section below (Resolving Mismatch for default configuration or custom configuration).
  • Page 26 Further Actions to Resolve Mismatch If the mismatch remains unsolved, either for default or custom configuration, the following will be performed by the Anybus CompactCom 40 PROFINET IRT to find a solution that will make exchange of valid data possible: Incomplete output mapping: If the controller tries to connect to fewer output submodules than are plugged by the application, the controller will not be granted ownership of any output submodule.
  • Page 27 ® ™ Diagnostics Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.6. Diagnostics 4.6.1. Standard Diagnostics PROFINET IO devices uses alarms when informing the IO Controller of diagnostic entries. In the Anybus implementation, it is possible for the application to create alarms via diagnostic entries by means of the Diagnostic Object (02h).
  • Page 28 While I&M0 information describes the application, the I&M5 information describes the communication unit i.e. the Anybus CompactCom 40 PROFINET IRT, to the PROFINET network. Most of the information is provided by the module, but the application can change the order ID and the IM annotation (attributes #25 and #26, see PROFINET IO Object (F6h) (page 112)).
  • Page 29 Hardware version of the Anybus CompactCom Software revision 4 bytes Product version of the Anybus CompactCom See also.. • PROFINET IO Object (F6h) (page 112) • Anybus CompactCom 40 Software Design Guide, Application Object (FFh) SCM-1202-021 Version 2.6 Page 21 of 177...
  • Page 30 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Asset Management Ethernet 4.8. Asset Management Asset management provides means to collect information on non PROFINET automation components, that are connected to PROFINET networked devices. These components are not part of the PROFINET system, but the collected information will facilitate troubleshooting and exchange of faulty components.
  • Page 31 ® ™ Fast Start Up Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.9. Fast Start Up 4.9.1. General Information The Fast Start Up (FSU) function enables PROFINET IO devices, connected to the network, to power up quickly. This is useful in, for example, robot applications, where rapid retooling is necessary. With FSU activated, the module will send a DCP Hello message as soon as possible after power-on.
  • Page 32 Ethernet 4.10. Address Conflict Detection (ACD) The Anybus CompactCom 40 PROFINET IRT supports Address Conflict Detection (ACD). This mechanism involves the following two aspects: • Initial probing: before using an IP address, the module issues ARP probes to see if the address is already in use (three probes with a 100 ms delay).
  • Page 33 4.11.1. Implementation The PROFIenergy profile is implemented in the Anybus CompactCom 40 PROFINET IRT according to the state machine described in the PROFIenergy Technical Specification (available from PROFIBUS International). PROFIenergy commands arriving from the network will be translated into the Anybus CompactCom...
  • Page 34 4.12. PROFIsafe The Anybus CompactCom 40 PROFINET IRT supports the PROFIsafe profile. This profile makes it possible for a user to send data on a black channel interface, i.e. a safe channel over PROFINET using an add on Safety Module, e.g.
  • Page 35 ® ™ Factory Reset from Network Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.13. Factory Reset from Network Performing a factory reset from the network is done using the Discovery and Basic Configuration Protocol (DCP), a protocol for PROFINET used for name and address resolution. The supported reset types and their execution behavior are described in this section.
  • Page 36 The RI, when implementing a modular device, is generated from the Module IDs as defined in the Modular Device Object (ECh) (see the Anybus CompactCom 40 Software Design Guide) and from the process data mappings as shown in the example below.
  • Page 37 ® ™ Safety Module Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 5.4. Safety Module A safety module, such as the IXXAT Safe T100/PS may be used within the modular device concept. If enabled, the safety module will be plugged into slot 1 and the host application will not be allowed to add a process data mapping for any ADI within the range of this slot.
  • Page 38 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Modular Device Example Ethernet 5.6.3. Device Layout Modular Device – API 0 Slot 0 – Head node (ADI 1..256) - Module ident: 0xA0000001 Subslot 1 – DAP Subslot 0x8000 – Interface Subslot 0x8001 –...
  • Page 39 ® ™ Recommendations Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 5.7. Recommendations 5.7.1. I&M Data Identification & Maintenance data may be used by the engineering tool to assist in resolving mismatching configurations. By comparing the OrderID from the expected GSD module with the OrderID from the I&M data of the actual, plugged module, the user can adapt the configuration to match the real identification.
  • Page 40 132). 6.3. Management Information (MIB) A MIB is a device database that is accessed by an SNMP agent. The Anybus CompactCom 40 PROFINET IRT supports standardized MIBs: LLDP-MIB and MIB-II. Standardized MIBs are defined in RFC standards and contain variables that are divided into so called groups. The host application can change the values of some of the variables for the MIB-II.
  • Page 41 ® ™ MIB-II Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 6.4.2. Interfaces Group Variables Access authorizations for all variables are read only with values from internal sources. The number in brackets refers to the port number (1 - Port 1, 2 - Port 2, 3 - Internal port) If nothing else is specified, the value of a variable is 0.
  • Page 42 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Media Reduncancy Protocol (MRP) Ethernet 7. Media Reduncancy Protocol (MRP) 7.1. General Media Redundancy Protocol (MRP) is a PROFINET specific ring protocol ensuring redundancy in the network, which can significantly decrease network downtime. It is a token based ring protocol with a master-slave hierarchy.
  • Page 43 ® ™ Transparent Ethernet Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 8. Transparent Ethernet 8.1. General Information Transparent Ethernet offers the possibility for a host application, that includes an IT implementation, to let the Anybus CompactCom handle an industrial Ethernet protocol (in this case PROFINET), without the need for extra Ethernet ports.
  • Page 44 Transparent Ethernet is not enabled at delivery. Attribute #16 (instance #1) in the Anybus Object (01h) has to be set to 0002h during setup. If this attribute is not changed, the Anybus CompactCom 40 PROFINET IRT will start up with full IT functionality instead of transparent Ethernet functionality. Transparent Ethernet cannot be enabled after setup is finished.
  • Page 45 ® ™ Routing Restrictions Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • X3-XX-00-00-00-00 (X: any number 0-F) 8.5.3. UDP/TCP Ports The following ports may be used by the Anybus CompactCom, and must not be used by the host application: •...
  • Page 46 Ethernet 9. Firmware Upgrade The Anybus CompactCom 40 PROFINET IRT firmware can be updated either by running the Firmware Manager II tool (FMII), available at www.anybus.com/support, or by downloading the firmware upgrade file directly to the host application file system. For any of these methods to work the following needs to be implemented and/or performed: •...
  • Page 47 ® ™ Anybus Module Objects Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10. Anybus Module Objects 10.1. General Information Standard Objects: • Anybus Object (01h) (page 40) • Diagnostic Object (02h) (page 41) • Network Object (03h) (page 44) •...
  • Page 48 10.2.3. Supported Commands Object: Get_Attribute Reset Instance: Get_Attribute Set_Attribute Get_Enum_String 10.2.4. Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) 10.2.5. Instance Attributes (Instance #1) Basic Name Access Type Value Module type UINT16 0403h (Standard Anybus CompactCom 40) 2...
  • Page 49 10.3. Diagnostic Object (02h) 10.3.1. Category Extended 10.3.2. Object Description This object provides a standardized way of handling host application events & diagnostics, and is thoroughly described in the general Anybus CompactCom 40 Software Design Guide. 10.3.3. Supported Commands Object: Get_Attribute Create...
  • Page 50 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Diagnostic Object (02h) Ethernet Major unrecoverable events cause the module to disconnect itself from the network, thus preventing network participation. Other severity levels either produce a Channel Diagnostic entry/alarm or a Generic Diagnostic entry/alarm, depending on the Event Code: Event Code Result...
  • Page 51 ® ™ Diagnostic Object (02h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.3.7. Object Error Codes Code Error API does not exist No module inserted in the specified slot No submodule inserted in the specified subslot Slot number specified is out-of-range Subslot number specified is out-of-range Failed to add the channel diagnostic entry Failed to send the channel diagnostic alarm...
  • Page 52 Anybus CompactCom 40 Software Design Guide. 10.4.3. Supported Commands Object: Get_Attribute Instance: Get_Attribute Set_Attribute Get_Enum_String Map_ADI_Write_Area Map_ADI_Read_Area Map_ADI_Write_Ext_Area Map_ADI_Read_Ext_Area 10.4.4. Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) Page 44 of 177 SCM-1202-021 Version 2.6...
  • Page 53 Write process data size UINT16 Current write process data size (in bytes) Updated on every successful Map_ADI_Write_Area. (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) Read process data size UINT16 Current read process data size (in bytes) Updated on every successful Map_ADI_Read_Area.
  • Page 54 ADI 0. Padding bits might not be visible on the network. • This command may permanently alter the state of the Anybus CompactCom 40 PROFINET IRT even though the command is returned with an error. Network specific restrictions may lead to n mapping items to be accepted, but with an error on mapping item n+1.
  • Page 55 ® ™ Network Object (03h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • Command details: Field Contents CmdExt[0] The number of mapping items to add (0-217) CmdExt[1] Reserved. Set to 0 MsgData[0-1] New mapping item 1: ADI number MsgData[2] New mapping item 1: Number of elements in the ADI MsgData[3] New mapping item 1: Index to the first element to map (0-254)
  • Page 56 Instance Description This command is only supported by Anybus CompactCom 40 devices. This command is equivalent to Map_ADI_Read_Area, but can map more than 256 bytes of data. It is identical to Map_ADI_Write_Ext_Area, described above, except that it maps ADIs to Read Process Data.
  • Page 57 UINT16 Supported number of instances Highest instance number UINT16 Highest instance number (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) 10.5.5. Instance Attributes (Instance #3, IP Address) Value is used after module reset. Name Access Data Type...
  • Page 58 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Configuration Object (04h) Ethernet IMPORTANT This attribute should not be set by the application at every power on, as this would cause certification problems. 10.5.6. Instance Attributes (Instance #4, Subnet Mask) Value is used after module reset.
  • Page 59 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Name Access Data Type Description Name Array of CHAR “DHCP” (Multilingual, see page Multilingual Strings (page 54)) Data type UINT8 08h (= ENUM) Number of elements UINT8 01h (one element) Descriptor...
  • Page 60 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Configuration Object (04h) Ethernet 10.5.10. Instance Attributes (Instance #10, DNS2) This instance holds the address to the secondary DNS server. Changes are valid after reset. Name Access Data Type Description Name Array of CHAR “DNS2”...
  • Page 61 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.5.14. Instance Attributes (Instance #20, Station Name) The Station Name identifies the Anybus module on PROFINET. If this value is changed by the host application during runtime, a reset is required in order for changes to have effect. Changes made through DCP will have immediate effect, however.
  • Page 62 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Configuration Object (04h) Ethernet Name Access Data Type Description Name Array of CHAR “F-Address” (Multilingual, see page Multilingual Strings (page 54)) Data type UINT8 05h (= UINT16) Number of elements UINT8 01h (one elements) Descriptor...
  • Page 63 This object provides an interface to the built-in file system. Each instance represents a handle to a file stream and contains services for file system operations. This object is thoroughly described in Anybus CompactCom 40 Software Design Guide. SCM-1202-021 Version 2.6...
  • Page 64 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Ethernet Object (0Ch) Ethernet 10.7. Network Ethernet Object (0Ch) 10.7.1. Category Extended 10.7.2. Object Description This object provides Ethernet-specific information to the application. The object has three instances, each corresponding to a port: Instance # Port Internal port...
  • Page 65 ® ™ Network Ethernet Object (0Ch) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.7.5. Instance Attributes (Instances #1 - #3) Name Access Data Type Description MAC Address Array of UINT8 Reserved, used for backwards compatibility. (Device MAC address.) (See also Ethernet Host Object (F9h) (page 132)) Port 1 MAC Address...
  • Page 66 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Ethernet Object (0Ch) Ethernet 10.7.7. Media Counters Array indices of Media Counters attribute (#6) Index Name Description AlignmentErrors; Frames received that are not an integral number of octets in length FCSErrors;...
  • Page 67 10.8.1. Category Extended 10.8.2. Object Description When the application maps ADIs to process data during start-up, the Anybus CompactCom 40 PROFINET IRT will create the module configuration as described in Real Identification (RI) (page 15). The modules in the GSDML file must then be described in the same way.
  • Page 68 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet Removing and Exchanging Modules and Submodules If the RI has been created by the host application through custom configuration, there are ways of removing modules and plug new modules during runtime. The application will be notified by the command Cfg_Mismatch_Ind for every submodule that does not match.
  • Page 69 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.8.5. Instance Attributes (Instance #1) Extended Name Access Type Value OnLineTrans UINT32 Diagnostic counters; keeps track of the number of on-line transitions OffLineTrans UINT32 Diagnostic counters; keeps track of the number of off-line transitions (reserved) Last AbortInd ReasonCode UINT16...
  • Page 70 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet 10.8.6. Command Details: Plug_Module Category Extended Details Command Code: Valid For: Object Instance Description This command may be called during start-up to specify the Real Identification. It may also be called during runtime in case there are changes to the Real Identification.
  • Page 71 A submodule plugged with this command can hold IO data to the master, from the master or data in both directions. It is also possible to plug submodules which do not carry any data at all. The Anybus CompactCom 40 PROFINET IRT supports up to 128 submodules in total. NOTE In case the slot number in the command is set to 0 (zero), the ADI number must also be 0 (zero), since slot 0 cannot hold any actual data.
  • Page 72 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet • Command Details Field Contents Comments CmdExt[0] Bit 0: Submodule type 0: Normal I/O submodule 1: Safety submodule (no ADI mapping, set Data[0..5] to 0) Bit 1-7: (reserved, set to zero) (reserved for future use) CmdExt[1]...
  • Page 73 A submodule plugged with this command can hold IO data to the master, from the master or data in both directions. It is also possible to plug submodules which do not carry any data at all. The Anybus CompactCom 40 PROFINET IRT supports up to 128 submodules in total. NOTE In case the slot number in the command is set to 0 (zero), the ADI number must also be 0 (zero), since slot 0 cannot hold any actual data.
  • Page 74 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet • Command Details Field Contents Comments CmdExt[0] Bit 0: Submodule type 0: Normal I/O submodule 1: Safety submodule (no ADI mapping, set Data[0..7] to 0) Bit 1-7: (reserved, set to zero) (reserved for future use) CmdExt[1]...
  • Page 75 This command removes a module from the configuration. Can be issued at any time. During runtime, it can be called in case there are changes to the Real Identification. The Anybus CompactCom 40 PROFINET IRT then automatically issues a Pull or Pull Module alarm to the master.
  • Page 76 This command removes a submodule from the configuration and can be issued at any time. During runtime, it can be called in case there are changes to the Real Identification. The Anybus CompactCom 40 PROFINET IRT then automatically issues a Pull alarm to the master.
  • Page 77 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.8.11. Command Details: API_Add Category Extended Details Command Code: Valid For: Object Instance Description By default, the module only supports API 0 (zero). If additional APIs are to be supported, or if the host application shall handle plugging/unplugging of modules and submodules, this command must be used to specify the API implementation.
  • Page 78 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet 10.8.12. Command Details: Appl_State_Ready Category Extended Details Command Code: Valid For: Object Instance Description This command is only applicable if the host application implements support for End_Of_Prm_Ind, and signals to the module (and in turn the I/O Controller) that the host application is ready for data exchange.
  • Page 79 > 0 to nonvolatile memory. In this case, all modules that carry discrete I&M data shall be included in the I&M0 Carrier Data. (The Anybus CompactCom 40 PROFINET IRT will include the DAP submodule (located in slot 0, subslot 1) in the I&M0 Carrier Data and Device Representative Data.) When transparent I&M data for slot 0 is enabled, the application must store I&M data for slot 0 to nonvolatile...
  • Page 80 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet • Command Details If the I&M0 Filter Data is of no interest, the Data Field is left out (command length = 0). The command may contain one or several I&M0 Filter Data entries. The maximum amount of entries depends on the application.
  • Page 81 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.8.15. Command Details: Ident_Change_Done Category Extended Details Command Code: Valid For: Object Instance Description This command shall be sent to the module when the host application has finished its adaptations of the Real Identification.
  • Page 82 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network PROFINET IO Object (0Eh) Ethernet 10.8.16. Command Details: Add_Safety_Module Category Extended Details Command Code: Valid For: Object Instance Description Usage of this command is conditional. • If API_Add has been issued, ADD_Safety_Module must be issued. Any slot can be specified (1... 7FFFh). •...
  • Page 83 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.8.17. Object Specific Error Codes Code Meaning The ADI has not been mapped with command Map_ADI_Write_Area The ADI has not been mapped with command Map_ADI_Read_Area Element does not exist for the ADI This ADI/element is already mapped API 0 must be added first...
  • Page 84 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Functional Safety Module Object (11h) Ethernet 10.9. Functional Safety Module Object (11h) 10.9.1. Category Extended 10.9.2. Object Description This object contains information provided by the Safety Module connected to the Anybus CompactCom module. Please consult the manual for the Safety Module used, for values of the attributes below.
  • Page 85 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.9.5. Instance Attributes (Instance #1) Name Access Data Type Description State UINT8 Current state of the Safety Module Please consult the manual for the Safety Module used. Vendor ID UINT16 Identifies vendor of the Safety Module.
  • Page 86 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Functional Safety Module Object (11h) Ethernet Exception Information If Exception Code 09h is set in the Anybus object, there is an error regarding the functional safety module in the application. Exception information is presented in instance attribute #10 according to this table: Value Exception Information No information...
  • Page 87 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 10.9.6. Command Details: Error_Confirmation Category Extended Details Command Code: Valid For: Object Description When the Safety Module has entered the Safe State, for any reason, it must receive an error confirmation before it can leave the Safe State.
  • Page 88 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Functional Safety Module Object (11h) Ethernet 10.9.7. Command Details: Set_IO_Config_String Category Extended Details Command Code: Valid For: Object Description This command is sent from the host application when there is a need to change the default configuration of the safety inputs and outputs.
  • Page 89 Description This command can be issued by the application to get the complete safety output PDU sent by the PLC. The Anybus CompactCom 40 PROFINET IRT will respond with the complete safety PDU, that the application then has to interpret.
  • Page 90 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Functional Safety Module Object (11h) Ethernet 10.9.10. Object Specific Error Codes Error Code Description Comments The safety module rejected a message. Error code sent by safety module is found in MsgData[2] and MsgData[3]. Message response from the safety module has incorrect format (for example, wrong length).
  • Page 91 Energy Measurement Object (E4h) (page 84) • Functional Safety Object (E8h) (page 100) • “ Application File System Object (EAh)” (see Anybus CompactCom 40 Software Design Guide) • “ Modular Device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide) •...
  • Page 92 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet 11.2. Energy Measurement Object (E4h) 11.2.1. Category Extended 11.2.2. Object Description This object defines a standardized way of reporting different types of measurement values (current, voltage, power, energy etc.) from a measuring device.
  • Page 93 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.2.4. Object Attributes (Instance #0) Name Access Data Type Value Name Array of CHAR “Energy Measurement” Revision UINT8 Number of instances UINT16 One instance per supported measurement device Highest instance no.
  • Page 94 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID VoltagePH-N UINT64 0: L1-N TS FLOAT 1: L1-N Value UINT32 2: Reserved UINT64 3: L2-N TS FLOAT 4: L2-N Value UINT32...
  • Page 95 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID UINT64 3: L2-L3 TS FLOAT 4: L2-L3 Value UINT32 5: Reserved UINT64 6: L3-L1 TS FLOAT 7: L3-L1 Value UINT32...
  • Page 96 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID UINT64 6: L3-G TS FLOAT 7: L3-G Value UINT32 8: Reserved UINT64 9: Avg L-G TS FLOAT 10: Avg L-G Value UINT32...
  • Page 97 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID Apparent Power UINT64 0: L1 TS FLOAT 1: L1 Value UINT32 2: Reserved UINT64 3: L2 TS FLOAT 4: L2 Value...
  • Page 98 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID UINT64 3: L2 TS FLOAT 4: L2 Value UINT32 5: Reserved UINT64 6: L3 TS FLOAT 7: L3 Value UINT32...
  • Page 99 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID UINT64 6: L3 TS FLOAT 7: L3 Value UINT32 8: Reserved UINT64 9: Total TS FLOAT 10: Total Value UINT32...
  • Page 100 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet Attr ID# Access Rule Name Data Type Element number:description PROFIenergy Measurement ID Field rotation UINT64 0: Field rotation TS FLOAT 1: Field rotation Value UINT32 2: Reserved Total Active energy(Sum UINT64 0: Consumed TS...
  • Page 101 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet The table below describes how the generic values for the different variable categories are represented on PROFINET. Attr # Variable category Unit Comments Voltage RMS value Absolute value 10-12 Current...
  • Page 102 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Measurement Object (E4h) Ethernet 11.2.6. Command Details: Get_Attribute_Measurement_List Details Command Code: Valid For: Instance Description This command is used to gather all supported attribute elements of an instance. If several instances are supported, the command will be sent numerous times (implied by object attribute Highest instance number).
  • Page 103 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • Response Details Field Contents Description Data[0 - 1] Attribute #1 Data type: BITS16 Bit 0 – First element Data[2 - 3] Attribute #2 Bit 1 – Second element Data[...] …...
  • Page 104 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Asset Management Object (E5h) Ethernet 11.3. Asset Management Object (E5h) 11.3.1. Category Extended 11.3.2. Object Description This object implements asset management information, i.e. identification information about one or several non PROFINET components of a device. Each component is represented by one object instance. The application collects identification information and assembles it in the instance attributes for each object instance.
  • Page 105 ® ™ Asset Management Object (E5h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Name Access Data Type Default Comment Value AM info Type UINT8 Asset management data representation AM_FullInfo AM_HardwareOnlyInfo; attributes AM Software Revision and IM Software Revision are irrelevant AM_FirmwareOnlyInfo;...
  • Page 106 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Asset Management Object (E5h) Ethernet Name Access Data Type Default Comment Value AM Hardware Array of CHAR 64 blanks Manufacturer defined hardware revision Revision Maximum number of elements in array: 64 If attribute #14, IM Hardware Revision, is supported, then this attribute should not be implemented.
  • Page 107 ® ™ Asset Management Object (E5h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.3.7. AM_DeviceIdentification Array index Description Organization (0=PI) 0: Must be used 1–FFFFh: reserved Vendor ID Device ID Device Sub ID: 0: Must be used 1–FFFFh: reserved SCM-1202-021 Version 2.6 Page 99 of 177...
  • Page 108 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Functional Safety Object (E8h) Ethernet 11.4. Functional Safety Object (E8h) 11.4.1. Category Extended 11.4.2. Object Description IMPORTANT Do not implement this object if a safety module is not used. This object specifies the safety settings of the application. It is mandatory if Functional Safety is to be supported and a Safety Module is connected to the Anybus CompactCom module.
  • Page 109 ® ™ Functional Safety Object (E8h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.4.5. Instance Attributes (Instance #1) Name Access Data Type Default Value Comment Safety enabled BOOL When TRUE, enables communication with the Safety Module. NOTE If functional safety is not supported, this attribute must be set to FALSE.
  • Page 110 11.5.2. Object Description This object contains the host object sync settings. The implementation of this object is optional. If it is not implemented the Anybus CompactCom 40 PROFINET IRT can not be used for a synchronous application. If there is any problem with the configuration of the sync functionality as a whole, the application must indicate this in the application status register.
  • Page 111 The sync functionality is described differently in the PROFINET network specification than how it is described in the specification for Anybus CompactCom in general. See the Anybus CompactCom 40 Software Design Guide for a detailed description of the Anybus CompactCom sync functionality.
  • Page 112 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Sync Object (EEh) Ethernet T_IO_InputMin T_IO_InputMin consists of two delays: • The delay added by the Anybus CompactCom. This is the time from when the message is available in the device until it is available on the network. This delay is 12 μs in the current implementation. •...
  • Page 113 ® ™ Sync Object (EEh) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.5.7. Instance Attributes (Instance #1) Name Access Corresponding term Data Value for PROFINET Type Cycle time Get/Set T_DC UINT32 Application cycle time in nanoseconds Output valid Get/Set T_IO_Output UINT32 Output valid point relative to SYNC events, in nanoseconds...
  • Page 114 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Control Object (F0h) Ethernet 11.6. Energy Control Object (F0h) 11.6.1. Category Extended 11.6.2. Object Description This object implements energy control functionality, i.e. energy specific settings, in the host application. The implementation of this object is optional.
  • Page 115 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.6.3. Supported Commands Object: Get_Attribute StartPause EndPause Preview_Pause_Time (not PROFINET) Instance: Get_Attribute 11.6.4. Object Attributes (Instance #0) Name Access Data Type Value Name Array of CHAR “Energy Control”...
  • Page 116 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Control Object (F0h) Ethernet 11.6.5. Instance Attributes (Instance #1 - #8) Name Access Data Type Description ModeAttributes BITS16 Bit 0: Meaning: Only static time and energy values are available (Value of bit 0 attribute is not implemented) Dynamic time and energy values are available Bit 1-15:...
  • Page 117 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Command Details: Start_Pause Details Command Code: Valid For: Object Description This command is sent to the host application when the system wants to initialize a pause of the system. The length of the pause is specified in milliseconds.
  • Page 118 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Energy Control Object (F0h) Ethernet Command Details: End_Pause Details Command Code: Valid For: Object Description This command is sent to the host application when the system wants to return the system from a pause mode back to “Ready to operate”...
  • Page 119 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Command Details: Preview_Pause_Time Details Command Code: Valid For: Object Description Not used for PROFINET devices. This command is sent to the host application when the system wants to preview the application’s choice of Energy saving mode.
  • Page 120 See also... • Network PROFINET IO Object (0Eh) (page 59) • Flowchart — Record Data Access (page 139) • Anybus CompactCom 40 Software Design Guide, “Error Codes” 11.7.3. Supported Commands Object: Get_Attribute (01h) Get_Record (10h, see below) Set_Record (11h, see below)
  • Page 121 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.7.5. Instance Attributes (Instance #1) Basic Name Access Data Type Default Comment Device ID UINT16 0010h Identifies the device. (Assigned by manufacturer) If not implemented, the default value will be used. Vendor ID (I&M UINT16 010Ch (HMS...
  • Page 122 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet Name Access Data Type Default Value Comment MaxAr UINT32 0000 0003h Max. no.of simultaneous ARs. (Range 1... 4) Note 1: With S2Enabled = True, MaxAr needs to be at least 2. GSDML attribute NumberOfDeviceAccessAR must be set to MaxAr - 2.
  • Page 123 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Name Access Data Type Default Value Comment Port 2 MAC Array of 6 byte physical address value; overrides the preprogrammed Mac address. address UINT8 Do not implement this attribute if the preprogrammed Mac address is to be used.
  • Page 124 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet 11.7.6. Command Details: Get_Record Category Extended Details Command Code: Valid For: Object Instance Description The module issues this command in the following situations: • Module receives a Record Data Read request towards an API other than 0 (zero). •...
  • Page 125 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • Response Details (Error) Field Contents Comments CmdExt[0... 1] (reserved) (set to zero) MsgData[0] Object specific error MsgData[1] Error Code 1 Details: Error Code 1 (page 131) MsgData[2] Error Code 2 User specific error code...
  • Page 126 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet 11.7.7. Command Details: Set_Record Category Extended Details Command Code: Valid For: Object Instance Description The module issues this command in the following situations: • Module receives a Record Data Write request towards an API other than 0 (zero). •...
  • Page 127 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet See also... • Command details for “Get_Record” • Flowchart — Record Data Access (page 139) SCM-1202-021 Version 2.6 Page 119 of 177...
  • Page 128 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet 11.7.8. Command Details: AR_Check_Ind Category Extended Details Command Code: Valid For: Object Instance Description The module issues this command to inform the host application that an Application Relationship (AR) is to be established.
  • Page 129 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • Command Details Field Contents Comments CmdExt[0] AR handle (low byte) Handle for Application Relationship (AR) CmdExt[1] AR handle (high byte) MsgData[0] IP address (low word, low byte) IP address of the remote station (IO Controller/Supervisor) MsgData[1] IP address (low word, high byte)
  • Page 130 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet Bit(s) Value / Description Combined object container (COC) with StartupMode = Legacy No COC (reserved) with StartupMode = Advanced No COC Usage of COC required Startup mode: Legacy Advanced Pull module alarm allowed:...
  • Page 131 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.7.9. Command Details: Cfg_Mismatch_Ind Category Extended Details Command Code: Valid For: Object Instance Description The module issues this command to inform the host application that the configuration in the IO Controller (i.e. the Expected Identification) does not match the configuration defined by the host application (i.e.
  • Page 132 Expected_Ident_Ind is similar to AR_Info_Ind but uses a different segmentation protocol that shall be used for the CompactCom 40 series, see Anybus CompactCom 40 Software Design Guide (Message Segmentation). For very large configurations where the Expected Identification cannot fit into one message, this segmentation protocol will be used.
  • Page 133 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Data Format When all data has been received, the resulting data shall be interpreted as follows: Type Name Description UINT16 iNbrApi Number of APIs in configuration UINT32 iApiNbr Initial module block including API number and number of module blocks in the API.
  • Page 134 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet Example Initial API Block No. of APIs 0002h Initial Module Block API no. 00 00 00 00h (API #0) No. of Modules 0002h Slot no. 0001h Module Block No.
  • Page 135 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.7.11. Command Details: End_Of_Prm_Ind Category Extended Details Command Code: Valid For: Object Instance Description The module may issue this command to indicate to the host application that the parameterization phase is completed.
  • Page 136 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet 11.7.12. Command Details: AR_Abort_Ind Category Extended Details Command Code: Valid For: Object Instance Description This command is optional. The module issues this command to indicate to the host application that an Application Relationship (AR) is aborted (by the application or any other source).
  • Page 137 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet • Response Details (no data) 11.7.13. Command Details: Indicate_Device Category Extended Details Command Code: Valid For: Object Instance Description This command is optional. The module issues this command to inform the application that the DCP command Set Control/Signal has been received on the network.
  • Page 138 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent PROFINET IO Object (F6h) Ethernet 11.7.14. Command Details: Prm_Begin_Ind Category Extended Details Command Code: Valid For: Object Instance Description This command is optional. The module issues this command to indicate to the host application that a parameterization phase, outside of the connection establishment, is initiated.
  • Page 139 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.7.15. Details: Error Code 1 The error codes below shall be used when providing error responses to the following commands: • Get_Record • Set_Record • Get_IM_Record •...
  • Page 140 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Host Object (F9h) Ethernet 11.8. Ethernet Host Object (F9h) 11.8.1. Object Description This object implements Ethernet features in the host application. 11.8.2. Supported Commands Object: Get_Attribute Instance: Get_Attribute Set_Attribute 11.8.3. Object Attributes (Instance #0) Name Access Data Type...
  • Page 141 ® ™ Ethernet Host Object (F9h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Name Access Data Type Default Value Comment MAC address Array of UINT8 6 byte physical address value; overrides the preprogrammed Mac address. Note that the new Mac address value must be obtained from the IEEE.
  • Page 142 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Host Object (F9h) Ethernet Name Access Data Type Default Value Comment 02h: Inactive. The attribute is set to this value for a device that only has one physical port. All two-port functionality is disabled. No references can be made to this port.
  • Page 143 ® ™ Ethernet Host Object (F9h) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 11.8.5. Network Status This attribute holds a bit field which indicates the overall network status as follows: Contents Description Comment Link Current global link status EtherCAT only: This link status indicates whether the Anybus CompactCom is able to communicat using Ethernet over EtherCAT (EoE) or not.
  • Page 144 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Categorization of Functionality Ethernet Appendix A. Categorization of Functionality The objects, including attributes and services, of the Anybus CompactCom and the application are divided into two categories: basic and extended. 1. Basic This category includes objects, attributes and services that are mandatory to implement or to use.
  • Page 145 ® ™ Anybus Implementation Details Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Appendix B. Anybus Implementation Details 1. SUP-Bit Definition The supervised bit (SUP) indicates that the network participation is supervised by another network device. In the case of PROFINET, this bit is set when one or more IO connections are established. 2.
  • Page 146 For GSDML entries, see the SYNC example GSDML file that is included in the configuration files package, that can be downloaded from the Anybus CompactCom 40 PROFINET IRT page at www.anybus.com/support. 4. Application Watchdog Timeout Handling Upon detection of an application watchdog timeout, the module will cease network participation and shift to the state EXCEPTION.
  • Page 147 ® ™ Flowcharts Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Appendix C. Flowcharts 1. Flowchart — Record Data Access This flowchart illustrates how Record Data requests are handled by the Anybus module. Incoming Record Data Request Reject Api/Slot/Subslot Record Data inserted? request PROFIsafe...
  • Page 148 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Flowchart — I&M Record Data Handling Ethernet 2. Flowchart — I&M Record Data Handling This flowchart illustrates how I&M Record Data requests are handled by the Anybus module. I&M request ReadRecord OR Reject request Format Check >0...
  • Page 149 ® ™ Flowchart —Establishment of Real Identification (RI) Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 3. Flowchart —Establishment of Real Identification (RI) This flowchart illustrates the establishment of the Real Identification. (Power on) Map ADIs (Map_ADI_Write_Area) (Map_ADI_Read_Area) Issue 'API_Add' Customize RI? (API #0) Support...
  • Page 150 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Flowcharts — Handling of Configuration Mismatch Ethernet 4. Flowcharts — Handling of Configuration Mismatch 4.1. Default Configuration Mismatch This flowchart shows how the Anybus CompactCom automatically handles a configuration mismatch when the Real Identification has been established by the default configuration method.
  • Page 151 ® ™ Flowcharts — Handling of Configuration Mismatch Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.2. Custom Configuration mismatch This flowchart shows how to handle a configuration mismatch when the Real Identification has been established by the host application (custom configuration). Application receives Expected_Ident_Ind TRUE...
  • Page 152 Protocol) 1. General The Anybus CompactCom 40 PROFINET IRT supports the Secure HICP protocol used by the Anybus IPconfig utility for changing settings, e.g. IP address, Subnet mask, and enable/disable DHCP. The protocol offers secure authentication. Anybus IPconfig can be downloaded free of charge from the HMS website, www.anybus.com.
  • Page 153 ® ™ Technical Specification Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Appendix E. Technical Specification 1. Front View 1.1. Front View (PROFINET IRT, Ethernet Connectors) Item Network Status LED Module Status LED Link/Activity LED (port 1) Link/Activity LED (port 2) 1.2.
  • Page 154 In order to ensure proper EMC behavior, the module must be properly connected to functional earth via the FE pad/FE mechanism described in the Anybus CompactCom 40 Hardware Design Guide. Proper EMC behavior is not guaranteed unless these FE requirements are fulfilled.
  • Page 155 Anybus CompactCom 40 Hardware Design Guide. 3.2. Power Consumption The Anybus CompactCom 40 PROFINET IRT is designed to fulfil the requirements of a Class B module. The current hardware design consumes up to 390 mA. The Anybus CompactCom 40 PROFINET IRT FO is designed to fulfil the requirements of a Class C module. The current hardware design consumes up to 740 mA.
  • Page 156 LEDs. The front of the Anybus CompactCom 40 PROFINET IRT does not carry enough LEDs to show both the link and the activity indications that are demanded in the AIDA LED mode, but the signals are available on the host application connector.
  • Page 157 ® ™ Anybus CompactCom AIDA LED Mode Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 2.2. Bus Failure LED LED State Description Comments No problem Fatal event Major internal error (this indication is combined with a red system failure LED) Station Name error Station Name not set IP address error...
  • Page 158 No Activity Orange, flashing Activity There is no LED on the front of the Anybus CompactCom 40 PROFINET IRT showing this indication, but the signal is available in the host application connector according to this table: AIDA indication Signal Name, Host Application Connector...
  • Page 159 Appendix G. Conformance Test Guide 1. General When using the default settings of all parameters, the Anybus CompactCom 40 PROFINET IRT is precertified for network compliance. This precertification is done to ensure that your product can be certified. Changes in the parameters in the example GSD file, supplied by HMS Industrial Networks, will require a certification.
  • Page 160 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Reidentifying Your Product Ethernet 2. Reidentifying Your Product After successful setting of the Setup Complete attribute in the Anybus Object (01h), the Anybus module asks for identification data from the host PROFINET IO Object (F6h). Therefore, the attributes listed below shall be implemented and proper values returned.
  • Page 161 3. The network is informed that the I/O data of all submodules is substituted with zeros (clear). No process data is updated in the host interface. 4. A shift register application must use the PA signal to clear outputs when the Anybus CompactCom 40 PROFINET IRT is not in the state PROCESS_ACTIVE.
  • Page 162 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Certification in Generic Anybus Mode Ethernet 7. Certification in Generic Anybus Mode In Generic Anybus Mode (when the command API_add in the Network PROFINET IO Object (0Eh) is not used) there is normally nothing that needs to be considered apart from what is mentioned earlier in this appendix. The example HMS GSD file has to be modified with respect to the process mapping and identity of the product and this requires a certification of the product.
  • Page 163 ® ™ Certification in Advanced Mode Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 8. Certification in Advanced Mode In advanced mode (Network PROFINET IO Object (0Eh) is used), the most important thing is to use a Device Access Point (DAP) that conform to PROFINET IO Specification v2.0 or later (DAP2). From specification version 2.0 it is possible to describe the physical Ethernet interface and its ports (PDEV, or Physical Device) with a special mechanism.
  • Page 164 9. Changes in GSD File for Conformance Class B The example GSD file, supplied by HMS Industrial Networks, is adapted for testing an Anybus CompactCom 40 PROFINET IRT for conformance class C. If the implementation does not need the isochronous features of the device, the GSD file can be modified to mirror this.
  • Page 165 ® ™ Backward Compatibility Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Appendix H. Backward Compatibility The Anybus CompactCom M40 series of industrial network modules have significantly better performance and include more functionality than the modules in the Anybus CompactCom 30 series. The 40 series is backward compatible with the 30 series in that an application developed for the 30 series should be possible to use with the 40 series, without any major changes.
  • Page 166 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Hardware Compatibility Ethernet 2. Hardware Compatibility Anybus CompactCom is available in three hardware formats; Module, Chip, and Brick. 2.1. Module The modules in the 30-series and the 40-series share physical characteristics, like dimensions, outline, connectors, LED indicators, mounting parts etc.
  • Page 167 ® ™ Hardware Compatibility Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 2.3. Brick The Anybus CompactCom B40-1 does not share dimensions with the Anybus CompactCom B30. The B40-1 is thus not suitable for migration. However HMS Industrial Networks has developed a separate brick version in the 40-series, that can be used for migration.
  • Page 168 Active Anybus CompactCom 30 HIGH Active Anybus CompactCom 40 MI[0..1] shall only be sampled by the application during the time period from power up to the end of SETUP state. The pins are low at power up and before reset release.
  • Page 169 RMII Compatibility If the RMII mode is being used on an Anybus CompactCom 40 module and it is desired to remain compatible with the 30 series, it is important to disable this connection when switching to an Anybus CompactCom 30 module due to pin conflicts.
  • Page 170 Memory areas not supported by the specific network cannot be used. Make sure you do not access these areas, e.g. for doing read/write memory tests. Related Information: Anybus CompactCom 40 Software Design Guide (HMSI-216-125), Section “Memory Map”. 3.2. Faster Ping-Pong Protocol The ping-pong protocol (the protocol used in the 30-series) is faster in the 40-series.
  • Page 171 The functionality is always enabled. All released Anybus CompactCom 30 example drivers from HMS Industrial Networks comply with this difference. Related Information: Anybus CompactCom 40 Software Design Guide (HMSI-216-125), section “Status Register”. 3.7. Control Register CTRL_R-bit 30-series The application may change this bit at any time.
  • Page 172 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Specific — PROFINET Ethernet 4.1. Network Object (03h) Attribute Default Anybus CompactCom Comment Product #1, Network 0084h 30-series, PROFINET IO 1- The 30-series module is a PROFINET RT module without IRT capabilities. The Type Port 40-series module has PROFINET IRT capabilities.
  • Page 173 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Attribute 30-series 40-series Change/Action/Comment #7, Record Data See Comment I&M Record data transparent mode (bit 1) is replaced with the IM_Options command in Mode the Network PROFINET IO object (0Eh). If this bit is 0 in the current implementation, no action is needed.
  • Page 174 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent Network Specific — PROFINET Ethernet 4.5. Network Configuration Object (04h) The instances in the Network Configuration Object have been rearranged for the Ethernet based modules for consistency. Network specific instances are moved to instance number 20 and onwards. This is done to increase the number of instances in the section that are not network specific.
  • Page 175 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet 4.8. LED Indications Changes has been made regarding the specification of the LED indications. See tables below for differences. Figure H.6. Network Status LED (LED1[A..B]) LED State 30-series 40-series Comments...
  • Page 176 Anybus CompactCom 40 provides a window for "seamless" adaptation of Real Identification (RI). In ADI based RI mode through remap, and in advanced mode by blocking in the connect request handling. It is not ok to adapt RI by rebooting.
  • Page 177 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet For detailed information about how a configuration mismatch is handled in the 40-series, see Anybus CompactCom 40 PROFINET IRT Network Guide, HMSI-27-226, Section “Configuration Mismatch”. 4.12. Media Redundancy Protocol (MRP) MRP is supported in the 40-series and cannot be disabled by the host application.
  • Page 178 Modifications for Conformance Class B (if you want to disable support for IRT) The example GSD file, supplied by HMS Industrial Networks, is prepared for testing an Anybus CompactCom 40 PROFINET IRT for conformance class C, which includes PROFINET isochronous communication mode (IRT). If the implementation does not need the isochronous features of the device, the GSD file can be modified to reflect this.
  • Page 179 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet Keywords Keyword Comments GSDML-DeviceProfile version 2.31 for 30-series, 2.42 for 40-series DeviceIdentity->DeviceID Must be changed to reflect the Device ID you have configured in the PROFINET IO object (F6h), Attribute 1 DeviceAccessPointItem->CheckDeviceID_Allowed False for 30-series, true for 40-series...
  • Page 180 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent License Information Ethernet Appendix I. License Information Print formatting routines Copyright (C) 2002 Michael Ringgaard. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1.
  • Page 181 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF...
  • Page 182 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent License Information Ethernet INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
  • Page 183 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Author: David van Moolenbroek <david@minix3.org>...
  • Page 184 ® ™ Anybus CompactCom 40 - PROFINET IRT Transparent License Information Ethernet IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
  • Page 185 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT Transparent Ethernet to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.