RemoteActuatorActivity Class

Detailed Description

The remote window registers one RemoteActuatorActivity with its activity loader and configures it with the Remote node and the shared ControlPlanningHeader. A push, or a resume after the current agent changed, binds the activity to that agent: it takes the agent client's ActuatorCourier and AgentStateCourier and scopes the courier to the fixed diagnostic stanza id, so each control writes one actuator directly.

The actuator count comes from the agent's hardware.controller sync section. If the count is not there yet, the activity waits for the section to change and builds its controls then.