0% found this document useful (0 votes)
288 views

Lab Report Format, Lab Evaluation Criteria & Electrical Safety Guidelines

The document provides guidelines for evaluating labs and preparing lab reports for a course on microprocessor interfacing and programming. It discusses three criteria for evaluating labs: experiments and reports, quizzes, and a final evaluation. It also provides a format for lab reports, with sections on introduction, objective, design, issues, conclusions, and applications. Safety guidelines are provided for working with electricity in labs, addressing risks of electrocution, overloaded circuits, exposed wires, and proper maintenance of equipment.

Uploaded by

Umair Hameed
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
288 views

Lab Report Format, Lab Evaluation Criteria & Electrical Safety Guidelines

The document provides guidelines for evaluating labs and preparing lab reports for a course on microprocessor interfacing and programming. It discusses three criteria for evaluating labs: experiments and reports, quizzes, and a final evaluation. It also provides a format for lab reports, with sections on introduction, objective, design, issues, conclusions, and applications. Safety guidelines are provided for working with electricity in labs, addressing risks of electrocution, overloaded circuits, exposed wires, and proper maintenance of equipment.

Uploaded by

Umair Hameed
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Lab Manual of Microprocessor Interfacing & Programming

Appendix-A: Lab Evaluation Criteria


Labs with projects
1. Experiments and their report 50%
a. Experiment 60%
b. Lab report 40%
2. Quizzes (3-4) 15%
3. Final evaluation 35%
a. Project Implementation 60%
b. Project report and quiz 40%

Labs without projects


1. Experiments and their report 50%
a. Experiment 60%
b. Lab report 40%
2. Quizzes (3-4) 20%
3. Final Evaluation 30%
i. Experiment 60%
ii. Lab report, pre and post
experiment quiz 40%

Notice:
Copying and plagiarism of lab reports is a serious academic misconduct. First instance of
copying may entail ZERO in that experiment. Second instance of copying may be reported to
DC. This may result in awarding FAIL in the lab course.

Page | 1
Lab Manual of Microprocessor Interfacing & Programming

Appendix-B: Safety around Electricity


In all the Electrical Engineering (EE) labs, with an aim to prevent any unforeseen accidents
during conduct of lab experiments, following preventive measures and safe practices shall be
adopted:

 Remember that the voltage of the electricity and the available electrical current in EE
labs has enough power to cause death/injury by electrocution. It is around 50V/10 mA
that the “cannot let go” level is reached. “The key to survival is to decrease our
exposure to energized circuits.”
 If a person touches an energized bare wire or faulty equipment while grounded,
electricity will instantly pass through the body to the ground, causing a harmful,
potentially fatal, shock.
 Each circuit must be protected by a fuse or circuit breaker that will blow or “trip”
when its safe carrying capacity is surpassed. If a fuse blows or circuit breaker trips
repeatedly while in normal use (not overloaded), check for shorts and other faults in
the line or devices. Do not resume use until the trouble is fixed.
 It is hazardous to overload electrical circuits by using extension cords and multi-plug
outlets. Use extension cords only when necessary and make sure they are heavy
enough for the job. Avoid creating an “octopus” by inserting several plugs into a
multi-plug outlet connected to a single wall outlet. Extension cords should ONLY be
used on a temporary basis in situations where fixed wiring is not feasible.
 Dimmed lights, reduced output from heaters and poor monitor pictures are all
symptoms of an overloaded circuit. Keep the total load at any one time safely below
maximum capacity.
 If wires are exposed, they may cause a shock to a person who comes into contact with
them. Cords should not be hung on nails, run over or wrapped around objects, knotted
or twisted. This may break the wire or insulation. Short circuits are usually caused by
bare wires touching due to breakdown of insulation. Electrical tape or any other kind
of tape is not adequate for insulation!
 Electrical cords should be examined visually before use for external defects such as:
Fraying (worn out) and exposed wiring, loose parts, deformed or missing parts,
damage to outer jacket or insulation, evidence of internal damage such as pinched or
crushed outer jacket. If any defects are found the electric cords should be removed
from service immediately.
 Pull the plug not the cord. Pulling the cord could break a wire, causing a short circuit.
 Plug your heavy current consuming or any other large appliances into an outlet that is
not shared with other appliances. Do not tamper with fuses as this is a potential fire
hazard. Do not overload circuits as this may cause the wires to heat and ignite
insulation or other combustibles.
 Keep lab equipment properly cleaned and maintained.
 Ensure lamps are free from contact with flammable material. Always use lights bulbs
with the recommended wattage for your lamp and equipment.
 Be aware of the odor of burning plastic or wire.
 ALWAYS follow the manufacturer recommendations when using or installing new
