EndScan

1. Dish Leaf Node provides API for end-scan workflow. The EndScan command is a long-running command that officially terminates an active scan observation.

2. The Dish Leaf Node accepts the command if :—

   1. The dish is in one of the following operating modes:

      1. OPERATE

      2. STANDBY_FP

      3. STOW

      4. MAINTENANCE

   2. The Dish Master is online and responsive.

3. The following state requirements are applied for command execution :-

   1. The dish must be in OPERATE, STANDBY_FP, STOW, or MAINTENANCE mode.

   2. The Dish Master must remain reachable during execution.

4. No input JSON is required

   1. The EndScan command takes no arguments.

   2. No JSON parsing or schema validation is performed.

5. The command execution involves the following key operations :-

   1. Connect to Dish Master A connection to the Dish Master device is established.

   2. Invoke EndScan on Dish Master The command is sent directly to clear the scanID attribute on the Dish Master, marking the scan as complete.

   3. Result Handling

      • If accepted, Dish Master returns ResultCode.QUEUED.

      • A unique command ID is stored in command_unique_id_dict["EndScan"].

      • Final result is delivered asynchronously via the long-running command result attribute.

6. The TMC Dish Leaf Node monitors progress via long-running command results :-

   1. Command is successful when:

      • The Dish Master reports ResultCode.OK on its longRunningCommandResult attribute.

      • The scanID is successfully cleared.

      • Final status: ResultCode.OK on the TMC Dish Leaf Node.

   2. Command fails if any of the following occur:

      • Dish Master reports FAILED, REJECTED, or NOT_ALLOWED.

      • The command times out (exceeds command_timeout from Helm configuration).

      • Final status: ResultCode.FAILED with error details.

7. No input JSON schema

   1. The EndScan command requires no input.

   2. Schema URL: Not applicable