Versions Compared

Old Version 3

changes.mady.by.user Rajkumar Narayanan

Saved on

compared with

New Version Current

changes.mady.by.user Rajkumar Narayanan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Children Display

Table of Contents

Info

This Page is under Development

Introduction

 This document describes the Voice control of RPI board using Tech 4 Home remote. Voice command from remote is transferred to RPI board  via bluetooth and is processed by Voice plugin to proceed further./

Environment Setup

The build procedure is as follows:

...

  • Flashing the image

       Image is flashed to SD card before inserting to RPI board.   

    sd-card size requisite

    It is must to have minimal size of 8GB SD-Card for Firmware upgrade Voice plugin support

    Command to flash the image

        Generated image has to be flashed to an SD card using this command in local PC:

    $ sudo dd if=<path to ImageName.rpi-sdimg> of=<path to SD card space> bs=4M

...

        For testing Voice plugin , we need Tech 4 Home remote and RPI board with bluetooth support. Before using the remote, it needs to be paired and assigned to the RPI board. 

Already assigned remote needs to unassigned before assigning a new remote.


         

  • Set-up Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

  • User Access Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

  • Accessing the System

<Provide detailed information and describe the procedures necessary to access the system. If applicable, include how to get a user ID and log on to the system, as well as the actions a user must take to change and/or reset a password.>

  • System Work Flow

<Describe how system flow is happening mentioning checkpoints which can be verified during flow to ensure system is working as expected>

  • Exiting the System

<Mention the validation artifacts that are essential to ensure the functionality is working as expected. Also any limitation while closing the validation process>

Executing System

Describe the specific system function or feature in detail and depict graphically by including screen prints and descriptive narrative as appropriate. Ensure each screen print is captioned and has an associated tag providing appropriate alternative text

Follow the above for sub feature / use cases

Troubleshooting

  • Error Messages

<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>

  • Special Considerations

<If applicable, describe any special circumstances, actions, exceptions, etc., that should be considered for troubleshooting.>

Support

...

Contact

...

Organization

...

Phone

...

Email

...

Role

  • Tech 4 Home Remote

 Image Added


  • Pairing Remote with RPI

 We can pair remote using Controller UI via Bluetooth Control panel. Before we start, we have to make sure BluetoothControl and BluetoothRemoteControl plugins are enabled, if not the same can be enabled via controller UI.

Image Added

The scan is initiated from UI and once remote is detected we can pair it. 

  • On the BluetoothControl UI, click on scan button to initiate scanning and wait till scanning is completed. Devices detected are listed in the drop down column "Devices"
  • Image Added

After scan, UI list out the available bluetooth devices, select Remote based on the MAC address of the remote. After scanning if the device is not listed in drop down column, reload Controller UI once.

Image Added

  • Once the remote is detected, click on Pair button to pair it with the device. To check whether paired or not reload Controller UI once.

Image Added

  •  Once remote is paired , we can connect the remote to the device. Click on Connect  button to connect the remote.

Image Added


  •  Once remote is connected , we can assign the remote to the device. Click on Assign  button to assign the remote.

RPi - Board

  • Flash the image supported with voice plugin feature in the RPI board.
  •  Verify whether remote is paired or not using curl command. If paired confirm whether its assigned or not using curl commands. 

Eg:

curl --data-binary '{"jsonrpc": "2.0", "id": 1234567890, "method": "BluetoothRemoteControl.1.address" }' -H 'content-type:text/plain;' http://192.168.1.6/jsonrpc
{"jsonrpc":"2.0","id":1234567890,"result":"04:EE:03:78:39:DB"}root@raspberrypi-rdk-hybrid-thunder:~#

 curl --data-binary '{"jsonrpc": "2.0", "id": 1234567890, "method": "BluetoothControl.1.device@04:EE:03:78:39:DB" }' -H 'content-type:text/plain;' http://192.168.1.6/jsonrpc

{"jsonrpc":"2.0","id":1234567890,"result":{"name":"Notus S1","type":"LowEnergy","connected":true,"paired":true}}root@raspberrypi-rdk-hybrid-thunder:~#

Executing System

   Press and hold voice button in Tech 4 Home remote and give audio command, like launch CNN. 

   Release the button once audio command is completed.

   Observe the TV monitor to confirm whether CNN is launched as per request.

Troubleshooting

  • If the device is paired with RPI, folder with MAC address of device will be created under Devices directory in BluetoothControl folder. 
root@raspberrypi-rdk-hybrid-thunder:~# ls BluetoothControl/Devices/
   04:EE:03:78:39:DB.json

...

<Contact Name>

...

<Organization>

...

<Phone>

...

<Email>

...