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

Anybus CompactCom 40 Network Manual

Hide thumbs Also See for CompactCom 40:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Network Manual
®
Anybus
CompactCom
40
™
PROFIBUS DP-V0/DP-V1
NETWORK GUIDE
HMSI-27-210-EN 2.3 ENGLISH

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Anybus CompactCom 40

Summary of Contents for Anybus CompactCom 40

  • Page 1 ® Anybus CompactCom ™ PROFIBUS DP-V0/DP-V1 NETWORK GUIDE HMSI-27-210-EN 2.3 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 PROFIBUS DP-V0/DP-V1 Network Guide...

  • Page 3: Table Of Contents

    Related Documents .......................5 Document History ......................5 Document Conventions ....................5 Document Specific Conventions..................6 Abbreviations ........................6 Trademark Information ....................6 About the Anybus CompactCom 40 PROFIBUS DPV1/DPV0 ......8 General.........................8 Features ........................8 Fieldbus Conformance and Certification..............9 Fieldbus Conformance Notes..................9 Certification ........................9 Basic Operation......................10 General Information .....................10...
  • Page 4 B Implementation Details....................42 SUP-Bit Definition ......................42 Anybus State Machine ....................42 Watchdog Behavior (Application Stopped) ..............42 C Error Handling........................ 43 Translation of Anybus Error Codes ................43 Other Errors ........................43 D GSD File Customization ....................44 General........................44 Device Identification .....................44 Supported Hardware Features ..................45 Supported DP Features....................46...
  • Page 5 Table of Contents Timing & Performance ....................60 General Information .....................60 Internal Timing......................60 G Backward Compatibility ....................62 Initial Considerations....................62 Hardware Compatibility ....................62 General Software......................68 Network Specific — PROFIBUS ..................70 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 6 This page intentionally left blank...

  • Page 7: Preface

    This document is intended to provide a good understanding of the functionality offered by the Anybus CompactCom 40 PROFIBUS DPV1/DPV0. The document describes the features that are specific to Anybus CompactCom 40 PROFIBUS DPV1/DPV0. For general information re- garding Anybus CompactCom, 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 Preface 7 (72) All other trademarks are the property of their respective holders. ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 10: About The Anybus Compactcom 40 Profibus Dpv1/Dpv0

    Any device that supports this standard can take advantage of the features provided by the module, allowing seamless network integration regardless of network type. 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: Fieldbus Conformance And Certification

    Modify the PROFIBUS DP-V1 GSD file so that it corresponds to the changes made above. In addition, all modules used in the application must be defined in the GSD file. For more infor- mation, see Configuration Data Handling, p. ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 12: Basic Operation

    General Information 4.1.1 Software Requirements No additional network support code needs to be written in order to support the Anybus Com- pactCom 40 PROFIBUS DPV1/DPV0, however certain restrictions must be taken into account: • Due to the nature of the PROFIBUS networking system, at least one ADI must be mapped to Process Data.

  • Page 13: Communication Settings

    9.6 kbps • 19.2 kbps • 45.45 kbps • 93.75 kbps • 187.5 kbps • 500 kbps • 1.5 Mbps • 3 Mbps • 6 Mbps • 12 Mbps ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 14: Device Identity

    I/O device. The I&M information is accessed by the master by means of the Call State Machine using DP-V1 read/write services. By default, Anybus module supports I&M records 0... 4 for slot #0 (which is the device itself). Optionally, the host application can implement the commands Get_IM_Record and Set_IM_Re- cord’-commands...

  • Page 15: Data Exchange

    Due to technical reasons, it is generally not recommended to use ADI numbers 1... 255 since this may cause trouble with certain PROFIBUS configuration tools. See also.. • GSD File Customization, p. 44 • Implementation Details, p. 42 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 16: Parameterization Data Handling

    The maximum amount of User Parameterization Data that can be handled by the module is 234 bytes. See also... • GSD File Customization, p. 44 • PROFIBUS DP-V1 Object (FDh), p. 36(Attribute #2, Parameterization Data) • Parameterization Related Keywords, p. 53 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 17: Configuration Data Handling

    4.6.1 General Information The Anybus module determines its Expected Configuration Data based on the ADI mapping process. Alternatively, it can be specified by the host application by implementing the Get serv- ice of the attribute configuration Data (#3) in the PROFIBUS DP-V1 Object (FDh), p.
  • Page 18 If the application discards the remap command, the module will signal configuration fault on the network. For backward compatibility with the Anybus CompactCom 30 series, it is also possible for the module to approve the configuration if the following criteria are met: •...
  • Page 19 Preferably, choose to reject the Actual Configuration Data and adapt to it by restarting the Anybus module and then revise the Process Data map and/or the Expected Configuration Data. Also note that the new configuration must exist in the GSD file of the product.

  • Page 20: Set Slave Address

    Fac- tory Default-reset on the Network Configuration Object (consult the general Anybus Compact- Com 40 Software Design Guide for more information). This behavior is mandatory for the application to pass PROFIBUS network certification.
  • Page 21 0000... FFFFh Number of the ADI which shall be read ADI (low) 11...n Data (actual data) Data returned from the host application The max value of n = 244 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 22 (reserved, set to zero) Subindex (high) Subindex 0001h, used when reading Subindex (low) ADI number ADI (high) 0000... FFFFh Number of the ADI which shall be read ADI (low) ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

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

    IM Order ID “ABCC 40-DPV1” IM Serial Number (unique serial number, set during manufacturing) IM Hardware Revision (Anybus hardware revision ID, set during manufacturing) IM Software Revision (Anybus software revision, set during manufacturing) IM Revision Counter (Revision counter) IM Profile ID...
  • Page 24 Controller/Supervisor.) I&M4 Signature (Data of this field can only be accessed from the network by the IO bytes Controller/Supervisor.) See also... • PROFIBUS DP-V1 Object (FDh), p. 36 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 25: Diagnostics

    The application defines whether to use transparent diagnostics using the DP-V0 diagnostic ob- ject (10h), or to use the Anybus diagnostic object (02h). It is not possible to change type of diag- nostics at runtime, thus it has to be defined in the indesign phase.

  • Page 26: Anybus Module Objects

    Anybus Module Objects 24 (72) Anybus Module Objects General Information This chapter specifies the Anybus Module Object implementation and how the objects corre- spond to the functionality in the Anybus CompactCom 40 PROFIBUS DPV1/DPV0. Standard Objects: • Anybus Object (01h), p. 25 •...

  • Page 27: Anybus Object (01H)

    Anybus Module Objects 25 (72) 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 28: Diagnostic Object (02H)

    This object provides a standardised way of handling host application events, alarms, and diagnostics, and is thoroughly described in the general Anybus CompactCom 40 Software Design Guide. In the case of PROFI- BUS, each instance created in this object adds one Status PDU to the Extended Diagnostics.
  • Page 29 This parameter indicates the severity level of the event, and describes the kind of PROFIBUS diagnostics generated for the different levels. It also indicates whether extended diagnostics are used by the instance. For more information, see the Anybus CompactCom 40 Software Design Guide. Severity Levels...

  • Page 30: Network Object (03H)

    Object Description This object contains network specific data for the module. It also controls the mapping of ADIs to the process data part of the telegrams. For more information, consult the general Anybus CompactCom 40 Software De- sign Guide. The order in which ADIs are mapped to Process Data is significant and must be replicated in the PROFIBUS master when setting up the network communication.
  • Page 31 Anybus module has shifted to the EXCEPTION state. Exception Information This attribute holds additional information when the Anybus module shifts to the EXCEPTION state. Value No information. The ADI mapping resulted in too much configuration data.

  • Page 32: Network Configuration Object (04H)

    Set_Attribute Get_Enum_String Object Attributes (Instance #0) (Consult the general Anybus CompactCom 40 Software Design Guide for further information). Instance Attributes (Instance #1) Basic The module must be assigned a unique node address (a.k.a. device address) in order to be able to communi- cate on the PROFIBUS network.
  • Page 33 Anybus Module Objects 31 (72) Multilingual String The instance name in this object is multilingual, and is translated based on the current language settings as follows: Instance English German Spanish Italian French IP address IP-Adresse Dirección IP Indirizzo IP Adresse IP ®...

  • Page 34: Profibus Dp-V0 Diagnostic Object (10H)

    Anybus Module Objects 32 (72) PROFIBUS DP-V0 Diagnostic Object (10h) Object Description Implementing this object makes it possible to create transparent diagnostic data, instead of using the stand- ard diagnostic data. For the diagnostic functionality to work correctly during the connection phase with the master, the application must write zero bytes to attribute #1 in instance #1 before setting setup complete.
  • Page 35 Anybus Module Objects 33 (72) Object Specific Error Codes Number Name In Response to Command Diagnostic Object (02h) in Set_Attribute Invalid extended diagnostic Set_Attribute data flag value ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 36: Host Application Objects

    PROFIBUS implementation. Standard Objects: • Application Object (see Anybus CompactCom 40 Software Design Guide) • Application Data Object (see Anybus CompactCom 40 Software Design Guide) • Modular Device Object (ECh), p. 35 Network Specific Object: •...

  • Page 37: Modular Device Object (Ech)

    This object is used to describe a modular device. Modular devices consist of a backplane with a certain num- ber of “slots”. The first slot is occupied by the “coupler” which contains the Anybus CompactCom module. All other slots may be empty or occupied by modules.

  • Page 38: Profibus Dp-V1 Object (Fdh)

    Technical Specification, p. 57 • Support for DP-V1 and DP-V0, p. 10 • GSD File Customization, p. 44 • Guideline Information & Maintenance functions • Anybus CompactCom Software Design Guide, “Error Codes” Supported Commands Object: Get_Attribute Get_IM_Record Set_IM_Record Instance: Get_Attribute...
  • Page 39 Serial number, up to 16 characters. If not implemented, the serial number from the Application Object (FFh), at- tribute #3 will be used. If this attribute is also missing, the Anybus CompactCom defaults to its production as- signed serial number. Hardware Revision UINT16 Hardware revision of the device.
  • Page 40 “T” Test device UINT8 Major version Functional enhancement Range: 0,,, 255 UINT8 Minor version Bug fix Range: 0,,, 255 UINT8 Internal change No impact on function Range: 0,,, 255 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 41 Slot number (0... 254) Msg_Data[1... 3] (reserved, ignore) • Response Details (Success) Field Comments Msg_Data[0... 9] I&M user specific header Msg_Data[10... 63] I&M Record; I&M parameters associated with the request ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 42 Slot number (0... 254) Msg_Data[1... 3] (reserved, ignore) Msg_Data[4... 13] I&M user specific header. Msg_Data[14... 67] I&M Record; I&M parameters associated with the request • Response Details (Success) (no data) ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 43: 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 44: B Implementation Details

    Parameterization and Configuration Data has been accepted (i.e. MS0 connection established) • An MS2 connection is open Anybus State Machine The table below describes how the Anybus state machine relates to the PROFIBUS network Anybus State Description WAIT_PROCESS No MS0 connection...

  • Page 45: C Error Handling

    43 (72) Error Handling Translation of Anybus Error Codes When a DP-V1 request is received from the network, the module translates this request into an object request to the application data object. When such requests are rejected by the host appli- cation, the error code in the response is translated to DP-V1 standard as described in the table below.

  • Page 46: Dgsd File Customization

    HMS provides an example GSD 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 a way that invalidates the example GSD file. In such case, a cus- tom GSD file must be created, and fieldbus recertification is necessary.

  • Page 47: Supported Hardware Features

    Description <vendor> Vendor name as text (e.g. “HMS Industrial Networks”) <product> Product name as text (e.g. “Anybus CompactCom DPV1”) <prod_rev> Product revision (major.minor) (e.g. “1.01”) <ident_no> PNO Ident Number in HEX. Written as 0xNNNN, where NNNN is the hexadecimal value.

  • Page 48: Supported Dp Features

    9.6_supp = 1 19.2_supp = 1 45.45_supp = 1 93.75_supp = 1 187.5_supp = 1 500_supp = 1 1.5M_supp = 1 3M_supp = 1 6M_supp = 1 12M_supp = 1 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 49: Maximum Responder Time For Supported Baud Rates

    Modular_Station = 1 Max_Module = <module> Max_Input_Len = <input> Max_Output_Len = <output> Max_Data_Len = <total> Modul_Offset = 1 Basic Setting Unit Description <module> bytes <input> bytes <output> bytes <total> bytes ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 50: Definition Of Modules

    01 = One byte I/O data specification for input follows 10 = One byte I/O data specification for output follows 11 = Two bytes I/O data specification follows (not valid) ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 51 1 = Whole length (The module will set this bit to 1 if the module only contains one ADI or only one ADI input and output) Vendor Specific Data Byte 0: Bit 7: More cfg follows ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 52 00 = No I/O data specification follows 01 = One byte I/O data specification for input follows 10 = One byte I/O data specification for output follows 11 = Two bytes I/O data specification follows ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 53 Bit 7: Byte 1 - 13: ADI index in the module, i.e. which ADIs within a slot that are mapped to this module (1 byte for each ADI, outputs first) ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...
  • Page 54 [0xC6 0x41 0xC0 0x02 0x04 0x00 0x09 0x0A 0x13] (Slot 4 - ADI 210, 211, 220) GSD Entries Modular_Station = 1 Modul_Offset DPV1_Data_Types = 0 Chk_Cfg_Mode Max_Module = 40 Number of slots in Modular object ; Definition of modules ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 55: Parameterization Related Keywords

    Actual User Parameterization Data as hexadecimal values. The first three bytes are fixed and should be set to C0h, 00h, 00h. D.10.3 Related Information • PROFIBUS DP-V1 Object (FDh), p. 36 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 56: Diagnostic Related Keywords

    Basic Setting Description <supp> 1: I&M supported D.12.2 Related Information • PROFIBUS DP-V1 Object (FDh), p. 36 • Device Identity, p. 12 • Network Configuration Object (04h), p. 30 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 57: Status Diagnostics Messages

    These settings specify the bit range to associated with <val> and <text>. <end> <val> Value <text> String associated with the value of <val> D.13.3 Related Information • Diagnostic Object (02h), p. 26 • Diagnostics, p. 23 ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 58: Dp-V1 Related Keywords

    GSD File Entries ; Alarm Extra_Alarm_SAP_supp ; Do not change Alarm_Sequence_Mode_Count = 32 ; Max. allowed value Alarm_Type_Mode_supp Diagnostic_Alarm_supp Process_Alarm_supp Pull_Plug_Alarm_supp Status_Alarm_supp Update_Alarm_supp Manufacturer_Specific_Alarm_supp Diagnostic_Alarm_required Process_Alarm_required Pull_Plug_Alarm_required Status_Alarm_required Update_Alarm_required Manufacturer_Specific_Alarm_required ® Anybus CompactCom ™ 40 PROFIBUS DP-V0/DP-V1 Network Guide HMSI-27-210-EN 2.3...

  • Page 59: E Technical Specification

    LED State Indication Comments Not initialized Anybus state = SETUP or NW_INIT Green Initialized Anybus module has left the NW_INIT state Extended diagnostic bit is set Flashing Green Initialized, diagnostic event (s) present Exception error Anybus state = EXCEPTION ®...

  • Page 60: Functional Earth (Fe) Requirements

    Functional Earth (FE) Requirements In order to ensure proper EMC behavior, the module must be properly connected to functional earth via the FE pad / FE mechanism described in the general Anybus CompactCom M40 Hard- ware Design Guide. HMS Industrial Networks AB does not guarantee proper EMC behaviour unless these FE re- quirements are fulfilled.

  • Page 61: Environmental Specification

    In line with HMS policy of continuous product development, we reserve the right to change the exact power requirements of this product without prior notification. Note however that in any case, the Anybus CompactCom 40 PROFIBUS DPV1/DPV0 will remain as a Class A module. Environmental Specification Consult the Anybus CompactCom Hardware M40 Design Guide for further information.

  • Page 62: F Timing & Performance

    (serial mode) F.2.2 NW_INIT Handling This test measures the time required by the Anybus CompactCom 40 PROFIBUS DPV1/DPV0 module to perform the necessary actions in the NW_INIT-state. Parameter Conditions No. of network specific commands Max.
  • Page 63 μs T102 Write process data delay Time from when the Anybus Compact- Com module ex- changes write process data buffers, to when the first bit of the new process data frame is sent out on the network interface towards the PHY.

  • Page 64: G 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 PROFIBUS DPV1/DPV0, when designing with both series in one applica- tion, or when adapting a 30 series application for the 40 series.
  • Page 65 Anybus CompactCom M30/M40 G.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 66 G.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 67 Related Information: Anybus CompactCom M40 Hardware Design Guide (HMSI-216-126), Sec- tion “Application Connector Pin Overview” Module Identification (MI[0..1]) These pins are used by the host application (i.e your product) to identify what type of Anybus CompactCom that is mounted. The identification differs between the 30-series and the 40- series.
  • Page 68 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 69 67 (72) RMII Compatibility If the RMII mode is being used on an Anybus CompactCom 40 module and it is desired to re- main compatible with the 30 series, it is important to disable this connection when switching to an Anybus CompactCom 30 module due to pin conflicts. The RMII port of the host processor should be set to tristate by default, and only be enabled if an RMII capable Anybus Compact- Com 40 is detected.

  • Page 70: 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” G.3.2 Faster Ping-Pong Protocol The ping-pong protocol (the protocol used in the 30-series) is faster in the 40-series.
  • Page 71 G.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 72: Network Specific - Profibus

    Available Removed Attribute removed in the 40-series. The Any- bus CompactCom will never request this at- tribute. The host application cannot influence the I&M version implemented by the Anybus CompactCom. #17, I&M Supported Available Removed Attribute removed in the 40-series. The Any- bus CompactCom will never request this at- tribute.
  • Page 73 71 (72) G.4.4 Network Configuration Object (04h) The following attributes are removed in the 40–series. The Anybus CompactCom will never re- quest these attributes. It is only possible to set these values via the network (I&M1-4) – end user configuration.
  • Page 74 last page © 2018 HMS Industrial Networks AB Box 4126 300 04 Halmstad, Sweden info@hms.se HMSI-27-210-EN 2.3.8580 / 2018-05-28...

This manual is also suitable for:

Profibus dp-v1Profibus dp-v0

Table of Contents