Anybus CompactCom 40 Network Manual
  1. Manuals
  2. Brands
  3. Anybus Manuals
  4. Control Unit
  5. CompactCom 40 Modbus-TCP
  6. Network manual

Anybus CompactCom 40 Network Manual

Profinet irt
Hide thumbs Also See for CompactCom 40:
Table of Contents

Advertisement

Quick Links

®
Anybus
CompactCom
40
™
PROFINET IRT
NETWORK GUIDE
SCM-1202-023 EN 1.8 ENGLISH

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Anybus CompactCom 40

Summary of Contents for Anybus CompactCom 40

  • Page 1 ® Anybus CompactCom ™ PROFINET IRT NETWORK GUIDE SCM-1202-023 EN 1.8 ENGLISH...
  • Page 2 HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de- scribed in this document. These intellectual property rights may include patents and pending patent applications in the USA and other countries. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...

  • Page 3: Table Of Contents

    About this document ......................5 Related Documents .......................5 Document History ......................5 Document Conventions ....................6 Terminology........................6 Trademark Information ....................7 About the Anybus CompactCom 40 PROFINET IRT ..........8 General.........................8 Features ........................8 Basic Operation....................... 9 General Information .......................9 Network Identity ......................12 Communication Settings....................12 Network Data Exchange ....................13...
  • Page 4 10 JSON..........................65 10.1 General Information .....................65 10.2 JSON Objects......................66 10.3 Example........................84 11 SNMP Agent........................85 11.1 General........................85 11.2 Community Strings.......................85 11.3 Management Information (MIB)..................85 11.4 MIB_II .........................85 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 5 Table of Contents 12 Media Reduncancy Protocol (MRP)................88 12.1 General........................88 12.2 GSDML Entries......................88 13 Anybus Module Objects ....................89 13.1 General Information .....................89 13.2 Anybus Object (01h) ....................90 13.3 Diagnostic Object (02h) ....................91 13.4 Network Object (03h) ....................94 13.5 Network Configuration Object (04h)................99...
  • Page 6 Fiber Optics Compliance (MAU type Compliance) ............219 AIDA LED Mode ......................220 How to Design for AIDA LED Mode ................220 Anybus CompactCom AIDA LED Mode ............... 220 G Conformance Test Guide ..................223 General........................223 Reidentifying Your Product ..................224 Factory Default Reset....................

  • Page 7: Preface

    This document is intended to provide a good understanding of the functionality offered by the Anybus CompactCom 40 PROFINET IRT. The document describes the features that are specif- ic to Anybus CompactCom 40 PROFINET IRT. For general information regarding Anybus Com- pactCom, consult the Anybus CompactCom design guides.

  • Page 8: Document Conventions

    The terms “Anybus” or “module” refers to the Anybus CompactCom module. • The terms “host” or “host application” refer to the device that hosts the Anybus. • Hexadecimal values are written in the format NNNNh or 0xNNNN, where NNNN is the hex- adecimal value.

  • Page 9: Trademark Information

    Preface 7 (258) Trademark Information Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 10: About The Anybus Compactcom 40 Profinet Irt

    General The Anybus CompactCom 40 PROFINET IRT communication module provides instant PROFI- NET 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 11: Basic Operation

    General Information 3.1.1 Software Requirements Generally, no additional network support code needs to be written to support the Anybus Com- pactCom 40 PROFINET IRT, however due to the nature of the PROFINET networking system certain things must be taken into account: •...
  • Page 12 – Sensors • Replace the ProductFamily value “Anybus CompactCom 40 PIR” with a string which de- scribes your device. In addition to the above, there are a few more places where identity related information is present in the GSD file.
  • Page 13 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 re- cord data, but that can be enabled if needed.

  • Page 14: Network Identity

    If none of these attributes are implemented, the value equals Anybus CompactCom default value (“ABCC-PIR”). It is recommended to customize the identity information so that the Anybus module appears as a vendor specific implementation rather than a generic Anybus product.

  • Page 15: Network Data Exchange

    (not associated with ADIs) >0 Application Process Instances (API), p. 18 See also... • Caveats, p. 14 • Application Process Instances (API), p. 18 • PROFINET IO Object (F6h), p. 184 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 16: Web Interface

    See also... • File System, p. 16 • FTP Server, p. 36 • Web Server, p. 38 • Server Side Include (SSI), p. 45 • JSON, p. 65 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 17: E-Mail Client

    • File System, p. 16 • E-mail Client, p. 44 • Server Side Include (SSI), p. 45 • JSON, p. 65 • SMTP Client Object (09h), p. 125 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 18: 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 19: General Information

    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 In- terface 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 20: Profinet Implementation Details

    Application Process Instances (API) As mentioned previously, acyclic requests towards API 0 are forwarded to the Application Data Object. Cyclic data exchange is by default carried out through API 0 (i.e. the Anybus associates mod- ules and submodules with API 0). See also...

  • Page 21: Application Relationships (Ar)

    During the establishment of an IO Connection towards the Anybus CompactCom 40 PROFI- NET 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 Identifica- tion or RI) are compared.
  • Page 22 Submodule_Ext. This way, the host application can define exactly how 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 Compact- Com 40 PROFINET IRT.
  • Page 23 Further Actions to Resolve Mismatch, p. Resolving Mismatch (Default Configuration) If the Real Identification has been established according to the default mode, the Anybus Com- pactCom 40 PROFINET IRT will try to remap the Real Identification to match the Expected Identification.
  • Page 24 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:...

  • Page 25: Diagnostics

    Channel Diagnostic Alarm Generic Diagnostic Alarm (See Extended Diagnostics, p. Minor, unrecoverable Major, recoverable Major, unrecoverable Anybus enters Exception state Process alarms can not be created. See also.. • Diagnostic Object (02h), p. 91 4.5.2 Extended Diagnostics Using the network specific event code (FFh) creates a Generic Diagnostic Alarm on the net- work.

  • Page 26: Identification & Maintenance (I&M)

    184. If the example GSD file is used, I&M5 has to be disabled there aswell, se below. I&M5 is not available for Anybus IP. See below how to disable I&M5 in the GSD file for Anybus IP. Default I&M0 information:...
  • Page 27 4 bytes Product version of the Anybus CompactCom revision See also.. • PROFINET IO Object (F6h), p. 184 • Anybus CompactCom 40 Software Design Guide, Application Object (FFh) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 28: Asset Management

    The settings for Asset Management have to be added at the end of the Device Access Point, di- rectly after </Graphics>, or the GSD checker tool will invalidate the file: <DeviceAccessPointItem...> ..<Graphics> <GraphicItemRef Type=”DeviceSymbol” GraphicItemTarget”1”/> </Graphics> <AssetManagement/> </DeviceAccessPointItem> ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 29: Fast Start Up

    4.8.3 Fast Start Up Configuration with STEP7 The example below shows the procedure when the Siemens tool STEP7 is used for configuration. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 30 Double click on “Interface” in the Module column. The window shown to the right will ap- pear. Choose the Generaltab and check the box Prioritized startup. Fig. 4 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 31: Address Conflict Detection (Acd)

    Address announcement: after the initial probing, the module issues ARP announcements. If an IP address conflict is detected, IP address error will be indicated on the Network Status LED. The module will use address 0.0.0.0. A new address can be configured via the Anybus IP- config tool.

  • Page 32: Profienergy Profile

    4.10.1 Implementation The PROFIenergy profile is implemented in the Anybus CompactCom 40 PROFINET IRT ac- cording to the state machine described in the PROFIenergy Technical Specification (available from PROFIBUS International). PROFIenergy commands arriving from the network will be...

  • Page 33: Profisafe

    4.11 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. the IXXAT Safe T100/PS. For more information about this module, see IXXAT Safe T100 Manual, available at www.ixxat.com.

  • Page 34: Modular Device

    The first slot (slot 0) is always occupied by the Device Access Point (DAP) module, which repre- sents the head node where the Anybus CompactCom is located. It is not allowed to add a proc- ess data mapping for any ADI within the range of slot 0. The remaining slots are assigned fixed ranges of ADIs, set up using the Modular Device Object.

  • Page 35: Safety Module

    Map_ADI_Read_Ext_Area( ADI=760, FirstIndex=0, NumElems=3, DataTypes=(BIT4, PAD2, BIT2) ) Slot 3: Map_ADI_Write_Ext_Area( ADI=769, FirstIndex=0, NumElems=8, DataTypes=(UINT8,) ) Map_ADI_Read_Ext_Area( ADI=812, FirstIndex=3, NumElems=2, DataTypes=(UINT16,) ) Map_ADI_Read_Ext_Area( ADI=816, FirstIndex=0, NumElems=1, DataTypes=(INT32,) ) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 36 Fig. 6 5.6.4 Example View in TIA Portal Note that the GSD instantiates the same module, Module Type B in both slot 1 and slot 3. Fig. 7 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 37: Recommendations

    Fig. 8 After a successful process data remap the entire RI is regenerated and any I&M0 Filter Data must be reconfigured. Refer to the Expected_Ident_Ind command for finding out the new RI. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...

  • Page 38: Ftp Server

    Notes: • Usernames must not exceed 16 characters in length. • Passwords must not exceed 16 characters in length. • Usernames and passwords must only contain alphanumeric characters. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 39: Session Example

    - Substitute <user> with the username – - Substitute <password> with the password Press Enter. The Explorer will now attempt to connect to the Anybus module using the specified settings. If successful, the file system will be displayed in the Explorer window. Fig. 9 ®...

  • Page 40: Web Server

    If a complete customized web system is designed and no files in the vfs folder are to be used, it is recommended to turn off the virtual file system completely, see the Anybus File System Inter- face Object.
  • Page 41 IP address or name Max 64 characters User Max 64 characters Password Max 64 characters Safety Module Settings Name Description F-address The F-address used for the Safety Module as PROFIsafe address ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 42 Frame Size Too Long Frames received that exceed the maximum permitted frame size. Frame Size Too Short Frames received that are shorter than lowest permitted frame size. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 43: Server Configuration

    Web Server 41 (258) Description Fiber Optical Statistics (only avail- able for the Anybus CompactCom 40 PROFINET IRT Fiber Optic) Port 1 Temperature (C): Current temperature of port 1 transceiver, in degrees Celsius. Port 1 Power Budget (dB): Current received power budget for port 1 transceiver, in dB.
  • Page 44 Optionally, a login message can be specified by including the key [AuthName]. This message will be displayed by the web browser upon accessing the protected directory. File Format: Username1:Password1 Username2:Password2 UsernameN:PasswordN ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 45 If the list of approved users is put in another file, be aware that this file can be accessed and read from the network. In the following example, the list of approved users will be loaded from here.cfg and too.cfg. [File path] \i\put\some\over\here.cfg \i\actually\put\some\of\it\here\too.cfg [AuthName] Howdy. Password, please. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 46: E-Mail Client

    Optionally, delete the e-mail instance using the Delete command (04h) Sending a message based on a file in the file system is achieved using the Send Email from File command. This command is described in the SMTP Client Object (04h). ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...

  • Page 47: Server Side Include (Ssi)

    Server Side Include functionality, or SSI, allows data from files and objects to be represented on web pages and in e-mail messages. SSI are special commands embedded within the source document. When the Anybus Com- pactCom module encounters such a command, it will execute it, and replace it with the result (if applicable).
  • Page 48 Default Output Scenario Default Output Success (value of specified key) Authentication Error “Authentication error” File open error “Failed to open file ‘filename’” Key not found “Tag (key) not found” ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 49 Server Side Include (SSI) 47 (258) Example The following SSI... <?--exec cmd_argument='GetConfigItem("\example.cnf", "B")'--> ... in combination with the following file (‘\example.cnf’)... First Second Third ... returns the string ‘Third’. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 50 Scenario Default Output Success “Configuration stored to‘filename’” Authentication Error “Authentication error” File open error “Failed to open file ‘filename’” File write error “Could not store configuration to ‘filename’” ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 51 The resulting file (‘\food.txt’) may look somewhat as follows: [Name] Cliff Barnes [Food] Cheese [Drink] Beer In order for this example to work, the HTML file must be named “test.shtm”. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 52 This command stores returns the username on an authentication session. This command cannot be used in e-mail messages. Syntax: <?--#exec cmd_argument='DisplayRemoteUser'--> Default Output Scenario Default Output Success (current user) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 53 <P> <LABEL for="lang">Language(0-4): </LABEL><BR> <INPUT type="text" name="lang"><BR><BR> <INPUT type="submit" name="_submit"> </P> </FORM> </BODY> </HTML> In order for this example to work, the HTML file must be named “test.shtm”. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 54 <HEAD><TITLE>IncludeFile Test</TITLE></HEAD> <BODY> <H1> Contents of ‘info.txt’:</H1> <P> <?--#exec cmd_argument='IncludeFile("info.txt")'-->. </P> </BODY> </HTML> Contents of ‘info.txt’: Neque porro quisquam est qui dolorem ipsum quia dolor sit amet,consectetur, adipisci velit... ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 55 Server Side Include (SSI) 53 (258) When viewed in a browser, the resulting page should look somewhat as follows: Fig. 11 See also... • Include File, p. 45 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 56 Specifies whether to overwrite or append data to existing files. Default Output Scenario Default Output Success “Configuration stored to ‘filename’” Authentication Error “Authentication error” File Write Error “Could not store configuration to ‘filename’” ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 57 </HTML> The resulting file (\stuff.txt) will contain the value specified for the form object called “Meat”. In order for this example to work, the HTML file must be named “test.shtm”. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 58 56 (258) 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-func- tion printf(). The function accepts a template string containing zero or more formatting tags, followed by a number of arguments.
  • Page 59 (no effect) • Modifier Modifier Meaning Character Argument is interpreted as SINT8 or UINT8 Argument is interpreted as SINT16 or UINT16 Argument is interpreted as SINT32 or UINT32 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 60 “Too much data” ABCCMessage error ABCCMessage error string (Errors, p. Example See also... ABCCMessage(), p. 60 Example (Set_Attribute):, p. 62 Formatting Tags Formatting tags are written as follows: %[*][Width][Modifier]type ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 61 Width (Optional) Specifies the maximum number of characters to be read • Modifier (Optional) Specifies a different data size. Modifier Meaning SINT8, SINT16, UINT8 or UINT16 SINT32 or UINT32 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 62: Argument Functions

    Specifies the data type in the response (msgdata), see below. Numeric input can be supplied in the following formats: Decimal (e.g. 50) (no prefix) Octal (e.g. 043) Prefix 0 (zero) Hex (e.g. 0x1f) Prefix 0x ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 63 Failure to observe this may cause loss of data or other undesired side effects. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 64 Instance #3 (IP address) command Set_attribute Attribute #5 msgdata Use data parsed by scanf() call c_type UINT8[4] Array of 4 unsigned 8-bit integers r_type NONE Response message holds no data ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 65 “Not enough data in msg data field” “Out of range” “Invalid state” “Out of resources” “Segmentation failure” “Segmentation buffer overflow” 17... 255 “Unknown error” See also... SSI Output Configuration, p. 64 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 66: Ssi Output Configuration

    If no information for the selected language is found, it will use the default SSI output. Value of X Language English German Spanish Italian French See also... • SsiOutput(), p. 50 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 67: Json

    JSON is an acronym for JavaScript Object Notation and an open standard format for storing and exchanging data in an organized and intuitive way. In Anybus CompactCom, it is used to transmit data objects consisting of name - value pairs between the webserver in the Anybus CompactCom and a web application.

  • Page 68: Json Objects

    Response data: Name Data Type Description — Array of Strings Sorted list of string representations of the ADI value attributes JSON response example (using offset): "FF", "A201", "01FAC105" ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 69 <offset> or <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 70 "numelements": 1, "datatype": "min": "00", "max": "FF", "access": 0x03 JSON response example (using inst): "instance": "name": "Temperature threshold", "numelements": 1, "datatype": "min": "00", "max": "FF", "access": 0x03 null, null ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 71 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. The ADI metadata is static during runtime.
  • Page 72 "numsubelements": null "elementname": null JSON response example (instance): "instance": "numelements": 1, "datatype": "descriptor": "name": "Temperature threshold", "max": "FF", "min": "00", "default": "00", "numsubelements": null "elementname": null null, null ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 73 String representation for the corresponding value. value Number Value corresponding to the string representation. JSON response example: "string": "String for value 1", "value": 1 "string": "String for value 2", "value": 2 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 74 A callback function for JSONP output. 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 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 75 JSON response example: "modulename": "ABCC M40", "serial": "ABCDEF00", "fwver": [ 1, 5, 0 ], "uptime": [ 5, 123456 ], "cpuload": "fwvertext": "1.05.02", "vendorname": "HMS Industrial Networks", "hwvertext": "2", "networktype": "0085", ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 76 1: Link speed Number 0: 10 Mbit 1: 100 Mbit duplex Number 0: Half 1: Full JSON response example: "mac": "003011FF0201", "comm1": "link": "speed": "duplex": "comm2": "link": "speed": "duplex": ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 77 "domainname": "hms.se" To change IP settings, use network/ipconf.json. It accepts any number of arguments from the list above. Values should be in the same format. Example: GET ipconf.json?dhcp=0&addr=10.11.32.2&hostname=abcc123&domainname=hms.se ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 78 The parameters “comm1” and “comm2” are configurable by adding them as arguments to the GET request: GET network/ethconf.json?comm1=0&comm2=4 The parameters “comm1” and “comm2” may hold an error object with Anybus error code if the module fails processing the request: "mac": [00, 30, 11, FF, 02, 01], "comm1":...
  • Page 79 IN: unsupported protocol type outoctets Number OUT: bytes outucast Number OUT: unicast packets outnucast Number OUT: broadcast and multicast packets outdiscards Number OUT: discarded packets outerrors Number OUT: errors ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 80 Number Times that the carrier sense was lost or never asserted when attempting to transmit a frame toolong Number Frames received that exceed the maximum permitted frame size ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 81 { "name": "Connection Close Requests", "value": 0 }, { "name": "Connection Close Format Rejects", "value": 0 }, { "name": "Connection Other Rejects", "value": 0 }, { "name": "Connection Timeouts", "value": 0 }, ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 82 { "name": "Rx aborts received", "value": 0 }, { "name": "Transaction aborts sent", "value": 0 }, { "name": "Transaction rejects sent", "value": 0 }, { "name": "Transaction errors sent", "value": 0 }, ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 83 { "name": "AE Confirmed notifications sent", "value": 0 }, { "name": "AE UnConfirmed notifications sent", "value": 0 }, { "name": "AE Confirmed notification errors", "value": 0 }, { "name": "AE DAB lookup errors", "value": 0 }, ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 84 { "name" : "Port 2 Temperature (C)", "value" : "40.57" }, { "name" : "Port 2 Power Budget (dB)", "value" : "0.0" }, { "name" : "Port 2 Power Budget Status", "value" : "OK" } ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 85 The value 5 encoded as a UINT16, with dataformat = 0 (little endian): 0500 The character array “ABC” encoded as CHAR[3] (dataformat is not relevant for CHAR): 414243 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 86: Example

    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. <html> <head> <title>Anybus CompactCom</title> <!-- Imported libs --> <script type="text/javascript" src="vfs/js/jquery-1.9.1.js"></script> <script type="text/javascript" src="vfs/js/tmpl.js"></script>...

  • Page 87: Snmp Agent

    11.3 Management Information (MIB) A MIB is a device database that is accessed by an SNMP agent. The Anybus CompactCom 40 PROFINET IRTsupports standardized MIBs: LLDP-MIB and MIB-II. Standardized MIBs are de- fined 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 88 (1..3) = Number of tocols requested be transmitted to a non-uni- non-unicast packets cast (i.e. a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 89 Reference to MIB definitions specific to the particular media being used to realize the in- terface. Here no reference is available, so a fixed value is used for all ports. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 90: Media Reduncancy Protocol (Mrp)

    The Media Redundancy Clients (MRC) basically work as switches that pass on the tokens. The Anybus CompactCom supports acting as a Me- dia Redundancy Client (MRC). It also supports propagating link change to the Media Redun- dancy Master.

  • Page 91: Anybus Module Objects

    Anybus Module Objects 89 (258) Anybus Module Objects 13.1 General Information Standard Objects: • Anybus Object (01h), p. 90 • Diagnostic Object (02h), p. 91 • Network Object (03h), p. 94 • Network Configuration Object (04h), p. 99 Network Specific Objects: •...

  • Page 92: Anybus Object (01H)

    Anybus Module Objects 90 (258) 13.2 Anybus Object (01h) Category Basic Object Description This object assembles all common Anybus data, and is described thoroughly in the general Anybus CompactCom 40 Software Design Guide. Supported Commands Object: Get_Attribute Instance: Get_Attribute Set_Attribute...

  • Page 93: Diagnostic Object (02H)

    13.3 Diagnostic Object (02h) Category Extended 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. Supported Commands Object: Get_Attribute Create Delete...
  • Page 94 Anybus Module Objects 92 (258) 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:...
  • Page 95 Anybus Module Objects 93 (258) 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...

  • Page 96: Network Object (03H)

    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 Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 97 Write process data UINT16 Current write process data size (in bytes) size Updated on every successful Map_ADI_Write_Area. (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) Read process data UINT16 Current read process data size (in bytes) size Updated on every successful Map_ADI_Read_Area.
  • Page 98 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 99 Indicated by network specific error code 01h (total error re- sponse is FFh FFh 01h). Error control is only performed on the command parameters. The Anybus module does not verify the cor- rectness of these parameters by a read of the actual ADI attributes.
  • Page 100 98 (258) 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 101: Supported Commands

    Description Number of instances UINT16 Supported number of instances Highest instance UINT16 Highest instance number number (Consult the general Anybus CompactCom 40 Software Design Guide for further information.) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 102 Anybus Module Objects 100 (258) Instance Attributes (Instance #3, IP Address) Value is used after module reset. Name Access Data Type Description Name Array of “IP address” CHAR (Multilingual, see page 106) Data type UINT8 04h (= UINT8) Number of elements...
  • Page 103 Anybus Module Objects 101 (258) Instance Attributes (Instance #5, Gateway Address) Value is used after module reset. Name Access Data Type Description Name Array of “Gateway” CHAR (Multilingual, see page 106) Data type UINT8 04h (= UINT8) Number of elements...
  • Page 104 Anybus Module Objects 102 (258) 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 “DNS1” CHAR (Multilingual, see page 106) Data type...
  • Page 105 Anybus Module Objects 103 (258) 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 “Host name” CHAR (Multilingual, see page 106) Data type UINT8...
  • Page 106 Anybus Module Objects 104 (258) 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 “SMTP Pswd” CHAR (Multilingual, see page 106)
  • Page 107 Instance Attributes (Instance #20, Station Name) The Station Name identifies the Anybus module on PROFINET. If this value is changed by the host applica- tion during runtime, a reset is required in order for changes to have effect. Changes made through DCP will have immediate effect, however.
  • Page 108 Anybus Module Objects 106 (258) 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).
  • Page 109 Anybus Module Objects 107 (258) 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 110: Get_Attribute

    Anybus Module Objects 108 (258) 13.6 Socket Interface Object (07h) Category Extended Object Description This object provides direct access to the TCP/IP stack socket interface, enabling custom protocols to be im- plemented over TCP/UDP. Note that some of the commands used when accessing this object may require segmentation. A message will be segmented if the amount of data sent or received is larger than the message channel can handle.
  • Page 111 Anybus Module Objects 109 (258) 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 Local port that the socket is bound to...
  • Page 112 Anybus Module Objects 110 (258) 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. • Command Details Field Contents CmdExt[0]...
  • Page 113 Anybus Module Objects 111 (258) 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 114 Anybus Module Objects 112 (258) 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 115 Anybus Module Objects 113 (258) 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) • Response Details (no data) ®...
  • Page 116 Anybus Module Objects 114 (258) 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. The new socket is connected with the host and the response returns its instance number.
  • Page 117 Anybus Module Objects 115 (258) 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 118 Anybus Module Objects 116 (258) 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, p.
  • Page 119 Anybus Module Objects 117 (258) 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, p.
  • Page 120 Anybus Module Objects 118 (258) 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, p.
  • Page 121 Anybus Module Objects 119 (258) 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 segmen- tation may be used to send up to 1472 bytes (For more information, see appendix For more information, see Message Segmentation, p.
  • Page 122 Anybus Module Objects 120 (258) 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” automatically, however this command may be used to specify up to 20 additional memberships.
  • Page 123 Anybus Module Objects 121 (258) 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 CmdExt[0] (reserved) (set to zero) CmdExt[1] Data[0...
  • Page 124 Anybus Module Objects 122 (258) 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 A timeout event occurred...
  • Page 125 The maximum message size supported by the Anybus CompactCom 40 is normally 1524 bytes. In some ap- plications a maximum message size of 255 bytes is supported, e.g. if an Anybus CompactCom 40 is to re- place an Anybus CompactCom 30 without any changes to the application. The maximum socket message size is 1472.
  • Page 126 Anybus Module Objects 124 (258) Response Segmentation When a response is segmented, the command initiator requests the next segment by sending the same com- mand multiple times. For each response, the data field is exchanged with the next data segment.

  • Page 127: Smtp Client Object (09H)

    Anybus Module Objects 125 (258) 13.7 SMTP Client Object (09h) Category Extended Object Description This object groups functions related to the SMTP client. Supported Commands Object: Get_Attribute Create Delete Send e-mail from file (see below) Instance: Get_Attribute Set_Attribute Send e-mail (see below)
  • Page 128 Anybus Module Objects 126 (258) 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] • Response Details Field Contents...
  • Page 129 Anybus Module Objects 127 (258) Command Details: Delete Category Extended Details Command Code Valid for: Object Description This command deletes an e-mail instance. • Command Details Field Contents Comments CmdExt[0] E-mail instance number low byte CmdExt[1] high byte • Response Details (no data) ®...
  • Page 130 Anybus Module Objects 128 (258) 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:...
  • Page 131 Anybus Module Objects 129 (258) Command Details: Send E-mail Category Extended Details Command Code Valid for: Instance Description This command sends the specified e-mail instance. • Command Details (no data) • Response Details (no data) Object Specific Error Codes Error Codes...

  • Page 132: File System Interface Object (0Ah)

    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. ® Anybus CompactCom ™...

  • Page 133: Network Ethernet Object (0Ch)

    Anybus Module Objects 131 (258) 13.9 Network Ethernet Object (0Ch) Category Extended 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 Port 1 Port 2 Each instance provides statistic counters for the port with the MAC address given in attribute #4.
  • Page 134 Anybus Module Objects 132 (258) Name Access Data Type Description Interface Counters Array of Array containing MIB-II interface counters (rfc1213) UINT32 See table below for array indices. Media Counters Array of Array containing Ethernet-Like MIB counters for the port. UINT32 See table below for array indices.

  • Page 135: Map_Adi_Write_Area

    If the end-user wishes to define modules in another way the application must provide the module configura- tion to the Anybus CompactCom 40 PROFINET IRT. This is achieved by using the following commands: •...
  • Page 136 Anybus Module Objects 134 (258) 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 137: Object Attributes (Instance #0)

    Anybus Module Objects 135 (258) Object Attributes (Instance #0) Name Access Data Type Value Name Array of “Network PROFINET IO” Char Revision UINT8 Number of instances UINT16 0001h Highest instance UINT16 0001h number Instance Attributes (Instance #1) Extended Name Access...
  • Page 138 Anybus Module Objects 136 (258) 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 139 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. In such case, the Anybus will automatically issue a Plug or Plug Wrong Submodule-alarm to the IO Controller.
  • Page 140 Anybus Module Objects 138 (258) • 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 Bit 1-7: (reserved, set to zero) (reserved for future use) CmdExt[1]...
  • Page 141 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. 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 142 Anybus Module Objects 140 (258) • 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 Bit 1-7: (reserved, set to zero) (reserved for future use) CmdExt[1]...
  • Page 143 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 144 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 IRT0 then automatically issues a Pull alarm to the master.
  • Page 145 This command may only be issued prior to setting the Setup Complete-attribute in the Anybus Object. This command clears the default Real Identification created by the Anybus module while mapping ADIs to Proc- ess Data. Therefore, issuing this command effectively makes it mandatory to specify the actual Real Identifica- tion by means of the Plug_Module and Plug_Submodule-commands.
  • Page 146 Anybus Module Objects 144 (258) 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 sig- nals to the module (and in turn the I/O Controller) that the host application is ready for data exchange.
  • Page 147 > 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 148 Anybus Module Objects 146 (258) • 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 de- pends on the application.
  • Page 149 Anybus Module Objects 147 (258) 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. It is optional to implement support for this command, except for that it must be issued if the host application previously has responded with Block to the command Expected_Ident_Ind (1Bh).
  • Page 150 Anybus Module Objects 148 (258) 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...
  • Page 151 Anybus Module Objects 149 (258) 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...

  • Page 152: Functional Safety Module Object (11H)

    Functional Safety Module Object (11h) Category Extended Object Description This object contains information provided by the Safety Module connected to the Anybus CompactCom mod- ule. Please consult the manual for the Safety Module used, for values of the attributes below. Supported Commands Object:...
  • Page 153 0x02, second byte = 0x0C UINT8 Minor 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...
  • Page 154 Safe State at the same time. The application issues this command to the Anybus CompactCom module, when an error has been cleared by for example an operator. The Anybus CompactCom forwards the command to the Safety Module.
  • Page 155 Anybus Module Objects 153 (258) 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. This string is used by networks where there are no other means (e.g. PLC or some other tool) to provide the configuration to the safety module.
  • Page 156 This command can be issued by the application to get the complete safety input PDU sent by the safety mod- ule. The Anybus CompactCom 40 PROFINET IRT will respond with the complete safety PDU, that the appli- cation then has to interpret.
  • Page 157 Anybus Module Objects 155 (258) Object Specific Error Codes Error Code Description Comments The safety module rejected a Error code sent by safety module is found in MsgData[2] and MsgDa- message. ta[3]. Message response from the safety module has incorrect format (for ex- ample, wrong length).

  • Page 158: Host Application Objects

    Energy Measurement Object (E4h), p. 157 • Functional Safety Object (E8h), p. 172 • “ Application File System Object (EAh)” (see Anybus CompactCom 40 Software Design Guide) • “ Modular Device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide) •...

  • Page 159: Energy Measurement Object (E4H)

    The table below shows an example of how the instances of the Anybus CompactCom object model maps to PROFIenergy. PROFIenergy uses the Object number to address a logical device, while the Measurement ID refers to the actual measurement value.
  • Page 160 PH – Phase (L1–Line 1, L2 –Line 2, L3 – Line 3) – N – Neutral, G – Ground • “-” indicates the measurement value has no representation on PROFIenergy. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 161 4: L2-L3 Value UINT32 5: Reserved UINT64 6: L3-L1 TS FLOAT 7: L3-L1 Value UINT32 8: Reserved UINT64 9: Avg L-L TS FLOAT 10: Avg L-L Value UINT32 11: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 162 4: L2-G Value UINT32 5: Reserved 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 11: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 163 4: L2 Value UINT32 5: Reserved UINT64 6: L3 TS FLOAT 7: L3 Value UINT32 8: Reserved UINT64 9: Total TS FLOAT 10: Total Value UINT32 11: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 164 4: L2 Value UINT32 5: Reserved UINT64 6: L3 TS FLOAT 7: L3 Value UINT32 8: Reserved UINT64 9: Total TS FLOAT 10: Total Value UINT32 11: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 165 4: L2 Value UINT32 5: Reserved UINT64 6: L3 TS FLOAT 7: L3 Value UINT32 8: Reserved UINT64 9: Total TS FLOAT 10: Total Value UINT32 11: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 166 1: Consumed Value UINT32 2: Reserved UINT64 3: Generated TS FLOAT 4: Generated Value UINT32 5: Reserved UINT64 6: Sum TS FLOAT 7: Sum Value UINT32 8: Reserved ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 167 Sum variable a positive value indicates consumed reactive energy (induc- tive load); a negative value indicates generated reactive energy (capacitive load). Total Apparent Absolute value energy ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 168 Host Application Objects 166 (258) Command Details: Get_Attribute_Measurement_List Details Command Code Valid for: Instance ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 169 This command is used to gather all supported attribute elements of an instance. If several instances are sup- ported, the command will be sent numerous times (implied by object attribute Highest instance number). Based on the response(s) the Anybus CompactCom will provide information to the network indicating which measurement values that are supported by a device.

  • Page 170: Asset Management Object (E5H)

    Revision UINT8 Number of instances UINT16 Max 32. Depends on number of non PROFINET components. Highest instance no. UINT16 Max 32. Depends on number of non PROFINET components. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 171 AM_SoftwareRevision and IM_Software_Revision are of no interest and thus not read by the Anybus CompactCom. In the same manner, if AM_FirmwareOnly is selected the attributes AM_HardwareRe- vision and IM_Hardware_Revision are of no interest and thus not read by the Anybus CompactCom. Name...
  • Page 172 If attribute #14, IM Hardware Revision, is sup- ported, then this attribute should not be implemented. IM Hardware UINT16 Manufacturer defined hardware revision Revision 0000h-FFFFh (FFFFh indicates availability of profile specific information) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 173 Level 10 Level 11 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 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 174: Functional Safety Object (E8H)

    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 sup- ported and a Safety Module is connected to the Anybus CompactCom module. Supported Commands...
  • Page 175 The Anybus CompactCom validates the cycle time according to the minimum values above. If e.g. baud rate is 625 kbit/s and the cycle time is set to 2 ms the Anybus CompactCom will enter the EXCEPTION state. FW upgrade in...

  • Page 176: Sync Object (Eeh)

    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 177 T_IO_OutputMin consists of two delays: • The delay added by the Anybus CompactCom. This is the time from when the message is available on the network until it is available to the application. This delay is 0 in the current implementation.
  • Page 178 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 179 Input processing T_IO_InputMin - 12 UINT32 Maximum required time, in nanoseconds, µs from “Input capture” until write process data has been completely written to the Anybus CompactCom module Min cycle time T_DC_Min UINT32 Minimum cycle time supported by the appli-...

  • Page 180: Energy Control Object (F0H)

    All instance attributes shall be seen as required and must be imple- mented in the application. If the Anybus module detects that an attribute is missing during run time an appro- priate network error is sent and the Discard Responses counter is increased in the Anybus Object instance attribute Error Counter.
  • Page 181 If the value is undefined the value 0.0 shall be used. Transition to “Power BOOL Indicates whether transition to “Power off” mode is supported or off” mode supported not. Not supported Supported ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 182 False Not available True Available (Value if attribute not implemented) Power Consumption UINT32 Indicates the power consumption of the device when in this state. Not used for PROFINET. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 183 Given the state of the device and the requested pause time it is currently not possible to enter any energy saving mode 0x12 Value too low The requested pause time is too short ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 184 If the application is unable to end the pause it shall return the error code in the table below. Error code Description 0x0D Invalid state Given the state of the device, it is currently not possible to end the pause ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 185 Given the state of the device and the requested pause time it is currently not possible to enter any energy saving mode 0x12 Value too low The requested pause time is too short ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 186: Profinet Io Object (F6H)

    See also... • Network PROFINET IO Object (0Eh), p. 133 • Flowchart — Record Data Access, p. 210 • Anybus CompactCom 40 Software Design Guide, “Error Codes” Supported Commands Object: Get_Attribute (01h) Get_Record (10h, see below) Set_Record (11h, see below)
  • Page 187 <DeviceIdentity VendorID=“0x010C” DeviceID=“0x0010”> • Attribute #3 corresponds to the following entry in the GSDML file: DNS_CompatibleName=“ABCC40-PIR” • Attribute #8 correspond to the following entry in the GSDML file: <OrderNumber Value="ABCC40-PIR"/> ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 188 If an attribute is not implemented, the default value will be used. • The Anybus module in itself does not alter its behavior based on the value of attributes #13 and #14. The host application has to implement the corresponding functionality..
  • Page 189 Valid characters are letters “a” to “z”, numbers “0” to “9”, hyphens and periods. The attribute value must begin with a letter. Maximum number of elements in array: 58 For more information, see the Anybus CompactCom M40 Hardware Design Guide. IM Module Order ID Array of Anybus I&M5 parameter.
  • Page 190 Index of request MsgData[9] Index (high byte) MsgData[10] Length (low byte) Range: 1 - 1524 MsgData[11] is only available if the length value exceeds MsgData[11] Length (high byte) 255. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 191 User specific. Set to zero if no Additional Data 2 is defined. See also... • Details for the command Set_Record (below) • Flowchart — Record Data Access, p. 210 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 192 Host Application Objects 190 (258) Command Details: Set_Record Category Extended Details Command Code Valid for: Object Instance ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 193 Additional Data 2 User specific. Set to zero if no Additional Data 2 is defined. See also... • Command details for “Get_Record” • Flowchart — Record Data Access, p. 210 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 194 FIRST_AR COMPANION_AR MsgData[10] Remote station name length Length of remote station name, in bytes MsgData[11.. Remote station name Remote station name (IO Controller/Supervisor) • Response Details (no data) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 195 Host Application Objects 193 (258) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 196 Expected Submodule Identifier (low word, high byte) MsgData[14] Expected Submodule Identifier (high word, low byte) MsgData[15] Expected Submodule Identifier (high word, high byte) • Response Details (no data) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 197 For very large configurations where the Expected Identification cannot fit into one message, this segmenta- tion protocol will be used. If the number of modules/sub-modules exceeds the capabilities of the Anybus CompactCom the message will be truncated. The size of the configuration can be up to 2370 bytes at maxi- mum number of modules/sub-modules.
  • Page 198 Each module starts with a module block, which holds the slot number, the number of submodules (or sub- slots) and the module identity number. Finally each submodule block holds subslot number, submodule identification number, input and output data lengths. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 199 In this example, the configuration contains two APIs with the following properties: • API #0 contains two modules, the first with three submodules, the second with one submodule • API #2 contains one module with two submodules ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 200 Ready for Data Exchange Not ready for data exchange (Appl_State_Ready must be issued at a later stage) See also... • Appl_State_Ready, details in Network PROFINET IO Object (0Eh), p. 133 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 201 Host Application Objects 199 (258) Command Details: AR_Abort_Ind Category Extended Details Command Code Valid for: Object Instance ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 202 Not synchronized (cannot start companion- Wrong topology (cannot start companion- Dcp, station-name changed Dcp, reset to factory-settings Cannot start companion AR because of pa- rameter error • Response Details (no data) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 203 The application should flash its dedicated Network Status LED for 3 seconds after receiving this command. • Command Details Field Contents Comments CmdExt[0] (reserved) CmdExt[1] • Response Details (no data) ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 204 Resource unavailable 4... 7 (reserved) 8... 15 User specific 13... 15 User specific (user specific) User specific See also... • Command details for Get_Record • Command details for Set_Record ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 205: Ethernet Host Object (F9H)

    Enable Web BOOL True Enable/Disable Web Server Server (Enabled) (Not used if Transparent Ethernet is enabled.) (reserved) Reserved for Anybus CompactCom 30 applications. Enable Web ADI BOOL True Enable/Disable Web ADI access access (Enabled) (Not used if Transparent Ethernet is enabled.)
  • Page 206 0 = False Enables the option to reset the module from HICP. from HICP IP configuration Struct of: Whenever the configuration is assigned or changed, the Anybus CompactCom module will update this attribute. UINT32 (IP address) UINT32 (Subnet mask) UINT32 (Gateway) ®...
  • Page 207 (mask off and ignore) Link port 1 Current link status for port 1 EtherCAT only: This link status indicates whether the Anybus CompactCom is able to communicat 1 = Link sensed using Ethernet over EtherCAT (EoE) or not. That 0 = No link...
  • Page 208 Example 2: If Attribute #22 has been set to 2 (Host Name) Attribute #23 will be ignored and the Client Identifier will be the same as the configured Host Name. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 209: A Categorization Of Functionality

    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. The basic functions of the industrial network are used.

  • Page 210: B Anybus Implementation Details

    In the case of PROFINET, this bit is set when one or more IO connections are established. Anybus State Machine The table below describes how the Anybus State Machine relates to the PROFINET network. Anybus State Implementation Comment...

  • Page 211: B.4 Application Watchdog Timeout Handling

    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. Application Watchdog Timeout Handling Upon detection of an application watchdog timeout, the module will cease network participation and shift to the state EXCEPTION.

  • Page 212: C Flowcharts

    Appendix C: Flowcharts 210 (258) Flowcharts 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? handler Range: AFF0h... AFFFh Range: Profile Specific I&M handler...

  • Page 213: C.2 Flowchart — I&M Record Data Handling

    Appendix C: Flowcharts 211 (258) 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 I&M Transp for slot 0 I&M Transp...

  • Page 214: C.3 Flowchart —Establishment Of Real Identification (Ri)

    Issue 'API_Add' Additional (API #X) API? Issue 'Plug_Module' (Slot 0) Issue 'Plug_SubModule' (Slot 0, Sub-slot 1) (Anybus assembles RI automatically) Issue 'Plug_SubModule' (Slot 0, Sub-slot 8000h) Issue 'Plug_SubModule' (Slot 0, Sub-slot 8001h) Issue 'Plug_SubModule' (Slot 0, Sub-slot 8002h) Issue 'Plug_Module'...

  • Page 215: C.4 Flowcharts — Handling Of Configuration Mismatch

    Flowcharts — Handling of Configuration Mismatch C.4.1 Default Configuration Mismatch This flowchart shows how the Anybus CompactCom automatically handles a configuration mis- match when the Real Identification has been established by the default configuration method. Connect with *The controller may choose to connect to...
  • Page 216 Expected Identification Send “Block” Send “Continue” Response Response Pull mismatching module/ submodule Repeat for all adaptable modules/submodules Plug adapted module/ submodule Send Ident_Change_Done command Done Fig. 20 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 217: D Secure Hicp (Secure Host Ip Configuration Protocol)

    Anybus IPconfig utility for changing settings, e.g. IP address, Subnet mask, and enable/disable DHCP. Anybus IPconfig can be downloaded free of charge from the HMS website, www.anybus. com. This utility may be used to access the network settings of any Anybus product connected to the network via UDP port 3250.

  • Page 218: E Technical Specification

    Test sequences are performed on the Network and Module Status LEDs during startup. E.1.2 Front View (Fiber Optics Connectors) Item Network Status LED Module Status LED Optical signal from the Anybus CompactCom module Optical signal to the Any- bus CompactCom module Link/Activity LED (port 1) Link/Activity LED (port 2) Test sequences are performed on the Network and Module Status LEDs during startup.
  • Page 219 LINK/Activity LED LED State Description Comments No Link No link, no communication present Green Link Ethernet link established, no communication present Green, flickering Activity Ethernet link established, communication present ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 220: E.2 Functional Earth (Fe) Requirements

    For further information, see PROFINET Installation Guideline for Cabling and Assembly, avail- able for download at www.profinet.com. Power Supply E.3.1 Supply Voltage The Anybus CompactCom 40 PROFINET IRT requires a regulated 3.3 V power source as specified in the general Anybus CompactCom 40 Hardware Design Guide. ® Anybus CompactCom ™...

  • Page 221: E.4 Environmental Specification

    E.3.2 Power Consumption TheAnybus CompactCom 40 PROFINET IRT is designed to fulfil the requirements of a Class B module. The current hardware design consumes up to 390 mA TheAnybus CompactCom 40 PROFINET IRT FO is designed to fulfil the requirements of a Class C module.

  • Page 222: F.1 How To Design For Aida Led Mode

    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 sig- nals are available on the host application connector.
  • Page 223 No Activity Orange, flashing Activity There is no LED on the front of the Anybus CompactCom 40 PROFINET IRT showing this indi- cation, but the signal is available in the host application connector according to this table: AIDA indication Signal Name, Host Application Connector...
  • Page 224 The Port Activity signals are always available in the host application connector in all operating modes except 16 bit parallel. For more information consult the Anybus CompactCom M40 Hard- ware Design Guide (module) or the Anybus CompactCom B40-1 Design Guide (brick).

  • Page 225: G Conformance Test Guide

    223 (258) Conformance Test Guide 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 AB, will require a certification.

  • Page 226: G.2 Reidentifying Your Product

    224 (258) Reidentifying Your Product After successful setting of the Setup Complete attribute in the Anybus Object (01h), the Any- bus 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 227: G.3 Factory Default Reset

    Anybus module will erase all IP and Station Name information and inform the host application that a hardware reset of the Anybus module is required. This is done by sending a Reset command to the Application Object (FFh) of the host. For more details, please consult the Anybus CompactCom Software Design Guide.

  • Page 228: G.6 Documentation Considerations

    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. A shift register application must use the PA signal to clear outputs when the Anybus Com- pactCom 40 PROFINET IRT is not in the state PROCESS_ACTIVE.
  • Page 229 Plug the modules of slot 1-x Set the product identity information in PROFINET IO Object (F6h) Anybus Object (01h), Instance #1, Setup Complete set to 1 Fig. 23 The figure shows how to set up a PROFINET compatible DAP. Please note that for some com- mands only the relevant parameters are shown.

  • Page 230: G.9 Changes In Gsd File For Conformance Class B

    The example GSD file, supplied by HMS Industrial Networks AB, is adapted for testing a Any- bus 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. The im- plementation can then be conformance tested for conformance class B instead.

  • Page 231: H Backward Compatibility

    30 and 40 series modules in the same application. This appendix presents the backwards compatibility issues that have to be considered for Any- bus CompactCom 40 PROFINET IRT, when designing with both series in one application, or when adapting a 30 series application for the 40 series.

  • Page 232: H.2 Hardware Compatibility

    Anybus CompactCom M30/M40 H.2.2 Chip The chip (C30/C40) versions of the Anybus CompactCom differ completely when it comes to physical dimensions. There is no way to migrate a chip solution from the 30-series to the 40-series without a major hardware update.
  • Page 233 H.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 AB has de- veloped a separate brick version in the 40-series, that can be used for migration. This product, B40-2, shares dimensions etc.
  • Page 234 Related Information: Anybus CompactCom M40 Hardware Design Guide (HMSI-216-126), Sec- tion “Application Connector Pin Overview” Module Identification (MI[0..1]) These pins are used by the host application (i.e your product) to identify what type of Anybus CompactCom that is mounted. The identification differs between the 30-series and the 40- series.
  • Page 235 In the 40-series, there is a possibility to set the GIP[0..1] and GOP[0..1] in high impedance state (tri-state) by using attribute #16 (GPIO configuration) in the Anybus object (01h). I.e. if it is not possible to change the host application hardware, this attribute can be configured for high impe- dance state of GIP and GOP before leaving NW_INIT state.
  • Page 236 234 (258) RMII Compatibility If the RMII mode is being used on an Anybus CompactCom 40 module and it is desired to re- main compatible with the 30 series, it is important to disable this connection when switching to an Anybus CompactCom 30 module due to pin conflicts. The RMII port of the host processor should be set to tristate by default, and only be enabled if an RMII capable Anybus Compact- Com 40 is detected.

  • Page 237: H.3 General Software

    Memory areas not supported by the specific network cannot be used. Make sure you do not ac- cess these areas, e.g. for doing read/write memory tests. Related Information: Anybus CompactCom 40 Software Design Guide (HMSI-216-125), Sec- tion “Memory Map” H.3.2 Faster Ping-Pong Protocol The ping-pong protocol (the protocol used in the 30-series) is faster in the 40-series.
  • Page 238 H.3.5 Control Register CTRL_AUX-bit 30-series The CTRL_AUX bit in the control register indicates to the Anybus CompactCom if the process data in the current telegram has changed compared to the previous one. 40-series The value of the CTRL_AUX bit is always ignored. Process data is always accepted.

  • Page 239: H.4 Network Specific — Profinet

    Appendix H: Backward Compatibility 237 (258) Network Specific — PROFINET Related Information: Anybus CompactCom 40 PROFINET IRT Network Guide, HMSI-27-226 Network Interface Appendix, Anybus CompactCom 30, PROFINET IO 2-Port, HMSI-168-49 H.4.1 Network Object (03h) Attribute Default Anybus CompactCom Product Comment...
  • Page 240 “ABCC40- 40-series, PROFINET IRT series. PIR” If the attribute is not implemented, the default value differs between the different Anybus CompactCom PRO- FINET types. #19, System “HMS Indus- 30-series, PROFINET IO 1-Port If the attribute is implemented in the Description...
  • Page 241 Available Removed Attribute removed in the 40-series. The Any- bus CompactCom will never request this at- tribute. The host application cannot influence the I&M implemented by the Anybus CompactCom. 16, I&M Supported Available Removed Attribute removed in the 40-series. The Any- bus CompactCom will never request this at- tribute.
  • Page 242 API, Slot, and Subslot are determined with the help of Slot and ADI given by the extended diagnostic mode. Process alarms cannot be created in the 40-series. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 243 I&M4 is removed in the 40-series. Writeable I&M records in GSD must be updated (see GSD section below). H.4.8 LED Indications Changes has been made regarding the specification of the LED indications. See tables below for differences. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 244 Station Name error Station name not set IP address error IP address not set Red, 2 flashes Red, 3 flashes Configuration error Expected Identification differs from Real Identification. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 245 Object (04h), Attribute 17) and sysName (Network Configuration Object (04h), Attrib- ute 15) are no longer used. Nothing needs to be updated in your implementation but attribute values will no longer be used. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 246 Module ID: Submodule ID: 0: Mapped to write PD area Number of ADI start ADI number 1: Mapped to read PD area elements to map element number Fig. 30 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 247 Anybus CompactCom 30 PROFINET IO Network Appendix, HMSI-168-74, Section “Configura- tion Mismatch”. 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”. H.4.12 Media Redundancy Protocol (MRP) MRP is supported in the 40-series and cannot be disabled by the host application.
  • Page 248 The example GSD file, supplied by HMS Industrial Networks AB, is prepared for testing an Any- bus CompactCom 40 PROFINET IRT for conformance class C, which includes PROFINET iso- chronous 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 249 New MRP keyword in the 40-series. MRP not supported in 30-series. IsDefaultRingport="true" New MRP keyword in the 40-series. MRP not supported in 30-series. VirtualSubmoduleItem->Writeable_IM_Re- I&M4 removed in the 40-series cords="1 2 3" ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...

  • Page 250: I Copyright Notices

    License is also granted to make and use derivative works provided that such works are identi- fied as "derived from the RSA Data Security, Inc. MD4 Message-Digest Algorithm" in all material mentioning or referencing the derived work. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 251 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. ******************************************************************************** rsvp.js ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 252 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide...
  • Page 253 THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 254 OR CONTRIBUTORS BE LIABLE 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 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 255 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. ******************************************************************************** ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 256 2. Redistributions in binary form must reproduce the above copyright notice, this list of condi- tions and the following disclaimer in the documentation and/or other materials provided with the distribution. ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 257 3. This notice may not be removed or altered from any source distribution. L. Peter Deutsch ghost@aladdin.com ******************************************************************************** The “inih” library is distributed under the New BSD license: ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 258 This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/. To obtain customized changes please contact foss@anybus.com. ********************************************************************************...
  • Page 259 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. @(#)queue.h 8.5 (Berkeley) 8/20/94 ® Anybus CompactCom ™ 40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8...
  • Page 260 last page © 2018 HMS Industrial Networks AB Box 4126 300 04 Halmstad, Sweden info@hms.se SCM-1202-023 EN 1.8 / 2018-06-18 / 8748...

Table of Contents