We all met as a team for the first time and began to do discuss the overall design of our robot. We brainstormed all the potential sensors we would need to in order to have our robot navigate the field. The type of motor we would use that will give us the right amount of speed and right amount of torque to fit our needs of the robot.
once we had an idea of the components we would use, we came up with two prototype designs that would be presented in class and get critiqued by the TA's, tutors, and staff so that we can improve our design where needed.
The team got together after the critiquing process and went to lab to finalize the design and begin to build a 1:1 model in solid works and begin to prototype
Troy: Worked on the solidWorks and built the over components we would need to in order to see the model comes together with no problems before we cut it out and built it for real.
Omar: Started working on the tank circuit that will be used for detecting the track wire that is apart of the obstacles, he also worked on a bandpass filter that would ignore the noise coming from the motor as it runs so that it does not accidentally get triggered.
Christian: Worked drawing out the finalized design that would be built for the final project and started working on the website that would work as the lab journal for everyone.
Christian and Omar with a group of other students went to the Jameco electronics to pick up driving motors so that troy the mechanical lead can finish the design of the robot with the correct measurements. This was important for the check off on Tuesday, also when we returned Omar finished the track wire sensor and was able to detect the track wire from over 4 inches away.
Accomplished:
Troy almost finished up the design and was able to mock everything up but the bumpers and the launcher because we are waiting for the launch motors to come in through amazon
Omar finished the track wire sensor and began to plan out the design on a track wire.
Christian began to draw out the top level state machine in order to determine what are the important things we need to keep track of, and time schedules.
Omar: Redesigned and completed a new track wire sensor on the breadboard that would only use one op amp for each track wire circuit, this saves space and gives us the ability to add more sensors if we decide to use them for the final project without wasting so much space.
Troy: 90% done with the design of the droid, still waiting on the motors for the firing mechanism to come in, the online posing did not provide data sheet of any kind so we are delayed until then.
Christian: Redesigned the way the HFSM will work, added multiple substates that will make debugging easier in the long run when the FSMs become more and more complicated. Also, keeps updating the journal and the gantt chart.
Omar: Finished the Track wire sensor and the Beacon detector for the Tuesday checkoff. but decided to make a back up beacon detector just in case the one we have breaks for some reason. He redesigned the entire thing using a 2nd order butterworth bandpass filter instead of the narrow bandpass filter he had before. He also drew the block diagram to show how all the components will be connected , and the updated schematics for the new beacon detector and track wire circuit.
Troy: All our parts finally came in so he was able to finish the design of the droid in Solid works. He will try to cut out the second and third base tomorrow in order to see how the UNO block and the unidirectional H-bridge will fit because that is a tight fit.
Christian: Continued to work on the state machine diagrams that will be used for the droid, and set up the ES_framework in MPLabX so that the team can begin programing as soon as the IR sensors are done. Helped with the block diagram while Omar started working on the second beacon detector.
Block Diagram:
Beacon Detector:
Track Wire :
Today we checked off for the first checkoff of many to come. Omar our Electrical Lead used the new beacon detector circuit, the new design was able to attenuate the signals we were trying to ignore very well. The original beacon detector we had had a maximum range of 7 feet which would not be enough to reach the other end of the board since each side of the field has a dimension of 8x4 the new design that we implemented was able to get as close as 1" to the beacon and had a full accurate distance of roughly 20' from the beacon, the final design is posted below.
The second thing that got checked off was the over all design of our robot. The design was done using SolidWorks. Our mechanical lead Troy was able to finish a preliminary final design so that all we had to do as we continued on our project would be small design changes instead of time consuming. images are also below, the body of our design is a 6" x 4.5" x 9" which makes it really compact but a little tall . The rules give us a max size of 11 x 11 x 11 and must fit within what is known as the cube of compliance. The cube of compliance is a metal cube that the bot must fit into or else they are disqualified from the competition. Images are also posted below.
Christian worked making test harnesses for the motors. He made a test harness that would toggle the the enable output pin to change the direction of the motor. he connected the UNO stack output pins to the H-Bridge that would be powering bot the driving wheels and noticed that there was a lot of noise coming out of the outputs. This was because everything being powered from the power distribution board on the UNO stack needed to have a common ground. This was fixed by making a common ground hub. This solution should reduce the amount of noise overall.
Motor Testing :
Updated circuit design for the new beacon detector:
Preliminary final design of the bot:
Top View
Side View
Back View
Front View
For the third week of the project. We focused on getting synchronous sampling. we thought this would be a good idea because even though we would always be working in the lab for almost the entire duration of the lab, checkoff will be held in a different room and the lighting in the other room will not match ours meaning that if you decide to go with a hysteresis bounds to determine your thresholds for when your droid is on the tape or off the tape, you will run into trouble because that will change depending in the room you are in and even the room for the competition will have different lighting making it difficult to choose proper hysteresis bounds. Synchronous sampling will help with that because we will take a reading when our tape sensors are off and when our tape sensors are on then subtract the difference to get rid of any noise that is around making simple to detect when we are off and on the tape. The video show the IR(Tape) sensors turning on and off.
The Circuit for the Tape sensors
The Circuit for our Bumpers