Table of Contents Executive Summary 2

Prototyping and Testing 4.1 Build and implementation Strategy

Download 471.88 Kb. Page 15/17 Date 31.07.2017 Size 471.88 Kb. #25812

Navigate this page:

• 4.1.2 Coach Application
• 4.1.3 Fan Application

4.0 Prototyping and Testing 4.1 Build and implementation Strategy 4.1.1 Umpire Indicator After completing the research and design phases of this Senior Design Project, the group will begin to order all of the necessary parts to complete this design. Upon receiving the ordered parts assembly can begin. The first step taken to assembling all the necessary components will be to assemble the parts of the design that can be tested individually and not as a whole assembled piece. The first part to be assembled in this fashion will be the LED displays. These displays and the controllers for them can be fully tested for functionality apart from the microcontroller. Once the three screen controller and 7 segment display assemblies are complete they can be set aside waiting to be connected with the microcontroller. The microcontroller will be the next component to be set up. For many in the group this project is the first main interaction with coding and building things at the microcontroller level. The group would like to load basic functions and tasks to the microcontroller to test the understanding of how it works and test that it is fully functional. When the microcontroller is being tested and programmed all by itself is when it is best to find shortcomings in the design plan or programming rather than upon full assembly of the device. After the group is confident with their understanding of the microcontroller, the program for the umpire indicator will be loaded onto the chip. The low battery monitoring circuit next needs to be assembled. This circuit needs to be tested for working properly and after completing the check can wait to be added to the main circuit board. The next step to completing the building of the umpire device will be to connect the pushbuttons to the microcontroller. After the push buttons have been added to the microcontroller the functions of those buttons can be tested. After that test phase has been marked complete the low battery circuits and LEDs can be added to the build. At this stage in the build the displays can be hooked to the microcontroller for testing of all functions of the device short of wireless transmission of the data. The last step to assembling the PCB is to add the Bluetooth chipset to the microcontroller and test to see that the Bluetooth chip is transmitting. At this point in the build the group will have a fully assembled PCB. The next step is to properly mark on the enclosure where the buttons and displays need to be cut out and to carefully cut those holes in the plastic top piece. The buttons and screens also need to be properly labeled by etching or sticker of some kind to aid in the use of the device. After properly prepping the case for the assembled PCB it can be installed into the case and the building of the handheld umpire device is complete. At this point the device will be fully tested in its complete form with all other aspects of this Senior Design Project. 4.1.2 Coach Application: All development for the coach application will be done on a Windows 7 computer through the Eclipse IDE described in section 2.4 Android development. The android project will created by using the downloadable ADT plugin’s automatic Project creation features, which extends to all XML and class files that will additionally be needed in the development of the coach application. All class files will be implemented as indicated in section 3.3.2 Classes in the class diagrams. All classes and methods will follow the framework of the Android API so as to ensure the elimination of any bugs that may result from the use of incompatible Java libraries that may not work within the Android framework. The intended tablet device for the development of this coach application is the Archos 101 internet table, a multimedia tablet device that runs on the Android 2.2 Froyo framework, which can be seen in 4.1.2 Figure 1 below. The device has a high resolution capacitive touch screen with a resolution of 1024x600 pixels (which can additionally be set on the ADT emulator for code testing prior to the acquisition of the tablet device). Additionally, the device features both WiFi (802.11 b/g/n) and Bluetooth 2.1 connection capabilities, both of which being required for unit testing of the coach application. The device also features a both front and back facing cameras (allow for the immediate acquisition and application of player photos in the Pre-Game manager interface) and a rechargeable battery rated to last for over 10 hours of internet browsing, which is more than satisfactory for the implementation of this system. The price of the device is very reasonable at $299.99 MSRP, which is half of comparable devices such as the apple iPad and the Sansung Galaxy tab. Due to the economic price of the device, two can be acquired, allowing simultaneous testing of 2 devices communicating with each other, as would be occurring within the actual ball field. 4.1.2 Figure 1: The Archos internet tablet that will be used in the development and testing of the coach application. 4.1.3 Fan Application All development for the fan application will be done on a Windows 7 computer through the Eclipse IDE described in section 2.4 Android development. The android project will created by using the downloadable ADT plugin’s automatic Project creation features, which extends to all XML and class files that will additionally be needed in the development of the coach application. All class files will be implemented as indicated in section 3.3 Fan Application in the class diagrams. All classes and methods will follow the descriptions given in section 3.3.2 Classes, and follow the framework of the Android API so as to ensure the elimination of any bugs that may result from the use of incompatible Java libraries that may not work within the Android framework. The prototype will be just like the final design, incorporating all elements of the fan application. It will be an executable APK file that will install on the Motorola Droid 2 phone (Shown below in 4.1.3 Figure 1) that was chosen for the prototype build. The Droid 2 is a smart phone produced by Motorola for Verizon’s cell phone network that runs on Android’s 2.2 Froyo operating system. The device has a 3.7-in., FWVGA (480 x 854) screen which is one of the native screen sizes for the ADK software emulator. Additionally, the device features internet connectivity through Verizon’s CDMA network, allowing the testing of the application from anywhere within range of Verizon cell towers. Finally, the device also features a 1400 mAh Li Ion battery that claims over 10 hours of continuous usage time, which is more than sufficient for the prototype build of this application. 4.1.3 Figure 1: A picture of the Motorola Droid 2’s touch screen interface running Android’s 2.2 Froyo operating system. The prototype will be used to test the integrity of the application, its connection with the database, and its speed sending and receiving from the database. The prototype build will run on any other device that uses Android’s 2.2 Froyo operating system, so additional devices maybe be briefly tested to ensure cross compatibility of the fan application. Directory: seniordesign -> fa2010sp2011 seniordesign -> Hvac control and Feedback System 0 Group 2 Steve Jones Mathew Arcuri Elroy Ashtian, Jr seniordesign -> Group 5 Spr-Sum 2011 seniordesign -> Senior Design II paper seniordesign -> Remote Touchscreen-Controlled Defense Turret Senior Design Documentation Courtney Mann, Brad Clymer, Szu-yu Huang Group 11 seniordesign -> Flight Performance Data Logging System seniordesign -> Amphibious vehicle seniordesign -> T-100 Watch Dog (Autonomous Security Vehicle) seniordesign -> Ehvac: Wireless Modular Multi-Zone hvac controller Group b javier Arias Ryan Kastovich Genaro Moore Michael Trampler Download 471.88 Kb. Share with your friends: