What Is Foundation Fieldbus?

Back to Blog

H1 and HSE: The Two Layers

Foundation Fieldbus H1 is the field-level network. It runs at 31.25 kbit/s over a single twisted pair that both powers the instruments and carries data, and it supports intrinsic safety for hazardous areas - making it well suited to transmitters, valve positioners, and analysers in refineries and gas plants. A key feature is control-in-the-field: PID and other function blocks can execute inside the field devices themselves, so a control loop can keep running even if the host controller is unavailable.

HSE (High Speed Ethernet) is the FF backbone layer, running at 100 Mbit/s over standard Ethernet to link H1 segments, host systems, and linking devices. In practice, H1 dominates real installations; HSE is used to aggregate segments back to the DCS or host.

Foundation Fieldbus, DCS, and SCADA

Foundation Fieldbus is closely associated with distributed control systems (DCS) in large continuous plants. Field instruments on H1 segments connect through linking devices or fieldbus interface cards into the DCS, which handles supervisory control, operator displays, and historization. Because FF carries rich diagnostics, it also feeds asset-management and predictive-maintenance workflows.

A SCADA or cloud platform typically consumes Foundation Fieldbus data one level up, reading process values and device status from the DCS or a fieldbus host over OPC UA or Modbus TCP rather than tapping the H1 bus directly. This means an operator can add cloud-based remote monitoring, cross-site dashboards, and long-term historian storage - for instance via a platform like Merobix reading the host over OPC UA - without disturbing the intrinsically safe field wiring or the certified control loops.

H1 Segment Design in Practice

An H1 segment is a trunk with short spurs, fed by a fieldbus power supply through a power conditioner, and terminated at exactly two points - one terminator at each end of the trunk. Device couplers connect the spurs, and most modern ones include spur short-circuit protection so a single shorted instrument does not take down the segment. How many devices a segment carries is not a single number: it falls out of the power budget (each instrument draws its quiescent current from the segment), cable type and length, spur lengths, and the hazardous-area method, all resolved in the project's segment design calculation.

In classified areas the design choices multiply. Intrinsic safety concepts such as FISCO were developed specifically to make IS fieldbus segments practical, and high-energy-trunk architectures keep the trunk outside the IS boundary while individual spurs remain energy-limited. Which approach fits a given unit is an area-classification and project decision, made against the site's hazardous-area documentation and with the people responsible for it.

The Link Active Scheduler and the Macrocycle

H1 is deterministic by design. A Link Active Scheduler (LAS) owns the segment's schedule: within a repeating macrocycle it compels each publishing device at its planned moment, so the AI block in a transmitter publishes, the PID block subscribing to it executes, and the AO block in the positioner receives its command, in coordinated order every cycle. The unscheduled time between compelled transfers carries acyclic traffic - diagnostics, configuration, maintenance reads - without disturbing the control schedule.

The LAS normally runs in the host's fieldbus interface, but the capability can also live in field devices as a backup. If the primary scheduler disappears, a backup LAS takes over and the segment keeps its schedule - the property that makes control-in-the-field genuinely robust rather than a demonstration feature. Macrocycle configuration is part of host engineering and is set against the execution rates the unit's loops actually require.

Troubleshooting a Misbehaving Segment

Symptom	First suspects
Devices drop off and rejoin intermittently	Wrong terminator count, loose trunk connection, moisture in a junction box
One device unreachable, the rest healthy	Its spur, its coupler port, or the device itself
Whole segment down	Power supply or conditioner, trunk short, host interface card
Rising retries and communication errors	Shield or grounding faults, noise coupled from adjacent power cabling

A fieldbus segment tester at the far end of the trunk tells you most of what matters: segment voltage compared against the design calculation, signal level, and noise. Because the physical layer is shared, one bad actor can disturb everyone on the segment, so isolating spurs one at a time is the standard narrowing move. In classified areas, opening enclosures and lifting connections follows the site's hazardous-area and work-permit procedures - the segment being 'just communications' does not exempt it.

Foundation Fieldbus in 2026: Brownfield and Greenfield

The installed base in refineries, gas plants, and chemical sites is large, mature, and worth maintaining well: the instruments are paid for, the diagnostics are rich, and a properly looked-after segment is reliable. For new projects the calculus has shifted - Ethernet-APL brings two-wire, loop-powered Ethernet to process instruments, and conventional 4-20 mA with HART remains the pragmatic choice for simpler units - so FF is now one option among several rather than the default digital answer. The right choice is project-specific.

Whatever the field layer, the supervisory pattern holds: the host aggregates, and upstream systems consume from the host. The underused opportunity in existing FF plants is the diagnostic layer - device alerts and block statuses that too often never leave the asset-management console. Mapping them into the historian alongside process values, for example when connecting OPC UA to cloud SCADA, turns the fieldbus's self-knowledge into trends a maintenance planner can actually schedule against.

Frequently Asked Questions