S14: Virtual Dog

=== Grading Criteria ===

• How well is Software & Hardware Design described?
• How well can this report be used to reproduce this project?
• Code Quality
• Overall Report Quality:
  • Software Block Diagrams
  • Hardware Block Diagrams

    Schematic Quality

  • Quality of technical challenges and solutions adopted.

Abstract

This section should be a couple lines to describe what your project does.
In this project, we plan to build a device which would be able to track and follow a particular object. So if suppose that object is you, that device will follow you just like your dog. This tracking and following will be done in two dimensions, i.e. not just forward-backward movement, but left-right also. This can be achieved with the help of two devices, one will be used as reference and other device will continuously keep on monitoring the reference device. If position of reference device changes other device rearranges its position so as to maintain the desired relationship between them.

Objectives & Introduction

The main objective is to build an object following robot, which will follow a particular object in 2-Dimension. To make the robot follow at the same speed as of object we used four DC motor for the four wheels of robot so that it can accelerate the robot to desired speed. To keep track of object movement we used three proximity sensors (20cm-150cm) so that the robot can easily track the object. To power up the robot we used two batteries, one of 5V and other of 12V. 5V battery is used to power up the SJOne Board and 12V battery is required to run the DC motors. We have also implemented an Android App to start/stop robot and read the realtime statistics of sensors and our algorithm. To display the value of sensor as well as decision taken by robot on Android App we used Bluetooth module.

Team Members & Responsibilities

• Hari
  • Implemented sensor driver and algorithm to normalize sensor values, Android Application.
• Manish
  • Implemented central control logic and FSM.
• Viral
  • Implemented motor driver and Motor State Machine, bluetooth driver.

Schedule

Week#	Task	Estimated Completion Date	Status	Notes
1	Order Parts	3/16	Partially Completed	Not finalized with sensor for distance measurement. Ordered other parts.
2	Sensor Study	3/23	Completed (3/30)	Research on sensors took more time than expected due speed constrains of sensors conflicting with our requirement. Finally decided to move with IR proximity sensor. Sensors ordered.
3	Sensor Controller Implementation	3/30	Completed (4/6)	Three sensors interfaced with on board ADC pins. Controller implemented to determine direction of movement based on those three sensors
4	Servo and Stepper Motor Controller Implementation	4/6	Completed (4/6)	Initially planned to use stepper motor for steering and servo to move robot. But due to power constraints, decided to use DC motors to make a 4WD robot. Controller implemented to move and turn robot based on differential wheel speeds.
5	Central Controller Logic Implementation	4/13	Completed (4/13)	Integrated both controllers and developed basic logic to control wheels based on sensor input.
6	Assembly and Building Final Chassis	4/20	Completed (4/20)	Mounted all hardware parts on chassis to make a standalone robot. Central controller logic is still tuning.
7	Unit Testing and Bug Fixing	4/27	Completed (5/4)	Tested various combinations of object movement and tuned our algorithm accordingly. Tuning of algorithm took more time than expected because of many corner cases.
8	Testing and Finishing Touch	5/4	Completed (5/11)	Faced strange problem at final stages. Earlier sensors were giving linear output for distance v/s ADC value. Over the period we realized that our robot is not following the way it used to follow earlier. So we need to calibrate distance v/s ADC value again, and based on that we required to change our algorithm.
9	Android Application using Bluetooth	N/A	Completed (5/22)	Developed an Android Application through which we can start and stop our robot and able to collect realtime data for sensor values as well as decisions taken by robot.

Parts List & Cost

#	Part Description	Quantity	Manufacturer	Part No	Cost
1	SJOne Board	1	Preet		$80.00
2	IR Distance Sensor (20cm - 150cm)	3	Adafruit	GP2Y0A02YK	$47.85
3	DC Motor (12V)	4	HSC Electronics		$6.00
4	Wheels	4	Polulu		$8.00
5	Battery 5V/1A 10000mAh	1	Amazon		$40
6	Battery 12V/1A 3800mAh	1	Amazon		$25
7	LM2938D (Motor Driver IC)	2	HSC Electronic		$5.40
8	Chassis	2	Walmart		$12.00
9	Accessories (jumper wires, nut-bolts, prototype board, USB socket)				$20.00
10	RN42-XV Bluetooth Module	1	Sparkfun	WRL-11601	$20.95
	Total (Excluding Shipping and Taxes)				$265.20

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

