HomeResourcesOil & Gas Field Device Protocols
Device Protocols

What are the Oil & Gas field device protocols?

ROC, Enron Modbus, ABB Totalflow, Bristol IP, and Floboss — these are the proprietary protocols that oil and gas flow computers use to report electronic flow measurement (EFM) data. They are specialized, narrower in audience than Modbus or DNP3, and essential if your SCADA or data platform needs to pull custody transfer records, historical logs, and alarm data from field flow computers.

Last reviewed: 2026Reading time: ~10 minTopics: ROC, Enron Modbus, ABB Totalflow, Bristol IP, Floboss, EFM, flow computer, custody transfer, TOP Server

What is EFM and why does it need specialized protocols?

Electronic Flow Measurement (EFM) is the process of using microprocessor-based flow computers to calculate and record gas or liquid volumes at a measurement point — typically a pipeline meter run, a well, a compressor station, or a custody transfer point. The flow computer reads raw sensor data (differential pressure, static pressure, temperature, flow pulse counts), applies the appropriate flow calculation standard (AGA-3, AGA-7, AGA-9, ISO 5167), and stores the result as an archive of periodic records — typically hourly log entries, daily totals, event logs, and alarm histories.

This archived data is what oil and gas operators, pipeline companies, and regulators need. Gas volume measurements at custody transfer points are the basis for commercial transactions — pipeline tariffs, royalty payments, and regulatory compliance reports all depend on the accuracy and completeness of the EFM archive. Getting that archive off the flow computer and into a back-office system reliably, completely, and with the original timestamps intact is the core problem that O&G field protocols solve.

Why not just use Modbus? Modbus can read real-time process values from a flow computer — current flow rate, pressure, temperature. What it cannot do is efficiently retrieve the stored EFM archive records: hourly logs, daily volumes, event logs, and alarm histories that are indexed by timestamp and record number inside the flow computer's proprietary database. The O&G protocols define the specific message formats, record structures, and retrieval sequences required to pull these archives correctly. Using Modbus for EFM data collection typically means building a custom polling and reassembly layer in the SCADA application — the dedicated protocols solve this problem at the driver level.

What EFM data looks like

EFM data chain — from physical measurement to back office
🌡️
Sensors
Differential pressure, static pressure, temperature, pulse counter
🖥️
Flow Computer
Applies AGA-3/7/9 calculation, stores hourly logs & event archive
📡
Field Protocol
ROC, Enron, Totalflow, Bristol — retrieves archive over serial or TCP
⚙️
OPC / EFM Exporter
Translates to standard format for SCADA, flow management, billing
🏢
Back Office
Gas accounting, regulatory reporting, custody transfer settlement

The key EFM record types that flow computers archive and that O&G protocols are designed to retrieve are:

  • Periodic (Interval) records: Typically hourly averages or totals of flow rate, volume, pressure, temperature, and other measured variables. These are the primary records used for gas accounting and billing.
  • Daily records: Daily summary totals of volume and energy content, often used as the basis for regulatory reporting and nomination management.
  • Event records: Timestamped log of configuration changes, power cycles, communication failures, and operator actions — essential for the audit trail required by custody transfer agreements and regulatory oversight.
  • Alarm records: Log of alarm activations and clearing, with timestamps.
  • Configuration data: The current meter configuration — orifice plate size, pressure tap locations, calculation parameters — that must accompany volume records to validate the calculation.
Data typeROC/FlobossEnron ModbusABB TotalflowBristol IP
Periodic (hourly) logsYes — Archive segmentsYes — History recordsYes — Periodic logsYes — Historical logs
Daily volume totalsYesYesYesYes
Event logYes — Event logVendor-dependentYesYes
Alarm logYesVendor-dependentYesYes
Real-time valuesYes — Points/parametersYes — Modbus registersYesYes
Configuration readsYes — Config segmentsLimitedYesYes

The protocols, one by one

ROC / Floboss
Fisher ROC Protocol & Floboss
Emerson (formerly Fisher Controls / Daniel) — most widely deployed O&G flow computer protocol in North America
Vendor: Emerson (ROC300, ROC800, Floboss S600+)
Transport: RS-232/RS-485 serial, TCP/IP
Port: TCP 4000 (ROC+), vendor-configurable

The ROC (Remote Operations Controller) protocol is Emerson's proprietary protocol for its ROC300, ROC800, and Floboss S600+ series flow computers — the dominant product line in North American gas measurement. ROC organizes device data into a point type / logical number / parameter number addressing scheme. Every configurable item in the flow computer — a measurement input, a calculated variable, a configuration parameter, an archive record — is a point with a specific type number, a logical instance number, and a parameter offset.

