THE UNIVERSITY OF TEXAS AT SAN ANTONIO

PROJECT PROPOSAL AUTOMATED VOLUME DETECTION AND FLUID

DISPENSING SYSTEM

SUBMITTED BY:

TEAM #2

BRENDAN BAKER FREDERICK WEISSBACH

SEAN TOVAR

SUBMITTED TO:

PROFESSOR AUGUST ALLO

THE UNIVERSITY OF TEXAS AT SAN ANTONIO 6900 N. LOOP 1604 WEST

SAN ANTONIO, TEXAS 78249

DECEMBER 8, 2009

2

Table of Contents

Table of Figures ..........................................................................................................................3

1. 0 Need for Design ...............................................................................................................4

2.0 Background Summary/Introduction .................................................................................5

3. 0 Objectives ........................................................................................................................5

3.1 Data Acquisition ...................................................................................................................... 6

3.2 Data Analysis and Line Detection............................................................................................. 6

3.3 Volume Calculation ................................................................................................................. 6

3.4 Fluid Flow Rate ....................................................................................................................... 6

3.5 Hardware Development ............................................................................................................ 7

3.6 Integration................................................................................................................................ 7

3.7 Graphical User Interface........................................................................................................... 7

3.8 Prototype ................................................................................................................................. 7

3.9 Internet Access and Data basing ............................................................................................... 7

4.0 Plan ..................................................................................................................................8

4.1 Parts ......................................................................................................................................... 8

4.2 Design ..................................................................................................................................... 9

4.3 Integration............................................................................................................................... 9

4.4 Finalize .................................................................................................................................. 10

5.0 Deliverables ................................................................................................................... 10

6.0 Schedule ......................................................................................................................... 11

7.0 Staffing .......................................................................................................................... 11

7.1 Frederick Weissbach .............................................................................................................. 12

7.2 Brendan Baker ....................................................................................................................... 12

7.3 Sean Tovar ............................................................................................................................. 13

8.0 Equipment and Materials ................................................................................................ 13

9.0 Budget ............................................................................................................................ 13

10.0 Conclusion ..................................................................................................................... 14

Appendix A............................................................................................................................... 15

3

Table of Figures

Figure 1: Functional Block Diagram ...........................................................................................8

Figure 2: Schedule shown with gant chart. ................................................................................11

4

Table of Tables

Table 1: Proposed budget for design ......................................................................................... 12

5

1. 0 Need for Design

Long lines are directly correlated to more time spent waiting for the product at the end of

that line. The beverage dispensing industry is slowly starting to incorporate more technology into

their products, but that technology is making little contribution to this problem. The Automated

Volume Detection and Fluid Dispensing System (AVD&FDS) could not only solve this problem,

but revolutionize the beverage dispensing industry.

2.0 Background Summary/Introduction

The AVD&FDS detects the volume of a given container and will dispense a beverage of

the user’s choice into the container without any input from the user beyond placing the container

in the system. The design process began with a literature search to find any sources relevant to

the AVD&FDS design. Engineering design constraints were then evaluated with health, safety,

and legal issues being among the most important in conjunction with proper engineering codes

and standards. After discussing with the public possible design features so as to have a

marketable product, additional requirements were established to meet those demands. A number

of alternate designs were considered which included the device being employee operated and

detecting a predetermined volume from a barcode embedded on the cup. The final design chosen

will implement a combination of the original design idea and a few key aspects of an alternate

design that involves using a timer for the dispensing valve. Finally, a functional block diagram

was created to map the initial design plan. The design team as a whole has extensive experience

in control system development and implementation that will help in their individual contribution

to the design. Individual tasks will include the development of a Graphical User Interface (GUI),

automatic volume detection, flow control, and the detection of a container for which to fill.

3. 0 Objectives

The objective of the AVD&FDS is to establish a unique convenience towards the

beverage service industry. The system will correctly identify the volume of any cylindrical

drinking apparatus placed within the means of the housing container. Using a collaboration of

new technologies and existing hardware, AVD&FDS will succeed in becoming the first fully

automated volume detection device and one of the most original and advanced beverage

6

dispensing units. To achieve such goals, the design process will draw upon the accomplishments

of separate intermediary stages:

3.1 Data Acquisition

In order to begin processing potential volume, computer recognizable imagery must be

obtained. Using cameras with varying color filters for proper contrast to the target container,

still images will be captured and input into a PC using National Instruments hardware and

software. This data will then undergo an appropriate analysis in MATLAB software.

3.2 Data Analysis and Line Detection

Using MATLAB, the image will be adjusted through a sequence of filtering and

intelligent manipulation to create a clean and robust edge. The code will be derived from a

graduate peer’s thesis on a new method of line detection. A very specific, detailed, and accurate

display of the container’s four edges will create a stable platform for the volume detection.

3.3 Volume Calculation

This step of the process will convert an image of edges into the empty space volume

inside the container. Between the top and bottom edges, the height will be determined. The side

edges will then be integrated from the base to mouth. Depending on desirable resolution, the

length of each interval will be chosen. The resolution will have diminishing returns vs.

processing time, so middle ground will be adjusted during prototyping. Then, in each interval,

the distance between each side edge will be calculated to a stacking set of diameters for the

entire height of the container. The basic equation for volume of a cylinder will be used at each

interval to subsequently create a large stack of cylinders, in which all the volumes will be added

together to find a theoretical volume of free space.

3.4 Fluid Flow Rate

To avoid error due to the varying properties of different fluids, constant flow rates will be

implemented. Through the research of liquids and the testing of valves, flow rates of ounces per

second will be determined.

7

3.5 Hardware Development

During this phase of the design, hardware will be constructed and troubleshot. A pump-

less keg tap, provided by a collaborative mechanical engineering design team, will be altered at

the valve to be controlled electronically. This will provide for a complete hands-free system

with a presumably constant pressure ideal for beverage dispensing. Based on parameters of the

data acquisition equipment, fluid reservoirs, and dispensing equipment, housing plans will be

constructed.

3.6 Integration

After so many specifics are operable and functioning at the appropriate level, integrating

the many working systems together will be the next objective. Integration includes connecting

and timing all peripherals to work in synchronization as shown on the next page in Figure 1.

This working model will be appropriate for demonstration.

3.7 Graphical User Interface

Once the integrated system is in full working order, a GUI will be designed to give the

average consumer the ability to operate the system with very little knowledge. Statistical data

and feedback will be available through the GUI.

3.8 Prototype

The final objective of the design of the AVD&FDS will involve the construction of the

housing structure. This will give the device a self sustaining presence, aesthetics through

concealment of infrastructure, and a rugged professional quality.

3.9 Internet Access and Data basing

Future plans of logging and tracking data of individual users on separate machines will

grow from connecting the device to the internet. Creating accounts accessible through RFID

cards or pass codes will allow tracking of financial activity and user statistics.

8

Figure 1: Functional Block Diagram

4.0 Plan

The plan below is the design process, mapped out in stages, that will be performed in

order for the product to be designed and fabricated in a professional manner. The plan will be

executed as follows: parts, design, integration, and finalize.

4.1 Parts

After the concept of the product has been refined to a feasible future device, hardware

research will take place to find the best parts for the design. The quality of the components that

make up the product will be selected based off of the need and importance that particular part is

assigned within the product. The budget will also play a role in the selection of the different

elements chosen so as to have an affordable final product. Parts needed for this design include a

microcontroller, communication board, machine vision camera, valve, communication cables,

and a few other essential parts for housing the product. The microcontroller will need multiple

I/O to control the valve and timing of the fluid being dispensed based off of an imported file

from MATLAB containing the volume. Machine vision related parts have been provided via the

Robotics and Intelligent Machines Laboratory. The majority of the other needed parts have been