All the three proximity sensor will measure their respective value analog and send it to the ADC pin of the SJOne board which will convert it to the digital value,the convert digital value will be utilized to determine the distance between the robot and the object. Based on the calculated distance the PWM value is determine for each DC motor, these PWM value is given as input to the DC motor via LM293D IC. The Bluetooth device will read the value of the sensor from the SJOne board through UART and send it to the Android App which will display the value of sensor as well as decision taken by robot.

DC Motor

We are using four DC motor for our project, the DC motor we are using has following rating 5-12V, 0.16Amp, 2000RPM. We are using DC motor so that we can provide 360 degree rotation to our robot wheel as well as it can help to drive the robot at a very high speed.

Proximity Sensor

This SHARP distance sensor bounces IR off objects to determine how far away they are. It returns an analog voltage that can be used to determine how close the nearest object is. These sensors are good for detection between 20cm-150cm.

LM293D IC

L293D is a typical Motor driver or Motor Driver IC which allows DC motor to drive on either direction. L293D is a 16-pin IC which can control a set of two DC motors simultaneously in any direction. It means that you can control two DC motors with a single L293D IC.

Bluetooth Module

The RN-42 is compatible with the Bluetooth versions 2 and below. The advantage of using this module is it's low power and at the same time can provide a good data rate. This provides a high performance on chip antenna where data rates upto 3Mbps are transferred. The disadvantage is that, it has a very less distance which is approximately 20 meters. There is a pull up circuit of 1k to the Vcc. This is provided so that if the input power supply has instability or tends to bounce which causes the that device to be damaged. There is separate pin allocated for the Factory Reset such that this comes into the picture when the module is misconfigured. The toggle of the specific GPIO pins indicate the status of the module. When toggled at 1Hz, the module is discoverable and is waiting for a connection. When at 10Hz, it made to change to the command mode. If it is very low, then module is already connected to another device over the bluetooth.

Hardware Interface

Pin connections for IR sensor through ADC:


Pin connections for Motor Driver using PWM:


Pin connections for Bluetooth Device for Andoird App

Software Design

On Start of the ROBOT, the ADC is initialised for the reading the data. This is used to calculate which zone the object lies. Based on this decision, the robot has to decide whether it should follow, stop or turn in any other direction. This is performed by initialising the PWM. If any other obstacle comes in between the range of the object and the robot, then the buzzer is activated and hence buzz sound is produced. The Bluetooth for the UART is initialised so that this is used for the communication between the Android application and ROBOT. With the help of the Application the Robot is started. This activates the sensor task so that data is read from all the three sensors. Based on the sensor readings and after the normalization of the data read, decision is made on which direction the Robot should move. Using the Motor Driver Task and with the help of the decision made, the motors are made to rotate in the appropriate direction. Finally, the values and the direction which are decided are sent to the Bluetooth task. This task functions in transmitting and receiving the data to the android application. This application also used to start and stop the robot.

In the Motor Driver task, the finite state machine is read for each entry of the sensor data. Based on the state machine the Robot decides on the direction to move. If the decision made is forward, then the front two wheels which are connected to the driver are made to move. This causes the device to move forward. If it is forward left, then the front left wheel’s speed is decreased. This causes the device to turn left. If it is forward right, then the front right wheel speed is decreased. This causes the device to turn left. If the decision made is reverse, the wheels are made to rotate in the opposite direction. If it is reverse left, then the back left wheel’s direction is opposite and the speed is decreased. This causes the device to turn reverse left. If it is reverse right, then the back right wheel’s direction rotates in the opposite direction and the speed is decreased. This causes the device to turn reverse right. With the help of all the decisions, the Robot can be made to rotate 360 degree making the Robot to detect the object’s range and moving in appropriate direction. Finally, after Robot has moved such that the object comes into the ZONE_2, all the state machines are reset. This loop occurs until there is an indicator received telling the Robot to stop.