Archive data is accessed through ROC's Archive Segment mechanism: the host requests a specific segment (hourly log, daily log, event log) for a given meter run, and the device responds with the records in that segment as a structured block. The protocol handles its own record sequencing and acknowledgment, making it much more reliable than Modbus for EFM archive retrieval over noisy serial links.

The Floboss S600+ uses the same underlying protocol family but with extensions for multi-run meter stations and more complex archive structures. TOP Server's ROC driver covers both ROC and Floboss variants, including the TCP-based ROC+ communication mode used by modern Emerson hardware.

Enron Modbus
Enron Modbus
Extended Modbus specification for EFM — widely adopted across multiple vendors
Origin: Enron Corporation specification (now public)
Transport: RS-232/RS-485 serial, Modbus TCP
Vendors: Emerson, Honeywell, ABB, Yokogawa, and many others

Enron Modbus is an extension to standard Modbus that adds EFM-specific capabilities — primarily the ability to retrieve time-stamped historical records from flow computers. It was created by Enron Corporation in the 1990s as a way to standardize EFM data collection from multiple vendors using a single protocol, and was widely adopted across the industry even after Enron's demise.

The key additions over standard Modbus are: 32-bit floating point registers (Enron Modbus specifies how 32-bit floats are stored across two Modbus registers, with a defined byte order), 32-bit integer registers (again with a specified multi-register mapping), and critically, history record retrieval using Function Code 3 reads against a defined range of holding registers that map to historical archive entries, each containing a timestamp and a set of measured values.

The practical challenge with Enron Modbus is that the historical record structure — which registers map to which archive, what the timestamp format is, how many records a device stores — varies by vendor and even by device model. TOP Server's Enron Modbus driver handles the standard record retrieval pattern, and per-device configuration handles vendor-specific variations in record layout.

ABB Totalflow
ABB Totalflow
ABB's proprietary protocol for the Totalflow XFC and XRC flow computer product line
Vendor: ABB (Totalflow XFC, XRC, G4, G5 series)
Transport: RS-232/RS-485 serial, TCP/IP
Port: TCP 10001 (default)

ABB's Totalflow protocol is used by the Totalflow XFC (eXtended Flow Controller) and XRC (eXtended Remote Controller) product line — a significant installed base in North American gas measurement, particularly in midstream gathering and transmission applications. The protocol is fully proprietary to ABB and is not interoperable with other vendors' equipment.

Totalflow uses an application-layer messaging scheme where the host sends command packets to request specific data types — current register values, periodic log records, event records, alarm records, and configuration data. Like ROC, the archive retrieval mechanism is designed specifically for EFM: records are retrieved by log type and time range, with the device returning structured record blocks containing timestamps and the measured/calculated values for each log period.

A distinguishing characteristic of Totalflow devices is their built-in Modbus server: in addition to the native Totalflow protocol, most XFC and XRC units can be configured to serve real-time values via Modbus holding registers. This gives SCADA systems a simple way to poll current values without the Totalflow driver — but the Modbus interface does not provide access to the historical archive records. For EFM data collection, the native Totalflow protocol is required.

Bristol IP / BSAP
Bristol IP (BSAP over IP)
Emerson Bristol Babcock — pipeline SCADA RTUs and controllers
Vendor: Emerson (formerly Bristol Babcock) — ControlWave, Network 3000
Transport: RS-232/RS-485 serial (BSAP), TCP/IP (Bristol IP)
Port: TCP 1234 (default)

Bristol BSAP (Bristol Standard Asynchronous Protocol) is the communication protocol for the Bristol Babcock product line of pipeline RTUs and remote controllers — the Network 3000 series and ControlWave family. Emerson acquired Bristol Babcock in 2004, and the product line continues as Emerson's pipeline SCADA solution, though it is separate from the ROC/Floboss product family.

BSAP is a peer-to-peer serial protocol designed for pipeline SCADA environments where multiple RTUs communicate with a central master over serial radio or leased line links. Bristol IP is the TCP/IP adaptation of BSAP — same application-layer protocol, carried over TCP rather than serial. The protocol addresses devices using a signal number / local station number scheme and supports reading and writing data sets (groups of related values) rather than individual registers.

ControlWave devices also support Modbus and OPC DA servers in addition to BSAP, but for full access to the device's historical archive, configuration data, and event logs, the native Bristol IP driver provides the most complete access. TOP Server's Bristol IP driver covers both serial BSAP and TCP-based Bristol IP communication modes.

