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: docs/configuration.rst
+11-6
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,15 @@ Configuration
4
4
5
5
Currently the objects have the following hierarchy.
6
6
7
-
Uds -> Tp -> Device
7
+
::
8
+
9
+
Uds -> Tp -> Device
8
10
9
11
For CAN this would be
10
12
11
-
Uds -> CanTp -> CanInterface
13
+
::
14
+
15
+
Uds -> CanTp -> CanInterface
12
16
13
17
Each class has its own config file which includes parameters relevant to that scope,
14
18
however these can be passed "down the chain" from an upper level object to initialise
@@ -23,11 +27,12 @@ E.g.
23
27
Keyword Arguments
24
28
-----------------
25
29
To configure a UDS connection instance the kwargs are passed down to each called object down the chain. The configuration can be passed down either by a config file, or by manually typing the keyword into the function call. The precidence is as follows:
26
-
Default Config
27
-
Config File
28
-
Keyword argument
29
30
30
-
The following sections detail the different keywords for each class
31
+
- Default Config
32
+
- Config File
33
+
- Keyword argument
34
+
35
+
The following sections detail the different keywords for each class.
0 commit comments