Anybus CompactCom M40 User manual

Anybus®CompactCom™M40
HARDWARE DESIGN GUIDE
HMSI-216-126 EN 2.6 ENGLISH

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

Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6
Table of Contents Page
1 Preface ............................................................................................................................... 3
1.1 About this Document......................................................................................................3
1.2 Related Documents .......................................................................................................3
1.3 Document history...........................................................................................................3
1.4 Document Conventions ..................................................................................................4
1.5 Document Specific Conventions......................................................................................4
1.6 Trademark Information ...................................................................................................5
2 Introduction ...................................................................................................................... 6
2.1 General Description .......................................................................................................6
2.2 Features .......................................................................................................................6
2.3 M12 Connector ..............................................................................................................7
3 Host Interface................................................................................................................... 8
3.1 Overview.......................................................................................................................8
3.2 Connector ...................................................................................................................10
3.3 Parallel Interface Operation ..........................................................................................20
3.4 SPI Operation..............................................................................................................26
3.5 Stand-alone Shift Register............................................................................................30
3.6 UART Operation ..........................................................................................................37
4 EMC................................................................................................................................... 40
4.1 General.......................................................................................................................40
4.2 Header Footprint..........................................................................................................40
4.3 Bulk and Decoupling ....................................................................................................40
4.4 Reset Signal................................................................................................................40
5 Black Channel/Safety Module.................................................................................... 41
A Implementation Examples .......................................................................................... 43
A.1 General.......................................................................................................................43
A.2 Design Considerations .................................................................................................43
A.3 Serial and 16–bit Parallel..............................................................................................44
A.4 8–bit/16–bit Parallel .....................................................................................................45
A.5 8–bit Parallel ...............................................................................................................46
A.6 SPI and Serial..............................................................................................................47
A.7 Network Status LED Outputs (LED[1A...4B]) ..................................................................48
A.8 Power Supply Considerations .......................................................................................49

Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6
Table of Contents
B Backward Compatibility .............................................................................................. 51
B.1 Background.................................................................................................................51
B.2 Initial Considerations....................................................................................................51
B.3 Hardware Compatibility ................................................................................................53
B.4 General Software.........................................................................................................58
B.5 Network Specific — BACnet/IP .....................................................................................60
B.6 Network Specific — CC-Link.........................................................................................61
B.7 Network Specific — DeviceNet......................................................................................62
B.8 Network Specific — EtherCAT.......................................................................................63
B.9 Network Specific — EtherNet/IP....................................................................................65
B.10 Network Specific — Modbus-TCP .................................................................................67
B.11 Network Specific — PROFIBUS....................................................................................69
B.12 Network Specific — PROFINET ....................................................................................71
C Technical Specification ............................................................................................... 82
C.1 Environmental .............................................................................................................82
C.2 Shock and Vibration .....................................................................................................82
C.3 Electrical Characteristics ..............................................................................................83
C.4 Regulatory Compliance ................................................................................................84
D Mechanical Specification ............................................................................................ 85
D.1 Overview.....................................................................................................................86
D.2 M12 Connector ............................................................................................................87
D.3 Footprint .....................................................................................................................88
D.4 Housing Preparations...................................................................................................89
D.5 Slot Cover ...................................................................................................................90
D.6 Host Connector............................................................................................................91
D.7 Fastening Mechanics ...................................................................................................95
E Anybus CompactCom 40 without Housing ............................................................ 97
E.1 General Information .....................................................................................................97
E.2 Ordering Information ....................................................................................................98
E.3 Footprint .....................................................................................................................99
E.4 Host Connectors........................................................................................................100
E.5 Height Restrictions.....................................................................................................100
E.6 Assembly ..................................................................................................................101
E.7 Dimensions ...............................................................................................................101
E.8 M12 Connectors ........................................................................................................109

