The D-Box has been the central connection point in Gilbarco's forecourt communication architecture for decades. Its standard function is to provide a physical interface between a controller or console and up to 16 fueling positions via the Two-Wire Interface (TWI). The D-Box also contains automatic isolation circuitry to prevent a failure on one fueling position from affecting the entire forecourt.
During and after fueling, the controller requests the current transaction data. The dispenser returns highly formatted strings containing: Accumulated cost.
✅ :
Gilbarco's PCN5 Board is designed to enable remote dispenser management, allowing retailers to perform remote software updates and configuration changes via a cloud-based hub.
When developing a new Pump Controller, the following workflow is recommended: The D-Box has been the central connection point
. It is primarily designed to facilitate data exchange between fuel dispensers and control systems (like POS terminals or forecourt controllers) over a single pair of wires. Physical Layer Specifications
Breakdown: Start (*), Address (04), Preset (P), 2000 (cents), Stop (L).
: Only the master console can initiate communication, preventing data collisions.
When a third-party controller detects an "Authorize Request", it evaluates the authorization source (e.g., an indoor POS, an outdoor payment terminal, or a mobile app fleet authorization). If approved, the controller sends an Authorization frame containing: During and after fueling, the controller requests the
To integrate a third-party controller, the system must handle both the physical signal conversion and the software logic:
Active/Passive Current Loop (typically 45mA or 20mA systems). Logical State Representation: Mark (Logic 1): Current flowing (Loop closed). Space (Logic 0): No current flowing (Loop open).
Ensure the polling engine can seamlessly manage a fully loaded loop of 16 simultaneous fueling positions without dropping packets. To help optimize your implementation, please let me know:
The protocol enables instantaneous authorization and reporting of transaction data. Common Challenges and Troubleshooting When developing a new Pump Controller, the following
Despite being 30+ years old, the two-wire protocol remains relevant because:
The controller constantly sends a status request to each address. The dispenser replies with its current state byte: Nozzle hung up, ready for transaction.
| Component | Description | | :--- | :--- | | | Signals the start of a transmission (often 0x00 or a specific hex code). | | Address Byte | Identifies the Pump ID (Side A or Side B). | | Command Byte | The instruction code (e.g., Authorize , Reset , Query Volume ). | | Data Block | Payload (e.g., Volume totals, Price per gallon). | | CRC/Checksum | Error checking byte to ensure data integrity. |
The open nature of the Two-Wire Protocol has fueled a diverse ecosystem of third-party solutions.