| Feature | Two-Wire (New Method) | Ethernet / IFSF | Traditional DBox | | :--- | :--- | :--- | :--- | | | <20ms (Critical for presets) | 100-200ms | 500ms+ | | Cabling Cost | Low (existing twisted pair) | High (Cat6/Fiber needed) | Very High (Proprietary) | | Third-Party Support | Newly accessible via converters | Native (if dispenser supports) | Poor (license fees) | | Legacy Dispensers | Works on 20-year-old units | Requires new dispenser | Works but costly |
Third-party developers must implement commands for bringing a pump online, configuring it, polling for status, and managing fuel sale data. Modern Upgrades | Feature | Two-Wire (New Method) | Ethernet
Long two-wire runs pick up noise from 3-phase motors. Isolated current-loop repeaters (e.g., Weidmuller) or use fiber optic converters for runs > 500 ft. The Gilbarco dispenser two-wire protocol is a master-slave
The Gilbarco dispenser two-wire protocol is a master-slave protocol that uses a two-wire serial communication link between the pump controller (master) and the dispenser (slave). The protocol is based on a simple, asynchronous serial communication standard, with a single master device (pump controller) and multiple slave devices (dispensers). Major dispenser manufacturers
For decades, the fuel retail industry has operated in a state of semi-walled gardens. Major dispenser manufacturers, particularly Gilbarco Veeder-Root, developed proprietary communication protocols that made it notoriously difficult for third-party point-of-sale (POS) systems, fleet fueling managers, and automated tank gauge (ATG) integrators to communicate directly with the dispenser’s hydraulic components.
This is the foundational logical interface manual. It defines the message format, including the 11-bit data frame and multi-drop addressing for up to 16 fueling positions.