Bluetooth Indoor Solar Development Kit (LES100) Operation Guide

Transcription

1 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 1 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Introduction Fully powered by indoor solar energy, the LES100 collects data from a variety of sensors and sends it to the cloud via Bluetooth Low Energy (BLE). This development kit is meant to be the first building block of any IOT sensing project or idea. The design makes it simple to add solar to any Bluetooth sensing application. PowerFilm's Indoor Solar Panels power the LES100 from indoor light sources, enabling completely self-sufficient IoT devices. The LES100 comes configured to measure temperature, light level, and battery level and includes a pin header to easily connect any additional external sensors. This operation guide is a technical reference for all components and software related to the LES100 and the LES100 Data Monitor including setup and development instructions. Figure 1, Product picture.

2 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 2 Table of Contents Introduction... 1 Use Cases... 4 Remote Sensing Applications... 4 Included in Kit... 4 System Overview... 4 Technical Specifications... 5 IC... 5 Solar... 5 Software... 5 Electrical... 5 Quick Setup Instructions... 6 Equipment... 6 Setup... 6 LES100 Data Monitor Notes... 9 Home Page... 9 Device Page... 9 Battery Profile Temperature Profile Light Level Profile Connection Control Service Saving Settings Code Composer Studio Additional Equipment Installation Setup Build and Download/Debug Single Step Flash Programming Overview of CC2650 Code Structure Adding a Custom Service or Profile Profile Setup External Sensor/Device Setup Initialization Android Studio... 31

3 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 3 Installation Setup Build and Run/Debug LES100 Data Monitor Overview of Android Code Structure Structure MainActivity.java DeviceActivity.java Bluetooth Profiles and Rows Layouts Other Adding a Customized Service or Profile SensorTagGatt.java modification gatt_uuid.xml modification Creating a Custom Bluetooth Profile Class DeviceActivity.java modification Custom Profile Row Block Diagram Diagram Block Diagram Notes BQ25570 Energy Harvester CC2650 Wireless MCU LES100 Data Monitor Schematic Overview BQ25570 Energy Harvester [final doc will have separate page for schematic] Bluetooth and Sensing MCU [final doc will have separate page for schematic] I/O Ports and Connectors Switches Layout Top Bottom LES100 Application Notes Power Consumption Optimization... 50

4 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 4 Hardware Configurations I/O Access Charge Control Configuration Capacitor/Super Capacitor Storage Element Operation Theory of Operation Specifications CC2650 Microcontroller Reset Use Cases Sensing Applications Temperature Humidity Pressure Light Level Vibration Motion Acoustic Air Flow Water Flow Strain Moisture Air Quality Occupancy Acceleration Water Level IoT Applications Home Automation Wearables Smart Buildings Smart City Smart Agriculture Wireless Nodes Asset Tracking Smart Transportation Gateways Beacons Equipment Monitoring Industrial Automation Included in Kit LES100 Board: fully assembled (battery and solar not connected) Solar Panel: LL Amorphous Silicon. Battery: 3.7V nominal Lithium Ion Polymer, 40mAh, circuit protection System Overview The LES100 dev board system extends the TI CC2650 SensorTag Bluetooth and data collection by integrating energy harvesting and an indoor solar panel. It is capable of operating at extremely low light levels, down to 200 lux and below.

5 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 5 LES100 is designed to be fully customizable. DevPack and JTAG connectors are present for debugging and adding TI DevPack plug-in modules. All IO pins can be accessed via a 10-pin female header so that external sensor can easily be added. The current onboard sensors can be disconnected by removing SMD jumpers to allow access to all 10 IO pins. Software development can be done using Code Composer Studio and Android Studio, which are both free to use. Hardware modifications can be done using EAGLE CAD software. The CC2650 device is a wireless MCU targeting Bluetooth, ZigBee and 6LoWPAN, and ZigBee RF4CE remote control applications. The protocol provided with the development kit is for Bluetooth LE, however other protocols could be loaded as well. Technical Specifications IC Solar CC2650 Simplelink Multi-Standard Wireless MCU. BQ25570 Nano Power Boost Charger and Buck Converter for Energy Harvester Powered Applications. OPT3001 Digital Ambient Light Sensor. LL Two Cell Tandem Amorphous Silicon lux. Thickness: 10mil Bend Radius: 2cm Software and Compatible IDEs Android Studio. Code Composer Studio v TI BLE Bluetooth Low Energy Stack. Electrical Pre-configured for li-ion battery charging. <10uA system sleep current. Operational down to 200 lux. 10mA peak transmission current (typical). See CC2650 Datasheet. See BQ25570 Datasheet.

