-If you're just requesting a PID, you can use this minimal field set for the
-`request` object:
-
- {"bus": 1, "id": 1234, "mode": 1, "pid": 5}
-
-### Responses
-
- {"bus": 1,
- "id": 1234,
- "mode": 1,
- "pid": 5,
- "success": true,
- "negative_response_code": 17,
- "payload": "0x1234",
- "parsed_payload": 4660}
-
-**bus** - the numerical identifier of the CAN bus where this response was
- received.
-
-**id** - the CAN arbitration ID for this response.
-
-**mode** - the OBD-II mode of the original diagnostic request.
-
-**pid** - (optional) the PID for the request, if applicable.
-
-**success** - true if the response received was a positive response. If this
- field is false, the remote node returned an error and the
- `negative_response_code` field should be populated.
-
-**negative_response_code** - (optional) If requested node returned an error,
- `success` will be `false` and this field will contain the negative response
- code (NRC).
-
-Finally, the `payload` and `value` fields are mutually exclusive:
-
-**payload** - (optional) up to 7 bytes of data returned in the response,
- represented as a hexadecimal number in a string. Many JSON parser cannot
- handle 64-bit integers, which is why we are not using a numerical data type.
-
-**value** - (optional) if the response had a payload, this may be the
- payload interpreted as an integer and transformed with a factor and offset
- provided with the request.
-
-The response to a simple PID request would look like this:
-
- {"bus": 1, "id": 1234, "mode": 1, "pid": 5, "payload": "0x2"}
-
-TODO again, it'd be nice to have the OBD-II PIDs built in, with the proper
-conversion functions so the response here included the actual transformed value
-of the pid and a human readable name