Product Overview

The ABB NTMF01​ is a Multi-Function Controller Termination Unit — the field-facing termination (FTA) that pairs with ABB’s INFI 90 / Symphony Harmony Multi-Function Controller (MFC) processor modules such as IMFCS01​ and IMFEC12, forming the same “smart electronic module + passive termination” split architecture that defines the Bailey INFI 90 I/O philosophy. While dedicated I/O modules in an INFI 90 rack (ICTAI01 for AI, ICTAO01 for AO, ICDIA01 for DI, ICDOA01 for DO) each have their own termination units (NTAI05, NTRO05, etc.), the MFC processor itself often needs a small complement of local, mixed-signal field I/O: hand/auto station contacts, alarm-acknowledge pushbutton, watchdog-reset, controller-status relays (running/primary/backup), maybe a local speed-reference or position-feedback for a small drive node where the MFC is the cell controller. The NTMF01​ is the FTA that lands those controller-local signals, keeping them separate from the rack’s I/O-module channels and giving the MFC its own dedicated field-wire landing without consuming I/O-module slots.Like its siblings in the NTxx family, the ABB NTMF01​ is passive — screw terminals for field wires, shield-drain terminals for noise discipline, and a 40-pin ribbon that mates to the MFC processor’s front header. The MFC (IMFCS01 / IMFEC12) seats on the INFI 90 rack’s backplane in a processor slot (often slots 1–2 in an HCU or Harmony rack), runs the CCF (Control Configuration Facility) control strategy — loops, sequences, interlocks for the I/O station — and the NTMF01​ clips onto the MFC’s front face (or DIN-mounts adjacent) landing the controller’s own I/O. Signal mix on the NTMF01​ is “multi-function” by design: typically a blend of 4–20 mA (maybe one AO for a local speed-ref or one AI for a local feedback), 24 V DC DI (hand/auto, alarm ack, remote enable), and relay DO or open-collector (controller-status: running, primary, backup, watchdog-fail) — the exact mix depends on the MFC firmware and the plant’s CCF build, but the NTMF01​ footprint accommodates the blend without segregating into separate FTAs.The split architecture advantage holds here as everywhere in INFI 90: when an MFC processor needs swapping (drift, firmware corruption, spare rotation), the NTMF01​ stays in place with all controller-local field wires undisturbed — hand/auto station, alarm-ack, watchdog relay, status beacon wires all stay landed. On a power-gen unit with 20+ INFI 90 I/O stations each with an MFC + NTMF01, this “no re-termination” saves turnaround hours. The NTMF01​ shares the same 35 mm DIN / rack-front clip flexibility as NTAI05, same shield-drain discipline, same passive robustness — no active components, no firmware, no config, just copper + screw + ribbon.Lifecycle-wise, the NTMF01​ belongs to the mature INFI 90 / Harmony termination family — ABB’s current DCS is Symphony Plus on AC 800M, but the installed base of INFI 90 MFC nodes globally (power-gen, oil & gas, petchem, metals) keeps NTMF01​ active in spares channels.

Technical Specifications

Main Features and Advantages