6 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 6 Quick Setup Instructions The following instructions will outline how to set up the LES100 to connect and send data to the LES100 Data Monitor application using the preloaded programs and configuration. Equipment LES100 Development board. LL Indoor Solar Panel. Lithium Ion battery (4.2V Max) or compatible capacitor/supercapacitor. Android Device with Bluetooth Low Energy capability. Small flathead Screwdriver. Setup Refer to Figure 2 to help find noted location on assembled circuit board. References to LES100 Data Monitor Figures 4,5, and 6 are located in the section LES100 Data Monitor Notes. 1. Open all screw terminals. a. Using the flathead screwdriver, turn each screw terminal counterclockwise until it is in the open position. NOTE: The terminals must clamp down on bare metal and not the insulation. Strip insulation off the end of wires if needed. 2. Connect the provided lithium ion battery to the LES100 board. a. Insert the positive red battery wire into the Bat+ terminal. Screw the terminal down until the wire is tightly held. b. Insert the negative black battery wire into the Bat- terminal. Screw the terminal down until the wire is tightly held. 3. Connect the LL Indoor Solar Panel to the Solar input. a. Insert the positive red solar wire into the Solar+ terminal. Screw the terminal down until the wire is tightly held. b. Insert the negative black solar wire into the Solar- terminal. Screw the terminal down until the wire is tightly held. NOTE: If using a capacitor or supercapacitor, allow adequate charge up time in decent indoor light (300 lux). See Figures 63 and 64 in the Capacitor Storage Element Operation section in the Application Notes for estimated charge times.

7 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 7 Figure 2, Assembled LES100 Circuit Board. Solar and Battery Inputs are circled in red. 4. Download the LES100 Data Monitor app from Google Play store, Figure 3, LES100 Data Monitor Google Play Store Listing. 5. Open the LES100 Data Monitor and scan for LES100 devices. a. From the home screen click Scan (Figure 4). Bluetooth devices found will be displayed on the screen. b. Once the LES100 device is found, Click Connect (Figure 5).

8 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 8 6. Once connected, observe light level, battery level, and temperature displays (Figure 6). 7. Configure sensors as desired. Changes to connection parameters are automatically saved (Figure 6). 8. If connection is lost, the LES100 Data Monitor will automatically reconnect to the last connected device if found, as long as Bluetooth scanning is not reset (turned off then back on).

9 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 9 LES100 Data Monitor Notes Home Page The LES100 Data Monitor home page can enable/disable Bluetooth scanning and displays Bluetooth devices found in a scrollable list. To enable/disable Bluetooth scanning, click the Start Scanning or Stop button at the bottom of the screen (Figure 4). To connect to a found LES100 device, click the Connect button next to the desired device (Figure 5). The LES100 Data Monitor remembers the last device it was connected too so if connection is lost it will automatically reconnect if it finds it again. Clicking the Stop scanning button will reset the device memory so the app will not automatically reconnect. Figure 4, LES100 Data Monitor Home Screen Figure 5, LES100 Data Monitor Scan Results Device Page After successfully connecting to a LES100 device, the device home page will be displayed. All of the LES100 Bluetooth profiles and services will be displayed as separate rows on the page (Figure 6). Each Profile or Service performs a different function such as displaying collected sensor data or adjusting Bluetooth connection parameter.

10 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 10 The LES100 Bluetooth profiles and services include the Battery Level Profile, the Temperature Profile, the Light Level Profile, the Connection Control Service, and the Device Information Service. Battery Profile Figure 6, LES100 Data Monitor Device Home Screen The Battery Profile displays battery level data collected by the battery monitoring circuitry. Data is plotted on a line chart while the measured battery state of charge (SOC) [%] and actual battery voltage is displayed in real time above it (Figure 7). Figure 7, Battery Level Data Display Row

11 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 11 Figure 8, Battery Level Configuration. Clicking on the Battery Profile row will reveal its configurable settings (Figure 8). The battery level sensor can be configured ON/OFF and the sensing period can be adjusted from 100ms 25.5s. Battery Max Level and Battery Min Level determine state of charge percentage that is displayed above the line chart and can also be adjusted to accommodate for different battery types and setups. The state of charge is calculated be comparing the current battery voltage to the maximum and minimum battery voltage settings. SOC % = (Battery Max Level Current Battery Level) (Battery Max Level Battery Min Level) 100 Battery level is measured by a resistive divider R BM_1 and R BM_2. The measured voltage is then sent to the LES100 Data Monitor where it is scaled to reflect the actual battery voltage. NOTE: Changing Battery Max Level and Battery Min Level has no effect on the charging scheme of the LES100 device, it is only used to calculate SOC. Connecting batteries to the LES100 device that are incompatible with the hardware configured charging scheme could result in damage to the battery and the LES100 device. Temperature Profile The Temperature Profile displays temperature data collected by the internal CC2650 sensor. Data is plotted on a line chart while the real time measured value is displayed above it (Figure 9). Figure 9, Temperature Configuration Due to the low resolution of the internal 6-bit ADC, the temperature measurements are accurate to ±2ºC. Clicking on the Temperature Profile row will reveal its configurable settings (Figure 10).

12 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 12 Figure 10, Temperature Configuration The Temperature Profile can configure the temperature sensor ON/OFF and adjust the sensor period from 100ms to 25.5 seconds. Light Level Profile The Light Level Profile displays data collected by the OPT3001 lux-meter. Data is plotted on a line chart while the real time measured value is displayed above it (Figure 11). Figure 11, Light Level Data Display Row The OPT3001 is capable of measuring light levels from.01-83,000 Lux. For perspective, an indoor room with no windows will be illuminated at approximately 300 Lux. Direct sunlight will measures approximately 100,000 Lux. Clicking on the Light Level Profile row will reveal its configurable settings. Figure 12, Light Level Configuration The Light Level Profile can configure the sensor ON/OFF and the adjust the sensor period from 100ms-25.5s.

