You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/udsoncan/questions_answers.rst
+4-10Lines changed: 4 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,8 @@ What version of the standard has been used?
6
6
7
7
.. epigraph::
8
8
9
-
The cod ewas originally written based on ISO-14229:2006. Some addition from the 2013 version has been added, but not exhaustively.
9
+
The code was originally written based on ISO-14229:2006. Some addition from the 2013 and 2020 version has been added, but not exhaustively.
10
10
11
-
Can we expect an update for the 2020 version?
12
-
---------------------------------------------
13
-
14
-
.. epigraph::
15
-
16
-
Yes, one day, when I'll put my hands on the 2020 document.
17
-
Access to ISO standard costs money and this project is 100% voluntary.
18
-
19
-
-----
20
11
21
12
How reliable is this code?
22
13
--------------------------
@@ -28,6 +19,8 @@ How reliable is this code?
28
19
29
20
Only a few common services have been tested on a real ECU.
30
21
22
+
The project lacks static type check, but it is in the plan to introduce it.
23
+
31
24
-----
32
25
33
26
Why is there unimplemented services?
@@ -39,6 +32,7 @@ Why is there unimplemented services?
39
32
40
33
- The actual synchronous client doesn't support it.
41
34
- The ratio of "service usage in the industry" over "the amount of work necessary to implement it" is too poor.
35
+
- The service has been added in the 2020 version and I haven't taken the time to implement it.
42
36
43
37
As for the client capabilities, I am aware that the single-request/single-response mechanism of the actual client is limiting. I believe it is enough to handle the majority of today's use-cases.
44
38
I may work in a future version for a more sophisticated client that will have message queues for each service with callback and everything, therefore allowing asynchronous services such as :ref:`ResponseOnEvent<ResponseOnEvent>` or :ref:`ReadDataByPeriodicIdentifier<ReadDataByPeriodicIdentifier>`
self.logger.warning('Given response code "%s" (0x%02x) is not supported byt the UDS standard version that the clients s enforcing (%s)'% (response.code_name, response.code, self.config['standard_version']))
self.logger.warning('Given response code "%s" (0x%02x) is not a supported negative response code according to UDS standard.'% (response.code_name, response.code))
Response.Code.SecurityAccessDenied, # ISO-14229:2006 Table A.1: "Besides the mandatory use of this negative response code as specified in the applicable services within ISO 14229, this negative response code can also be used for any case where security is required and is not yet granted to perform the required service."
0 commit comments