X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;ds=sidebyside;f=README.md;h=53b7c7863173f0e6813ec61a4218b9869779d37f;hb=57d06d4880cdb31f8f8448d8a5a9089a795a57de;hp=bf6960a8ba9271a61faf2127f21db4a9618971ba;hpb=21842ae6bf4aa2c2d7ecab86abe375dd3ba5c481;p=apps%2Fagl-service-can-low-level.git diff --git a/README.md b/README.md index bf6960a8..53b7c786 100644 --- a/README.md +++ b/README.md @@ -1,30 +1,74 @@ # OpenXC Message Format Specification +Version: v0.6.0 + This specification is a part of the [OpenXC platform][OpenXC]. An OpenXC vehicle interface sends generic vehicle data over one or more output -interfaces (e.g. USB or Bluetooth) as JSON objects, separated by newlines. +interfaces (e.g. USB or Bluetooth) as JSON or Protocol Buffers (protobuf). + +## JSON + +The JSON format is the most flexible and easiest to use. The format is fully +specified in the [JSON.mkd](JSON.mkd) file in this repository. +a more flexible option than binary, but is less compact and +therefore takes more bandwidth and processing power. + +The JSON format is best for most developers, as it is fairly efficient and very +flexible. + +## Binary (Protocol Buffers) + +The binary format is encoded using [Google Protocol +Buffers](https://code.google.com/p/protobuf/). The format is specified in the +file [openxc.proto](openxc.proto). The descriptions of the messages can be foud +in the JSON specs - the binary format mirrors this. + +The binary messages are published by the VI using the standard length-delimited +method (any protobuf library should support this). -There are two valid message types - single valued and evented. +The binary format is best if you need to maximize the amount of data that can be +sent from the VI, trading off flexibility for efficiency. -There may not be a 1:1 relationship between input and output signals - i.e. raw -engine timing CAN signals may be summarized in an "engine performance" metric on -the abstract side of the interface. +## Message Pack +MessagePack is an efficient binary serialization format. It lets you exchange data +among multiple languages like JSON. But it's faster and smaller. Small integers are +encoded into a single byte, and typical short strings require only one extra byte +in addition to the strings themselves -## Single Valued +For protocol specification visit +https://github.com/msgpack/msgpack/blob/master/spec.md -The expected format of a single valued message is: +## Trace File Format - {"name": "steering_wheel_angle", "value": 45} +An OpenXC vehicle trace file is a plaintext file that contains JSON objects, +separated by newlines (which may be either `\r\n` or `\n`, depending on the +platform the trace file was recorded). -## Evented +The first line may be a metadata object, although this is optional: -The expected format of an event message is: +``` +{"metadata": { + "version": "v3.0", + "vehicle_interface_id": "7ABF", + "vehicle": { + "make": "Ford", + "model": "Mustang", + "trim": "V6 Premium", + "year": 2013 + }, + "description": "highway drive to work", + "driver_name": "TJ Giuli", + "vehicle_id": "17N1039247929" +} +``` - {"name": "button_event", "value": "up", "event": "pressed"} +The following lines are OpenXC messages with a `timestamp` field added, e.g.: -This format is good for something like a button event, where there are two -discrete pieces of information in the measurement. + {"timestamp": 1385133351.285525, "name": "steering_wheel_angle", "value": 45} + +The timestamp is in [UNIX time](http://en.wikipedia.org/wiki/Unix_time) +(i.e. seconds since the UNIX epoch, 00:00:00 UTC, 1/1/1970). ## Official Signals @@ -56,11 +100,12 @@ manufacturers may support custom message names. * 1Hz, but sent immediately on change * transmission_gear_position * states: first, second, third, fourth, fifth, sixth, seventh, eighth, - reverse, neutral + ninth, tenth, reverse, neutral * 1Hz, but sent immediately on change * gear_lever_position * states: neutral, park, reverse, drive, sport, low, first, second, third, - fourth, fifth, sixth + fourth, fifth, sixth, seventh, eighth, ninth, tenth + * 1Hz, but sent immediately on change * odometer * Numerical, km 0 to 16777214.000 km, with about .2m resolution @@ -95,26 +140,31 @@ manufacturers may support custom message names. * numerical, -179.0 to 179.0 degrees with standard GPS accuracy * 1Hz -## Raw CAN Message format - -An OpenXC vehicle interface may also output raw CAN messages. Each CAN message -is sent as a JSON object, separated by newlines. The format of each object is: - - {"bus": 1, "id": 1234, "value": "0x12345678"} +## Signals from Diagnostic Messages -**bus** - the numerical identifier of the CAN bus where this message originated, - most likely 1 or 2 (for a vehicle interface with 2 CAN controllers). +This set of signals is often retreived from OBD-II requests. The units can be +found in the [OBD-II standard](http://en.wikipedia.org/wiki/OBD-II_PIDs#Mode_01). -**id** - the CAN message ID - -**data** - up to 8 bytes of data from the CAN message's payload, represented as - a hexidecimal number in a string. Many JSON parser cannot handle 64-bit - integers, which is why we are not using a numerical data type. +* engine_load +* engine_coolant_temperature +* barometric_pressure +* commanded_throttle_position +* throttle_position +* fuel_level +* intake_air_temperature +* intake_manifold_pressure +* running_time +* fuel_pressure +* mass_airflow +* accelerator_pedal_position +* ethanol_fuel_percentage +* engine_oil_temperature +* engine_torque License ======= -Copyright (c) 2012-2013 Ford Motor Company +Copyright (c) 2012-2014 Ford Motor Company Licensed under the BSD license.