ht9045-autostart-flow

The GTK Loader sends Ready with MO, Flow, and Ticket data to the Agent after loading the test program, retrying up to 3 times at 3-second intervals. The Agent then sends End Lot, Start Lot, and Auto Start commands to the HT9045 Handler in sequence.

START_REQUEST triggers Auto Start by calling fMain->Start(), but only when the machine status shows HALT and SystemStart is false. The spec code HTSET 333 maps to this OLP command, though final codes require vendor confirmation.

PAUSE_REQUEST sets bLockByServer=true and SoftStop=true to lock the machine, while RESUME_REQUEST clears bLockByServer to unlock it. When locked, the Handler refuses to enter Run state even if START_REQUEST arrives.

Packets use ASCII framing with STX (0x02) at start, SOH (0x01) as field separator, and ETX (0x03) at end. The structure is STX + Command + SOH + field count + data fields + ETX, for example STX + START_REQUEST + SOH + 0 + ETX.

ONECYCLE_REQUEST is wrapped in the DEBUG_DUTONOFF preprocessor condition, so release builds exclude it entirely. Enabling One Cycle mode requires the vendor to provide a build with DEBUG_DUTONOFF enabled or an alternative command.

The Agent compares the MO, Flow, and Ticket values from the Start Lot Ack against the values stored during Handshake. If any field differs or the Ack status is Fail, the Agent aborts the flow and displays Expected versus Actual values.