In the role of a diagnostic tester sequence author I want to generate my simulator files from existing CAN-traces such that I don't have to start from scratch when developing my simulations.
Acceptance Criteria:
Protocol UDS on ISO-TP is supported
The generator creates a skeleton that is tidy and readable and can be extended and changed by the author
The generated simulator file(s) can be used directly (no need for manual changes)
-> This does not mean that the recorded sequence must run correct out of the box
If the same request leads to different responses, this is reflected in the simulator
The generator decides according to the parameters of an UDS-service how much flexibility is needed and prepares the skeleton accordingly
-> e.g. a "transfer data" request always has a dynamic payload as a parameter, a "routine control" for a specific "routine identifier" has well defined sub-functions, and probably quite dynamic routine control options
Stories:
6 Generate static simulator file from CAN-Trace
7 Generate simulator from CAN-Trace with changing responses
In the role of a diagnostic tester sequence author I want to generate my simulator files from existing CAN-traces such that I don't have to start from scratch when developing my simulations.
Acceptance Criteria:
Stories:
6 Generate static simulator file from CAN-Trace
7 Generate simulator from CAN-Trace with changing responses
8 Generate simulator with timing from CAN-Trace