Team Four/Journal
| Line 12: | Line 12: | ||
At our meeting tonight we got our strategy and mechanical design mostly flushed out. Our cad model is coming along, and if we get our t-bolting to work the first time we can have a completed robot base within the next two days! ;) We also got a jump start on playing with vision code, however no significant progress has been made so far. | At our meeting tonight we got our strategy and mechanical design mostly flushed out. Our cad model is coming along, and if we get our t-bolting to work the first time we can have a completed robot base within the next two days! ;) We also got a jump start on playing with vision code, however no significant progress has been made so far. | ||
| + | |||
| + | '''Day Three''' | ||
| + | |||
| + | Today was a rather successful day. We have a moderately complete Finite State Machine laid out, and we have planned much of our software architecture. We were able to complete the day's checkpoint without much hassle and are working to implement some of the suggestions offered by the staff regarding both the software and mechanical aspects of our design. | ||
| + | |||
| + | In addition, we have made some good progress in our vision code. By the end of the night we were able to identify red blotches in static images, and have almost finished implementing some basic edge detection with a Hough transform. Early tomorrow we should be able to identify red balls in images and determine their location relative to the front of the robot. We expect to apply this code to the video stream from our webcam at some point tomorrow as well, allowing us to implement a basic PID aiming function and align the front of the robot with the balls on the field. | ||
| + | |||
| + | In addition to this software progress, the mechanical design has made a lot of headway as well. We've decided to use a total of 4 motors and 2 servos to control our mechanisms. This number has been changing a lot over the last few days, but we believe that we have settled on a design that is both robust and mechanically simple(r). We've replaced the small, shady kit motors with more powerful Trossen motors from the stock bin for use in our drive train, and relegated one of the kit motors to the front roller. We designed a right angle gearbox for the motor we ordered yesterday, allowing us to power the hopper from the base. There will also be room in the base to mount the Arduino and the Dagu controller. This will keep our power and mechanical elements more consolidated and our total center of mass much lower. In addition, the basic design of the hopper is complete, and over the next few days all of the acrylic plates can be cut out and we can start assembly. Hopefully we will have a drivable base with a working roller on the front by Friday! | ||
Revision as of 06:24, 10 January 2013
Day One
Today is one of those days where everything that can go wrong, will go wrong. In lab we promptly shorted out our battery (luckily we had properly hooked up the fuse) and right before finishing code for checkpoint two we accidentally plugged something somewhere it wasn't supposed to go and released the magic blue smoke from our motor controller. ヽ(`Д´)ﾉ ┻━┻
The end of the day is starting to look up though. We have most of the critical modules of our robot SoldidWorksed, as of right now we're in the process of adding in the specifics such motor mounts and standoffs. Hopefully by the end of tomorrow we will have everything finalized so we can cut out the relevant parts out of acrylic in Edgerton. We found these amazing motors that fulfill all of the requirements for operating our hopper and ball collection system, and put in an order for it. It should arrive sometime between Friday and Wednesday.
Tomorrow aside from lecture we plan on replacing our motor control and getting checkpoint two to work before leaving. I am also going to Edgerton to get training so I can use their laser cutter.
Day Two
Today was much better than the day before. We got our power cable re-soldered to the switches make sense, making it impossible to short out our board like we did the day before. Lesson learned. Q(^_^Q ) After a little fiddling with our code we finally got our checkpoint two to work. It turned out our bump sensor needed a pull down resistor, because otherwise it was acting as an antenna and every time one of us got close to the robot it activated the switch, which gave the appearance that the code wasn't working. Just goes to show you all the small things you don't really consider while soldering up electronics that can really mess you up. We'll be twice as vigilant in the future.
At our meeting tonight we got our strategy and mechanical design mostly flushed out. Our cad model is coming along, and if we get our t-bolting to work the first time we can have a completed robot base within the next two days! ;) We also got a jump start on playing with vision code, however no significant progress has been made so far.
Day Three
Today was a rather successful day. We have a moderately complete Finite State Machine laid out, and we have planned much of our software architecture. We were able to complete the day's checkpoint without much hassle and are working to implement some of the suggestions offered by the staff regarding both the software and mechanical aspects of our design.
In addition, we have made some good progress in our vision code. By the end of the night we were able to identify red blotches in static images, and have almost finished implementing some basic edge detection with a Hough transform. Early tomorrow we should be able to identify red balls in images and determine their location relative to the front of the robot. We expect to apply this code to the video stream from our webcam at some point tomorrow as well, allowing us to implement a basic PID aiming function and align the front of the robot with the balls on the field.
In addition to this software progress, the mechanical design has made a lot of headway as well. We've decided to use a total of 4 motors and 2 servos to control our mechanisms. This number has been changing a lot over the last few days, but we believe that we have settled on a design that is both robust and mechanically simple(r). We've replaced the small, shady kit motors with more powerful Trossen motors from the stock bin for use in our drive train, and relegated one of the kit motors to the front roller. We designed a right angle gearbox for the motor we ordered yesterday, allowing us to power the hopper from the base. There will also be room in the base to mount the Arduino and the Dagu controller. This will keep our power and mechanical elements more consolidated and our total center of mass much lower. In addition, the basic design of the hopper is complete, and over the next few days all of the acrylic plates can be cut out and we can start assembly. Hopefully we will have a drivable base with a working roller on the front by Friday!
