background image

Migrating from Anybus

®

CompactCom

30

to Anybus

®

CompactCom

40

DESIGN GUIDE

SCM-1202-043 1.1

ENGLISH

Summary of Contents for Anybus CompactCom 30

Page 1: ...Migrating from Anybus CompactCom 30 to Anybus CompactCom 40 DESIGN GUIDE SCM 1202 043 1 1 ENGLISH ...

Page 2: ...andards 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 ...

Page 3: ... 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 Stat...

Page 4: ...ific 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 Addit...

Page 5: ...h 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 PROFINETconfiguration file used by engineering tool 35 ...

Page 6: ...This page intentionally left blank ...

Page 7: ...m 40 Software Design Guide HMS HMSI 216 125 Anybus CompactCom M40 Hardware Design Guide HMS HMSI 216 126 Anybus CompactCom Host Application Implementation Guide HMS HMSI 27 334 Anybus CompactCom 40 Network Guides HMS Anybus CompactCom 30 Network Guides HMS PROFINET Installation Guideline for Cabling and Assembly PI The network guides for the industrial networks mentioned in this document as well a...

Page 8: ...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...

Page 9: ...gistered 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 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 ...

Page 10: ...ctCom 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 IIoTsolutions and advanced security features w...

Page 11: ... is compatible with the 40 series modules Small modifications to your cur rent 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 hard...

Page 12: ...e 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 Anybu...

Page 13: ...d a separate brick version in the 40 series that can be used for migration This product B40 2 shares dimensions etc with the B30 Please contact HMS Industrial Networks AB for more information on the Anybus CompactCom B40 2 Fig 2 Anybus CompactCom B30 Fig 3 Anybus CompactCom B40 1 not for migration Fig 4 Anybus CompactCom B40 2 Migrating from Anybus CompactCom 30 to Anybus CompactCom 40 Design Guid...

Page 14: ... Z digital input on the host processor it will be compatible with the 40 series An external pull up is recommended but not required If this pin is pulled low by the host during startup the 40 series module or brick will not enter the expected operating mode Related Information Anybus CompactCom M40 Hardware Design Guide HMSI 216 126 Sec tion Application Connector Pin Overview 4 4 2 Module Identifi...

Page 15: ...ion Anybus CompactCom M40 Hardware Design Guide HMSI 216 126 Sec tion LED Interface D8 D15 Data Bus 4 4 4 GOP 0 1 LED4 A B These pins are outputs high state by default in the 30 series In the 40 series these pins are tri stated until the state NW_INIT and after that they become push pull active low LED outputs LED4A LED4B This change should not affect your product Related Information Anybus Compac...

Page 16: ...ations parallel operating mode may see increased CPU load due to the increased speed 5 3 Requests from CompactCom to Host Application During Startup All requests to software objects in the host application must be handled and responded to even if the object does not exist This applies for both the 30 series and the 40 series The 40 series introduces additional objects for new functionality There m...

Page 17: ...ompactCom 30 example drivers from HMS comply with this difference Related Information Anybus CompactCom 40 Software Design Guide HMSI 216 125 section Status Register 5 7 Control Register CTRL_R bit 30 series The application may change this bit at any time 40 series For the 8 bit parallel operating mode the bit is only allowed to transition from 1 to 0 when the STAT_M bit is set in the status regis...

Page 18: ... SMTP Server 16 13 SMTP User 17 14 SMTP Password 18 15 Foreign Device Registration IP 19 23 Foreign Device Registration UDP Port 20 24 Foreign Device Registration Time to Live Value 21 25 6 2 Reduced Network Resources Due to Memory Constraints The Anybus CompactCom 40 BACnet IP will have reduced network resources compared to the AnybusCompactCom 30 due to memory constraints Network Resource 30 ser...

Page 19: ...all other data types for the data to be mapped to the Bit area If mapping bit data after having mapped other non bit data the data will be mapped to the Word area The change was made to get a more logical and faster mapping You need to make sure the process data is mapped according to the above in the host application 7 3 Diagnostic Object 02h To use the Diagnostic Events in conjunction with the a...