Preface 3 (114)
1 Preface
1.1 About this Document
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.
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.
1.2 Related Documents
Document Author Document ID
Anybus CompactCom 40 Software Design Guide HMS HMSI-216-125
Anybus CompactCom Host Application Implementation
Guide
HMS HMSI-27-334
Anybus CompactCom Network Guides (separate document
for each supported fieldbus or network system)
HMS
Low-Cost, Low-Power Level Shifting in Mixed-Voltage (5V,
3.3V) Systems (SCBA002A)
Texas Instruments
LT1767 Data Sheet Linear Technology
EN 61000 IEC
1.3 Document history
Version Date Description
1.40 2015-09-22 Last FM version.
2.0 2016–02-24 Moved from FM to XML
Misc. updates
2.1 2016-08-23 Misc. updates and corrections
2.2 2017-01-23 Transparent Ethernet
M12 connectors
2.3 2017-06-16 Major update to Backward Compatibility section
BACnet/IP and CC-Link IE Field added
2.4 2018-03-09 Updated Mechanical Specification
Added section on EMC
Updated section on usage of DIP1 and DIP 2 in stand alone mode
Minor corrections
2.5 2018-05-03 Minor corrections
2.6 2018–08–07 Minor correction
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Preface 4 (114)
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. 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.
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 Document Specific 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.
• A byte always consists of 8 bits.
• All dimensions in this document have a tolerance of ±0.20mm unless otherwise stated.
• Outputs are TTL compliant unless otherwise stated.
• Signals which are “pulled to GND” are connected to GND via a resistor.
• Signals which are “pulled to 3V3” are connected to 3V3 via a resistor.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Preface 5 (114)
• Signals which are “tied to GND” are directly connect GND,
• Signals which are “tied to 3V3” are directly connected to 3V3.
1.6 Trademark Information
Anybus®is a registered trademark of HMS Industrial Networks AB.
All other trademarks are the property of their respective holders.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Introduction 6 (114)
2 Introduction
2.1 General Description
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. Please consult the Anybus CompactCom B40–1
Design Guide for specific information about the Anybus CompactCom B40–1 brick solution.
This a class A product. In a domestic environment, this product may cause radio
interference in which case the user may be required to take adequate measures.
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.
2.2 Features
• Hardware support for triple buffered process data, which increases performance
• Supports synchronization for selected industrial networks
• Black channel interface, offering a transparent channel for safety communication for
selected networks
• Low latency
• Integrated protocol stack handling (where applicable)
• Galvanically isolated network interface (where applicable)
• On-board network status indications according to each network standard (where
applicable)
• On-board network connectors according to each network standard
• Compact size (52 x 50 mm, 2”″ x 1.97″”)
• Firmware upgradable (FLASH technology)
• 3.3 V design
• 8-bit and 16-bit parallel modes
• SPI mode
• Shift register mode
• Precompliance tested for network conformance (where applicable). Not finalized. All
Anybus CompactCom versions will be precertified for network conformance. While this is
done to ensure that the final product can be certified, it does not necessarily mean that the
final product does not require recertification. Contact HMS for further information.
• Precompliance tested for CE & UL. Not finalized. Contact HMS for further information.
• Version with M12 connector available for several networks.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Introduction 7 (114)
2.3 M12 Connector
A number of the Anybus CompactCom M40 modules are available with M12 connectors
instead of the usual network connector.
The M12 connector gives the opportunity to raise the IP rating of a product up to IP67.
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.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 8 (114)
3 Host Interface
This chapter describes the low level properties of the Anybus CompactCom interface
3.1 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.
Host
CPU
Flash
Parallel Interface,
8-bit or 16-bit
Serial Interface
LED I/F
or RMII
RAM
A0 ... A13
Tx
Rx
LED[1A, 1B, 2A, 2B]
LED[3A, 3B, 4A, 4B]
RESET
OM[0...3]
MI[0...1]
MD[0...1]
D0 ... D7
CS
OE
WE
IRQ
Physical Interface
Anybus
CPU
Network
Communications Controller
SPI
Shift Registers
SS
SCLK
MISO
MOSI
LD
SCLK
DO
DI
CT
PA
DIP1[0...7]
DIP2[0...7]
IRQ
D8 ... D15
Fig. 1
Please note that only one communication interface at a time is available. Which one is decided
at startup.
3.1.1 Parallel Interface, 8-bit or 16-bit
From an external point of view, the parallel interface is a common 8-bit or 16-bit parallel slave
port interface, which can easily be incorporated into any microprocessor based system that has
an external address/data bus. Generally, implementing this type of interface is comparable to
implementing an 8-bit or 16-bit wide SRAM. Additionally, the parallel interface features an
interrupt request line, allowing the host application to service the module only when actually
needed.
3.1.2 SPI
The Serial Peripheral Interface (SPI) is a synchronous serial link. It operates in full duplex mode
and devices communicate in master/slave mode where the Anybus CompactCom modules
always act as slaves. The interface can provide much higher performance than the serial
interface, but not as high as the parallel interface.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 9 (114)
3.1.3 Stand-Alone Shift Register Interface
In this mode the Anybus CompactCom M40 operates stand-alone, with no host processor.
Process data is communicated to the shift registers on the host.
3.1.4 Serial Interface (UART)
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.
3.1.5 LED Interface
Network status LED output signals are available in all operating modes except 16-bit parallel
mode. The status of the network LEDs is always available in the LED status register for all
modes, see Anybus CompactCom 40 Software Design Guide for more information.
3.1.6 Reduced Media-Independent Interface (RMII)
This interface is used for Transparent Ethernet, where Industrial Ethernet communication is
handled by the Anybus CompactCom and other Ethernet communication is routed to the host
application. 16–bit parallel mode and the LED Interface signals are not available when
Transparent Ethernet is enabled.
See RMII — Reduced Media-Independent Interface, p. 17for mor information.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 10 (114)
3.2 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
50
(GND)
26
(MD0)
(MD1)
25
(GND)
1
Fig. 2
See .Application Connector Pin Overview, p. 11 for information on how each pin is used in the
different modes.
The host interface is not pin compatible with the CompactFlash™standard. Also,
prior to exchanging a module, power should be turned off or the MD (module
detection signals should be used to shut down communication and power when the
module is removed. Failure to observe this may cause damage to the host product
and/or the Anybus CompactCom module.
The pin types of the host interface connector are defined in the table below. The pin type may
be different depending on which mode is used.
Pin type Definition
I Input
O Output
I/O Input/Output (bidirectional)
OD Open Drain
Power Pin connected directly to module power supply, GND or 3V3
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 11 (114)
3.2.1 Application Connector 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 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.
Pin Signal Name Type Notes
Serial
Mode
SPI Mode 8-bit
Mode
16-bit
Mode
Shift
Register
Mode
49 DIP1_0 DIP1_0 A0 WEH DIP1_0 I -
24 DIP1_1 DIP1_1 A1 A1 DIP1_1 I -
48 DIP1_2 DIP1_2 A2 A2 DIP1_2 I -
23 DIP1_3 DIP1_3 A3 A3 DIP1_3 I -
47 DIP1_4 DIP1_4 A4 A4 DIP1_4 I -
22 DIP1_5 DIP1_5 A5 A5 DIP1_5 I -
46 DIP1_6 DIP1_6 A6 A6 DIP1_6 I -
21 DIP1_7 DIP1_7 A7 A7 DIP1_7 I -
45 SS A8 A8 LD I -
20 SCLK A9 A9 SCLK O, I -
44 MISO A10 A10 DO O, I -
19 MOSI A11 A11 DI I -
43 ASI RX A12 A12 I -
18 ASI TX A13 A13 O, I -
14 DIP2_0 DIP2_0 D0 D0 DIP2_0 I, I/O -
39 DIP2_1 DIP2_1 D1 D1 DIP2_1 I, I/O -
15 DIP2_2 DIP2_2 D2 D2 DIP2_2 I, I/O -
40 DIP2_3 DIP2_3 D3 D3 DIP2_3 I, I/O -
16 DIP2_4 DIP2_4 D4 D4 DIP2_4 I, I/O -
41 DIP2_5 DIP2_5 D5 D5 DIP2_5 I, I/O -
17 DIP2_6 DIP2_6 D6 D6 DIP2_6 I, I/O -
42 DIP2_7 DIP2_7 D7 D7 DIP2_7 I, I/O -
4 LED1B LED1B LED1B D8 LED1B O, I/O In modules supporting RMII,
these pins are used for the
RMII interface, see RMII —
Reduced Media-Independent
Interface, p. 17.
29 LED1A LED1A LED1A D9 LED1A O, I/O
5 LED2B LED2B LED2B D10 LED2B O, I/O
30 LED2A LED2A LED2A D11 LED2A O, I/O
6 LED3B LED3B LED3B D12 LED3B OD, I/O
31 LED3A LED3A LED3A D13 LED3A OD, I/O
7 LED4B LED4B LED4B D14 LED4B O, I/O
32 LED4A LED4A LED4A D15 LED4A O, I/O
34 WE WEL CT I -
33 OE OE I -
10 CS CS I -
9 IRQ IRQ IRQ PA O -
28 RX ASI RX ASI RX ASI RX ASI RX I Connect to 3V3 if not used.
3 TX / OM3 ASI TX /
OM3
ASI TX /
OM3
ASI TX /
OM3
ASI TX /
OM3
O Strapping input with internal
weak pull-up during powerup.
To configure OM3, use an
external pull-up/pull-down of
1.0 to 2.2 kΩ). The pin
changes to output after
powerup.
36 OM0 OM0 OM0 OM0 OM0 I -
11 OM1 OM1 OM1 OM1 OM1 I -
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 12 (114)
Pin Signal Name Type Notes
Serial
Mode
SPI Mode 8-bit
Mode
16-bit
Mode
Shift
Register
Mode
35 OM2 OM2 OM2 OM2 OM2 I -
27 MI0/
SYNC
MI0/
SYNC
MI0/SYNC MI0/
SYNC
MI0/
SYNC
O Low at powerup and before
reset release.
2 MI1 MI1 MI1 MI1 MI1 O Connected to 3V3
26 MD0 MD0 MD0 MD0 MD0 O Connected to GND
25 MD1 MD1 MD1 MD1 MD1 O Connected to GND
8 RESET RESET RESET RESET RESET I -
3.2.2 Power Supply Pins
Signal Name Type Pin Description
GND Power 50
37
12
1
Power and signal ground reference.
3V3 Power 38
13
3.3 V power supply.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 13 (114)
3.2.3 LED Interface / D8–D15 (Data Bus)
Signal Name Pin Type Pin Description, LED Interface Description, Data Bus
LED1A / D9 O / I/O 29 LED 1 Indication A
• Green
D9 in 16-bit data bus mode
LED1B / D8 O / I/O 4 LED 1 Indication B
• Red
D8 in 16-bit data bus
modeData Bus
LED2A / D11 O / I/O 30 LED 2 Indication A
• Green
D11 in 16-bit data bus mode
LED2B / D10 O / I/O 5 LED 2 Indication B
• Red
D10 in 16-bit data bus mode
LED3A / D13 OD / I/O 31 LED 3 Indication A
• Green
• Mainly used for link/
activity on network port 1
on the Ethernet modules.
Pin is open-drain to maintain
backward compatibility with
existing applications, where
this pin may be tied to GND.
Also for compatibility with
passive modules where this
pin is a driver enable input
D13 in 16-bit data bus mode
LED3B / D12 OD / I/O 6 LED 3 Indication B
• Yellow or red, depending
on network
• Mainly used for link/
activity on network port 1
on the Ethernet modules
(yellow).
Pin is open-drain to maintain
backward compatibility with
existing applications, where
this pin may be tied to GND.
Also for compatibility with
passive modules where this
pin is as driver enable input
D12 in 16-bit data bus mode
LED4A / D15 O / I/O 32 LED 4 Indication A
• Green
• Mainly used for link/
activity on network port 2
on the Ethernet modules.
D15 in 16-bit data bus mode
LED4B / D14 O / I/O 7 LED 4 Indication B
• Yellow or red, depending
on network
• Mainly used for link/
activity on network port 2
on the EThernet modules
(yellow)
D14 in 16-bit data bus mode
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 14 (114)
Corresponding LED Placement on Module Fronts
The LED interface signals are shown on the module front as indicated in the pictures below.
See the different Anybus CompactCom 40 Network Guides (app. “Technical Specification”) for
details.
Anybus CompactCom M40 Ethernet modules have four LEDs on the front:
1 2
34
Fig. 3
LED no (in figure) Corresponding signal name in LED interface
1 LED1A/LED1B
2 LED2A/LED2B
3 LED3A/LED3B
4 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.
1 2
3
1 5
Fig. 4
LED no (in figure) Corresponding signal name in LED interface
1 LED1A/LED1B
2 LED2A/LED2B
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 15 (114)
3.2.4 Settings / Sync
Signal Name Type Pin Description
OM0
OM1
OM2
OM3 (ASI TX)
(TX)
I
I
I
I (Used as OM3
during power up)
36
11
35
3
Operating Mode
Used to select interface and baud rate, see below.
MI0 / SYNC
MI1
O
O
27
2
Module Identification
MI0 and MI1 can be used by the host application to determine
what type of Anybus CompactCom that is connected.
SYNC
On networks that support synchronous communication, a
periodic synchronization pulse is provided on the SYNC
output.
The SYNC pulse is also available as a maskable interrupt
using the IRQ signal.
MD0
MD1
O
O
26
25
Module Detection
These signals can be used by the host application to
determine that an Anybus CompactCom is inserted into the
slot, see Module Detection, p. 16.
The signals are connected directly to GND on the Anybus
CompactCom.
ASI RX
ASI TX
I
O
28
3
Black Channel Communication
These signals can be connected to a safety module, e.g. to
IXXAT Safe T100 to provide a safe channel for black channel
communication
If not used, pin 28 should be connected to 3V3.
RX
TX
I
O
28
3
Serial Communications Signals
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 16 (114)
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.
OM3 OM2 OM1 OM0 Operating Mode
LOW LOW LOW LOW Reserved
LOW LOW LOW HIGH SPI
LOW LOW HIGH LOW Stand-alone shift register
LOW LOW HIGH HIGH Reserved
LOW HIGH LOW LOW Reserved
LOW HIGH LOW HIGH Reserved
LOW HIGH HIGH LOW Reserved
LOW HIGH HIGH HIGH 16-bit parallel
HIGH LOW LOW LOW 8-bit parallel
HIGH LOW LOW HIGH Serial 19.2 kbps
HIGH LOW HIGH LOW Serial 57.6 kbps
HIGH LOW HIGH HIGH Serial 115.2 kbps
HIGH HIGH LOW LOW Serial 625 kbps
HIGH HIGH LOW HIGH Reserved
HIGH HIGH HIGH LOW Reserved
HIGH HIGH HIGH HIGH Service Mode
LOW = VIL
HIGH = VIH
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. The reason is that during startup the OM3 will indicate an
M30 mode if it is high. The signal will change to an output signal after startup, and will then be
used either for the serial interface towards the host application or for black channel
communication using an external safety module.
Module Detection
These signals are internally connected to GND, and can be used by the host application to
detect whether a module is present or not.
State Indication
MD0 MD1
HIGH HIGH Module not present
LOW HIGH
HIGH LOW
LOW LOW Module present
LOW = VOL
HIGH = VOH
If unused, leave these signals unconnected.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 17 (114)
Module Identification
These signals indicate which type of module that is connected. It is recommended to check the
state of these signals before accessing the module.
MI1 MI0 Module Type
LOW LOW Active Anybus CompactCom 30
LOW HIGH Passive Anybus CompactCom
HIGH LOW Active Anybus CompactCom 40
HIGH HIGH Customer specific
LOW = VOL
HIGH = VOH
On modules supporting “SYNC”, MI0 is used as a SYNC signal during operation. MI0 should only
be sampled by the application during the time period from power up to the end of SETUP state.
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. When setup is complete, they are set to inputs/outputs according to the
selected mode. See Anybus CompactCom 40 Software Design Guide for more information on
mode selection.
The 16–bit parallel mode can not be used when RMII is enabled
LED status will not be available when RMII is enabled.
Pin Signal Name Type Notes
4 RXD0 O -
29 RXD1 O -
5 RXDV O -
30 I Not used (connect to external pull-down)
6 TXD0 I -
31 TXD1 I -
7 TXEN I -
32 CLK I -
3.2.6 IRQ (Interrupt Request)
Signal Name Pin Type Pin Description
IRQ O 9 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.
This signal must be pulled to 3V3 on the host application side to prevent spurious interrupts
during startup.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6

Host Interface 18 (114)
3.2.7 RESET (Reset Input)
Signal Name Pin Type Pin Description
Reset I 8 Reset
Used to reset the module.
The 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.
The module does not feature any internal reset regulation. To establish a reliable interface, the
host application is solely responsible for resetting the module when the supply voltage is
outside the specified range.
There is no Schmitt trigger circuitry on this input, which means that the module requires a fast
rise time of the reset signal, preferably equal to the slew rate of typical logical circuits. A simple
RC circuit is for example not sufficient to guarantee stable operation, as the slew rate from logic
0 to logic 1 is too slow.
The rise time of the reset signal should be as fast as possible, and must not exceed
30 ns. The signal is not under any circumstances allowed to be left floating. Use a
pull-down to prevent this.
The following requirements must be met by the reset regulator connected to the reset input
signal.
Power Up
Power
RESET
0V
3.3V
Power
On
Power
Stable
tB
tA
VIL
VIH
t
t
Fig. 5
Power up time limits are given in the table below:
Symbol Min. Max. Definition
tA- - 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.
tB1ms -Safety margin.
Anybus®CompactCom™M40 Hardware Design Guide HMSI-216-126 EN 2.6