1. Manuals
  2. Brands
  3. Anybus Manuals
  4. Conference System
  5. CompactCom M40
  6. Manual

Anybus CompactCom M40 Manual

Hardware design guide
Hide thumbs Also See for CompactCom M40:
Table of Contents

Advertisement

Quick Links

See also: Network Manual
®
Anybus
CompactCom
M40
™
HARDWARE DESIGN GUIDE
HMSI-216-126 EN 2.6 ENGLISH

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CompactCom M40 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Anybus CompactCom M40

Summary of Contents for Anybus CompactCom M40

  • Page 1 ® Anybus CompactCom ™ HARDWARE DESIGN GUIDE HMSI-216-126 EN 2.6 ENGLISH...
  • Page 2 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. ® Anybus CompactCom ™ M40 Hardware Design Guide...

  • Page 3: Table Of Contents

    A Implementation Examples ..................43 General........................43 Design Considerations ....................43 Serial and 16–bit Parallel ....................44 8–bit/16–bit Parallel .....................45 8–bit Parallel .......................46 SPI and Serial......................47 Network Status LED Outputs (LED[1A...4B]) ..............48 Power Supply Considerations ..................49 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 4 M12 Connector ......................87 Footprint ........................88 Housing Preparations....................89 Slot Cover ........................90 Host Connector......................91 Fastening Mechanics ....................95 E Anybus CompactCom 40 without Housing ............97 General Information .....................97 Ordering Information ....................98 Footprint ........................99 Host Connectors ......................100 Height Restrictions..................... 100 Assembly ........................101 Dimensions .......................

  • Page 5: Preface

    This document is intended to provide a good understanding of the mechanical and electrical properties of the Anybus CompactCom platform. It does not cover any of the network specific features offered by the Anybus CompactCom 40 products; this information is available in the appropriate Network Guide.

  • Page 6: Document 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.

  • Page 7: Trademark Information

    Signals which are “tied to GND” are directly connect GND, • Signals which are “tied to 3V3” are directly connected to 3V3. Trademark Information Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders.

  • Page 8: Introduction

    All Anybus CompactCom module implementations share the same footprint and electrical interface, allowing the host application to support all major networking systems using the same hardware platform. In the same way all Anybus CompactCom B40-1 share footprint and electrical interface. This document describes the hardware details of the Anybus CompactCom M40 modules, both with and without housing.

  • Page 9: M12 Connector

    However, the standard Anybus CompactCom housing does not qualify for IP ratings above IP20. If a higher rating is needed, careful design of housings and/or module fronts is necessary. It is then recommended to use the Anybus CompactCom M40 without housing, and design a new housing/front that fulfills the requirements for IP67.

  • Page 10: Host Interface

    Host Interface 8 (114) Host Interface This chapter describes the low level properties of the Anybus CompactCom interface Overview The Anybus CompactCom has five different host communication interfaces, corresponding to different operating modes. The figure below illustrates the basic properties of these interfaces as well as various I/O and control signals, and how they relate to the host application.
  • Page 11 The serial interface is provided for backward compatibility with the Anybus CompactCom 30. The interface is event based, and it is not recommended to use it with an Anybus CompactCom M40 module as it can not take advantage of the greater performance of the 40-series. For more information about the serial interface, see the Anybus CompactCom M30 Hardware Design Guide.

  • Page 12: Connector

    Host Interface 10 (114) Connector The Anybus CompactCom uses a 50–pin CompactFlash style connector. The pinning is seen ™ form the host application side of the Anybus CompactCom module (MD1) (GND) (GND) (MD0) Fig. 2 .Application Connector Pin Overview, p. 11 for information on how each pin is used in the different modes.
  • Page 13 Depending on operating mode, the pins have different names and different functionality. Presented below is an overview of all pins except GND and 3V3. The ASI (Anybus Safety Interface) signals are used by a safety module to connect to the safety module interface of an Anybus CompactCom M40 series module.
  • Page 14 Connected to GND Connected to GND RESET RESET RESET RESET RESET 3.2.2 Power Supply Pins Signal Name Type Description Power Power and signal ground reference. Power 3.3 V power supply. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 15 O / I/O D14 in 16-bit data bus mode • Yellow or red, depending on network • Mainly used for link/ activity on network port 2 on the EThernet modules (yellow) ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 16 LED2A/LED2B LED3A/LED3B LED4A/LED4B Anybus CompactCom M40 modules not supporting Ethernet have two LEDs on the front. The picture shows the module front of the Anybus CompactCom M40 DeviceNet, but other modules, e.g. PROFIBUS, have LEDs in the corresponding positions. Fig. 4...
  • Page 17 These signals can be used by the host application to determine that an Anybus CompactCom is inserted into the slot, see Module Detection, p. The signals are connected directly to GND on the Anybus CompactCom. ASI RX Black Channel Communication ASI TX These signals can be connected to a safety module, e.g.
  • Page 18 These signals must be stable prior to releasing the RESET signal. Failure to observe this may result in faulty behavior. In an application, where it has to be possible to change an Anybus CompactCom M30 module for an Anybus CompactCom M40 module, there should be an external pull-up on the OM3 pin to ensure correct and stable behavior.
  • Page 19 Interrupt Request Active low interrupt signal. The interrupt request signal is active low. It is asserted by the Anybus CompactCom after a power up or a hardware reset event. . The use of this signal is optional but highly recommended. Even if the host application lacks interrupt capabilities, it is recommended to connect this signal to an input port to simplify software design.
  • Page 20 Time until the power supply is stable after power-on; the duration depends on the power supply design of the host application and is thus beyond the scope of this document. Safety margin. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 21 The reset pulse duration must be at least 10 µµs in order for the NP40 to properly recognize a reset. RESET Fig. 6 Symbol Min. Max. Definition 10 µs Reset pulse width. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 22: Parallel Interface Operation

    3.3.1 General Description The parallel interface is based on an internal memory architecture, that allows the Anybus CompactCom module to be interfaced directly as a memory mapped peripheral. The M40 modules can be configured for 8-bit or 16-bit parallel operation. The access time is 30 ns.
  • Page 23 RESET RESET (Reset Input), p. Applications with limited number of address lines may connect A[0..10] of the Anybus CompactCom to their CPU, and pull signals A[11..13] high. This will allow communication with the Anybus CompactCom using the smaller message format of the Anybus CompactCom 30 series, with a reduced set of address lines, allowing access to only 256 byte process data, see the Anybus CompactCom 30 Software Design Guide for more information.
  • Page 24 Black Channel/Safety Module, p. 41 Module Detection, p. RESET RESET (Reset Input), p. 18". Applications with limited number of address lines may connect A[0..10] of the Anybus CompactCom to their CPU, and pull signals A[11..13] high. This will allow communication with ® Anybus CompactCom ™...
  • Page 25 23 (114) the module using the smaller message format of the Anybus CompactCom 30 series, with a reduced set of address lines, allowing access to only 256 byte process data, see the Anybus CompactCom 30 Software Design Guide for more information.
  • Page 26 The WE input signal must remain high during a read access. The timing diagram shows a burst read, but the timing applies for a single read as well. The Anybus CompactCom M40 has no setup or hold timing requirements on the address bus relative to CS during read operations.
  • Page 27 Max (ns) Write cycle time Address valid before End-of-Write Address valid after End-of-Write CS and WE low pulse width Data valid before End-of-Write Data valid after End-of-Write Write recovery time ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 28: Spi Operation

    Presented below is an overview of all pins except GND and 3V3. Signal Name Type Description/Comments DIP1_0 DIP switch. Usage defined by application. DIP1_1 Readable through attribute #14 (Switch status) in Anybus Object, instance #1. DIP1_2 Connect to GND if not used. DIP1_3 DIP1_4 DIP1_5...
  • Page 29 Master input, slave output. Input to the master’s shift register, and output from the slave’s shift register. Slave Select (optional) For increased efficiency, the interrupt request signal (IRQ) is also available, allowing the host application to service the Anybus CompactCom only when necessary. ® Anybus CompactCom ™...
  • Page 30 In 4-wire mode the SS signal is used to indicate the start and stop of an SPI transfer. In this mode the SCLK signal is allowed to be either idle high or idle low. This mode also allows multiple SPI slaves on the same SPI bus, since Anybus CompactCom MISO is tri-stated when SS is high.
  • Page 31 Most bytes are transmitted with the most significant bit first, but the byte order is little endian. The least significant byte is transmitted first. The only exception is the CRC32 checksum field that is transmitted in big endian order. ® Anybus CompactCom ™ M40 Hardware Design Guide...

  • Page 32: Stand-Alone Shift Register

    ADI #33 Fig. 15 Even though the Anybus CompactCom M40 operates stand-alone, it is still possible to set host application attributes, via the use of the virtual attributes list. Some attributes are mandatory to implement in order to pass conformance tests See the Virtual Attributes section in the Anybus CompactCom 40 Software Design Guide for more information.
  • Page 33 Anybus CompactCom M40 is not in state PROCESS ACTIVE. Otherwise it will not be possible to certify the final product. See the Anybus CompactCom 40 PROFINET IRT Network Guide for more information.
  • Page 34 DIP2 is linked to the Network Configuration Object, instance 2 (baud rate) or instance 1 (Device ID, EtherCAT), or, in the case of PROFINET, linked to the PROFINET IO Object , instance 1, attribute 24. See Network Configuration Object (04h) in the Anybus CompactCom 40 Software Design Guide for more information. Network...
  • Page 35 The DIP2 switches set the last three digits of the station name. see the Anybus CompactCom 40 PROFINET IRT Network Guide. CC-Link 1 - 64 (Instance 1: Node Value: 0 - 4 (Network DIP1: Depending on number of address).
  • Page 36 Host Interface 34 (114) 3.5.3 Timing The Anybus CompactCom M40 operates in 12.5 MHz in shift register mode. Timing Diagram Fig. 17 Abbreviations from the diagram above, explained, and timing details: Item Description Min Value tSUO DO setup before SCK rising edge...
  • Page 37 (Pin 44) I0 D5 I0 D6 SR CLK (Pin 20) I0 D7 Input byte 0 SR LD_N (Pin 45) SR CT (Pin 34) SR DI (Pin 19) 74LV165/SO Fig. 18 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 38 DIP Switches Example Pull-down resistors are necessary if DIP switches are connected to the DIP inputs. DIP[1_0 .. 1_7] DIP1_1 DIP1_2 DIP1_3 DIP1_4 DIP1_5 DIP1_6 DIP1_7 DIP switches Fig. 20 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 39: Uart Operation

    General Description The serial interface is a common asynchronous serial interface, which can easily be interfaced directly to a microcontroller or UART. It is provided for backward compatibility with the Anybus CompactCom 30 series. The serial interface is activated using the OM[0...3] inputs, which also are used to select the operating baud rate, see Operating Modes, p.
  • Page 40 Presented below is an overview of all pins except GND and 3V3 Signal Name Pin Type Description/Comments DIP1_0 DIP switch. Usage defined by application. DIP1_1 Readable through attribute #14 (Switch status) in Anybus Object, instance #1. DIP1_2 Connect to GND if not used. DIP1_3 DIP1_4 DIP1_5...
  • Page 41 3.6.3 Baud Rate Accuracy As with most asynchronous communication devices, the actual baud rate used on the Anybus CompactCom may differ slightly from the ideal baud rate. The baud rate error of the module is less than ±1.5%. For proper operation, it is recommended that the baud rate accuracy in the host application lies within ±1.5% from the ideal value.

  • Page 42: Emc

    Bypass Capacitance, p. The capacitors have impact on the power quality at the Anybus CompactCom board, but are also of importance in relation to EMC immunity. These general recommendations should be evaluated for every design. The values may also need to be adjusted in relation to power consumption, power quality on the main board, and the layout of the main board.

  • Page 43: Black Channel/Safety Module

    I/O signals into standard automation devices. It connects via its serial black channel interface to the Anybus CompactCom. The safety module provides digital safe I/O signals that can be controlled via the network and that can be directly connected to the safety functions of an automation device.
  • Page 44 This page intentionally left blank...

  • Page 45: A Implementation Examples

    It is recommended for Anybus CompactCom M40 users to make sure that each signal controlling the Anybus CompactCom M40 has a drive strength enough to fulfill level and timing constraints even if the signal is loaded with 20 pF in parallel with 2.2 kΩ to GND or 3V3.

  • Page 46: Serial And 16-Bit Parallel

    The example in the figure below shows an implementation with serial communication and firmware update (via UART). An Anybus CompactCom 30, connected as shown, can thus be used in serial mode and is prepared for firmware update via the UART. Exchanging the M30 for the M40 will also give access to 16-bit parallel mode.

  • Page 47: 8-Bit/16-Bit Parallel

    48, for guidelines on how to connect the LED outputs. In 16-bit parallel mode it is not possible to use these outputs for LEDs. In this implementation, the LED outputs on the Anybus CompactCom M30 module are protected by external circuitry (74B3T3245, a SN74CB3T3245, 8-BIT FET BUS SWITCH is suggested).

  • Page 48: 8-Bit Parallel

    If LEDs are to be used in the host application, please refer to Network Status LED Outputs (LED[1A...4B]), p. 48, for guidelines on how to connect the LED outputs. The pull-down resistors on LED3A and LED3B make it possible to support Anybus CompactCom passive modules. ® Anybus CompactCom ™...

  • Page 49: Spi And Serial

    (using a UART). If the M30 is exchanged for a M40 the SPI interface will also be available. Firmware update for a M40 series module is preferably done using the File System Interface Object, see Anybus CompactCom 40 Software Design Guide. M30 pinning / M40 pinning [A0... A7] / (not used)

  • Page 50: Network Status Led Outputs (Led[1A

    LED1B LED1A *By connecting this signal to Ground, this design can be used to support Anybus CompactCom passive modules. Fig. 26 These pins can not be used for LEDs in 16-bit parallel mode, as the pins in that case are used for data.

  • Page 51: Power Supply Considerations

    A.8.1 General The Anybus CompactCom 40 platform in itself is designed to be extremely power efficient. The exact power requirements for a particular networking systems will however vary a lot depending on to the components used in the actual bus circuitry.
  • Page 52 (16V) 10uH SHDN 22uF 100nF (6.3V) (16V) 1,5nF (50V) 10uF (6.3V) SS14 Fig. 28 For detailed information regarding this example, consult the data sheet for the LT1767 (Linear Technology). ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 53: B Backward Compatibility

    B.1.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.
  • Page 54 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.

  • Page 55: Hardware Compatibility

    Anybus CompactCom M30/M40 B.3.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.
  • Page 56 B.3.3 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 developed a separate brick version in the 40-series, that can be used for migration. This product, B40-2, shares dimensions etc.
  • Page 57 Related Information: Anybus CompactCom M40 Hardware Design Guide (HMSI-216-126), Section “Application Connector Pin Overview” Module Identification (MI[0..1]) These pins are used by the host application (i.e your product) to identify what type of Anybus CompactCom that is mounted. The identification differs between the 30-series and the 40- series.
  • Page 58 In the 40-series, there is a possibility to set the GIP[0..1] and GOP[0..1] in high impedance state (tri-state) by using attribute #16 (GPIO configuration) in the Anybus object (01h). I.e. if it is not possible to change the host application hardware, this attribute can be configured for high impedance state of GIP and GOP before leaving NW_INIT state.
  • Page 59 57 (114) RMII Compatibility If the RMII mode is being used on an Anybus CompactCom 40 module and it is desired to remain compatible with the 30 series, it is important to disable this connection when switching to an Anybus CompactCom 30 module due to pin conflicts. The RMII port of the host processor should be set to tristate by default, and only be enabled if an RMII capable Anybus CompactCom 40 is detected.

  • Page 60: General Software

    Memory areas not supported by the specific network cannot be used. Make sure you do not access these areas, e.g. for doing read/write memory tests. Related Information: Anybus CompactCom 40 Software Design Guide (HMSI-216-125), Section “Memory Map” B.4.2 Faster Ping-Pong Protocol The ping-pong protocol (the protocol used in the 30-series) is faster in the 40-series.
  • Page 61 B.4.5 Control Register CTRL_AUX-bit 30-series The CTRL_AUX bit in the control register indicates to the Anybus CompactCom if the process data in the current telegram has changed compared to the previous one. 40-series The value of the CTRL_AUX bit is always ignored. Process data is always accepted.

  • Page 62: Network Specific - Bacnet/Ip

    Foreign Device Registration UDP Port Foreign Device Registration Time to Live Value B.5.2 Reduced Network Resources Due to Memory Constraints The Anybus CompactCom 40 BACnet/IP will have reduced network resources compared to the Anybus CompactCom 30 due to memory constraints. Network Resource 30-series...

  • Page 63: Network Specific - Cc-Link

    To use the Diagnostic Events in conjunction with the automatic System Area Handler (CC-Link Host Object (F7h), Attribute #5, System Area Handler) in the Anybus CompactCom 40 CC-Link, there is one modification required. The application is now required to use the Diagnostic Events with the severity representing Latching Events or handle the system area completely in the application.

  • Page 64: Network Specific - Devicenet

    30-series and the 40-series. If the attribute is not implemented, the default value is used. #6, Product Name Default: “Anybus- Default: If the attribute is implemented in the host CC DeviceNet” “CompactCom 40 application, it overrides the default value and DeviceNet(TM)”...

  • Page 65: Network Specific - Ethercat

    An ESI-file generator is available on the HMS Industrial Networks AB website. The generator will create an up to date ESI file fitted for the specific design. The ESI generator works for both the 30-series and the 40-series. The generator can be downloaded from www.anybus.com/starterkit40. ® Anybus CompactCom ™...
  • Page 66 Since the 40-series is using the HMS slave controller, the EEPROM byte size and the SII configuration data must be changed according to the following settings. <ByteSize>384</ByteSize> <ConfigData>80360046F4010000000000000000</ConfigData> The 40-series supports the boot strap state, and requires the following keyword. <BootStrap>0040000400480004</BootStrap> ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 67: Network Specific - Ethernet/Ip

    DLR” (Highest performance) or with “Announce based DLR” which both are Ethernet redundancy protocols. The 40-series is only available with “Beacon based DLR”. The network type value differs between the versions. Value Network Type Anybus CompactCom Product 0085h EtherNet/IP, No DLR 30-series 1-port 009Ch...
  • Page 68 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: . Keywords The following keywords differs between the 30-series and the 40-series. The EDS generator reflects this change.

  • Page 69: Network Specific - Modbus-Tcp

    Process data mapped BOOL arrays are not compressed to bit-fields on the network in the 40- series, but handled as a normal 8-bit datatype. To create bit-arrays in the 40-series, use the new datatypes BITx instead. ® Anybus CompactCom ™ M40 Hardware Design Guide...
  • Page 70 40-series Change/Action/Comment #4, Enable Modbus- Available Removed Attribute removed in the 40-series. The Anybus CompactCom will never request this attribute. Nothing needs to be changed in the host application. B.10.6 Process data In the 30-series modules, writing to the ADI register area would only result in a Set_Attribute command to the application (Application Data Object (FEh)) if the ADI was not mapped to read process data.

  • Page 71: Network Specific - Profibus

    #16, I&M Version Available Removed Attribute removed in the 40-series. The Anybus CompactCom will never request this attribute. The host application cannot influence the I&M version implemented by the Anybus CompactCom. #17, I&M Supported Available Removed Attribute removed in the 40-series. The Anybus CompactCom will never request this attribute.
  • Page 72 70 (114) B.11.4 Network Configuration Object (04h) The following attributes are removed in the 40–series. The Anybus CompactCom will never request these attributes. It is only possible to set these values via the network (I&M1-4) – end user configuration. •...

  • Page 73: Network Specific - Profinet

    Appendix B: Backward Compatibility 71 (114) B.12 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 B.12.1 Network Object (03h) Attribute Default Anybus CompactCom Product...
  • Page 74 Appendix B: Backward Compatibility 72 (114) B.12.2 PROFINET IO Object (F6h) Attribute Default Anybus CompactCom Product Comment #1, Device ID 0007h 30-series, PROFINET IO 1-Port The Device ID controls how your product identifies itself on the 0009h 30-series, PROFINET IO 2-Port PROFINET network.
  • Page 75 In the 30-series this parameter is used for all API:s. #15, I&M Version Available Removed Attribute removed in the 40-series. The Anybus CompactCom will never request this attribute. The host application cannot influence the I&M implemented by the Anybus CompactCom. 16, I&M Supported...
  • Page 76 30-series 40-series Change/Action/Comment Ar_Info_Ind Available Removed Command removed in the 40-series. The Anybus CompactCom will never use this command in a request. The command is replaced by the command Expected_Ident_Ind Ar_Offline_Ind Available Removed Command removed in the 40-series. The Anybus CompactCom will never use this command in a request.
  • Page 77 I&M4 is removed in the 40-series. Writeable I&M records in GSD must be updated (see GSD section below). B.12.8 LED Indications Changes has been made regarding the specification of the LED indications. See tables below for differences. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 78 Red, 1 flash Station Name error Station name not set Red, 2 flashes IP address error IP address not set Red, 3 flashes Configuration error Expected Identification differs from Real Identification. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 79 Configuration Object (04h), Attribute 17) and sysName (Network Configuration Object (04h), Attribute 15) are no longer used. Nothing needs to be updated in your implementation but attribute values will no longer be used. ® Anybus CompactCom ™ M40 Hardware Design Guide...
  • Page 80 Module ID: Submodule ID: 0: Mapped to write PD area Number of ADI start ADI number 1: Mapped to read PD area elements to map element number Fig. 35 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 81 Anybus CompactCom 30 PROFINET IO Network Appendix, HMSI-168-74, Section “Configuration 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”. B.12.12 Media Redundancy Protocol (MRP) MRP is supported in the 40-series and cannot be disabled by the host application.
  • Page 82 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 Anybus CompactCom 40 PROFINET IRT for conformance class C, which includes PROFINET isochronous communication mode (IRT). If the implementation does not need the isochronous features of the device, the GSD file can be modified to reflect this.
  • Page 83 New MRP keyword in the 40-series. MRP not supported in 30- series. IsDefaultRingport="true" New MRP keyword in the 40-series. MRP not supported in 30- series. VirtualSubmoduleItem->Writeable_IM_ I&M4 removed in the 40-series Records="1 2 3" ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 84: C Technical Specification

    Appendix C: Technical Specification 82 (114) Technical Specification The properties specified in this chapter apply to all Anybus CompactCom M40 modules unless otherwise stated. Any deviations from what is stated in this chapter is specified separately in each network appendix.

  • Page 85: Electrical Characteristics

    C.3.3 Functional Earth & Shielding All Anybus CompactCom modules features a cable shield filter designed according to each network standard. To be able to support this, the host application must have a conductive area connected to functional earth as described in Mechanical Specification, p.

  • Page 86: Regulatory Compliance

    EMC directive in that installation. Once the end product has successfully passed the EMC test using any of the Anybus CompactCom modules, the precompliance test concept allows any other interface of the same type in the Anybus CompactCom family to be embedded in that product without further EMC tests.

  • Page 87: D Mechanical Specification

    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 ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 88: Overview

    The dimensions below are given in millimeters and include a tolerance of ±0.20 mm. 18.9 18.1 Grounding (GND) Mechanics Functional Earth (FE) Mechanics Fastening Mechanics 42.1 50.1 22.3 Fig. 36 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 89: M12 Connector

    The modules that are equipped with M12 connectors, either have two female connectors or one female and one male connector. The dimensions below are given in millimeters and include a tolerance of ±0.10 mm. 50,1 Fig. 37 50,1 Fig. 38 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 90: Footprint

    Under no circumstances may components, via holes, or signal lines, be placed on the PCB-layer facing the Anybus module. Failure to comply with this requirement may induce EMC/EMI problems, mechanical compatibility issues, or even short circuit.

  • Page 91: Housing Preparations

    Appendix D: Mechanical Specification 89 (114) Housing Preparations The dimensions below are given in millimeters and include a tolerance of ±0.10 mm. Fig. 40 Fig. 41 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 92: Slot Cover

    HMS Industrial Networks AB can supply a “blind” slot-cover, which may be used to cover the Anybus CompactCom slot when not in use, allowing the Anybus CompactCom module to be supplied as an end-user option instead of being mounted during manufacturing.

  • Page 93: Host Connector

    HMS Industrial Networks AB offers a host connector, that is designed to simplify the mounting and to meet the demands for a secure and stable connection of the Anybus CompactCom modules. The dimensions of the connector and the information needed for the PCB layout are presented in the figure on the next page.
  • Page 94 Appendix D: Mechanical Specification 92 (114) Fig. 45 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 95 Fig. 47 It is recommended to use connectors which can be screwed into the host application board, to minimize mechanical strain on solder joints etc. The following connectors have been verified for use with the Anybus CompactCom: Manufacturer Part No.
  • Page 96 The surface mounted pins of the HMS compact flash connector are numbered from left to right (see figure below), corresponding to pin numbers 1, 26, 2, 27..25, 50 of the host interface connector. Bottom view of the host connector Fig. 48 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 97: Fastening Mechanics

    To support the fastening mechanism, the host application PCB thickness must be 1.60 (±10%) Recommended screw tightening torque is 0.25 Nm. When fastening the module into the end product, make sure that the Anybus module is properly aligned into the CompactFlash socket prior to applying any force.
  • Page 98 Appendix D: Mechanical Specification 96 (114) D.7.2 Removal TORX 8 Fig. 50 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 99: E Anybus Compactcom 40 Without Housing

    General Information In some applications the standard Anybus CompactCom plug-in housing concept cannot be used. Instead an Anybus CompactCom 40 module without housing is mounted on the PCB, using a specially designed Anybus CompactCom Mounting Kit. This enables full Anybus CompactCom functionality for all applications without loss of network compatibility or environmental characteristics.

  • Page 100: Ordering Information

    Appendix E: Anybus CompactCom 40 without Housing 98 (114) Fig. 52 All dimensions expressed in this document are stated in millimeters and have a tolerance of ±0.10mm unless stated otherwise. Ordering Information Part No. Name Contents 019180 ABCC Mounting Kit...

  • Page 101: Footprint

    Under no circumstances may components, vias, or signal lines, be placed on the PCB- layer facing the Anybus CompactCom module. Failure to comply with this requirement may induce EMC/EMI problems, mechanical compatibility issues, or even short circuit.

  • Page 102: Host Connectors

    -0.05 mm). The gray area in the figure above specifies the maximum height occupied by onboard components of the Anybus module. To ensure isolation, it is recommended to add an additional 2.5 mm on top of these dimensions. 2.63 1.36...

  • Page 103: Assembly

    Appendix E: Anybus CompactCom 40 without Housing 101 (114) Assembly Fig. 56 Dimensions All dimensions are in millimeters. ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 104 Appendix E: Anybus CompactCom 40 without Housing 102 (114) E.7.1 General (Host Application PCB) 44.5 27.4 36.6 32.6 R 1.2 28.6 Component-free area Fig. 57 E.7.2 Standard LED Positions Standard Anybus CompactCom: 34.3 Module Status Network Status 23.5 Fig. 58 ®...
  • Page 105 Appendix E: Anybus CompactCom 40 without Housing 103 (114) Standard Anybus CompactCom, Ethernet versions: Fig. 59 Anybus CompactCom for M12 connectors: Fig. 60 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 106 Appendix E: Anybus CompactCom 40 without Housing 104 (114) E.7.3 Mounting Kit Parts Unless specified otherwise all dimensions are in millimeters, tolerance ± 0.1 mm. Bottom Part 26,3 Fig. 61 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 107 Appendix E: Anybus CompactCom 40 without Housing 105 (114) Top Part 23,1 Fig. 62 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 108 Appendix E: Anybus CompactCom 40 without Housing 106 (114) Fastening Screw Recommended screw tightening torque is 0.3 Nm (tolerance ±10 %). EJOT DELTA PT Schraube WN 5451 30x10 EJOT TORX PLUS/AUTOSERT 10IP Penetration depth: 1.00/1.30 -0.56 Detail “X” “X” 2.09 ±0.08...
  • Page 109 Appendix E: Anybus CompactCom 40 without Housing 107 (114) E.7.4 D-sub 30.8 12.6 50.4 Fig. 64 E.7.5 RJ45, 2–port 2x15 33.6 54.5 Fig. 65 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 110 Appendix E: Anybus CompactCom 40 without Housing 108 (114) E.7.6 Fiber Optics, 2–port 16,8 33,6 Detachable plug 86,4 95,9 Fig. 66 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...

  • Page 111: M12 Connectors

    Appendix E: Anybus CompactCom 40 without Housing 109 (114) M12 Connectors E.8.1 Dimensions Female - Female 64,6 50,5 47,6 Fig. 67 Female - Male 66,4 50,5 47,6 Fig. 68 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 112 Appendix E: Anybus CompactCom 40 without Housing 110 (114) E.8.2 IP Rating To ensure that the final design will fulfill the requirements for IP67 rating, the M12 connectors have to be firmly and tightly attached on both sides of the front plate. The dimensions for the front plate are given below.
  • Page 113 Appendix E: Anybus CompactCom 40 without Housing 111 (114) Fig. 70 Fig. 71 ® Anybus CompactCom ™ M40 Hardware Design Guide HMSI-216-126 EN 2.6...
  • Page 114 E.8.3 M12 Connector Assembly The M12 connector parts are not joined on the Anybus CompactCom module at delivery. The connector has to be tightly mounted on both sides of the front plate if the design is to be rated in class IP67.
  • Page 115 Appendix E: Anybus CompactCom 40 without Housing 113 (114) Guides for mechanical keying. Fig. 73 There are also markings on the casings of the connectors to make it easier to mount the connectors at the correct mounting angle. Markings that show the correct mounting angle.
  • Page 116 last page © 2018 HMS Industrial Networks Box 4126 300 04 Halmstad, Sweden info@hms.se HMSI-216-126 EN 2.6 / 2018-08-07 / 9027...

Table of Contents

Save PDF