UNT Research Experiences for Teachers: Robotics project
Jun 27, 2012
Week 3: Day 13
Out
in the morning - sick child. Liz worked on our presentation and we
were given more specifics for the presentation on Friday. So this
afternoon, we were researching several websites that aid us in defining
our Garcia Robot here at UNT as well as how what we learn here will
translate into our classrooms. All of this research will be presented
on Friday.
Week 3: Day 12
We
spent the morning working on our lesson plan, filling in some details
and identifying corresponding TEKS. We also worked on the midterm
presentation.
Jun 26, 2012
Week 3: Day 11
June 26, 2012
Liz and I looked at more research regarding RF transeivers. We continued to document our research and started building our presentation for Friday. We also continued our lesson plans while building our literature review to be used for our final paper.
We built two NXT “Explorer” robots and programs. The robots randomly search an area and detect and avoid obstacles. It utilizes two different sensors. One is ultrasonic and one is touch. If either sensor determines that the robot is at the end of its current path, the robot stops, looks for the most open path and turns in that direction to continued its most unencumbered movement. To test them, we had a “battle bot” between them to see which would “win”. In a confined environment, they will periodically cross paths and have to avoid each other. On less frequent occasions, they run into each other and avoid each other. Even less frequently, they run into each and get stuck.
Aside from the randomness of the search patterns (which cannot easily be controlled with them at this time), the operation was a great deal of fun!!!
Liz and I looked at more research regarding RF transeivers. We continued to document our research and started building our presentation for Friday. We also continued our lesson plans while building our literature review to be used for our final paper.
We built two NXT “Explorer” robots and programs. The robots randomly search an area and detect and avoid obstacles. It utilizes two different sensors. One is ultrasonic and one is touch. If either sensor determines that the robot is at the end of its current path, the robot stops, looks for the most open path and turns in that direction to continued its most unencumbered movement. To test them, we had a “battle bot” between them to see which would “win”. In a confined environment, they will periodically cross paths and have to avoid each other. On less frequent occasions, they run into each other and avoid each other. Even less frequently, they run into each and get stuck.
Aside from the randomness of the search patterns (which cannot easily be controlled with them at this time), the operation was a great deal of fun!!!
Jun 25, 2012
Week 2: Day 10
June 22, 2012
I tried to get the NXT working - there are continued battery issue (we don't have any). Jennifer found some rechargeable batteries and a charger for the battery pack. I plugged all of them in to charge them.
I finally figured out some basic programming for the NXT's. I wrote a simple program. When the battery pack had some charge, I tried to download it to the NXT. The driver for them needs to be installed, however, so I was unsuccessful (I do not have the permissions to install the driver). Instead, I used the NXT directly with some of the basic commands to drive the robot around a little bit.
I also spoke with Eduardo about the programming. There is an issue with the distance traveled down the hallway. The robot cannot treat the distances independently. Therefore, if an obstacle is encountered, the robot would not make it to the end of the hall (the total distance would remain the same). As a result, we are going to try to treat the entire path down the hall as a variable. If a turn is made, the total distance will increased and the robot will travel down the hallway until the total distance is reached.
I tried to get the NXT working - there are continued battery issue (we don't have any). Jennifer found some rechargeable batteries and a charger for the battery pack. I plugged all of them in to charge them.
I finally figured out some basic programming for the NXT's. I wrote a simple program. When the battery pack had some charge, I tried to download it to the NXT. The driver for them needs to be installed, however, so I was unsuccessful (I do not have the permissions to install the driver). Instead, I used the NXT directly with some of the basic commands to drive the robot around a little bit.
I also spoke with Eduardo about the programming. There is an issue with the distance traveled down the hallway. The robot cannot treat the distances independently. Therefore, if an obstacle is encountered, the robot would not make it to the end of the hall (the total distance would remain the same). As a result, we are going to try to treat the entire path down the hall as a variable. If a turn is made, the total distance will increased and the robot will travel down the hallway until the total distance is reached.
Jun 22, 2012
Week 2: Day 9
June 21, 2012
I
saw Prof Namuduri on my way in. He provided the 2nd NXT to us. In the
mean time, we continued to research the possibility of designing and a
building a RF beacon for our rockets. The further we go, the more
likely it seems that it is implausible. There are some very cheap “off
the shelf” systems already available.
As we were realizing this, Prof Namuduri came in and told us that Eduardo (our exchange student from Mexico) has gotten object detection working. In other words - we are back in business!!!
We took previous flowcharts and simplified them to help build baby steps:
Step 1: drive around in a box (completed)
Step 2: avoid a simple object while driving around the box (we are almost here - there is still a little work to do)
Step 3: Avoid any object while driving around a box.
All three flowcharts were completed and provided to Eduardo. He is excited about completing this programming challenge!!! He would like to get started on the most difficult, but we dialed him back. We will stay on task and complete baby step 2.
At 3 pm, we joined a seminar on wire sensors and networks - this took the remainder of the afternoon!
As we were realizing this, Prof Namuduri came in and told us that Eduardo (our exchange student from Mexico) has gotten object detection working. In other words - we are back in business!!!
We took previous flowcharts and simplified them to help build baby steps:
Step 1: drive around in a box (completed)
Step 2: avoid a simple object while driving around the box (we are almost here - there is still a little work to do)
Step 3: Avoid any object while driving around a box.
All three flowcharts were completed and provided to Eduardo. He is excited about completing this programming challenge!!! He would like to get started on the most difficult, but we dialed him back. We will stay on task and complete baby step 2.
At 3 pm, we joined a seminar on wire sensors and networks - this took the remainder of the afternoon!
Week 2: Day 8
June 20, 2012
We received direction this morning to proceed utilizing the Lego Mindstorms only. We are to try to get them to link together to perform tasks. We are to try to utilize sensors or optics to determine obstacles size. Potential issues include the resources for this. We don’t know if we have any of the necessary materials for this.
More direction from Prof. Thompson: Perhaps determine a way to go find a lost rocket - our original idea. We are conducting research into the feasibility of this compared to working with the NXT’s. We will have a decision sometime tomorrow.
After lunch, we went to the Discovery Park Engineering Library for another session on using the library resources. As a group, we also discussed stumbling blocks everyone was facing and the confusion on what our final products are to be. There is a lot of confusion about the final paper, as far as content and format, and Sharon will get with Dr. Acevedo as soon as possible to clear this up.
We received direction this morning to proceed utilizing the Lego Mindstorms only. We are to try to get them to link together to perform tasks. We are to try to utilize sensors or optics to determine obstacles size. Potential issues include the resources for this. We don’t know if we have any of the necessary materials for this.
More direction from Prof. Thompson: Perhaps determine a way to go find a lost rocket - our original idea. We are conducting research into the feasibility of this compared to working with the NXT’s. We will have a decision sometime tomorrow.
After lunch, we went to the Discovery Park Engineering Library for another session on using the library resources. As a group, we also discussed stumbling blocks everyone was facing and the confusion on what our final products are to be. There is a lot of confusion about the final paper, as far as content and format, and Sharon will get with Dr. Acevedo as soon as possible to clear this up.
Jun 20, 2012
Week 2: Day 7
June 19, 2012
Received NXT robot this morning. Build minibot to drive around to test our flowchart / plan. Tried the batteries in the controller. They are not working. It appears they need to be charged. Looked at the programming for the NXT’s. We will need some time to figure this out.
We went to the Garcia Robot Lab. The robots can drive fairly successfully in a square. It seems to have some glitches and we will have to work them out.
We went to a three hour LabView training seminar in the afternoon.
Received NXT robot this morning. Build minibot to drive around to test our flowchart / plan. Tried the batteries in the controller. They are not working. It appears they need to be charged. Looked at the programming for the NXT’s. We will need some time to figure this out.
We went to the Garcia Robot Lab. The robots can drive fairly successfully in a square. It seems to have some glitches and we will have to work them out.
We went to a three hour LabView training seminar in the afternoon.
Subscribe to:
Posts (Atom)