Difference between revisions of "FTC 7314 Engineering Notebook 2014-12-30"

From DEW Robotics
Jump to: navigation, search
(Competition Season Meeting)
(Competition Season Meeting)
Line 5: Line 5:
 
!Meeting Date !!Meeting Time !!Location !!Attendees
 
!Meeting Date !!Meeting Time !!Location !!Attendees
 
|-
 
|-
|  
+
| 12/30/14
|  
+
| 4-9pm
 
| TCHS Brandywine
 
| TCHS Brandywine
|  
+
| Nick, Laura, Akhila
 
|}
 
|}
  
Line 17: Line 17:
 
!Tasks !! Reflections
 
!Tasks !! Reflections
 
|-  
 
|-  
| '''Task in bold'''
+
| '''Learning about the IR seeker'''
 
|  
 
|  
* Bullet point for each reflection
+
* To start the meeting, Laura and Nick discussed how the IR seeker worked, so they would be better equipped to write programs with it.
 +
* We learned that there are 5 sensors inside the seeker, and you can get signal strengths for each one.
 +
* We also learned that there are 9 "zones" that use the 5 sensors. If the energy from the beacon hits two sensors, then it is in a makeshift zone between them. In the program, you can get signal strengths, or the highest powered zone. The even number zones(which are when the energy hits two sensors) are much smaller, and thus more accurate.
 
|-
 
|-
| '''Task in bold'''
+
| '''Working on Parking Zone Auton'''
 
|  
 
|  
* Bullet point for each reflection
+
* After learning about the IR seeker, Laura, Nick, and Akhila started to work on the parking zone auton.
 +
* First, we got it to work with the new schematic.
 +
* Then, the nxt started freezing. By disabling pieces of code, we determined it froze while reading the encoder counts, after searching with for the IR beacon.
 +
* After many failed attempts to fix it, we tried a technique that a LabView employee sugessted. We wrote the other values from the encoder VI to an indicator. This fixed the freeze, and we continued on.
 +
* We ran the program three times for each position of the center goal, and recorded the encoder counts and IR signal strengths. After gathering this data, we wrote an algorithm to determine the position of the center goal.
 +
* Next time we work on auton, we will be able to continue to write the code to line up with the center goal, then knock the kickstand.
  
 
|} <!-- End of tasks table; DO NOT REMOVE -->
 
|} <!-- End of tasks table; DO NOT REMOVE -->

Revision as of 23:41, 31 December 2014

Competition Season Meeting

Meeting Date Meeting Time Location Attendees
12/30/14 4-9pm TCHS Brandywine Nick, Laura, Akhila


Tasks Reflections
Learning about the IR seeker
  • To start the meeting, Laura and Nick discussed how the IR seeker worked, so they would be better equipped to write programs with it.
  • We learned that there are 5 sensors inside the seeker, and you can get signal strengths for each one.
  • We also learned that there are 9 "zones" that use the 5 sensors. If the energy from the beacon hits two sensors, then it is in a makeshift zone between them. In the program, you can get signal strengths, or the highest powered zone. The even number zones(which are when the energy hits two sensors) are much smaller, and thus more accurate.
Working on Parking Zone Auton
  • After learning about the IR seeker, Laura, Nick, and Akhila started to work on the parking zone auton.
  • First, we got it to work with the new schematic.
  • Then, the nxt started freezing. By disabling pieces of code, we determined it froze while reading the encoder counts, after searching with for the IR beacon.
  • After many failed attempts to fix it, we tried a technique that a LabView employee sugessted. We wrote the other values from the encoder VI to an indicator. This fixed the freeze, and we continued on.
  • We ran the program three times for each position of the center goal, and recorded the encoder counts and IR signal strengths. After gathering this data, we wrote an algorithm to determine the position of the center goal.
  • Next time we work on auton, we will be able to continue to write the code to line up with the center goal, then knock the kickstand.


Recorded by: Date: Journal Editor: Date: