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.

1. Use OmegaJr firmware 030.001.033 or newer and connect its diagnostic USB port to the computer.
2. Select OmegaJr DiagPort. The utility forces Serial mode and lists the available COM ports.
3. Select the diagnostic COM port. Use Refresh if it was connected after the utility started.
4. Click Connect. The serial settings are fixed at 57600 baud, 8 data bits, no parity, and 1 stop bit.

The utility sends a dedicated FD2TestUtility/OmegaJr negotiation frame that cannot be produced by clicking an ordinary diagnostic-menu option. It requires the firmware's unique negotiation acknowledgment, PCC-ready response, and framed OmegaJr identity before enabling controls. No terminal work or security-code typing is required.

The same handshake runs immediately before every OmegaJr PCC command. If firmware inactivity returned the port to its default menu, the handshake safely re-enters PCC first. If the firmware state cannot be verified, the selected command is not sent and the utility closes the connection rather than retrying against an uncertain mode.

If connection fails, confirm the firmware version, choose the correct diagnostic COM port, and make sure another program does not have the port open.

Click OmegaJr Diagnostics to open the same public firmware menu shown to a normal terminal connection. The handshake does not grant diagnostic privilege. The utility turns every option in the current firmware menu into a labeled button.

Select Security code and submit the numeric response to enter privileged mode through the normal firmware menu flow. Only then do dispenser configuration, reset, log tests and maintenance, UID, and memory-dump options appear. Nested menus and predefined dispenser-brand controls also appear as buttons. Use Back / ESC to move up a menu. Closing the window resumes PCC service automatically and clears diagnostic privilege.

Commands are accepted only in their matching connection state. Buttons from an earlier screen are invalidated as soon as an option is selected, connection-management keys are withheld from the diagnostics window, and modifying actions require a second confirmation click.

Free-form terminal input is not available. The only typed field is the memory-dump address, and it accepts at most eight hexadecimal digits after being explicitly enabled.

After identity verification, the utility enables the applicable main-window actions for price writes, authorization, stop, resume, payout/sale data, totals, status, system version, and compatible custom PCC commands.

Unsupported commands are blocked locally and shown in TX/RX instead of being sent. Extended ! commands, deauthorize, license/files, reader/other-device actions, IFSF commands, and price-sign commands are unavailable in this mode.

Disconnect, changing away from OmegaJr mode, or closing the utility safely ends the diagnostic session and closes the COM port.

Enter the two-digit channel, sign line/level, PPU decimal count, and human-readable price. The dialog scales and rounds the price to an eight-digit integer, then sends:

*Hccldpppppppp

• cc: configured price-sign channel, 01-99.
• l: line or level, 1-8.
• d: decimal places, 0-5.
• pppppppp: zero-padded scaled price.

For example, channel 01, line 1, three decimals, and price 3.499 produces *H011300003499. An ACK means FD2 accepted and queued the value; the configured driver still performs its own line range, scaling, delivery, and read-back checks.

Choose Manual or Automatic and enter an intensity from 0 through 100. The command is *Iccmiii, where m is M or A and iii is the zero-padded intensity. Example: *I01M050.

Display control is currently supported by the Generic and Daktronics drivers. Other configured sign drivers reject *I with NAK.

*Jcc returns an eight-character framed status payload. The dialog decodes it into channel, communication, price delivery, dim mode, and intensity.

Use status after a set command to distinguish acceptance by FD2 from successful delivery to the physical sign.

The dialog offers the PCC-wide range of lines 1-8 and decimals 0-5. The configured driver may support a smaller line range or a fixed wire precision, so a syntactically valid command can still receive NAK. Current drivers include Bever, Daktronics, Everbrite, Generic, Novyc, Passport-compatible, PWM, Skyline, and VeriFone-compatible.

Close closes the Price Sign Test window without disconnecting the main utility.

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.