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
  • Exciting Changes to Match Play
    Over the past decade, FIRST® Tech Challenge has continued to grow, serving the FIRST mission of creating excitement and exposing students to the wonderful world of science, technology, engineering and math. With growth, must come change, as most of our community has seen through our evolution of robot technology. We continue to work to make this program more accessible and affordable, while still engaging and challenging students of all skill levels.


    Since the 2015 season, FIRSTTech Challenge has moved away from a centralized control system to the Android based platform you see today. The increased reliability of the Android based/REV platform, is allowing us to improve the flow of the matches. We are making significant and exciting changes that teams and volunteers need to be aware of for the 2017-2018 season.



    Autonomous to Driver Controlled Transition

    Starting in the 2017-2018 season, there will no longer be a hard stop following the autonomous period to transition to the driver controlled period of the match. Once the autonomous portion of the match ends, the emcee/game announcer will tell the teams to pick up their driver station. As a visual cue, the scoring system will display to teams that they must pick up their driver station. Teams will only have 5 seconds to pick up their driver station, so they should make sure to pay close attention! After the 5 seconds, there will be a 3-2-1 countdown and the driver controlled period of the match will begin right away.

    Why make the change?
    • Since the reliability of our technology has come so far, the large gap between autonomous and driver controlled periods of the match is no longer necessary.
    • The game design doesn’t require field reset between the autonomous and driver controlled periods.
    • The shortened break between autonomous to driver controlled period increases engagement by keeping the excitement of the match going.
    • The shortened break will encourage teams to build smarter and create sturdier robots, that can move successfully from autonomous to driver controlled unhindered.
    What does this mean to teams?

    Teams must remember is to keep an eye on the match timer display, and listen for the cues from the Emcee or Game Announcer to pick up their driver stations. The transition will happen quickly, and the scoring system will automatically run the rest of the match. Since the robots are not tied directly to the scoring system, teams must make sure they are ready to run their driver controlled programs after the 3-2-1 countdown.

    How does this impact the number of matches played?

    This will not impact the number of matches played at an event. From League Meets to State Championships, teams will still be able to play between 5 and 6 matches, depending on the specific tournament. Teams will still receive a minimum of 7 minutes between each match. Super Regionals and World Championship events will have additional matches. The number of matches at these events will be announced at a later date.

    Up righting/Untangling/Reconnecting Robots

    Because of the shortened transition from autonomous to driver controlled period, field personnel will no longer enter the field to upright or untangle any robots. Robots that have lost connections will not be reconnected by the Field Technical Adviser. Teams should take this into consideration when building and designing their robot.

    If you have any questions about the new changes to our match play format please email ftcteams@firstinspires.org. Happy Relic Recovering!

    Click here to watch the New Changes to  Match Play video on YouTube!