element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Bluetooth Unleashed Design Challenge
  • Challenges & Projects
  • Design Challenges
  • Bluetooth Unleashed Design Challenge
  • More
  • Cancel
Bluetooth Unleashed Design Challenge
Blog Smart Doorbell System - Part 1 - Getting to know the CC2640R2
  • Blog
  • Forum
  • Documents
  • Polls
  • Files
  • Events
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: shabaz
  • Date Created: 6 May 2018 2:50 PM Date Created
  • Views 1737 views
  • Likes 11 likes
  • Comments 9 comments
  • bluetooth
  • cc2640r2
  • ti launchpad
  • bluetooth le
  • bluetooth_unleashed
  • bt_smart_doorbell
  • design_challenges
  • bluetooth 5.0
  • texas_instruments
  • cc2640r2f
  • texas instruments
  • bluetooth_le
Related
Recommended

Smart Doorbell System - Part 1 - Getting to know the CC2640R2

shabaz
shabaz
6 May 2018

Introduction

This first blog post in the Smart Doorbell System series discusses why one would want a better doorbell, and introduces what will be at the heart of it - the CC2640R2 LaunchPad board, and briefly explores its microcontroller.

 

This blog post also discusses how an enclosure could be created using Autodesk Fusion from the circuit board CAD files. A nice enclosure is important for consumer applications.

 

Motivation

Most existing wireless doorbells (lets call them doorbell 1.0) seem to be built down to the lowest cost. I wanted to build Doorbell 2.0! The cheapest ones come in two parts; the bell push or transmitter portion, and the chime or receiver portion. They are a compromise. The person pressing the button actually has little idea if the chime has actually actuated if the chime is located too far, because it will be inaudible. There isn’t much feedback. Also, if the user is outside in the garden or visiting a neighbour, they may forget to take the wireless chime module with them, or it may not operate with batteries. There are versions with multiple chime modules (including battery powered versions) but they do not necessarily have a good wireless range, so one may as well just buy a version with a louder audio output perhaps and hope for the best if you’re in the garden. Finally there are existing Internet-connected solutions that can also capture video too, but they are more of an amalgamation of a doorbell, door entry system and security system, and are in a very different price ballpark too.

 

It would be interesting to use Bluetooth because then bidirectional communication is possible between the bell push, and the chime module, instead of the one-way transmission with existing low cost systems. Also, in future the system could be expanded with more functionality, such as bidirectional audio communication like an intercom. I didn’t want to do that type of thing for the first design, because then there is the risk of excessive feature creep. I’d rather implement the core doorbell features well in this design challenge, and leave future enhancements for a doorbell 2.1 for another time.

 

(Image source: ti.com)image

 

I was keen to use the Texas Instruments CC2640R2 LaunchPad board, because it uses the CC2640R2 which is really low-power. It should be ideal for both the bell push, and the chime module. However, this wasn’t the only reason. I also liked that there was the possibility of having great radio range because it supports the latest Bluetooth Low Energy (BLE or Bluetooth LE) 5.0 specification! Also, the CC2640R2 has a very powerful microcontroller inside; in fact there are several microcontrollers inside the chip. This would provide the capabilities for lots of additional functionality one day, without needing another separate microcontroller which could be difficult to fit inside a small bell push. And finally, many TI designs have a reputation for low energy. This of course is essential for the bell push which usually operates from a small battery.

 

My core requirements are:

  1. No wiring needed for the bell push (i.e. no power cabling or bell wire)
  2. Ability to use the chime indoors or outdoors
  3. A better range than typical wireless doorbells
  4. Ability to alert multiple chime locations from a single single doorbell
  5. Feedback to the caller, so they are aware that the chime is functioning
  6. A good service-free life, at least a year before any batteries need swapping out

 

 

On top of this, there are some additional requirements to make it a successful product, such as a ease-of-use, uncomplicated, classic look to suit most homes, interference-free, an expansion capability so that purchasers know that their investment isn’t wasted after a few years or if they move to a larger home and need longer range, and a design that is easy to expand to create many different products in the range with different chimes and alerts for instance, or with multiple buttons for use with apartments, or for controlling gates or fitted inside tables for letting the waiter know you’re ready to pay the bill. These are all scenarios where I think there could also be great benefits to using Bluetooth LE instead of proprietary RF schemes, and I’m hoping the work done in this design challenge can be applicable to a wide variety of applications.

 

So, while this example implementation of one possible doorbell design looks simple, I’m hoping the end result is more than flexible enough to be useful not only for different doorbell products in the range, but also for many different scenarios too.

image

 

While I’m waiting for the board to arrive, I thought it worthwhile to start digging into the online documentation to learn as much about it all as possible.

 

What is the CC2640R2F?

The CC2640R2F is the microcontroller that is used on the CC2640R2 LaunchPad. Internally it actually has more than one core. The main core is a powerful ARM Cortex-M3, but there is a separate Cortex-M0 that is dedicated to handling the radio tasks. Finally there is also a Sensor Controller Engine that can perform certain input-related tasks while the rest of the device is asleep! It allows for extremely low power consumption.