identified and located at an affordable price by in house research and testimonials from other

9

classmates. The few remaining parts are either waiting to be found at a lower price or are already

owned by a group member.

4.2 Design

Once the necessary parts have arrived, the architectural design may initiate. Other

internal design features such as code development, barcode software, and database testing will

have been in motion prior to the arrival of the needed parts in order to confidently stay on

schedule. The code development will entail using edge detection in MATLAB of the picture

obtained through the machine vision camera to find the edges of the cup being used helping us

realize Objectives 3.1&2. These edges will allow our algorithm to compute the volume of the

cup relative to the number of pixels between the detected edges. These counted pixels will be put

into another algorithm that will compute the volume of the consumer’s cup, which will realize

Objective 3.3. The actual fluid dispensing will incorporate using a valve and a constant flow rate.

The valve will be left open for the correct amount of time relative the oz/sec measured for that

particular liquid. This will achieve Objective 3.4&5. The barcode software and database

construction will be used for the purpose of maintaining financial records and transactions to

help accomplish Objective 3.7. Once all of the software has proven its functionality, different

stages of testing will begin to determine the actual positioning of the hardware within the

housing unit. These tests will establish if certain components need to be in a different location

relative to another component and give us an optimal design that is both functional and

aesthetically pleasing.

4.3 Integration

After testing the individual components of the hardware in conjunction with the software,

final integration of the product will occur. The final integration will employ all of the required

parts along with all of the developed code working in unison. This will allow us to validate our

individual component tests while the product simultaneously takes the form of our working

prototype. These steps will allow us to realize Objective 3.6&8. By this point in our design plan,

the major hardware and software problems should have been taken care of, thus allowing a

smooth integration. A graphical user interface (GUI) will also be added to ensure the customer

has a comfortable experience with the product thus completing Objective 3.7. It is at this point in

the design that we will finish the final enclosure of the product to hide all of the circuitry and

10

electronic equipment while also completing Objective 3.5. The enclosure will provide stability,

protection, and can add more aesthetic appeal to the final design.

4.4 Finalize

In this stage, the product will be verified and validated. Vigorous testing will occur to

ensure the performance and stableness of our product in a consumer oriented environment while

containing all of the required constraints in the final design. Testing procedures will be made

along with our User’s Manual that will describe the simple process in detail. Troubleshooting

steps will be included in the manual for technicians to easily repair or replace components if it

that is needed. This working prototype will have a barcode reader to identify a customer and

machine vision to accurately dispense the correct amount of fluid automatically to a satisfied

customer. Once this goal is accomplished, the final report will be written and submitted with our

project folder containing all materials pertinent to the design process.

5.0 Deliverables

The following articles will be delivered during the design process:

Weekly Reports

Product Specifications

Drafts of Final Report

Final Report

MATLAB Code

Microcontroller Code

Physical Model (prototype demonstration)

Final Presentation

Webpage

Project File

11

6.0 Schedule

Figure 2: Schedule shown with gant chart.

The schedule shown is an approximate schedule that allows for predicaments that the

group might encounter during our design process. The schedule shows six separate phases of

design that correlate to the plan described above. The Integration in this schedule does not show

the verification and validation reports along with the final report that will be due at the end of the

semester. The software has the longest amount of time allotted to it because of the complexity it

will involve but it does not account for starting code development early. Major milestones in this

schedule include a completed concept to work towards, completed and configured hardware

ready for software, completed software development, and a working prototype ready for

demonstration three weeks before finals.

7.0 Staffing

The most important aspect pertaining to the successful design and creation of the

AVD&FDS project is the design team. Composed of three electrical engineering undergraduates

studying at the University of Texas at San Antonio, the team has the appropriate skills, resources,

12

and knowledge to generate a well defined design plan and construct a properly functioning

product. The three dynamic team members are Frederick Weissbach, Sean Tovar, and Brendan

Baker.

7.1 Frederick Weissbach

