Anybus CompactCom B40 Installation and maintenance instructions

Anybus®CompactCom™B40 Modbus Serial
EtherNet/IP
NETWORK GUIDE
SCM-1202-131 1.1 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™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US
Table of Contents Page
1 Preface ................................................................................................................................. 3
1.1 About this Document........................................................................................................3
1.2 Document History ............................................................................................................3
1.3 Document Conventions.....................................................................................................3
1.4 Document Specific Conventions..........................................................................................4
1.5 Trademark Information.....................................................................................................4
2 About the Anybus CompactCom B40 Modbus Serial - EtherNet/IP ................................ 5
2.1 General Information .........................................................................................................5
2.2 Features (EtherNet/IP)......................................................................................................6
2.3 Overview........................................................................................................................6
3 Basic Operation ................................................................................................................... 7
3.1 Electronic Data Sheet (EDS)................................................................................................7
3.2 Network Identity..............................................................................................................7
3.3 Anybus Custom Modbus Function Code 70 ........................................................................... 8
3.4 Communication Settings....................................................................................................9
3.5 Beacon Based DLR (Device Level Ring) .................................................................................9
3.6 Network Data Exchange .................................................................................................. 10
4 FTP Server .......................................................................................................................... 12
4.1 Session Example ............................................................................................................ 12
5 Web Server ........................................................................................................................ 13
5.1 General Information ....................................................................................................... 13
5.2 Web Pages.................................................................................................................... 13
6 CIP Objects......................................................................................................................... 16
6.1 General Information ....................................................................................................... 16
6.2 Identity Object (01h) ...................................................................................................... 17
6.3 Message Router (02h)..................................................................................................... 19
6.4 Assembly Object (04h) .................................................................................................... 20
6.5 Connection Manager (06h) .............................................................................................. 22
6.6 Parameter Object (0Fh)................................................................................................... 26
6.7 DLR Object (47h)............................................................................................................ 28
6.8 QoS Object (48h) ........................................................................................................... 29
6.9 ADI Object (A2h)............................................................................................................ 30
6.10 TCP/IP Interface Object (F5h) ........................................................................................... 32
6.11 Ethernet Link Object (F6h)............................................................................................... 35

Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US
A LED Indications .................................................................................................................. 41
A.1 Network Status LED........................................................................................................ 41
A.2 Module Status LED ......................................................................................................... 41
A.3 LINK/Activity LEDs.......................................................................................................... 41
B Conformance Test Guide .................................................................................................. 42
B.1 General ........................................................................................................................ 42
B.2 Suggested Test Tools ...................................................................................................... 42
B.3 Statement of Conformance (STC) ...................................................................................... 44
C Copyright Notices .............................................................................................................. 47

Preface 3 (54)
1 Preface
1.1 About this Document
This network guide is intended to provide a good understanding of the functionality offered by
the Anybus CompactCom B40 Modbus Serial - EtherNet/IP .
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, along with the Anybus
CompactCom B40 Modbus Serial user manual should normally be sufficient to implement a
design. However, if advanced EtherNet/IP specific functionality is required for the network
interface of the device, 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 information, please visit the support website at www.anybus.com/support.
1.2 Document History
Version Date Description
1.0 2019-04-30 First release
1.1 2019-05-16 Minor corrections
1.3 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
...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. 3
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.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Preface 4 (54)
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.4 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.
• All dimensions in this document have a tolerance of ±0.10 mm unless otherwise stated.
• Outputs are TTL compliant unless otherwise stated.
• Signals which are “pulled to GND” are connected to GND via a resistor.
• Signals which are “pulled to 3V3” are connected to 3V3 via a resistor.
• Signals which are “tied to GND” are directly connected to GND,
• Signals which are “tied to 3V3” are directly connected to 3V3.
1.4.1 Pin Types
The pin types of the connectors are defined in the table below. The pin type may be different
depending on which mode is used.
Pin type Definition
I Input
O Output
I/O Input/Output (bidirectional)
OD Open Drain
Power Pin connected directly to module power supply, GND or 3V3
1.5 Trademark Information
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™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

2 About the Anybus CompactCom B40 Modbus Serial -
EtherNet/IP
2.1 General Information
The Anybus CompactCom B40 Modbus Serial - EtherNet/IP is a communication solution for
simple industrial field devices. The host application communicates with the product using the
Modbus RTU protocol. The Anybus CompactCom B40 Modbus Serial - EtherNet/IP then
communicates the data to the network. Typical applications are basic level I/O blocks,
temperature controllers, measuring devices, and sensors.
The Anybus CompactCom B40 Modbus Serial - EtherNet/IP software interface is designed to be
network protocol independent, making it possible to support several networking systems using
the same application software code/driver.
The Anybus CompactCom B40 Modbus Serial - EtherNet/IP share footprint and electrical
interface with the other members of the product family, independent of fieldbus or network. The
host application connector provides an interface between the host application (Modbus RTU)
and the Anybus CompactCom, while the network connector provides access to the chosen
network. The Anybus CompactCom acts as a Modbus RTU slave on the host application side.
The Anybus CompactCom 40 family offers a wide range of functionality. For advanced products and
applications, we recommend the standard Anybus CompactCom 40.
For general information about other products using the Anybus CompactCom 40 platform,
consult www.anybus.com/support.
This a class A product. In a domestic environment, this product may cause radio
interference in which case the user may be required to take adequate measures.
This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if
ESD control procedures are not followed. Static control precautions are required when
handling the product. Failure to observe this may cause damage to the product.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