13 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 13 Connection Control Service The Connection Control Profile can adjust the Bluetooth Connection Interval, Slave Latency, and Timeout. These parameters define how the LES100 and LES100 Data Monitor behave after connection. A connection event refers to a specific time when the two devices send data back and forth. This could be data collected from sensors or a handshake to verify the other device is still present. Figure 13, Connection Control Service Row The Connection Interval sets the time between connection events. After connecting and after connection events, each device will wait exactly one Connection Interval and then attempt a connection event with the other device. If the other device is not found it will wait another connection interval and try again. If the device continues to not find the other device a timeout will occur and the connection will be lost. The Slave Latency is the maximum consecutive number of times a device can skip a connection event without the connection being lost. At the time of a connection event, if a device has no data to transfer it can skip the event and stay asleep to conserve power. The Supervision Timeout is the maximum amount of time allowed between two successful connection events. If a successful connection event does not occur within the Supervision Timeout, the connection will be severed. According to the Bluetooth Low Energy protocol, the maximum allowed time between connection events is 16 seconds. This restricts the values that the parameters can be set at. In General; The Connection Interval multiplied by the Slave Latency +1 must be less than 16seconds. The Supervision Timeout must be greater than the previous bullet point and must be less than 32 seconds. To modify the connection settings, adjust the parameters to the desired levels and click the Send Parameters button.

14 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 14 Sending connection parameters does not guarantee that they will be accepted. Once received, the LES100 device can accept or reject the sent parameters or may wait until a more convenient time to change connection parameters. To read the current connection settings click the Read Parameters button. These settings greatly impact the power consumption of the LES100 device. These parameters, along with the sensor time period, can be optimized so that the device can operate down to 200 lux and below. For more information on the Bluetooth connection parameters see Chapter 5 of the CC2640 and CC2650 SimpleLink Bluetooth Low Energy Software Stack Developer s Guide. NOTE: In this guide and in the LES100 Data Monitor, the parameter units are expressed in seconds whereas the CC2640 and CC2650 SimpleLink Bluetooth Low Energy Software Stack Developer s Guide expresses the parameters by their actual integer values. For conversion from seconds to actual integer value see Chapter 5 of mentioned guide. Saving Settings All settings in the app save automatically after they are changed. This includes the on/off and periods of all sensors, the minimum and maximum Battery levels, and the connection parameters. When the app is closed and reopened, all settings will be configured to the last used values. Code Composer Studio Additional Equipment SimpleLink SensorTag Debugger DevPack (Sold Separately). Micro USB to USB cable (Sold Separately). Installation Setup Modification and customization of the original TI SensorTag code was implemented using Code Composer Studio v and TI BLE v2.2.1 Bluetooth stack, which is free to download and use. NOTE: Instructions are based on the Windows 7 OS. 1) Install TI BLE Bluetooth stack. a. Open the provided LES100 Software folder. b. Run the ble_sdk_2_02_01_18_setup.exe executable. c. Follow the standard recommended installation process which will include installation of TI-RTOS for CC13xx and CC26xx Wireless MCUs

15 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 15 i. If a previous version of TI-RTOS is already installed, TI-RTOS may not be installed automatically and will need to be installed manually. Installation executable can be found in the included software. ii. Verify that TI-RTOS is installed into the TI home directory (default: C:\ti). See Figure 14. Figure 14, TI-RTOS installation folder. 2) Update SimpleLink directory. a. Navigate to the TI home directory (default C:\ti). b. Rename the old SimpleLink folder to save a copy of the original. Ex. C:\ti\SimpleLink_Original c. Open the provided LES100 Software folder. d. Right click the zipped SimpleLink folder and Select Extract All. e. Click Browse. f. Navigate to and select the TI home directory (default C:\ti). g. Click Extract. h. Wait for the Extraction to finish. The TI home directory should now contain both the original simplelink folder and the provided simplelink folder (Figure 15).

16 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 16 Figure 15, TI home directory after updating simplelink folder. 3) Install CCS v a. Open the provided LES100 Software folder. b. Run the ccs_setup_ exe file. c. Accept terms and agreement. Press Next d. Select CCS Installation/Home folder (default is c:\ti, Figure 16). Press Next. Figure 16, TI Installation Location e. For Processor Support: Check SimpleLink Wireless MCUs. CC2538 device support, CC26xx device support and TI ARM Compiler options are required (Figure 17). Press Next

17 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 17 Figure 17, Processor Support Options f. For Debug Probe Options, TI XDS and Tiva/Stellaris ICDI debug probe support are required (Figure 18). Press Next. Figure 18, Debug Probe Options g. No App Center options are required (Figure 19). Press Next.