In the Sensor Driver Task, the sensor values from all the three proximity sensors are read. They are normalized by using calculating the mean of the previous 30 sensor values. Based on this, the object position is determined. If the object is located in the Zone 1 of the middle sensor, then the finite state machine is changed to reverse. The robot moves until the original position is achieved. If the object is located in the       Zone 3 and Zone 4 of the middle sensor, then finite state machine is moved to the Forward state which causes the robot to move forward. The left sensor detects the object if it is in Zone 1 and Zone 2. Based on the decision, the finite state machine is changed to reverse right. This moves the robot in the reverse right direction causing the direction of the robot to turn left. The right sensor detects the object if it is in Zone 1 and Zone 2, and the finite state machine is moved to the reverse left. This causes to change the direction of the robot to the right.  The left sensor detects the object if it is in Zone 3 and Zone 4. Based on the decision, the finite state machine is changed to forward left. This moves the robot in the forward and left direction causing the direction of the robot to turn left. The right sensor detects the object if it is in Zone 3 and Zone 4, and the finite state machine is moved to the forward right. This causes to change the direction of the robot to the right. Thus based on the sensor values, the next stage of the Finite State Machine is decided and moves to that particular state.

Implementation

Proximity Sensor:
To determine the distance of object from robot with the help of proximity sensor we follow the below steps.
1. The proximity sensor detect the object present in front of it, based on object distance from it, it generate the analog value.
2. The analog value is given as input to ADC which converts this analog value to digital value.
3. Based on the digital value of all the three sensors a normalized algorithm is used which calculate the exact distance of object from sensor.

DC Motor:
To move the robot in a particular direction based on object movement we follow the below steps.
1. Based on the calculated distance from proximity sensor the PWM value is given to different motor.
2. The PWM act as input to the motor via L293D IC, based on this value the motor will accelerate.

Bluetooth Module:
To display the sensor value as well as decision taken by the robot on Android Application we follow the below steps.
1. The sensor value as well as decision taken by robot is send to the Bluetooth UART pin by the UART present on the SJOne board.
2. The UART of the Bluetooth send the data it received wirelessly to the Android device to which it is connected.
3. The Android Application display the data it received wirelessly from the Bluetooth module to which it is connected.

Movement of robot according to the movement of object
When the object which the robot is following is in ZONE_CLOSE range with respect to middle sensor than the robot will move backward, when the object is in ZONE_IN range with respect to middle sensor than the robot will remain in stationary state, when the object is in ZONE_FAR range with respect to middle sensor than the robot will move forward and start following the object, when the object is in ZONE_TOO_FAR range with respect to middle sensor than the robot will move towards the object at very high speed. When the object is in ZONE_OUT_OF_RANGE than the robot will remain stationary and will notify that the object is out of range.
When the object tries to take left/right turn than it will move ZONE_OUT_OF_RANGE with respect to middle sensor but the left or right sensor will detect the object and move the robot accordingly till it come in ZONE_IN range with respect to middle sensor.

The four LED’s present on the SJOne Board indicate the movement of the robot in the following way.
When the 1st and 4th LED is blinking simultaneously very fast than the robot is at stationary state and it is waiting for the object to come in its range i.e. object is in ZONE_OUT_OF_RANGE.
When the 1st and 4th LED and 2nd and 3rd LED are blinking alternately than it indicate the object is in ZONE_IN range.
When the 1st and 4th LED is blinking simultaneously than it indicates that the robot is moving in REVERSE direction so the object is in ZONE_CLOSE range.
When the 2nd and 3rd LED is blinking simultaneously than it indicates that the robot is moving in FORWARD direction so the object is in ZONE_TOO_FAR or ZONE_FAR range.
When the 3rd and 4th LED is blinking simultaneously than it indicates that the robot is taking RIGHT turn so that the robot can come in ZONE_IN range with respect to object.
When the 2nd and 1st LED is blinking simultaneously than it indicates that the robot is taking LEFT turn so that the robot can come in ZONE_IN range with respect to object.
When only 4th LED is blinking than it indicates that the robot is taking BACK RIGHT turn so that the robot can come in range with respect to object.
When only 1st LED is blinking than it indicates that the robot is taking BACK LEFT turn so that the robot can come in range with respect to object.
When all the four LED is blinking simultaneously than it indicate that the robot has detect some obstacle in its range.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

My Issue #1

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

Send me your zipped source code and I will upload this to SourceForge and link it for you.

References

Acknowledgement

We would like to acknowledge and thank Preet for helping us with the Sensor Interface and its issues.

References Used

link LPC_USER_MANUAL

Appendix

You can list the references you used.