1. Manuals
  2. Brands
  3. Anybus Manuals
  4. Control Unit
  5. CompactCom 40 EtherNet/IP
  6. Network manual

Anybus CompactCom 40 EtherNet/IP Network Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Network Guide
®
Anybus
CompactCom 40 EtherNet/IP
Doc.Id. HMSI-27-212
Rev. 1.5
Connecting Devices
HMS Industrial Networks
Mailing address: Box 4126, 300 04 Halmstad, Sweden
E-mail: info@hms-networks.com
Visiting address: Stationsgatan 37, Halmstad, Sweden
Web: www.anybus.com

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Anybus CompactCom 40 EtherNet/IP

Summary of Contents for Anybus CompactCom 40 EtherNet/IP

  • Page 1 Network Guide ® Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Rev. 1.5 Connecting Devices HMS Industrial Networks Mailing address: Box 4126, 300 04 Halmstad, Sweden E-mail: info@hms-networks.com Visiting address: Stationsgatan 37, Halmstad, Sweden Web: www.anybus.com...
  • Page 2 These intellectual property rights may include patents and pending patent applications in the US and other countries. Trademark Acknowledgements Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders. Warning: This is a class A product.

  • Page 3: Table Of Contents

    Related Documents..........................8 Document History ........................... 8 Conventions & Terminology........................9 Abbreviations............................9 Support ..............................9 Chapter 1 About the Anybus CompactCom 40 EtherNet/IP General..............................10 Features..............................10 Beacon Based DLR (Device Level Ring) ................... 11 Chapter 2 Basic Operation General Information..........................
  • Page 4 Chapter 3 FTP Server General Information..........................22 User Accounts ............................22 Session Example............................. 23 Chapter 4 Web Server General Information..........................24 Default Web Pages..........................24 Network Configuration ........................25 Ethernet statistics page ........................27 Server Configuration..........................29 General Information........................29 Index Page.............................
  • Page 5 Chapter 7 JSON General Information..........................51 JSON Objects ............................51 ADI.............................. 51 Module ............................54 Network............................55 Services ............................59 Hex Format Explained......................... 59 Example ..............................60 Chapter 8 CIP Objects General Information..........................61 Translation of Status Codes........................62 Identity Object (01h) ..........................63 Message Router (02h) ..........................
  • Page 6 Network Configuration Object (04h) ....................99 Socket Interface Object (07h) ......................109 SMTP Client Object (09h) ........................126 Anybus File System Interface Object (0Ah) ..................131 Examples ............................ 144 Network Ethernet Object (0Ch)......................148 Functional Safety Module Object (11h).................... 149 CIP Port Configuration Object (0Dh)....................
  • Page 7 Appendix D Secure HICP (Secure Host IP Configuration Protocol) General..............................192 Appendix E Technical Specification Front View ............................193 Protective Earth (PE) Requirements....................194 Power Supply ............................194 Environmental Specification ......................194 EMC Compliance..........................194 Appendix F Timing & Performance General Information..........................

  • Page 8: Preface

    Preface P. About This Document For more information, documentation etc., please visit the HMS website, ‘www.anybus.com’. P.1 Related Documents Document Author Anybus CompactCom 40 Software Design Guide Anybus CompactCom M40 Hardware Design Guide Anybus CompactCom B40 Hardware Design Guide CIP specification, Volumes 1 (CIP Common) and 2 (EtherNet/IP) ODVA P.2 Document History...

  • Page 9: Conventions & Terminology

    The terms ‘Anybus’ or ‘module’ refers to the Anybus CompactCom 40 module. • The terms ‘host’ or ‘host application’ refers to the device that hosts the Anybus module. • Hexadecimal values are either written in the format NNNNh or the format 0xNNNN, where NNNN is the hexadecimal value.

  • Page 10: About The Anybus Compactcom 40 Ethernet/Ip

    An- ybus module. This product conforms to all aspects of the host interface for Anybus CompactCom 40 modules defined in the Anybus CompactCom 40 Hardware and Software Design Guides, making it fully interchangeable with any other device following that specification.

  • Page 11: Beacon Based Dlr (Device Level Ring)

    The Anybus CompactCom 40 EtherNet/IP implements the DLR protocol, and it is enabled by default. The device is able to process and act on beacon frames sent by ring supervisors, and supports beacon rates down to 100 μs.

  • Page 12: Basic Operation

    2.1 General Information 2.1.1 Software Requirements Generally, no additional network support code needs to be written in order to support the Anybus Com- pactCom 40 EtherNet/IP. However, due to the nature of the EtherNet/IP networking system, certain restrictions must be taken into account: •...

  • Page 13: Device Customization

    (generic) EDS-file, which corresponds to the default settings in the module. However, due to the flexible nature of the Anybus CompactCom concept, it is possible to alter the behavior of the product in ways which invalidate the generic EDS-file. In such case, a custom EDS-file needs to be created, which in turn invalidates the default identity information and require re-certification of the product.

  • Page 14: Ethernet/Ip & Cip Implementation

    2.2.5 Socket Interface (Advanced Users Only) The built in socket interface allows additional protocols to be implemented on top of TCP/IP. See also... • “Socket Interface Object (07h)” on page 109 (Anybus Module Object) • “Message Segmentation” on page 189 Anybus CompactCom 40 EtherNet/IP Doc.Id.

  • Page 15: Modular Device Functionality

    2.2.6 Modular Device Functionality Modular devices consist of a backplane with a certain number of “slots”. The first slot is occupied by the “coupler” which contains the Anybus CompactCom module. All other slots may be empty or occu- pied by modules.

  • Page 16: Communication Settings

    Basic Operation 16 2.3 Communication Settings As with other Anybus CompactCom products, network related communication settings are grouped in the Network Configuration Object (04h). In this case, this includes... • TCP/IP settings These settings must be set properly in order for the module to be able to participate on the net- work.

  • Page 17: Communication Settings In Stand Alone Shift Register Mode

    2.3.1 Communication Settings in Stand Alone Shift Register Mode If the Anybus CompactCom 40 is used stand alone, there is no application from which to set the IP address. The IP address is instead set using the DIP1 switches (IP address byte 3) and the virtual attrib- utes (Ethernet Host object (F9h), attribute #17), that are written to memory during setup (IP address byte 0 - 2).

  • Page 18: Diagnostics

    The severity value of all pending events are combined (using logical OR) and copied to the correspond- ing bits in the ‘Status’-attribute of the Identity Object (CIP). See also... • “Identity Object (01h)” on page 63 (CIP) • “Diagnostic Object (02h)” on page 97 (Anybus Module Object) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 19: Network Data Exchange

    “Assembly Object (04h)” on page 67 (CIP) • “Connection Manager (06h)” on page 70 (CIP) 2.5.3 Translation of Data Types The Anybus data types are translated to CIP-standard and vice versa as follows: Anybus Data Type CIP Data Type Comments BOOL BOOL Each ADI element of this type occupies one byte.

  • Page 20: File System

    2.6 File System Category: Extended 2.6.1 Overview The Anybus CompactCom 40 EtherNet/IP has an in-built file system, that can be accessed from the application and from the network. Three directories are predefined: • VFS - The virtual file system that e.g. holds the web pages of the module.

  • Page 21: General Information

    2.6.2 General Information The built-in file system hosts 28 MByte of non volatile storage, which can be accessed by the HTTP and FTP servers, the email client, and the host application (through the Anybus File System Interface Object (0Ah)). The file system uses the following conventions: •...

  • Page 22: Ftp Server

    • Usernames must not exceed 16 characters in length. • Passwords must not exceed 16 characters in length. • All printable characters, except the separator ‘:’, are allowed in usernames and passwords. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 23: Session Example

    - Substitute <user> with the username - Substitute <password> with the password 3. 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.

  • Page 24: General Information

    File System Interface Object. See also... • “File System” on page 20 • “Anybus File System Interface Object (0Ah)” on page 131 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 25: Network Configuration

    The module needs to be reset for the TCP/IP and SMTP settings to take effect. The Ethernet Config- uration settings will take effect immediately. Available editable settings will be explained on the next page. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 26 SMTP Settings The module needs a reset before any changes take effect Name Description Server IP address or name Max 64 characters User Max 64 characters Password Max 64 characters Confirm password Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 27: Ethernet Statistics Page

    Frames for which reception of an interface fails due to an internal MAC sublayer receive error. MAC Transmit Errors Frames for which transmission fails due to an internal MAC sub- layer receive error. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 28 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. a. Not provided with current PHY interface. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 29: Server Configuration

    Note 1: Substitute <WebRoot> with the web root directory specified in ‘\http.cfg’. Note 2: If no index page is found, the module will default to the virtual index file (if enabled). See also... • “Default Web Pages” on page 24 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 30: Default Content Types

    UsernameN:PasswordN • Optionally, a login message can be specified by including the key [AuthName]. This message will be displayed by the web [AuthName] browser upon accessing the protected directory. (message goes here) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 31 The field ‘AuthType´ is used to identify the authentication scheme. Value Description Basic Web authentication method using plain- text passwords. Digest More secure method using challenge- response authentication. Used as default if no [Authtype] field is specified. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 32: E-Mail Client

    Sending a message based on a file in the file system is achieved using the ‘Send Email from File’-com- mand. For a description of the file format, see “Command Details: Send Email From File” on page 129. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212...

  • Page 33: 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 module encoun- ters such a command, it will execute it, and replace it with the result specified operation (if applicable).

  • Page 34: Command Functions

    Command functions executes commands and includes the result. General Syntax: <?--#exec cmd_argument='command'--> command-Command function, see below. Command Functions: Command Valid for Email Messages Page GetConfigItem() SetConfigItem() SsiOutput() DisplayRemoteUser ChangeLanguage() IncludeFile() SaveDataToFile() printf() scanf() Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 35: Getconfigitem()

    Key not found “Tag (key) not found” Example: The following SSI... <?--exec cmd_argument='GetConfigItem("\fruit.cnf", "Lemon")'--> ... in combination with the following file (‘\fruit.cnf’)... [Apple] Green [Lemon] Yellow [Banana] Blue ... returns the string Yellow. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 36: Setconfigitem()

    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 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 37 </BODY> </HTML> The resulting file (‘\food.txt’) may look somewhat as follows: [Name] Cliff Barnes [Food] Cheese [Drink] Beer Note: In order for this example to work, the HTML-file must be named ‘test.shtm’. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 38: Ssioutput()

    6.3.5 DisplayRemoteUser This command stores returns the user name on an authentication session. Note: 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 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 39: Changelanguage()

    <?--#exec cmd_argument='ChangeLanguage("lang")'--> <FORM action="test.shtm"> <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> Note: In order for this example to work, the HTML-file must be named ‘test.shtm’. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 40: Includefile()

    Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit... When viewed in a browser, the resulting page should look somewhat as follows: See also... • “Include File” on page 33 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 41: Savedatatofile()

    </FORM> </BODY> </HTML> The resulting file (‘\stuff.txt’) will contain the value specified for the form object called ‘Meat’. Note: In order for this example to work, the HTML-file must be named ‘test.shtm’. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 42: Printf()

    Server Side Include (SSI) 42 6.3.9 printf() This function returns a formatted string which may contain data from the Anybus module and/or ap- plication. 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 43 Specifies the max. no. of characters to be printed (no effect) • Modifier Modifier Character Meaning Argument is interpreted as SINT8 or UITN8 Argument is interpreted as SINT16 or UINT16 Argument is interpreted as SINT32 or UINT32 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 44: Scanf()

    Too much data for argument “Too much data ” ABCC Message error ABCCMessage error string ( “Errors” on page 49) Example: See also... - “ABCCMessage()” on page 46 - “Example (Set_Attribute):” on page 48 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 45 Data is read but ignored. It is not assigned to the corresponding argument. • 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 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 46: Argument Functions

    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 See also... • “Example (Get_Attribute):” on page 48 • “Example (Set_Attribute):” on page 48 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 47 ENUM value. It will then issue a ‘Get Enum String’-command to retrieve the actual enumeration string. The actual data type in the response will be STRING. FLOAT BITS8 BITS16 BITS32 OCTET BIT1 - 7 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 48 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 See also... - “scanf()” on page 44 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 49 “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” on page 50 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 50: Ssi Output Configuration

    The module will then select the correct output string based on the language settings. 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()” on page 38 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 51: Chapter 7 Json

    The JSON resources should be password protected. Add password protection by adding a file called web_accs.cfg in the root directory. See “Authorization” on page 30 for more information. Error If the module fails to parse or process a request the response will contain an error object with an Anybus error code: "error": 02 7.2 JSON Objects...
  • Page 52 Maximum value. May be NULL of no maximum value is present. access Number Bit 0: Read access Bit 1: Write access JSON object layout: "instance": "name": "Temperature threshold", "numelements": 1, "datatype": "min": "00", "max": "FF", "access": 0x03 nine more... Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 53 When <element> is not specified, <data> shall represent the entire array value. Option- ally, a callback may be passed to the request for JSONP output. Name Data Type Note result Number 0 = success POST adi/update.json - form data: inst=15&value=FF01 "result" : 0 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 54: Module

    Array of Number [high, low] milliseconds (ms) cpuload Number CPU load in % JSON object layout: "modulename": "ABCC M40", "serial": "ABCDEF00", "fwver": [ 1, 5, 0 ], "uptime": [ 5, 123456 ], "cpuload": Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 55: Network

    0: No link 1: Link speed Number 0: 10 Mbit 1: 100 Mbit duplex Number 0: Half 1: Full JSON object layout: "mac": "003011FF0201", "comm1": "link": "speed": "duplex": "comm2": "link": "speed": "duplex": Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 56 The values of "comm1" and "comm2" comes from the Network Configuration object (04h) instance 7 and instance 8. See “Instance Attributes (Instance #7, Ethernet Communication Settings 1)” on page 101 for more information. Name Data Type Note comm1 Number comm2 Number Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 57 IN: errors inunknown Number 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 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 58 Get network specific statistics: GET network/nwstats.json?get=<ID>. <ID> is an “identifier” value returned from the previous command (“eip”, for example) { "name": "Established Class1 Connections", "value": 0 }, { "name": "Established Class3 Connections", "value": 1 } Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 59: Services

    “info.json” on page 51). Examples: The value “5” encoded as a UINT16, with data format = 0 (little endian): 0500 The character array “ABC” encoded as CHAR[3] (data format is not relevant for CHAR): 414243 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 60: Example

    <script type="text/javascript" src="vfs/js/tmpl.js"></script> </head> <body> <div id="info-content"></div> <script type="text/x-tmpl" id="tmpl-info"> <b>From info.json</b><br> Module name: {%=o.modulename%}<br> CPU Load: {%=o.cpuload%}%<br> </script> <script type="text/javascript"> $.getJSON( "/module/info.json", null, function(data){ $("#info-content").html( tmpl("tmpl-info", data ) ); </script> </body> </html> Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 61: General Information

    “EtherNet/IP Host Object (F8h)” on page 161 and “Command Details: Process_CIP_- Object_Request” on page 166. Unconnected CIP routing is supported, which means that a message can be sent to a device without first setting up a connection. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 62: Translation Of Status Codes

    8.2 Translation of Status Codes If an error occurs when an object is requested from the application, an error code is returned. These Anybus CompactCom 40 error codes are translated to CIP status codes according to the table below. Anybus CompactCom 40 Error Code...

  • Page 63: Identity Object (01H)

    See also ..• “EtherNet/IP Host Object (F8h)” on page 161 • “CIP Identity Host Object (EDh)” on page 158 Supported Services Class: Get_Attribute_Single Get_Attributes_All Instance: Get_Attribute_Single Set_Attribute_Single Get_Attributes_All Reset Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 64 See “Device Status” on page 65 Serial Number UDINT Unique serial number (assigned by HMS) Product Name SHORT_STRING “Anybus CompactCom 40 EtherNet/IP (TM)” 11 Active language Set Struct of: Requests sent to this instance are forwarded to the Application USINT Object.
  • Page 65 There are two types of network reset requests on EtherNet/IP: • Type 0: ‘Power Cycling Reset’ This service emulates a power cycling of the module, and corresponds to Anybus reset type 0 (Power cycling). For further information, consult the general Anybus CompactCom 40 Software Design Guide.

  • Page 66: Message Router (02H)

    The Message Router Object provides a messaging connection point through which a client may address a service to any object class or instance residing in the physical module. In the Anybus CompactCom 40 module it is used internally to direct object requests. Supported Services...

  • Page 67: Assembly Object (04H)

    See also... • “Process Data” on page 19 • “EtherNet/IP Host Object (F8h)” on page 161 • Assembly Mapping Object (see Anybus CompactCom 40 Software Design Guide) Supported Services Class: Get_Attribute_Single Instance: Get_Attribute_Single Set_Attribute_Single...
  • Page 68 This instance is used as heartbeat for input-only extended connections, and does not carry any attributes. The state of connections made to this instance does not affect the state of the Anybus CompactCom 40 module, i.e. if the connection times out, the module does not switch to the Error state. The data size of the Heartbeat instance in the Forward_Open-request should be 0 bytes, however other values are also permitted.
  • Page 69 This instance is used as heartbeat for listen-only extended connections, and does not carry any attributes. The state of connections made to this instance does not affect the state of the Anybus CompactCom 40 module, i.e. if the connection times out, the module does not switch to the Error state. The data size of the Heartbeat instance in the Forward_Open-request should be 0 bytes, however other values are also permitted.

  • Page 70: Connection Manager (06H)

    Number of Forward Close service requests which were rejected for reasons other than bad format. Connection Timeouts UINT Total number of connection timeouts that have occurred in connec- tions controlled by this Connection Manager. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 71 - Supported trigger types: Cyclic, CoS (Change of State) - Supported priorities: Low, High, Scheduled, Urgent a. Requested packet interval b. Target, in this case the module c. Origin, in this case the master Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 72 CIP Objects 72 Connection Types • Exclusive-Owner connection This type of connection controls the outputs of the Anybus module and does not depend on oth- er connections. - Max. no. of Exclusive-Owner connections:  - Connection point O Assembly Object, instance 96h (Default) ...
  • Page 73 - No. of simultaneous Class 3 connections: - Supported RPI: 100 - 10000 ms - T->O Connection type: Point-to-point - O->T Connection type: Point-to-point - Supported trigger type: Application - Supported connection size: 1448 bytes - Supported priorities: Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 74: Parameter Object (0Fh)

    0005h (If the application supports configuration data, unless the configuration instance number has been changed using attribute 15 in the EtherNet/IP Host Object.) a. Consult the general Anybus CompactCom 40 Software Design Guide for further information. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 75 16 Scaling Offset 0000h 17 Multiplier Link UINT 18 Divisor Link UINT 19 Base Link UINT 20 Offset Link UINT 21 Decimal Precision USINT a. The Data Type is defined in attribute 5. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 76 11 Maximum value 12 Default value 13 Scaling Multiplier 14 Scaling Divisor 15 Scaling Base 16 Scaling Offset 17 Multiplier Link 18 Divisor Link 19 Base Link 20 Offset Link 21 Decimal Precision Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 77: Dlr Object (47H)

    This attribute holds the IP address (IPv4) and/or the Ethernet Mac Supervisor UDINT address of the active ring supervisor Address Array of: 6 USINTs 12 Capability Flags Get DWORD 82h (Beacon-based ring node, Flush_Table frame capable) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 78: Qos Object (48H)

    CIP transport class 1 messages with priority High Default: 43 DSCP Low USINT CIP transport class 1 messages with priority Low Default: 31 DSCP Explicit USINT CIP UCMM and CIP class 3 Default: 27 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 79: Base Energy Object (4Eh)

    The Anybus CompactCom 40 EtherNet/IP module supports one instance of the Base Energy Ob- ject. For instance, an electric power monitor may count metering pulse output transitions of a separate metering device.
  • Page 80 Depending on whether the instance reports consumed or generated energy, either attribute #7 or attribute #8 is required. b. This struct data type makes it possible to represent very large values, for more information please consult the CIP specification Volume 1 (CIP Common). Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 81: Power Management Object (53H)

    The Energy Control Object (F0h) has to be implemented for this object to gain access to the network. See also .. • Energy Control Object (F0h) (Anybus CompactCom 40 Software Design Guide) Supported Services Class: Get_Attribute_Single...
  • Page 82 REAL Power Level (Power in kW for this mode) BOOL Availability (Specifies whether this mode can be entered given the current device state) Sleeping State BOOL 0 (Sleeping state not supported) Support Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 83: Adi Object (A2H)

    Equals attribute #4 in the Application Data Object Number of instances UINT Equals attribute #3 in the Application Data Object a. Consult the general Anybus CompactCom 40 Software Design Guide for further information. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 84 CIP Objects 84 Instances Attributes Each instance corresponds to an instance within the Application Data Object (for more information, consult the general Anybus CompactCom 40 Software Design Guide). Extended Name Access Type Description Name SHORT_STRING Parameter name (Including length) ABCC Data type...

  • Page 85: Port Object (F4H)

    The object exists only if enabled in the EtherNet/IP Host Object (Instance Attribute #17). See also... • “EtherNet/IP Host Object (F8h)” on page 161 (Anybus Module Object) • “CIP Port Configuration Object (0Dh)” on page 153 (Host Application Object) Supported Services...
  • Page 86 Struct of: UINT (Min.) Min. node number on port UINT (Max.) Max. node number on port See also... • “CIP Port Configuration Object (0Dh)” on page 153 ( “Instance Attributes” on page 154) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 87: Tcp/Ip Interface Object (F5H)

    TCP/IP-related settings in one instance for each TCP/IP capable communications interface. See also... • “Communication Settings” on page 16 • “Network Configuration Object (04h)” on page 99 (Anybus Module Object) Supported Services Class services: Get_Attribute_All Get_Attribute_Single Instance services:...
  • Page 88 Default gateway UDINT (DNS1) Primary DNS UDINT (DNS2) Secondary DNS STRING (Domain) Default domain Host Name Get/Set STRING Host name of Anybus module TTL Value Get/Set USINT TTL value for EtherNet/IP multicast packets Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 89 “Conform- ance Test Guide” on page 12. d. This attribute exists if attribute #26 in the EtherNet/IP Host Object is implemented, see “Instance Attributes (Instance #1)” on page 162. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 90: Ethernet Link Object (F6H)

    Exactly one instance for each communications interface on the module is supported. Instances for internally accessible interfaces can also be supported. See also... • “Communication Settings” on page 16 • “Network Configuration Object (04h)” on page 99 (Anybus Module Object) Supported Services Class services: Get_Attribute_All Get_Attribute_Single Instance services:...
  • Page 91 Frame Too Long UDINT Frames received that exceed the maximum permitted frame size MAC Receive Errors UDINT Frames for which reception on an interface fails due to an internal MAC sublayer receive error Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 92 1 Reset is required in order for changes to have effect Local Hardware Fault Value:Meaning: 0 No local hardware fault detected 1 Local hardware fault detected 7-31 (reserved) Set to 0. a. Recommended default values are 10 Mbps, half duplex. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 93 This attribute controls the administrative setting of the interface state. Value Description (reserved) Enable the interface. Disable the interface. 3-255 (reserved) Interface Label Instance Value Port 1 Port 2 Internal Interface Type Instance Value Description Twisted-pair Twisted-pair Internal interface Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 94 1 for external interfaces ported. 1 = Indicates that the interface supports manual setting of speed/duplex via the Interface Control attribute (#6) 4 - 31 Reserved Shall be set to 0 Return 0 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 95: General Information

    Chapter 9 9. Anybus Module Objects 9.1 General Information This chapter specifies the Anybus Module Object implementation and how they correspond to the func- tionality in the Anybus CompactCom 40 EtherNet/IP. Standard Objects: • “Anybus Object (01h)” on page 96 •...

  • Page 96: Anybus Object (01H)

    9.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 Get_Enum_String Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information.)

  • Page 97: Diagnostic Object (02H)

    9.3 Diagnostic Object (02h) General Information Basic Object Description This object provides a standardised way of handling host application events & diagnostics, and is thor- oughly described in the general Anybus CompactCom 40 Software Design Guide. Supported Commands Object: Get_Attribute Create...

  • Page 98: Network Object (03H)

    9.4 Network Object (03h) Category Basic Object Description For more information regarding this object, consult the general Anybus CompactCom 40 Software De- sign Guide. 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.)

  • Page 99: Network Configuration Object (04H)

    If the settings in this object do not match the configuration used, the Module Status LED will flash red to indicate a minor error. The object is described in further detail in the Anybus CompactCom 40 Software Design Guide. See also...
  • Page 100 Array of UINT8 Holds the configured value, which will be written to attribute #5 after the module has been reset. Valid range: 0.0.0.0 - 255.255.255.255 (Default =0.0.0.0) a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 101 01h ‘10 HDX’ 10Mbit, half duplex 02h ‘10 FDX’ 10Mbit, full duplex 03h ‘100 HDX’ 100Mbit, half duplex 04h ‘100 FDX’ 100Mbit, full duplex a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 102 Array of UINT8 Holds the configured value, which will be written to attribute #5 after the module has been reset. Valid range: 0.0.0.0 - 255.255.255.255 (Default =0.0.0.0) a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 103 Array of UINT8 Holds the configured value, which will be written to attribute #5 after the module has been reset. Host name, 64 characters a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 104 Array of CHAR Holds the configured value, which will be written to attribute #5 after the module has been reset. SMTP server address, 64 characters a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 105 Array of CHAR Holds the configured value, which will be written to attribute #5 after the module has been reset. SMTP account password, 64 characters a. Multilingual, see “Multilingual Strings” on page 107. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 106 Holds the configured value, which will be written to attribute Value:Enum. String:Meaning: 00h ‘Auto’ (default) 01h ‘MDI’ 02h ‘MDIX’ Instance Attributes (Instances #18 and #19) These instances are reserved for future attributes. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 107 10 HDX 10 HDX 10 FDX 10 FDX 10 FDX 10 FDX 10 FDX 100 HDX 100 HDX 100 HDX 100 HDX 100 HDX 100 FDX 100FDX 100 FDX 100 FDX 100 FDX Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 108 Nom Domaine SMTP Server SMTP Server Servidor SMTP Server SMTP SMTP serveur SMTP User SMTP User Usuario SMTP Utente SMTP SMTP utilisa. SMTP Pswd SMTP PSWD Clave SMTP Password SMTP SMTP mt passe Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 109: Socket Interface Object (07H)

    Object Attributes (Instance #0) Name Access Data Type Value Name Array of CHAR ‘Socket interface’ Revision UINT8 Number of instances UINT16 Highest instance no. UINT16 11 Max. no. of instances Get UINT16 0008h Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 110 TCP Connect timeout in seconds (default = 75s) Timeout a. Must belong to group in order to get the loop backed message b. Resolution is 50ms, i.e. 50...99 = 50ms, 100...149 = 100ms, 199 = 150ms etc. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 111 01h SOCK_STREAM, BLOCKING (TCP) 02h SOCK_DGRAM, NON-BLOCKING (UDP) 03h SOCK_DGRAM, BLOCKING (UDP) • Response Details Field Contents Comments Data[0] Instance number (low) Instance number of the created socket. Data[1] Instance number (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 112 FIN-flag instead. • Command Details Field Contents Comments CmdExt[0] Instance number to delete (low) Instance number of socket that shall be deleted. CmdExt[1] Instance number to delete (high) • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 113 Set to 0 (zero) to request binding to any free port. CmdExt[1] Requested port number (high) • Response Details Field Contents Comments CmdExt[0] Bound port number (low) Actual port that the socket was bound to. CmdExt[1] Bound port number (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 114 2. Try to send any unsent data to the host. 3. Send shutdown with CmdExt[1] set to 01h. This will send FIN-flag to host shutting down the receive channel. 4. Delete the socket instance. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 115 Command Code.: Valid for: Instance Description This command puts a TCP socket in listening state. • Command Details Field Contents Comments CmdExt[0] (reserved) (set to zero) CmdExt[1] (reserved) • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 116 Host IP address byte 3 (low) Data[3] Host IP address byte 2 Data[4] Host IP address byte 1 Data[5] Host IP address byte 0 (high) Data[6] Host port number (low) Data[7] Host port number (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 117 Host IP address byte 2 Data[2] Host IP address byte 1 Data[3] Host IP address byte 0 (high) Data[4] Host port number (low) Data[5] Host port number (high) • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 118 Note: The data in the response may be segmented (see “Message Segmentation” on page 189). Field Contents Notes CmdExt[0] (reserved) (set to zero) CmdExt[1] Segmentation Control bits see “Response Segmentation” on page 191 Data[0...n] Received data Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 119 Host IP address byte 2 Data[0] Data[2] Host IP address byte 1 Data[3] Host IP address byte 0 (high) Data[4] Host port number (low) Data[5] Host port number (high) Data[6...n] Received data Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 120 Data[0...n] Data to send • Response Details Field Contents Notes CmdExt[0] (reserved) (ignore) CmdExt[1] Data[0] Number of sent bytes (low) Only valid in the last segment Data[1] Number of sent bytes (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 121 Data[6...n] Data to send • Response Details Field Contents Notes CmdExt[0] (reserved) (ignore) CmdExt[1] Data[0] Number of sent bytes (low) Only valid in the last segment Data[1] Number of sent bytes (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 122 CmdExt[1] Data[0] Group IP address byte 3 (low) Data[1] Group IP address byte 2 Data[2] Group IP address byte 1 Data[3] Group IP address byte 0 (high) • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 123 CmdExt[1] Data[0] Group IP address byte 3 (low) Data[1] Group IP address byte 2 Data[2] Group IP address byte 1 Data[3] Group IP address byte 0 (high) • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 124 (set to zero) CmdExt[1] Data[0] IP address byte 3 (low) IP address of the specified host Data[1] IP address byte 2 Data[2] IP address byte 1 Data[3] IP address byte 0 (high) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 125 Delete command, this error code will be returned to the blocking command. DNS name error Failed to resolve the host name (name error response from DNS server) DNS timeout Timeout when performing a DNS lookup DNS command Other DNS error failed Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 126: Smtp Client Object (09H)

    11 Max. no. of instances UINT16 0006h 12 Success count UINT16 Reflects the no. of successfully sent messages 13 Error count UINT16 Reflects the no. of messages that could not be delivered Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 127 This command creates an email instance. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] • Response Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0] Instance number low byte MsgData[1] high byte Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 128 Command Details: Delete Category Extended Details Command Code.: Valid for: Object Description This command deletes an email instance. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 129 [Message] actual email message • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Path + filename of message file • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 130 Object Specific Error Codes Error Codes Meaning SMTP server not found SMTP server not ready Authentication error SMTP socket error SSI scan error Unable to interpret email file Unspecified SMTP error (other) (reserved) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 131: Anybus File System Interface Object (0Ah)

    9.8 Anybus File System Interface Object (0Ah) Category Extended Object Description 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 provides the host application with access to the built-in file system of the module, e.g.
  • Page 132 Type Description Instance type UINT8 Value:Type: 00h Reserved 01h File instance 02h Directory instance File size UINT32 File size in bytes (zero for directories) Path Array of CHAR Path where instance operates Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 133 This command creates a file operation instance. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] • Response Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0] Instance number low byte MsgData[1] high byte Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 134 Comments CmdExt[0] Mode Value:Mode: 00h Read mode 01h Write mode 02h Append mode CmdExt[1] (reserved, set to zero) MsgData[0... n] Path + filename Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 135 This command permanently deletes a specified file from the file system. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Path + filename Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 136 Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Source path + filename Relative to current path, separated by NULL NULL Destination path + filename • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 137 Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Old path + filename Relative to current path, separated by NULL NULL New path + filename • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 138 Field Contents Comments CmdExt[0] Bytes no. of bytes to read CmdExt[1] (reserved, set to zero) • Response Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Data Data read from file Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 139 This command opens a directory. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] Data[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 140 This command permanently deletes an empty directory from the file system. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 141 MsgData[3] High byte, high word MsgData[4] Flags Bit:Meaning: 0 Entry is a directory 1 Entry is read-only 2 Entry is hidden 3 Entry is a system entry MsgData[5... n] Name of entry Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 142 This command changes the current directory/path for an instance. • Command Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 143 Failed to create directory Failed to delete directory Failed to change directory Copy operation failure (could not open source) Copy operation failure (could not open destination) Copy operation failure (write failed) Unable to rename file Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 144: Examples

    An imaginary folder structure will be used in the example, with the following files in the root folder: Root [reports] weld_current (txt) weld_formation (txt) weld_info (txt) configuration (html) down (jpg) index (html) left (jpg) navigation (js) right (jpg) status (html) test (txt) up (jpg) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 145 Keep reading until the Read command returns (Zero bytes returned) zero (0) or the desired content has been read. InstX.File Close( ) Close the file. Obj.Delete ( InstX ) Delete the instance. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 146 InstX.File Write( data ) Write the desired data to the file. Keep writing until the desired content has been Done written. InstX.File Close( ) Close the file. Obj.Delete ( InstX ) Delete the instance. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 147 Keep reading until all entries have been read. Done When there are no more entries, this is indicated by a zero data size in the response. InstX.Directory Close( ) Close the file. Obj.Delete ( InstX ) Delete the instance. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 148: Network Ethernet Object (0Ch)

    Number of instances UINT16 Highest instance no. UINT16 Instance Attributes (Instance #1) Extended Name Access Type Description MAC Address Array of UINT8 Current MAC address. See also “Ethernet Host Object (F9h)” on page 171) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

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

    9.10 Functional Safety Module Object (11h) Category Extended Object Description This object contains information provided by the Safety Module connected to the Anybus Compact- Com module. Please consult the manual for the Safety Module used, for values of the attributes below. Supported Commands Object:...
  • Page 150 Input data Array of UINT8 Current value of the Safety Module input data, i.e. data sent TO the network. Note: This data is unsafe, since it is provided by the Anybus CompactCom module. Error counters Struct of Error counters (each counter stops counting at FFFFh)
  • Page 151 Exception Information If Exception Code 09h is set in the Anybus object, there is an error regarding the functional safety mod- ule in the application. Exception information is available in instance attribute #10 according to this table: Value Exception Information...
  • Page 152 When the Safety Module has entered the safe state, for any reason, it must receive an error confirmation from the application, before it can leave the safe state. The application sends this command to the Anybus CompactCom module, that forwards it to the Safety Module. •...

  • Page 153: Cip Port Configuration Object (0Dh)

    IMPORTANT: Note that the module does not take over the host application responsibility for error control; the module will not verify that the data set by the host application is correct. Supported Commands Object: Get_Attribute Create Delete Instance: Get_Attribute Set_Attribute Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 154 See also... • “Port Object (F4h)” on page 85 ( “Instances Attributes (Instance #1)” on page 86) • “Port Object (F4h)” on page 85 ( “Instances Attributes (Instances #2... #8)” on page 86) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 155: General Information

    Standard Objects: • Application Object (FFh) - (see Anybus CompactCom 40 Software Design Guide) • Application Data Object (FEh) - (see Anybus CompactCom 40 Software Design Guide) • Energy Control Object (F0h) - (see Anybus CompactCom 40 Software Design Guide) •...

  • Page 156: Functional Safety Host Object (E8H)

    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. Supported Commands...
  • Page 157 • 1000000 (1000 kbit/s) • 1020000 (1020 kbit/s) If not implemented, the default value 1020 kbit/s will be used. If other values are set in this attribute the Anybus Compact- Com module will go into Exception state. IO Configuration Array of UINT8 Optional attribute.

  • Page 158: Cip Identity Host Object (Edh)

    See also... Product Code UINT16 - “Identity Object (01h)” on page 63 (CIP- Revision struct of: object) UINT8 Major UINT8 Minor Status UNIT16 Serial Number UINT32 Product Name Array of CHAR - Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 159 This service must be implemented by the application for all instances that exist in the CIP identity host object. If identity data is requested from the network the Anybus module will issue this command to the application. The application will then respond with a message containing a struct of all attributes in the requested instance.

  • Page 160: Sync Object (Eeh)

    10.1 Sync Object (EEh) Category Extended Object Description The Anybus CompactCom 40 EIP does not support CIP Sync. This object is only used to store the cycle time for the last established IO connection that consumes data. Supported Commands Object:...

  • Page 161: Ethernet/Ip Host Object (F8H)

    • “Assembly Object (04h)” on page 67 (CIP) • “Port Object (F4h)” on page 85 (CIP) • “CIP Port Configuration Object (0Dh)” on page 153 (Anybus Module Object) • Anybus CompactCom 40 Software Design Guide, “Error Codes” Supported Commands Object:...
  • Page 162 - “Identity Object (01h)” on page 63 (CIP- UINT8 Minor object) Serial Number UINT32 (set at production) Product Name Array of CHAR ‘Anybus CompactCom Note: Changing any of these attributes 40 EtherNet/IP(TM)’ requires a new Vendor ID. Extended Name Access Type...
  • Page 163 Ethernet Link Object Instance #2 22 Interface label Array of CHAR Internal The value of this attribute is used to change internal port the interface label for Ethernet Link Object Instance #3 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 164 If the module is configured to use EIP QuickConnect functionality, the EDS file has to be changed. As the EDS file is changed, the identity of the module has to be changed and the module will require certification, see “Conform- ance Test Guide” on page 12. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 165 7 - Producing Instance Number <---> <---> 12 - Read PD Instance List <---> 8 - Consuming Instance Number <---> <---> See also ... • Assembly Mapping Object (see Anybus CompactCom 40 Software Design Guide) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 166 IMPORTANT: When using this functionality, make sure to implement the common CIP Class Attribute (attribute #1, ‘Revision’) for all objects in the host application firmware. Failure to observe this will prevent the module from success- fully passing conformance tests. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 167 MsgData[0] Error code Anybus error code MsgData[1] Extended error code If the Anybus error code is set to FFh, the extended error code shall be translated as shown in “Extended Error Code” on page 168. MsgData[2 - 3] Index If the Extended error code is set to 02h (invalid configura- tion), this parameter points to the attribute that failed.
  • Page 168 3]. The extended error code shall only be used if the request originated from a Forward Open request, not for explicit set requests. See also... • “Connection Manager (06h)” on page 70 (CIP) • “Message Segmentation” on page 189 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 169 Additional Status Array Additional status, if applicable MsgData[n+1... m] Response Data Actual response data See also... • “Port Object (F4h)” on page 85 (CIP) • “CIP Port Configuration Object (0Dh)” on page 153 Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 170 Object Instance Description If the configuration data is requested from the network, the Anybus will issue this command to the ap- plication. The application shall send the stored configuration data in the response message. Segmentation is used since the telegram length on the host interface is limited. The maximum total amount of configuration data that will be accepted by the module is 458 bytes.

  • Page 171: Ethernet Host Object (F9H)

    If an attribute is not implemented, the module will use this value instead b. The module is pre-programmed with a valid Mac address. To use that address, do not implement this attribute. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 172 True Possible to reset the module from HICP False Not possible to reset the module from HICP IP configuration Struct of: The Anybus CompactCom writes the IP con- UINT32 figuration (IP address, Subnet mask, Gateway) (IP address) to this attribute whenever the configuration is UINT32 assigned or changed.
  • Page 173 If using an M40 module with two Ethernet ports, use state 01h (Disable) instead. If any of these attributes are implemented, the admin state attribute (#9) in the CIP Ethernet Link object (F6h) will not be available, see page 90. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 174: Application File System Interface Object (Eah)

    FTP server to the application. The application decides the available memory space. Instances are created and deleted dynamically during runtime. The object is structurally identical to the “Anybus File System Interface Object (0Ah)” on page 131. Supported Commands...
  • Page 175 Type Description Instance type UINT8 Value:Type: 00h Reserved 01h File instance 02h Directory instance File size UINT32 File size in bytes (zero for directories) Path Array of CHAR Path where instance operates Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 176 This command creates a file operation instance. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] • Response Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0] Instance number low byte MsgData[1] high byte Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 177 Field Contents Comments CmdExt[0] Mode Value:Mode: 00h Read mode 01h Write mode 02h Append mode CmdExt[1] (reserved, ignore) MsgData[0... n] Path + filename Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 178 This command permanently deletes a specified file from the file system. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Path + filename Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 179 Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Source path + filename Relative to current path, separated by NULL NULL Destination path + filename • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 180 Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Old path + filename Relative to current path, separated by NULL NULL New path + filename • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 181 Field Contents Comments CmdExt[0] Bytes no. of bytes to read CmdExt[1] (reserved, ignore) • Response Details Field Contents Comments CmdExt[0] (reserved, set to zero) CmdExt[1] MsgData[0... n] Data Data read from file Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 182 Description This command opens a directory. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] Data[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 183 This command permanently deletes an empty directory from the file system. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 184 MsgData[3] High byte, high word MsgData[4] Flags Bit:Meaning: 0 Entry is a directory 1 Entry is read-only 2 Entry is hidden 3 Entry is a system entry MsgData[5... n] Name of entry Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 185 This command changes the current directory/path for an instance. • Command Details Field Contents Comments CmdExt[0] (reserved, ignore) CmdExt[1] MsgData[0... n] Path + name of directory Relative to current path • Response Details (no data) Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 186 Failed to create directory Failed to delete directory Failed to change directory Copy operation failure (could not open source) Copy operation failure (could not open destination) Copy operation failure (write failed) Unable to rename file Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 187: Appendix A Categorization Of Functionality

    Appendix A A. Categorization of Functionality The objects, including attributes and services, of the Anybus CompactCom and the application are di- vided into two categories: basic and extended. A.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 188: Appendix B Implementation Details

    In the case of EtherNet/IP, this means that the SUP-bit is set when one or more CIP (Class 1 or Class 3) connections has been opened towards the module. B.2 Anybus Statemachine The table below describes how the Anybus Statemachine relates to the EtherNet/IP network. Anybus State Implementation...

  • Page 189: Appendix C Message Segmentation

    C.1 General Category: Extended The maximum message size supported by the Anybus CompactCom 40 is 1524 bytes. If the host appli- cation implements a data message size of 1524 bytes, a message will always fit into one segment. The host application can implement a shorter data message size (255 bytes for backwards compatibility with the 30-series).

  • Page 190: Command Segmentation

    If a segmentation error is detected during transmission, an error message is returned, and the cur- rent segmentation message is discarded. Note however that this only applies to the current seg- ment; previously transmitted segments are still valid. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 191: Response Segmentation

    For single segment responses (i.e. size less or equal to 255 bytes), both FS and LS are set. • The command initiator may at any time abort the operation by issuing a message with AB set. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

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

    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 193: Appendix E Technical Specification

    Green Link (100 Mbit/s) established Green, flickering Activity (100 Mbit/s) Yellow Link (10 Mbit/s) established Yellow, flickering Activity (10 Mbit/s) Ethernet Interface The Ethernet interface supports 10/100Mbit, full or half duplex operation. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

  • Page 194: Protective Earth (Pe) Requirements

    Hardware Design Guide. Power Consumption The Anybus CompactCom 40 EtherNet/IP is designed to fulfil the requirements of a Class B module. For more information about the power consumption classification used on the Anybus CompactCom 40 platform, consult the general Anybus CompactCom 40 Hardware Design Guide.

  • Page 195: Appendix F Timing & Performance

    The Anybus CompactCom 40 EtherNet/IP module is able to receive and handle the first application telegram (serial mode) F.2.2 NW_INIT Handling This test measures the time required by the Anybus CompactCom 40 EtherNet/IP module to perform the necessary actions in the NW_INIT-state. Parameter Conditions No.

  • Page 196: Event Based Wrmsg Busy Time

    Ethernet Ethernet Host NP40 Ethernet Host Application connector Trafo connector Network Read process data delay Anybus Ethernet Ethernet Ethernet Host NP40 Ethernet Host Application connector Trafo connector Network Write process data delay Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 197 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 SUCH DAMAGE. -------------------------------------------------------------------------------- Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...
  • Page 198 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. Anybus CompactCom 40 EtherNet/IP Doc.Id. HMSI-27-212 Doc.Rev. 1.5...

Table of Contents