diff options
| author |   Christopher Peplin <chris.peplin@rhubarbtech.com> | 2014-11-07 08:57:03 -0500 |
|---|---|---|
| committer | Christopher Peplin <chris.peplin@rhubarbtech.com> | 2014-11-07 08:57:03 -0500 |
| commit | 75bc6db24e48f4b577f68a4e27cace82ff8e442c (patch) | |
| tree | 810d127b459912698cabedf0ad060b580e7e88b9 /JSON.mkd | |
| parent | b8f82bd6b22237928d16cfb5e97a9bcf30919698 (diff) | |
Back off change to CAN message ID for backwards compatibility.
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.
Diffstat (limited to 'JSON.mkd')
| -rw-r--r-- | JSON.mkd | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -39,12 +39,12 @@ discrete pieces of information in the measurement. The format for a plain CAN message: - {"bus": 1, "message_id": 1234, "data": "0x12345678"} + {"bus": 1, "id": 1234, "data": "0x12345678"} **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). -**message_id** - the CAN message ID +**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 |