18 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 18 Figure 19, App Center Options h. You may need to allow the program firewall access. i. Press Finish. 4) Update the CCS flashcc26xx.dll file. a. Open the provided software files. b. Right click and copy FlashCC26xx.dll. c. Navigate to the <CCS62 INSTALL DIR>\ccsv6\ccs_base\DebugServer\bin directory (default install directory is C:\ti) and find FlashCC26xx.dll. d. Rename the old FlashCC26xx.dll to FlashCC26xxVOID.dll. e. Paste the new FlashCC26xx.dll copied from the provided software. f. The directory should now resemble Figure 20. Figure 20, Updated <CCS62 INSTALL DIR>\ccsv6\ccs_base\DebugServer\bin directory.

19 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 19 5) Install TI ARM compiler. Refer to Figure 21 and 22 for help identifying mentioned fields. a. Open CCS (Code Composer Studio) b. On the top menu bar click Help Install New Software (Figure 21). This will take you to the Available Software Installation page (Figure 22). Figure 21, Install New Software

20 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 20 Figure 22, Install Available Software Page. c. In the bottom left hand corner, uncheck the Show only the latest versions of available software box. d. In Work with field, type: e. Under TI Compiler Updates, select TI ARM Compiler Tools Version Click Next. (Figure 22) f. The Review Licenses screen should appear. Accept and Click Finish. g. Restart CCS to finish installation. 6) Install the Debugger Dev Pack interface. a. Close out of CCS if it is open. b. Plug the Debugger Dev Pack into a USB port on your computer Via a B-Male Micro USB to an A-Male USB cable and wait for the driver to finish installing. (Figure 23)

21 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 21 Figure 23, Debugger Driver Installation. 7) Install TIRTOS v a. Open the provided software folder. b. Run the tirtos_simplelink_setupwin32_2_11_01_09 executable. c. After the setup wizard loads, click Next (Figure 24) Figure 24, TI-RTOS setup wizard. d. Accept the license agreement. Click next e. Select the proper home directory (default is C:\ti). Click Next f. After Installation Click Finish. g. Open CCS or close and restart it if it is already open. h. CCS should detect new installable products (Figure 25). Click Install.

22 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 22 Figure 25, Install Discovered Products. 8) Import the LES100 CCS app and stack projects. a. Open CCS. b. Make sure that the CCS Edit button in the upper right corner is pressed. c. In the Project menu tab click Import CCS projects (Figure 26). Figure 26, Import CCS Project tab.

23 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 23 d. The Select CCS Project to Import page should now be open. (Figure 27) Figure 27, Select CCS Projects to import e. Under Select search-directory, Click Browse f. Navigate to <TI home directory (default: C:\ti)>\simplelink\ble_sdk_2_02_01_18\examples\cc2650stk\sensortag\ and select the ccs folder (Figure 28). Click OK

24 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 24 Figure 28, LES100 Project Location g. The sensortag_cc2650stk_app and sensortagcc2650stk_stack projects should appear in the Discovered projects box (Figure 27). h. Check the box for each project (Figure 27). i. Make sure that copy projects into workspace box is unchecked (Figure 27). j. Automatically import referenced projects found in same search-directory box can be checked or unchecked (Figure 27). k. Click Finish.

25 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 25 9) Import the LES100 CCS bim_extflash project. a. Return to the Import CCS Projects page by clicking Projects Import CCS Projects... b. Under Select search-directory:, navigate to <TI home directory (default: C:\ti)>\simplelink\ble_sdk_2_02_01_18\examples\util\bim_extflash\cc2640\ and select the ccs folder. Click OK c. The bim_extflash project should appear in the Discovered projects: box. d. Check the box next to the bim_extflash project. e. Make sure the Copy projects into workspace box is unchecked. f. The Automatically import reference projects found in same search-directory box can be checked or unchecked. g. Click Finish. The bim_extflash project should appear in the Project Explorer along with the sensortag_cc2650stk_app and sensortag_cc2650stk_stack projects. (Figure 29). Figure 29, Project Explorer with imported projects. See instructions below for build and download/debug instructions. Build and Download/Debug The build and download process is more involved due to the multi project structure. The build configurations of each project depend on each other so the order in which projects are built is important. Some projects also share memory segments so the order of download is also important. For more information on the build and debug process see the CC2640 and CC2650 SimpleLink Bluetooth Low Energy Software Stack Developer s Guide sections 2.6. ( ) Follow these steps to build, download and debug code on the LES100.

26 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 26 1) Clean all projects. a. Under Projects menu tab, Click Clean. (Figure 30). Figure 30, Project - Clean... b. The Clean form should appear (Figure 31). Figure 31, Clean Projects Screen.

27 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 27 c. At the top right of the form select the Clean all projects radio button. d. UNCHECK the Start a build immediately box at the bottom right of the form. e. Click OK. Wait for the cleaning process to finish. 2) Build bim_extflash project. a. Right Click the bim_extflash project in the Project Explorer (Figure 32). Figure 32, Right Click - Build Project. b. Select Build Project. Wait for the build process to finish. 3) Repeat the build process (Step 2) except for the sensortag_cc2650stk_stack project 4) Repeat the build process (Step 2) except for the sensortag_cc2650stk_app project 5) Connect Debugger Dev Pack to the LES100 and plug it into a USB port on your computer. Wait for the driver software to finish installing. 6) Attach the Debugger Dev Pack to the LES100 using the Dev Pack Connectors P1 and P2. (Figure 33)

