Physiscs-QA462

Physiscs-QA462 Online Services

 

Chapter 1

 

Introduction

 

Most of the rechargeable batteries drain away quickly after some number of recharge cycles. There is a need for the user to know whether his/her battery has sufficient capacity to perform to the required expectation. Rechargeable battery Tester analyzes the battery capacity and let know the user the condition of the battery.
 
We analyze the voltage and load current attached to the battery test unit and determine the capacity (Ah) of the battery. Based on this capacity, we evaluate the condition of the battery. Some of the required properties that are needed for this process are [1]

  • Battery voltage(volts)
  • Load current(Ampere)
  • Maximum capacity of battery(Ah)
  • Battery internal impedance(Ohms)
  • Maximum discharge current(Ampere)

System may include modules like

  • System power supply
  • Battery discharge unit
  • Logical processor and Analyzer
  • Display unit

 

Current Procedures
 

  • Multi meter

For a quick check, we can use multi meters which gives the voltage reading of the battery. But it cannot display the capacity of the battery.

  • Manual process

By calculating the capacity of the battery manually. First we need to charge the battery and then after noting down the readings we need to discharge the battery. By some calculations we arrive at the capacity of the battery

  • Battery Capacity Testers

These are ready made products available in the market which gives the capacity of the battery in mAh. These often come with charging modules for charging batteries. These products can test the battery while it is in service.

 

Limitations of Current Designs or Technology
 

The limitations for this system
 

  • Confined to the daily usage batteries having low capacity, not the industrial batteries.
  • Regarding the current that the battery can safely discharge and the time constraints regarding overall execution of the system.

 

Similarities and differences between your concept and existing technologies
 
The existing modules gives the battery parameters like voltage, current but cannot comment on whether the battery is good to use or not
 
Similarities

  • Voltage indication
  • Load Current indication

Differences

  • Capacity Testing
  • Rating a battery based on its capacity

 

Existing or patented technologies that may be relevant to your design? If so, what are they and why are they relevant

 

There are many ways by which we can estimate life of battery. All of them are helpful in better understanding of problem and help us in setting the right process so as to arrive at our goal
 

  • AccuPower IQ-328 Battery Charger Analyzer Tester[3]
  • La Crosse Technology BC-700[4]

 

Chapter 2

 

Team Chartering Document

 

Chartering body Sponsor (Instructor) Team Leader Mentor Team Kickoff Date:  
OC Systems Design Professor Steve Maher Avantika Keverala Professor Bell January 25, 2018  
 
Mission Statement: To test the capacity of a rechargeable battery and determine its longevity.
High Level Objective(s): 1. Analyzing charging and discharging cycles of RC battery

2. Developing a module to quickly charge and discharge a RC battery and collect data.

3. Module to analyze the collected data and comment on the longevity of the battery.
Problem Statement(s):  Testing the condition of a RC battery whether it can hold charge for sufficient time or not.
Business Priority:

 

 

 This project can be useful to organizations where quick RC battery tests are required to know the condition of battery.
Scope:

 

 

 The team will be working on a rechargeable battery tester which can determine the capacity of the rechargeable battery. This helps in evaluating the battery life. Our goal do not include determining percentage of the charge left.
Team Members: 1. Avantika Keverala (EEE)

2. Ashok Kanjarla (EEE)

3. Srikanth Gonuguntla (ECE)

 
Team Expectations/ Deliverables: 1. Analyzing different batteries and studying properties of RC batteries. – January 2018
 
2. Module for collecting data from battery while charging and discharging.- February 2018
  
3. Module for controlled discharging of battery. –  February 2018

4. Module for analyzing the collected charging and discharging curves – February 2018
 
5. Integration of project – February 2018
Team Ratification Required For: Team Charter must be approved by mentor.
Team Review

Schedule:

 1. Team will review progress with mentor weekly.
 
2. Team will give progress reports to the systems class and faculty every two weeks.

 
Sunset Clause: End of semester

 

Chapter 3

 

Project and Concept Overview

 

Customer Needs and Analysis

 

  • The whole equipment should be on a bench
  • The system can have external power supply and perhaps external load

    •  

  • The system can have a charged battery
  • The system may use an external battery as power source

    •  

  • The system should start the process at the hit of a button
  • The system should determine whether the testing RC battery is “good” or “bad”

    •  

  • The system gives rating for testing battery from 0-10 which describes it’s charge holding capacity
  • The desirable or expected time for completion of whole process is less than or equal to a minute.

 

Overview of the QFD work (House of Quality)

 

Functional Requirements

 

 

Functional Decomposition

 

 

Chapter 4

 

Concept Generation
 

Sub-system Concept 1 Concept 1-2
Manual Process Calculation of battery capacity by discharging battery using a load whose discharge current is known Requires a load and measuring equipment
Using discharge curve analysis Analysis of discharge curves of test battery against an ideal discharge curve at given load Requires load for discharging battery and programmed logical unit for data collection

 

Morphological Table

 

User Discharge Method Control sequence Processing results Display
Battery testers Resistor Manual Manual processing LED display
students Robot Arduino Arduino Laptop (windows)
Technicians LED’s Microprocessor Program on a computer(MS. Excel)  
  Load with constant discharge current      

 

Chapter 5

 
Concept Selection

 

Chapter 6

 

System Architecture

 

 

Other Considerations

 

Research Reports and Presentations

 

In this section, include the Research Reports and Presentations done by each of the team members.

 

Introduction

This introduction should provide sufficient information to allow the reader to understand your vision, mission, and project.  This is an introduction to your design effort.  Unlike the Executive Summary, which serves to summarize your report, the Introduction serves to motivate the report.  It should make clear to the reader why your design project is being pursued and what is expected to be the outcome. This should be written at the beginning.

 

Team Charter

 

Place your Team Charter here as a stand-alone document.

 

Project and Concept Overview

 

It is appropriate and necessary to start with an overview of the project.  Start with a paragraph giving an overview of the approach and contents of this section.  Sections that are recommended (speak with your mentor for the specifics of your project):

 

  • Customer and Needs Analysis
  • Overview of the QFD work (House of Quality)
  • Functional Requirements
  • Design specifications with targets
  • Context Diagram
  • Functional decomposition
  • Utilize appendices as appropriate to include supporting figures and graphs.

 

This section should then present the Customer and Needs Analysis and the Quality Functional Deployment (QFD).  The QFD should summarize the sections of the House of Quality (HOQ) in a concise manner.  All requirements (specifications) for the design should be clearly stated with target values noted for each.  After this section, the reader should have no questions about what a successful design will accomplish.

 

This section should present the Functional Decomposition.  A graphical representation is likely best.  Use multiple diagrams if all the functions of your system can not readily be presented in one diagram.  Each function necessary to reach the design specifications and targets needs to be described in this section.  This section should make it clear how your system is to behave functionally.

 

 
Concept Generation
 

This section should present all the potential concepts you generated for your design.  It is understood that many concepts were likely created, but each needs to be described.  As such, you should strive to provide a concise description of each at a level of detail only sufficient to distinguish concepts.  Use graphical representations heavily in this section.  A picture of a potential concept tells much more than a few words.

 

One effective method for presenting your concepts would be to first show the “big picture” by providing an overview of all the concepts considered for each subsystem.  A concept table or a morphological table is one approach (among many) that might look something like the following…

 

(Note: in actual document, do not show a split table; make sure the entire table appears together)

 

A very brief word description of each concept would be used in this table.  Subsections would then be added to the text to discuss each of the concepts to an appropriate level of detail.  This section should make it completely clear to the reader what ideas will be considered during concept selection.

 

Concept Selection

 

This section should present the methodology used to narrow your design options.  Absolutely no ambiguity should remain concerning the selected concept.  All decision matrices should be presented with clear justification of criteria and weighting utilized.  Both subsystem and system matrices are appropriate.  No “selection” should be presented that can not be justified in some way.

 

System Architecture
 

This section should summarize your selected concept and communicate exactly what you intend to build.  Describe each selected subsystem that comprises the design and provide drawings (sketches) of the entire system level architecture. It should concisely and completely describe the system level design showing how each selected sub-system contributes to the final system concept.  This should be done in a combination of words and pictures.  A system level block diagram is typically very useful.  Upon reading this section, an individual should fully understand the system you are designing (enough to completely describe it him or herself).

 

Detailed Design Analysis
 

Several subsections, collectively discussing the detailed design of all subsystem within the selected concept, should be included.  This section will likely be longer than most of the other sections in the report as it must provide sufficient detail for the reader to assess the validity of the design.  Use appendices when you need to include long calculations or large figures and/or tables.  Be certain to reference the appendices from the text.

 

Other Considerations
 

This section should assess your completed design as to how it addresses and satisfies the other considerations, or “non-technical” factors.  Examine how analyses of the other considerations were incorporated into the design, then how the design is expected to impact those areas.  If the consideration is not particularly relevant to the design, then explain that rationale.  If relevant, explain how that impacted the design process for the project.  Explain how solutions to issues or trade-offs incorporated into the design made the results better or worse.

 

Research Reports and Presentations

 

In this section, include the Research Reports and Presentations done by each of the team members.

 

Design Confidence Assessment

This section should assess your confidence in the selected design satisfying the target specifications.  On a subsystem by subsystem basis, discuss if the selected concept will clearly satisfy all functional requirements noted prior in the report.  This discussion should be backed up with evidence either from a reference or from the detailed design analysis.  If a selected concept poses significant risk, detail how the risk will be managed and provide potential design contingencies.  Also assess your confidence that, given success in the design of each subsystem, the components will integrate to form a fully functional system.  You are strongly encouraged to use belief maps within this section.

 
Product code: Physiscs-QA462

 
Looking for best Physiscs-QA462 online ,please click here
 

Summary