Gilbarco Dispenser Twowire Protocol For Third | Party Pump Controllers New

The Gilbarco Two-Wire protocol is a proprietary communication standard used to interface fuel dispensers with control consoles or point-of-sale (POS) systems. For third-party developers, mastering this protocol requires understanding its physical current-loop layer, the specific baud rates associated with different dispenser models, and the logical "master-slave" polling structure. 1. Physical Layer: The Current Loop

Part 1: The Anatomy of the Two-Wire Protocol

To understand the "new," you must first understand the "old." The Gilbarco two-wire system (often referred to as the G-Site or Bi-directional asynchronous protocol) is a serial communication standard that runs over a simple, unshielded twisted pair of copper wires. Header : A single byte that indicates the

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. Practical next steps (for integration)

Whether you are a fleet operator wanting to bypass expensive POS licensing, a C-store owner integrating loyalty rewards directly into the nozzle, or a hobbyist reviving a classic dispenser, the two-wire protocol is your golden ticket. fuel authorization code

: Communication is achieved via a 20mA or 45mA current loop. Third-party controllers usually require a hardware interface or "D-Box" (Distribution Box) to convert standard serial signals (RS-232 or RS-485) into the specific current loop required by the dispenser. Data Parameters : Typical settings vary by dispenser model: Legacy (Highline-2, Euroline) : 4800 baud, 8 data bits, Even parity, 1 stop bit. Modern (Encore, SK700) : Often referred to as "Corporate baudrate" at , 8 data bits, Even parity, 1 stop bit. Data Format

Gilbarco Dispenser Two-Wire Protocol for Third-Party Pump Controllers

1. Header: A single byte that indicates the start of a message ( typically 0x55).
2. Address: A single byte that specifies the dispenser address (0-15).
3. Command: A single byte that specifies the command or request from the pump controller (e.g., authorize fueling, report fuel level).
4. Data: A variable-length field that contains data related to the command (e.g., fuel authorization code, fuel level).
5. Checksum: A single byte that contains the checksum of the message.

Practical next steps (for integration)

1. Obtain the specific Gilbarco dispenser model’s TwoWire protocol spec or SDK (model‑specific opcodes and addressing).
2. Implement a strict state machine with CRC, ACK/NAK, and timeout/retry.
3. Build safety fallbacks: automatic disable on comms failure, meter reconciliation.
4. Create test harness: emulator to inject events (nozzle lift, stuck, sensor errors).
5. Validate with hardware and run compliance/regulatory checks.