Daniel / S600
Daniel Industries / Floboss S600
Emerson Daniel flow computers for liquid measurement and fiscal metering
Vendor: Emerson (Daniel 2551, 3810, Floboss S600+)
Transport: RS-232/RS-485, TCP/IP
Primary use: Liquid measurement, LNG, multi-product pipelines

Daniel Industries (acquired by Emerson) specializes in liquid flow measurement — crude oil, refined products, LNG, and custody transfer liquid metering. Daniel flow computers and the Floboss S600+ for liquid applications use a protocol family that is related to but distinct from the gas-focused ROC protocol. Daniel's own proprietary protocol and ROC-based communication are both used across the product range.

For pipeline operators running both gas and liquid measurement, having an OPC server that handles both ROC (for gas measurement) and Daniel (for liquid measurement) from a single platform simplifies the SCADA architecture significantly. TOP Server covers this with its Emerson suite of drivers spanning both gas and liquid measurement product families.

How these protocols fit into a SCADA architecture

O&G field protocols sit at the bottom of the data stack — between the physical flow computer in the field and the OPC server or EFM platform that makes the data available to SCADA, gas accounting, and regulatory reporting systems. The architecture is consistent across all five protocol families:

O&G field data collection — typical architecture
1
Flow computers
ROC800, XFC, ControlWave, S600+, etc. — measuring, calculating, and archiving EFM data at the meter run or wellhead. Connected via serial or TCP over cellular/satellite/radio WAN.
2
OPC Server + O&G Drivers
TOP Server with ROC, Enron Modbus, Totalflow, Bristol IP drivers — polls real-time values and retrieves EFM archive records using the device's native protocol. Exposes all data via OPC DA/UA.
3
EFM Exporter
Software Toolbox EFM Exporters — reads EFM archive records from the OPC server and exports them in standard formats (Flow-Cal, PGAS, EnergySoft, XML) for gas accounting and billing systems.
4
Gas accounting / SCADA / Reporting
Flow-Cal, PAS, EnergySoft, OpenFlow, or custom gas management systems — receive the exported EFM data for volume allocation, royalty calculation, regulatory reporting, and custody transfer settlement.

What is an EFM Exporter? An EFM Exporter is a specialized software component that sits between the OPC server (which retrieves raw EFM records from the flow computer) and the gas accounting back-office system (which needs the data in a specific file format). Software Toolbox's EFM Exporters read EFM archive data from TOP Server's O&G drivers and write it in the formats that gas accounting platforms expect — Flow-Cal TFX/EX, PGAS, EnergySoft, or custom XML. This completes the chain from field device to back-office without any manual data export or custom scripting.

Software Toolbox products for O&G connectivity

OPC Server + O&G drivers
TOP Server — Oil & Gas Suite
TOP Server's Oil & Gas Suite bundles the ROC/Floboss, Enron Modbus, ABB Totalflow, Bristol IP, and Daniel drivers in a single licensed package. Each driver handles the full protocol conversation — real-time value polling, EFM archive segment retrieval, event log collection, and configuration reads — and exposes all data to OPC DA and OPC UA clients. Historical EFM records are surfaced as time-stamped tag arrays that EFM Exporters and SCADA historians can consume directly. The suite also includes Modbus variants used by smaller and non-standard flow computers on the same network.
EFM archive export
EFM Exporters
Software Toolbox's EFM Exporters are purpose-built software components that read EFM archive records (periodic logs, daily logs, event logs, alarm logs) from TOP Server's O&G drivers and export them in the standard file formats that gas accounting and custody transfer systems consume: Flow-Cal (TFX/EX), PGAS/B format, EnergySoft, OpenFlow, and custom XML. Exporters run on a scheduled basis, automatically retrieving new records since the last successful export and handling connection failures with configurable retry logic. They support multi-meter, multi-driver configurations, allowing a single exporter instance to collect from ROC, Totalflow, Bristol, and Enron Modbus devices simultaneously.
Remote edge collection
N3uron + TOP Server at the edge
For remote wellpad and compressor station deployments where the flow computer is connected over expensive cellular or satellite links, TOP Server and N3uron deployed on a local edge gateway collect EFM data locally, buffer it during link outages, and forward real-time values to the central SCADA via MQTT with report-by-exception. EFM archive records are forwarded on schedule via the EFM Exporters. This reduces WAN traffic dramatically compared to polling all values from a central SCADA server, and ensures no archive records are lost during link interruptions.

Frequently asked questions

What is the difference between a flow computer protocol and a PLC protocol?+

The fundamental difference is the type of data each is designed to deliver. PLC protocols (Modbus, EtherNet/IP, S7) are optimized for real-time control data: current register values, I/O states, setpoints. They assume a fast, reliable network with frequent polling and no need to retrieve historical records.

