Gilbarco: Dispenser Twowire Protocol For Third Party Pump Controllers New
Technical Report: Gilbarco Two-Wire Protocol for Third-Party Pump Controllers
Date: October 26, 2023 Subject: Interface Specifications & Integration Guide for Gilbarco Dispensers Audience: System Integrators, POS Developers, Forecourt Controller Engineers
5. Message Frame Example (Third-Party to Dispenser)
Request to authorize grade 1 for $50.00:
Note: If a pump does not respond within a specific timeout window (usually 50ms–200ms), the Master marks it as "Offline" and proceeds to the next pump. Encryption: The legacy Two-Wire protocol does not support
9. Final Summary for Technical Reviewers
| Aspect | Verdict | |--------|---------| | Maturity | Very stable, decades of field use | | Ease of integration | Moderate (requires current-loop hardware, not standard serial) | | Security | Poor – no authentication, no encryption | | Future-proof | Declining, but still supported by Gilbarco for legacy | | Best for | Retrofit, fleet sites, budget-limited third-party controllers | | Worst for | New high-volume retail, EMV compliance, remote diagnostics |
Below is a proper technical review of this topic, focusing on what’s “new” or relevant for third-party integration in 2024–2026. Encryption: The legacy Two-Wire protocol does not support
The Gilbarco Two-Wire protocol is a standard communication interface used to connect Gilbarco fuel dispensers (such as the Encore 500 and SK700) to Point-of-Sale (POS) systems and third-party controllers. It utilizes a 2-wire current loop to facilitate real-time data exchange for transactions, inventory management, and diagnostics. Technical Specifications
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. Encryption: The legacy Two-Wire protocol does not support
4.2 Data Frame Format
While exact byte structures are proprietary, the general frame structure for the Two-Wire protocol typically follows this logic:
- Encryption: The legacy Two-Wire protocol does not support encryption natively. Security relies on physical isolation of the wires.
- Access Control: The third-party controller should authenticate the operator before sending
Authorizecommands. - Transaction Integrity: Always perform a "Read Back" after sending a Preset amount to ensure the pump received the correct volume/price.