2.2 Features (EtherNet/IP)
• Two EtherNet/IP ports
• Both RJ45 and M12 connectors are possible for the physical network interface
• 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
• 10/100 Mbit, full/half duplex operation
• Web server
• FTP server
• Customizable identity information
• CIP parameter object support
All Anybus CompactCom 40 Modbus Serial, where the host is running an exemplary
application, will be precertified for network conformance. This is done to ensure that the
final product can be certified, but it does not necessarily mean that the final product does
not require recertification. Contact HMS Industrial Networks for further information.
2.3 Overview
The picture below shows the data flow in the Anybus CompactCom B40 Modbus Serial -
EtherNet/IP. The application sets up the Modbus RTU communication, and the Anybus
CompactCom maps the process data to the industrial network/fieldbus.
Host processor
with applicaon
Anybus
CompactCom
Modbus
Serial
Process DataData
Industrial Network
Modbus RTU
Fig. 1
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Basic Operation 7 (54)
3 Basic Operation
3.1 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.
Since the module implements the Parameter Object, it is possible for configuration tools such as
Tockwell Automation RSNetWorx™to automatically generate a suitable EDS-file.
See also..
•Parameter Object (0Fh), p. 26 (CIP object)
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: “CompactCom 40 EtherNet/IP(TM)”
Optionally, it is possible to customize the identity of the module by using the Anybus Custom
Modbus function code 70.
See also...
•Identity Object (01h), p. 17 (CIP object)
•Anybus Custom Modbus Function Code 70, p. 8
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Basic Operation 8 (54)
3.3 Anybus Custom Modbus Function Code 70
This command can be used to send an Anybus CompactCom message to change identity and to
configure the Anybus CompactCom B40 Modbus Serial - EtherNet/IP. The request and respond
formats of the telegram are described in the Anybus CompactCom B40 Modbus Serial User
Manual. The data field part of the telegram is composed by concatenating the content for each
configuration option to include. Note that the total amount of configuration options to set is
limited to 244 bytes of data.
Byte 1 2 3 4 5 6 7–n
Configuration
option
Identifier Length Reserved Value
Disable Web
server
249 1 0 3 1 0 0
Disable FTP
server
249 1 0 6 1 0 0
Vendor ID 248 1 0 1 2 0 16-bit Vendor ID in little
endian
Product Code 248 1 0 3 2 0 16-bit Product code in
little endian
Revision 248 1 0 4 2 0 Major rev (8 bits),
minor rev (8 bits)
Serial Number 248 1 0 5 4 0 32-bit serial number in
little endian
Product Name 248 1 0 6 Value
length
0ISO 8859-1 encoded
product name string
(max 32 char)
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. HMS approves use of the HMS Vendor ID (005Ah), in combination with the
default serial number, under the condition that the implementation requires no
deviations from the standard EDS-file.
To obtain a Vendor ID, contact the ODVA.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Basic Operation 9 (54)
3.4 Communication Settings
IP address communication settings are configured by the “Application switch 1” register. An
application may select to write the value from a physical DIP switch, rotary switch or similar, to
this register or it can assign it by other means.
“Application switch 2” is not used for EtherNet/IP network configuration.
Application switch 1
value
User communication
settings
Comment
0Use currently stored
communication settings
Factory default stored communication settings:
IP address: 0.0.0.0
Subnet mask: 0.0.0.0
Gateway address: 0.0.0.0
DHCP: ON
Note: Communication settings may be set by external software, see
below.
1-254 IP address: 192.168.0.X
Subnet mask:
255.255.255.0
Gateway address:
0.0.0.0
DHCP: OFF
Where X in the IP address is the “Application switch 1” value.
Resulting communication settings are stored and can later be used
if “Application switch 1” value is set to 0.
255 IP address: N/A
Subnet mask: N/A
Gateway address: N/A
DHCP: ON
Communication settings received by DHCP are stored and can later
be used if “Application switch 1” value is set to 0.
The communication settings can also be changed from the internal web page, using the IPConfig
tool, available at www.anybus.com/support, or through the EtherNet/IP network. Note that
changing the configuration through any of these interfaces will affect the currently used and/or
stored configuration, but will only be used after the next restart if “Application switch 1” is set to
0.
3.4.1 IPConfig
The IP address can also be configured using the IPConfig tool that is available for download at
the product page at www.anybus.com/support.
When the application is started, the network is automatically scanned for Anybus products. The
network can be rescanned at any time by clicking Scan.
To alter the network settings of a module, double-click on its entry in the list. A window will
appear, containing the settings for the module.
Validate the new settings by clicking Set, or click Cancel to cancel all changes.
3.5 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 B40 Modbus
Serial - EtherNet/IP implements the DLR protocol, which is always enabled. The device is able to
process and act on beacon frames sent by ring supervisors, and supports beacon rates down to
100 μs.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Basic Operation 10 (54)
3.6 Network Data Exchange
3.6.1 Process Data
Process Data is represented as dedicated instances in the Assembly Object (CIP).
See also...
•Assembly Object (04h), p. 20 (CIP object)
•Connection Manager (06h), p. 22 (CIP object)
3.6.2 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
UINT8 USINT One byte
UINT16 UINT Two bytes
3.6.3 File System
Overview
Anybus CompactCom B40 Modbus Serial - EtherNet/IP has an in-built file system that can be
accessed from the network. Three directories are predefined:
VFS The virtual file system that e.g. holds the web pages of the module.
Application Reserved
Firmware Firmware updates are stored in this directory.
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 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, other 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. 12
•Web Server, p. 13
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Basic Operation 11 (54)
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
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

