Expand description
Refer to the module [uds] for all the documentation
Structs
- Single response entry
- Extended 29-bit CAN Identifier (
0..=1FFF_FFFF
). - Flow control options aka
can_isotp_fc_options
- ISO-TP otions aka
can_isotp_options
- Link layer options aka
can_isotp_ll_options
- Struct containing rejected sid and nrc for UdsError::Enc type
- Response of all read_data_by_identifier methods
- Used only by 0x04
- Shared between 0x02, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x13, 0x15
- Shared between subfunctions 0x01, 0x07, 0x11, 0x12
- Standard 11-bit CAN Identifier (
0..=0x7FF
). - Main struct providing all API calls.
Enums
- If program was able to parse received data, the response struct will be stored in Parsed. If parsing was not successful, the Raw will contain all received data, without first byte (SID) which is encoded in UdsResponse Enum
- Possible errors
- A CAN Identifier (standard or extended).
- So called NRC - when server (ECU) sends negative response (SID 0x7F) it is followed by NRC byte, representing the error.
- Used for defining request Service Identifiers (SIDs)
- Containing possible errors and negative responses
- All possible services containing responses DataFormat represents wether the parsing into response struct was succesful