28 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Figure 33, Circuit Board Dev Pack Connector. 7) Download/Debug the bim_extflash project. (Figure 34) a. Right Click the bim_extflash project. b. Select Debug As 1 Code Composer Debug Session. c. Wait for the program to load. Figure 34, Download/Debug. Page 28

29 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 29 d. Click the red stop square on the toolbar to stop the debug session. (Figure 35) Figure 35, Terminate Debug Session. 8) Repeat the Download/Debug process (Step 7) except for the sensortag_cc2650stk_stack project. 9) Repeat the Download/Debug process (Step 7) except for the sensortag_cc2650stk_app a. To debug the application, click the green run arrow instead of the red stop square after program loads. Single Step Flash Programming A single step programming process is possible by merging the output HEX files together and using a Flash Programming tool. The TI SmartRF Flash Programmer tool can be used with the Debugger Dev Pack to flash load HEX files to the CC2650 chip. The process of creating and using merged HEX files is outlined in the CC2640 and CC2650 SimpleLink Bluetooth Low Energy Software Stack Developer s Guide section 2.7 and the CC2640 BLE OAD User s Guide. Overview of CC2650 Code Structure The code structure of the LES100 is broken up into three separate projects; bim_extflash, sensortag_cc2650stk_stack, and sensortag_cc2650stk_app. These projects are loaded into separate segments of flash memory and work together to produce the final functionality of the device. The bim_extflash project is the Boot Image Manager which handles Over Air Downloads. This gives users the ability to update device software through the BLE interface. For more information on using the BIM refer to the CC2640 BLE OAD User s Guide. ( key/communityserver-discussions-components-files/538/cc2640- BLE-OAD-User_2700_s-Guide.pdf). The sensortag_cc2650stk_stack contains the BLE software stack and is responsible for implementing the Bluetooth Low Energy protocol. For details on the BLE stack see the CC2640 and CC2650 SimpleLink Bluetooth Low Energy Software Stack Developer s Guide.

30 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 30 The sensortag_cc2650stk_app contains the application. This includes the main application loops and threads, Bluetooth profiles, startup procedures, hardware interfaces, and the interfacing the BLE stack. The majority of customization will only affect the sensortag_cc2650stk_app project. Adding sensors or profiles can be done by modifying the application project (See Adding a Custom Service or Profile). More information, examples, and documentation for TI SimpleLink TIRTOS can be found in the TI Resource Explorer found at Particularly helpful is the SimpleLink Academy for SimpleLink CC2640R2 SDK 1.50 found under Software SimpleLink CC2640R2 SDK -v: SimpleLink Academy It provides thorough explanation of the TI BLE stack, TIRTOS operating system, interfacing with sensor drivers, and examples. Adding a Custom Service or Profile New sensors or functionality added to the LES100 will have to be integrated into the application code structure. Profile Setup A tutorial on how to set up a custom profile in a TI BLE application can be found in the TI Resource Explorer under Software SimpleLink CC2640R2 SDK -v: SimpleLink Academy Lab Overview Bluetooth 4.2 Custom Profile. External Sensor/Device Setup A tutorial on setting up sensors and an example setting up a UART connection can be found in the TI Resource Explorer under Software SimpleLink CC2640R2 SDK -v: SimpleLink Academy Lab Overview TI Drivers Configuring TI Drivers. Initialization Once the sensor is configured and the profile is set up the last step is to initialize the profile in the application code. This can be done in the sensortag_init() function located in the sensortag.c file. Figure 36 shows where an example initialization function, SensorCustom_init(), should be place. The initialization function should include required components outline by profile setup section.

31 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 31 Android Studio Installation Setup Figure 36, Location in code to initialize a custom service. 1) Install Android Studio. a. Download the latest version of Android Studio from b. Run the installation executable after it has finished downloading. c. The Android Studio Setup welcome screen should appear (Figure 37). Click Next. Figure 37, Android Studio Installation Wizard Welcome Screen. d. For Choose Components, check all boxes (Figure 38). Click Next.

32 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 32 Figure 38, Choose Android Studio Components. e. For License Agreement, Click I Agree (Figure 39). Figure 39, Android Studio License Agreement.

33 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 33 f. For Configuration Settings, Choose a desired Android installation location and SDK installation location or use the default locations (Figure 40). Click Next. Figure 40, Android Studio Configuration Settings. g. For Choose Start Menu Folder, Choose a location to create the program shortcuts or use the default Android Studio folder. Click Install. h. Wait for the Installation to finish. Click Next. i. On the Completing Android Studio Setup screen, check the Start Android Studio box (Figure 41). Click Finish.

34 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 34 Figure 41, Android Studio Installation Completion Screen. Android Studio should open up. j. The first time running Android Studio, it will go through the preferences setup. Choose settings as desired. 2) Import the LES100 Data Monitor project. a. Open Provided LES100 Software folder. b. Right click the zipped sensortag-20-android folder and click Extract All. c. Choose a location on your computer put the LES100 Data Monitor project. Click Extract. Wait for extractor to finish. d. Open Android Studio if it is not already open. e. Close out of any open projects and navigate to the Android Studio welcome screen (Figure 42).

35 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 35 Figure 42, Android Studio Home Screen. f. Select import project (Eclipse ADT, Gradle, etc.). g. Browse to the project location you choose to extract to. h. Expand sensortag-20-android folder expand sensortag20 folder Select build.gradle (Figure 43). Figure 43, Import Android LES100 Data Monitor Project from Provided LES100 Software.

36 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 36 i. Click OK. j. An error prompt will appear indicating the SDK path has changed. Allow Android Studio to reroute the SDK path by clicking OK. k. Android Studio will attempt to build and sync the project. This should fail because the needed software packages have not been installed yet. 3) If build/sync failed, install needed software packages. a. In the bottom tool bar, Open the Messages tab to view the build error (Figure 44). Figure 44, Missing Platform(s) error. b. If the build error is failed to find target, Click the provided link; Install missing platform(s) and sync project. i. Accept license agreement, Click Next (Figure 45). Figure 45, SDK Liscense Agreement.

37 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 37 ii. Wait for the package to be installed, Click Finish. c. If the build error is failed to find build Tools, click the provided link; Install Build Tools revision and sync project (Figure 46). Figure 46, failed to find build tools error. i. Wait for Build Tools to install. Click Finish. d. If you get an error saying: Gradle sync failed: Unsupported method: BaseConfig.getApplicationIdSuffix(). The version of Gradle you connect to does not support that method. To resolve the problem, you can change/upgrade the target version of Gradle you connect to. Alternatively, you can ignore this exception and read other information from the model. Consult IDE log for more details (Help Show Log) (14s 289ms). Double click on build.gradle file and change the line classpath 'com.android.tools.build:gradle:1.3.0'to classpath 'com.android.tools.build:gradle:3.0.0'. Then click on Try Again located in the gray area above the code text box. e. If any other errors due to missing software occur, follow the provided links to install the missing components. 4) Install USB ADB driver for the specific Android device you will be using for development. As an example, the set-up process for a Kindle Fire Tablet will be shown. a. Using the Windows Device manager, uninstall any drivers the computer has installed for the Kindle Fire (Figure 47).

38 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 38 Figure 47, Uninstall Any Drivers present for your Android Device. b. Make sure Android Device is not plugged into your computer. c. Enable USB Debugging on your Android device. Android device developer settings are hidden by the manufacturer and need to be enabled. i. To enable Developer settings. 1. Open Settings About. (or find where the build umber is located on your device) 2. Click Build number 7 times. (For Kindle Fire, Serial Number is tapped 7 times instead of build number and is located in Settings Device Options) 3. After the 7 th tap, the developer menu should appear in the settings menu. 4. Although the procedure should be the same for all android devices, the Build number setting may have a different name and be located in different places for different devices. ii. In Developer settings, make sure Enable ADB or USB debugging are enabled. d. Obtain the USB ADB driver for you specific Android Device. The following webpage provides instructions on installing OEM USB Drivers for a variety of Android device manufacturers. i. For Kindle Fire, USB ADB driver can be downloaded from this URL; e. Follow the manufactures instructions on installing the ADB driver for your android device. i. For Kindle Fire, a setup executable is provided.

39 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 39 ii. After running the executable and following the installation prompts, the driver is ready to use. iii. After connecting the Kindle Fire to the computer via USB it was able to successfully recognize and install the correct driver for the Kindle Fire (Figure 48). Figure 48, Kindle Fire Driver Installation. f. Connect to Android Device in Android Studio i. Open Android Studio. ii. On the bottom tool bar, click 6: Android Monitor (or 6: Logcat) (Figure 49). The ADB should initialize. Figure 49, Kindle Fire Driver Installation. iii. A popup to enable USB debugging should appear on your android device (Figure 50). Click OK.

40 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 40 Figure 50, Allow USB Debugging on Android Device. g. Your Android device is now connected and ready to use in Android Studio. Build and Run/Debug LES100 Data Monitor The following steps will outline how to build and debug the LES100 project on a connected Android device. Assuming you have already gone through the Android Installation and setup procedure. 1) Open the LES100 Android Studio project. 2) Connect your Android device to the computer via USB. 3) Open the Android Monitor tab on the toolbar at the bottom of the screen (Figure 51).

41 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 41 Figure 51, Android Monitor Initialize ADB. 4) After the ADB initializes, a pop up message to allow USB debugging on your Android device will appear. Click OK. 5) To build the project, select Build on the top menu bar and click Make Project (Figure 52). Figure 52, Make Project. 6) To download and run or debug the project on your Android device, select Run on the top menu bar and click Run BleSensorTag or Debug BleSensorTag. (Figure 53).