Flow computer protocols are optimized for EFM archive retrieval: pulling stored records — each containing a timestamp and a set of measured variables — from the device's internal database. The records must be retrieved in sequence, gaps must be detected and filled, and the protocol must handle the realities of remote field communication: slow serial links, satellite latency, cellular dropouts, and devices that may have been powered off during the collection window. ROC, Enron Modbus, and the others were designed with these specific challenges in mind.

Can I use Modbus to read EFM data from a flow computer?+

You can use standard Modbus to read real-time process values from most flow computers — current flow rate, pressure, temperature. These are typically mapped to standard Modbus holding registers and are accessible with any Modbus driver.

However, standard Modbus cannot efficiently retrieve the EFM archive — the historical log records with timestamps that gas accounting systems need. The Enron Modbus extension adds a defined mechanism for this, but it still requires the Enron-specific driver to correctly interpret the record structure. For ROC, Totalflow, and Bristol devices, the native protocol is the only supported mechanism for archive retrieval.

What is custody transfer and why does it require such precise data collection?+

Custody transfer is the measurement of gas or liquid volume at the point where ownership changes hands — where a producer delivers gas to a pipeline company, where a pipeline delivers to a distribution company, or where product is transferred between ships, tanks, or trucks. The volumes measured determine the financial settlement: how much the buyer pays, how much royalty is owed on produced gas, and what pipeline tariffs apply.

Because these measurements directly drive financial transactions often worth millions of dollars per month, the accuracy and completeness of the EFM archive is subject to contractual requirements, regulatory oversight (FERC in the US, provincial energy boards in Canada), and audit. A missing hourly record or an incorrect timestamp is not just a data quality issue — it may require a volume estimation procedure, a billing dispute resolution, or a regulatory notification. This is why the specialized EFM protocols that preserve record integrity and timestamps exist, and why EFM data collection requires more care than standard process data collection.

How does the EFM Exporter know which records it has already collected?+

The EFM Exporter maintains a "high water mark" — a record of the timestamp or record number of the last successfully exported record for each meter/device. On each collection run, the exporter requests records from that point forward, collecting only the new records since the last run. This prevents duplicate records in the gas accounting system while ensuring no records are missed.

When a connection to a flow computer has been down for an extended period, the flow computer's internal event buffer holds the records accumulated during the outage. On reconnection, the exporter detects the gap (last exported record timestamp vs. current device time), retrieves all records in the gap sequentially, and exports them with their original source timestamps. The back-office system receives a complete, contiguous history — not a gap followed by a sudden catch-up.

Does the ROC driver in TOP Server cover ROC800, ROC300, and Floboss S600+ in a single license?+

Yes. TOP Server's ROC driver covers the entire Emerson ROC/Floboss product family under a single driver license: ROC300 series (serial), ROC800 series (serial and TCP), and Floboss S600+ (TCP-based ROC+ protocol). The driver configuration specifies the device type and communication parameters, and the driver handles the appropriate protocol variant automatically. A single TOP Server configuration can poll ROC300 devices on serial links and ROC800/S600+ devices over TCP simultaneously.

What output formats do the EFM Exporters support?+

Software Toolbox's EFM Exporters support the major gas accounting and flow management file formats used in North American pipeline operations:

Flow-Cal TFX: The most widely used format for gas measurement data exchange. Required by Flow-Cal's FLOWPRO and TOTALFLOW software.

Flow-Cal EX (Extended): Extended Flow-Cal format for additional data types.

PGAS / PGAS-B: Pipeline Gas Accounting System format, used by several gas accounting platforms.

EnergySoft: Format for EnergySoft's gas management application.

OpenFlow: XML-based format for platforms using the OpenFlow standard.

Custom XML: Configurable XML output for integration with proprietary gas accounting systems.

The exporter can write files to a local directory, a network share, or an FTP/SFTP server, depending on how the downstream gas accounting system expects to receive the files.

Connecting O&G flow computers to your SCADA or gas accounting system?

Software Toolbox has been connecting ROC, Totalflow, Bristol, and Enron Modbus devices to OPC and gas accounting platforms for decades. TOP Server's O&G Suite plus EFM Exporters covers the full chain from field device to back-office report.

Ready to connect your O&G flow computers?

Software Toolbox has been connecting ROC, Totalflow, Bristol, and Enron Modbus devices to OPC and gas accounting platforms for decades. TOP Server's O&G Suite plus EFM Exporters covers the full chain from field device to back-office report.

Talk to an engineer