1. Manuals
  2. Brands
  3. Anybus Manuals
  4. Control Unit
  5. CompactCom 40 Common Ethernet
  6. Design manual

Anybus CompactCom 40 Common Ethernet Design Manual

Communication module
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
®
Anybus
CompactCom
40
™
Common Ethernet
DESIGN GUIDE
HMSI-27–269 2.1 ENGLISH

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Anybus CompactCom 40 Common Ethernet

Summary of Contents for Anybus CompactCom 40 Common Ethernet

  • Page 1 ® Anybus CompactCom ™ Common Ethernet DESIGN GUIDE HMSI-27–269 2.1 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 Common Ethernet Design Guide...

  • Page 3: Table Of Contents

    About this document ......................5 Related Documents .......................5 Document History ......................5 Document Conventions ....................5 Document Specific Conventions..................6 Trademark Information ....................6 About the Anybus CompactCom 40 Common Ethernet ........7 General.........................7 Features ........................7 Basic Operation....................... 8 General Information .......................8 Software Requirements ....................8 Device Customization.....................8...
  • Page 4 Network Configuration Object (04h)................58 10.6 Socket Interface Object (07h)..................65 10.7 SMTP Client Object (09h) .....................82 10.8 Anybus File System Interface Object (0Ah) ..............87 10.9 Network Ethernet Object (0Ch) ..................88 11 Host Application Objects .................... 89 11.1 General Infomration .....................89 11.2 Application File System Interface Object (EAh)...............90...
  • Page 5 Table of Contents D Technical Specification ....................98 Front View ........................98 Functional Earth (FE) Requirements................99 Power Supply ......................99 Environmental Specification..................99 EMC Compliance......................99 E Copyright Notices .......................100 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 6 This page intentionally left blank...

  • Page 7: Preface

    About this document This document is intended to provide a good understanding of the functionality offered by the Anybus CompactCom 40 Common Ethernet. The document describes the features that are specific to Anybus CompactCom 40 Common Ethernet. For general information regarding Any- bus CompactCom 40, consult the Anybus CompactCom 40 design guides.

  • Page 8: Document Specific 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: About The Anybus Compactcom 40 Common Ethernet

    Anybus 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 10: Basic Operation

    Firmware Download / Firmware Upgrade, p. Software Requirements Generally, no additional network support code needs to be written in order to support the Any- bus CompactCom 40 Common Ethernet. However, certain restrictions must be taken into account. • Certain functionality in the module requires that the command Get_Instance_Number_By_ Order (Application Data Object, FEh) is implemented in the host application.

  • Page 11: Communication Settings

    Socket Interface Object (07h), p. 65 • Message Segmentation, p. 80 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 network.
  • Page 12 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 attributes (Ethernet Host object (F9h), attribute #17), that are written to memory during setup (IP address byte 0 - 2).

  • Page 13: Diagnostics

    3.7.1 Overview The Anybus CompactCom 40 Common Ethernet has an in-built file system, that can be ac- cessed 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. The virtual file system is enabled by default in the Anybus File System Interface Object (0Ah).
  • Page 14 File system File 1 File 2 File 1 File 2 Application Application File system The Anybus CompactCom accesses the application file system through the Application File System Interface Object. File A1 File A2 Directory A1 File A1:1 Firmware File A1:2 Fig.

  • Page 15: General Information

    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 Sys- tem Interface Object (0Ah)). The 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 16: Firmware Download / Firmware Upgrade

    Using Firmware Manager II This tool is available without cost from the HMS Industrial Networks AB support website, www. anybus.com/support. It can be used to download new firmware or firmware upgrades for all Anybus CompactCom modules. Fig. 3 Using the tool, perform the following steps to download new firmware to the module.

  • Page 17: Via The Internal File System

    /firmware directory. See also... • FTP Server, p. 16 • File System, p. 11 • Application File System Interface Object (EAh), p. 90 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 18: Ftp Server

    .UserN:PasswordN 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 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 19: 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. 4 ®...

  • Page 20: Web Server

    File System Interface Object. See also... • File System, p. 11 • Anybus File System Interface Object (0Ah), p. 87 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide...
  • Page 21 Network Configuration Object. Fig. 5 Fig. 6 The module needs to be reset for the TCP/IP and SMTP settings to take effect. The Ethernet Configuration settings will take effect immediately. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 22 In Unknown Protos: Received packets with unsupported protocol type. Out Octets: Sent bytes. Out Ucast packets: Sent unicast packets. Out NUcast packets: Sent non unicast packets (broadcast and multicast). ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 23: Server Configuration

    Configures the web server name included in the HTTP header of the responses from the module. [ServerName] Web Root Directory The web server cannot access files outside this directory. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 24 Content types can be added or redefined by adding them to the server configuration file. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 25 The field “AuthType” is used to identify the authentication scheme. Description Value Basic Web authentication method using plaintext passwords. Digest More secure method using challenge-response authentication. Used as default if no [Auth- type] field is specified. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 26: 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 Common Ethernet Design Guide...

  • Page 27: 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 28 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 29 Server Side Include (SSI) 27 (104) 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 30 Default Output 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 31 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 32 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 33 <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> In order for this example to work, the HTML file must be named “test.shtm”. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 34 <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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 35 Server Side Include (SSI) 33 (104) When viewed in a browser, the resulting page should look somewhat as follows: Fig. 7 See also... • Include File, p. 25 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 36 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 37 </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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 38 36 (104) 8.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 39 Specifies the max. no. of characters to be printed (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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 40 “Too much data” ABCCMessage error ABCCMessage error string (Errors, p. Example See also... ABCCMessage(), p. 40 Example (Set_Attribute):, p. 42 Formatting Tags Formatting tags are written as follows: %[*][Width][Modifier]type ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 41 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 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 42: 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 43 Failure to observe this may cause loss of data or other undesired side effects. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 44 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 45 “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. 44 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 46: 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. 30 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 47: Json

    1 = Big endian (Affects value, min and max representations) numadis Number Total number of ADIs webversion Number Web/JSON API version JSON object layout: "dataformat": 0, "numadis": 123, "webversion": 1 ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 48 Maximum value. May be NULL of no maximum value is present. access Number Bit 0: Read accessBit 1: Write access JSON object layout: "instance": "name": "Temperature threshold", "numelements": 1, "datatype": "min": "00", "max": "FF", "access": 0x03 nine more... ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 49 Optionally, 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 50 [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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 51 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 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 52 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 ethconf.json GET network/ethconf.json Name Data Type Note comm1 Number comm2 Number ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 53 Number Frames received that exceed the maximum permitted frame size tooshort Number Frames received that are shorter than the lowest permit- ted frame size ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 54 { "name": "Established Class3 Connections", "value": 1 } 9.2.4 Services smtp.json GET services/smtp.json. Password is not returned when retrieving the settings. Name Data Type Note server String user String ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 55: 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 56: Anybus Module Objects

    Anybus Module Objects 54 (104) Anybus Module Objects 10.1 General Information This chapter specifies the Anybus Module Object implementation. Standard Objects: • Anybus Object (01h), p. 55 • Diagnostic Object (02h), p. 56 • Network Object (03h), p. 57 •...

  • Page 57: 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. Instance attribute #16 has to be set to 0002h during SETUP state to enable Transparent Ethernet functionality.

  • Page 58: Diagnostic Object (02H)

    10.3 Diagnostic Object (02h) Category Basic 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 59: Network Object (03H)

    Anybus Module Objects 57 (104) 10.4 Network Object (03h) Category Basic Object Description For more information regarding this object, consult the general Anybus CompactCom 40 Software Design 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...

  • Page 60: Network Configuration Object (04H)

    If the settings in this object do not match the configuration used, the Module Status LED will flash red to indi- cate a minor error. The object is described in further detail in the Anybus CompactCom 40 Software Design Guide. See also...
  • Page 61 Anybus Module Objects 59 (104) Instance Attributes (Instance #4, Subnet Mask) Value is used after module reset. Name Access Data Type Description Name Array of “Subnet mask” CHAR (Multilingual, see page 64) Data type UINT8 04h (= UINT8) Number of elements...
  • Page 62 Anybus Module Objects 60 (104) Instance Attributes (Instance #7 Ethernet Communication Settings 1) Changes have immediate effect. Name Access Data Type Description Name Array of “Comm 1” CHAR (Multilingual, see page 64) Data type UINT8 08h (= ENUM) Number of elements...
  • Page 63 Anybus Module Objects 61 (104) 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 64) Data type...
  • Page 64 Anybus Module Objects 62 (104) 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 64) Data type UINT8...
  • Page 65 Anybus Module Objects 63 (104) 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 64)
  • Page 66 Anybus Module Objects 64 (104) Instance Attributes (Instances #18 and #19) These instances are reserved for future attributes. Multilingual Strings The instance names and enumeration strings in this object are multilingual, and are translated based on the current language settings as follows:...

  • Page 67: Socket Interface Object (07H)

    Anybus Module Objects 65 (104) 10.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 68 Anybus Module Objects 66 (104) 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 69 Anybus Module Objects 67 (104) 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 70 Anybus Module Objects 68 (104) 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 71 Anybus Module Objects 69 (104) 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 72 Anybus Module Objects 70 (104) 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 73 Anybus Module Objects 71 (104) 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 74 Anybus Module Objects 72 (104) 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 75 Anybus Module Objects 73 (104) 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 76 Anybus Module Objects 74 (104) 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 77 Anybus Module Objects 75 (104) 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 78 Anybus Module Objects 76 (104) 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 79 Anybus Module Objects 77 (104) 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 80 Anybus Module Objects 78 (104) 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 81 Anybus Module Objects 79 (104) 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 82 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 83 Anybus Module Objects 81 (104) 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 84: Smtp Client Object (09H)

    Anybus Module Objects 82 (104) 10.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 85: Cmdext

    Anybus Module Objects 83 (104) 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 86: (No Data)

    Anybus Module Objects 84 (104) 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 87 Anybus Module Objects 85 (104) 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 88: Command Code

    Anybus Module Objects 86 (104) 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 89: Anybus File System Interface Object (0Ah)

    This provides the host application with access to the built-in file system of the module, e.g. when application specific web pages are to be installed. Instances are created and deleted dynamically during runtime. This object is thoroughly described in Anybus CompactCom 40 Software Design Guide. ® Anybus CompactCom ™...

  • Page 90: Network Ethernet Object (0Ch)

    Anybus Module Objects 88 (104) 10.9 Network Ethernet Object (0Ch) Category Extended Object Description This object provides Ethernet-specific information to the application. Supported Commands Object: Get_Attribute Instance: Get_Attribute Object Attributes (Instance #0) Name Access Data Type Value Name Array of “Network Ethernet”...

  • Page 91: Common Ethernet Design Guide Hmsi-27-269

    Standard Objects: • Application Object (see Anybus CompactCom 40 Software Design Guide) • Application Data Object (see Anybus CompactCom 40 Software Design Guide) Network Specific Objects • Application File System Interface Object (EAh), p. 90 • Ethernet Host Object (F9h), p. 91 ®...

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

    This allows the user to download software through the FTP server to the application. The application decides the available memory space. This object is thoroughly described in Anybus CompactCom 40 Software Design Guide. ®...

  • Page 93: 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 94 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 95 (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 96 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 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 97: 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 98: B Implementation Details

    96 (104) Implementation Details SUP-Bit Definition Not used. Anybus State Machine The table below describes how the Anybus Statemachine relates to the EtherNet/IP network Anybus State Implementation Comment WAIT_PROCESS The module stays in this state as long as it is running.

  • Page 99: C Secure Hicp (Secure Host Ip Configuration Protocol)

    Anybus IPconfig utility for changing settings, e.g. IP address, Subnet mask, and enable/dis- able 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 100: D Technical Specification

    Link (10 Mbit/s) established Yellow, flickering Activity (10 Mbit/s) D.1.5 Fatal Error If both the Network Status LED and the Module Status LED are red, a fatal error has occurred. ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...

  • Page 101: D.2 Functional Earth (Fe) Requirements

    Power Supply D.3.1 Supply Voltage The Anybus CompactCom 40 Common Ethernet requires a regulated 3.3 V power source as specified in the general Anybus CompactCom 40 Hardware Design Guide. D.3.2 Power Consumption TheAnybus CompactCom 40 Common Ethernet is designed to fulfil the requirements of a Class B module.

  • Page 102: E Copyright Notices

    Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: ® Anybus CompactCom ™ 40 Common Ethernet Design Guide...
  • Page 103 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ftpd.c - This file is part of the FTP daemon for lwIP -------------------------------------------------------------------------------- ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 104 PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE- MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, ® Anybus CompactCom ™ 40 Common Ethernet Design Guide...
  • Page 105 Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. This notice may not be removed or altered from any source distribution. L. Peter Deutsch ghost@aladdin.com ® Anybus CompactCom ™ 40 Common Ethernet Design Guide HMSI-27–269 2.1...
  • Page 106 last page © 2017 HMS Industrial Networks AB Box 4126 300 04 Halmstad, Sweden info@hms.se HMSI-27–269 2.1.4666 / 2017-07-10T11:06:42...

Table of Contents