42 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 42 Figure 53, Run Program. 7) If a deployment target has not been set, a prompt will ask you to select a target device. Choose your connected Android device. Click OK. NOTE: Run/Debugging with Virtual Devices is incompatible with the LES100 Data Monitor because of the Bluetooth features. Overview of Android Code Structure Structure The LES100 Data Monitor utilizes both java and xml to create the functionality and User Interface (UI) of the application. In general, java activities handle the flow of the application while xml files are used to define the various layouts, constants and other UI components. Apart from the build files, the project code is separated into the java, assets, and res (resource) folders. (located at \sensortag20\blesensortag\src\) The java folder (located at \sensortag20\blesensortag\src\main\jave\com\powerfilm\les100\ble\sensortag) contains the main application activities. For the LES100, this includes MainActivity.java, DeviceActivity.java and all of the Bluetooth profiles and row java files. MainActivity.java The MainActivity.java code is run at the start of the application and is responsible for handling user interaction with the home screen. It handles scanning for Bluetooth devices and displaying devices found to the user. DeviceActivity.java The DeviceActivity.java code runs when the main activity selects a device to connect too. This activity handles the Bluetooth connection, data transfer and interaction with the device home page. After discovering all Profiles and Services of the connected device, the DeviceActivity initializes a row for each one. If new Bluetooth profiles or service are added to the application, this activity will need to be modified to include those as well.

43 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 43 Bluetooth Profiles and Rows Each Bluetooth Profile or Service of the LES100 has a java activity associated with it. This code is run after the profile or service is discovered. These activities handle data specific to their functionality. The LES100 Profiles and services functionality are outlined in the section LES100 Data Monitor Notes. Rows are defined by the GenericCharacteristicTableRow activity and display data and information on the UI. If extra features are required, profiles may have their own specific row activity which is an extension of the GenericCharacteristicTableRow. For example, the Battery Level Profile needs extra features to define the Max and Min Battery levels. These features are created in the BatteryTableRow activity. Layouts The LES100 UI is defined in the xml files located in the layout section of the res folder. The xml files define the UI elements for the various pages and screens throughout the application. Other The res folder also contains xml files with string constants, gatt_uuids, and preferences. The Android Manifest file located in the root directory somewhat ties all application components together. This is where the project launch location is stored, application permissions, and other critical settings are. Android Studio projects use the Gradle build system to save build settings and configurations. Adding a Customized Service or Profile After adding a sensor along with a service or profile to the LES100, the LES100 Data Monitor must also be updated to be able to discover and display its data. For general information about android BLE development and SensorTag specific Android development see the SensorTag wiki guide at ent To integrate a new Bluetooth service into the existing Android project, the DeviceActivity.java, SensorTagGatt.java and the gatt_uuid.xml files will have to be modified. Also, a new Bluetooth profile class will have to be created. If the service requires more than a generic row to display its data then a new row class will have to be created. SensorTagGatt.java modification The SensorTagGatt.java class contains the UUIDs for all Bluetooth services used by the LES100. The UUIDs of the new service must be added to this class. Figure 54 shows an example entry for a new custom profile commented out.

44 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 44 Figure 54, Example template of the UUID entries for a custom service commented out in the SensortagGatt.java class. gatt_uuid.xml modification The gatt_uuid.xml file contains descriptions and names of the UUIDs of each service and its characteristics and are used by the user interface. Descriptions and names will need to be given for a new service or profile. The commented-out code in the gatt_uuid.xml file, seen in Figure 55, can be used as a template. Figure 55, Example template of UUID name and description entries commented out in gatt_uuid.xml Creating a Custom Bluetooth Profile Class A custom Bluetooth profile class will be an extension of the generic Bluetooth profile class. These together will handle reading and writing data to the service characteristics, initializing the table row on the user interface, and any functionality related to the custom Bluetooth profile. To create a new custom Bluetooth class, use the SensorTagCustomProfile template found in the source, BleSensorTag-java-com.powerfilm.les100-ble-sensortag-SensorTagCustomProfile.java Uncomment code sections during implementation. DeviceActivity.java modification The DeviceActivity.java code runs when the main activity selects a device to connect too. The new profile must be added to the existing code structure so it is discoverable to the LES100. Use the commented-out code, seen in Figure 56, as a template. This code is run in the mgattupdatereceiver broadcast receiver when the onreceive method is triggered.

45 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 45 Figure 56, Example Custom Service initialization entry commented out in DeviceActivity.java The Custom profile will also need to be added to the code that enables each row, use the commented-out line as a template (Figure 57). Figure 57, location to enable a Custom Service during initialization in DeviceActivity.java, example commented out. Custom Profile Row By default, a new profile will use the GenericCharacteristicTableRow to display data using a Sparkline, turn the service or sensor on/off, and adjust the service period. If the custom profile requires addition elements on the row a designated row class that extends the GenericCharacteristicTableRow will be required. See the profiles that use designated row classes for examples on how to implement a custom row class.

46 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 46 Block Diagram Diagram Figure 58, LES100 system block diagram. Block Diagram Notes BQ25570 Energy Harvester Responsible for collecting solar energy from the indoor solar panel and storing that energy into a Li-ion battery or other rechargeable storage element. Provides steady power to the entire system. Output voltage is adjustable from 1.3V to Storage Element voltage via R out_1 and R out_2. CC2650 Wireless MCU Responsible for collecting data and configuring sensors. Handles Bluetooth Low Energy connection and communication with external Bluetooth devices. LES100 Data Monitor Receives and displays data from connected LES100 devices. Provides a user interface for configuring sensor and Bluetooth connection settings. Schematic Overview

47 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 47 The LES100 design can be broken down into the energy harvesting portion and the Bluetooth MCU portion. These components are physically separated on different halves of the circuit board and are only connected by ground, the power supply rail, and the battery level signal. BQ25570 Energy Harvester [final doc will have separate page for schematic] Figure 59, LES100 BQ25570 energy harvester circuit diagram. The BQ25570 is an ultra-low-power boost-buck charge controller and battery management dedicated IC. Solar is connected to the SOLAR_GND and SOLAR_PWR pins and the storage element is connected to BATT_GND and BATT_PWR pins. The BQ25570 will provide steady power to the RAILOUT_PWR rail using energy collected from the solar or from energy stored in the battery. The energy harvesting circuit is connected to the Bluetooth MCU circuit through RAILOUT_PWR, RAILOUT_GND, and the VBATT_SIGNAL pins.

48 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 48 Bluetooth and Sensing MCU [final doc will have separate page for schematic] Figure 60, LES100 Bluetooth and sensing circuit diagram. The CC2650 Wireless MCU runs the LES100 application, collects data from sensors, and handles Bluetooth communication. I/O Sensors are connected to IO of the CC2650. The OPT3001 uses three IO pins to set up I2C serial communication with the MCU; DIO_1, DIO_2, and DIO_5. The Battery Level signal is routed to pin DIO_6. Ports and Connectors P1 is the programming JTAG interface. P2 is the 20 pin TI Dev Pack connector. This enables TI sensor Dev Packs to be plugged in and integrated into the LES100 system. P1 and P2 are physically oriented to allow the TI Debugger DevPack to be connected and used for programming and debugging. (See Code Composer section for more information on setting up the Debugger Dev Pack) Access to all 10 IO pins is available via P3 female pin header.

49 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 49 Switches S1 is the reset button switch. Under normal operation, CC2650 NRESET pin is pulled high. When S1 is depressed then released, the NRESET pin is pulled to ground and the CC2650 will reset. Layout Top Figure 61, LES100 circuit board top layout.

50 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 50 Bottom LES100 Application Notes Power Consumption Optimization Figure 62, LES100 circuit board bottom layout. The LES100 is able to adjust Bluetooth connection parameters, which can greatly reduce power consumption. The power consumption of the device is heavily dependent on the Bluetooth connection interval and the data period of the sensors. Both parameters can be adjusted within the application. Using long connection intervals (16 seconds max) and long time periods between sensor measurements will allow the device to operate at very low light levels (< 100 lux). Hardware Configurations I/O Access External sensors can be added to the system via the 10 pin I/O breakout header. On board sensors can be disconnected by removing SMD jumpers so that all I/O pins can be accessed. The Luxmeter can be disconnected by removing resistors R3, R7, R8, and R10. This will free I/O pins DIO_1, DIO_2, and DIO_3 and disconnect the OPT3001 from the power supply rail. The Battery monitor circuitry can be disconnected by removing resistor R9. This will free DIO_6.

51 Bluetooth Indoor Solar Development Kit (LES100) Operation Guide Page 51 Charge Control Configuration The LES100 hardware is currently configured to charge a Li-ion type battery with max voltage of 4.2V and the output voltage is set to 3.0V. The configuration can be customized by modifying SMD resistor dividers per the BQ25570 datasheet specifications which can be found at section 7.3. Output voltage can be set using R OUT _1 and R OUT _2. Max Battery Voltage can be set using R OV _1 and R OV _2. The minimum battery voltage and output turn on voltage can be set using resistors R OK _1,2,3. Capacitor/Super Capacitor Storage Element Operation The LES100 is capable of running and operating with a capacitor as the storage element instead of the li-ion battery. Except the capacitor, the hardware configuration of the board can remain the same. Theory of Operation A capacitor will behave similarly to a small capacity battery when used as a storage element. It will charge and discharge quicker and may not hold as much energy as a li-ion battery. Starting from fully discharged, when the LES100 is placed in a decently lit room the capacitor will begin to charge up. Once the voltage is above 3.2V the Bluetooth radio will be enabled and ready to connect to the LES100 Data Monitor Android Application. The capacitor will maintain steady power to the system while light is available. If the lights are turned off, the capacitor will discharge. When it reaches 3V the radio will shut down. The LES100 Data Monitor comes configured to remember the last connected device and will automatically reconnect once the device turns back on. Specifications Capacitor must be at least 1800uF or greater. Capacitor must be rated for 6V or greater. Charge and discharge rate will be greatly affected by the size of the capacitor. If the capacitor is completely discharged (0V) the charge rate will be slower because the harvester chip is not yet fully functional. Figures 63 and 64 show charge up times vs storage capacitance size for 0V-3V and 3V-4.2V.