Gilbarco Dispenser Twowire Protocol For Third Party Pump Controllers New · Pro

Ensure the new controller has the appropriate current loop interface boards to interface physically with the Gilbarco wires.

Nozzle returned to boot, final transaction data ready for retrieval.

: Known as the "Corporate baudrate," used by Highline-111, Euroline, Euro Dimension, and A.G. Walker models. 4800 bit/sec

While the current loop is robust, it still has maximum distance limitations (typically around 1,000–3,000 feet, depending on cable quality and noise). Ensure the new controller has the appropriate current

To manage this, a is almost always required. This device sits between the third-party controller and the Gilbarco dispenser, converting the PC's standard RS-232 or USB signals into the 20mA current loop signals that the dispenser understands. Many modern interfaces feature a USB port and appear as a Virtual Serial COM Port to the host system, making them compatible with microcomputers like a Raspberry Pi for custom integration projects.

Every fueling position (side of a pump) is assigned a unique numerical address, typically ranging from 1 to 16 (or up to 32 on expanded systems).

: A USB-powered, optically isolated converter that provides a physical bridge between the dispenser and a POS. Note that this is not a protocol converter; the POS software must still implement the actual Gilbarco logic. PTS-U3 Controller : A specialized board modification from Technotrade Walker models

By utilizing a standardized two-wire interface, retailers are not locked into a single vendor's proprietary forecourt controller ecosystem. This facilitates:

1 Start Bit, 7 Data Bits, 1 Even Parity Bit, 1 Stop Bit (7E1) or 8 Data Bits, No Parity, 1 Stop Bit (8N1) depending on the specific dispenser CPU generation (e.g., Advantage vs. Encore series). The Distribution Box (D-Box) Factor

Third-party controllers must implement the logical interface to interact with the dispenser's internal software. Key functions include: Authorization This device sits between the third-party controller and

If you are currently developing or debugging a third-party pump controller interface, let me know which stage you are working on. I can provide explicit details on the , clarify the exact byte sequences for specific pump commands, or help troubleshoot hardware circuit designs for the active current loop interface.

: The protocol is not just for legacy hardware. Levtech's Fuel Management System recently announced new support for the Gilbarco Two-Wire Protocol, allowing pumps to be connected directly without complex conversions or additional interfaces, making integration faster and smoother. This shows that the protocol remains a primary target for modern, cloud-based management systems seeking to interface directly with forecourt hardware.

| 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 |

Since the protocol is proprietary, third-party pump controllers often require specialized hardware interfaces to convert the current loop signal into standard serial (RS-232/RS-485) or USB formats. 4-20mA Comunications - All About Circuits Forum

The converter then translates this into the two-wire current loop pulse train. Within 50ms, the Gilbarco dispenser activates the relay for that hose.