Controlling the signal light tower based on the
status of the machine. Getting the remote commands through the host. Developing
configurable lights and other controls.
Porting of a software from DOS to VxWorks, User
Interface Design and Software Testing tools for XVME based multiplexer cards for a Semiconductor Equipment
Manufacturer.
Real time process control software development for
following activities,
Data collection
Recipe management
Maintenance and diagnostics.
Endpoint detection algorithms.
MPI is involved in complete equipment control
software design for Dambar and Trim/Form equipment. It involves systems
requirement analysis, design, coding , testing and implementation. This also
involves integrating other components into the system like machine vision,
quality control monitor, and material tracking (bar code interface).
Using MFC
and SDK created a wafer map display application for a Die Sort equipment. This
project involved
·
Display
the wafer map and its header information
·
Edit
the wafer map
·
Change
of bin code
·
Selection
of color code for respective bin code
Automated Guide Vehicle (AGV) Interface software for an automation project
of a leading etching equipment manufacturer.
Epitaxial reactor software for motion control and
gas flow control. This project involved
menu oriented GUI and SECS-II communication protocol.
Design and
development of SECS-II communication protocol streams/functions (Standard &
Custom). User Interface design,
Conformance testing, Monitoring and Control of digital and analog I/Os,
position, temperature, flow and pressure.
Implement SECS/GEM under windows environment with
functionality for Data Collection, Alarm and Event Handling, Recipe Management,
Spooling and Limits Monitoring
Implement SECS/GEM under windows environment with
functionality for:
- Data Collection
- Alarm and Event Handling
- Recipe Management
- Spooling and limits monitoring
The existing software was changed to accommodate
following features as per the End User’s requirements,
1.
Custom
SECS II messages.
2.
Advanced
Wafer Processing.
3.
Modified
Alarms and Events.
4.
Modification
of remote command.
5.
Modification
of operator screen.
·
Testing
of GPIB interface.
·
Enet
and SCSI-A interface were tested with Integrator 2.1 and 1220 prober.
·
Writing
prober driver for 19S prober.
19S prober is similar to
1007 prober but it supports only downloading of prober setup file name. The prober, then uploads the setup form
local disk and then carries the further initialization.The implementation required
two classes, a prober driver class and a prober initiator class for carrying the initialization of driver class.
All the prober specific things are
encapsulated in these two classes. These two classes were implemented and tested with Integrator 2.1.
·
Testing
of Ink Die Inspection(IDI) and Ink Die Count(IDC) on 12xx prober.
·
The
IDI/IDC were tested with Integrator 2.1
·
Implementation
of First Die Integrity(FDI) on 12xx prober.
In normal operation of probing and testing of wafer,
operator has to choose the reference die. This die is used to finalize the
wafer geometry. It is possible that operator may choose different die in
subsequent passes, thereby wrong dies may get inked. This problem can be
eliminated with the help of FDI, i.e. by storing the information of first die
coordinates. The implementation of FDI is carried-out by tracking wafer
specific parameters and deciding the exact reference die.
The objective of this project is to develop an
on-line material tracking system which eliminates the paper travelers in a
waferfab. Each proceesing tool is connected to a station controller (MSC) which
talks to a UNIX Server via TCP/IP connection. Material arrival/departure
information is collected and sent to server by MSC. Server end runs a daemon
process that forms the business rules of the system receives all these messages
and validates against an MES system and local Oracle database. Project involved Data Modeling, Schema
Design, Project Specifications development, Scheduling, ODBC connection,
connectivity of Client and Server.
This project involved validation of GEM all the
capabilities those are implemented on the wafer inspection equipment. The
validation procedure involved testing of each SECS II message and GEM
capability considering various test cases for every single event, variable and
alarm.
This project involved review of technical
specifications customer has decided to implement for their new line of Burn-In-Test systems. Customer is planning
to implement GEM/HSMS interface for the Host communication interface. MPI
suggested customer various GEM capabilities that should be implemented.
This project was for one of the leading
semiconductor equipment manufacturer. It involved modification, revision and
addition of more information to the
existing GEM document. The project
involved technical inputs related to
fundamental GEM requirements, associated Streams and Functions, and their
description.
The equipment manufacturer provides GEM interface as
an option. The add-on nature of the GEM interface required a modification in
physical connection, hardware and software setup. MPI out lined a section that
describes this setup.
TCP/IP, Ethernet based Distributed System design and
implementation using Remote Procedure Call.
Diagnostic software for testing PCMCIA-Flash memory
card for a leading IC manufacturer in the Bay Area.
Implementation and porting of SECS II messages under TCP/IP protocol. The
TCP/IP was implemented as a resident part of the kernel for the customized
real-time operating system being used by the client. TCP/IP protocol using
3COM-509 communication board for a SMIF based Robotic equipment serves more
than 3 servers.
The Micro Station Controller software is an
application software that provides pseudo multi-tasking under the DOS
environment. The software was split
into distinct blocks to make handling
and maintenance easier. Also the interdependencies between the blocks were
removed. The only link between the individual modules was through intertask
messages and through variables passed as parameters in functions. Some of the
functions accessed by more than one module were placed in a common utility
module. Global variables were taken care by creating a data-base from which the
value could be read/written.