1. This is where our design begins This is the Compressor which builds the necessary pressure to operate the Pneumatics, and is stored in the blue container.
2 a. Here if the marbles are small enough, (either the wood or metal) the follow the track down the track where the heavier one (metal) will go past the spring and the lighter (wood ) will "spring backwards to a different bin
2. b. If the marble is too large to fit into wood and metal marble track it is stopped in front of the Pneumatic device which launches it onto another track.
4. On the next track the marble is stopped by our gate which is programed to hold the marble in place in front of the Photosensor to get an accurate reading of the marbles translucency.
5 Last, depending on what reading the photosensor gets it will fire one or none of the Pneumatics to either guide the marbles off the track or let it follow it all the way down the track.
6. Here is our main program. This program is responsible for seperating the metal/wooden marbles from the glass marbles (discussed in part 2)
7. Next, we have our glass program.
This was the part of the programming that took the most time to complete. We had to spend quite a few class periods to finally find the values that worked. When the marble arrives at the photoresistor, this program dictates what happens based on that reading. If the photo resistor gets a reading less than 240, it moves onto the next branch of the program. If its more than 240, the marble is placed in the bin on the right. The next branch takes that reading and if it is more than 200, then it is placed in the bin on the left. If it is less than 200, then nothing happens and it rolls into the bin waiting at the bottom of the ramp.
8. Lastly, we have our gate program. This program is responsible for controlling the gate that keeps the marble in the photoresistor long enough for it to get a reading.
We had to find times that worked so that the gate did not move to a different spot at any point during the trial. We found that the gate moved faster going down than it did going up, so, as you can see in the program, we made it go 1.5 seconds up and 1.4 seconds down to combat this problem.
Good job modularizing your program and explaining the functionality of each sub-program.
ReplyDelete