Controller-Local I/O on a Dedicated FTA.​ The NTMF01​ exists because the MFC processor in an INFI 90 rack isn’t just a “brain” talking to I/O modules — it also needs its own small I/O footprint that belongs to the controller itself, not to the process loops. Typical MFC-local signals: Hand/Auto contact from the pulpit (DI), Alarm Acknowledge pushbutton (DI), Remote Enable from upstream guard (DI), Watchdog-OK relay (DO — dry contact to PLC or annunciator), Controller-Active / Primary / Backup status relays (DO — dry contacts to MCC beacon tree), and occasionally a local analog — e.g., a speed-reference AO to a small auxiliary drive, or a position-feedback AI from a local transducer. Segregating these onto the NTMF01​ (instead of consuming I/O-module channels on, say, an ICTAI01) keeps the I/O-module slots free for process AI/AO/DI/DO and keeps the controller’s own signals on a termination that swaps with the MFC. If you mixed Hand/Auto into the station’s ICTDI01, then when the MFC swaps you’d still be fine (the DI module stays), but the status relays and watchdog absolutely must follow the MFC — putting them on NTMF01​ ensures the “controller identity” (which slot is primary, which is backup, which watchdog is alive) stays with the processor, not with the I/O station’s generic DI/DO pool.Split Architecture Extends to the Controller Slot.​ The same “electronic module + passive termination” split that makes NTAI05 valuable for AI modules applies to the MFC + NTMF01​ pair. The MFC (IMFCS01 / IMFEC12) is the smart part — CCF runtime, INFI 90 bus interface, I/O expander bus master, redundancy logic (primary/backup MFC pair in one rack). The NTMF01​ is the dumb part — screw terminals, shield drains, 40-pin ribbon. When the MFC needs swapping (firmware corruption from a noisy 24 V rail, CCF memory parity error, proactive spare rotation at turnaround), the NTMF01​ stays clipped with all controller-local wires landed: Hand/Auto station (maybe a 3-position mushroom on the pulpit door, 50 m of 2.5 mm² screened pair), Alarm Ack (momentary NO), watchdog relay (NO to beacon, NC to safety-chain), Primary/Backup status relays (NO to pulpit annunciator tree). None of those get disturbed. On a power-gen unit with 20+ I/O stations (each an MFC + I/O modules), that’s 20+ NTMF01​ units on the BOM, and the “no re-terminate” benefit compounds across the turnaround.Mixed-Signal Footprint.​ “Multi-function” in the NTMF01​ name signals that this FTA isn’t pure AI or pure DO — it’s a blended layout: a few 4–20 mA screw pairs (maybe 2–4 channels, for a local AO like speed-ref to a small VFD, or AI like a local position-feedback), several 24 V DC DI screw pairs (Hand/Auto, Alarm Ack, Remote Enable, maybe a few spares), and several relay / open-collector DO screw pairs (watchdog, running, primary, backup, maybe a spare for annunciator). The exact channelization varies by NTMF01​ revision and by the MFC firmware’s CCF allocation, but the footprint is deliberately “controller-local blend” rather than “process I/O bulk.” This avoids the plant having to stock three separate FTAs (NTAIxx + NTROxx + NTDIOxx) just for the MFC’s handful of points — one NTMF01​ covers the MFC’s entire local-I/O need.Shield Discipline & 24 V Distribution.​ Like the NTAI05, the NTMF01​ provides dedicated shield-drain terminals (per channel or per small group, revision-dependent) so the commissioning tech can land shield-at-DCS-only, breaking ground loops on long Hand/Auto or Alarm Ack runs from the pulpit to the DCS room (these runs often parallel 120/230 V AC pulpit lighting and VFD output cables, so CMV is real). For any 4–20 mA channels on the NTMF01​ (local AO/AI), the 24 V loop-power either passes through from the MFC’s own 24 V distribution (derived from the NPOW-41 rack PSU) or from an external 24 V bussed onto the NTMF01​ loop-power terminals — same pattern as NTAI05, scaled to the MFC’s local needs. The DI channels (Hand/Auto, Alarm Ack) are typically dry-contact-from-field (pulpit pushbutton/mushroom, 24 V sourced from the MFC side, returned through the NTMF01​ DI screw to the MFC’s DI circuitry). The DO relay contacts are potential-free dry (NO/NC), rated for typical control-relay coil loads (24–250 V AC/DC, ~2–5 A depending on relay rating on the NTMF01​ revision) — they land on the pulpit beacon tree, the annunciator, the PLC DI island upstream.Rack-Front Clip or DIN.​ The NTMF01​ clips onto the MFC’s front header (the MFC processor card has guide pins + header that match the NTxx family footprint) so it sits flush on the INFI 90 rack face, field wires landing from the front, labels visible. Alternatively DIN-mount adjacent if the rack face is crowded (some retrofits where an HCU rack got an MFC added later and the front clip geometry conflicts with existing FTAs). The 40-pin ribbon to the MFC is short (maybe 100–150 mm), keyed, pin-1 triangle — same as NTAI05→ICTAI01, so the plant’s spare crib tech doesn’t need a different “ribbon handling” mental model across FTAs.