image

 

Getting to Know the CC2640R2 LaunchPad

The Texas Instrument LaunchPad boards and ‘BoosterPack’ boards form an ecosystem of interchangeable microcontroller boards (these are the LaunchPad boards) and add-on boards (the BoosterPacks). It is a similar concept to Arduino boards and shields for instance. This TI system relies on two 20-way header pin blocks for connections, and often the BoosterPack boards are stackable too. Templates are available to design custom BoosterPacks too, and I will probably use that to create the wireless chime hardware functionality (such as the speaker amplifier).

 

Another great thing about LaunchPads is that they contain an on-board debugger that allows for programming and debugging. The top half of the board contains the debugger, and the lower half has the CC2640R2 circuit. In theory the board could be chopped in half with some care, to reduce the size of it.

 

Unlike an Arduino, the LaunchPad boards often have a few buttons and LEDs already connected to some inputs/outputs, so that users can immediately begin coding and testing with some basic I/O capability. The LEDs can be isolated using on-board jumpers, if desired.

image

 

Pin Assignments

By exploring the CC2640R2 LaunchPad documentation and the CC2640R2 reference guide, it was possible to map out the pin assignments. There is a lot of flexibility; most of the input/output pins can be assigned arbitrarily to most functions. For the chime module, I may use the PWM capability to produce tones, but there is also the possibility to use the digital audio interface to produce high quality sounds. For that reason, the pins with the orange text will be assigned for digital audio. I chose these pins to be compatible with a TI audio BoosterPack in case I chose to use that during the coming weeks as the design comes together.

image

 

Making Enclosures with Autodesk Fusion

Texas Instruments provide a lot of information for their LaunchPad boards. This includes Gerber format files which define the PCB detail. It is possible to go from there into a 3D environment where an enclosure can be designed to fit the LaunchPad perfectly.

 

I’m not a 3D expert, but the process seemed feasible. The first part is to import the Gerber files into a viewer application. Viewmate from PentaLogix is low-cost and allows this. Next, you can export in STL format. This converts some of the information from the Gerber files into a 3D model. I used the file that contained the top copper and board outline. Using Autodesk Fusion, it was possible to import the STL file, and see all the precise data in the 3D CAD package.

image

 

For my project, I will most likely use an off-the-shelf enclosure for the chime unit. However, it is good to know that there is sufficient information to design and 3D print a custom enclosure for those who have such printers.

 

Also, for commercial designs, this exact same process could be used. The PCB designer can work with the enclosure designer and share the output from the PCB CAD tool, so that the enclosure can be accurately fitted, even for fancy curved outline PCBs and enclosures sometimes needed for consumer-friendly applications like chimes!

  • Sign in to reply

Top Comments

  • Jan Cumps
    Jan Cumps over 7 years ago +4
    shabaz , check out the onboard Sensor Controller Engine. You may be able to put the ARM core and BLE radio in a deep deep sleep with that SCE serving as low power watchdog - certainly for the sending side…
  • DAB
    DAB over 7 years ago +3
    Interesting project. DAB
  • Jan Cumps
    Jan Cumps over 7 years ago +3
    I've worked with that Sensor Controller Engine on another BLE microcontroller, from the same family as yours. Here's a blog series on what it does for the CC sub-1 GHz controllers (it's 3 blogs, starting…
  • aspork42
    aspork42 over 7 years ago

    Cool idea!

     

    I have long had lose ideas/plans to make my own doorbell pushbutton / chime system. In the US there is usually around 16-18 VAC available at the pushbutton; so if one is crafty they can make a power supply from that.

    If you are planning on a 1 year battery life, that would be awesome. I've done battery projects (Using Arduino ProMini + ESP 01 module) and it was a lot of work to get the power consumption down.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • mcb1
    mcb1 over 7 years ago

    Great Project.

    Determining where to stop is key to these Design Challenges, as it's easy to run out of time ... image

     

    I wonder if the next iteration (2.1) you can add battery low warning that triggers the chime, in theory you only need to check it at each bell press, and act if it is low.

     

    Look forward to the upcoming posts.

    Mark

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • shabaz
    shabaz over 7 years ago in reply to Jan Cumps

    Hi Jan,

     

    Thanks for the info! It will be interesting to explore the Sensor Controller Engine, and see how low the current consumption can go. I'm definitely excited to explore the power consumption side of things, since that can make or break such a product.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • shabaz
    shabaz over 7 years ago in reply to DAB

    Hi DAB,

     

    Thanks!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • shabaz
    shabaz over 7 years ago in reply to genebren

    Hi Gene,

     

    Thanks! Hehe yes I will definitely try to concentrate on the core tasks, and try to execute them as best as I can, so I have a foundation for the future to do all the cool things that could be possible beyond doorbell applications too. A doorbell will be challenging for the antenna to be honest; not much space for an antenna and ground plane once all the other bits and pieces are in there, so I need to research and experiment a bit.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube