Summary of Contents for HMS Anybus CompactCom B40-1
Page 1
A A n n y y b b u u s s ® ® C C o o m m p p a a c c t t C C o o m m B B 4 4 0 0 - - 1 1 DESIGN GUIDE HMSI-27-230 3.4 en-US ENGLISH...
Page 2
Important User Information Liability Every care has been taken in the preparation of this document. Please inform HMS Industrial Networks of any inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial Networks, 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.
About this Document......................3 Related Documents ......................3 Document history ......................3 Document Conventions .....................4 Document Specific Conventions..................4 Trademark Information .....................5 About the Anybus CompactCom B40-1................6 General Information ......................6 Features .........................7 Host Interface ........................8 Overview ........................8 Host Application Connector ..................... 10 Parallel Interface Operation .....................
Page 4
Black Channel/Safety Interface ..................51 Mechanical Specification ....................53 Anybus CompactCom B40-1 ..................... 53 Connector Board for PROFIBUS ..................54 Connector Board for Copper Based Ethernet............... 55 Connector Board for Fiber Optic Ethernet ................56 Connector Board for CC-Link and DeviceNet ............... 57 Footprints........................
Preface 3 (78) Preface About this Document This document is intended to provide a good understanding of how to use the Anybus CompactCom B40-1. The reader of this document is expected to be familiar with hardware design and communication systems in general. For additional information, documentation, support etc., please visit the support website at www.anybus.com/support.
This is a cross-reference within this document: Document Conventions, p. 4 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.
Power Pin connected directly to module power supply, GND or 3V3 Trademark Information Anybus ® is a registered trademark of HMS Industrial Networks. EtherCAT ® is a registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany. All other trademarks are the property of their respective holders.
There are also available interface boards for several networks, providing network connectors and physical interface. All Anybus CompactCom B40-1 share footprint and electrical interface. The brick has two connectors that provides communication with the host application board. The host application connector provides an interface between the host application and the brick, while the network connector provides network access.
Precompliance tested for CE & UL. Contact HMS Industrial Networks for further information. All Anybus CompactCom B40-1 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.
Host Interface 8 (78) 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
SPI and parallel modes. For more information about the serial interface, see the Anybus CompactCom Hardware Design Guide for the 30 series. Please note that the Anybus CompactCom B40-1 is not backward compatible to the Anybus CompactCom B30 hardware wise. 3.1.5...
Host Interface 10 (78) Host Application Connector The host application connector provides an interface between the host application and the Anybus CompactCom B40-1. Outline of brick Pin 1 Network interface Pin 1 Application interface Top view Fig. 2 The connector is implemented by a standard 1.27 mm 56 pin header surface mounted to the bottom side of the PCB.
Page 14
Host Interface 12 (78) 3.2.1 Pin Overview 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 pin types of the connector are defined in PIN Types, p.
Page 15
Host Interface 13 (78) Signal Name Type Notes Serial SPI Mode 8-bit 16-bit Shift Mode Mode Mode Register Mode ASI RX ASI RX ASI RX ASI RX TX / OM3 ASI TX / ASI TX / ASI TX / ASI TX / Strapping input with internal weak pull-up during powerup.
Page 16
Host Interface 14 (78) 3.2.3 LED Interface / D8–D15 (Data Bus) Signal Name Pin Type Description, LED Interface Description, Data Bus D9 Data Bus LED1A / D9 O / I/O LED 1 Indication A • "D9" in 16-bit parallel • Green mode.
Page 17
Host Interface 15 (78) 3.2.4 Settings / Sync Signal Name Type Description Operating Mode Used to select interface and baud rate, see below. OM3 (ASI TX) (TX) I (Used as OM3 during power up) Module Identification MI0 / SYNC MI0 and MI1 can be used by the host application to determine what type of Anybus CompactCom that is connected.
Page 18
Host Interface 16 (78) Operating Modes These inputs select the interface that should be used to exchange data (SPI, stand-alone shift register, parallel or serial) and, if the serial interface option is used, the operating baud rate. The state of these signals is sampled once during startup, i.e. any changes require a reset in order to have effect.
Page 19
Host Interface 17 (78) 3.2.5 RMII — Reduced Media-Independent Interface In RMII enabled modules, the pins described in the table below are used for the RMII communication. They are set to tristate during startup, making it impossilbe to indicate e.g. exception during setup.
Page 20
Host Interface 18 (78) 3.2.7 RESET (Reset Input) Signal Name Pin Type Description RESET Reset Used to reset the module. The master reset input is active low. It must be connected to a host application controllable output pin in order to handle the power up sequence, voltage deviations and to be able to support network reset requests.
Page 21
Host Interface 19 (78) Restart The reset pulse duration must be at least 10 µs in order for the NP40 to properly recognize a reset. RESET Fig. 6 Max. Symbol Min. Definition 10 µs Reset pulse width. HMSI-27-230 3.4 en-US Anybus ®...
Host Interface 20 (78) 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. Polled operation is possible, but at the cost of an overhead.
Page 23
Host Interface 21 (78) Signal Name Pin Type Description/Comments O, I OM3 / ASI TX Black channel output. Black Channel/Safety Interface, p. During startup the pin (with OM[0..2]) is used to define the operating mode of the module. Connect to external pull-up for 8-bit parallel operating mode, see Pin Overview, p.
Page 24
Host Interface 22 (78) 3.3.3 Pin Usage in 16-bit Parallel Mode The parallel 16-bit interface uses the following signals: Signal Name Pin Type Description/Comments A[1...13]: Mandatory address input signals. Selects source/target location. Standard bidirectional data bus. Write enable high byte. Write enable low byte.
Page 25
Host Interface 23 (78) Function Table (CS, WEL, WEH, OE, D[0...15]) Comment D[0...15] State HIGH High impedance Module not selected. HIGH Data Input (Write) Data on D[0...7] is written to low byte of location selected by address bus. HIGH Data Input (Write) Data on D[8...15] is written to high byte of location selected by address bus.
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 B40-1 has no setup or hold timing requirements on the address bus relative to CS during read operations. The only limitation on read setup and hold times is that the pingpong and powerup interrupt will be acknowledged if all address lines are high for 10-15 ns or more while CS is low.
Page 27
Host Interface 25 (78) 3.3.5 Memory Access Write Timing It doesn’t matter if the OE signal is low or high as long as WE is active (low). In 16 bit mode, the timing requirements of WE applies to both WEL and WEH. The timing diagrams show a burst write but the timing applies for a single write as well.
Host Interface 26 (78) SPI Operation 3.4.1 General Description The SPI (Serial Peripheral Interface) bus is a synchronous serial data link standard which operates in full duplex mode. The SPI interface is activated using the OM[0...3] inputs. See Operating Modes, p. 3.4.2 Pin Usage in SPI Mode Presented below is an overview of all pins except GND and 3V3.
Page 29
Host Interface 27 (78) Signal Name Type Description/Comments ASI RX Black channel input. Connect to 3V3 if not used. Black Channel/Safety Interface, p. 51 Module Identification, p. 16 MI0/SYNC Module Detection, p. 16 RESET RESET (Reset Input), p. 18 3.4.3 SPI Interface Signals The SPI interface option uses three (optionally four) signals: Description...
Page 30
Host Interface 28 (78) 4–Wire Mode 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
Host Interface 29 (78) 3–Wire Mode In 3-wire mode the SS signal must be tied low permanently, and the SCLK signal must be idle high. Multiple SPI slaves on the same bus are not possible in this mode. The module detects start and stop of a transfer by monitoring SCLK activity.
ADI #62 Fig. 15 Even though the Anybus CompactCom B40-1 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 test. See the Virtual Attributes section in the Anybus CompactCom 40 Software Design Guide for more information.
Page 33
Process active signal for shift register mode. In a PROFINET shift register stand-alone application, the PA signal must be used to clear outputs, when the Anybus CompactCom B40-1 is not in state PROCESS ACTIVE. Otherwise it will not be possible to certify the final product.
Page 34
Host Interface 32 (78) DIP1 and DIP2 Pins Usage The use of the DIP1 and DIP2 pins is network specific. If used, they will be read during SETUP state. Thereafter, DIP switch changes will be sampled and written to the Network Configuration Object every 0.5 seconds.
Page 35
Host Interface 33 (78) Network DIP1 (linked to Network DIP2 Notes Configuration Object) PROFINET 1 - 254 (Instance 3: IP Value: 1 — 255 (PROFINET If DIP1 is set to 0, saved values from address) IO object, Instance 1, instances 3 - 6 are used. If DIP1 is set attribute 24) to 255, DHCP is used for all settings.
Page 36
Host Interface 34 (78) 3.5.3 Timing The Anybus CompactCom B40-1 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 38
Host Interface 36 (78) 3.5.5 Reset Circuit Example The reset circuit example in the figure, is a common 3.3 V supervisor. The main usage is to obtain a defined reset release delay after the voltage is switched on. The power supply has to provide a stable voltage within the interval 3.15–3.45 V 100nF/16V H_RESET_N...
Host Interface 37 (78) UART Operation 3.6.1 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
Host Interface 38 (78) 3.6.2 Pin Usage in Serial Mode 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.
Page 41
Host Interface 39 (78) Signal Name Pin Type Description/Comments O, I Transmit Output TX / OM3 • Direction: CompactCom -> Host application • Idle state = High This pin doubles as OM3 strapping input on Anybus CompactCom M40 modules. Connect a pull-up resistor on the application for this pin in serial mode.
Network Connector 40 (78) Network Connector The network connector provides network access to the brick. Outline of brick Pin 1 Network interface Pin 1 Application interface Top view Fig. 21 The signals from the brick network connector can be directly routed to the (optional) connector board, which carries a network connector(s) identical or similar to the ones on the corresponding Anybus CompactCom M40 module.
3.3 V power supply. How to Connect Unused Network Connector Pins For Ethernet versions of the Anybus CompactCom B40-1 it is recommended to terminate Ethernet signals in the network interface if one of the Ethernet ports is unused. For the 10/100 Mb/s hardware version it is sufficient to terminate pair no.
Network Connector 44 (78) Ethernet Based Networks (Copper) The industrial networks, that use Ethernet for communication, share the same hardware design. However, the firmware downloaded to the brick is different depending on network. Physically they use the same set of pins in a similar way. Bricks are available for the following Ethernet based networks: EtherNet/IP, EtherCAT.
Network Connector 45 (78) Ethernet Fiber Optic Networks Ethernet fiber optic networks use more or less the same pins as copper based Ethernet networks. The brick supports PROFINET fiber optic network (PROFINET IRT). The brick supports dual network ports, signal group A is be connected to the left port (port 1) and signal group B to the right port (port 2)on the connector board, looking at the front, see Connector Board for Fiber Optic Ethernet, p.
Page 48
Network Connector 46 (78) Trans- Trans- Trans- Brick Brick Brick ceiver ceiver ceiver AC coupled transceiver DC coupled transceiver DC coupled transceiver with bias current Fig. 25 The AC coupling capacitors typically have a value of 100 nF. Resistors draining bias current typically have a value of 150 Ω.
Network Connector 47 (78) DeviceNet The Anybus CompactCom B40-1 DeviceNet communication interface uses the following pins: Type Description Signal Name C_TX C_RX C_BUSP_N Bus power detection. Active low GATE1 Low voltage MOS gate driver. For fieldbus isolated DC supply circuitry.
Network Connector 48 (78) LED Indicators The Anybus CompactCom 40 series supports four bicolored LED indicators. Signal Name Default Functionality LED name Pin no. Default color LED1 NW_LED1A Green Network status NW_LED1B LED2 NW_LED2A Green Module status NW_LED2B LED3 NW_LED3A Green All Industrial Link/Act for the...
50 (78) This section offers information, necessary when designing in an Anybus CompactCom B40-1, to ensure sufficient performance related to EMC. However, an engineering assessment is always needed to ensure the quality. HMS Industrial Networks does not leave any guarantees, but provides relevant information to the customers.
51 (78) Black Channel/Safety Interface Black Channel/Safety Interface The black channel is a transportation mechanism for safety related protocol extensions over a nonsafe communication media. The safety layer performs safety related transmission functions and checks on the communication to ensure that the integrity of the link meets the requirement for SIL 3, cat4/PL e.
Failure to observe this may cause damage to the product. All dimensions are in millimeters, tolerance ±0.10 mm, unless otherwise stated. Anybus CompactCom B40-1 The dimensions for the Anybus CompactCom B40-1 are given in the picture below. Pin 1 Application...
Appendix A: Mechanical Specification 54 (78) Connector Board for PROFIBUS The connector board for the PROFIBUS network interface carries a D-sub connector If the connector board is mounted in an environment that is subject to vibration, please make sure to secure the network cable in such a manner, that the vibrations will not harm the D-sub connector.
Footprints A.6.1 Anybus CompactCom B40-1 The Anybus CompactCom B40-1 is connected to the host application board through the host application interface connector and a network interface connector. The footprint for the Anybus CompactCom B40-1 is shown in the picture below.
Appendix A: Mechanical Specification 59 (78) A.6.2 Network Connector Board The network connectors are mounted on a separate connector board. The footprint for a connector board is shown in the figure below. This footprint is the same for all connector boards Outline of connector board Pin 1...
Fig. 38 Assembly The Anybus CompactCom B40-1 and the connector board are mounted separately on to the host application board. The connector board has to be secured using a screw, joining FE (functional earth) on the connector board to FE on the host application board. The screw holes of the Anybus CompactCom B40-1 are not connected to FE, but to GND.
Page 63
Pemnet SMTSO-M3-4-ET Stand-off (M3) The screw standoffs are typically 4 mm tall. If the Anybus CompactCom B40-1 and connector board are to be soldered directly to the host application board, standoffs should be 2 mm tall. Outer diameter may be 6 mm max. The standoffs should not extend outside the screw mount pads.
Page 64
Appendix A: Mechanical Specification 62 (78) PCB layout Outline of connector board Pin 1 Network interface Top view Outline of brick Pin 1 Network interface Pin 1 Application interface Top view M3: Standoff with internal thread, size M3 Fig. 40 HMSI-27-230 3.4 en-US Anybus ®...
It is recommended for Anybus CompactCom B40-1 users to make sure that each signal controlling the Anybus CompactCom B40-1 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.
EN61000-4-4 Fast transients/burst EN61000-4-5 Surge immunity EN61000-4-6 Conducted immunity Since all Anybus CompactCom B40-1 modules have been evaluated according to the EMC directive through above standards, this serves as a base for our customers when certifying Anybus CompactCom B40-1 based products.
It is possible to disable Ethernet Port 2 on the Anybus CompactCom B40-1 EtherNet/IP. • Do not connect signal group B • Do not connect signals LED4A/B It is not possible to disable Ethernet Port 2 on any other Anybus CompactCom B40-1 than EtherNet/IP. For descriptions of signals see: • Overview, p. 41 •...
66 (78) Implementation Examples General In this appendix HMS Industrial Networks provides examples of possible implementations for the Anybus CompactCom B40-1 series. There are many different processors with different functionality available on the market today. The implementations in this appendix are to be regarded as examples that are designed for one single type of processor.
Appendix D: Implementation Examples 68 (78) 16-bit Parallel This example shows a design for 16-bit parallel mode. Host Application CPU (3.3V) WR/WR0 GPIO5 GPIO6 MI0/SYNC GPIO7 GPIO8 GPIO10 RESET Fig. 42 If LEDs are to be used in the host application, please refer to Network Status LED Outputs (LED [1A...4B]), p.
Appendix D: Implementation Examples 69 (78) 8-bit Parallel This design is intended for 8-bit parallel mode. M40 pinning Host Application CPU (3.3V) LED1B LED1A LED2B LED2A LED3B LED3A LED4B LED4A WR/WR0 GPIO5 GPIO6 MI0/SYNC GPIO7 GPIO9 GPIO10 RESET Fig. 43 If LEDs are to be used in the host application, please refer to Network Status LED Outputs (LED [1A...4B]), p.
Appendix D: Implementation Examples 70 (78) Serial The example in the figure below shows an implementation with serial communication. Host Application CPU (3.3V) LED1B LED1A LED2B LED2A LED3B LED3A LED4B LED4A WR/WR0 GPIO1 GPIO2 GPIO3 Tx/OM3 GPIO5 GPIO6 MI0/SYNC GPIO7 GPIO8 GPIO10 RESET...
Page 73
Appendix D: Implementation Examples 71 (78) LED4B LED4A LED3B LED3A LED2B LED2A LED1B LED1A *By connecting this signal to Ground, this design can be used to support Anybus CompactCom passive modules. Fig. 45 These pins can not be used for LEDs in 16-bit parallel mode, as the pins in that case are used for data. All network status LED signals are present on the network interface connector, and can be connected from there.
Appendix D: Implementation Examples 72 (78) Power Supply Considerations D.7.1 General The Anybus CompactCom 40 platform in itself is designed to be extremely power efficient. The exact power requirements for a particular networking system will however vary a lot depending on the components used in the actual bus circuitry.
Page 75
Appendix D: Implementation Examples 73 (78) D.7.2 Bypass Capacitance The power supply inputs must have adequate bypass capacitance for high-frequency noise suppression. It is therefore recommended to add extra bulk capacitors near preferably all the power supply inputs (or at least two): Value (Ceramic) Reference 10 µF / 6.3 V...
Appendix E: Design Examples, Network Interface 74 (78) Design Examples, Network Interface If the optional connector board is used, the signals from the network interface connector of the brick can be routed directly to the corresponding pins of the connector on the connector board. Section shows an example PCB layout for this case.
Page 77
Appendix E: Design Examples, Network Interface 75 (78) • DC/DC transformer selection recommendations: – 1:2.1 turns ratio – 500 kHz switching frequency – The transformer shall be able to deliver at least 100 mA on the network interface side without saturating, at Anybus CompactCom min/max supply voltage, and at the relevant min/max ambient temperature that is applicable –...
76 (78) PCB Layout The pin headers of the Anybus CompactCom B40-1 have pins which are 2.3 mm tall nominally, but to avoid risk of short circuit when the pin length is in the upper tolerance region, it is suggested to have via/route keepouts on the PCB top layer, in between the pad rows, as the figure shows, unless a receptacle taller than 2.6 mm is used.
Appendix E: Design Examples, Network Interface 77 (78) Network Interface Examples This section contains typical examples, of how to design the network interface, if the optional connector board is not to be used. Examples are given for the usual network connectors as well as for M12 connectors making a higher IP rating possible.
Need help?
Do you have a question about the Anybus CompactCom B40-1 and is the answer not in the manual?
Questions and answers