FD2 Test Utility

Choose the protocol FD2 expects. For most dispenser testing, use PCC. Use FD Socket only when testing the FD socket text interface.

When in doubt, start with PCC. The main price and authorization examples are PCC-shaped.

• Ethernet: enter the controller IP and TCP port.
• Serial: enter the COM port and serial settings.

For Ethernet, enter the FD2/controller IP and port. The common test port is 9200.

For Serial, enter the COM port and matching baud/parity/data/stop settings.

After a successful connection, the utility shows CONNECTED. If it does not, check protocol, address, port, cabling, and whether FD2 is listening.

Set Price, Amount, and Volume decimals to match the controller or dispenser setup. Common values are price 3, amount 2, and volume 3.

Pick the dispenser number, such as 01 or 02. The Selected: XX label confirms the active target.

Choose Selected Hose in the price bar.

Click Send Price. The utility builds the command from the selected protocol, dispenser, hose, and decimal settings.

Click Custom Price when you need to enter specific credit and cash prices instead of using the utility's generated test prices. The dialog validates the values before sending.

Click All Hoses to send prices for the hose range up to the selected hose.

If FD2 NAKs the command, check that the hose exists and that the price decimal format matches the controller setup.

Click Remove/Disable to send the utility's price-clear style command for the selected hose.

Click Authorize. The dialog opens with the current dispenser already selected.

• Dollar preset: enter a money amount.
• Volume preset: enter a volume amount.
• Fillup: authorize without a normal preset limit.

Select Credit (1) or Cash (2). The utility uses that choice when building the PCC authorization flag.

Use Hose to allow one hose. Use Multi to allow a selected group of hoses. Leave it on None for no hose lock.

Click OK. The utility sends the command and updates the TX/RX panel. While the command is in progress, the Authorize button is disabled to prevent duplicate sends.

A dollar preset in PCC normally builds an A command with a money flag and a scaled money value.

When Fillup is selected, choose the fillup type that matches the test:

• Legacy (4): legacy fillup authorization.
• Cash (5): cash fillup authorization.
• Credit (6): credit fillup authorization.

Shows the command payload sent by the utility. For PCC, the utility frames it internally, but this box shows the command in a readable form.

Shows the controller response with control bytes expanded:

• ACK means FD2 accepted the command.
• NAK means FD2 rejected the command.
• STX and ETX mark framed PCC payload boundaries.

[no response] means the utility did not receive data before the receive timeout. Check the connection, command format, and whether the remote side closed the socket.

The utility serializes command sends through the shared transport so two commands do not write/read over the same socket at the same time. Reconnects close the previous socket before opening a new one.

Click Read Files.

Choose where downloaded files should be saved. If no folder is selected, the utility may prompt later.

• Read config.xml (*CR): request controller configuration.
• Logs dir (*VL): request logs.
• JSON dir (*VJ): request JSON files.
• DB dir (*VD): request database files.
• Reader dir (*VR): request reader files.
• License dir (*VC): request license files.
• PIE data dir (*VP): request PIE data files.

The window shows the response, and Copy to main TX/RX can copy the result into the main panel.

Clear empties the response box in the Read Files window. Close closes the window without changing the main connection.

Select a message template and click Apply, or type a command manually.

• A010000100000000 - PCC-style authorization example.
• *VL - log-file request example.

Use Show raw when you need visible control bytes. Use Copy to main TX/RX when you want the main window to show the same exchange.

Click Send and read the response before sending another command.

Close closes the Custom Command window. It does not disconnect the main utility.