From 58dfea8e7562588b3dfc71e07c3c8736187e29dc Mon Sep 17 00:00:00 2001
From: Christopher Peplin <chris.peplin@rhubarbtech.com>
Date: Mon, 6 Oct 2014 23:20:36 -0400
Subject: [PATCH] Give diagnostic request field a more specific name.
Fixed #18.
---
JSON.mkd | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/JSON.mkd b/JSON.mkd
index 71546bc..43f7ea9 100644
--- a/JSON.mkd
+++ b/JSON.mkd
@@ -65,7 +65,7 @@ A diagnostic request is added or cancelled with a JSON object like this example:
{ "command": "diagnostic_request",
"action": "add",
- "request": {
+ "diagnostic_request": {
"bus": 1,
"id": 1234,
"mode": 1,
@@ -92,7 +92,7 @@ simple one-time diagnostic request:
{ "command": "diagnostic_request",
"action": "add",
- "request": {
+ "diagnostic_request": {
"bus": 1,
"id": 1234,
"mode": 1,
@@ -111,7 +111,7 @@ previous example as a recurring request at 1Hz:
{ "command": "diagnostic_request",
"action": "add",
- "request": {
+ "diagnostic_request": {
"bus": 1,
"id": 1234,
"mode": 1,
@@ -125,7 +125,7 @@ To cancel a recurring request, send a `cancel` action with the same key, e.g.:
{ "command": "diagnostic_request",
"action": "cancel",
- "request": {
+ "diagnostic_request": {
"bus": 1,
"id": 1234,
"mode": 1,
--
2.16.6