Daily operation

Start and inspect

Use System Console Overview/HRSDK to start the configured SDK service. For shell operation use the configured operator account and either the installed systemd service or CLI, keeping one lifecycle owner:

systemctl status hrsdk.service --no-pager
hr version

Starting through systemd runs the packaged hr start under the selected operator. Starting a separate Compose project manually can create competing processes or port/device conflicts. Check the current owner before starting another instance.

Confirm API health, adapter connection, selected robot configuration, expected services and provider/device readiness. A green host service indicator does not prove the camera, speech provider or torque state.

Operate through Robot WebUI

Use TeleOps for chat, exact speech, behavior, expressions, gestures, targeting and compact performance playback. Use Motors for deliberate individual control and torque, Performances for editing/execution, Faces for enrollment/recognition, Settings for runtime configuration and Visualization for Unity. UI walkthrough.

Start with read-only state/catalog inspection. Confirm the intended robot before issuing state-changing commands. Speech/chat, runtime setting updates and physical motion have different effects. Runtime command acknowledgement is not proof of hardware completion.

Stop and restart

Use console service controls or the matching lifecycle command. A normal CLI stop preserves named volumes; hr stop --volumes removes them and is not routine operation. Restarting can rebuild runtime state from source/saved settings and interrupt sessions/performances.

The WebUI command.stop result is unsupported in the current adapter. A performance Stop affects that runtime; arm Stop affects its player. Neither is documented as a whole-robot emergency stop. Follow the robot's physical safety procedure when required.

Logs and incident capture

journalctl -u hrsdk.service -n 150 --no-pager
journalctl -u hr-system-console.service -n 150 --no-pager
docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'
df -h

Capture timestamps, selected release, component versions/commits, robot identity, task IDs, affected endpoint and actual response/error. Container names depend on Compose project; discover them before requesting logs. Redact credentials and personal recordings from support bundles.

The console Logs page requires selecting a service and refreshing; it is not a continuous full log stream. Cached metrics may carry stale/error metadata, so include that state when diagnosing.

Routine pre-session checks

Inspect disk capacity, host load/temperature, network route/DDS status, audio input/output, USB/serial devices, perception state and provider credentials. Test one intended interaction at a controlled scope before a public demonstration. Verify Unity and browser microphone permissions in the operator's actual browser.

Evidence: packaged hrsdk.service, console and WebUI frontend/backend, CLI stop/start implementation and current launch/configuration.