Feature request - IM5
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 599
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
Description of IM5 taken from a Profibus document:
IM5 is mandatory if the PROFINET device contains a separate communication module with its own hardware/firmware. The IM5 data provides information about the communication module of a field device, comparable to an electronic nameplate.
A differentiation can thus be made between the HW/FW versions of the communication module and the actual device. The actual device reports its HW/FW versions via IM0.
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
The issue names no file, test, or entry point. Start by locating where PROFINET identification data, including IM0, is defined and consult the referenced Profibus document for IM5 requirements. Before implementation, clarify the expected data source, API or wire representation, and acceptance tests; done should mean IM5 is correctly reported for devices with a separate communication module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100