... | ... | @@ -127,9 +127,9 @@ In the lesson plan, an alternative build is presented (see Figure 5, "Figure 6" |
|
|
|
|
|
### Vehicle 3
|
|
|
|
|
|
We chose to create the robot by combining sound sensors and light sensors.
|
|
|
The lesson plan's first suggestion is to use a light sensor and an ultrasound sensor, but we chose to follow the alternative suggestion of using a sound sensor instead of an ultrasound sensor. We thus constructed the robot by combining sound sensors and light sensors.
|
|
|
|
|
|
Based on our knowledge from the last exercises, we can see from figure 7 that the robot will seek both light and sound, since the sound sensors have a 'straight' connection to the motors and are inhibitory, causing the robot to steer towards sound, and the light sensors have a 'crossed' connection to the motors, but are exitatory, and as such cause the robot to steer towards light sources as well.
|
|
|
The illustration in Figure 6 ("Figure 7" in the lesson plan) shows the sound sensors with a direct, inhibitory connection to the motors, while the light sensors have a 'crossed', exhibitory connection to the motors. Based on our experiences in the previous exercises, we can infer from this that the robot will steer towards both light and sound.
|
|
|
|
|
|
We wrote a program **RaveBot.java** that tries to seek towards places with both high sound and high light levels. The program is mostly a mash of our previous programs **SoundLover.java** and **LightLover.java**, where we simply add together the two values received from the sensors, and then dividing by two (halfing each sensors impact), and then using the value as motor power for the appropriately connected motor, according to the drawing in figure 7. The result can be seen in video [RAVE BOT TIME]
|
|
|
|
... | ... | |