Professional Documents
Culture Documents
1920
The idea of a robot is not new.
For thousands of years man has
been imagining intelligent
mechanized devices that
perform human-like tasks. He
has built automatic toys and
mechanisms and imagined
robots in drawings, books, plays
and science fiction movies.
4
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
However, robots of today are not exactly the walking,
talking intelligent machines of of movies, stories and our
dreams. Today, we find most robots working for people
in factories, warehouses, and laboratories. In the future,
robots may show up in other places: our schools, our
homes, even our bodies.
5
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
Today fully functioning androids
are many years away due to the
many problems that must be
solved. However, real, working,
sophisticated robots are in use
today and they are revolutionizing
the workplace. These robots do
not resemble the romantic
android concept of robots. They
are industrial manipulators and
are really computer controlled
"arms and hands".
6
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
Robots have the potential to change our economy, our health,
our standard of living, our knowledge and the world in which we
live. As the technology progresses, we are finding new ways to
use robots.
7
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
Benefits of Robots
8
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
Robotics for bio-production
9
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History EMT
HAZBOT III is part of JPL's Emergency Response Robotics
Project, a five-year effort begun in 1991 to apply robotics
technology to the safe handling of hazardous materials. Robots
such as HAZBOT also hold potential for use in mining and law
enforcement. "It's almost standard now to have robots on bomb
squads in major cities, but it took several years for the idea to
catch on," said Richard Welch, task manager of Emergency
Response Robotics at JPL.
10
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Robotics History
And Future
The Mars 2003 Rover
Project is designed to have
two scientific rovers going
to Mars in 2003. Each
rover will search for
evidence of liquid water
that may have been
present in Mars past. The
rovers will be identical to
each other, but will land at
different regions of Mars.
11
Wee
Thursday, December 09, 2021 copyright© Kaushik Ray k1
Classification of Robotics
• Manual Robotics
• Semi-Autonomous Robotics
• Autonomous Robotics
Power Control
Management ROBOT
System
Sensors
Sensing?
Internal information
Localization
Obstacles
Tracking
Touch Sensors
Infrared(IR) Sensors
Thermal Sensor
Rotation Sensor
Laser Sensor
Light Sensor
Video Camera
Thursday, December 09, 2021 copyright© Kaushik Ray 19
Sensors
Touch Sensors
Simplest sensor.
Uses a crude method of sensing.
electrical flow
force voltage
measurement
Infrared Sensors
Infrared (IR) radiation is part of the electromagnetic
spectrum.
Radio Waves
Microwaves
Infrared
The Visible Spectrum
Ultra Violet
Gamma Rays
x-Rays
The name means “below red”, red being the color of visible
light of longest wavelength.
Wave length range- 750 nm and 1 mm.
Thursday, December 09, 2021 copyright© Kaushik Ray 21
Sensors
Infrared Sensors
Transmitter
Transmitter
Infrared Sensors
Receiver
Receiver
Light Sensors
Measures the amount of light that it sees.
It outputs a number between 0 (total darkness) and 100 (very
bright).
The light sensor uses its own light source, a red Light Emitting
Diode (LED), to illuminate a small area in front of its receiver.
When the light sensor is over the white paper, it reads a value of
50. When it is over the black paper, it reads a value of 13.
Light Sensors
This consist of a photodiode which allows current through
voltage
measurement
light energy
voltage
measurement
Thursday, December
electrical flow 09, 2021 copyright© Kaushik Ray 26
Sensors
Light Sensors
LDR’s are light dependent resistance
Two types of LDR circuits -
R2 R5 R5
100R R4 R4
10K 100K
2K2 2K2
U3A U3A
3
5 5
IR LED + Digital O/P + Digital O/P
V+
V+
D3 Photo Dio de 2 2
D4 R3 OUT R3 OUT
4 4
- -
V-
V-
LM339 LM339
12
12
0 0
IR Proximity Detector Bump Detector
VCC
VCC
R6
R6
5K
Digital O/P 5K
Digital O/P
8 - Bit ADC
R2
8 - Bit ADC
1k R2
1k
LDR
Thermistor
0
Light Intensity Detector 0
Temperature Detector
OP AMP implementation of
voltage comparator
In electronics, a comparator
is a device which compares
two voltages or currents and
switches its output to indicate
which is larger. More
generally, the term is also
used to refer to a device that
compares two items of data.
Differential drive
Car type drive
Skid steer drive
Synchronous drive
Pivot drive
V = IR V = V+
V=0
V = IR
(V = -IR)
DC MOTOR
Q1 Q3
NOT GATE NOT GATE
2
2
2 1
A
-
Q2 + Q4
L R
1
1
GND
Easy to operate.
High Torque
Less torque
Not Smooth
Smooth drive
0100
0001
1000
0100 0011
0010
1001
1000 0110
1100 0100
Thursday, December 09, 2021 copyright© Kaushik Ray 82
Comparison
Double coil
Single coil
High torque
•Low torque
Consume double
•Consume less energy
energy
Data
Motor 2
Port2
◦ Buffer P = A
A P
A P
0 0
1 1
A P
◦ Not P=A
0 1 A P
1 0
Basic AND / OR
Circuits with two Inputs
A B P
0 0 0
◦ AND P = A.B 0 1 0 A P
1 0 0 B
1 1 1
A B P
0 0 0 A
◦ OR P=A+B 0 1 1 B
P
1 0 1
1 1 1
Basic NAND / NOR
Problems with two Inputs
A B P
◦ NAND P = A.B
0 0 1 A P
0 1 1 B
1 0 1
1 1 0
A B P
0 0 1
A
◦ NOR P=A+B 0 1 0 P
1 0 0
B
1 1 0
Basic XOR / XNOR
Circuits with two Inputs:
A B P
0 0 0
◦ XOR P = A B 0 1 1
1 0 1 A
P
1 1 0 B
A B P
0 0 1 A
P
◦ XNOR P = A B 0
1
1
0
0
0
B
1 1 1
Simple Line Follower
AT89C51
Similar to a Microcontroller.
Uses:
Microcontrollers have become common in many areas, and
can be found in home appliances, computer equipment,
and instrumentation.
They are often used in automobiles, and have many
industrial uses as well, and have become a central part of
industrial robotics.
Because they are usually used to control a single process
and execute simple instructions, microcontrollers do not
require significant processing power.
LM324 L298
How to interface
sensors,
Comparator with
microcontroller
AT89C51
Don't try to build a robot and then write software for it. These two domains feedback on each other. Develop them both concurrently, they are
really just two different pieces of the same problem. You'll save a lot of frustration and headaches if you write the software as you go.
The robot needs to be able to survive on its bumper behavior alone. All other sensors will eventually depend on the bumper to rescue them from
failure modes. A robust collision detection method should not allow the robot to run into anything without sensing it. And there is great peace of
mind in the knowledge that the robot won't rip itself apart if you are not watching it all the time!
Let the robot run around your living/working space and observe the bumper collision recovery failures. Figure out how to resolve them. A quick
look at the robots which run in the DPRG contests will reveal that very few have ever had to survive an encounter with the back end of a
rocking-chair. Nice flat walls are not the problem.
Find the situations in which the robot's response is not appropriate, where it gets stuck, or scrapes off a sensor, or snags a wire, and see if you
can develop a software- hardware solution which does not require human intervention!
I have a real temptation when I'm working to change a software or hardware feature, put the robot down on the floor for 30 seconds of
evaluation, and then pick it back up for more changes. This is a mistake. These are really "chaotic" systems, greatly dependent on initial
conditions and unobservable real-world parameters.
Let it run a lot, in different conditions and environments, before determining the effectiveness of a certain behavior or modification. Evaluation
should take the lion's share of your development time. It's also the most fun!
4. Document, document, document. Write down what you did, comment your control programs, draw diagrams/schematics/etc and keep them
up-to-date, label wires and connectors (especially ones that carry the power supply). In two weeks, you won't remember what changes you made
to board A that needs to connect to board B that you haven't had time yet to fix. You won't remember which orientation a connector is supposed
to attach. You'll be glad you wrote it down.
5. Use fuses, optical isolators, and/or other forms of protection liberally in your design. A fuse for each power source: battery, DC-DC converter,
charger, etc.
6. Be very methodical in your debugging. Check the simplest things first, even twice if you aren't SURE after the first time. Problems always
seem to come up at the interfaces -- connectors, sockets, serial protocols, etc. Use a voltmeter to check your connections, even AFTER you
physically connect them.
7. Beware of anyone else's pre-canned control code. If you use someone else's stuff, check everything they've done in it against what it should
be. No one is perfect, and the code may not do exactly what you assume it will do.
8. Design your drive motor system to carry twice as much weight as you predict your robot will weigh when finished. The margin will disappear
quickly with "small", seemingly insignificant additions.
9. Use the techniques and knowledge of others to avoid re-inventing the wheel. E.g.: if you need 68HC11 or 8051 code to control hobby servos,
post a request to the club. The same goes for motor control, IR detection, etc.
10. If you use an oscilloscope, put Ground pins in easy-to-reach places on your circuit boards.
11. I recommend getting an oscilloscope if you don't have one. It will save you time and money in the long run.
12. Give your robot lots of outputs: LEDs, sound, servos, etc. They're great for diagnostic output as well as entertainment.
13. Start with something simple, then add to it. Don't try to build a complex robot without first making sure you can build a simple one that works.
Then take baby steps, adding functionality to the simple one. (By the way, "subsumption" is a good control software model to use for this... I
believe David took this approach, too. Start with bumper switches, then add infrared, sonar, imaging, etc.)
14. Unless you have lots of time and money, build your robot modular. If the motor controller is one module, power management another, speech
another, etc, it's easier to troubleshoot if you have a standalone module. It also makes it much easier to transfer your technology to your next robot.
15. Don't overlook thrift stores, swap meets, and garage sales as good sources for parts. Many times technology only a few years old will show up
at a swap meet for $.05 on the dollar.
16. Develop a system of construction and stick to it. Black wires will always be ground, red wires will always be VCC, white wires will always be
motor supply, etc. If you get in the habit of grabbing what ever color wire is handy to build your bot, troubleshooting will be much more difficult.
It also makes documentation much easier.
18. Add to your parts bin when the opportunity arises. Unless you live next to the ultimate Robot Parts Store, or plan to special order every gear
you need, pick them up when you see them -- taking storage space and spousal tolerances into account, of course!
20. Get datasheets for what you don't understand. Read them, digest them, absorb them. Then go back and read them again until you can explain
them to someone else.
21. Share with others what you are doing. Think out loud. Often times in the process of answering questions about your plans, you'll be forced to
further define things and polish some of the rough spots.
22. Be proud of what you build. Some people talk, some people build. If you have to pick just one, then build. But doing both is preferred.
Sensors
http://www.sensorland.com/HowPage022.html
http://www.answers.com/Infrared%20Sensors
http://www.barello.net/ARC/projects/LEGO/
http://www.sensorland.com/HowPage022.html
Light Sensors
http://www-education.rec.ri.cmu.edu/roboticscurriculum/lightsensor.htm
http://www-education.rec.ri.cmu.edu/multimedia/rcx.shtml
http://www-education.rec.ri.cmu.edu/multimedia/rotationsensore.shtml
http://www.doctronics.co.uk/ldr_sensors.html
Microcontroller
http://www.mrrobot.com/
http://en.wikipedia.org/wiki/Microcontroller
http://www.answers.com/topic/microcontroller
http://computer.howstuffworks.com/microprocessor.htm
http://www.knightlight.co.uk/info-microprocessor-information.asp
http://lucy.vub.ac.be/links.htm
http://www.ti.com