Anybus CompactCom 40 Modbus-TCP Installation and maintenance instructions

Anybus CompactCom 40
EtherNet/IP IIoT
NETWORK GUIDE
SCM-1202–069 1.9 en-US ENGLISH

Important User Information
Disclaimer
The information in this document is for informational purposes only. Please inform HMS Industrial Networks of any
inaccuracies or omissions found in this document. HMS Industrial Networks disclaims any responsibility or liability
for any errors that may appear in this document.
HMS Industrial Networks reserves the right to modify its products in line with its policy of continuous product
development. The information in this document shall therefore not be construed as a commitment on the part of
HMS Industrial Networks and is subject to change without notice. HMS Industrial Networks makes no commitment
to update or keep current the information in this document.
The data, examples and illustrations found in this document are included for illustrative purposes and are only
intended to help improve understanding of the functionality and handling of the product. In view of the wide range
of possible applications of the product, and because of the many variables and requirements associated with any
particular implementation, HMS Industrial Networks cannot assume responsibility or liability for actual use based on
the data, examples or illustrations included in this document nor for any damages incurred during installation of the
product. Those responsible for the use of the product must acquire sufficient knowledge in order to ensure that the
product is used correctly in their specific application and that the application meets all performance and safety
requirements including any applicable laws, regulations, codes and standards. Further, HMS Industrial Networks will
under no circumstances assume liability or responsibility for any problems that may arise as a result from the use of
undocumented features or functional side effects found outside the documented scope of the product. The effects
caused by any direct or indirect use of such aspects of the product are undefined and may include e.g. compatibility
issues and stability issues.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US
Table of Contents Page
1 Preface ................................................................................................................................. 5
1.1 About this document........................................................................................................5
1.2 Related Documents ..........................................................................................................5
1.3 Document History ............................................................................................................5
1.4 Document Conventions.....................................................................................................5
1.5 Document Specific Conventions..........................................................................................6
1.6 Abbreviations..................................................................................................................6
1.7 Trademarks.....................................................................................................................6
2 About the Anybus CompactCom 40 EtherNet/IP .............................................................. 7
2.1 General..........................................................................................................................7
2.2 Features.........................................................................................................................8
2.3 IIoT – Industrial Internet of Things.......................................................................................8
3 Basic Operation ................................................................................................................... 9
3.1 General Information .........................................................................................................9
3.2 Network Identity............................................................................................................ 10
3.3 Communication Settings.................................................................................................. 10
3.4 Beacon Based DLR (Device Level Ring) ............................................................................... 13
3.5 Network Data Exchange .................................................................................................. 13
3.6 Web Interface ............................................................................................................... 14
3.7 E-mail Client.................................................................................................................. 14
3.8 Modular Device Functionality........................................................................................... 14
3.9 File System ................................................................................................................... 15
4 EtherNet/IP Implementation Details ............................................................................... 17
4.1 General Information ....................................................................................................... 17
4.2 EtherNet/IP & CIP Implementation.................................................................................... 17
4.3 Using the Assembly Mapping Object (EBh) ......................................................................... 18
4.4 Socket Interface (Advanced Users Only) ............................................................................. 20
4.5 Diagnostics ................................................................................................................... 21
4.6 QuickConnect................................................................................................................ 21
4.7 CIP Safety ..................................................................................................................... 21
5 FTP Server .......................................................................................................................... 22
5.1 General Information ....................................................................................................... 22
5.2 User Accounts ............................................................................................................... 22
5.3 Session Example ............................................................................................................ 23

Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US
6 Web Server ........................................................................................................................ 24
6.1 General Information ....................................................................................................... 24
6.2 Default Web Pages......................................................................................................... 24
6.3 Server Configuration....................................................................................................... 29
7 E-mail Client....................................................................................................................... 32
7.1 General Information ....................................................................................................... 32
7.2 How to Send E-mail Messages.......................................................................................... 32
8 Server Side Include (SSI) ................................................................................................... 33
8.1 General Information ....................................................................................................... 33
8.2 Include File ................................................................................................................... 33
8.3 Command Functions....................................................................................................... 33
8.4 Argument Functions ....................................................................................................... 48
8.5 SSI Output Configuration................................................................................................. 52
9 JSON ................................................................................................................................... 53
9.1 General Information ....................................................................................................... 53
9.2 JSON Objects................................................................................................................. 54
9.3 Example ....................................................................................................................... 72
10 OPC UA............................................................................................................................... 73
10.1 General ........................................................................................................................ 73
10.2 Namespaces.................................................................................................................. 74
10.3 CompactCom 40 Device Type ........................................................................................... 75
10.4 Application Data Exchange............................................................................................... 80
10.5 Time............................................................................................................................ 85
10.6 Authorization ................................................................................................................ 85
10.7 Error Code Translation .................................................................................................... 85
10.8 Stack Configuration ........................................................................................................ 87
11 MQTT ................................................................................................................................. 89
11.1 Anybus CompactCom MQTT Implementation...................................................................... 90
11.2 MQTT Configuration....................................................................................................... 92
11.3 MQTT Topic ................................................................................................................. 92
11.4 Dataset Encoding ........................................................................................................... 92

Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US
12 CIP Objects......................................................................................................................... 96
12.1 General Information ....................................................................................................... 96
12.2 Translation of Status Codes.............................................................................................. 97
12.3 Identity Object (01h) ...................................................................................................... 98
12.4 Message Router (02h)................................................................................................... 101
12.5 Assembly Object (04h) .................................................................................................. 102
12.6 Connection Manager (06h) ............................................................................................ 105
12.7 Parameter Object (0Fh)................................................................................................. 109
12.8 DLR Object (47h).......................................................................................................... 112
12.9 QoS Object (48h) ......................................................................................................... 113
12.10 Base Energy Object (4Eh)............................................................................................... 114
12.11 Power Management Object (53h) ................................................................................... 116
12.12 ADI Object (A2h).......................................................................................................... 118
12.13 Port Object (F4h) ......................................................................................................... 120
12.14 TCP/IP Interface Object (F5h) ......................................................................................... 122
12.15 Ethernet Link Object (F6h)............................................................................................. 125
13 Anybus Module Objects.................................................................................................. 130
13.1 General Information ..................................................................................................... 130
13.2 Anybus Object (01h)..................................................................................................... 131
13.3 Diagnostic Object (02h)................................................................................................. 132
13.4 Network Object (03h) ................................................................................................... 133
13.5 Network Configuration Object (04h) ................................................................................ 134
13.6 Socket Interface Object (07h)......................................................................................... 147
13.7 SMTP Client Object (09h)............................................................................................... 164
13.8 Anybus File System Interface Object (0Ah)........................................................................ 169
13.9 Network Ethernet Object (0Ch) ...................................................................................... 170
13.10 CIP Port Configuration Object (0Dh) ................................................................................ 172
13.11 Functional Safety Module Object (11h) ............................................................................ 174
14 Host Application Objects ................................................................................................ 181
14.1 General Information ..................................................................................................... 181
14.2 MQTT Host Object (E2h)................................................................................................ 182
14.3 OPC UA Object (E3h) .................................................................................................... 185
14.4 Energy Reporting Object (E7h)........................................................................................ 187
14.5 Functional Safety Object (E8h)........................................................................................ 188
14.6 Application File System Interface Object (EAh) .................................................................. 190
14.7 CIP Identity Host Object (EDh)........................................................................................ 191
14.8 Sync Object (EEh)......................................................................................................... 193
14.9 Energy Control Object (F0h) ........................................................................................... 194
14.10 EtherNet/IP Host Object (F8h) ........................................................................................ 200
14.11 Ethernet Host Object (F9h) ............................................................................................ 209

Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US
A Categorization of Functionality ...................................................................................... 213
A.1 Basic.......................................................................................................................... 213
A.2 Extended .................................................................................................................... 213
B Implementation Details .................................................................................................. 214
B.1 SUP-Bit Definition ........................................................................................................ 214
B.2 Anybus State Machine .................................................................................................. 214
B.3 Application Watchdog Timeout Handling.......................................................................... 214
C Secure HICP (Secure Host IP Configuration Protocol) ................................................... 215
C.1 General ...................................................................................................................... 215
C.2 Operation................................................................................................................... 215
D Technical Specification.................................................................................................... 216
D.1 Front View.................................................................................................................. 216
D.2 Functional Earth (FE) Requirements................................................................................. 217
D.3 Power Supply .............................................................................................................. 217
D.4 Environmental Specification........................................................................................... 217
D.5 EMC Compliance.......................................................................................................... 217
E Timing & Performance .................................................................................................... 218
E.1 General Information ..................................................................................................... 218
E.2 Internal Timing ............................................................................................................ 218
F Conformance Test Guide ................................................................................................ 220
F.1 General...................................................................................................................... 220
F.2 Suggested Test Tools .................................................................................................... 220
F.3 Statement of Conformance (STC) .................................................................................... 222
G License Information ........................................................................................................ 238

