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
Hide thumbs Also See for Anybus CompactCom 40:
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
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

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 NETWORK GUIDE SCM-1202-023 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 3. Basic Operation ........................5 3.1.
  • Page 4 ® ™ Anybus CompactCom 40 - PROFINET IRT 4.11. PROFIenergy Profile ....................... 26 4.11.1. Implementation ..................... 26 4.12. PROFIsafe ........................27 4.13. Factory Reset from Network .................... 28 5. Modular Device ........................29 5.1. General ......................... 29 5.2. Modular Device RI ......................29 5.3.
  • Page 5 ® ™ Anybus CompactCom 40 - PROFINET IRT 9.4.2. ABCCMessage() ....................... 60 9.5. SSI Output Configuration ....................64 10. JSON ........................... 65 10.1. General Information ....................... 65 10.1.1. Encoding ......................65 10.1.2. Access ........................65 10.1.3. Error Response ...................... 65 10.2.
  • Page 6 ® ™ Anybus CompactCom 40 - PROFINET IRT 13.5.3. Supported Commands .................... 96 13.5.4. Object Attributes (Instance #0) ................. 96 13.5.5. Instance Attributes (Instance #3, IP Address) ............... 97 13.5.6. Instance Attributes (Instance #4, Subnet Mask) ............97 13.5.7. Instance Attributes (Instance #5, Gateway Address) ............98 13.5.8.
  • Page 7 ® ™ Anybus CompactCom 40 - PROFINET IRT 13.9.1. Category ......................127 13.9.2. Object Description ....................127 13.9.3. Supported Commands ..................127 13.9.4. Object Attributes (Instance #0) ................127 13.9.5. Instance Attributes (Instances #1 - #3) ..............128 13.9.6. Interface Counters ....................128 13.9.7.
  • Page 8 ® ™ Anybus CompactCom 40 - PROFINET IRT 14.4.1. Category ......................171 14.4.2. Object Description ....................171 14.4.3. Supported Commands ..................171 14.4.4. Object Attributes (Instance #0) ................171 14.4.5. Instance Attributes (Instance #1) ................172 14.5. Sync Object (EEh) ......................173 14.5.1.
  • Page 9 ® ™ Anybus CompactCom 40 - PROFINET IRT 2. Flowchart — I&M Record Data Handling ................211 3. Flowchart —Establishment of Real Identification (RI) .............. 212 4. Flowcharts — Handling of Configuration Mismatch ..............213 4.1. Default Configuration Mismatch .................. 213 4.2.
  • Page 10 ® ™ Anybus CompactCom 40 - PROFINET IRT 2.3. Brick ........................231 2.4. Host Application Interface ..................232 3. General Software ......................234 3.1. Extended Memory Areas ................... 234 3.2. Faster Ping-Pong Protocol ..................234 3.3. Requests from Anybus CompactCom to Host Application During Startup ......234 3.4.
  • Page 11 For additional related documentation and file downloads, please visit the support website at www.anybus.com/support. 1.2. Related Documents Document Author Document ID Anybus CompactCom 40 Software Design Guide HMSI-216–125 Anybus CompactCom M40 Hardware Design Guide HMSI-216–126 Anybus CompactCom B40 Design Guide HMSI-27-230...
  • Page 12 ® ™ Anybus CompactCom 40 - PROFINET IRT Document History 1.3. Document History Version Date Description 2016-11-23 Modular Device Minor Corrections Document number changed and version numbering restarted. 2017-01-18 M12 connectors added Minor corrections 2017-03-15 PROFIenergy profile added Asset management and I&M5 added 2017-04-10 Updated to PROFIenergy 2 Minor corrections...
  • Page 13 ® ™ Terminology Anybus CompactCom 40 - PROFINET IRT 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 14 2. About the Anybus CompactCom 40 PROFINET IRT 2.1. General The Anybus CompactCom 40 PROFINET IRT communication module provides instant PROFINET Real Time connectivity via the patented Anybus CompactCom host interface. Any device that supports this standard can take advantage of the features provided by the module, allowing seamless network integration regardless of network type.
  • Page 15 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 16 – 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 17 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 18 Network Identity 3.2. Network Identity By default, the module identifies itself as a generic Anybus implementation as follows: Device ID 0010h (Anybus CompactCom 40 PROFINET) Vendor ID 010Ch (HMS Industrial Networks) Station Type The Station Type will be assigned a value according to this priority: If the PROFINET IO Object (F6h) is implemented, the value equals that of attribute #3 in instance #1.
  • Page 19 ® ™ Network Data Exchange Anybus CompactCom 40 - PROFINET IRT 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 20 ® ™ Anybus CompactCom 40 - PROFINET IRT Web Interface 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 21 3.7. File System 3.7.1. Overview The Anybus CompactCom 40 PROFINET IRT has a built-in file system, that can be accessed from the application and from the network. Three directories are predefined: The virtual file system that e.g. holds the web pages of the module.
  • Page 22 ® ™ Anybus CompactCom 40 - PROFINET IRT File System 3.7.2. General Information The built-in file system hosts 28 Mb of nonvolatile storage, which can be accessed by the HTTP and FTP servers, the e-mail client, and the host application (through the Anybus File System Interface Object (0Ah). Maximum number of directories and files that can be stored in the root directory is 511, if only short filenames are used (8 bytes name + 3 bytes extension).
  • Page 23 ® ™ PROFINET Implementation Details Anybus CompactCom 40 - PROFINET IRT 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 24 ® ™ Anybus CompactCom 40 - PROFINET IRT Application Relationships (AR) 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 25 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 26 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 27 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 28 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 29 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 30 ® ™ Anybus CompactCom 40 - PROFINET IRT Diagnostics 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 31 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 183)).
  • Page 32 Hardware version of the Anybus CompactCom Software revision 4 bytes Product version of the Anybus CompactCom See also.. • PROFINET IO Object (F6h) (page 183) • Anybus CompactCom 40 Software Design Guide, Application Object (FFh) Page 22 of 249 SCM-1202-023 Version 2.6...
  • Page 33 ® ™ Asset Management Anybus CompactCom 40 - PROFINET IRT 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 34 ® ™ Anybus CompactCom 40 - PROFINET IRT Fast Start Up 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 35 40 - PROFINET IRT 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 36 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 37 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 38 ® ™ Anybus CompactCom 40 - PROFINET IRT Factory Reset from Network 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 39 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 40 ® ™ Anybus CompactCom 40 - PROFINET IRT Safety Module 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 41 ® ™ Modular Device Example Anybus CompactCom 40 - PROFINET IRT 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 – Port 1 Subslot 0x8001 –...
  • Page 42 ® ™ Anybus CompactCom 40 - PROFINET IRT Recommendations 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 43 ® ™ FTP Server Anybus CompactCom 40 - PROFINET IRT 6. FTP Server 6.1. General Information The built-in FTP-server makes it easy to manage the file system using a standard FTP client. It can be disabled using attribute #6 in the Ethernet Host Object (F9h). By default, the following port numbers are used for FTP communication: •...
  • Page 44 ® ™ Anybus CompactCom 40 - PROFINET IRT User Accounts 6.2. User Accounts User accounts are stored in the configuration file \ftp.cfg. This file holds the usernames, passwords, and home directory for all users. Users are not able to access files outside of their home directory. File Format: User1:Password1:Homedirectory1 User2:Password2:Homedirectory2...
  • Page 45 ® ™ Session Example Anybus CompactCom 40 - PROFINET IRT 6.3. Session Example The Windows Explorer features a built-in FTP client which can easily be used to access the file system as follows: 1. Open the Windows Explorer. 2. In the address field, type FTP://<user>:<password>@<address> •...
  • Page 46 ® ™ Anybus CompactCom 40 - PROFINET IRT Web Server 7. Web Server 7.1. General Information The built-in web server provides a flexible environment for end-user interaction and configuration purposes. JSON, SSI and client-side scripting allow access to objects and file system data, enabling the creation of advanced graphical user interfaces.
  • Page 47 ® ™ Default Web Pages Anybus CompactCom 40 - PROFINET IRT 7.2.1. Network Configuration The network configuration page provides interfaces for changing TCP/IP and SMTP settings in the Network Configuration Object. Figure 7. The module needs a reset for the changes to take effect. Available IP Configuration Settings Name Description...
  • Page 48 ® ™ Anybus CompactCom 40 - PROFINET IRT Default Web Pages Safety Module Settings Name Description F-address The F-address used for the Safety Module as PROFIsafe address 7.2.2. Ethernet Statistics Page The Ethernet statistics web page contains the following information: Current IP Configuration Description DHCP:...
  • Page 49 Frames received that exceed the maximum permitted frame size. Frame Size Too Short Frames received that are shorter than lowest permitted frame size. Fiber Optical Statistics (only available for the Anybus CompactCom 40 Description PROFINET IRT Fiber Optic) Port 1 Temperature (C): Current temperature of port 1 transceiver, in degrees Celsius.
  • Page 50 ® ™ Anybus CompactCom 40 - PROFINET IRT Server Configuration 7.3. Server Configuration 7.3.1. General Information Basic web server configuration settings are stored in the system file \http.cfg. This file holds the web server name, root directory for the web interface, content types, and a list of file types which shall be scanned for SSI. File Format: [ServerName] WebServerName...
  • Page 51 ® ™ Server Configuration Anybus CompactCom 40 - PROFINET IRT 7.3.3. Default Content Types By default, the following content types are recognized by their file extension: File Extension Reported Content Type htm, html, shtm text/html image/gif jpeg, jpg, jpe image/jpeg image/x-png application/x-javascript bat, txt, c, h, cpp, hpp...
  • Page 52 ® ™ Anybus CompactCom 40 - PROFINET IRT Server Configuration 7.3.4. Authorization Directories can be protected from web access by placing a file called ‘web_accs.cfg’ in the directory to protect. This file shall contain a list of users that are allowed to access the directory and its subdirectories. Optionally, a login message can be specified by including the key [AuthName].
  • Page 53 ® ™ E-mail Client Anybus CompactCom 40 - PROFINET IRT 8. E-mail Client 8.1. General Information The built-in e-mail client allows the application to send e-mail messages through an SMTP-server. Messages can either be specified directly in the SMTP Client Object (04h), or retrieved from the file system. The latter may contain SSI, however note that for technical reasons, certain commands cannot be used (specified separately for each SSI command).
  • Page 54 ® ™ Anybus CompactCom 40 - PROFINET IRT Server Side Include (SSI) 9. Server Side Include (SSI) 9.1. General Information Server Side Include functionality, or SSI, allows data from files and objects to be represented on web pages and in e-mail messages.
  • Page 55 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT 9.3. Command Functions 9.3.1. General Information Command functions executes commands and includes the result. General Syntax <?--#exec cmd_argument='command'--> command: Command function, see below NOTE “command” is limited to a maximum of 500 characters. Command Functions Command Valid for E-mail Messages...
  • Page 56 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.2. GetConfigItem() This command returns specific information from a file in the file system. File Format The source file must have the following format: [key1] value1 [key2] value2 [keyN] valueN Syntax: <?--exec cmd_argument='GetConfigItem("filename", "key"[,"separator"])'-->...
  • Page 57 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT 9.3.3. SetConfigItem() This function stores an HTML-form as a file in the file system. NOTE This function cannot be used in e-mail messages. File Format Each form object is stored as a [tag], followed by the actual value. [form object name 1] form object value 1 [form object name 2]...
  • Page 58 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions Example The following example demonstrates how to use this function. The resulting page sends a form to itself, which is then evaluated by the SetConfigItem command. <HTML> <HEAD><TITLE>SetConfigItem Test</TITLE></HEAD> <BODY> <?--#exec cmd_argument='SetConfigItem("\food.txt")'-->...
  • Page 59 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT 9.3.4. SsiOutput() This command temporarily modifies the SSI output of the following command function. Syntax: <?--#exec cmd_argument='SsiOutput("success", "failure")'--> success: String to use in case of success failure: String to use in case of failure Default Output (this command produces no output on its own) Example...
  • Page 60 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.6. ChangeLanguage() This command changes the language setting based on an HTML form object. NOTE This function cannot be used in e-mail messages. Syntax: <?--#exec cmd_argument='ChangeLanguage( "source" )'--> source: Name of form object which contains the new language setting. The passed value must be a single digit as follows: Form value Language...
  • Page 61 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT Example The following example demonstrates how to use this function. The resulting page sends a form to itself, which is then evaluated by the ChangeLanguage() command. <HTML> <HEAD><TITLE>ChangeLanguage Test</TITLE></HEAD> <BODY> <?--#exec cmd_argument='ChangeLanguage("lang")'-->...
  • Page 62 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.7. IncludeFile() This command includes the content of a file. Note that the content is not scanned for SSI. Syntax: <?--#exec cmd_argument='IncludeFile("filename" [, separator])'--> filename: Source file separator: Optional; specifies line separation characters (e.g. “<br>”). Default Output Scenario Default Output...
  • Page 63 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT When viewed in a browser, the resulting page should look somewhat as follows: Figure 8. See also... • Include File (page 44) SCM-1202-023 Version 2.6 Page 53 of 249...
  • Page 64 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.8. SaveDataToFile() This command stores data from an HTML form as a file in the file system. Content from the different form objects are separated by a blank line (2*CRLF). NOTE This function cannot be used in e-mail messages.
  • Page 65 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT Example The following example demonstrates how to use this function. The resulting page sends a form to itself, which is then evaluated by the SaveDataToFile command. <HTML> <HEAD><TITLE>SaveDataToFile Test</TITLE></HEAD> <BODY> <?--#exec cmd_argument='SaveDataToFile("\stuff.txt", “Meat”, Overwrite)'-->...
  • Page 66 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.9. printf() This function returns a formatted string which may contain data from the Anybus CompactCom module and/or application. The formatting syntax used is similar to that of the standard C-function printf(). The function accepts a template string containing zero or more formatting tags, followed by a number of arguments.
  • Page 67 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT • Type (Required) The Type-character is required and determines the basic representation as follows: Type Character Representation Example Single character d, i Signed decimal integer e, E Floating-point number in exponential notation 5.6538e2 Floating-point number in normal, fixed-point notation 565.38...
  • Page 68 ® ™ Anybus CompactCom 40 - PROFINET IRT Command Functions 9.3.10. scanf() This function is very similar to the printf() function described earlier, except that it is used for input rather than output. The function reads a string passed from an HTML form object, parses the string as specified by a template string, and sends the resulting data to the specified argument.
  • Page 69 ® ™ Command Functions Anybus CompactCom 40 - PROFINET IRT • Type (Required) The Type-character is required and determines the basic representation as follows: Type Input Argument Data Type Single character CHAR Accepts a signed decimal integer SINT8 SINT16 SINT32 Accepts a signed or unsigned decimal integer.
  • Page 70 ® ™ Anybus CompactCom 40 - PROFINET IRT Argument Functions 9.4. Argument Functions 9.4.1. General Information Argument functions are supplied as parameters to certain command functions. General Syntax: (Syntax depends on context) Argument Functions: Function Description ABCCMessage() 9.4.2. ABCCMessage() This function issues an object request towards an object in the module or in the host application. Syntax ABCCMessage(object, instance, command, ce0, ce1, msgdata, c_type, r_type)
  • Page 71 ® ™ Argument Functions Anybus CompactCom 40 - PROFINET IRT • Command Data Types (c_type) For types which support arrays, the number of elements can be specified using the suffix [n], where n specifies the number of elements. Each data element must be separated by space. Type Supports Arrays Data format (as supplied in msgdata)
  • Page 72 ® ™ Anybus CompactCom 40 - PROFINET IRT Argument Functions Example (Get_Attribute): This example shows how to retrieve the IP address using printf() and ABCCMessage(). <?--#exec cmd_argument='printf( "%u.%u.%u.%u", ABCCMessage(4,3,1,5,0,0,NONE,UINT8[4] ) )'--> Variable Value Comments object Network Configuration Object (04h) instance Instance #3 (IP address) command Get_attribute...
  • Page 73 ® ™ Argument Functions Anybus CompactCom 40 - PROFINET IRT Errors In case an object request results in an error, the error code in the response will be evaluated and translated to readable form as follows: Error Code Output “Unknown error” “Unknown error”...
  • Page 74 ® ™ Anybus CompactCom 40 - PROFINET IRT SSI Output Configuration 9.5. SSI Output Configuration Optionally, the SSI output can be permanently changed by adding the file \output.cfg. File format: Each error code corresponds to a dedicated output string, labelled from 1 to 16. [ABCCMessage_X] Errors (page 63) 0:"Success string"...
  • Page 75 If the module fails to parse or process a request, the response will contain an error object with an Anybus error code: "error" The Anybus error codes are listed in the Anybus CompactCom 40 Software Design Guide. SCM-1202-023 Version 2.6 Page 65 of 249...
  • Page 76 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects 10.2. JSON Objects 10.2.1. ADI info.json GET adi/info.json[?callback=<function>] This object holds information about the ADI JSON interface. This data is static during runtime. Name Data Type Note dataformat Number 0 = Little endian 1 = Big endian (Affects value, min and max representations) numadis Number...
  • Page 77 <instance>. The returned information provided is a transparent representation of the attributes available in the host Application Data object (FEh). See the Anybus CompactCom 40 Software Design Guide for more information about the content of each attribute. The ADI metadata is static during runtime.
  • Page 78 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects Response data: Name Data Type Description instance Number name String Is NULL if no name is present. numelements Number datatype Number String Hex formatted string, see Hex Format Explained (page 81) for more information.
  • Page 79 Structures. The information provided is a transparent representation of the attributes available in the host Application Data object (FEh). See the Anybus CompactCom 40 Software Design Guide for more information about the content of each attribute.
  • Page 80 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects JSON response example (using offset): "instance": "numelements": 1, "datatype": "descriptor": "name": "Temperature threshold", "max": "FF", "min": "00", "default": "00", "numsubelements": null, "elementname": null JSON response example (instance): "instance": "numelements": 1, "datatype": "descriptor": "name":...
  • Page 81 ® ™ JSON Objects Anybus CompactCom 40 - PROFINET IRT Request data: Name Data Type Description inst Number Instance number of the ADI to get enum string for. value Number Optional. If given, only the enumstring for the requested <value> is returned. callback String Optional.
  • Page 82 JSON Objects Response data: Name Data Type Note result Number 0 = success The Anybus CompactCom error codes are used. Please see the Anybus CompactCom 40 Software Design Guide. "result" : 0 10.2.2. Module info.json GET module/info.json Response data: Name...
  • Page 83 ® ™ JSON Objects Anybus CompactCom 40 - PROFINET IRT 10.2.3. Network ethstatus.json GET network/ethstatus.json Name Data Type Description String 6 byte hex comm1 Object See object definition in the table below comm2 Object See object definition in the table below Comm Object Definition: Name Data Type...
  • Page 84 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects Name Data Type Note dhcp Number addr String subnet String gateway String dns1 String dns2 String hostname String domainname String "dhcp": "addr": "192.168.0.55", "subnet": "255.255.255.0", "gateway": "192.168.0.1", "dns1": "10.10.55.1", "dns2": "10.10.55.2", "hostname": "abcc123",...
  • Page 85 [00, 30, 11, FF, 02, 01], "comm1": "comm2": { error: 14 }, The Anybus CompactCom error codes are used. Please see the Anybus CompactCom 40 Software Design Guide. ifcounters.json GET network/ifcounters.json?port=<port> • Valid values for the argument <port> are 0, 1, and 2.
  • Page 86 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects Name Data Type Description align Number Frames received that are not an integral number of octets in length Number Frames received that do not pass the FCS check singlecoll Number Successfully transmitted frames which experienced exactly one collision multicoll Number...
  • Page 87 ® ™ JSON Objects Anybus CompactCom 40 - PROFINET IRT "eipstats" { "name": "Established Class1 Connections", "value": 0 }, { "name": "Established Class3 Connections", "value": 1 }, { "name": "Connection Open Request", "value": 0 }, { "name": "Connection Open Format Rejects", "value": 0 }, { "name": "Connection Open Resource Rejects", "value": 0 }, { "name": "Connection Open Other Rejects", "value": 0 }, { "name": "Connection Close Requests", "value": 0 },...
  • Page 88 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects "bacnetaplserverstats" { "name": "Active transactions", "value": 0 }, { "name": "Max Active transactions", "value": 1 }, { "name": "Tx segments sent", "value": 0 }, { "name": "Tx segment ACKs received", "value": 0 }, { "name": "Tx segment NAKs received", "value": 0 }, { "name": "Rx segments received", "value": 0 }, { "name": "Rx segment ACKs sent", "value": 0 },...
  • Page 89 ® ™ JSON Objects Anybus CompactCom 40 - PROFINET IRT "bacnetalarmstats" { "name": "COV Active subscriptions", "value": 0 }, { "name": "COV Max active subscriptions", "value": 1 }, { "name": "COV Lifetime subscriptions", "value": 0 }, { "name": "COV Confirmed resumes", "value": 0 }, { "name": "COV Unconfirmed resumes", "value": 0 }, { "name": "COV Confirmed notifications sent", "value": 0 }, { "name": "COV Unconfirmed notifications sent", "value": 0 },...
  • Page 90 ® ™ Anybus CompactCom 40 - PROFINET IRT JSON Objects "eoeifcounters" { "name": "In Octets", "value": 22967 }, { "name": "In Ucast Packets", "value": 121 }, { "name": "In NUcast Packets", "value": 31 }, { "name": "In Discards", "value": 0 }, { "name": "In Errors", "value": 0 }, { "name": "In Unknown Protos", "value": 0 }, { "name": "Out Octets", "value": 169323 },...
  • Page 91 ® ™ JSON Objects Anybus CompactCom 40 - PROFINET IRT 10.2.4. Services smtp.json GET services/smtp.json NOTE Password is not returned when retrieving the settings. Name Data Type Note server String IP address or name of mail server, e.g. “mail.hms.se” user String { "server": "192.168.0.55"}, { "user": "test"}...
  • Page 92 ® ™ Anybus CompactCom 40 - PROFINET IRT Example 10.3. Example This example shows how to create a web page that fetches Module Name and CPU load from the module and presents it on the web page. The file, containing this code, has to be stored in the built-in file system, and the result can be seen in a common browser.
  • Page 93 203). 11.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 94 ® ™ Anybus CompactCom 40 - PROFINET IRT MIB-II 11.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 95 ® ™ Media Reduncancy Protocol (MRP) Anybus CompactCom 40 - PROFINET IRT 12. Media Reduncancy Protocol (MRP) 12.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 96 ® ™ Anybus CompactCom 40 - PROFINET IRT Anybus Module Objects 13. Anybus Module Objects 13.1. General Information Standard Objects: • Anybus Object (01h) (page 87) • Diagnostic Object (02h) (page 88) • Network Object (03h) (page 91) • Network Configuration Object (04h) (page 96) Network Specific Objects: •...
  • Page 97 13.2.3. Supported Commands Object: Get_Attribute Reset Instance: Get_Attribute Set_Attribute Get_Enum_String 13.2.4. Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) 13.2.5. Instance Attributes (Instance #1) Basic Name Access Type Value Module type UINT16 0403h (Standard Anybus CompactCom 40) 2...
  • Page 98 13.3. Diagnostic Object (02h) 13.3.1. Category Extended 13.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. 13.3.3. Supported Commands Object: Get_Attribute Create...
  • Page 99 ® ™ Diagnostic Object (02h) Anybus CompactCom 40 - PROFINET IRT 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 100 ® ™ Anybus CompactCom 40 - PROFINET IRT Diagnostic Object (02h) 13.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 101: Table Of Contents

    Anybus CompactCom 40 Software Design Guide. 13.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 13.4.4. Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) SCM-1202-023 Version 2.6 Page 91 of 249...
  • Page 102 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 103 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 104 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Object (03h) • 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) MsgData[4]...
  • Page 105 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 106: 13.5.3. Supported Commands

    Name Access Data Type Value Description Number of instances UINT16 Supported number of instances Highest instance number UINT16 Highest instance number (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) Page 96 of 249 SCM-1202-023 Version 2.6...
  • Page 107 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT 13.5.5. Instance Attributes (Instance #3, IP Address) Value is used after module reset. Name Access Data Type Description Name Array of CHAR “IP address” (Multilingual, see page Multilingual Strings (page 103)) Data type UINT8...
  • Page 108 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Configuration Object (04h) 13.5.7. Instance Attributes (Instance #5, Gateway Address) Value is used after module reset. Name Access Data Type Description Name Array of CHAR “Gateway” (Multilingual, see page Multilingual Strings (page 103)) Data type UINT8...
  • Page 109 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT 13.5.9. Instance Attributes (Instance #9, DNS1) This instance holds the address to the primary DNS server. Changes are valid after reset. Name Access Data Type Description Name Array of CHAR “DNS1”...
  • Page 110 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Configuration Object (04h) 13.5.12. Instance Attributes (Instance #12, Domain name) This instance holds the domain name. Changes are valid after reset. Name Access Data Type Description Name Array of CHAR “Host name” (Multilingual, see page Multilingual Strings (page 103))
  • Page 111 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT 13.5.15. Instance Attributes (Instance #15, SMTP Password) This instance holds the password for the SMTP account. Changes are valid after reset. Name Access Data Type Description Name Array of CHAR “SMTP Pswd”...
  • Page 112 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Configuration Object (04h) 13.5.17. 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 113 ® ™ Network Configuration Object (04h) Anybus CompactCom 40 - PROFINET IRT 13.5.18. Instance Attributes (Instance #21, F-Address) This instance holds the F-Address, which is the PROFIsafe address for the safety module. This instance has no effect unless the attribute #1 (Safety enabled) is set to TRUE in the Functional Safety host object (instance #1). If the attribute is set to FALSE in the Functional Safety host object the application is advised to hide this instance to the end user.
  • Page 114 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Configuration Object (04h) 13.5.20. Command Details: Reset Category Details Command Code: Valid For: Object Instance Description A reset command to this object will result in that all instances are set to their default values. It is optional to implement support for this command.
  • Page 115 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6. Socket Interface Object (07h) 13.6.1. Category Extended 13.6.2. Object Description This object provides direct access to the TCP/IP stack socket interface, enabling custom protocols to be implemented over TCP/UDP. Note that some of the commands used when accessing this object may require segmentation.
  • Page 116 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.5. Instance Attributes (Sockets #1...Max. no. of instances) Extended Name Access Data Type Description Socket Type UINT8 Value: Socket Type SOCK_STREAM, NONBLOCKING (TCP) SOCK_STREAM, BLOCKING (TCP) SOCK_DGRAM, NONBLOCKING (UDP) SOCK_DGRAM, BLOCKING (UDP) Port UINT16...
  • Page 117 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.6. Command Details: Create Category Extended Details Command Code: Valid For: Object Instance Description This command creates a socket. This command is only allowed in WAIT_PROCESS, IDLE and PROCESS_ACTIVE states. •...
  • Page 118 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.7. Command Details: Delete Category Extended Details Command Code: Valid For: Object Instance Description This command deletes a previously created socket and closes the connection (if connected). • If the socket is of TCP-type and a connection is established, the connection is terminated with the RST-flag. •...
  • Page 119 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.9. Command Details: Shutdown Category Extended Details Command Code: Valid For: Instance Description This command closes a TCP-connection using the FIN-flag. Note that the response does not indicate if the connection actually shut down, which means that this command cannot be used to poll non-blocking sockets, nor will it block for blocking sockets.
  • Page 120 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.10. Command Details: Listen Category Extended Details Command Code: Valid For: Instance Description This command puts a TCP socket in listening state. • Command Details Field Contents CmdExt[0] (reserved, set to zero) CmdExt[1] (reserved)
  • Page 121 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.11. Command Details: Accept Category Extended Details Command Code: Valid For: Instance Description This command accepts incoming connections on a listening TCP socket. A new socket instance is created for each accepted connection.
  • Page 122 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.12. Command Details: Connect Category Extended Details Command Code: Valid For: Instance Description For SOCK-DGRAM-sockets, this command specifies the peer with which the socket is to be associated (to which datagrams are sent and the only address from which datagrams are received).
  • Page 123 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.13. Command Details: Receive Category Extended Details Command Code: Valid For: Instance Description This command receives data from a connected socket. Message segmentation may be used to receive up to 1472 bytes (for more information, see Message Segmentation (page 121)).
  • Page 124 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.14. Command Details: Receive_From Category Extended Details Command Code: Valid For: Instance Description This command receives data from an unconnected SOCK_DGRAM-socket. Message segmentation may be used to receive up to 1472 bytes (For more information, see Message Segmentation (page 121)).
  • Page 125 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.15. Command Details: Send Category Extended Details Command Code: Valid For: Instance Description This command sends data on a connected socket. Message segmentation may be used to send up to 1472 bytes (For more information, see Message Segmentation (page 121)).
  • Page 126 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.16. Command Details: Send_To Category Extended Details Command Code: Valid For: Instance Description This command sends data to a specified host on an unconnected SOCK-DGRAM-socket. Message segmentation may be used to send up to 1472 bytes. (For more information, see Message Segmentation (page 121).) •...
  • Page 127 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.17. Command Details: IP_Add_Membership Category Extended Details Command Code: Valid For: Instance Description This command assigns the socket an IP multicast group membership. The module always joins the “All hosts group”...
  • Page 128 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.18. Command Details: IP_Drop_Membership Category Extended Details Command Code: Valid For: Instance Description This command removes the socket from an IP multicast group membership. • Command Details Field Contents CmdExt[0] (reserved, set to zero)
  • Page 129 ® ™ Socket Interface Object (07h) Anybus CompactCom 40 - PROFINET IRT 13.6.19. Command Details: DNS_Lookup Category Extended Details Command Code: Valid For: Object Description This command resolves the given host name and returns the IP address. • Command Details Field Contents Comments...
  • Page 130 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) 13.6.20. Socket Interface Error Codes (Object Specific) The following object-specific error codes may be returned by the module when using the socket interface object. Error Code Name Meaning ENOBUFS No internal buffers available ETIMEDOUT...
  • Page 131 The maximum message size supported by the Anybus CompactCom 40 is normally 1524 bytes. In some applications a maximum message size of 255 bytes is supported, e.g. if an Anybus CompactCom 40 is to replace an Anybus CompactCom 30 without any changes to the application. The maximum socket message size is 1472.
  • Page 132 ® ™ Anybus CompactCom 40 - PROFINET IRT Socket Interface Object (07h) Response Segmentation When a response is segmented, the command initiator requests the next segment by sending the same command multiple times. For each response, the data field is exchanged with the next data segment. Response segmentation is used for responses to the following commands (Socket Interface Object specific commands): •...
  • Page 133 ® ™ SMTP Client Object (09h) Anybus CompactCom 40 - PROFINET IRT 13.7. SMTP Client Object (09h) 13.7.1. Category Extended 13.7.2. Object Description This object groups functions related to the SMTP client. 13.7.3. Supported Commands Object: Get_Attribute Create Delete Send e-mail from file (see below) Instance: Get_Attribute Set_Attribute...
  • Page 134 ® ™ Anybus CompactCom 40 - PROFINET IRT SMTP Client Object (09h) 13.7.6. Command Details: Create Category Extended Details Command Code: Valid For: Object Description This command creates an e-mail instance. • Command Details Field Contents Comments CmdExt[0] (reserved) (set to zero) CmdExt[1] •...
  • Page 135 ® ™ SMTP Client Object (09h) Anybus CompactCom 40 - PROFINET IRT 13.7.8. Command Details: Send E-mail From File Category Extended Details Command Code: Valid For: Object Description This command sends an e-mail based on a file in the file system. The file must be a plain ASCII-file in the following format: [To] recipient...
  • Page 136 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. Page 126 of 249...
  • Page 137 ® ™ Network Ethernet Object (0Ch) Anybus CompactCom 40 - PROFINET IRT 13.9. Network Ethernet Object (0Ch) 13.9.1. Category Extended 13.9.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 138 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Ethernet Object (0Ch) 13.9.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 203)) Port 1 MAC Address Array of UINT8...
  • Page 139 ® ™ Network Ethernet Object (0Ch) Anybus CompactCom 40 - PROFINET IRT 13.9.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; Frames received that do not pass the FCS check SingleCollisions;...

  • Page 140: Map_Adi_Write_Area

    13.10.1. Category Extended 13.10.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 16). The modules in the GSDML file must then be described in the same way.

  • Page 141: Object Attributes (Instance #0)

    ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT 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 142 ® ™ Anybus CompactCom 40 - PROFINET IRT Network PROFINET IO Object (0Eh) 13.10.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 143 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT 13.10.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 144 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 145 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT • 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] (reserved, set to zero)
  • Page 146 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 147 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT • 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] (reserved, set to zero)
  • Page 148 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 149 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 150 ® ™ Anybus CompactCom 40 - PROFINET IRT Network PROFINET IO Object (0Eh) 13.10.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 151 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT 13.10.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 152 > 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 153 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT • 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 154 ® ™ Anybus CompactCom 40 - PROFINET IRT Network PROFINET IO Object (0Eh) 13.10.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 155 ® ™ Network PROFINET IO Object (0Eh) Anybus CompactCom 40 - PROFINET IRT 13.10.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 156 ® ™ Anybus CompactCom 40 - PROFINET IRT Network PROFINET IO Object (0Eh) 13.10.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 API does not exist...
  • Page 157 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT 13.11. Functional Safety Module Object (11h) 13.11.1. Category Extended 13.11.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 158 ® ™ Anybus CompactCom 40 - PROFINET IRT Functional Safety Module Object (11h) 13.11.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 159 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT 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 160 ® ™ Anybus CompactCom 40 - PROFINET IRT Functional Safety Module Object (11h) 13.11.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 161 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT 13.11.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 162 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 163 ® ™ Functional Safety Module Object (11h) Anybus CompactCom 40 - PROFINET IRT 13.11.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 164 Energy Measurement Object (E4h) (page 155) • Functional Safety Object (E8h) (page 171) • “ Application File System Object (EAh)” (see Anybus CompactCom 40 Software Design Guide) • “ Modular Device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide) •...
  • Page 165 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 14.2. Energy Measurement Object (E4h) 14.2.1. Category Extended 14.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. Each instance, logical device, represents a group of measurement values for one separate measurement device.
  • Page 166 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) 14.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 167 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 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 168 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) 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 8: Reserved...
  • Page 169 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 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 170 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) 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 UINT32...
  • Page 171 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 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 8: Reserved...
  • Page 172 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) 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 11: Reserved...
  • Page 173 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 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 = Consumed –...
  • Page 174 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) 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 RMS value...
  • Page 175 ® ™ Energy Measurement Object (E4h) Anybus CompactCom 40 - PROFINET IRT 14.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 176 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Measurement Object (E4h) • 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 177 ® ™ Asset Management Object (E5h) Anybus CompactCom 40 - PROFINET IRT 14.3. Asset Management Object (E5h) 14.3.1. Category Extended 14.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 178 ® ™ Anybus CompactCom 40 - PROFINET IRT Asset Management Object (E5h) 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; attributes AM Hardware Revision and IM Hardware Revision are irrelevant IM Unique Array of UINT8...
  • Page 179 ® ™ Asset Management Object (E5h) Anybus CompactCom 40 - PROFINET IRT 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 180 ® ™ Anybus CompactCom 40 - PROFINET IRT Asset Management Object (E5h) 14.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 Page 170 of 249 SCM-1202-023 Version 2.6...
  • Page 181 ® ™ Functional Safety Object (E8h) Anybus CompactCom 40 - PROFINET IRT 14.4. Functional Safety Object (E8h) 14.4.1. Category Extended 14.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 182 ® ™ Anybus CompactCom 40 - PROFINET IRT Functional Safety Object (E8h) 14.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 183 14.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 184 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 185 ® ™ Sync Object (EEh) Anybus CompactCom 40 - PROFINET IRT 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 186 ® ™ Anybus CompactCom 40 - PROFINET IRT Sync Object (EEh) 14.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 Default value: 0 Input capture...
  • Page 187 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT 14.6. Energy Control Object (F0h) 14.6.1. Category Extended 14.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. All instance attributes shall be seen as required and must be implemented in the application.
  • Page 188 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Control Object (F0h) 14.6.3. Supported Commands Object: Get_Attribute StartPause EndPause Preview_Pause_Time (not PROFINET) Instance: Get_Attribute 14.6.4. Object Attributes (Instance #0) Name Access Data Type Value Name Array of CHAR “Energy Control” Revision UINT8 Number of instances...
  • Page 189 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT 14.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 190 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Control Object (F0h) 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 191 ® ™ Energy Control Object (F0h) Anybus CompactCom 40 - PROFINET IRT 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 192 ® ™ Anybus CompactCom 40 - PROFINET IRT Energy Control Object (F0h) 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 193 See also... • Network PROFINET IO Object (0Eh) (page 130) • Flowchart — Record Data Access (page 210) • Anybus CompactCom 40 Software Design Guide, “Error Codes” 14.7.3. Supported Commands Object: Get_Attribute (01h) Get_Record (10h, see below) Set_Record (11h, see below)
  • Page 194 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 14.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 195 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 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 196 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 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 197 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 14.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 198 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) • 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 202) MsgData[2] Error Code 2 User specific error code MsgData[3]...
  • Page 199 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 14.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 200 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) See also... • Command details for “Get_Record” • Flowchart — Record Data Access (page 210) Page 190 of 249 SCM-1202-023 Version 2.6...
  • Page 201 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 14.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 202 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) • 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 203 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 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: Subslot number 0 shall indicate pulling of module in conjunction with AlarmType(=Pull)
  • Page 204 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 14.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 205 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 206 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 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 207 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 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 208 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 14.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 209 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 14.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 210 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) • Response Details (no data) 14.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 211 ® ™ PROFINET IO Object (F6h) Anybus CompactCom 40 - PROFINET IRT 14.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 212 ® ™ Anybus CompactCom 40 - PROFINET IRT PROFINET IO Object (F6h) 14.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 • Set_IM_Record High nibble (bits 4...
  • Page 213 ® ™ Ethernet Host Object (F9h) Anybus CompactCom 40 - PROFINET IRT 14.8. Ethernet Host Object (F9h) 14.8.1. Object Description This object implements Ethernet features in the host application. 14.8.2. Supported Commands Object: Get_Attribute Instance: Get_Attribute Set_Attribute 14.8.3. Object Attributes (Instance #0) Name Access Data Type...
  • Page 214 ® ™ Anybus CompactCom 40 - PROFINET IRT Ethernet Host Object (F9h) 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 215 ® ™ Ethernet Host Object (F9h) Anybus CompactCom 40 - PROFINET IRT 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 216 ® ™ Anybus CompactCom 40 - PROFINET IRT Ethernet Host Object (F9h) 14.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 217 ® ™ Categorization of Functionality Anybus CompactCom 40 - PROFINET IRT 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. They will be enough for starting up the Anybus CompactCom and sending/receiving data with the chosen network protocol.
  • Page 218 ® ™ Anybus CompactCom 40 - PROFINET IRT Anybus Implementation Details 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 219 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 220 ® ™ Anybus CompactCom 40 - PROFINET IRT Flowcharts 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 Safety module?
  • Page 221 ® ™ Flowchart — I&M Record Data Handling Anybus CompactCom 40 - PROFINET IRT 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 Slot...
  • Page 222 ® ™ Anybus CompactCom 40 - PROFINET IRT Flowchart —Establishment of Real Identification (RI) 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 Issue 'API_Add'...
  • Page 223 ® ™ Flowcharts — Handling of Configuration Mismatch Anybus CompactCom 40 - PROFINET IRT 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. Connect with *The controller may choose to connect to mismatch*...
  • Page 224 ® ™ Anybus CompactCom 40 - PROFINET IRT Flowcharts — Handling of Configuration Mismatch 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 225 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 226 ® ™ Anybus CompactCom 40 - PROFINET IRT Technical Specification 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. Front View (Fiber Optics Connectors) Item Network Status LED Module Status LED...
  • Page 227 ® ™ Front View Anybus CompactCom 40 - PROFINET IRT 1.4. Network Status LED LED State Description Comments Offline • No power • No connection with IO Controller Green Online (RUN) • Connection with IO Controller established • IO Controller in RUN state Green, 1 flash Online (STOP) •...
  • Page 228 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 229 40 - PROFINET IRT 6. Fiber Optics Compliance (MAU type Compliance) The optical interface of the Anybus CompactCom 40 PROFINET IRT is compliant with the non IEEE802.3 MAU type POF. The supported cables are stated in the PI document PROFINET Cabling and Interconnection Technology;...
  • Page 230 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 231 ® ™ Anybus CompactCom AIDA LED Mode Anybus CompactCom 40 - PROFINET IRT 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 IP address not set...
  • Page 232 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 233 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 234 ® ™ Anybus CompactCom 40 - PROFINET IRT Reidentifying Your Product 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 235 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 236 ® ™ Anybus CompactCom 40 - PROFINET IRT Certification in Generic Anybus Mode 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 237 ® ™ Certification in Advanced Mode Anybus CompactCom 40 - PROFINET IRT 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 238 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 239 ® ™ Backward Compatibility Anybus CompactCom 40 - PROFINET IRT 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 240 ® ™ Anybus CompactCom 40 - PROFINET IRT Hardware Compatibility 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 241 ® ™ Hardware Compatibility Anybus CompactCom 40 - PROFINET IRT 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 242 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 243 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 244 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 245 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 246 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Specific — PROFINET 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 247 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT 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 248 ® ™ Anybus CompactCom 40 - PROFINET IRT Network Specific — PROFINET 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 249 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT 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 Offline...
  • Page 250 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 251 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT 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 252 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 253 ® ™ Network Specific — PROFINET Anybus CompactCom 40 - PROFINET IRT 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 254 ® ™ Anybus CompactCom 40 - PROFINET IRT License Information 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 255 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT 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 256 ® ™ Anybus CompactCom 40 - PROFINET IRT License Information 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 257 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT 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> ******************************************************************************** MD5 routines Copyright (C) 1999, 2000, 2002 Aladdin Enterprises.
  • Page 258 ® ™ Anybus CompactCom 40 - PROFINET IRT License Information 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 259 ® ™ License Information Anybus CompactCom 40 - PROFINET IRT 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.

Table of Contents