Inroduction

There are eight modules as part of the practical aspects of this course. Each module consists of a practical part using LabVIEW and a more theoretical part which may involve more research and/or some other programming (not necessarily in LabVIEW).

1. Simple Analog Input/Output In this module we look at the simplest forms of analog input and output to a system, how these are achieved and their strengths and limitations





2. Disk reading and writing This module examines the issues of data taking speed and how the computer system can restrict the ability to take data. It also touches on some issues of data storage and integrity.





3. Simple Digital Input/Output The world of digital control and input are examined with a view to seeing how interaction with the computer is achieved in the real world. Several simple interfaces are used to examine the possibilities of digital I/O and control.





4. Timing and Event Marking - Timing of events and other things is an essential part of control. This module looks at some timing issues and how various forms of control can be achieved.





5. More on D-to-A and A-to-D Conversion Module 1 looked at some very simple forms of analog input and output. This module probes things a bit more deeply and considers some signal processing issues.





6. Serial Communications^th Controlling other instruments is a serious issue. This module (which is done in pairs) examines the issues of building controllers and instruments in a real environment.





7. Signal Processing and FFTs Signal processing is an integral part of modern data taking processes. This module looks at the possibilities for on-line signal processing as opposed to "off-line" processing. It also introduces the real aspects of the Discrete Fourier Transform





8. Digital Filtering The real world of digital signal processing permits us to do in digital hardware what was once only possible in analog parts. This module examines how real filters can be constructed in digital terms and their real performance.

Marking/Evaluation

Each report is worth 10% (one-tenth of the final mark). Up to three modules may be substituted by an agreed project which would then be evaluated as an equivalent weighting (ie a project which substituted for two modules would be evaluated at a weight of 20%)

Report Format

Reports must contain the following:

• An explanation of how you went about tackling the problem(s)
• Things that you thought were important, relevant or especially worthy of notice about your solution(s)
• A record of any programs or VIs you created or used in the course of your solution(s)
• A record of any special input and output
• Examples of the system(s) in operation if appropriate
• Notations of any problems you encountered
• Suggestions as to how things could be extended/expanded/improved
• An answer to every question asked in the instructions





• Reports should be clearly hand-written or printed.





• No report should exceed 10 pages of text plus 10 pages of print-out. Project report lengths are in proportion to the weighting - if a project is substituting for two modules, the allowed length is doubled. There is no compulsion to use all the permitted length - brevity is a virtue!

Projects

Projects are to be nogotiated with the professor. Projects are encouraged within the limitations of our resources. If you would like to do a project, please contact the professor early in the term.

Hand-In

Reports are to be handed in on time. Late reports will be penalised one mark per working day that they are late up to a maximum of one week, after which they will not be accepted.

In the event that you will not be able to hand in a report on time for good reason. Please see either the professor or the demonstrator as soon as the problem is known. Neither are very susceptible to reasons which suddenly appear on the due date for the report!