Expand description
Refer to the module [uds] for all the documentation
Structs§
- Data
Record - Single response entry
- EcuReset
Response - Extended
Id - Extended 29-bit CAN Identifier (
0..=1FFF_FFFF). - Flow
Control Options - Flow control options aka
can_isotp_fc_options - IsoTp
Behaviour - IsoTp
Options - ISO-TP otions aka
can_isotp_options - Link
Layer Options - Link layer options aka
can_isotp_ll_options - NrcData
- Struct containing rejected sid and nrc for UdsError::Enc type
- Read
Data ByIdentifier Response - Response of all read_data_by_identifier methods
- Read
Memory ByAddress Response - ReportDTC
Snapshot Record ByDTC Number - Used only by 0x04
- ReportDT
CsResponse - Shared between 0x02, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x13, 0x15
- Report
Number OfDTC ByMask Response - Shared between subfunctions 0x01, 0x07, 0x11, 0x12
- Standard
Id - Standard 11-bit CAN Identifier (
0..=0x7FF). - TxFlags
- UdsClient
- Main struct providing all API calls.
- UdsSocket
- Write
Data ByIdentifier Response
Enums§
- Data
Format - 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
- Error
- Possible errors
- Id
- A CAN Identifier (standard or extended).
- Negative
Response Code - So called NRC - when server (ECU) sends negative response (SID 0x7F) it is followed by NRC byte, representing the error.
- ReadDTC
Information Response - Reset
Type - Service
Identifier - Used for defining request Service Identifiers (SIDs)
- UdsCommunication
Error - UdsError
- Containing possible errors and negative responses
- UdsResponse
- All possible services containing responses DataFormat represents wether the parsing into response struct was succesful