Preface 5 (244)
1 Preface
1.1 About this document
This document is intended to provide a good understanding of the functionality offered by the
Anybus CompactCom 40 EtherNet/IP. The document describes the features that are specific to
Anybus CompactCom 40 EtherNet/IP. For general information regarding Anybus CompactCom,
consult the Anybus CompactCom design guides.
The reader of this document is expected to be familiar with high level software design and
communication systems in general. The information in this network guide should normally be
sufficient to implement a design. However if advanced EtherNet/IP specific functionality is to be
used, in-depth knowledge of EtherNet/IP networking internals and/or information from the
official EtherNet/IP specifications may be required. In such cases, the persons responsible for the
implementation of this product should either obtain the EtherNet/IP specification to gain
sufficient knowledge or limit their implementation in such a way that this is not necessary.
For additional related documentation and file downloads, please visit the support website at
www.anybus.com/support.
1.2 Related Documents
Document Author Document ID
Anybus CompactCom 40 Software Design Guide HMS HMSI-216-125
Anybus CompactCom M40 Hardware Design Guide HMS HMSI-216-126
Anybus CompactCom B40 Design Guide HMS HMSI-27-230
Anybus CompactCom Host Application Implementation Guide HMS HMSI-27-334
CIP specification, Volumes 1 (CIP Common) and 2 (EtherNet/IP) ODVA
1.3 Document History
Version Date Description
1.4 2017-11-28 First release
1.5 2017-12-15 Updated Copyright Appendix
Corrected Network Type ID
1.6 2018-05-07 Added Conformance Test Guide
Updates to CIP objects ADI and QoS
Misc updates
1.7 2018-09-19 Added MQTT functionality
Updated Set_Configuration_Data descriptions in EtherNet/IP Host object
1.8 2018-10-23 Minor update, mainly to MQTT section
1.9 2019-06-10 Rebranding
Minor updates
1.4 Document Conventions
Ordered lists are used for instructions that must be carried out in sequence:
1. First do this
2. Then do this
Unordered (bulleted) lists are used for:
• Itemized information
• Instructions that can be carried out in any order
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Preface 6 (244)
...and for action-result type instructions:
►This action...
→ leads to this result
Bold typeface indicates interactive parts such as connectors and switches on the hardware, or
menus and buttons in a graphical user interface.
Monospaced text is used to indicate program code and other
kinds of data input/output such as configuration scripts.
This is a cross-reference within this document: Document Conventions, p. 5
This is an external link (URL): www.hms-networks.com
This is additional information which may facilitate installation and/or operation.
This instruction must be followed to avoid a risk of reduced functionality and/or damage
to the equipment, or to avoid a network security risk.
Caution
This instruction must be followed to avoid a risk of personal injury.
WARNING
This instruction must be followed to avoid a risk of death or serious injury.
1.5 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
hexadecimal value.
• A byte always consists of 8 bits.
• The terms “basic” and “extended” are used to classify objects, instances and attributes.
1.6 Abbreviations
Abbreviation Meaning
API assigned packet interval
RPI requested packet interval
Ttarget (in this case the module)
Oorigin (in this case the master)
1.7 Trademarks
Anybus®is a registered trademark of HMS Industrial Networks.
EtherNet/IP is a trademark of ODVA, Inc.
All other trademarks are the property of their respective holders.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

