Description
ABB 1TGE120021R0010
Product Overview
The ABB 1TGE120021R0010 is an MLink communication gateway used within the ABB MNS iS low-voltage motor-control and switchgear architecture. Its purpose is straightforward but important: it provides a communications path between the MNS iS system and a higher-level process-control or supervisory environment. For this exact hardware ID, ABB documentation identifies Modbus RTU/TCP as the fieldbus interface and lists the unit as MLink Hardware Version 2. The same documentation places 1TGE120021R0010 in the MNS iS hardware generation used from MNS iS V6.1 onward.
In a plant automation system, the ABB 1TGE120021R0010 does not function as a conventional PLC CPU or analog/digital I/O card. It acts as the communications gateway for MNS iS motor-management information. Depending on the configured interface, Modbus RTU can operate over RS-232, RS-422, or RS-485, while Modbus TCP uses Ethernet. ABB also documents MLink web-interface, OPC connectivity, and time-stamping capabilities as system functions that can be available across MLink types.
That distinction matters when replacing a failed unit. The gateway’s hardware identification, MNS iS software generation, fieldbus configuration, MLink application files, network settings, and downstream DCS configuration all have to agree. ABB specifically documents downloading MLink configuration through MNavigate, and communication troubleshooting includes checking Modbus addressing, baud rate, parity, stop bits, interface selection, and IP configuration.
Product Introduction
A failed MLink gateway can make an otherwise healthy MNS iS installation appear disconnected from the plant control system. The 1TGE120021R0010 provides the communications bridge needed to move MNS iS information toward a Modbus-based supervisory or DCS environment.
For a legacy replacement, the part number alone is not enough. This is an application-configured communications device; MLink software, network parameters, Modbus settings, and MNS iS generation must be checked before commissioning.
Key Technical Specifications
| Parameter | Specification |
|---|---|
| Product Model | ABB 1TGE120021R0010 |
| Extended Product Type | MLink |
| Product Type | Communication Gateway |
| Application | ABB MNS iS low-voltage switchgear / motor-management system |
| Hardware Version | MLink Hardware Version 2 |
| Fieldbus | Modbus RTU / Modbus TCP |
| Serial Interfaces | RS-232 / RS-422 / RS-485, configuration-dependent |
| Ethernet | Ethernet TCP/IP |
| MNS iS Version Reference | From V6.1 onward for this hardware ID |
| PROFINET | MLink architecture supports PROFINET IO; exact fieldbus option must be verified before treating this specific R0010 unit as a PROFINET device |
| Web Interface | Available as an MLink software function |
| OPC Connectivity | Available as an MLink software function |
| Time Synchronization | Available as an MLink software function |
| Redundant Operation | Available where the appropriate MLink configuration/software is installed |
| Product Width | 160 mm |
| Product Height | 140 mm |
| Product Depth | 250 mm |
| Product Net Weight | Approx. 2 kg |
| Country of Origin in ABB Product Data | Czech Republic |
| Declaration | CE declaration documented |
ABB’s product data identifies 1TGE120021R0010 specifically as “MLink (Hardware Version 2, Fieldbus: Modbus RTU/TCP, PROFINET IO),” while the MLink hardware-selection table identifies the R0010 hardware ID specifically with the Modbus interface. The exact protocol enabled on a particular installed unit should therefore be verified from the configuration rather than inferred from the family description.
1TGE120021R0010
Major Features / Practical Advantages
Dedicated MNS iS Communications Gateway
The 1TGE120021R0010 is designed around ABB’s MNS iS architecture. That makes it different from a generic protocol converter. It handles the MNS iS-side data structure and communicates with the plant-level system through the configured fieldbus interface.
For an existing MNS iS installation, retaining the correct MLink hardware generation is often more important than simply finding a gateway with the same physical dimensions.
Modbus RTU and Modbus TCP
The R0010 variant is documented for Modbus RTU/TCP. Modbus RTU can use RS-232, RS-422, or RS-485 depending on the selected MLink interface. ABB’s Modbus documentation also provides configurable slave addressing, baud rate, parity, stop bits, and interface selection.
Documented Modbus RTU baud rates include 9,600, 19,200, 38,400, and 115,200 baud. The default slave address is documented as 247, with an allowed range of 1–247.
Ethernet-Based Modbus TCP
For a Modbus TCP installation, the MLink provides an Ethernet path to the supervisory system. IP configuration is part of commissioning, and ABB’s documentation specifically notes that IP-address settings should be coordinated with the network administrator.
This means replacing the hardware without restoring the original network configuration can leave the MNS iS system physically operational while the DCS remains unable to communicate.
MLink Web Interface
ABB documents a web interface that can be activated in MLink. A connected PC or MView station can use the web interface to display MLink information. This provides a useful diagnostic path when troubleshooting communications without immediately modifying the MNS iS field devices.
OPC Connectivity
MLink can provide data to the MNS iS OPC Server when the corresponding software module is activated. This is relevant in installations where MNS iS information is passed to a supervisory server rather than directly mapped into a PLC. The OPC capability is a software function, however, so it should not be assumed solely from the hardware part number.
Configuration Through MNavigate
MLink configuration is handled through MNavigate. ABB documentation states that Modbus parameters are configured in MNavigate and then downloaded to MLink, with a restart required for the settings to take effect.
That makes configuration backup an important part of replacement work.
Hardware Generation Identification
ABB explicitly differentiates older MLink hardware IDs from 1TGE120021R0010. The documentation states that older 1TGE1020x9Rxxxx hardware is associated with MNS iS versions up to V6.0, while 1TGE120021R0010 is the hardware available from V6.1 onward.
This is a useful distinction when dealing with older MNS iS cabinets because a visually similar communications module may belong to a different software generation.
Related Products
- ABB 1TGE120021R0110 — MLink hardware associated with the PROFIBUS DP/DP-V1 interface option.
- ABB 1TGE1020x9Rxxxx — Earlier-generation MLink hardware used with MNS iS versions up to V6.0.
- ABB 1TGE120016R0104 — MNS iS switchgear-bus connector arrangement for non-redundant Modbus configurations.
- ABB 1TGE120016R0103 — Switchgear-bus connector arrangement associated with dual-redundant MNS iS configurations.
- ABB MLink — Communication gateway family used to interface MNS iS with DCS and supervisory systems.
- ABB MNS iS — Low-voltage motor-control and switchgear platform served by the MLink gateway.
- ABB MNavigate — Engineering/configuration software used for MLink configuration.
- ABB MNS iS MControl — MNS iS motor-management architecture communicating through the MLink interface.
FAQ
What is ABB 1TGE120021R0010?
It is an ABB MNS iS MLink communication gateway, Hardware Version 2, identified for the Modbus RTU/TCP fieldbus configuration.
Is 1TGE120021R0010 a PLC CPU?
No. It is a communications gateway for the MNS iS motor-control/switchgear architecture. It should not be treated as a general-purpose PLC processor or standard analog/digital I/O module.
Can 1TGE120021R0010 communicate with a DCS?
Yes. MLink is specifically intended to provide communications from MNS iS toward a process-control system. The R0010 hardware is documented for Modbus RTU/TCP, while other MLink variants provide different fieldbus options.
What Modbus RTU settings does it use?
ABB documents configurable slave address, baud rate, parity, stop bit, and serial-interface type. The documented baud rates are 9,600, 19,200, 38,400, and 115,200 baud; the default slave address is 247. These settings are configured through MNavigate.
Can I hot-swap the MLink?
Do not assume hot replacement. ABB’s available MLink documentation describes installation, configuration, redundancy, and troubleshooting but should not be interpreted as a blanket hot-swap authorization for every cabinet configuration. Follow the MNS iS maintenance procedure and isolate the applicable power/control circuits before removing the gateway unless the installed system specifically documents online replacement.
Does 1TGE120021R0010 support firmware v3.1?
The part number does not establish a firmware version such as v3.1. MLink uses software modules, image/application files, and MNavigate configuration. ABB documentation gives software requirements for particular MNS iS releases, so the installed MLink software should be checked directly before a replacement is commissioned.
Is 1TGE120021R0010 the same as the PROFIBUS MLink?
No. ABB’s hardware-selection table distinguishes the 1TGE120021R0010 Modbus hardware from 1TGE120021R0110, which is the PROFIBUS DP/DP-V1 variant.
Can I replace an older 1TGE1020x9Rxxxx with 1TGE120021R0010?
Not automatically. ABB identifies the older hardware generation with MNS iS versions up to V6.0 and 1TGE120021R0010 with versions from V6.1 onward. The MNS iS software release and MLink application files therefore need to be checked before making that substitution.
Procurement Note
For ABB 1TGE120021R0010, the most important procurement checks are MNS iS version, fieldbus configuration, MLink software, and saved network parameters.
Before approving a replacement, verify:
- Exact ABB part number: 1TGE120021R0010.
- MNS iS software/system generation.
- Modbus RTU or Modbus TCP architecture.
- RS-232/RS-422/RS-485 requirement if using Modbus RTU.
- Modbus slave address and baud rate.
- IP address, subnet, and gateway if using Modbus TCP.
- MLink image/application versions.
- MNavigate version and configuration backup.
- Redundant versus non-redundant system architecture.
- DCS driver and register mapping.
The configuration is not something I would recreate from memory. ABB explicitly documents downloading MLink application files through MNavigate, and its troubleshooting material provides specific communication parameters that need to be preserved.
For New Surplus, verify the actual hardware identification and version marking. For Used or Refurbished equipment, ask for evidence that the unit boots correctly, establishes the expected MNS iS-side communication, and supports the required Modbus interface. A power-up test alone does not prove compatibility with the customer’s MNS iS software generation or DCS configuration.
