1. ECE 477 Design Review Team 8  Spring 2007
Ryan Schroeder - Team leader - Systems
Dave Canada – Software
Tom Germon – PCB/Packaging
Jay Doyle – Web Interface
Jay Dave Tom Ryan

2. Outline Project overview Project-specific success criteria
Block diagram
Component selection rationale
Packaging design
Schematic and theory of operation
PCB layout
Software design/development status
Project completion timeline
Questions / discussion
In the following presentation, I will give a general summary of the project, including the project specific success criteria.
Dave will continue with an overview of the block diagram and discuss our component selection rationale and finish up with the packaging design.
Ryan will take over and give a summary of the schematic and theory of operation.
Tom will provide an overview of the PCB layout
And I will wrap it up with an overview of the software and our completion timeline.
Please hold your questions until the end.

3. Project Overview Compatible with multiple technologies
NiCad, NiMH, Li-Ion and Lead Acid
Interface with a wide variety of battery sizes
Each size will have its own attachment
Track individual battery statistics
Interface via an LCD panel and pushbuttons
Report statistics through an onboard website
Charge duration, voltage, total charges...
The BatteryMax team is building a universal battery charger. In order to make it truly universal, it must be able to charge a variety of battery technologies as well as various shapes and sizes. The BatteryMax will also be smart. It will be able to track individual battery statistics, such as total energy, charge time, last charge date.
The user will be able to control the BatteryMax using a series of pushbuttons with feedback being provided on an LCD display.
The pushbutton/LCD is limited, therefore statistics and some settings will be able to be controlled through the onboard website.

4. Project-Specific Success Criteria
A Universal Battery Charger must:
Recharge Multiple Battery Technologies.
Communicate with an LCD Display.
Have an HTTP Server and Webpage.
Perform Basic Battery Testing.
Track Individual Battery Statistics.
In order to ensure that the BatteryMax works, we have outlined certain criteria that we must meet for this project to be considered a success.
To make it universal, it must be compatible with the various battery technologies.
The user must be able to interact with it, using an LCD display and a webpage.
And it must relay information back to the user in the form of battery testing and statistics.
Now Dave will give you a general overview of the block diagram

5. Software Design Status
Software flow has been designed.
Major components have been pseudo coded.
NE64 TCP/IP stack has been examined.
Peripherals examined (SCI, SPI, I2C, ATD)
Demonstrational microcontroller web page
Battery voltage and current graphing script
The general software flow has been determined. We know what we need to do and have a good idea about how to do it.
The major software components have been outlined and some have been pseudo coded.
We will be using the provided NE64 TCP/IP stack to host the webpage.
We have determined how each external device will integrate with the microcontroller.
We have a demonstrational version of the webpage as an outline to what we expect the final webpage to be.
A graphing script to relay battery statistics has been written.

6. Software Blocks These are our major design blocks.
On reset, the microcontroller will go into an initialization phase. Here the display will be blanked and loaded with the BatteryMax logo. The digital potentiometers will be set to put the smallest voltage possible through the charging circuit and the relay switch will be disengaged. Any setup that the web server needs will be handled here.
The rest is an infinite polling loop. The microcontroller will check the web server, the pushbuttons and the battery and make changes accordingly.
If there is a HTTP request, the microcontroller will service that request in the Serve Data routine.
If any of the pushbuttons are pressed, the switch algorithm block will handle it and update the display if necessary.
The microcontroller will also check the battery parameters if there is a battery charging and go into the switch algorithm routine if any of the battery parameters are out of spec.

7. Main Loop Flowchart
After setup, the main routine will enter into an infinite loop.
The first thing to be checked will be the web server. If there is a requested file, it will be sent.
Next it will check the pushbuttons, if they are pressed the handler will be called.
The microcontroller will then tell the A to D converter to perform a conversion on ports 0, 1, and 2.
The LCD will be updated as necessary.
If there is a battery, then it will check the battery parameters read in by the A to D converter and if they are out of line make adjustments.
The flow then loops back to checking the HTTP requests.

8. Microcontroller Website
Our sample web page has two main areas: Battery Statistics and BatteryMax Settings.
On the statistics page, the user will select the specific battery he/she wants statistics for, then the statistics will be presented, along with a graph of the last charge.
The settings page will contain some simple user preferences.

9. Project Completion Timeline
Our project completion timeline is broken up into hard deliverables and soft deliverables. The hard deliverables correspond to tangible objects, the physical items that must be completed. The soft deliverables are the documentation and presentations due at the end of the semester.
The PCB will not be returned until week 11, which prevents us from doing much of the physical assembly and testing until later in the semester.
It should be noted that the requirements here are for final products, not the prototype.

10. Questions / Discussion

11. Homeworks http://cobweb.ecn.purdue.edu/~477grp8/documents/hw01.doc

12. Data Sheets
NE64 microcontroller
NE64 TCP/IP stack
ACS LCD Display
Digital Potentiometer
Linear Regulator
Temperature Sensor
1Mb EEPROM