Skip to content

Update web with controller parameters - #11

Merged
fmrico merged 1 commit into
mainfrom
safety_works_1
Oct 2, 2026
Merged

fmrico merged 1 commit into
mainfrom
safety_works_1

Conversation

@fmrico

@fmrico fmrico commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Hi

Update of the controller parameters

Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
Copilot AI balanced review requested due to automatic review settings October 2, 2026 16:57
@fmrico
fmrico merged commit b687f9d into main Oct 2, 2026
@fmrico
fmrico deleted the safety_works_1 branch October 2, 2026 16:57

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Two descriptions inaccurately characterize timeout frequency comparison and idle-command diagnostics.

Review effort: Balanced
Findings: 2 Low severity

Open (2)
What changed in this PR

Documents new controller velocity safety, timeout, keepalive, diagnostics, and fault-injection behavior.

Changes:

  • Explains stale-command handling and keepalive parameters.
  • Requires timestamps on controller commands.
  • Documents recovery integration through velocity diagnostics.
File Description
developer_guide/​recovery.rst Describes controller diagnostics consumed by recovery.
developer_guide/​design.rst Documents velocity robustness and parameters.
developer_guide/​blackboard.rst Updates the controller example with timestamps.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +364 to +366
writing the same one. It must be longer than the controller's period (``<controller>.rt_freq``),
or configuring fails. A controller plugin must therefore stamp each new command
(``header.stamp``).
Comment on lines +256 to +258
Besides its own evaluators, it sees the diagnostics other components write to NavState's
``diagnostics`` group, e.g. ``ControllerNode``'s ``diagnostics.cmd_vel`` when no new velocity command
arrives or one is discarded (``hardware_id: controller_node``, see :ref:`velocity_output`).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants