Confirmed Design Constraint
Expanding the commands that the “Loop Control” function sends to the regulator does not require modifying the “Processor” macro. Keep the processor unchanged and treat the command set as part of the loop-control-to-regulator interface.
Change Boundary
| Component | Required action | Evidence status |
|---|---|---|
| “Processor” macro | No modification required | Confirmed |
| “Loop Control” function | Extend the commands sent to the regulator | Confirmed change location at the functional level |
| Regulator interface | Determine how it accepts additional commands | Implementation details not provided |
Implementation and Verification
The evidence does not identify command names, parameters, software versions, or an editing procedure. Do not infer them. Use the existing project’s loop-control configuration or command-mapping mechanism, while leaving the processor macro intact.
- Identify the existing command path from “Loop Control” to the regulator.
- Add the required command through that interface without changing the processor macro.
- Verify that existing commands still operate and that the regulator receives and executes the added command.
FAQ
Must I modify the Processor macro to add regulator commands?
No. The available evidence explicitly states that expanding the command set does not require changing the processor.
Where should additional regulator commands be added?
Add them at the “Loop Control” command interface to the regulator. The evidence does not provide the exact configuration screen, block, or command identifier.
How do I verify a new loop-control command?
Confirm that the regulator receives and executes the added command, then retest the existing commands to ensure the unchanged processor path still operates correctly.