About the Anybus CompactCom 40 EtherNet/IP 7 (244)
2 About the
Anybus CompactCom 40 EtherNet/IP
2.1 General
The Anybus CompactCom 40 EtherNet/IP communication module provides instant EtherNet/IP
conformance tested connectivity via the patented Anybus CompactCom host interface. Any
device that supports this standard can take advantage of the features provided by the module,
allowing seamless network integration regardless of network type. The module supports both
linear and ring network topology (DLR, Device Level Ring).
The modular approach of the Anybus CompactCom 40 platform allows the CIP-object
implementation to be extended to fit specific application requirements. Furthermore, the
Identity Object can be customized, allowing the end product to appear as a vendor-specific
implementation rather than a generic 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. Generally, no additional
network related software support is needed, however in order to be able to take full advantage
of advanced network specific functionality, a certain degree of dedicated software support may
be necessary.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

About the Anybus CompactCom 40 EtherNet/IP 8 (244)
2.2 Features
• Two EtherNet/IP ports
• Ethernet connectors
• Supports OPC UA technology
• Supports MQTT functionality
• Max. read process data: 1448 bytes
• Max. write process data: 1448 bytes
• Max. process data (read + write, in bytes): 2896 bytes
• Beacon Based DLR (Device Level Ring) and linear network topology supported
• Black channel interface, offering a transparent channel supporting CIP Safety.
• 10/100 Mbit, full/half duplex operation
• Web server w. customizable content
• FTP server
• Email client
• Server Side Include (SSI) functionality
• JSON functionality
• Customizable Identity Information
• Up to 65535 ADIs
• CIP Parameter Object support
• Expandable CIP-object implementation
• Supports unconnected CIP routing
• Transparent Socket Interface
• Modular Device functionality
• QuickConnect supported
• Multiple IO assembly instances can be created
2.3 IIoT – Industrial Internet of Things
IIoT gives an application access to the data of a product over the internet. This is, among other
things, useful for
• uncovering product failures and deficiencies
• discovering how products are used
• ensuring the quality of products faster
To support IIoT, the Anybus CompactCom 40 EtherNet/IP supports the protocols OPC UA and
MQTT.
See also ...
•OPC UA, p. 73
•MQTT, p. 89
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 9 (244)
3 Basic Operation
3.1 General Information
3.1.1 Software Requirements
No additional network support code needs to be written in order to support the Anybus
CompactCom 40 EtherNet/IP, however due to the nature of the EtherNet/IP networking system,
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.
• Up to 5 diagnostic instances (See Diagnostic Object (02h), p. 132) can be created by the host
application during normal conditions. An additional 6th instance may be created in event of
a major fault. This limit is set by the module, not by the network.
• EtherNet/IP in itself does not impose any specific timing demands when it comes to acyclic
requests (i.e. requests towards instances in the Application Data Object), however it is
generally recommended to process and respond to such requests within a reasonable time
period. The application that sends the request, also decides the timeout, e.g. EIPScan
employs a timeout of 10 seconds.
• The use of advanced CIP-specific functionality may require in-depth knowledge in CIP
networking internals and/or information from the official CIP and EtherNet/IP specifications.
In such cases, the people responsible for the implementation of this product is expected
either to obtain these specifications to gain sufficient knowledge or limit their
implementation is such a way that this is not necessary.
See also...
•Diagnostic Object (02h), p. 132 (Anybus Module Objects)
• Anybus CompactCom 40 Software Design Guide, “Application Data Object (FEh)”
For in depth information regarding the Anybus CompactCom software interface, consult the
Anybus CompactCom 40 Software Design Guide.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 10 (244)
3.1.2 Electronic Data Sheet (EDS)
On EtherNet/IP, the characteristics of a device is stored in an ASCII data file with the suffix EDS.
This file is used by configuration tools etc. when setting up the network configuration. HMS
Industrial Networks supplies a standard (generic) EDS file, which corresponds to the default
settings in the module. However, due to the flexible nature of the Anybus CompactCom concept,
it is possible to alter the behavior of the product in ways which invalidate the generic EDS file. In
such case, a custom EDS file needs to be created, which in turn invalidates the default identity
information and require re-certification of the product.
Since the module implements the Parameter Object, it is possible for configuration tools such as
RSNetWorx to automatically generate a suitable EDS-file. Note that this functionality requires
that the command Get_Instance_Number_By_Order (Application Data Object, FEh) has been
implemented in the host application.
See also..
•Parameter Object (0Fh), p. 109 (CIP object)
• Anybus CompactCom 40 Software Design Guide, “Application Data Object (FEh)”
HMS Industrial Networks approves use of the standard EDS-file only under the condition
that it matches the actual implementation and that the identity information remains
unchanged.
3.2 Network Identity
By default, the module uses the following identity settings:
Vendor ID: 005Ah (HMS Industrial Networks)
Device Type: 002Bh (Generic Device)
Product Code: 0037h (Anybus CompactCom 40 EtherNet/IP)
Product Name: “Anybus CompactCom 40 EtherNet/IP(TM)”
Optionally, it is possible to customize the identity of the module by implementing the
corresponding instance attributes in the EtherNet/IP Host Object.
See also...
•Identity Object (01h), p. 98 (CIP object)
•EtherNet/IP Host Object (F8h), p. 200 (Host Application Object)
According to the CIP specification, the combination of Vendor ID and serial number must
be unique. It is not permitted to use a custom serial number in combination with the
HMS Vendor ID (005Ah), nor is it permitted to choose Vendor ID arbitrarily. Failure to
comply to this requirement will induce interoperability problems and/or other unwanted
side effects.
To obtain a Vendor ID, contact the ODVA.
3.3 Communication Settings
Network related communication settings are grouped in the Network Configuration Object (04h),
and includes:
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 11 (244)
IP settings These settings must be set properly in order for the module to be able to participate on
the network.
The module supports DHCP, which may be used to retrieve the IP settings from a DHCP-
server automatically. DHCP is enabled by default, but can be disabled if necessary.
Physical Link Settings By default, the module uses auto negotiation to establish the physical link settings,
however it is possible to force a specific setting if necessary.
The parameters in the Network Configuration Object (04h) are available from the network
through the built in web server, and through the TCP/IP Interface Object (CIP).
The parameters in the Network Configuration Object (04h) are available from the network
through the TCP/IP Interface Object (CIP).
See also...
•Web Server, p. 24
•TCP/IP Interface Object (F5h), p. 122 (CIP object)
•Ethernet Link Object (F6h), p. 125 (CIP object)
•Network Configuration Object (04h), p. 134 (Anybus Module Object)
•Secure HICP (Secure Host IP Configuration Protocol), p. 215
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 12 (244)
3.3.1 Communication Settings in Stand Alone Shift Register Mode
If the Anybus CompactCom 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). A flowchart is shown below.
Start
DIP1 switch settings
(0 - 255)
2550
1 - 254
Values stored in
Network Conguration
Object instances #3 - #6
will be used
Ethernet
Host Object (F9h),
attribute #17
implemented
Yes
No Use default value for
IP address bytes 0 - 2:
192.168.0.X
Use DIP switch settings
for IP address byte 3
End
Use attribute #17 values
for IP address bytes 0 - 2
IP address is stored in Network
Conguration Object (04h),
instance #3
Check for DHCP
availability
Yes
No
DHCP will be used for
communication settings,
that will be stored in
Network Conguration
Object (04h), instances #3 - #6
Values stored in
Network Conguration
Object instances #3 - #6
will be used
Network Conguration Object (04h)
Instance #4, Subnet mask: 255.255.255.0
Instance #5 Gateway address: 0.0.0.0
Instance 6, DHCP: OFF
Fig. 1
See also ...
•Ethernet Host Object (F9h), p. 209
• Anybus CompactCom M40 Hardware Design Guide
•Network Configuration Object (04h), p. 134
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 13 (244)
3.4 Beacon Based DLR (Device Level Ring)
Device Level Ring (DLR) is a network technology for industrial applications that uses embedded
switch functionality in automation end devices, such as programmable automation controllers
and I/O modules, to enable Ethernet ring network topologies at the device level. DLR technology
adds network resilience to optimize machine operation. Beacon based DLR networks consist of a
ring supervisor and a number of ring nodes, and use “beacons” to detect breaks in the ring.
When a DLR network detects a break in the ring, it provides ways to alternatively route the data
to recover the network. Diagnostics built into DLR products can identify the point of failure, thus
helping to speed maintenance and reduce repair time. The Anybus CompactCom 40 EtherNet/IP
implements the DLR protocol, and it is enabled by default. The device is able to process and act
on beacon frames sent by ring supervisors, and supports beacon rates down to 100 μs. If
needed, the DLR functionality can be disabled. This can be done by setting attribute #31 (Enable
DLR) in the EtherNet/IP Host Object to False. See EtherNet/IP Host Object (F8h), p. 200.
3.5 Network Data Exchange
3.5.1 Application Data
Application Data Instances (ADIs) are represented through the ADI Object (CIP). Each instance
within this objects corresponds directly to an instance in the Application Data Object on the host
application side.
Accessible range of ADIs is 1 to 65535.
See also...
•Parameter Object (0Fh), p. 109 (CIP object)
•ADI Object (A2h), p. 118 (CIP object)
3.5.2 Process Data
Process Data is represented as dedicated instances in the Assembly Object (CIP).
See also...
•Assembly Object (04h), p. 102 (CIP object)
•Connection Manager (06h), p. 105 (CIP object)
3.5.3 Translation of Data Types
The Anybus data types are translated to CIP-standard and vice versa as follows:
Anybus Data Type CIP Data Type Comments
BOOL BOOL Each ADI element of this type occupies one byte.
ENUM USINT
SINT8 SINT
UINT8 USINT
SINT16 INT Each ADI element of this type occupies two bytes.
UINT16 UINT
SINT32 DINT Each ADI element of this type occupies four bytes.
UINT32 UDINT
FLOAT REAL
CHAR SHORT_STRING SHORT_STRING consists of a single-byte length field (which in this case
represents the number of ADI elements) followed by the actual
character data (in this case the actual ADI elements). This means that a
10-character string occupies 11 bytes.
SINT64 LINT Each ADI element of this type occupies eight bytes.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 14 (244)
Anybus Data Type CIP Data Type Comments
UINT64 ULINT
BITS8 BYTE Each ADI element of this type occupies one byte.
BITS16 WORD Each ADI element of this type occupies two bytes.
BITS32 DWORD Each ADI element of this type occupies four bytes.
OCTET USINT
BITS1-7 BYTE Bit fields of size 1 - 7
PAD0-8 BYTE Bit fields of size 0 - 8 used for padding
PAD9-16 BYTE Bit fields of size 9 - 16 used for padding
BOOL1 BOOL
3.6 Web Interface
The web interface can be fully customized to suit a particular application. Dynamic content can
be created by means of JSON and SSI scripting. Data and web pages are stored in a FLASH-based
file system, which can be accessed using any standard FTP-client.
See also...
•File System, p. 15
•FTP Server, p. 22
•Web Server, p. 24
•Server Side Include (SSI), p. 33
•JSON, p. 53
3.7 E-mail Client
The built-in e-mail client enables the host application to send e-mail messages stored in the file
system, or defined directly within the SMTP Client Object (09h). Messages are scanned for SSI
content, which means it’s possible to embed dynamic information from the file system.
See also...
•File System, p. 15
3.8 Modular Device Functionality
Modular devices consist of a backplane with a certain number of slots. The first slot is occupied
by the “coupler” which contains the Anybus CompactCom module. All other slots may be empty
or occupied by modules.
When mapping ADIs to process data the application shall map the process data of each module
in slot order.
A list of modules in a Modular Device is available to the EtherNet/IP network master by a
request to the CIP Identity object.
See also ...
• “Modular Device Object (ECh)” (see Anybus CompactCom 40 Software Design Guide)
•Identity Object (01h), p. 98 (CIP object)
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 15 (244)
3.9 File System
3.9.1 Overview
The Anybus CompactCom 40 EtherNet/IP has an in-built file system, that can be accessed from
the application and from the network. Three directories are predefined:
VFS The virtual file system that e.g. holds the web pages of the module. The virtual file
system is enabled by default in the Anybus File System Interface Object (0Ah).
Application This directory provides access to the application file system through the Application File
System Interface Object (EAh) (optional).
Firmware Firmware updates are stored in this directory.
In the firmware folder, it is not possible to use append mode when writing a file. Be sure to use write
mode only.
Anybus
CompactCom
File system
File 1
File 2
VFS
File 1
File 2
Application
Application
File system
File A1
File A2
Directory A1
File A1:1
File A1:2
The Anybus CompactCom accesses
the application file system through the
Application File System Interface Object.
Anybus CompactCom Application
Firmware
Fig. 2
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

