Real-time Monitoring and Diagnostic Solution for an HVAC System

ECE Team 169Anthony Bellantoni (EE)Greg Carmichael (EPhys)Joe Grassi (EE)

Sponsored by: Qualtech Systems Inc.Advisor: John Chandy

Presentation Outline

• Project Goals

• Last Semester Accomplishments

• TEAMS

• Completed Designer Model

• Overview of Code

• Project Limitations

• Project Timeline

• Project Budget

• Wrapping Up Project

Overall Project Goals

• Update and complete HVAC Model- Previous Senior Design Project

–Developed Partial Diagnostic Model of the ITEB HVAC System

• Develop C++ program, extract and analyze real-time data from the building sensors

• Combine model and code to detect for faults in real-time.

Fall 2012

• Completed and fixed HVAC model

• Met with facilities to ensure model was correct

• Main Limitation

o No Real-time data Hard to develop code

TEAMS

• Testability Engineering and Maintenance system

• Designer• RDS

o Remote Diagnostic Server• SDK

o Combines client to RDS

http://tomgpalmer.com/wp-content/uploads/legacy-images/FLASH%20LIGHT.jpg

Procedure

3rd Floor Schematics

Picture for RDS

using mike (maintenance group)

most likely 3 slides

RDS

C++ Coding Goals

• Extract sensor values from text file and determine whether or not a failure is occurring

• Save results to a text file • Import results file into TEAMS-RT• TEAMS-RT will combine code with our model

and determine most probable failure point and associated test cost

How to determine a failure

• Set threshold value for maximum deviation from setpoint

• Cannot assume failure after one test

• Initiate a counter to count number of tests in a row that fail

• If consecutive tests trend toward the set point, counter returns to 0

• If deviation from the set point is less than the maximum allowed, counter returns to 0

• If n tests in a row fail and do not approach set point, assume failure

How to arrange code, method 1

Advantages/Disadvantages+ Code is simple- Harder to change n- Lots of files/messy

Sensor 1

Sensor 2

Sensor n

Combine all sensor code to one file and create an n-column text file with results

Input results into TEAMS-RT

Method 2

Advantages/Disadvantages+ Code is neat and easy to debug+ Easy to change number of sensors- Coding is difficult

Temperature

Humidity

One code file to extract results from n sensor files and output results into an n-column text file

Input results into TEAMS-RT

Project Limitations

• Cost and time of each failureo Talked to facilities: do not have information

• Obtaining access to actual VAV sensor values

Project TimelineTask September October November December January February March April

Software access

Schematics

Research HVAC

Update model

Learn C++

Develop code

Merge code and model

Test and debug

Project Budget

http://i.crn.com/images/free_cloud_400.jpghttp://blog.outreach.com/wp-content/uploads/2011/09/Church-events-on-no-Budget.jpg

http://www.rosemarierealty.com/wp-content/uploads/2012/03/dreamstime_xs_17999966-300x300.jpg

http://static.seekingalpha.com/uploads/2009/3/4/saupload_mar04_09_bm.jpg

Next Steps: Weekly GoalsMarch 10 - March 16• Multiply our code to work for multiple VAVs• Learn and Read TEAMS-SDK Manual• Label possible reasons of failure for maintenance checks in TEAMS Designer

March 17 - March 23 (Spring Break)• Research associated pricing for each component (including maintenance)

March 24 - March 31• Continue to debug and implement code• Continue step-by-step instructions for maintenance fixes• Add any found costs/maintenance pricing found into TEAMS• Wrap up model + code

April• Contact Moises to check if model is complete• Begin final presentation & report preparation• Wrap up Entire project and present it

Questions

?