Check the command and feedback

1. Confirm the exact target bus/Unit ID/register and the supported write function in the field-device manual. A holding register is not necessarily writable.
2. Check whether the client writes raw values or engineering values. Apply type/order and inverse scaling only where required. For a linear definition, raw = (engineering value − offset) / scale.
3. Write a complete multi-register value using the device's documented method. Avoid partial updates made with unrelated single-register writes.
4. Read the documented feedback/setpoint after the acknowledgement. A command register may be write-only or may not be the correct feedback point.
5. Check required remote/automatic mode, unlock/apply steps, limits, and interlocks. Observe whether another controller or local override immediately replaces the value.
6. Restore the previous test value or release the override according to the device instructions when the test is complete.

Perform only a planned, reversible test suitable for the installation. An acknowledgement confirms a protocol response; it does not by itself confirm physical movement or a persistent configuration change.

Expected result

Feedback and equipment behavior match the intended command, or a documented interlock/override explains the difference. Provide the exact write, acknowledgement, feedback read, and operating mode if they do not.