... | @@ -195,8 +195,23 @@ |
... | @@ -195,8 +195,23 @@ |
|
> ## Exercise 6 - Party Finder Robot
|
|
> ## Exercise 6 - Party Finder Robot
|
|
>
|
|
>
|
|
> #### Task
|
|
> #### Task
|
|
|
|
> To make a party finder robot which detects and drives in the direction of the loudest sound.
|
|
>
|
|
>
|
|
> #### Plan
|
|
> #### Plan
|
|
|
|
> We intended to mount two sound sensors on the robot [fig. ??] and use the readings from these sensors to always
|
|
|
|
> drive towards the location with the loudest sound level.
|
|
|
|
>
|
|
|
|
> The two sound sensors were mounted on the opposite sides of the robot facing away from each other at a 90 degree
|
|
|
|
> angle (perpendicular to each other), as can be seen in fig. ??.
|
|
|
|
>
|
|
|
|
> We wrote a class called NoiseFinder using eclipse with the LejOs plugin. The class imported a number of LejOs
|
|
|
|
> features, but primarily sensorPort and soundSensor were the ones we used during this exercise.
|
|
|
|
> The primary feature of the class was to constantly compare the decibel measurements of the two sound sensors with a
|
|
|
|
> set decibel threshold. If the noise level on one of sound sensors was above the given threshold, and larger than
|
|
|
|
> that of the opposite sound sensor, the robot would turn in the direction of the loudest noise. This was simply done
|
|
|
|
> with three part if, else if & else loop [fig. ??]. This of course meant that the robot only could drive to the
|
|
|
|
> right, left and straight ahead. If no sound was detected above the sound threshold, the robot would simply drive
|
|
|
|
> straight ahead at a reasonable pace.
|
|
>
|
|
>
|
|
> #### Results
|
|
> #### Results
|
|
>
|
|
>
|
... | | ... | |