Page 20: ...ault value is used 6 Product Name Default Any bus CC DeviceNet Default Com pactCom 40 De viceNet TM 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 If the attribute is not implemented the default value is used 8 2 EDS file Electronic Datasheet file used by configuration tool 8 2 1 Keywords Th...

Page 21: ...ttribute 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 If the attribute is not implemented the default value is used 9 3 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 availab...

Page 22: ...ut Timeout StateMachine The sync manager start addresses have been changed in the 40 series and the sync manager sizes are now configurable in the EtherCATconfiguration tool Sm MinSize 34 MaxSize 1486 DefaultSize 276 StartAddress x4000 ControlByte x26 Enable 1 MBoxOut Sm Sm MinSize 34 MaxSize 1486 DefaultSize 276 StartAddress x4800 ControlByte x22 Enable 1 MBoxIn Sm Sm StartAddress x2800 ControlBy...

Page 23: ... the 40 series If the attribute is not implemented the default value is used 002Eh 30 series EtherNet IP Announce Based DLR 0036h 30 series EtherNet IP Beacon Based DLR 0037h 40 series EtherNet IP Beacon Based DLR 6 Product Name Anybus CC EtherNet IP 30 series EtherNet IP No DLR If the attribute is implemented in the host application it overrides the de fault value and there is no difference betwe...

Page 24: ...enerator Tool An EDS generator for automatic EDS file generation up to date with the differences below The EDS generator only works with the 40 series version 1 30 and later The generator can be downloaded from www anybus com starterkit40 10 3 2 Keywords The following keywords differs between the 30 series and the 40 series The EDS generator re flects this change Keyword Comments Capacity MaxCIPCo...

Page 25: ...Fh 1010h 101Fh ADI Number 2 0220h 022Fh 1020h 102Fh ADI Number 3839 FFF0h FFFFh Input Registers 3x Write Process Data 0000h 00FFh 0000h 02FFh Diagnostic Event Count 0100h 0800h Diagnostic Event 1 0101h 0801h Diagnostic Event 2 0102h 0802h Diagnostic Event 3 0103h 0803h Diagnostic Event 4 0104h 0804h Diagnostic Event 5 0105h 0805h Diagnostic Event 6 0106h 0806h Coils 0x Read Process Data 0000h 0FFF...

Page 26: ...there is no difference between the 30 series and the 40 series If the attribute is not implemented the default value is used 11 Modbus read write registers com mand offset In the 30 series this register address offset is only applied when accessing holding regis ters with the command Read Write Multiple registers 23 The 40 series applies this register offset to all holding register access i e comm...

Page 27: ...in the 40 series The Any bus CompactCom will never request this attribute Nothing needs to be changed 6 Buffer Mode Available Removed Attribute removed in the 40 series The Any bus CompactCom will never request this at tribute No buffer modes needed in the 40 series since maximum sizes for all buffers are supported Nothing needs to be changed 7 Alarm Settings Available Removed Attribute removed in...

Page 28: ... configuration file used by engineering tool Implementation Type If the keyword Implementation Type is present in the GSD file optional keyword the value for the 30 series shall be NP30 and the value for the 40 series shall be NP40 Length Related Keywords The following keywords are possible to set to maximum values if neeed in the 40 series In the 30 series the maximum lengths were dependent of th...

Page 29: ...ries module has PROFINET IRTcapabilities The Net work Type value differs between the different CompactCom PROFINET versions 0096h 30 series PROFINET IO 2 Port 0089h 40 series PROFINET IRT 2 Network Type String PROFINET IO 30 series PROFINET IO 1 Port The 30 series module is a PROFI NET RT module without IRTcapabil ities The 40 series module has PROFINET IRTcapabilities The Net work Type value diff...

Page 30: ...rs between the different CompactCom PROFINET types ABCC PRT 2 Port 30 series PROFINET IO 2 Port ABCC40 PIR 40 series PROFINET IRT 8 I M Or der ID ABCC PRT 30 series PROFINET IO 1 Port If the attribute is implemented in the host application it overrides the de fault value and there is no difference between the 30 series and the 40 series If the attribute is not implemented the default value differs...

