Description
As a user, I would like to have an option to create translator by providing data specific for my ECU only, so I do not have to create services translators on my own.
As a user, I would like to have documentation how to create configurable translator, so I do not have to analyze the code.
Acceptance Criteria
- factory for
Translator class created
- enum with UDS version defined, user can choose which version to use as a base
- user can provide following parameters:
- whole services (replace default definitions if provided) - shall be used when message format changes
- mapping for each subfunctions (update default mappings with provided values) - shall be used when default message format is unchanged
- DID's mappings
- DID value -> DID name
- DID value -> DID structure
- RID's mappings
- RID value -> RID name
- RID value -> RID structure
Description
As a user, I would like to have an option to create translator by providing data specific for my ECU only, so I do not have to create services translators on my own.
As a user, I would like to have documentation how to create configurable translator, so I do not have to analyze the code.
Acceptance Criteria
Translatorclass created