Anybus CompactCom 40 Network Manual page 234

Appendix H: Backward Compatibility
H.2.4 Host Application Interface
Fig. 28
Some signals in the host application interface have modified functionality and/or functions which
must be checked for compatibility. See the following sections.
Tx/OM3
In the 30-series, this pin is only used for Tx. It is tri-stated during power up, and driven by the
Anybus CompactCom UART after initialization. In the 40-series this pin is used as a fourth oper-
ating mode setting pin (OM3). During startup after releasing the reset, this pin is read to deter-
mine the operating mode to use. The pin is then changed to a Tx output.
In the 40-series, this pin has a built-in weak pull-up. If this pin, on a 30-series module or brick is
unconnected, pulled high, or connected to a high-Z digital input on the host processor, it will be
compatible with the 40-series. An external pull-up is recommended, but not required.
Related Information: Anybus CompactCom M40 Hardware Design Guide (HMSI-216-126), Sec-
tion "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.
If your software use this identification you need to handle the new identification value.
MI1
LOW
HIGH
MI[0..1] shall only be sampled by the application during the time period from power up to the
end of SETUP state. The pins are low at power up and before reset release.
Related Information: Anybus CompactCom M40 Hardware Design Guide (HMSI-216-126), Sec-
tion "Settings/Sync".
®
Anybus CompactCom ™ 40 PROFINET IRT Network Guide
25
50
If this pin is pulled low by the host during startup in a 30-series application, any 40-
series module or brick, substituted in the application, will not enter the expected
operating mode.
MI0 Module Type
LOW Active Anybus CompactCom 30
LOW Active Anybus CompactCom 40
232 (258)
1
26
SCM-1202-023 EN 1.8