Answer Happy

CSE/EEE 120 Capstone Design Project Spring 2022 Temperature Control Project Summary The goal of this project is to design part of the controller to regulate temperature as part of the design of a thermostat. As required for all HVAC (Heating, Ventilation, and Air Conditioning) systems, the controller must be designed so that the equipment is not damaged. The controller has two inputs and two outputs. The inputs are R, for Raise the temperature, and L, to Lower the temperature. These are driven by two sources. There is a sensor that monitors the temperature and compares it to the temperature specified by the user. There is also the ability of the user to manually set R or L to override the current setting. The outputs are H for Heat, to turn on the heating system when it is too cold, and C for Cool, to turn on the cooling system when it is too hot. The inputs function as follows: R=0, L=0 means the temperature is good. R=0, L=1 means the temperature is too high. R=1, L=0 means the temperature is too low. R=1, L=1 is undefined. It is up to you to define how this works. These are important rules which MUST be followed: Rule 1: H and C may never be 1 at the same time. That is, the cooler and heater can't be enabled simultaneously. Rule 2: There MUST be 3 clocks when both H and C are 0 when switching between heating and cooling or vice versa. For example, if the inputs change from RL=10 to RL=01, there must be 3 clocks during which H is 0 and C remains 0 before C can transition to 1. These 3 clocks are a "buffer” to make sure the equipment isn't damaged while switching from one mode to the other. (The same HVAC equipment is often used to both cool and heat homes by reversing the way it operates. Switching over from cooling to heating or vice versa too quickly may seriously damage the equipment. As a result, thermostats have built in delays when switching between heating and cooling.) You have other design decisions to make. During the 3-clock buffer, what happens if you request the original setting? For example, the setting is RL=10 so the heater is on. The user changes the setting to RL=01 for 1 clock and then changes the setting back to RL=10. Does the equipment still need the 3-clock buffer? Can the buffer be reduced to 2 clocks in such cases? Finally, how do you want to define RL=11? Does the design prevent this from being possible or do you want to use it for some other feature? Your first task is to interview several customers (at least 3) to gain insight into what type of features and functionality are preferred by potential clients. These customers can be professors, TAs, UGTAs, or other classmates. You then weigh their opinions to help you finish certain features regarding this design. These people may have conflicting opinions. It is up to you to document these findings and judge which suggestions to accept. You will need to analyze how your design adds value from multiple perspectives (technological, societal, environmental,
financial, etc.), so be sure to ask questions other than just about the automation, but about the environment and type of customer that will be using it. Make sure you record the names of the people you speak to about your design in your template. Once you go through this customer discovery, create two finite state machine designs applying what you learned from your interviews and using different assumptions. This means documenting the assumptions made for each design and going through the design process (State Definition Table, State Transition Diagram, State Transition Table, Combinational Logic Design). Note that the two designs you create must be functionally different. That is, you can't create the same design once as a Mealy machine and once as a Moore machine. That is, the assumptions you make for RL=01, 10, and 11 must be different for the two designs. In addition, at least one of the designs must be based on Karnaugh maps and logic gates. You will also need to figure out if you want to incorporate any asynchronous inputs (Preset, Clear). Once you have completed two different designs, you will need to choose one design to implement and simulate in Digital. To do this, you will need to select at least 5 different criteria to use for comparison of each design and aid in your decision-making process. These criteria can originate from your customer interviews or from your own engineering intuition. Examples of criterion can be "ease of design, ease of understanding how it works, size of circuit, extra features." Each criterion must be given a weight (totaling 100%) of how important it is to include in the final design. Each design will then need to be rated against how well it meets each of the suggested criteria. Based on these ratings, select the best design that meets the customer's needs, and implement it in Digital, then simulate it through enough clock cycles showing each possible state transition. (Depending on your design, this may take multiple simulations.) In addition, you must show that each position can be visited using proper moves. Items which go into your template include all your design documents. These include state definition tables, state transition diagrams, Karnaugh maps, behavioral equations, etc. When you implement the design in Digital, be sure to include a screenshot of your completed design. You will also create a video in which you showcase your design. Topics to be covered in the video should include, but are not limited to, 1. The design assumptions you made 2. A brief description of your two designs and why the one you built was best 3. Showing your Digital design schematic and its features 4. Simulating the design in Digital showing some different scenarios and showing you visiting each position with proper moves. Deliverables You need to propose two different sets of assumptions. That is, how your two designs differ. You need to design two finite state synchronous machines that you can demonstrate to your stakeholders. This would usually be the company liaison, but in this class the stakeholders are your (UG)TAs, classmates, and instructors.
. . . . The designs must be different in their functionality. You should comment on why your controller adds value from multiple perspectives (technological, societal, financial, environmental, etc.). One or two sentences is sufficient. The number of states is not defined, you can use as few or as many as you need to provide the desired functionality. If something is not clearly documented in the summary, you need to make assumptions. The assumptions need to be documented. Please remember that you can design the state machines and add functionality to the design as you see fit. However, you need to collect feedback from at least three stakeholders. Again, stakeholders are your UGTAs, the lab TAs, and the instructors. You should describe in a sentence or two how you changed your design based on the feedback you received. You can use D flip flops, T flip flops or J-K flip flops in your design. The type does not matter. Mixing different types of flip flops with different trigger edge sensitivity is possible but not recommended. You need to properly document your designs. If you do a “classic” paper-based design, you need to include diagrams and state tables as well as K-Maps and logic. If you decide to go with a different implementation (ROM, HDL), you need to comment your code. You must have a schematic design in Digital which matches your simulation. You need to pick the best design and explain why it is the best. It is very helpful to have judgement metrics in mind, for example, number of states, features, ease of building, number of logic elements, your understanding of the design, or others that you can come up with. You need to define the weight of each of these metrics. That is, ease of building is worth 10 points, number of logic elements 20 points, number of states 40 points, etc. Award points to each design. For example, if one design is easier to build than the other, it might get 6 of the 10 points in the category while the other design gets the remaining 4. The design which has the highest point total is the best! Again, it is up to you to define the categories (minimum of 5) and the number of points each category is worth. You must justify the points awarded with one sentence per category. (Do NOT write an essay!) You will need to simulate one design in Digital and show the simulation in your video. The simulation must demonstrate that you meet the rules and must also show how your assumptions modified the base specification. • A short video, the contents of which were described above. Upload your completed template (which must include a link to your video) and a zip file of your capstone folder. Upload the template separately even if it is in your zip file. There will be a 5-point deduction if your template is not submitted separately. . .
Grading Policy Spring 22 Version 0.1 3 . . . The grade will be allocated as follows: 5% for the value proposition. 5% for the stakeholder interviews. 5% for documenting the changes performed to your original idea. 20% for documentation in the report of how the first circuit performs the application. 20% for documentation in the report of how the second circuit performs the application. 5% for establishing reasonable criteria for picking one design as the “best” design. (The one design you build in the hardware lab does not need to be the best design.) 5% for picking a preferred, “best” design. 15% for Digital implementation 15% for the video demonstration. 5% for following design template guidelines (organization, legibility) 2% (Extra Credit) Completed Self-Assessment Worksheet . . . .