Simba-Avionic / Simba-Avionic/Rurku-docs
Diagnostyka HW przez UDS
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Opis:
Rozszerzenie istniejącego mechanizmu UDS o weryfikację HW: co odczytywać/zapisywać/wykonywać (joby), w jakich procedurach, prototyp endpointów UDS, propozycja narzędzia CLI/GUI.
DOD:
- Tabela endpointów: DID/RID/job → HW element → cel diagnostyczny
- Mapowanie na procedury: pre-flight, post-flight, bench test, manufacturing
- Spec UDS (DIDs, RIDs, NRC, security level)
- Prototyp toola do wywoływania testów HW
- Przykładowe sesje: test spłonki, GPS lock, LoRa TX, czujnik ciśnienia, pamięć logów
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
No files, tests, or entry points are named. Start by locating the existing UDS mechanism and documenting its current endpoints and procedures, then define the DID/RID/job mappings, security behavior, and tool scope listed in the DOD. Done means the endpoint table, procedure mappings, UDS specification, prototype, and example hardware-test sessions are complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100