Team 14
This presentation is the property of its rightful owner.
Sponsored Links
1 / 29

Diffusion Furnace Controller Design PowerPoint PPT Presentation


  • 39 Views
  • Uploaded on
  • Presentation posted in: General

Team 14 Joe Grady James Crow Hongyu Chen Prakalp Sudhakar Victor Villagomez Client/Faculty Advisor: Dr. Gary Tuttle. Diffusion Furnace Controller Design .

Download Presentation

Diffusion Furnace Controller Design

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Diffusion furnace controller design

Team 14

Joe Grady

James Crow

Hongyu Chen

PrakalpSudhakar

Victor Villagomez

Client/Faculty Advisor: Dr. Gary Tuttle

Diffusion Furnace Controller Design


Problem statement

The objective of the senior design project is to design a new set of temperature controllers to use on a set of diffusion furnaces located at the Microelectronics Research Center.

The project goals include:

Temperature calibration of the furnaces

Implementing of new temperature controllers into the current furnace system

Providing a computer interface so that temperature of the furnaces can be controlled and monitored remotely.

Problem Statement


System overview

System Overview


Functional requirements

  • Controller must have a temperature tolerance within +/- 1 degree Celsius

  • Controller must be digital and programmable (∆T/ ∆t)

  • Controller must have communication capability

  • Controller must be able to sample and store information for every cycle

  • Controller must be able to control temperatures independently of each section

Functional Requirements


Functional requirements1

  • Software must be able to monitor and control the parameters of the temperature controller

  • Software must be able to support simultaneous use by multiple students

  • Software must be able to display graphs of the process

  • Software needs to be accessed online via web browser

  • Graphical interface of the software must be user-friendly

  • Error checking and deviation

Functional Requirements


Non functional requirements

  • The new controllers need to be placed where the old ones were so they need to able to fit within a certain space

  • Connectors must be compatible with the new controller

  • All the schematics and layout designs need to be of industry standards for future reference.

Non-functional Requirements


Risks and mitigations

  • Group might possibly lose members

  • No way to verify that the wafer is placed in the correct oven

  • The amount of inputs on the CN616 controller will not allow us to use all of thermocouples used in the current set-up.

Risks and Mitigations


Budget

Total Expected Expenses

Current Expenses

Budget


Schedule 1 st semester

Schedule – 1st Semester


Software architecture

Software Architecture


Software architecture sequence diagram

Software Architecture – Sequence Diagram


Software architecture use cases

Software Architecture – Use Cases


Software overview

Software Overview


User interface

All text field have a acceptable range

User Interface


Software test plan

Simulation

  • CubicTestTools

    • A graphical Eclipse plug-in

    • For writing Selenium and Watir tests.

  • Catus

    • A simple framework for unit testing server-side code.

    • It use JUnits and extends it.

  • JMeter

    • A full multithreading framework allows concurrent sampling.

    • GUI interface for user friendly.

Software Test Plan


Software test plan1

What to test

  • Website Application Module (user side)

  • Internet Server Module (between the server and the website)

  • Communication Module (between server and controller)

Metrics & Hypothesis

  • Assume all hardware are working correctly

  • Test extreme cases --- like negative values and value out of range

  • Match corresponding protocols to the parameters

Software Test Plan


Prototype implementation of serial communication

  • Baud Rate = 4800

  • Data Bits = 8

  • Parity = N

  • Stop = 1

  • Operating Protocol

  • Controllers do not initiate communication, Command Module does.

  • All communication is in ASCII format

  • To start communication Command Module sends alert code followed by ID

Prototype Implementation of Serial Communication


Schematic old controller

Schematic – Old Controller


Hardware interface issues

  • SCR data sheets are unavailable and we are required to create test to determine the characteristics of the SCR.

  • To control the SCR pairs we will need an op-amp interface circuit between the CN616 controller and the SCR’s gates.

Hardware Interface Issues


Thermocouple interfacing

Thermocouple interfacing


Rs 232 interfacing

RS-232 INTERFACING


Prototype scr interfacing

Omega CN616 – 1 output

SCR Pair

Prototype SCR Interfacing


Hardware test plan

  • Isolate a single SCR for characteristic testing to get its turn-on gate voltage

  • Use this information to help interface the CN616 controller to the SCR circuit

  • Test a single furnace with both a single thermocouple and the SCR circuit connected to the controller. Using a thermometer to compare controller measured temperature and actual temperature.

Hardware Test Plan


Hardware test plan1

  • Thermocouple

    • Connect the master thermocouple pair (J2) to the CN616 controller input (Z2).

    • Check that the 120VAC line voltage is properly connected to the CN616 controller, if so power it on.

    • Once the CN616 is powered on set the controller’s 4th digit in the 4 digit model code to 6 as shown in Figure 4-2 below. This will correspond to an S-type thermocouple.

  • Figure 4-2, Function Setting

    • Connect a multi-meter with the red lead connected to the thermocouples red wire and the black lead to ground to verify that the voltages are between 0-40mV.

Hardware Test Plan


Hardware test plan2

  • SCR

  • Connect the center SCR gates to the op-amp circuits output’s and then connect the op-amp circuit’s input to the CN616 controller output (Z2)

  • Check that both the master thermocouple pair (J2) is connected to the CN616 controller input (Z2) and that the 120VAC line voltage is properly connected to the CN616 controller, if so power it on.

  • Use CN616 manual, pages 33-34 to set the temperature to 1000° Celsius at a ramp up time of 20 minutes.

  • Connect a multi-meter in series with the output of the CN616 and the op-amp circuit input to verify that the current does not exceed 10mA.

Hardware Test Plan


Current project status

  • Thermocouple, AC line power, RS 232 have been all successfully interfaced and verified compatible.

  • The tests have been developed for creating the SCR characteristics.

  • The Op-amp interface circuit between the CN616 controller output and the input to the SCR gate has been designed and is in the process of being debugged.

  • The software design module is setup.

  • The core test cases have been written, there is need for more test cases.

  • The controller can already be tested for communication

Current project status


Schedule 2 nd semester

Schedule – 2nd Semester


Resources

Professor

  • Thorough knowledge about current microcontrollers, and advice for digital microcontrollers

  • User Manuals

  • Manual for current analog microcontrollers

  • Manual for new digital microcontroller.

  • Manufacturers

  • Websites to purchase new digital microcontrollers

    • Omega.com – New microcontroller

    • Easysw.com – Serial Programming Guide

Resources


Questions

Questions ?


  • Login