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 CC-Link IE Field Network Guide...
About this document ......................3 Related Documents .......................3 Document History ......................3 Document Conventions ....................4 Terminology........................4 Trademark Information ....................4 About the Anybus CompactCom 40 CC-Link IE Field ........... 6 General.........................6 Features ........................6 Basic Operation....................... 7 General Information .......................7 Data Exchange ......................8 CC-Link IE Field Implementation Details ..............13 Process Data Mapping ....................13...
Page 4
Table of Contents B Implementation Details....................42 SUP-Bit Definition ......................42 Anybus State Machine ....................42 Application Watchdog Timeout Handling ................42 C Certification Information ..................... 43 Basics.........................43 Model Type........................43 Other ..........................43 CSP+ File Customization....................44 D Technical Specification ....................46 Front View ........................46 Functional Earth (FE) Requirements................47...
This document is intended to provide a good understanding of the functionality offered by the Anybus CompactCom 40 CC-Link IE Field. The document describes the features that are spe- cific to Anybus CompactCom 40 CC-Link IE Field. For general information regarding Anybus CompactCom 40, consult the Anybus CompactCom 40 design guides.
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 7
Preface 5 (52) All other trademarks are the property of their respective holders. ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
This product conforms to all aspects of the host interface defined in the Anybus CompactCom 40 Hardware- and Software Design Guides, making it fully interchangeable with any other de- vice following that specification.
3.1.1 Software Requirements No additional network support code needs to be written in order to support the Anybus Com- pactCom 40 CC-Link IE Field, however due to the nature of the CC-Link IE Field networking system, certain restrictions must be taken into account: •...
Memory Read • Memory Write The Anybus CompactCom 40 CC-Link IE Field supports ADI #1 to 65535 and all ADI data types. The data is handled in 16–bit granularity. Transient Server Memory Read and Memory Write To access ADI data from the CC-Link IE Field network there are two dedicated functions that...
Page 11
(n + 1):th word in the write request data. Example with 3 byte ADI Data layout in master 1122h 3344h Data on network Resulting ADI data ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 12
Example RIRD (transient2 read memory) Data layout in ADI Data on network Resulting data in the master 2211h XX33h ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 13
Application in invalid ported in the current state state Out of resources The target object cannot exe- XX0Eh Out of resources cute the command due to lim- ited resources ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 14
Timeout Considerations If a timeout is detected for a RIRD or RIWT function, please consult the CC-Link IE Field net- work master manual for timeout settings and retry factors. ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
This makes it possible to comply with any profile buffer data layout. If no mapping is done by the application, the Anybus CompactCom 40 CC-Link IE Field auto- matically generates the minimum CC-Link IE Field network configuration (16 bit points/4 word points), but with no connection/mapping towards the application.
If SLMP is implemented in a standard Ethernet device, the device can be accessed and also exchange data across the network. The Anybus CompactCom 40 CC-Link IE Field supports SLMP server functionality in the config- urations shown in the figures below.
Page 20
SLMP is enabled by default in the device, but can be disabled by setting attribute #7 (Enable SLMP) in the CC-Link IE Field Network Host Object (E6h). The Anybus CompactCom 40 CC- Link IE Field supports a limited set of SLMP commands by default. If attribute #8 (Enable SLMP...
Page 21
4.3.1 SLMP (Default) By default, the Anybus CompactCom 40 CC-Link IE Field supports the SLMP commands listed in the table below. An SLMP client data request, will automatically be handled in the same man- ner as for transient/acyclic data exchange, see Acyclic Data Exchange, p.
Page 22
(When data is to be read in bit units, the value of the sub-command is 0001h). Request Da- startAddr Head address 00000001h 4 Octets ta[ 0 - N ] Word length 0001h 2 Octets ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 23
Data (word units) Xxxxh 16-bit Data[ 0 ] 4.3.3 SLMP Diagnostics By default, the Anybus CompactCom 40 CC-Link IE Field will respond with diagnostic informa- tion to the following requests: Command # Subcommand # Command name Description/Comments 3119h 0000h...
Page 24
Data size too big type size exceeds the maximum read size (727 words) Object specific error The object returned an object specific X0FFh See meaning error code column. ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Anybus Module Objects 23 (52) Anybus Module Objects General Information This chapter specifies the Anybus module object implementations and how they correspond to the functionality in the Anybus CompactCom 40 CC-Link IE Field. The following Anybus module objects are implemented: •...
Anybus Module Objects 24 (52) Anybus Object (01h) Category Basic Object Description This object groups common Anybus information, and is described thoroughly in the general Anybus Com- pactCom 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 Software 40 Design Guide for further information.
This object provides a standardized way of handling host application events and diagnostics, and is thor- oughly described in the general Anybus CompactCom Software 40 Design Guide. The module supports two instances of this object, where one is reserved for a major unrecoverable diagnostic event.
Anybus Module Objects 26 (52) Network Object (03h) Category Basic Object Description For more information regarding this object, consult the general Anybus CompactCom 40 Software Design Guide. See also..• Network CC-Link IE Field Object (12h), p. 31 Supported Commands...
Anybus Module Objects 27 (52) Network Configuration Object (04h) Category Basic Object Description This object holds network specific configuration parameters that may be set by the end user. A reset com- mand (factory default) issued towards this object will result in all instances being set to their default values, in- cluding resetting the NVS storage.
Page 30
Any value written to attribute #5 after setup is finished, will be saved in attribute #6 instead of in attribute #5. After a power cycle has been performed, attribute #5 will be updated with the value saved in attribute #6. If no valid station number is entered the module will enter Anybus state EXCEPTION, when leaving Anybus state NW_INIT.
Page 31
Anybus Module Objects 29 (52) Multilingual Strings The instance names in this object are multilingual and are translated based on the current language settings as follows: Instance English German Spanish Italian French Station No. Stationsnr. Núm. Estación No. Stazione Num station Network No.
Object Description This object provides an interface to the built-in file system. In an Anybus CompactCom 40 CC-Link IE Field, the file system consists of one folder, called “Firmware”. This folder is used to save a firmware file to upgrade the module.
Anybus Module Objects 31 (52) Network CC-Link IE Field Object (12h) Category Basic Object Description This object implements CC-Link IE Field network specific services in the module. Reading instance #1, attrib- ute #1, gives information on the cyclic data size that the node represents on the network.
Page 34
Anybus Module Objects 32 (52) Command Details: Execute_External_Loopback_Test Category Basic Details Command Code: Valid for: Object Instance Description This command is used for executing the external Ethernet port loopback test from the application. Use of the test requires a connected Ethernet cable between port 1 and port 2. It is only valid during setup. The LED indi- cation sequence is described in External Loopback test, p.
Object Attributes (Instance #0) Name Access Data Type Value Name Array of “CC-Link IE Field Network” CHAR Revision UINT8 Number of instances UINT16 0001h Highest instance no. UINT16 0001h ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 37
Request (11h). If the application responds with the error bit set the module will respond in the same way as if this attribute was set to 00h (disabled). ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Page 38
It the application returns “Unsupported command” (05h) or any other error response, the Anybus Compact- Com 40 CC-Link IE Field will hand over the indication to the master. Indication will be done towards the network and the module will enter the Anybus state ERROR if these two configuration settings do not match.
Page 40
38 (52) Description If SLMP request forwarding is enabled (attribute #8), the Anybus CompactCom 40 CC-Link IE Field forwards SLMP server requests to the application using this command. The application evaluates the requests and returns a correct response, as well as acts upon the command, e.
MAC ad- If implemented, this attribute must be set during initialization Address UINT8 dress, 6 (in Anybus state SET_UP). If not implementet, the value set bytes at production will be used. Network UINT16 Information about current network status, see below.
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.
The SUP bit is set to “0” if a master is not present on the network, or if the application or the cyclic transmission is not working properly. Anybus State Machine The table below describes how the Anybus State Machine relates to the CC-Link IE Field net- work status. Anybus State...
Other C.3.1 1000BASE-T Compliance The Anybus CompactCom 40 CC-Link IE Field, module version, is tested for 1000BASE-T com- pliance. When the end product is sent for compliance test, the HMS Industrial Networks AB cer- tificate can be used. When using the brick version, the HMS Industrial Networks AB certificate can not be used, and a retest is mandatory.
An generic CSP+ file is provided by HMS Industrial Networks AB. This file is based on the ex- ample application that follows with the Anybus CompactCom 40 Starter Kit, but can be used as a basis for customizing to any other host application. A tool, “Profile Creation Tool”, for modify- ing the file is available at the CLPA web page (www.cc-link.org, membership is required).
Page 47
RWrSize RWr size used by module Set to the RWr size used by the module. Turns up in the RWw/RWR Setting window (under Points in the configuration tool). ® Anybus CompactCom ™ 40 CC-Link IE Field Network Guide HMSI-27-338 1.2...
Operation normal (Fatal Event) If NS/RUN and AS/ERR turn red, this indicates a fatal event. D.1.2 AS/ERROR LED This LED indicates Anybus status and CC-Link IE Field communication errors etc. LED State Indication Description No error No error (or no power) Error An error occurred in the device.
Shielded cables must be used for the CC-Link IE Field network. The shield of the RJ45 connector is not connected directly to FE. If a product using the Anybus CompactCom 40 has problems passing the CC-Link IE Field noise test on the network cables, the network cable shield may have to be connected to the chassis ground at each port in the network.
D.3.2 Power Consumption The Anybus CompactCom 40 CC-Link IE Field is designed to fulfil the requirements of a Class C module. For more information about the power consumption classification used on the Any- bus CompactCom platform, consult the general Anybus CompactCom M40 Hardware Design Guide.
The Anybus CompactCom 40 CC-Link IE Field is able to receive and handle the first application telegram (serial mode) E.2.2 NW_INIT Handling This test measures the time required by the Anybus CompactCom 40 CC-Link IE Field module to perform the necessary actions in the NW_INIT-state. Parameter Conditions No.
Page 52
Parameter Description Delay (min.) Delay (typ.) Delay Unit (max.) μs T101 Read process data delay μs T102 Write process data delay Anybus Ethernet Ethernet Ethernet Host NP40 Ethernet connector Trafo connector Host Application Network Read process data delay Fig. 5...
Need help?
Do you have a question about the CompactCom 40 and is the answer not in the manual?
Questions and answers