Basic Operation 16 (244)
3.9.2 General Information
The built-in file system hosts 28 MByte of non volatile storage, which can be accessed by the
HTTP and FTP servers, the email client, and the host application (through the Anybus File System
Interface Object (0Ah)).
The 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). The number of files that can
be stored in other directories, than the root directory, is unlimited.
The file system uses the following conventions:
• \ (backslash) is used as a path separator
• Names may contain spaces, but must not begin or end with one.
• Valid characters in names are ASCII character numbers less than 127, excluding the
following characters: \ / : * ? “ < > |
• Names cannot be longer than 48 characters
• A path cannot be longer than 126 characters (filename included)
See also ...
•FTP Server, p. 22
•Web Server, p. 24
•E-mail Client, p. 32
•Server Side Include (SSI), p. 33
•Anybus File System Interface Object (0Ah), p. 169
•Application File System Interface Object (EAh), p. 190
The file system is located in flash memory. Due to technical reasons, each flash segment
can be erased approximately 100000 times before failure, making it unsuitable for
random access storage.
The following operations will erase one or more flash segments:
• Deleting, moving or renaming a file or directory
• Writing or appending data to an existing file
• Formatting the file system
3.9.3 System Files
The file system contains a set of files used for system configuration. These files, known as
“system files”, are regular ASCII files which can be altered using a standard text editor (such as
the Notepad in Microsoft Windows™). The format of these files are, with some exceptions, based
on the concept of keys, where each keys can be assigned a value, see below.
Example 1:
[Key1]
value of Key1
[Key2]
value of Key2
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

EtherNet/IP Implementation Details 17 (244)
4 EtherNet/IP Implementation Details
4.1 General Information
This chapter covers EtherNet/IP specific details in the Anybus implementation. Note that the use
of such functionality may require in-depth knowledge in EtherNet/IP networking internals and/or
information from the official EtherNet/IP and CIP specifications. In such cases, the people
responsible for the implementation of this product are expected either to obtain these
specifications to gain sufficient knowledge or limit their implementation in such a way that this is
not necessary. The EDS file must be changed to reflect all changes.
4.2 EtherNet/IP & CIP Implementation
By default, the module supports the generic CIP profile. Optionally, it is possible to re-route
requests to unimplemented CIP objects to the host application, thus enabling support for other
profiles etc.
To support a specific profile, perform the following steps:
1. Set up the identity settings in the EtherNet/IP Host Object according to profile requirements.
2. Implement the Assembly Mapping Object in the host application.
3. Set up the Assembly Instance Numbers according to profile requirements.
4. Enable routing of CIP messages to the host application in the EtherNet/IP Host Object.
5. Implement the required CIP objects in the host application.
See also...
•Using the Assembly Mapping Object (EBh), p. 18
•EtherNet/IP Host Object (F8h), p. 200 (Host Application Object), details for the command
Process_CIP_Object_Request.
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US

EtherNet/IP Implementation Details 18 (244)
4.3 Using the Assembly Mapping Object (EBh)
4.3.1 Introduction
This guide will describe how to map CIP instances to ADI data, using the assembly mapping
object (EBh).
4.3.2 Adding Data - The Application Data Object
According to the Anybus object model, all data that is used in the application must be
represented by application data instances (ADIs). ADIs are small portions of structured data, each
representing only one of three possible different types: variable, array or structure.
See the Application Data Object (FEh) in the Software Design Guide for more information.
Below is an example with 30 ADIs. Instances 1 - 6 and 30 are implemented in the application,
and 7 - 29 are not implemented.
Application Data Object (FEh) Instances
Instance # Implemented Order #
1 Yes 1
2 Yes 2
3 Yes 3
4 Yes 4
5 Yes 5
6 Yes 6
7...29 No -
30 Yes 7
Anybus CompactCom 40 EtherNet/IP IIoT Network Guide SCM-1202–069 1.9 en-US