aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2015-10-29and commit files for 0.5Eric Marsman3-4/+6
2015-10-29bump to 0.5 for releaseEric Marsman1-0/+1
2015-09-15Merge pull request #23 from mgiannikouris/crosschasm-c5Eric8-4805/+5874
added uptime field to VehicleMessage - new support for CrossChasm C5 BT & Cell devices
2015-09-15link to web server projectEric Marsman1-1/+1
2015-09-14abs link jsonmgiannikouris1-1/+1
2015-09-14jsonmgiannikouris1-1/+1
2015-09-14More JSON.mkdmgiannikouris1-2/+2
2015-09-14More JSON.mkdmgiannikouris1-1/+1
2015-09-14All caps makes it look like I'm yelling...mgiannikouris1-1/+1
2015-09-14Updated JSON.mkdmgiannikouris1-0/+22
Added details on the "modem_configuration" command.
2014-12-01added uptime field to VehicleMessagemgiannikouris7-4804/+5851
2014-11-15Bump to next development release.Christopher Peplin2-1/+3
2014-11-15Bump to v0.4 for release.Christopher Peplin2-2/+2
2014-11-15Merge branch 'next'Christopher Peplin11-1441/+5559
2014-11-07Back off change to CAN message ID for backwards compatibility.Christopher Peplin8-573/+539
I don't think this change is worth breaking compatibility with exiting trace files. The meaning of an ID is much more clean when inside a CAN message object, so that's why I think it make sense to be different than the "id" inside a diagnostic request.
2014-11-06Update changelog.Christopher Peplin1-3/+20
2014-10-28Specify the response when no device ID is known.Christopher Peplin1-0/+2
2014-10-14Update protobuf options to use new field names.Christopher Peplin3-12/+19
2014-10-06Remove redundant 'type' field from binary SimpleVehicleMessage.Christopher Peplin6-415/+131
You can figure out the type based on the value and event DynamicFields. Fixed #19.
2014-10-06Use more specific 'message_id' in JSON, not just 'id'.Christopher Peplin1-12/+12
There often isn't enough context to know if it's the message ID or a transaction ID or something else. Fixed #20.
2014-10-06Give diagnostic request field a more specific name.Christopher Peplin1-4/+4
Fixed #18.
2014-10-06Mention 'status' field in all command response JSON examples.Christopher Peplin1-3/+23
Fixed #13.
2014-10-06Deprecate "translated" and "raw" names in binary format.Christopher Peplin6-586/+578
Fixed #16.
2014-10-06Merge remote-tracking branch 'origin/16-new-names' into nextChristopher Peplin1-6/+6
Conflicts: README.md
2014-10-06Give frame format field a more specific name.Christopher Peplin6-140/+140
2014-10-06Add a field to CAN messages to explicitly set the frame format.Christopher Peplin7-102/+329
See openxc/vi-firmware:230.
2014-10-06Move JSON spec to a separate file to keep the length down.Christopher Peplin2-356/+364
2014-09-29Add a command to enable/disable pre-defined OBD-II requests.Christopher Peplin7-94/+805
See openxc/vi-firmware#303.
2014-09-27Standardize names for payload format.Christopher Peplin7-305/+304
2014-09-27Remove unnecessary 'bus' field from message format command.Christopher Peplin7-185/+89
2014-09-27Return response to set message format command in original format.Christopher Peplin1-1/+2
2014-09-27Add a command to change message format while running.Christopher Peplin7-85/+1021
2014-09-27Update compiled files.Christopher Peplin2-2/+2
2014-09-27Add a control command to control AF bypass status.Christopher Peplin7-83/+892
See openxc/vi-firmware#301.
2014-09-21Add missing comma in example.Christopher Peplin1-1/+1
2014-09-21Deprecate "translated" and "raw" verbiage.Christopher Peplin1-5/+5
Partway towards #16 but need to updated the binary format, too.
2014-09-20Simplify passthrough command to just a boolean.Christopher Peplin7-260/+108
2014-09-20Merge remote-tracking branch 'origin/latest-nanopb' into passthrough-commandChristopher Peplin3-70/+106
Conflicts: gen/cpp/openxc.pb.c gen/cpp/openxc.pb.h
2014-09-20Add passthrough command and refactor commands in binary format.Christopher Peplin7-267/+1803
The ControlCommand is now more like a VehicleMessage - it has a 'type' and many optional fields pointing to the various types. If the type is diagnostic, the client should look at the diagnostic_request field.
2014-09-16Re-build with nanopb v0.3.1.Christopher Peplin3-66/+98
2014-09-05Move a TODO to issue #14.Christopher Peplin1-3/+0
2014-09-04Note that 0x prefix on hex strings is optional.Christopher Peplin1-3/+5
2014-08-11Move action field to ControlCommand in binary format.Christopher Peplin6-276/+275
2014-08-10Add a 'status' field to command responses.Christopher Peplin6-54/+148
2014-08-10Remove 'update' feature of diag request commands.Christopher Peplin7-100/+65
2014-08-04Require an 'action' in diagnostic requests.Christopher Peplin7-75/+372
It wasn't very clean to try and infer a delete/create/update based on the value of the frequency field - this will require a little more code, but as they say in Python, explicit is better than implicit. Fixed https://github.com/openxc/openxc-message-format/issues/12
2014-08-04Explain when to use JSON vs. binary.Christopher Peplin1-3/+10
2014-08-04Expand diagnostic mode field to a full byte's range.Christopher Peplin2-2/+3
Fixed #10.
2014-06-25Add 'extras' field to JSON messages for custom data.Christopher Peplin2-1/+15
2014-06-25Make the protobuf format more clear in README.Christopher Peplin2-14/+18