Siemens Micro 2000 HART Conversion: Why 4-20mA Won't Become HART

1. Problem Overview

The Siemens Micro 2000 residual chlorine analyzer is a wall-mount, multi-parameter wet-chemistry instrument that uses a measurement module (SFC or MFC electronic variant) to convert photometric sensor signals into analog and digital data. The analyzer's analog output is a single 0/4–20 mA channel with a load limit of <500 Ω and a stated accuracy of <0.5 % of full scale, galvanically isolated to 50 V relative to earth. The instrument is commonly applied in drinking-water disinfection loops, wastewater chlorination/dechlorination, and industrial process water treatment.

The recurring engineering question is: can the Micro 2000's 4–20 mA loop be "converted" into a HART signal so that a Yokogawa DCS (CENTUM VP, EXP5000, or a newer HIS) can poll device variables, diagnostics, and configuration over HART?

2. Why the Micro 2000 Cannot Be Retrofitted With HART

HART (Highway Addressable Remote Transducer) is a hybrid analog+digital protocol standardized as HART Protocol by the FieldComm Group. It encodes a 1.2 kbit/s Bell 202 FSK digital signal on top of a 4–20 mA current loop. To produce a valid HART signal, the transmitter must contain:

1. A HART-compliant FSK modem (typically an SMAR HT2012, TI AFE8820, or ADI AD5700/AD5700-1 analog front end).
2. A microprocessor running a HART stack that exposes a defined Universal Command set (commands 0, 1, 2, 3, 6, 11, 12, 13, 14, 15, 16, 17, 18, 19, and 48).
3. A registered Device Type (manufacturer ID, device ID, and Device Revision) with the FieldComm Group.
4. A published Device Descriptor (DD or EDD) and binary DD (DD/EDDL) file that HART masters (handheld communicators, DCS HART I/O cards, FDT/DTM hosts) require to interpret the device's variables, menus, and methods.
5. Polling address support (long-form address 1–63 with 4–20 mA, or multidrop mode 0 with 4 mA fixed current and digital-only variables).

The Micro 2000 datasheet and the Wallace & Tiernan product brochure for the SFC and MFC electronics explicitly enumerate the digital interfaces as RS-232 and RS-485 to a Wallace & Tiernan ChemWeb-Server, OPC server, or CMS software. There is no HART silicon, no FSK modem, and no HART DD registered for the Micro 2000 family. A passive "signal injector" attached to the loop cannot synthesize HART frames because the loop current is generated by the analyzer, not by the injector, and the DCS would see a corrupt composite waveform that fails HART physical-layer checks (start bit timing, parity, and preamble).

2.1 The DD File Problem

Even if a third-party hardware adapter could generate a plausible Bell 202 waveform, every HART master (375/475 Field Communicator, Yokogawa CENTUM HART I/O, Emerson AMS, PACTware) requires a Device Descriptor. The DD is a tokenized EDDL file that describes variables, methods, and menus. Without a published DD for the Micro 2000, the HART master will display the device as a generic "unknown manufacturer/device 0" and will only be able to read Universal Commands. Common Practice Commands (40-series) and device-specific commands cannot be parsed.

3. Micro 2000 Communication Architecture

The Micro 2000 family is built around two replaceable electronic modules that share a common sensor interface but differ in their I/O density:

• SFC (Single-Function Controller): Single 4–20 mA output, RS-232 service port, RS-485 fieldbus port, isolated sensor interface.
• MFC (Multi-Function Controller): Multiple 4–20 mA outputs (process variable plus optional temperature/auxiliary), RS-232, RS-485, and the same fieldbus options as the SFC.

Both modules connect to the Wallace & Tiernan ChemWeb-Server — a PC-based supervisory platform that historically used an OPC DA server to expose tag data to the plant DCS over Ethernet.

4. SFC vs. MFC Comparison

5. Available Communication Protocols on the Micro 2000

The Wallace & Tiernan product brochure for the SFC/MFC electronics module (document WT.040.565.000.IE.PS.0509) confirms that the fieldbus option card supports three industrial Ethernet / fieldbus protocols natively:

1. Profinet IO — Siemens-promoted industrial Ethernet; integrates directly with Siemens S7-1500/S7-400 PLCs and the Yokogawa CENTUM VP via the Yokogawa Profinet IO device license.
2. Profibus DP — Mature RS-485-based fieldbus; widely supported in legacy Yokogawa DCS I/O subsystems (e.g., ALP111, AAR145) as a DP-V0/V1 slave.
3. Modbus TCP — Open Ethernet protocol with a documented register map; supported on virtually every modern DCS, including Yokogawa CENTUM VP, Honeywell Experion, Emerson DeltaV, and ABB 800xA.

These are the only digital paths to the Micro 2000. The 4–20 mA output is a hard-wired analog channel without superimposed HART.

6. HART Protocol Technical Requirements (Reference)

The HART physical layer is a Bell 202 modem shifting between 1200 Hz (mark, "1") and 2200 Hz (space, "0") on the 4–20 mA loop. The average value of the FSK is zero, so it does not shift the DC loop current. Key timing parameters (per Texas Instruments SLAEH0 — A Basic Guide to the HART Protocol):

7. Alternative Path 1 — Modbus TCP Integration

Modbus TCP is the most direct replacement for the requested HART functionality. The Micro 2000's Ethernet option card exposes a documented holding-register map over TCP port 502. Integration steps with a Yokogawa CENTUM VP station:

1. Assign a fixed IP address to the Micro 2000 (e.g., 192.168.10.50/24) and confirm reachability from the CENTUM VP HIS station with ping 192.168.10.50.
2. In CENTUM VP Builder, create a new Communication Subsystem node, choose TCP/IP – Modbus/TCP driver, and define a polling group with a 1-second scan period.
3. Map the required process variables (chlorine concentration ppm, sample pH, sample temperature, flow switch, controller output) to Function Blocks (PVI, AIN) on the HIS.
4. Configure the Yokogawa ALR121 / AAR145 Modbus scanner card to poll the analyzer's register block; verify with the CENTUM VP Self-Diagnostic window that the device is online and the response timeout is < 500 ms.
5. Expose the same data over the Yokogawa Vnet/IP control bus for the operator HMI; lay down a faceplate showing live value, signal-quality, and any device-level alarms raised by the analyzer's status word.

Modbus TCP gives you deterministic access to all process variables, plus the analyzer's internal status word (0x0001 = device OK, 0x0002 = lamp failure, 0x0004 = sample flow low, 0x0008 = water detection alarm, 0x0010 = reagent low, 0x0020 = calibration due). This is functionally equivalent to a HART Diagnostic Variable read in operation.

8. Alternative Path 2 — Profinet IO / Profibus DP

If the Yokogawa DCS is already Profinet-capable (CENTUM VP R6.05 and later, or the ProSafe-RS subsystem), the Micro 2000's Profinet IO option card drops in as a slave device. The GSD file is supplied with the analyzer; the typical module slot is a 4-byte I/O module with the following assignment:

Profibus DP uses the same data map on a 244-byte I/O slot. On the Yokogawa side, the ALP111 (Profibus master, DP-V0) and ALP121 (DP-V1) cards can be configured to scan the Micro 2000 with a 4-ms cycle, well within the 1-second response time expected of a wet-chemistry analyzer.

9. Alternative Path 3 — OPC Server / ChemWeb Architecture

The legacy Wallace & Tiernan ChemWeb-Server still represents a viable path where the analyzer's RS-485 port is brought up as a Modbus RTU link to a ChemWeb PC, which then exposes tag data via an OPC DA server. The Yokogawa CENTUM VP (or any modern DCS) acts as an OPC client. This is the topology documented in the original Micro 2000 commissioning manual.

10. Yokogawa DCS Integration Options (CENTUM VP / VP6)

Recommendation: for a new install, deploy the Profinet IO or Modbus TCP option card and connect directly to a Yokogawa PROFIBUS/Profinet-capable subsystem. This eliminates the OPC PC, removes a single point of failure, and gives the operator full diagnostics comparable to a HART-enabled instrument.

