Gilbarco Dispenser Twowire Protocol For Third Party - Pump Controllers New

| Feature | Two-Wire Protocol | Modern Gilbarco (Ethernet/D-Box) | | :--- | :--- | :--- | | Fuel price lookup | Yes (polled) | Instant | | Receipt printing | No | Yes | | Loyalty/card reader | No (simple auth only) | Yes | | Grade status (full/empty) | No | Yes | | Multiple POS per site | Not supported | Yes |

Because Gilbarco uses a specific current loop (typically 45mA at 12VDC), third-party controllers cannot usually connect directly via standard RS-232 or RS-485 without an interface converter.

Connecting a standard PC or a modern PLC to a Gilbarco dispenser often requires an interface converter to bridge the gap between RS-232/USB/RS-485 and the 2-wire current loop.

Gilbarco Two-Wire Protocol is a proprietary current-loop serial communication standard used to interface Gilbarco fuel dispensers with Point-of-Sale (POS) systems or third-party pump controllers

Fuel retail automation relies on robust communication between the Point of Sale (POS) system, the Forecourt Controller (FCC), and the fuel dispensers. Gilbarco Veeder-Root dominates this space with its proprietary two-wire current loop protocol. For third-party automation vendors, reverse-engineering or natively implementing this protocol is essential to controlling Gilbarco dispensers without relying on expensive proprietary distribution boxes. | Feature | Two-Wire Protocol | Modern Gilbarco

Maximizing Forecourt Efficiency: Integrating the Gilbarco Dispenser Two-Wire Protocol with Third-Party Pump Controllers

: Used by Highline-2, Euroline, Euro Dimension, Doms DP-9000, and Australian models. Data Format : 8 Data bits, Even Parity, and 1 Stop bit. Physical Layer

Optical isolation is strictly required at both the controller and the dispenser end to prevent ground loops and protect hardware from high-voltage spikes on the forecourt. Serial Configuration

The Ultimate Guide to the Gilbarco Two-Wire Protocol for Third-Party Integration Data Format : 8 Data bits, Even Parity, and 1 Stop bit

The true power of the Two-Wire Protocol lies in its ability to liberate station owners from single-vendor lock-in. The protocol is explicitly named for use by "Third-Party Pump Controllers," and a thriving ecosystem of hardware and software has grown around it.

The protocol follows a architecture. The pump controller (Master) initiates all communication by polling the dispensers (Slaves). Every unit on the loop receives the data, but only the specific unit addressed responds, while others ignore the message. Interface Requirements for Third-Party Systems

+-----------+ | IDLE | <------------------------------------+ +-----------+ | | | | (Customer lifts nozzle / Nozzle Switch) | v | +-----------+ | | REQUESTING| | +-----------+ | | | | (Controller sends AUTHORIZE command) | v | +-----------+ | | FUELING | | +-----------+ | | | | (Customer replaces nozzle / Limit reached) | v | +-----------+ | | FINISHED | -------------------------------------+ +-----------+ (Controller pulls data & clears transaction) State Sequence Details 4-20mA Comunications | Page 3 - All About Circuits Forum

The two-wire protocol returns pulses as a frequency. The new converters output these as standard quadrature encoder pulses or Modbus registers. Your third-party pump controller can now read with sub-penny accuracy. but only the addressed dispenser responds.

The controller acts as the master, initiating all communication. Every unit in the loop receives the data, but only the addressed dispenser responds. Interfacing with Third-Party Controllers

To connect a standard microcontroller or microprocessor (UART TTL/RS-232) to a Gilbarco current loop, third-party developers must use a specialized (Current Loop to Serial Converter) featuring high-speed optocouplers to isolate forecourt electrical noise from the control logic. 2. UART Serial Configuration

Historically standardized at 57600 baud , though legacy configurations may operate at 4800 or 9600 baud .

A typical command packet sent from the controller to the pump follows this architecture: