FOUNDATION Fieldbus H1 is a two-wire, digital, multi-drop field communication protocol designed for process automation. Developed by the Fieldbus Foundation (now FieldComm Group), it enables bi-directional digital communication with field devices while powering them over the same two wires. Understanding FOUNDATION Fieldbus is essential for engineers working in refineries, petrochemical plants, and pharmaceutical facilities where it remains widely deployed.

How FOUNDATION Fieldbus Works

Unlike 4-20 mA, where each device needs its own dedicated pair of wires back to the control room, FOUNDATION Fieldbus H1 uses a multi-drop topology. Multiple devices share a single segment (a pair of wires), each with its own address. Communication runs at 31.25 kbps and uses Manchester encoding to combine power and data on the same cable.

Each H1 segment typically supports 4-16 devices, depending on power consumption per device, cable length, and whether you use a Segment Power Conditioner (SPC) or an intrinsically safe barrier. Power is typically 24 VDC injected at the segment conditioner; device current draw is 10-20 mA each.

The key distinguishing feature of FOUNDATION Fieldbus is the distributed function block execution model. Unlike HART, where the device simply responds to poll requests, a FOUNDATION Fieldbus device can execute control function blocks (PID, signal characteriser, integrator) directly in the field device. This means a pressure transmitter can execute a PID loop that directly drives a control valve on the same segment, without the DCS controller being in the execution path.

Function Block Architecture

FOUNDATION Fieldbus devices are described by device descriptions (DD files) that define their function blocks and parameters. The standard function blocks include:

  • AI (Analog Input): Reads a measured value from the physical sensor and applies engineering unit conversion, filtering, and status generation. Every transmitter has at least one AI block.
  • AO (Analog Output): Drives a physical output (valve positioner setpoint, motor speed reference). Handles fallback modes if communication is lost.
  • PID: A full PID control algorithm that can run inside the field device. Output connects directly to an AO block on a valve positioner on the same segment.
  • Signal Characteriser (SC): Applies linearisation curves — used for flow transmitters with non-linear flow elements.
  • Integrator (IT): Accumulates a flow quantity over time. Used for totalising flows.

The DCS host configures the function block linkages and provides supervisory setpoints, but the execution runs in the devices themselves. This is called a “control in the field” architecture.

Wiring and Segment Design

Proper segment wiring is critical for FOUNDATION Fieldbus performance. Key design rules:

  • Cable type: Use Type A (shielded, twisted pair, 18 AWG) cable for best noise immunity. The maximum segment length with Type A cable is 1,900 metres at 31.25 kbps. Type D unshielded cable is limited to 200 metres.
  • Termination: Each segment must have exactly two terminators (one at each end). A terminator is a 100-ohm resistor in series with a 1 microfarad capacitor. Most segment power conditioners have a built-in terminator; a device must be installed at the far end of the spur. Incorrect termination causes signal reflections and communication errors.
  • Spur length: Spurs (branches from the trunk cable to individual devices) must be kept short — maximum 60 metres in non-intrinsically safe applications. Longer spurs cause signal reflections.
  • Intrinsic safety: For hazardous areas (Zone 0/1 or Div. 1), use FISCO (Fieldbus Intrinsically Safe Concept) or Entity model zener barriers or galvanic isolators. FISCO simplifies cable calculation by defining standard power supply and cable parameters.

Commissioning FOUNDATION Fieldbus Segments

Commissioning a FOUNDATION Fieldbus segment follows a defined sequence:

  1. Physical layer check: Measure segment voltage (typically 9-32 VDC at device terminals), signal levels (minimum 150 mV peak-to-peak at the farthest device), noise level, and verify termination. Use a fieldbus analyser (Relcom FBT-6, Pepperl+Fuchs FieldConnex Segment Checker) for accurate measurements.
  2. Device registration: Connect the segment to the host (via a FOUNDATION Fieldbus interface card in the DCS). The host will discover all devices on the segment and assign them to the project configuration based on their device tags and addresses.
  3. Function block configuration: Download the function block configuration (AI modes, PID parameters, AO fallback modes) to each device through the host engineering tool.
  4. Link Active Scheduler (LAS) verification: The LAS is the bus master that schedules all communication on the segment. Verify that the designated LAS (usually the host interface card) has assumed the role and that no device has incorrectly taken over as LAS.
  5. Control in the field testing: For segments using distributed control, verify that the function block schedule runs at the configured macrocycle rate and that the PID output correctly drives the valve without DCS involvement.

Common Commissioning Problems

  • Duplicate node addresses: Two devices with the same H1 address will conflict. Always pre-assign unique addresses before connecting devices to the segment.
  • Missing termination: Segments with one or no terminator will have signal integrity problems, especially under heavy communication load. Verify terminator count with a fieldbus analyser.
  • Ground loops: Multiple earth connections on the cable shield cause circulating ground currents that appear as noise on the signal. Ground the shield at one point only, typically at the segment power conditioner.
  • DD file mismatch: The DCS host may not recognise device parameters if the Device Description (DD) file version does not match the device firmware version. Always load the correct DD file before connecting a new device.

FOUNDATION Fieldbus vs HART: When to Use Which

HART is a better choice for small, scattered field devices where the cost and complexity of segment design is not justified. FOUNDATION Fieldbus is the better choice when you need more than 16 devices in a concentrated area, when you want distributed control execution in the field, or when your DCS is designed around a FOUNDATION Fieldbus architecture (ABB 800xA with AF100, Honeywell Experion with FIM4, Emerson DeltaV with FF interface cards).

In new greenfield projects, PROFINET and EtherNet/IP are increasingly preferred over FOUNDATION Fieldbus for new installations due to higher bandwidth and simpler engineering. However, the installed base of FOUNDATION Fieldbus devices in process plants worldwide is large, and engineers will be commissioning, troubleshooting, and maintaining FF segments for decades to come.