Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Publish uavcan.node.port.List #285

Open
thirtytwobits opened this issue Feb 21, 2020 · 0 comments
Open

Publish uavcan.node.port.List #285

thirtytwobits opened this issue Feb 21, 2020 · 0 comments
Labels
class-requirement Issue that can be traced back to a design requiement domain-production Pertains to the shippable code rather than any scaffolding
Projects
libuavcan v1
Milestone
v1.0

Comments

@thirtytwobits
Copy link
Contributor

See section 5.3.4 of the specification
@thirtytwobits thirtytwobits added this to accepted in libuavcan v1 via automation Feb 21, 2020
@pavel-kirienko pavel-kirienko added the resolution-invalid The issue was closed as not an issue or something that should not be handled using GitHub issues. label Feb 21, 2020
@pavel-kirienko pavel-kirienko changed the title Implement Bus data flow monitoring Publish uavcan.node.port.List Apr 4, 2024
@pavel-kirienko pavel-kirienko added domain-production Pertains to the shippable code rather than any scaffolding class-requirement Issue that can be traced back to a design requiement and removed resolution-invalid The issue was closed as not an issue or something that should not be handled using GitHub issues. v1 labels Apr 4, 2024
@pavel-kirienko pavel-kirienko added this to the v1.0 milestone Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
class-requirement Issue that can be traced back to a design requiement domain-production Pertains to the shippable code rather than any scaffolding
Projects
libuavcan v1
  
accepted
Milestone
v1.0
Development

No branches or pull requests
2 participants
@pavel-kirienko @thirtytwobits