Migration to binding v3

[apps/agl-service-can-low-level.git] / docs / 3-Usage.md

diff --git a/docs/3-Usage.md b/docs/3-Usage.md
index 317e072..4c0f820 100644 (file)
--- a/docs/3-Usage.md
+++ b/docs/3-Usage.md
@@ -99,7 +99,7 @@ The binding reads system configuration file _/etc/dev-mapping.conf_ at start to
 map logical name from signals described in JSON file to linux devices name
 initialized by the system.
 
 map logical name from signals described in JSON file to linux devices name
 initialized by the system.
 

-Edit file _/etc/dev-mappping.conf_ and add mapping in section `CANbus-mapping`.
+Edit file _/etc/dev-mapping.conf_ and add mapping in section `CANbus-mapping`.

 
 Default binding configuration use a CAN bus named `hs` so you need to map it to
 the real one, here are some examples:
 
 Default binding configuration use a CAN bus named `hs` so you need to map it to
 the real one, here are some examples:


@@ -311,11 +311,11 @@ Examples:
 low-can write { "bus_name": "hs", "frame": { "can_id": 1568, "can_dlc":
 8, "can_data": [ 255,255,255,255,255,255,255,255]} }
 # Write a signal's value.
 low-can write { "bus_name": "hs", "frame": { "can_id": 1568, "can_dlc":
 8, "can_data": [ 255,255,255,255,255,255,255,255]} }
 # Write a signal's value.

-low-can write { "signal_name": "engine.speed", "value": 1256}
+low-can write { "signal_name": "engine.speed", "signal_value": 1256}

 ```
 
 To be able to use write capability, you need to add the permission
 ```
 
 To be able to use write capability, you need to add the permission

- ```urn:AGL:permission:low-can:platform:write``` to your package configuration
+ ```urn:AGL:permission::platform:can:write``` to your package configuration

  file that need to write on CAN bus through **low-can** api.
 
 Then in order to write on bus, your app needs to call verb **auth**
  file that need to write on CAN bus through **low-can** api.
 
 Then in order to write on bus, your app needs to call verb **auth**