}
}
-## Single Valued
+## Simple Vehicle Message
-There may not be a 1:1 relationship between input and output signals - i.e. raw
+There may not be a 1:1 relationship between input and output signals - i.e.
engine timing CAN signals may be summarized in an "engine performance" metric on
the abstract side of the interface.
{"name": "steering_wheel_angle", "value": 45}
-## Evented
+## Evented Simple Vehicle Message
The expected format of an event message is:
This format is good for something like a button event, where there are two
discrete pieces of information in the measurement.
-## Raw CAN Message format
+## CAN Message
-The format for a raw CAN message:
+The format for a plain CAN message:
{"bus": 1, "id": 1234, "data": "0x12345678"}
complete string must have an even number of characters. The `0x` prefix is
optional.
+**format** - (optional) explicitly set the frame format for the CAN message, one
+ of `standard` or `extended`. If the `id` is greater than `0x7ff`, the extended
+ frame format will be selected automatically.
+
## Diagnostic Messages
### Requests
**name** - (optional, defaults to nothing) A human readable, string name for
this request. If provided, the response will have a `name` field (much like a
- normal translated message) with this value in place of `bus`, `id`, `mode` and
+ simple vehicle message) with this value in place of `bus`, `id`, `mode` and
`pid`.
**multiple_responses** - (optional, false by default) if true, request will stay