TI Single Mode v4.0 8051 8kB 17.9mA / 18.2mA to 14.7mA / 14.3mA 24uA / 6.8uA Texas Instruments CC256x Dual Mode Classic + No - External None None - - Texas Instruments CC26xx Single Mode BLE v4.1 Cortex[c10] 128kB 20kB 5.9mA - Nordic Semiconductor nRF51822 Single Mode v4.1 / ANT Cortex-M0 128kB / 256kB 16kB / 32kB 9.7mA / 8mA 15.5uA / 5.6uA Nordic Semiconductor nRF8001 Single Mode v4.0 None None None - Dialog Semiconductor DA14580 Single Mode BLE v4.1 Cortex-M0 32kB OTP 42kB + 8kB 4.9mA / 4.9mA - Cypress Semiconductor PSoC 4 BLE / PRoC BLE Single Mode BLE v4.1 Cortex-M0 128kB / 256kB 16kB / 32kB 15.6mA / 16.4mA 18.9uA / 6.2uA CSR CSR101x Single Mode BLE v4.1 16-bit RISC 64kB 64kB 16mA 28uA / 10.8uA 3.3.5.4 – Antennas A vital component of a wireless communication system is the antenna. The antenna is used to transmit the information and with an improperly manufactured antenna, there will be no communication. The design of the antenna and the RF layout is vital since this is how the devices are able to communicate. The antenna design, the layout and enclosure is what determines the range of the device. If 41
Figure Tracker Software findMe Decision Making Flow Chart Finally, the application will need to setup the watchdog timer in case the application hangs up and need reset. Along with the setup of the watchdog timer, the application must also monitor and reset the timer in the event that the software takes longer than the watchdog timer is set for. The figure below is a use case diagram for the tracker application. Figure below is a use case diagram of the EverythingFinder’s tracker application. Figure Tracker Use Case Diagram The EverythingFinder’s tracker application will be attempt to increase battery life of the LIR2450 by entering a low power mode whenever it is possible. Entering low power mode will cut the power consumption by 80 percent. As when it comes to using the TSP62730 to decrease power consumption, it will be exclusively reserved for when we transmit and received data to the main application. Senior Design 2 update: The final design for the EverythingFinder uses a client server architecture. The peripheral serves as a server which post a few services that can be access these services by the central device. These few services convey information like battery status and indication type. 6.0 – PROTOTYPING AND PARTS ACQUISITION The following section of this document contains information related to the prototyping of the EverythingFinder and the acquisition of parts for the EverythingFinder. This section includes a bill of materials and information related to the DFRobot Bluno. Other information can also be found here. 6.1 - DFRobot BLUNO To prototype the many ideas that make up the EverythingFinder, a development board known as the Bluno was purchased from DFRobot. The DFRobot Bluno , shown in Figure 42, is a modified Arduino Uno with a built-in Bluetooth 4.0 (BLE) module. It features many of the same specifications as the open-source Arduino Uno including the Atmel ATmega328P microcontroller. The major difference between the Bluno and the Arduino Uno is that this development board is
30 K-ohm resistor R10 1 13 K-ohm Resistor R3 1 1 nH inductor BLE/MCU L7 1 2 nH inductor BLE/MCU L9, L6 2 3 nH inductor BLE/MCU L8 1 32.768-kHz CRYSTAL OSCILLATOR BLE/MCU Q3 1 32-MHz CRYSTAL OSCILLATOR BLE/MCU Q4 1 CC2450 2.4-GHz Bluetooth low energy System-on-Chip BLE/MCU IC1 1 ANTENNA CHIP 2.4GHZ BLE/MCU A1 1 3.6 V Coin Battery Power MGMT B1 1 4.7 uF capacitor Power MGMT C1, C2 2 470-ohm resistor Power MGMT R1 1 8.2-kohm resistor Power MGMT R2 1 IC Controller Li-ion Power MGMT G1 1 CONN USB MICRO B RECPT Power MGMT 1 Red LED Power MGMT D4 1 Battery holder Power MGMT H1 1 Step Down Converter with Bypass Mode Buck Converter 1 Ferrite Bead 1000-ohms @ 100 MHz Buck Converter LBEAD 1 Table Bill of Materials and Parts Acquisition Component Subsystem System Reference Quantity 2.2 uF capacitor Buck Converter C3, C4, C301, C5 4 1 uF capacitor Buck Converter C6 1
7.1.9 Hardware Integration Tests The following tables, Table 33, Table 34, and Table 35 runs through the test procedure for testing the hardware integration of the MCU, recharge, and buck converter subsystems. Table hardware Integration Test Hardware Integration Test Step Procedure Expected Results Observations 1. With the integrated circuit set up, load test program 2. LED Blinks twice indicating the MCU is running the new program. Passed 2. Measure and record the supply voltage to the MCU Supply voltage is at 3.3 volts. Passed 3. Press button 1 of the MCU. LED Blinks three times to indicate selection of the MCU to set the TSP62730 into low power active mode. Passed 4. Measure the supply voltage to the MCU. Voltage measurement reads 2.1 volts. Passed 5. Press button 1 of the MCU. LED Blinks four times to indicate the selection of the MCU to set the TSP62730 into bypass mode. Passed 6. Measure the supply voltage to the MCU. Voltage measurement reads about the same voltage as the battery. Passed 7. Replace battery with battery that has half charge and the voltage measurement is about 2.5 volts. Load MCU test program 3. LED blinks twice at a rate of 60 Hz to indicate that the MCU has the program loaded to test the automatic bypass transition mode of the TSP62730. Passed
Table Hardware Integration Test (continued) Hardware Integration Test Step Procedure Expected Results Observations 8. Measure the supply voltage to the MCU Supply voltage to the MCU reads about 2.1 volts. Passed 9. Press button 1 of the MCU. Monitor the supply voltage to the MCU throughout the duration of the LED being on. The LED comes on and stays on. The supply voltage to the MCU is about 2.1 volts until the battery reached about 2.2 volts. At this point the TSP62730 switches to automatic bypass mode and the voltage supplied to the MCU is about the same as the battery voltage. Passed 10. Connect the micro USB to the charging port. Charging LED comes on and the MCU enters bypass mode again. Passed 11. Measure the MCU supply voltage. Voltage supplied to the MCU is about 2.1 V Passed 12. Press button 1 of the MCU The LED turns off and the MCU enters the section of the test to test battery charging. Passed 13. Let the battery charge for about 30 minutes. The battery voltage increases from 2.1 to above 3 volts Passed
Table Phone Application Test Phone application test Step Procedure Expected Results Observations 1. On the host phone, turn off the Bluetooth. Phone Bluetooth is disabled. Passed 2. Open the EverythingFinder application. Pop up message appears on the phone application “Turning on Bluetooth.” Passed 3. Ensure the phone’s Bluetooth is enabled. Phone Bluetooth enabled. Passed 4. Click “Register new tracker”. Applications shows the available Bluetooth devices within range. Passed 5. Select cancel. Available Bluetooth window closes. Application bring the user to the main page where there is one mock tracker listed. Passed 6. Verify mock tracker has a grey indication for battery health indication. Battery health indicator is grey due to tracker not being within range. Passed 6. Select “Edit” on the mock tracker. The “Edit Tracker Settings” page appears with the field of tracker name, an unregister tracker, and drop down menu for Indication type. Passed 7. Select the indication drop down menu. “Visual, audio, both” are listed. Passed 8. Select to change the indication type to both. “Unable to change the indication type at this time, the tracker is out of Passed
to the home page and Tracker 1 appears on this page. Table System Integration Test(continued) System Integration Test Step Procedure Expected Results Observations 5. Verify the battery status for Tracker 1 is green. Battery indicator shows green for Tracker 1 in the application. Passed 6. Remove the battery from Tracker 1. Battery status becomes grey for unknown. Passed 7. On the application, select the tracker 1 find me button. The application shows “Tracker is not within range. The map will show the last location where the item was within range” message. A map appears with a marker indicating the last position the trackers was successfully communicated with. Passed 8. Install the battery back into tracker 1. Battery indicator shows green for Tracker 1 in the application. Passed 9. On the application, select the tracker 1 find me button. The application displays message “Finding tracker 1”. Tracker1’s buzzer begins to ring and the LED flashes. Passed 10. On Tracker1, press button. Tracker 1 stops the ringing and the blinking of the LED Passed
11. On Tracker1, press the button to find the cell phone. The cell phone begins to ring. Passed 12. On the application, select the ok button to silence the alarm The cell phone alarm seizes. Passed Table System Integration Test (continued) System Integration Test Step Procedure Expected Results Observations 13. Set the cell phone to silence mode. The cell phone is now in silence mode. Passed 14 On Tracker1, press the button to find the cell phone. The cell phone begins to ring. Passed 15. On the application, select the ok button to silence the alarm The cell phone alarm seizes. Passed 16. Replace the battery for tracker1, with a battery that has a voltage value of 2.5 volts or less. Tracker1’s battery status on the application now shows yellow or red. Passed 17. At the bottom of the application, select the “Register button” Application takes the user to the discovery page for initial registration. Passed 18. Select tracker2 from the discovery list. “Would you like to add this tracker?” message appear. Select Yes. Application adds tracker to the list and sends the user to the properties page. Passed 19. In the property page, name the tracker “Tracker 2”, and for indication type select The application connects to the tracker and saves Tracker 2 to Passed
Appendix B - Copyright Permissions Section B.1 - Zits Comic by Scott and Borgman “Greetings Jerry and Jim, I'm Tim Aries, an Electrical Engineering student at the University of Central Florida. Currently, I am in my final two semesters and I am working with a group on a building a senior design project called the EverythingFinder. Once completed it will allow users to track their belongings with an app on their phone. Part of this project is a 120 page technical documentation. I was wondering if it would be possible have your permission to use a Zits comic to illustrate a point in our presentation. We would greatly appreciate it! Thank you, Tim” “Hi Tim, Thanks for asking. All Zits permissions requests are handled by our agent Scott Olsen at Reed Brennan Media Associates. Please contact Scott at: Scott Olsen Reed Brennan Media Associates 628 Virginia Drive Orlando, FL 32803 800/708-7311 solsen@hearstsc.com Thanks, Jim and Jerry” “Dear Scott, I was referred to you by James Borgman. I'm Tim Aries, an Electrical Engineering student at the University of Central Florida. Currently, I am in my final two semesters before graduating. I am working with a group on a building a senior design project called the EverythingFinder. Once completed it will allow users to track their belongings with an app on their phone. Part of this project is a 120 page technical documentation and presentation. We were wondering if it would be possible have your permission to use a Zits comic to illustrate a point in our presentation. Our professor will not allow us to use any media without written consent. We would greatly appreciate your help! The comic is attached to this email for reference. Thank you, Tim Aries” “Hi Edmund/Tim,