Microchip® Advanced Software Framework

 All Data Structures Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Heart Rate Application

Introduction

******************************Introduction ***********************************

The Heart Rate example application bring-up the Heart Rate profile defined by the Bluetooth SIG which would send the Heart Rate information to BLE enabled collector device. The Heart rate Profile enables the collector device (GATT Client) to connect and interact with a Heart Rate Sensor (GATT Server) for use in fitness applications. The Heart rate sensor sends the heart rate measurement in bpm, energy expended in kilojoules and R-R intervals in seconds. In addition to the heart rate service the heart rate profile also implements the Device Information Service, which provides the information about the Heart Rate Sensor Device.

  • Features -
    • Device Discovery and Disconnection
    • Pairing / Bonding
    • Heart Rate Senor Measurements
    • Console Display
  • Supported Evolution Kit -
    • ATSAML21-XPRO-B + ATBTLC1000 XPRO
    • ATSAMD21-XPRO + ATBTLC1000 XPRO
    • ATSAMG55-XPRO + ATBTLC1000 XPRO
    • ATSAM4S-XPRO + ATBTLC1000 XPRO
  • Running the demo -
    • 1. Build and flash the binary into supported evaluation board.
    • 2. Open the console using TeraTerm or any serial port monitor.
    • 3. Press the Reset button.
    • 4. Wait for around 10 seconds for the patches to be downloaded device will initialize and start-up.
    • 5. The device is now in advertising mode.
    • 6. On a BLE compatible iPhoneŽ/Android phone, enable Bluetooth in the Settings page. Start the 'Atmel Smart Connect Application' and scan for devices. ATMEL-HRP will be appear among the devices scanned. Click on ATMEL-HRP to connect to supported platform.
    • 7. Once connected, the client side will request for the pairing procedure. The console log provides a guidance to the user to enter the pass-key.
    • 8. Once the device is connected, the supported services of Heart Rate and Device Information will be displayed.
    • 9. Once the notifications are enabled the HRM values are displayed as shown in the console and the corresponding mobile app.
    • 10. User can turn off notification by clicking on Stop Notify.

Modules

***************************** MODULES *****************************************

  • BLE Manager -
    • The Event Manager is responsible for handling the following:
      • Generic BLE Event Handling:-
        • BLE Event Manager handles the events triggered by BLE stack and also responsible for invoking all registered callbacks for respective events. BLE Manager handles all GAP related functionality. In addition to that handles multiple connection instances, Pairing, Encryption, Scanning.
      • Handling Multi-role/multi-connection:-
        • BLE Event Manager is responsible for handling multiple connection instances and stores bonding information and Keys to retain the bonded device. BLE Manager is able to identify and remove the device information when pairing/encryption gets failed. In case of multi-role, it handles the state/event handling of both central and peripheral in multiple contexts.
      • Controlling the Advertisement data:-
        • BLE Event Manager is responsible for generating the advertisement and scan response data for BLE profiles/services that are attached with BLE Manager.
  • BLE Profile- The Heart Rate service exposes heart rate and other data from a Heart Rate Sensor intended for fitness applications.
    • Heart Rate service has three characteristics:
      • Heart Rate Measurement -
        • This characteristic is used to send a heart rate measurement.
      • Body Sensor Location -
        • The Body Sensor Location characteristic of the device is used to describe the intended location of the heart rate measurement for the device..
      • Heart Rate Control Point -
        • The Heart Rate Control Point characteristic is used to enable Client to write control points to a Server to control behaviour.
  • BLE Platform Services -
    • Interface Settings -
      • Connect ATBTLC1000 XPRO to SAML21-XPRO-B -> EXT1
      • Connect ATBTLC1000 XPRO to SAMD21-XPRO -> EXT1
      • Connect ATBTLC1000 XPRO to SAMG55-XPRO -> EXT1
      • Connect ATBTLC1000 XPRO to SAM4S-XPRO -> EXT1
    • Serial Console COM port settings -
      • Baudrate 115200
      • Parity None, Stop Bit 1, Start Bit 1
      • No Hardware Handshake
    • 6-Wire Mode Connection Setup -
      • Pins are 1:1 match with SAML21/D21 Xpro EXT1 Header to BTLC1000 XPro Header
      • UART(No Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin13, Tx-Pin14)
      • UART(With Flow Control)-SAM G55 Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6, Rx-Pin16, Tx-Pin17)
      • BTLC1000 Wakeup Pin-SAM G55 XPro Pins(Pin4)
      • BTLC1000 Chip Enable Pin-SAM G55 XPro Pins(Pin10)
      • BTLC1000 Vcc Pin-SAM L21/D21/G55 Xpro Pins(Pin20)
      • BTLC1000 GND Pin-SAM L21/D21/G55 Xpro Pins(Pin19)
    • 4-Wire Mode Connection setup -
      • UART(With Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin15, Tx-Pin17, RTS-Pin16, CTS-Pin18)
      • BTLC1000 Wakeup Pin-SAM L21/D21 XPro Pins (Rx-Pin6)
      • BTLC1000 Chip Enable Pin-SAM L21/D21 XPro Pins (Rx-Pin4)
      • UART(With Flow Control)-SAM G55/4S Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6)
      • BTLC1000 Wakeup Pin-SAM G55/4S XPro Pins(Pin4)
      • BTLC1000 Chip Enable Pin-SAM G55/4S XPro Pins(Pin10)
      • BTLC1000 Vcc Pin-SAM L21/D21/G55/4S Xpro Pins(Pin20)
      • BTLC1000 GND Pin-SAM L21/D21/G55/4S Xpro Pins(Pin19)

Package

***************************** BluSDK Package *****************************************

Generated on Fri Mar 4 2022 23:25:14 for Heart Rate Sensor Application- SAM D21 Xplained Pro by   doxygen 1.8.5