Page 31: ...e 40 series The Any bus CompactCom will never request this at tribute The host application cannot influence the I M implemented by the Anybus CompactCom 16 I M Supported Available Removed Attribute removed in the 40 series The Any bus CompactCom will never request this at tribute The host application cannot influence the I M supported by the Anybus CompactCom 20 Interface description Available Rem...

Page 32: ...ill use the general Get_ Record command instead filter on index AFF0h AFFFh Set_IM_Record Available Removed Command removed in the 40 series The Any bus CompactCom will never use this com mand in a request It will use the general Set_ Record command instead filter on index AFF0h AFFh 13 3 PROFINET Additional Diagnostic Object 0Fh Object removed in the 40 series All diagnostics are handled via the ...

Page 33: ...r removed The following instances are removed in the 40 series They are only possible to set via the network Instance 16 in 30 series Function Tag Instance 17 in 30 series Location Tag Instance 18 in 30 series Installation Date Instance 19 in 30 series Description 13 6 Network PROFINET IO Object 0Eh Attribute 30 series 40 series Change Action Comment 3 Last OffLineInd ReasonCode Removed Attribute ...

Page 34: ...stab lished IO controller in STOP state or IO data bad IRTsynchronization not finished Green 3 flashes Identify Flashing 3 times 1Hz continuously to identify slave DCP_Identify Green cont flash Online STOP Connection with IO controller estab lished IO controller in STOP state Red Fatal event Fatal event Major internal error this indication is combined with a red module status LED Red 1 flash Stati...

Page 35: ... 2 flashes IP address error Red 3 flashes Station Name Error Red 4 flashes Internal error Alternating Red Green Firmware Update Do NOT power off the module Turn ing the module off during this phase could cause permanent damage 13 9 SNMP MIB II sysContact sysLocation and sysName are used to give the product identification in the end installation In the 40 module these variables are only set from th...

Page 36: ...ubmodule ID 0x00000000 Output 4 word Module ID 0x00000050 Submodule ID 0x00000000 Input 1 byte Module ID 0x00000002 Submodule ID 0x00000000 Input 1 word Module ID 0x00000003 Submodule ID 0x00000000 Input 2 word Module ID 0x00000004 Submodule ID 0x00000000 Input 4 word Module ID 0x00000005 Submodule ID 0x00000000 One submodule per module 13 10 2 40 series DAP Module ID 0x80010000 Submodule ID 0x000...

Page 37: ...HMSI 168 74 Section Configura tion Mismatch For detailed information about how a configuration mismatch is handled in the 40 series see Anybus CompactCom 40 PROFINET IRT Network Guide HMSI 27 226 Section Configuration Mismatch 13 12 Media Redundancy Protocol MRP MRP is supported in the 40 series and cannot be disabled by the host application You need to add new keywords in your GSD file see GSD se...

Page 38: ...ing an IRTcapable switch or placed at the end of the line 1 1 The value of the ConformanceClass attribute in the CertificationInfo ele ment in each DAP must be changed from C to B CertificationInfo ConformanceClass B ApplicationClass NetloadClass III 2 The value of the SupportedRT_Classes attribute in the InterfaceSubmoduleItem element in each DAP must be RT_CLASS_1 I e the RT_CLASS_2 and RT_ CLAS...

Page 39: ...ries VirtualSubmoduleItem API Removed in 40 series API 0 default VirtualSubmoduleItem IOData IOPS_ Length Removed in 40 series Default 1 VirtualSubmoduleItem IOData IOCS_ Length Removed in 40 series Default 1 VirtualSubmoduleItem Writeable_IM_ Records 1 2 3 4 in 30 series 1 2 3 in 40 series VirtualSubmoduleItem MayIssueProcessAlarm Mandatory for 2 32 False in 40 series InterfaceSubmoduleItem PTP_ ...

Page 40: ...last page 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 ...

Reviews: