ABB 1TGE102009R1001 MNS MLink Module – Profibus DP Gateway for MNS MCC, 16-Drawer Capacity

Description

Technical Specifications

Main Features and Advantages

Native MNS MCC integration, no drawer re-wiring:The ABB 1TGE102009R1001​ is designed to snap into the MNS communication compartment with the MNS bus already factory-wired through the cubicle backbone to every drawer’s CP/CMS relay. One ABB 1TGE102009R1001​ serves up to 16 drawers — the MNS scan polls each CP/CMS every cycle, aggregates motor current (3-phase), run-status, trip-cause code (overload / stall / GF / unbalance), alarm flags, and relay health, and presents it as a Profibus DP I/O image to the DCS. For the plant DCS engineer, the MNS section looks like one Profibus slave with a structured data map; for the MCC panel builder, the ABB 1TGE102009R1001​ means no separate gateway PLC, no extra DIN space, no custom ladder to poll 16 relays — ABB did it in the MNS firmware. This is the architectural win of MNS Digital: the ABB 1TGE102009R1001​ + CP/CMS + MNS bus = visibility without engineering.Profibus DP 12 Mbps to plant DCS masters:The upward face of the ABB 1TGE102009R1001​ is a standard Profibus DP slave (DB9 female, B-cable pinout). It auto-negotiates speed with the DCS master (typically 1.5 Mbps or 3 Mbps in MCC-to-MCR runs of 200–500 m; 12 Mbps max for short in-panel runs). The GSD file for the ABB 1TGE102009R1001​ is available from ABB (MNS Digital package), so importing into Siemens Step 7 / TIA or ABB Control Builder is a 2-minute job. The Profibus image carries cyclic I/O (motor current, status bits, trip bits) and supports acyclic services (DCS reads the CP/CMS relay’s trip-log, or writes a remote-reset to a stalled motor) — which means the control-room operator can ACK a motor trip and re-init the drawer contactor (if the interlock allows) without walking to the MCC room. On a WWTP with 30 MNS sections across 4 pump stations, that remote visibility via the ABB 1TGE102009R1001​ is what lets one operator cover the whole site.LED diagnostics for walkthroughs:Four LEDs on the ABB 1TGE102009R1001​ front — Pwr (green, 24 V present), Run (green blinking = MNS scan healthy, 16 drawers polling OK), Comm (yellow blink = Profibus traffic to DCS master), Fault (red = MNS bus error or Profibus slave error). An MCC walkthrough tells the electrician: “Pwr on, Run dark, Comm blinking” = MNS bus lost (check the CP/CMS in drawer 4 that someone just swapped and didn’t seat the MLink plug), not a ABB 1TGE102009R1001​ fault. “Pwr on, Run blinking, Comm dark, Fault off” = Profibus cable cut or DCS master lost (check the DB9 patch to the Profibus trunk, check the terminating resistor — the ABB 1TGE102009R1001​ itself has a built-in term enable jumper if it’s the last slave on the segment). That diagnostic clarity avoids the “MCC section dark, swap the MLink” reflex that wastes a good ABB 1TGE102009R1001.DIN-rail, low power, MNS PSU-friendly:The ABB 1TGE102009R1001​ draws <2 W from the MNS section’s 24 V DC PSU (which also feeds the 16 CP/CMS relays’ control-side, the MNS bus repeaters, and the section’s status LEDs). A typical MNS section 24 V PSU is 10 A class — the ABB 1TGE102009R1001​ is a rounding error. DIN-rail mount means the MNS panel builder drops it in the comm compartment during cubicle assembly; for MRO swaps, it’s release-clip + unplug + seat + re-plug DB9 + restore 24 V — <10 minutes. The spring-cage terminals on the ABB 1TGE102009R1001​ front hold the MNS bus pair (typically 2× 0.75 mm² shielded, pre-homed from the MCC backbone) and the Profibus DB9 breakout (A/B/+5V/shield, 2× 0.25 mm² twisted pair + shield). No screwdriver torque fights — spring-cage is consistent.R1001 (Profibus) vs R1002 (Modbus) sibling clarity:ABB sells the MLink in two upward-interface flavors under nearly identical 1TGE102009 part numbers: R1001 = Profibus DP​ (the subject here), R1002 = Modbus TCP​ (RJ45, 10/100 Mbps, typically to ABB AC800M or a Modbus-TCP-capable DCS). The ABB 1TGE102009R1001​ downward MNS bus is identical — same 16-drawer capacity, same scan, same CP/CMS compatibility — only the upward face changes. For spare-parts buyers, this means: confirm the plant’s MCC→DCS protocol before ordering. A WWTP on Siemens S7-400 Profibus buys R1001; a greenfield on ABB AC800M with Modbus TCP buys R1002. Mixing them on the same MNS fleet is fine (some sections Profibus, some Modbus) — the ABB 1TGE102009R1001​ and R1002 are mechanically identical, just different firmware/GSD.Compatibility across CP/CMS generations:The ABB 1TGE102009R1001​ MLink bus talks to ABB’s CP-E (current CP series, 3-phase current measurement, thermal overload, ground fault, communications-enabled), CP-M (compact CP for smaller drawers), and legacy CMS (older MCC relay, still in many 2005-vintage MNS cubicles). This backward compat matters because an MNS cubicle might have 8 drawers with CP-E (new in 2020 retrofit) and 8 drawers with CMS (original 2003 fit) — one ABB 1TGE102009R1001​ scans both without config changes. The MNS scan auto-discovers the relay type on each drawer position (the MNS bus addresses by drawer slot, not by relay model), so adding a CP-E during a drawer retrofit doesn’t require touching the ABB 1TGE102009R1001​ config — just seat the new relay, the MLink re-scans, the DCS sees the same data map (motor current, trip-cause) because ABB kept the CP/CMS→MLink→Profibus data map stable across generations. That’s the MNS “future-proof” story, and the ABB 1TGE102009R1001​ is the piece that carries it.