Skip to content

Describe the RMI timeout, error codes 45 and 52, and the CAN request counter - #178

Merged
michaelarnauts merged 1 commit into
masterfrom
docs-rmi-timeouts
Oct 20, 2026
Merged

michaelarnauts merged 1 commit into
masterfrom
docs-rmi-timeouts

Conversation

@michaelarnauts

Copy link
Copy Markdown
Owner
  • docs/PROTOCOL-RMI.md: error codes 45 (the node didn't answer within 1 second) and 52 (the bridge is still busy with another RMI to that node). Both are set by the bridge, not by the node.
  • docs/PROTOCOL.md: when a node doesn't answer within 1 second the bridge answers RMI_ERROR with code 45, and the bridge handles up to 4 RMI requests at the same time; more requests wait.
  • docs/PROTOCOL.md (CAN section): the field at bit 12 ("AnotherCounter") is a request counter. The bridge adds 1 (0 to 3) for every request to a node, and the response copies it.

Documentation only.

🤖 Generated with Claude Code

…equest counter

The bridge answers RMI_ERROR 45 when a node doesn't answer within 1
second and 52 when it is still busy with another RMI to that node, and
handles up to 4 RMI requests at the same time. The unknown CAN id field
at bit 12 is a request counter.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michaelarnauts
michaelarnauts merged commit 8ead6fc into master Oct 20, 2026
4 checks passed
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.

1 participant