Related Manuals for HMS Anybus CompactCom 30
Summary of Contents for HMS Anybus CompactCom 30
- Page 1 ® Migrating from Anybus CompactCom ™ to Anybus ® CompactCom ™ DESIGN GUIDE SCM-1202-043 1.1 ENGLISH...
- Page 2 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.
-
Page 3: Table Of Contents
Trademark Information ....................7 Background ........................8 Anybus CompactCom 30-Series ..................8 Upgrade to the 40-Series....................8 Access to Real-time Ethernet, IIoT and Advanced Security Features........8 Recommendations from HMS Industrial Networks AB............8 Initial Considerations..................... 9 Hardware Compatibility ....................10 Module........................10 Chip..........................10 Brick ........................... 11 Host Application Interface .....................12... - Page 4 Table of Contents Network Specific — DeviceNet .................. 18 DeviceNet Host Object (FCh)..................18 EDS file (Electronic Datasheet file used by configuration tool) .........18 Network Specific — EtherCAT ................... 19 Network Configuration Object (04h)................19 EtherCAT Object (F5h) ....................19 ESI-file (Configuration file used by engineering tool) ............19 10 Network Specific —...
- Page 5 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...
- Page 6 This page intentionally left blank...
-
Page 7: Preface
HMSI-27-334 Guide Anybus CompactCom 40 Network Guides Anybus CompactCom 30 Network Guides PROFINET Installation Guideline for Cabling and Assembly The network guides for the industrial networks mentioned in this document, as well as the de- sign guides, are available at www.anybus.com/support. -
Page 8: Document Conventions
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. -
Page 9: Trademark Information
Preface 7 (38) 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 is a trademark of ODVA, Inc. ™ DeviceNet is a trademark of ODVA, Inc. -
Page 10: Background
Background 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 in- dustrial 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. -
Page 11: Initial Considerations
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. -
Page 12: Hardware Compatibility
Hardware Compatibility 10 (38) Hardware Compatibility Anybus CompactCom is available in three hardware formats; Module, Chip, and Brick. 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. -
Page 13: Brick
The Anybus CompactCom B40-1 does not share dimensions with the Anybus CompactCom B30. The B40-1 is thus not suitable for migration. However HMS Industrial Networks AB has de- veloped a separate brick version in the 40-series, that can be used for migration. This product, B40-2, shares dimensions etc. -
Page 14: Host Application Interface
If your software use this identification you need to handle the new identification value. Module Type Active Anybus CompactCom 30 HIGH Active Anybus CompactCom 40 MI[0..1] shall only be sampled by the application during the time period from power up to the end of SETUP state. - Page 15 Hardware Compatibility 13 (38) 4.4.3 GIP[0..1]/LED3[A..B] These pins are tri-stated inputs by default in the 30-series. In the 40-series, these pins are tri- stated until the state NW_INIT. After that they become open-drain, active low LED outputs (LE- D3A/LED3B). No modification of the hardware is needed, if your current design has •...
-
Page 16: General Software
General Software 14 (38) General Software Extended Memory Areas The memory areas have been extended in the 40-series, and it is now possible to access larger sizes of process data (up to 4096 bytes instead of former maximum 256 bytes) and message data (up to 1524 bytes instead of former maximum 255 bytes). -
Page 17: Control Register Ctrl_Aux-Bit
40-series The value of the CTRL_AUX bit is always ignored. Process data is always accepted. All released Anybus CompactCom 30 example drivers from HMS comply with this difference. Related Information: Anybus CompactCom 40 Software Design Guide (HMSI-216-125), section “Control Register”. -
Page 18: Network Specific - Bacnet/Ip
Network Specific — BACnet/IP 16 (38) Network Specific — BACnet/IP Network Configuration Object (04h) The instances in the Network Configuration Object have been rearranged for the Ethernet based modules for consistency. Network specific instances are moved to instance number 20 and onwards. -
Page 19: Network Specific - Cc-Link
Network Specific — CC-Link 17 (38) Network Specific — CC-Link Network CC-Link Object (08h) The specific CC-Link mapping commands: Map_ADI_Specified_Write_Area, Map_ADI_Speci- fied_Read_Area have been removed. With these two previously used commands it was possi- ble to freely specify the location of the mapped data in the CC-Link address map; this is not possible anymore. -
Page 20: Network Specific - Devicenet
Network Specific — DeviceNet 18 (38) Network Specific — DeviceNet DeviceNet Host Object (FCh) Attribute 30-series 40-series Change/Action/Comment #2, Device Type Default: 0000h Default: 002Bh If the attribute is implemented in the host ap- plication, it overrides the default value and there is no difference between the 30-series and the 40-series. -
Page 21: Network Specific - Ethercat
ESI-file (Configuration file used by engineering tool) When migrating from the 30-series to the 40-series, a new, updated ESI-file is needed. To help you, there is an ESI-file Generator available from HMS Industrial Networks AB, see below. 9.3.1 ESI-file Generator An ESI-file generator is available on the HMS Industrial Networks AB website. - Page 22 FoE is disabled in the EtherCAT host object, this keyword must be removed from the ESI-file. <FoE/> Since the 40-series is using the HMS slave controller, the EEPROM byte size and the SII config- uration data must be changed according to the following settings.
-
Page 23: Network Specific - Ethernet/Ip
Network Specific — EtherNet/IP 21 (38) Network Specific — EtherNet/IP 10.1 Network Object (03h) Attribute #1, Network The 30-series module is available in two network type versions, either with Type “Beacon based DLR” (Highest performance) or with “Announce based DLR” which both are Ethernet redundancy protocols. -
Page 24: Eds File (Electronic Datasheet File Used By Configuration Tool)
Network Specific — EtherNet/IP 22 (38) 10.2.1 EtherNet/IP functionality Max Message The maximum number of simultaneous Class 3 connections are 16 in the 30- Connections series and 6 in the 40-series. No change is needed in the host application. EtherNet/IP The maximum number of simultaneous encapsulation sessions are 48 in the 30- Encapsulation series and 15 in the 40-series. -
Page 25: Network Specific - Modbus-Tcp
Network Specific — Modbus-TCP 23 (38) Network Specific — Modbus-TCP 11.1 Modbus Registers Rearrangements have been made in the Modbus register map, because process data sizes have been increased to 1536 bytes in each direction. An existing PLC configuration need to be changed to use the new addresses. -
Page 26: Network Configuration Object (04H)
Network Specific — Modbus-TCP 24 (38) 11.3 Network Configuration Object (04h) The instances in the Network Configuration Object have been rearranged for the Ethernet based modules for consistency. Network specific instances are moved to instance number 20 and onwards. This is done to increase the number of instances in the section that is not network specific. -
Page 27: Network Specific - Profibus
Network Specific — PROFIBUS 25 (38) Network Specific — PROFIBUS 12.1 Additional Diagnostic Object (05h) Object removed in the 40-series. To create diagnostics, use Diagnostic Object (02h). Another option is to use the PROFIBUS DP-V0 Diagnostic Object (10h) where diagnostics can be sent transparently from the host application to the network. -
Page 28: Network Configuration Object (04H)
Network Specific — PROFIBUS 26 (38) 12.4 Network Configuration Object (04h) The following attributes are removed in the 40–series. The Anybus CompactCom will never re- quest these attributes. It is only possible to set these values via the network (I&M1-4) – end user configuration. -
Page 29: Network Specific - Profinet
Network Specific — PROFINET 27 (38) Network Specific — PROFINET Related Information: Anybus CompactCom 40 PROFINET IRT Network Guide, HMSI-27-226 Network Interface Appendix, Anybus CompactCom 30, PROFINET IO 2-Port, HMSI-168-49 13.1 Network Object (03h) Attribute Default Anybus CompactCom Product Comment... -
Page 30: Profinet Io Object (F6H)
If the attribute is not implemented, the default value differs between the different Anybus CompactCom PRO- FINET types. #19, System “HMS Indus- 30-series, PROFINET IO 1-Port If the attribute is implemented in the Description trial Net- host application, it overrides the de-... - Page 31 Network Specific — PROFINET 29 (38) Attribute 30-series 40-series Change/Action/Comment #7, Record Data See Comment I&M Record data transparent mode (bit 1) is Mode replaced with the IM_Options command in the Network PROFINET IO object (0Eh). If this bit is 0 in the current implementation, no action is needed #13, I&M Profile ID Used for all APIs...
-
Page 32: Profinet Additional Diagnostic Object (0Fh)
Network Specific — PROFINET 30 (38) Command 30-series 40-series Change/Action/Comment Ar_Info_Ind Available Removed Command removed in the 40-series. The Any- bus CompactCom will never use this com- mand in a request. The command is replaced by the command Expected_Ident_Ind Ar_Offline_Ind Available Removed Command removed in the 40-series. -
Page 33: Network Configuration Object (04H)
Network Specific — PROFINET 31 (38) 13.5 Network Configuration Object (04h) The instances in the Network Configuration Object have been rearranged for the Ethernet based modules for consistency. Network specific instances are moved to instance number 20 and onwards. This is done to increase the number of instances in the section that is not network specific. -
Page 34: Led Indications
Network Specific — PROFINET 32 (38) 13.8 LED Indications Changes has been made regarding the specification of the LED indications. See tables below for differences. Fig. 6 13.8.1 Network Status LED (LED1[A..B]) LED State 30-series 40-series Comments Offline Offline - No power- No connection with IO controller Green Online (RUN) -
Page 35: Snmp Mib-Ii
Network Specific — PROFINET 33 (38) 13.8.2 Module Status LED (LED2[A..B]) LED State 30-series 40-series Comments Not Initialized Not Initialized No power or Module in SETUP or NW_INIT state Green Normal Operation Normal Operation Module has shifted from the NW_IN- IT state Green, 1 flash Diagnostic Event... -
Page 36: Adi Based Configuration
Network Specific — PROFINET 34 (38) 13.10 ADI Based Configuration When using the ADI based configuration, the structure of module identifiers and submodule identifiers are changed in the 40-series to be able to support the re-map functionality. 13.10.1 30-series (2-Port) DAP V2.0: Module ID: 0x00000011, Submodule ID: 0x00000001 Modules: Fixed module IDs for different data sizes and data directions... -
Page 37: Configuration Mismatch
13.13.1 GSD Generator Tool When using the ADI-based configuration, it is possible to use a GSD Generator from HMS which will generate a basic GSD file (up to date with the above differences) with correct ADI modules. The GSD generator only works for the 40-series The generator can be downloaded from www.anybus.com/starterkit40... - Page 38 Modifications for Conformance Class B (if you want to disable support for IRT) The example GSD file, supplied by HMS Industrial Networks AB, is prepared for testing an Any- bus CompactCom 40 PROFINET IRT for conformance class C, which includes PROFINET iso- chronous communication mode (IRT).
- Page 39 Network Specific — PROFINET 37 (38) 13.13.3 Keywords Keyword Comments GSDML-DeviceProfile version 2.31 for 30-series, 2.32 for 40-series DeviceIdentity->DeviceID Must be changed to reflect the Device ID you have configured in the PROFINET IO object (F6h), Attribute 1. DeviceAccessPointItem->CheckDeviceID_ False for 30-series, true for 40-series Allowed DeviceAccessPointItem- NP30 for 30-series, NP40 for 40-series...
- Page 40 © 2017 HMS Industrial Networks AB Box 4126 300 04 Halmstad, Sweden info@hms.se SCM-1202-043 1.1.4546 / 2017-06-27T06:45:17...
Need help?
Do you have a question about the Anybus CompactCom 30 and is the answer not in the manual?
Questions and answers