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: JSON.mkd
+55-17Lines changed: 55 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -2,21 +2,16 @@
2
2
3
3
Each JSON message published by a VI is delimited with a `\0 ` character.
4
4
5
-
## Extra Values
5
+
## Table of Contents
6
+
1.[Vehicle Messages](#vehicle-messages)
7
+
2.[CAN Message](#can-message)
8
+
3.[Diagnostic Message](#diagnostic-message)
9
+
4.[Commands](#commands)
10
+
5.[Extra Values](#extra-values)
6
11
7
-
Any of the following JSON objects may optionally include an `extras`
8
-
field. The value may be any valid JSON object or array. The client libraries
9
-
will do their best to parse this information into a generic format and pass it
10
-
to your application. For example:
12
+
## Vehicle Messages
11
13
12
-
{"name": "steering_wheel_angle",
13
-
"value": 45,
14
-
"extras": {
15
-
"calibrated": false
16
-
}
17
-
}
18
-
19
-
## Simple Vehicle Message
14
+
### Simple Vehicle Message
20
15
21
16
There may not be a 1:1 relationship between input and output signals - i.e.
22
17
engine timing CAN signals may be summarized in an "engine performance" metric on
@@ -26,7 +21,7 @@ The expected format of a single valued message is:
26
21
27
22
{"name": "steering_wheel_angle", "value": 45}
28
23
29
-
## Evented Simple Vehicle Message
24
+
###Evented Simple Vehicle Message
30
25
31
26
The expected format of an event message is:
32
27
@@ -57,7 +52,7 @@ The format for a plain CAN message:
57
52
of `standard` or `extended`. If the `id` is greater than `0x7ff`, the extended
58
53
frame format will be selected automatically.
59
54
60
-
## Diagnostic Messages
55
+
## Diagnostic Message
61
56
62
57
### Requests
63
58
@@ -377,7 +372,7 @@ the response will be `true`.
377
372
378
373
The ModemConfigurationCommand message allows users to change certain aspects of modem operation on-the-fly (at runtime). The modem configuration settings are stored in flash memory and are untouched by the bootloader during a software update (assuming the correct cellular_c5 linker file is used during compilation of vi-firmware). Thus, new modem settings persistent across power cycles.
379
374
380
-
The ModemConfigurationCommand message provides three sub-messages for particular groups of modem settings. These are NetworkOperatorSettings, NetworkDataSettings, and ServerConnectSettings. These configuration messages are described in great detail within the [c5_cellular_config](https://github.com/openxc/vi-firmware/docs/advanced/c5_cell_config.mkd) documentation.
375
+
The ModemConfigurationCommand message provides three sub-messages for particular groups of modem settings. These are NetworkOperatorSettings, NetworkDataSettings, and ServerConnectSettings. These configuration messages are described in great detail within the [c5_cellular_config](https://github.com/openxc/vi-firmware/docs/advanced/c5_cell_config.html) documentation.
381
376
382
377
Currently, only the ServerConnectSettings sub-message is supported in the vi-firmware's command interpreter. All other settings are currently compile-time only.
383
378
@@ -394,4 +389,47 @@ The ServerConnectSettings part of ModemConfigurationCommand allows the user to s
0 commit comments