Professional Documents
Culture Documents
Session 1, 2014
Aim
The aim of this lab is to examine your ability to apply concepts from the areas of power and signal processing to the design and implementation of a system for the monitoring and management of power delivery systems.
S1, 2014
Requirements Discussion : The groups get together and discuss the requirements. This is essentially the requirements analysis phase. Approximately 15 minutes are allocated to this activity. Preliminary design phase : Duration 2-2.5hrs. It is extremely important that each group does this on their own and no interaction between the groups takes place. That is students should treat this as an exam where they are are not allowed to interact with anyone other than their partner. This is so that each group comes up with their solution and a variety of solutions are presented to the discussion phase. Design Presentation : Each team will very briey describe their solution. No questions or discussions are allowed here. A maximum of 5 or 6 minutes is allocated to each team. Design discussion : 20-30 minutes. The aim is to discuss and debate the solutions. This should be a positive discussion with constructive criticism one another in order to improve your collective chances of success. Essentially, the lab is divided into three major phases. The preparatory part, consisting of the reading time and rst discussion, and lasting about 30 minutes; the preliminary design part taking about 2.5 hrs of the lab time; and the presentation and nal discussion occupying the last hour of the lab. It is important to see the purpose behind this process. It consists of a combination of individual work and group interactions. During the rst discussion your task is to understand the requirements and identify the concepts that are required for you to complete the design task. In the second phase, the work in pairs allows you to use your knowledge to arrive at your own design. This is extremely important rstly to enable you to assess your prior knowledge and identify your weaknesses, and secondly to the success of the group session. The larger the variety of designs that are presented is, the more likely the quality of the nal design will be improved. Therefore, it is important to contribute and be able to constructively criticise the designs of others and to explain and defend your own (note that it is just as important that you see a valid point someone else might make regarding your approach). This should be done, however, in the spirit of cooperation and not competition. Imagine that you are a team in a company and are working together to produce this design. Your mark for this session will reect the quality of the contribution you make. The marks for the preliminary session are primarily allocated to the presentation and contribution to the nal discussion. Following the preliminary lab session, you have two weeks to complete your design, rene it, improve it, tweak it, or change it as you see t. During this time there is an open lab as per the schedule in the course outline. In nalising your design, you do not have to restrict yourselves to the results of the rst lab session. You must also produce your design report prior to the assessment lab. The report should include the following sections: 1. The Design Requirements : In this section you are to explain the design task and the requirements. 2. The Detailed Design : This section should explain your design in detail. 3. The implementation and Test Plan : This section should give a detailed implementation plan, including the detailed steps to get your design implemented with minimal risk. For example you should include the steps for measurement of actual component values and comparing them with nominal values. Calculations should be done to verify that deviations between actual and nominal values do not take the performance outside the acceptable bounds (that is the design should still satisfy the requirements). Test points and corresponding outputs should be clearly identied and their results documented. The implementation and test plans will be crucial in your assessment. Students will be required to submit their report through Moodle by 3pm during the assessment lab.
Assessment Session
The rst hour of the assessment lab is devoted for student teams to prepare for the marking. Each group should set up their design at their desk and the preliminary report will need to be submitted on Moodle before assessment starts (that is by 3pm). A random marking order will be announced (written on the board) and the asssessment will start at 3pm sharp. Every one will be asked to move away from their desk. Each group will be allocated a maximum of 25 minutes for the assessment. The assessors are instructed to adhere strictly to this time allocation and to uphold the schedule. You will be given no additional assessment after your assessment allocation is up and your design cannot be checked again. 5 minutes prior to the start of their assesssment, the group to be assessed may get back to their desk to be ready for the marking. It is important for you to be well prepared for the assessment. The time allocation will seem very short if you are not ready. You will rst be asked to explain and demonstrate your design. As mentioned in the course outline, 2
S1, 2014
you have a responsibility to show o your design and demonstrate that it works and meets the requirements. You should explain your reasoning, any assumptions you have made, design decisions you have taken, etc... If you cannot demonstrate your design, then it does not work as far as the assessor is concerned. In all this, it is dicult to overstress the importance of the implementation and test plans. You must prepare them carefully and make sure they are useful to you in the lab. Both of them will play a signicant role in your assessment. The implementation plan should give you the instructions to navigate your way from the start of the lab to a working system. The test plan should give you a clear way of testing and verifying that your system works (i.e. it does what it was designed to do, in the way it was designed to do it.) This is important both for debugging your system in case something does not work, and for demonstrating it to your lab assessor. The marking scheme for this session is based on the following criteria: Neatness of the breadboard/code. Demonstrating your design - Does your design achieve the requirements? Demonstrating your understanding, can you explain the operation of your system?
S1, 2014
PF Compensation Unit
Computer
Additional Information
Figure 2 shows a representation of the measurement and PF compensation units: Actual pictures of these devices are posted on Moodle.
S1, 2014
Mains Supply
PF Compensation Unit
1F
2.2 F
4.7F