FTP Server 12 (54)
4 FTP Server
The built-in FTP server makes it easy to manage the file system using a standard FTP client. It can
be disabled using Modbus Function Code 70, see Anybus Custom Modbus Function Code 70, p. 8.
The following port numbers are used for FTP communication:
• TCP, port 20 (FTP data port)
• TCP, port 21 (FTP command port)
The FTP server supports up to two concurrent clients.
4.1 Session Example
The Windows Explorer features a built-in FTP client which can easily be used to access the file
system as follows:
1. Open the Windows Explorer.
2. In the address field, type FTP://<address>
– Substitute <address> with the IP address of the Anybus module
3. Press Enter. The Explorer will now attempt to connect to the Anybus module using the
specified settings. If successful, the file system will be displayed in the Explorer window.
Fig. 2
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Web Server 13 (54)
5 Web Server
5.1 General Information
The built-in web server provides a flexible environment for end-user interaction and
configuration purposes.
The web interfaces are stored in the file system, which can be accessed through the FTP server. If
necessary, the web server can be completely disabled using Modbus Function Code 70, see
Anybus Custom Modbus Function Code 70, p. 8.
See also...
•FTP Server, p. 12
5.2 Web Pages
The web pages provide access to:
• Network configuration parameters
• Network status information
• Access to the host application parameters.
5.2.1 Network Configuration
The network configuration page provides interfaces for changing TCP/IP settings.
Fig. 3
The module needs to be reset for the TCP/IP settings to take effect. The Ethernet configuration
settings will take effect immediately.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Web Server 14 (54)
IP Configuration
The module needs a reset for any changes to take effect. The settings will only be used if
application switch 1 is set to 0.
Name Description
DHCP Enable or disable DHCP
Default value: enabled
IP address The TCP/IP settings of the module
Default values: 0.0.0.0 Value ranges: 0.0.0.0 - 255.255.255.255
Subnet mask
Gateway
Host name IP address or name
Max 64 characters
Domain name IP address or name
Max 48 characters
DNS 1 Primary and secondary DNS server, used to resolve host name
Default values: 0.0.0.0 Value ranges: 0.0.0.0 - 255.255.255.255
DNS 2
Ethernet Configuration
Changes will take effect immediately.
Name Description
Port 1 Ethernet speed/duplex settings
Default value: auto
Port 2
5.2.2 Ethernet Statistics Page
The Ethernet statistics web page contains the following information:
Ethernet Link Description
Port 1 Speed: The current link speed
Duplex: The current duplex configuration
Port 2 Speed: The current link speed
Duplex: The current duplex configuration
Ethernet/IP Statistics Description
Established Class1 Connections Current number of established class1 connections
Established Class3 Connections Current number of established class3 connections
Connection Open Requests Number of received connection open requests
Connection Open Format Rejects Connection open requests rejected due to request format error
Connection Open Resource Rejects Connection open requests rejected due to lack of resources
Connection Open Other Rejects Connection open requests rejected due to other reasons
Connection Close Requests Number of received connection open requests
Connection Close Format Rejects Connection close requests rejected due to request format error
Connection Close Other Rejects Connection close requests rejected due to other reasons
Connection Timeouts Number of connection timeouts
Interface Counters Description
In Octets: Received bytes
In Ucast Packets: Received unicast packets
In NUcast packets: Received non unicast packets (broadcast and multicast)
In Discards: Received packets discarded due to no available memory buffers
In Errors: Received packets discarded due to reception error
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

Web Server 15 (54)
Interface Counters Description
In Unknown Protos: Received packets with unsupported protocol type
Out Octets: Sent bytes
Out Ucast packets: Sent unicast packets
Out NUcast packets: Sent non unicast packets (broadcast and multicast)
Out Discards: Outgoing packets discarded due to no available memory buffers
Out Errors: Transmission errors
Media Counters Description
Alignment Errors Frames received that are not an integral number of octets in length
FCS Errors Frames received that do not pass the FCS check
Single Collisions Successfully transmitted frames which experienced exactly one collision
Multiple Collisions Successfully transmitted frames which experienced more than one collision
SQE Test Errors Number of times SQE test error messages are generated
(Not provided with current PHY interface)
Deferred Transmissions Frames for which first transmission attempt is delayed because the medium is
busy
Late Collisions Number of times a collision is detected later than 512 bit-times into the
transmission of a packet
Excessive Collisions Frames for which a transmission fails due to excessive collisions
MAC Receive Errors Frames for which reception of an interface fails due to an internal MAC sublayer
receive error
MAC Transmit Errors Frames for which transmission fails due to an internal MAC sublayer receive
error
Carrier Sense Errors Times that the carrier sense condition was lost or never asserted when
attempted to transmit a frame
Frame Size Too Long Frames received that exceed the maximum permitted frame size
Frame Size Too Short Frames received that are shorter than lowest permitted frame size
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

