Skip to main content

Complete Guide to the Bristol FB300 RTU for Oilfield Automation

By NFM Consulting 5 min read

Key Takeaway

The Bristol FB300 is a remote terminal unit (RTU) used in oil and gas automation to collect field data and communicate with SCADA systems using protocols including DNP3 and Modbus. This pillar guide covers hardware, programming, SCADA integration, and troubleshooting for oilfield deployments.

Quick Answer

The Bristol FB300 is a remote terminal unit (RTU) used in oil and gas automation to collect field data and communicate with SCADA systems using protocols including DNP3 and Modbus. Manufactured by Bristol (now part of Emerson), the FB300 has been a workhorse in upstream oil and gas operations across the Permian Basin, Eagle Ford, and Gulf Coast for decades.

What Is the Bristol FB300?

The Bristol FB300 is an RTU designed for harsh oilfield environments where reliable data acquisition and remote control are essential. Unlike general- purpose PLCs, the FB300 was purpose-built for SCADA telemetry — collecting analog and digital signals from field instruments, executing local control logic, and communicating with SCADA masters over serial or Ethernet links.

The FB300 belongs to Bristol's ControlWave and ROC family of field controllers. It is widely deployed at tank batteries, wellhead platforms, compressor stations, pipeline meter stations, and produced water facilities. Its rugged design handles extreme temperatures, vibration, and the electrical noise common in oil and gas environments.

Key capabilities include:

  • Multi-channel analog input (4–20 mA, 1–5 V) and digital I/O
  • DNP3 Level 2 outstation for modern SCADA integration
  • Modbus RTU/TCP master and slave operation
  • BSAP (Bristol Synchronous/Asynchronous Protocol) for legacy systems
  • Local control logic for pump control, alarm annunciation, and flow calculation
  • Battery-backed operation for remote, solar-powered sites

Hardware Overview

The FB300 platform uses a modular architecture with a main processor board and plug-in I/O cards. Typical configurations include:

  • CPU module: Central processor with onboard serial ports (RS-232 and RS-485), Ethernet (on later models), and non-volatile memory for configuration and historical data.
  • Analog input cards: 8-channel or 16-channel cards accepting 4–20 mA, 1–5 V, or thermocouple inputs. Resolution is typically 12-bit or 16-bit depending on card model.
  • Digital I/O cards: Configurable discrete input and output channels for valve status, pump run, level switches, and alarm contacts.
  • Communication cards: Serial expansion for additional RS-232/RS-485 ports, or Ethernet cards for TCP/IP networking.
  • Power supply: Wide-range DC input (10–30 VDC typical), designed for solar/battery installations common at remote wellsites.

The backplane design allows field technicians to swap I/O cards without replacing the entire unit — a critical advantage when maintaining dozens of remote sites across a production lease.

Programming the FB300

The FB300 is configured and programmed using OpenBSI (Open Bristol Systems Interface) or legacy ACCOL (ACCess Oriented Language) tools. OpenBSI provides a graphical configuration environment where engineers define:

  • I/O point configuration: Map physical channels to logical point names, set scaling parameters, and define engineering units.
  • Control logic: Build function-block logic for pump sequencing, high/low alarms, PID loops, and flow calculations.
  • Communication setup: Configure DNP3 outstation parameters, Modbus register maps, and serial port settings.
  • Historical logging: Define which points to log, sample rates, and storage depth for trend data and compliance reporting.

ACCOL, the legacy programming language, uses a text-based approach where engineers write control programs using predefined function blocks. While ACCOL is still supported, most new FB300 deployments use OpenBSI for its graphical interface and improved diagnostics. See our detailed programming guide for step-by-step instructions.

SCADA Integration

The FB300 integrates with modern SCADA systems as a DNP3 Level 2 outstation, making it compatible with virtually every SCADA master platform in use today:

  • Ignition by Inductive Automation: DNP3 driver connects directly to FB300 outstations over serial or TCP.
  • GE Cimplicity / iFIX: Native DNP3 support for Bristol RTU polling.
  • OSIsoft PI (AVEVA PI): DNP3 interface nodes collect data from FB300 units for historian storage.
  • Schneider Electric ClearSCADA (Geo SCADA): DNP3 and Modbus drivers for multi-vendor RTU networks.
  • VTScada: Built-in DNP3 polling for Bristol RTU integration.

For sites still running legacy BSAP networks, protocol converters or gateway devices can bridge BSAP-to-DNP3, allowing gradual migration to modern SCADA infrastructure without replacing field hardware. See our SCADA integration guide for detailed configuration steps.

Oilfield Automation Examples

The FB300 is commonly deployed in these oilfield automation scenarios:

Tank Battery Monitoring

At tank batteries, the FB300 monitors oil and water tank levels (via 4–20 mA level transmitters), pump status, valve positions, and gas detection alarms. Local logic can automate LACT unit operation, trigger high-level shutdowns, and calculate custody transfer volumes.

Wellsite Rod Pump Control

The FB300 monitors rod pump motor current, casing pressure, tubing pressure, and flow rate. Control logic manages pump-off detection (based on load or fluid level), automatic restart timers, and dynamometer card analysis when paired with compatible load cells.

Pipeline Meter Stations

At custody transfer and allocation meter stations, the FB300 performs AGA flow calculations (AGA-3 orifice, AGA-7 turbine, AGA-8 compressibility), logs flow data at configurable intervals, and reports instantaneous and accumulated volumes to the SCADA master.

Compressor Station Monitoring

Compressor stations use the FB300 to monitor suction/discharge pressures, temperatures, vibration levels, and compressor run status. Local logic provides high-vibration and high-temperature shutdown protection.

Troubleshooting

Common issues with FB300 deployments include communication timeouts, analog input drift, and configuration mismatches after firmware updates. Our troubleshooting guide covers systematic diagnostic procedures including LED status interpretation, serial port loopback testing, and DNP3 event log analysis.

Bristol FB300 Article Series

This guide is the starting point for a comprehensive series on the Bristol FB300 RTU. Explore the detailed sub-articles below:

Frequently Asked Questions

Ready to Get Started?

Our engineers are ready to help with your automation project.