ABB XFC Series Flow Computer Maintenance Guide

Attention: XIMV's factory calibration data is stored in a separate E ² PROM and will not be erased even if a "cold start" is performed. The calibration corrections made by the user will be superimposed on the factory data, allowing the equipment to adapt to the on-site environment while retaining the original benchmark.

Modular IO expansion (TFIO): flexibly respond to on-site signal requirements

XFC 6413 and 6713 support TFIO (Total Flow I/O) modules, and the system automatically identifies module types through the I ² C bus, without the need for complex address dialing settings. All TFIO modules are designed for low power consumption (milliampere level) and industrial environments.

3.1 List of commonly used TFIO modules

Module type, channel number, typical applications

Analog input (AI) 8 4-20mA transmitter (requires external resistor), 0-5V signal

Analog output (AO) 4 controls I/P converter and speed controller

Digital quantity/pulse/state input (DI/PI/State) 8 (software optional) switch status, dry contact, low-frequency pulse (such as turbine flowmeter)

Digital output (DO) 8 alarm indication, solenoid valve control

RTD input 4 100 Ω platinum resistor (three wire or four wire)

Thermocouple input 4 J, K, T, E, S types

Valve Control 1 (Analog or Digital) Electric/Pneumatic Valve Positioning with Feedback

Communication module 1 (RS232/485/422 switchable) extended serial port

3.2 On site installation and troubleshooting of TFIO module

Installation steps:

Power outage: Disconnect the main battery and external charging power source.

Open the electronic chamber cover (be careful not to lose the sealing ring).

Align the TFIO module with the I ² C slot on the backplane and press it vertically until the two side clips are locked.

The module is automatically recognized without the need for manual address allocation. You can check whether the module exists and the channel status through the "IO Scanner" interface of PCCU32.

Common faults:

Symptom: The newly installed module cannot be seen in PCCU32.

Possible reason: The module is not securely plugged in; Or the module itself may malfunction. Try unplugging again, if it still doesn't work, replace the module.

Symptom: The analog input reading is abnormally full range or zero.

Possible reason: The circuit has not been formed; The external transmitter is not powered; Or input type configuration error (such as connecting 4-20mA signal to 0-5V channel). Check the wiring and channel configuration in PCCU32.

Symptom: No action on digital output.

Possible reason: Insufficient output driving capability. The DO of XFC is an open collector type and requires an external pull-up resistor or relay. Check if the external power supply is connected.

Communication configuration and protocol selection

The XFC series provides a wide range of options for remote data transmission. The standard configuration includes:

1 dedicated local configuration port (RS232, for PCCU32 connection).

Two user selectable serial ports (RS232 or RS485 can be selected through plug-in modules).

Additional serial ports can be added through the TFIO communication module.

4.1 Common protocols and application scenarios

Typical uses of protocol direction

Totalflow Native Low Power efficient and low-power communication between ABB devices (9600 baud typical)

Modbus RTU/ASCII (slave) integrated with SCADA system, PLC, HMI

Modbus RTU (master station) reads third-party intelligent instruments (such as ultrasonic flow meters, chromatographs)

Enron Modbus from Specific Historical Legacy Systems

Square-D replaces old RTUs

LevelMaster specialized for master/slave liquid level measurement

Btu 8000/8001 main/auxiliary calorific value calculation equipment

4.2 On site troubleshooting of communication faults

Problem: The upper computer cannot read XFC data through Modbus.

Troubleshooting process:

Physical layer inspection:

RS485: Confirm that wires A and B are not reversed, and the terminal resistance (120 Ω) is only enabled at both ends of the bus. Measure the line to line voltage, which should be around 200-500mV when idle (A high B low).

RS232: Confirm that TX/RX/GND correspond one-to-one, and that the baud rate and parity are consistent.

Parameter verification: Connect XFC using PCCU32 and enter the "Communication" settings:

Modbus slave address (must be the same as the request address of the upper computer).

Baud rate, data bits, stop bits, parity check.

Response delay (default is 0, can be increased to 50-100ms in case of data conflicts).

Register mapping:

The standard Modbus mapping table of XFC is user programmable. If the read data location is found to be incorrect, check whether the register address requested by the upper computer is consistent with the "Modbus Map" configured in XFC.

For example, instantaneous flow is usually mapped to 40001, but if it has been modified, it needs to be reconfirmed.

Using monitoring tools: Open "Port Monitor" in the "Test" menu of PCCU32 to view the raw messages sent and received by XFC in real time, and quickly locate whether the request has not arrived or the response is incorrect.

Software functional modules and on-site application examples