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

Anybus CompactCom 40 Modbus-TCP Network Manual

Compactcom 40 series transparent ethernet
Hide thumbs Also See for CompactCom 40 Modbus-TCP:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Network Manual
®
Anybus
CompactCom
40
™
Modbus-TCP
®
Transparent Ethernet
NETWORK GUIDE
SCM-1202-022 1.1 ENGLISH

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Anybus CompactCom 40 Modbus-TCP

Summary of Contents for Anybus CompactCom 40 Modbus-TCP

  • Page 1 ® Anybus CompactCom ™ Modbus-TCP ® Transparent Ethernet NETWORK GUIDE SCM-1202-022 1.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 Modbus-TCP Transparent Ethernet Network 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 ....................7 About the Anybus CompactCom 40 Modbus-TCP ..........8 General.........................8 Features ........................8 Transparent Ethernet .....................8 Basic Operation......................10 Software Requirements ....................10 Device Customization....................11 Communication Settings....................12...
  • Page 4 Anybus Object (01h) ....................25 Diagnostic Object (02h) ....................27 Network Object (03h) ....................28 Network Configuration Object (04h)................29 Anybus File System Interface Object (0Ah) ..............38 Network Ethernet Object (0Ch) ..................39 Host Application Objects .................... 40 General Information .....................40 Modbus Host Object (FAh)....................41 Ethernet Host Object (F9h) ...................44...
  • Page 5 Table of Contents E Backward Compatibility ....................55 Initial Considerations....................55 Hardware Compatibility ....................56 General Software......................60 Network Specific — Modbus-TCP .................62 Copyright Notices ......................64 ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.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 Modbus-TCP. The document describes the features that are specific to Anybus CompactCom 40 Modbus-TCP. For general information regarding Anybus Compact- Com, consult the Anybus CompactCom 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: Trademark Information

    Preface 7 (70) Trademark Information Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 10: About The Anybus Compactcom 40 Modbus-Tcp

    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 11 The host application must include an Ethernet controller and a TCP/IP stack. Modbus- TCP protocol messages will be routed to the Anybus CompactCom internal software. Please note that the Transparent Ethernet functionality has to be enabled during startup by setting at- tribute #16 (instance #1) in the Anybus Object.

  • Page 12: Basic Operation

    Basic Operation Software Requirements No additional network support code needs to be written in order to support the Anybus Com- pactCom 40 Modbus-TCP, however due to the nature of the Modbus-TCP networking system, certain restrictions must be taken into account: •...

  • Page 13: Device Customization

    Modbus-TCP Implementation By default, a “Read Device Identification” request returns the following information: Vendor Name “HMS” Product Code: “Anybus CompactCom 40 Modbus-TCP” Major Minor Rev.: The current firmware version of the product Vendor URL: (no information returned by default) Product Name:...

  • Page 14: Communication Settings

    These settings must be set properly in order for the module to be able to participate on the network. IP settings must be synchronized between the Anybus CompactCom 40 and the host application. The module supports DHCP, which may be used to retrieve the IP settings from a DHCP-server automatically.
  • Page 15 Modbus does not feature a dedicated cyclic data channel in the same sense as many other net- works. In the Anybus CompactCom 40 implementation, process data can however still be ac- cessed from the network via dedicated entries in the Modbus register map.
  • Page 16 3344h * A 32-bit type occupies two Modbus * registers. 1122h BOOL[3] 0001h 3401h UINT16 1234h 0012h High byte from unmapped process data is set to zero. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 17: Modbus-Tcp Register Implementation

    0806h Diagnostic Event #6 Coils (0x) Range Contents Notes 0000h...2FFFh Read Process Data 3000h...7FFFh Reserved Discrete Inputs (1x) Range Contents Notes 0000h...2FFFh Write Process Data 3000h...07FFh Reserved ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 18: Modbus-Tcp Functions

    The data address received in the query is outside the initialized memory area 0x03 Illegal data value The data in the request is illegal See also... Modbus Host Object (FAh), p. 41 ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 19: Read Coils

    4x (Holding Registers) Details Mapped to Read- and Write Process Data, ADIs, and configuration registers. It is allowed to read parts of a larger Anybus CompactCom data type; it is also allowed to read multiple ADIs using a single request. ®...

  • Page 20: Read Input Registers

    Register Type: 0x (Coils) Details This function is mapped to the Read Process data, and the mapping is identical to that of the “Read Coils” function described above. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 21: Write Multiple Registers

    Identification strings are extracted from the host application via the Modbus Host Object (FAh), 41. If this object is not implemented, the default identification strings will be returned ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 22: Transparent Ethernet

    General Information Transparent Ethernet offers the possibility for a host application, that includes an IT implemen- tation, to let the Anybus CompactCom handle an industrial Ethernet protocol (in this case Mod- bus-TCP), without the need for extra Ethernet ports. Ethernet communication that is not related to Modbus-TCP is internally routed via the RMII in- terface to the Ethernet port and the TCP/IP stack of the host application.

  • Page 23: Enabling Transparent Ethernet

    Transparent Ethernet is not enabled at delivery. Attribute #16 (instance #1) in the Anybus Ob- ject (01h) has to be set to 0002h during setup. If this attribute is not changed, the Anybus Com- pactCom 40 Modbus-TCP will start up with full IT functionality instead of transparent Ethernet functionality.
  • Page 24 01-00-5E-40-F8-00 ... 01-00-5E-40-FB-FF • X3-XX-00-00-00-00 (X: any number 0-F) 6.5.3 UDP/TCP Ports The following ports may be used by the Anybus CompactCom, and must not be used by the host application: • UDP 67 & 68 (DHCP) • UDP 161 (SNMP) •...

  • Page 25: Firmware Upgrade

    “firmware” directory in the Anybus CompactCom (The Anybus CompactCom file system is accessed via the Anybus File System Object (0Ah).) The firmware will be updated upon the next reset of the Anybus CompactCom 40 Modbus-TCP. ®...

  • Page 26: Anybus Module Objects

    Anybus Module Objects 24 (70) Anybus Module Objects General Information This chapter specifies the Anybus Module Object implementation and how they correspond to the functionality in the Anybus CompactCom 40 Modbus-TCP. Standard Objects: • Anybus Object (01h), p. 25 •...

  • Page 27: Anybus Object (01H)

    Category Basic, extended 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 28 Anybus Module Objects 26 (70) Name Access Type Value Virtual attributes Get/Set Consult the general Anybus CompactCom 40 Software Design Guide for further information. Black list/White list Get/Set Network time UINT64 0 (Not supported) ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...

  • Page 29: Diagnostic Object (02H)

    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. See also ... • Diagnostics, p. 12 Supported Commands...

  • Page 30: Network Object (03H)

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

  • Page 31: 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 32 Anybus Module Objects 30 (70) 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 37) Data type UINT8 04h (= UINT8) Number of elements...
  • Page 33 Anybus Module Objects 31 (70) 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 37) Data type UINT8 08h (= ENUM) Number of elements...
  • Page 34 Anybus Module Objects 32 (70) 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 37) Data type...
  • Page 35 Anybus Module Objects 33 (70) 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 37) Data type UINT8...
  • Page 36 Anybus Module Objects 34 (70) Instance Attributes (Instances #13 - #15) (Reserved) Instance Attributes (Instance #16, MDI 1 Settings ) This instance holds the settings for MDI/MDIX 1. Changes have immediate effect. Name Access Data Type Description Name Array of “MDI 1”...
  • Page 37 Anybus Module Objects 35 (70) Instance Attributes (Instance #17, MDI 2 Settings ) This instance holds the settings for MDI/MDIX 2. Changes have immediate effect. Name Access Data Type Description Name Array of “MDI 2” CHAR Data type UINT8 08h (= ENUM)
  • Page 38 Anybus Module Objects 36 (70) Instance Attributes (Instance #21, Process active timeout) This instance holds the settings for the Process active timeout. Changes have immediate effect. See Commu- nication Settings, p. 12 for more information. Name Access Data Type Description...
  • Page 39 Anybus Module Objects 37 (70) Multilingual Strings The instance names and enumeration strings in this object are multilingual, and are translated based on the current language settings as follows: Instance English German Spanish Italian French IP address IP-Adresse Dirección IP...

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

  • Page 41: Network Ethernet Object (0Ch)

    Anybus Module Objects 39 (70) 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 42: Host Application Objects

    Standard Objects: • Application Object (FFh) - (see Anybus CompactCom 40 Software Design Guide) • Application Data Object (FEh) - (see Anybus CompactCom 40 Software Design Guide) Network Specific Objects: • Ethernet Host Object (F9h), p. 44 •...

  • Page 43: Modbus Host Object (Fah)

    CmdExt[0]”). In such case, the module will use its default value. If the module attempts to retrieve a value of an attribute not listed below, respond with an error message (06h, “Invalid CmdExt[0]”). See also ... • Anybus CompactCom 40 Software Design Guide, “Error Codes” Supported Commands Object: Get_Attribute Process-modbus-message...
  • Page 44 CHAR sponse to a “Read Device Identifica- tion” request. Attribute 2 and 3 will also Product Code Array of “Anybus CompactCom be used as identification on the web CHAR 40 Modbus-TCP” site and for SHICP (IPconfig). The Major Minor Revision Array of (firmware rev.)
  • Page 45 The response data size must not exceed 254 bytes, if more data is returned, no Modbus response message will be sent to the originator of the request. If the response contains no data, no Modbus response will be sent to the originator of the request. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide...

  • Page 46: 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 47 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 48 (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 49 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 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 50 This page intentionally left blank...

  • Page 51: 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 52: B Implementation Details

    This bit is set when in PROCESS_ACTIVE, and only if the Process active timeout value is greater than zero (0). Anybus State Machine The table below describes how the Anybus state machine relates to the Modbus-TCP network Anybus State Implementation...

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

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

  • Page 54: D Technical Specification

    Red, flashing Connection timeout. No Modbus message has been received within the configured “process active timeout” time A test sequence is performed on this LED during startup. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...
  • Page 55 Module Status LED LED State Description No power Green Normal operation Major fault (including Anybus exception), FATAL Red, flashing Minor fault Alternating red/green Firmware update from file system in progress A test sequence is performed on this LED during startup.

  • Page 56: Functional Earth (Fe) Requirements

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

  • Page 57: E Backward Compatibility

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

  • Page 58: Hardware Compatibility

    Anybus CompactCom M30/M40 E.2.2 Chip The chip (C30/C40) versions of the Anybus CompactCom differ completely when it comes to physical dimensions. There is no way to migrate a chip solution from the 30-series to the 40-series without a major hardware update.
  • Page 59 E.2.3 Brick The Anybus CompactCom B40-1 does not share dimensions with the Anybus CompactCom B30. The B40-1 is thus not suitable for migration. However HMS Industrial Networks AB has de- veloped a separate brick version in the 40-series, that can be used for migration. This product, B40-2, shares dimensions etc.
  • Page 60 See the following sections. Tx/OM3 This pin is Tx only in the 30-series. It is tri-stated during power up, and driven by the Anybus CompactCom UART after initialization. In the 40-series this pin is used as a fourth operating mode setting pin (OM3).
  • Page 61 In the 40-series, there is a possibility to set the GIP[0..1] and GOP[0..1] in high impedance state (tri-state) by using attribute #16 (GPIO configuration) in the Anybus object (01h). I.e. if it is not possible to change the host application hardware, this attribute can be configured for high impe- dance state of GIP and GOP before leaving NW_INIT state.

  • Page 62: General Software

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

  • Page 64: Network Specific - Modbus-Tcp

    Process data mapped BOOL arrays are not compressed to bit-fields on the network in the 40- series, but handled as a normal 8-bit datatype. To create bit-arrays in the 40-series, use the new datatypes BITx instead. ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 65 Modbus Host Object (FAh) Attribute 30-series 40-series Change/Action/Comment #2, Product Code Default: “Any- Default: “Anybus If the attribute is implemented in the host ap- bus-CC Modbus- CompactCom 40 plication, it overrides the default value and TCP (2-Port)” Modbus TCP” there is no difference between the 30-series and the 40-series.

  • Page 66: F Copyright Notices

    Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 67 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 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 68 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 69 1. The origin of this software must not be misrepresented; you must not ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide...
  • Page 70 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. L. Peter Deutsch ghost@aladdin.com ® ® Anybus CompactCom ™ 40 Modbus-TCP Transparent Ethernet Network Guide SCM-1202-022 1.1...
  • Page 71 This page intentionally left blank...
  • Page 72 last page © 2017 HMS Industrial Networks AB Box 4126 300 04 Halmstad, Sweden info@hms.se SCM-1202-022 1.1.4726 / 2017-07-11T09:25:39...

Table of Contents