Just One More Cougar Rover Run... PDF Print E-mail
Written by Jamie Diamond   
Wednesday, 25 August 2010 22:04
Dim lights Embed Embed this video on your site

 It's late.  The Live Mission Webcast is done.  We scored 220.

 At Dave Fort's suggestion Joey and I went down to the basement and made one more run.  We turned the rings to random orientations and sent the robot off to do it's thing one more time...  It proceeded to pick up all the rings but dropped one out of the basket for another 220, but this time with random ring orientations.  And here's the on-board video.

Last Updated on Thursday, 26 August 2010 17:55
 
Cougar RoverCam on the MoonBots Live Mission Webcast PDF Print E-mail
Written by The Cougars   
Wednesday, 25 August 2010 21:56

Dim lights Embed Embed this video on your site  The Robot's eye view during our Live Mission Webcast.  We scored 220. We only attempt 250 of the possible 350 points.  We have run 310 points but it takes us about 4 minutes.

 We took 2 photos of the Heritage Artifacts.  One at long range, as we paused on the landing pad for 1/2 a second after we started the mission.  This second one as we spun and paused, after leaving the Peak of Eternal Light. 
From Cougar LEGO Robotics Team - Photos of Heritage Artifacts
Last Updated on Wednesday, 25 August 2010 22:34
 
Cougar MoonBots Programs PDF Print E-mail
Written by The Cougars   
Wednesday, 25 August 2010 15:37

These are the programs that made our robot move.

Master Control 

xMission1-V11 - This is our master program.  It calls the mission sub-programs and manages the time

Mission MyBlocks 

xStartFront2 - Start based on the Front Ultrasonic sensor.  This program will pause, give a sound, and then wait for you to wave something very close to the front Proximity (ultrasonic) sensor.  It will give a beep to confirm that you actually triggered the front prox sensor. 

MP 1v10 p1 - Mission 1 version 10 using rear prox (ultrasonic sensor) on port 1.  Cross the field, pick up the 2 yellow rings by the back wall, park on the POEL.

MP 2bv12 p0 - Mission 2b version 12 using no rear prox sensor.  Leave the POEL, photograph the Heritage Artifacts, and pick up the blue ring in the right side crater.

MP 3bv12 p1 - Missoin 3b version 12 using rear prox sensor on port 1.  Leave the right side crater. Cross to the left side of the field.  Pick up the 2 yellow rings.

MP 4bv12 - Mission 4b version 12.  Dash for home after mission 3.

MP 5v11 p1 - Mission 5 version 11.  Pick up blue ring from left side crater and then dash for home, all after mission 3.

A Sample of our Standard Movement MyBlocks

xFwdDOC - Forward Duration On Course.  This MyBlock takes 3 inputs.  Duration (in degrees of rotation of the drive motors), Power, and Compass-Course.  It takes care of everything else.

xBwdDOC - Backwards Duration On Course.  This MyBlock also takes 3 inputs.  It's like xFwdDOC except it goes backwards instead of forwards.

xFwdPOC - Forward Proximity On Course.  This MyBlock takes 3 inputs.  Proximity (in centimeters, how far you want to get to what you are approaching), Power, and Compass-Course.  It will move the robot in the direction you want, at the motor power you want, until you are the distance you want from what you are approaching.

xBwdBP1OC - Backwards BackProximity On Course.  This MyBlock takes 3 inputs. Proximity (in centimeters, how far the back Prox sensor is from what you are backing up to), Power (how fast you will go), and Compass-Course (the direction the robot should try to stay facing, so you actually travel 180 degrees from this course since you are backing up, think about facing north but backing south)

xTurnToCourse - Turn to Compass Course.  This MyBlock takes 2 inputs.  Power and Course.  Power is how fast you will turn.  Course is the direction you will end up facing.  It will make the robot turn in the shortest direction to face the new direction. 

xRampArmDown - This program uses the loop counter (divided by 3) to determine the power of a motor block lowering the arm.  It also sets a maximum speed.  This is like our Ramp Move MyBlocks from the Smart Move Challenge.  It smoothly brings a motor up to a predetermined speed. (p.s. At the time of our Live Mission Webcast the arm didn't work quite right.  We worked on it over the weekend and got it fixed.  It turns out we forgot to put a motor stop block at the end of the this MyBlock.  Fixed now and works much better.) 

Attachments:
Download this file (xMission1-V11.rbtx)xMission1-V11.rbtx[A Complete ]4131 Kb30/08/10 07:28
Last Updated on Monday, 30 August 2010 07:33
 
Cougar MoonBot photos PDF Print E-mail
Written by Dr. M. Judith Radin   
Sunday, 22 August 2010 20:52

 

 

Here are some photos of our final Cougar Moonbot.

Last Updated on Sunday, 22 August 2010 22:23
 
Cougar blog - Joey PDF Print E-mail
Written by Joey   
Sunday, 22 August 2010 14:40
Its 3:40 PM on August 22. I just got home from Canada. I am seeing the field for the  first time.  Its a lot bigger than I realized. We finished the video in Canada and are working on uploading it now. It feels good to be home but it is weird. I cant wait to see the robot run in person. Ive seen videos but never live. The robot looks good. We will do some last touches tonight. There will be no more blogging after this until the actual session so until then...Joey out.
Last Updated on Sunday, 22 August 2010 15:17
 
«StartPrev12345678910NextEnd»

Page 7 of 21
Copyright © 2017 cougarrobot.com. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.
 

FTC Blog

FIRST Tech Challenge
The official FTC Blog
  • The Game Design Committee is Accepting Applications!
    If you’ve ever been interested in participating in the FIRST Tech Challenge Game Design Committee, this is your chance! We will be accepting applications to add one member to the committee. The application will be open from 11/20/2017 through 12/18/2017 at 12:00pm EST.

    The current Game Design Committee is made up of five members, and we are looking to add a sixth member who will help the committee make progress on the 2018-2019 season game cycle. This individual will also shadow the current committee on a weekly conference call to get a feel for how the GDC supports the current season game.



    If you are interested, or know anyone interested, please feel free to pass this along! The official volunteer description, along with a link to the application are listed below.

    Game Design Committee – Volunteer Position Description
    The FIRST Tech Challenge is seeking an interested individual to serve one game cycle (approximately 18 months) as part of our Game Design Committee. The Game Design Committee is a group of volunteers who brainstorm, create, and implement all aspects of the FIRST Tech Challenge games (less production/fulfillment). As a member of the Committee, this person will be responsible for attending weekly conference calls, and providing input and creative ideas for the game currently being designed for next the season. This person will contribute to the creation of Game Manuals Part 1 and 2, and to other supporting documents needed for the game. The person in this role will provide support for the game once it is released for the current season via the Official Q&A forum. We are looking for someone who is creative, is a team player, and can meet the time commitments outlined in the job description.

    Job Description:
    • Contribute a minimum of 5 hours each week, including a weekly conference call that occurs during normal business hours (eastern time).
    • Provides input during the design phase to insure the game meets requirements outlined by FIRST.
    • Contribute to the design phase to make sure game elements meet quality standards and budget requirements.
    • Contributes to documentation and manuals needed to support the game throughout the season.
    • Provides support through the Official Q&A Forum to answer team related questions throughout the season.
    • Maintains confidentiality of all aspects of design process. 
    • Applicants must be a minimum of 25 years old.
    • Position may require a trip to FIRST Headquarters in Manchester, NH.
    • CAD experience is a plus, but not required.