From 5620d308897249ad24dc44a93e0ad776cff37da2 Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Mon, 20 Mar 2017 13:50:06 +0000 Subject: [PATCH] Adding instructions to monitor CAN traffic. Change-Id: I80668eaccb25d8df07025aed3563bfc9d94a1271 Signed-off-by: Romain Forlot --- docs/3-Usage.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/docs/3-Usage.md b/docs/3-Usage.md index bee088e3..00dace09 100644 --- a/docs/3-Usage.md +++ b/docs/3-Usage.md @@ -157,7 +157,7 @@ NOTICE: vcan0 device opened and reading {binding low-can} NOTICE: Initialized 1/1 can bus device(s) {binding low-can} ``` -Then connect to the binding using previously installed ***AFB Websocket CLI*** tool : +On another terminal, connect to the binding using previously installed ***AFB Websocket CLI*** tool: ```bash # afb-client-demo ws://localhost:1234/api?token= @@ -232,3 +232,19 @@ ON-REPLY 2:low-can/unsubscribe: {"jtype":"afb-reply","request":{"status":"succes low-can unsubscribe { "event" : "doors*" } ON-REPLY 3:low-can/unsubscribe: {"jtype":"afb-reply","request":{"status":"success"}} ``` + +### Using CAN utils to monitor CAN activity + +You can watch CAN traffic and send custom CAN messages using can-utils preinstalled on AGL target. + +To watch watch going on a CAN bus use: + +```bash +# candump can0 +``` + +Send a custom message: + +```bash +# cansend can0 ID#DDDDAAAATTTTAAAA +``` -- 2.16.6