Frederick Weissbach is a student with discipline specialization in the systems and

controls concentration, and further studies in the computer concentration. These classes provide a

very tangible skill set that will help over the span of the design. He also works in the Robotics

and Intelligent Machines (RIM) laboratory for UTSA’s mechanical engineering research

department, involved primarily in data acquisition, sensor implementation, and interfacing with

collaborative robots. Closely working in a well-funded lab with intelligent graduate students and

industry personnel has given Frederick the rare opportunity of using state of the art research

technology and invaluable networking opportunities. This has also provided a slightly more in

depth skill of National Instruments software and MATLAB. He has also worked well alongside

both team members in previous class projects. With Sean, he has interfaced a triple-axis

accelerometer in National Instrument’s LABView for Electrical Engineering Lab I. Brendan and

Frederick together have generated a unique image encryption method while reporting on image

processing in MATLAB for Signals and Systems II, as well as numerous microcontroller coding

projects with hardware interfacing in Microcomputer Systems II.

7.2 Brendan Baker

Brendan Baker is an EE student with a specialization in controls at UTSA. He has

worked at Encino Automation, LLC the past two years and has gained invaluable knowledge in

system integration and programming. Along with this knowledge and experience, Brendan will

begin to work in the Robotics and Intelligent Machine Laboratory (RIM) in the spring and

expand his knowledge in sensor implementation and machine vision while working in close

collaboration with graduate students. He has also gained knowledge in programming and

interfacing with a microcontroller through EE 4583 Microcomputer Systems II. Brendan has

worked extensively with Frederick in numerous projects at UTSA that include an image

encryption via MATLAB for EE 3523-Signals and Systems II and designing a 5 band equalizer

for EE 4313-Circuits II. Brendan will also play a key role in locating the right hardware through

the distributors he knows from his time at Encino Automation, LLC.

13

7.3 Sean Tovar

Sean Tovar is a Controls Electrical Engineering student with knowledge in LabView and

MATLAB. Extensive use of LabView was used in a previou project in Electrical Engineering

Lab I (EE 3113) while MATLAB experience was gained during the course of Analysis and

Design of Control Systems (EE 3413). Sean will also be taking Intelligent Controls (4733) and

Embedded Control Systems (EE 4743) during the development of the system which will further

his knowledge in this discipline.

8.0 Equipment and Materials

Because EE Lab I (3.04.72) and EE Lab II (3.04.64) house oscilloscopes, computers, and

power sources, these two rooms along with the Sr. Design Lab will be the main meeting places

during the course of the product construction. A PC will be used as the main processing unit with

a microcontroller also being used to control valve behavior and a few extra sensors. A machine

vision camera will be implemented for edge detection. This will allow MATLAB to calculate the

volume measurements of the container through the executed code. A pressure sensor will detect

the presence of a container to make sure there is actually a cup to fill and a timer will control

how long the valve is open to control the volume being released into the container. Some liquid

tubing will be used by the system for the transport of the beverage from storage to the

consumer’s cup.

9.0 Budget

Product Cost

Microcontroller $100

Discrete Valve $30

Camera/Equipment UTSA+$50

PC Owned

Tubing $4

Cables $16

Housing Unknown at this time

Total ~$200 + Housing

Table 1: Proposed budget for design

14

10.0 Conclusion

Our team thanks you for taking the time to read this proposal and is sure it contains the

necessary information for you to make a well advised approval of this project. We believe this

product has future potential that could transform the way restaurants and large venues distribute

their beverages, which would lead to more than sufficient revenue for the company. Should there

be any more project data you would like to review, please do not hesitate to contact anyone from

our group (see Appendix A).

15

Appendix A

Brendan Baker

(210) 315-1604

hgo038@my.utsa.edu

Frederick Weissbach

(832) 704-2058

bmj119@my.utsa.edu

Sean Tovar

(210) 253-0645

wsx937@my.utsa.edu