Tracker Software findMe Decision Making Flow Chart Figure 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 tracker application. EverythingFinder’s Tracker Use Case Diagram Figure The tracker application will be attempt to increase battery life EverythingFinder’s 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
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
FinalDraftSD2-Rev1.docx