11. HART Handheld Communicator Limitations

A common misconception is that a HART handheld communicator (Emerson 475, Meriam MFC5150, Honeywell HHC) can be inserted into the 4–20 mA loop and "speak" HART to the Micro 2000. The communicator is a master; it requires a slave. With no HART slave in the analyzer, the handheld will display "Device not found," "Polling address 0 — no response," or a generic "HART device not detected" banner. Loop current meters (Fluke 771, Beamex MC6) are similarly limited to displaying the DC mA value.

Models suitable for genuine HART commissioning (and useful on a plant where other analyzers are HART-enabled):

• Emerson 475 Field Communicator (legacy, discontinued) — HART 5/6/7, 3-year support end 2022.
• Emerson AMS Trex Device Communicator — HART 7, FSK modem, DD library updates via Wi-Fi.
• Meriam MFC5150 — HART 7, 24 V loop power, DD library.
• Yokogawa YHC5150X — HART 7 handheld, full DD library, integrated with CENTUM VP project context.
• ProComSol DevCom2000 — Bluetooth HART modem for tablets/PCs, useful for bench calibration.

12. What About 3rd-Party HART "Add-On" Modules?

Brands such as Phoenix Contact, Prosoft, Moxa, and Moore Industries sell HART concentrators, HART multiplexers, and HART-to-Modbus gateways. These products assume the field device is HART-capable. The gateway aggregates HART frames from up to 32 instruments on a multidrop loop and re-exposes the variables over Modbus TCP, Modbus RTU, or EtherNet/IP. Because the Micro 2000 never produces a HART frame, the gateway has nothing to aggregate.

A 4–20 mA current loop receiver (e.g., a 250 Ω sense resistor feeding an Arduino A/D) recovers only the DC process value, not the HART FSK, because the FSK is generated by the slave device's modem, not by the loop current. The TI HART reference design confirms that a passive loop tap cannot decode HART from a non-HART transmitter.

13. HART Handheld vs. Analyzer Feature Comparison

14. Recommended System Architecture

1. Install the Modbus TCP fieldbus option card in the Micro 2000 SFC or MFC electronics module. The card slots into the same connector as the RS-485 port; no firmware change to the SFC/MFC is required.
2. Assign a fixed IP address in the Yokogawa control network. The Micro 2000 supports 192.168.x.y with a /24 mask; DNS is not used.
3. Add a Yokogawa ALR121 (Modbus TCP scanner) in the same station as the HIS. Create a polling group of 8 registers with a 1-second cycle.
4. Map the process value (ppm) to a PVI block; map the status word to a 16-bit alarm block (ALM) with individually latched bits for lamp failure, flow low, water detection, and reagent low.
5. Build a Yokogawa HMI faceplate mirroring the Emerson AMS device faceplate — process value large font, status icons, calibration menu, and remote/auto control of the setpoint.
6. Add a Heartbeat alarm: if no Modbus response within 5 s, the DCS raises a "Micro 2000 comm loss" alarm and freezes the last good value with a quality flag of BAD per ISA-18.2 / IEC 62682 good/bad limits.

15. Verification Steps

1. From the Yokogawa HIS, open a Test Maintenance window and force the Micro 2000 register 40001 (process value) to 5000 (5.00 ppm). Verify the HMI faceplate reads 5.00 ppm within 1.5 s.
2. Force the status register to 0x0002 (lamp failure) and confirm the lamp-failure alarm is raised, displayed on the alarm summary, and logged with time-stamp and operator ID.
3. Disconnect the Ethernet cable at the analyzer end. Within 5 s the DCS must raise a communication-loss alarm. Reconnect; confirm auto-recovery within 1 polling cycle.
4. Run a network capture with Wireshark on the control network; verify that Modbus TCP requests are Modbus/TCP Transaction ID 0x0001, Function Code 03 (Read Holding Registers), addressed to the analyzer's IP.
5. Document the loop test result, the IP/port, the polling group definition, and the alarm priority in the loop folder; sign off per the plant's Management of Change (MOC) procedure.

16. Frequently Asked Questions