HMS Anybus CompactCom 30, Anybus CompactCom 40 Migrating from Anybus CompactCom 30 to Anybus CompactCom 40
Migrating from Anybus®CompactCom
™
30
to Anybus
®
CompactCom
DESIGN GUIDE
SCM-1202-043 1.1 ENGLISH
™
40
Important User Information
Liability
Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements including any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this 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.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product described in this document. These intellectual property rights may include patents and pending patent applications in
the USA and other countries.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
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 ..................................................................................................6
1.5 Terminology...................................................................................................................6
1.6 Trademark Information ...................................................................................................7
2 Background ...................................................................................................................... 8
2.1 Anybus CompactCom 30-Series .....................................................................................8
2.2 Upgrade to the 40-Series................................................................................................8
2.3 Access to Real-time Ethernet, IIoT and Advanced Security Features ..................................8
2.4 Recommendations from HMS Industrial Networks AB.......................................................8
3 Initial Considerations ..................................................................................................... 9
4 Hardware Compatibility ...............................................................................................10
4.1 Module........................................................................................................................10
4.2 Chip............................................................................................................................ 10
4.3 Brick ........................................................................................................................... 11
4.4 Host Application Interface .............................................................................................12
5 General Software........................................................................................................... 14
5.1 Extended Memory Areas ..............................................................................................14
5.2 Faster Ping-Pong Protocol............................................................................................ 14
5.3 Requests from CompactCom to Host Application During Startup .....................................14
5.4 Anybus Object (01h) ....................................................................................................14
5.5 Control Register CTRL_AUX-bit....................................................................................15
5.6 Status Register STAT_AUX-bit...................................................................................... 15
5.7 Control Register CTRL_R-bit ........................................................................................ 15
5.8 Modifications of Status Register, Process Data Read Area, and Message Data Read Area 15
6 Network Specific — BACnet/IP..................................................................................16
6.1 Network Configuration Object (04h)............................................................................... 16
6.2 Reduced Network Resources Due to Memory Constraints ..............................................16
7 Network Specific — CC-Link ......................................................................................17
7.1 Network CC-Link Object (08h) ...................................................................................... 17
7.2 Network Object (03h) ................................................................................................... 17
7.3 Diagnostic Object (02h) ................................................................................................17
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Table of Contents
8 Network Specific — DeviceNet ..................................................................................18
8.1 DeviceNet Host Object (FCh)........................................................................................18
8.2 EDS file (Electronic Datasheet file used by configuration tool) .........................................18
9 Network Specific — EtherCAT ...................................................................................19
9.1 Network Configuration Object (04h)............................................................................... 19
9.2 EtherCAT Object (F5h) .................................................................................................19
9.3 ESI-file (Configuration file used by engineering tool) ....................................................... 19
10 Network Specific — EtherNet/IP................................................................................ 21
10.1 Network Object (03h) ................................................................................................... 21
10.2 EtherNet/IP Host Object (F8h) ...................................................................................... 21
10.3 EDS file (Electronic Datasheet file used by configuration tool) .........................................22
11 Network Specific — Modbus-TCP............................................................................. 23
11.1 Modbus Registers ........................................................................................................23
11.2 BOOL arrays ...............................................................................................................23
11.3 Network Configuration Object (04h)............................................................................... 24
11.4 Modbus Host Object (FAh)............................................................................................24
11.5 Ethernet Host Object (F9h) ........................................................................................... 24
11.6 Process data ...............................................................................................................24
12 Network Specific — PROFIBUS................................................................................. 25
12.1 Additional Diagnostic Object (05h)................................................................................. 25
12.2 Network PROFIBUS DP-V1 Object (0Bh) ......................................................................25
12.3 PROFIBUS DP-V1 Object (FDh) ...................................................................................25
12.4 Network Configuration Object (04h)............................................................................... 26
12.5 GSD file (PROFIBUS configuration file used by engineering tool) .................................... 26
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Table of Contents
13 Network Specific — PROFINET ................................................................................. 27
13.1 Network Object (03h) ................................................................................................... 27
13.2 PROFINET IO Object (F6h) .......................................................................................... 28
13.3 PROFINET Additional Diagnostic Object (0Fh) ...............................................................30
13.4 Diagnostic Object (02h) ................................................................................................30
13.5 Network Configuration Object (04h)............................................................................... 31
13.6 Network PROFINET IO Object (0Eh) ............................................................................. 31
13.7 I&M4........................................................................................................................... 31
13.8 LED Indications ........................................................................................................... 32
13.9 SNMP MIB-II ............................................................................................................... 33
13.10 ADI Based Configuration .............................................................................................. 34
13.11 Configuration Mismatch................................................................................................ 35
13.12 Media Redundancy Protocol (MRP)............................................................................... 35
13.13 GSD File (PROFINET configuration file used by engineering tool) ....................................35
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
This page intentionally left blank
Preface 5 (38)
1 Preface
1.1 About this Document
This document is intended to provide a good understanding of differences between the Anybus
CompactCom 30-series and the Anybus CompactCom 40-series to be able to migrate a host
application, i.e. a product, as smooth as possible
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 Host Application Implementation
Guide
Anybus CompactCom 40 Network Guides HMS
Anybus CompactCom 30 Network Guides HMS
PROFINET Installation Guideline for Cabling and Assembly PI
HMS HMSI-27-334
The network guides for the industrial networks mentioned in this document, as well as the design guides, are available at www.anybus.com/support.
1.3 Document History
Version Date Description
1.0 2017-04-28 First version
1.1 2017-06-27 BACnet updates
Migrating from Anybus
®
CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Preface 6 (38)
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
...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. 6
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 Terminology
• 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.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Preface 7 (38)
1.6 Trademark Information
Anybus®is a registered trademark of HMS Industrial Networks AB.
EtherCAT®is a registered trademark and patented technology, licensed by Beckhoff Automation
GmbH, Germany.
EtherNet/IP
DeviceNet
™
is a trademark of ODVA, Inc.
™
is a trademark of ODVA, Inc.
All other trademarks are the property of their respective holders.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Background 8 (38)
2 Background
2.1 Anybus CompactCom 30-Series
The Anybus CompactCom 30-series concept was introduced in 2005 and is based on the NP30
processor from HMS Industrial Networks AB. The concept supports various fieldbuses and industrial Ethernet networks. The Anybus CompactCom 30-series fieldbus and industrial Ethernet
solutions today offer a good level of performance and is used by many customers.
2.2 Upgrade to the 40-Series
During 2013, HMS Industrial Networks AB introduced the new Anybus CompactCom 40-series
which presented a high performance solution with very low latency, extended APIs, and the ability to meet the future demands of industrial networking. In addition to the new APIs, the Anybus
CompactCom 40-series supports the same APIs as the 30series, offering a possibility to enable
present Anybus CompactCom 30 applications an easy upgrade to the latest technology.
2.3 Access to Real-time Ethernet, IIoT and Advanced Security Features
The Anybus CompactCom 40-series is based on the NP40 processor which is the foundation
for the high performance and extended functions offered by the 40-series. Future technologies
and demands of advanced network functions, IIoT solutions, and advanced security features will
be incorporated in the Anybus CompactCom 40-series.
2.4 Recommendations from HMS Industrial Networks AB
For new designs the Anybus CompactCom 40-series is the recommended platform for communication, but the compatibility between the two series enables usage of both series in one product. This document describes the differences between the CompactCom 30-series and the
CompactCom 40-series in order to add guidance on how to modify an existing product to support the latest 40-series modules in addition to existing 30-series support.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Initial Considerations 9 (38)
3 Initial Considerations
There are two options to consider when starting the work to modify a host application developed
for Anybus CompactCom 30-series modules to also be compatible with the 40-series modules:
• Add support with as little work as possible i.e. reuse as much as possible of the current
design.
– This is the fastest and easiest solution but with the drawback that many of the new fea-
tures available in the 40-series will not be enabled (e.g. enhanced and faster communication interfaces, larger memory areas, and faster communication protocols).
– You have to check the hardware and software differences below to make sure the host
application is compatible with the 40-series modules. Small modifications to your current design may be needed.
• Make a redesign and take advantage of all new features presented in the 40-series.
– A new driver and host application example code are available at www.anybus.com/
starterkit40 to support the new communication protocol.This driver supports both 30-
series and 40-series modules.
– You have to check the hardware differences below and make sure the host application
is compatible with the 40-series modules.
This documentation only deals with differences between the 30-series and the 40-series. For a
description of new and enhanced functionality in the Anybus CompactCom 40-series, please
consult our support pages, where you can find all documentation.
Link to support page: www.anybus.com/support.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Hardware Compatibility 10 (38)
4 Hardware Compatibility
Anybus CompactCom is available in three hardware formats; Module, Chip, and Brick.
4.1 Module
The modules in the 30-series and the 40-series share physical characteristics, like dimensions,
outline, connectors, LED indicators, mounting parts etc. They are also available as modules
without housing.
Fig. 1 Anybus CompactCom M30/M40
4.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.
Migrating from Anybus®CompactCom™30 to Anybus®CompactCom™40 Design Guide SCM-1202-043 1.1
Loading...