lab equipment. Wiring installations should always be made by a licensed electrician
or other qualified person. All electrical lab equipment should have the label of a
testing laboratory.

Page | 2
Lab Manual of Microprocessor Interfacing & Programming

 Be aware of missing ground prong and outlet cover, pinched wires, damaged casings
on electrical outlets.
 Inform Lab engineer / Lab assistant of any failure of safety preventive measures and
safe practices as soon you notice it. Be alert and proceed with caution at all times in
the laboratory.
 Conduct yourself in a responsible manner at all times in the EE Labs.
 Follow all written and verbal instructions carefully. If you do not understand a
direction or part of a procedure, ASK YOUR LAB ENGINEER / LAB ASSISTANT
BEFORE PROCEEDING WITH THE ACTIVITY.
 Never work alone in the laboratory. No student may work in EE Labs without the
presence of the Lab engineer / Lab assistant.
 Perform only those experiments authorized by your teacher. Carefully follow all
instructions, both written and oral. Unauthorized experiments are not allowed.
 Be prepared for your work in the EE Labs. Read all procedures thoroughly before
entering the laboratory. Never fool around in the laboratory. Horseplay, practical
jokes, and pranks are dangerous and prohibited.
 Always work in a well-ventilated area.
 Observe good housekeeping practices. Work areas should be kept clean and tidy at
all times.
 Experiments must be personally monitored at all times. Do not wander around the
room, distract other students, startle other students or interfere with the laboratory
experiments of others.
 Dress properly during a laboratory activity. Long hair, dangling jewelry, and loose or
baggy clothing are a hazard in the laboratory. Long hair must be tied back, and
dangling jewelry and baggy clothing must be secured. Shoes must completely cover
the foot.
 Know the locations and operating procedures of all safety equipment including fire
extinguisher. Know what to do if there is a fire during a lab period; “Turn off
equipment, if possible and exit EE lab immediately.”

Page | 3
Lab Manual of Microprocessor Interfacing & Programming

Appendix-C: Guidelines on Preparing Lab Reports


Each student will maintain a lab notebook for each lab course. He will write a report for each
experiment he performs in his notebook. A format has been developed for writing these lab
reports.

Lab Report Format


1. Introduction: Introduce the new constructs/ commands being used, and their
significance.
2. Objective: What are the learning goals of the experiment?
3. Design: How do the new constructs facilitate achievement of the objectives; if
possible, a comparison in terms of efficacy and computational tractability with the
alternate constructs? Include the circuit diagram and code with explanation.
4. Issues: The bugs encountered and the way they were removed.
5. Conclusions: What conclusions can be drawn from experiment?
6. Application: Suggest a real world application where this exercise may apply.
7. Answers to post lab questions (if any).

Sample Lab Report for Programming Labs

Introduction

The ability to control the flow of the program, letting it make decisions on what code to
execute, is important to the programmer. The if-else statement allows the programmer to
control if a program enters a section of code or not based on whether a given condition is true
or false. If-else statements control conditional branching.

if ( expression )
statement1
else
statement2

If the value of expression is nonzero, statement1 is executed. If the optional else is present,
statement2 is executed if the value of expression is zero. In this lab, we use this construct to
select an action based upon the user's input, or a predefined parameter.

Page | 4
Lab Manual of Microprocessor Interfacing & Programming

Objective:

To use if-else statements for facilitation of programming objectives: A palindrome is a


number or a text phrase that reads the same backward as forward. For example, each of the
following five-digit integers is a palindrome: 12321, 55555, 45554 and 11611. We have
written a C++ program that reads in a five-digit integer and determines whether it is a
palindrome.

Design:

A. Hardware Circuit Diagram:

Fig.1. Circuit Diagram

B. Code with explanation:

The objective was achieved with the following code:

#include <iostream>
 
Using namespace std;
Int main()
{
    int i, temp, d, revrs=0;
 
    cout<<"enter the number to check :"; 
        cin>>i;
    temp=i;
    while(temp>0)
    {
        d=temp%10;
        temp/=10;
        revrs=revrs*10+d;
 
        }
    if(revrs==i)
    cout<<i<<" is palindorme";
    else
    cout<<i<<" is not palindrome";
 

Page | 5
Lab Manual of Microprocessor Interfacing & Programming

    }
}

Screen shots of the output for various inputs are shown in Figure 2:

Fig.2. Screen shot of the output

The conditional statement made this implementation possible; without conditional branching,
it is not possible to achieve this objective.

Issues:

Encountered bugs and issues; how were they identified and resolved.

Conclusions:

The output indicates correct execution of the code.

Applications:

If-else statements are a basic construct for programming to handle decisions.

Answers of Post Lab Questions

Page | 6

You might also like