mipidisaster / mipidisaster/miLibrary
ROS fault publishers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Each of the ROS nodes currently created all have a way to detecting faults with the hardware/external device.
Currently this is only used minimally, should update this such that the fault flag is provided as output of the node(s) as well.
Envision that the fault code value will be provided, and within the usual std_msgs/header 'Frame_Id' capture what the code means - based upon the enumerate text (if this can be easily retrieved)
- Update 'MCP_CAN' repository as well
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the ROS nodes' existing hardware or external-device fault detection and the related MCP_CAN repository. Determine how fault codes and their enumerate text are represented; done means the relevant node outputs the fault code and exposes its meaning through the standard message header, with MCP_CAN updated as needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100