CIP Objects 16 (54)
6 CIP Objects
6.1 General Information
This chapter specifies the CIP-object implementation in the module. These objects can be
accessed from the network, but not directly by the host application.
Mandatory objects
•Identity Object (01h), p. 17
•Message Router (02h), p. 19
•Assembly Object (04h), p. 20
•Connection Manager (06h), p. 22
•QoS Object (48h), p. 29
•TCP/IP Interface Object (F5h), p. 32
•Ethernet Link Object (F6h), p. 35
Optional Objects:
•Parameter Object (0Fh), p. 26
•DLR Object (47h), p. 28
Vendor Specific Objects:
•ADI Object (A2h), p. 30
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

CIP Objects 17 (54)
6.2 Identity Object (01h)
Object Description
The Identity Object provides identification of and general information about the module.
Instance attributes 1, 3, 4, 6 and 7 can be customized by implementing the Anybus Modbus command function
code 70.
Supported Services
Class: Get_Attribute_Single
Get_Attributes_All
Instance: Get_Attribute_Single
Set_Attribute_Single
Get_Attributes_All
Reset
Class Attributes
# Name Access Type Value
1 Revision Get UINT 0001h (Object revision)
2 Max instance Get UINT Maximum instance number
3Number of
instances
Get UINT Number of instances
Instance 01h Attributes
Attributes #1, 3, 4, 6 and 7 can be customized by implementing the Anybus Modbus command FC70.
# Name Access Type Value/Description
1Vendor ID Get UINT 005Ah (HMS Industrial Networks AB)
2 Device Type Get UINT 002Bh (Generic Device)
3Product Code Get UINT 0037h (Anybus CompactCom 40 EtherNet/IP)
4 Revision Get Struct of:
USINT
USINT
Major and minor firmware revision
5 Status Get WORD See Device Status table below
6Serial Number Get UDINT Unique serial number (assigned by HMS)
7Product Name Get SHORT_STRING “CompactCom 40 EtherNet/IP (TM)”
11 Active
language
Set Struct of:
USINT
USINT
USINT
Requests sent to this instance are forwarded to the module. If the request is
accepted, the module will update the language accordingly.
12 Supported
Language List
Get Array of:
Struct of:
USINT
USINT
USINT
List of languages supported by the host application. The list is read from the
module and translated to CIP standard. By default the only supported language
is English. The application has to implement the corresponding attributes in the
application object to enable more languages.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US

CIP Objects 18 (54)
Device Status
bit(s) Name
0Module Owned
1(reserved)
2Configured
This bit shows if the product has other settings than "out-of-box". The value is set to true if the module’s NV storage is
changed from default.
3(reserved)
4... 7 Extended Device Status:
Value: Meaning:
0000b Unknown
0010b Faulted I/O Connection
0011b No I/O connection established
0100b Non volatile configuration bad
0101b Major fault
0110b Connection in Run mode
0111b Connection in Idle mode
(other) (reserved)
8Set for minor recoverable faults.
9Set for minor unrecoverable faults.
10 Set for major recoverable faults.
11 Set for major unrecoverable faults.
12... 15 (reserved)
Service Details: Reset
The module forwards reset requests from the network to the host application.
There are two types of network reset requests on EtherNet/IP:
Type 0: Power Cycling Reset This service emulates a power cycling of the module, refer to Modbus register 0x0FFF for actions
needed to be taken by the application.
Type 1: Out of box reset This service sets a “out of box”configuration and performs a reset, refer to Modbus register 0x0FFF
for actions needed to be taken by the application.
Anybus®CompactCom™B40 Modbus Serial EtherNet/IP Network Guide SCM-1202-131 1.1 en-US