Presentation is loading. Please wait.

Presentation is loading. Please wait.

FRC Team #1714. Team #1714 Introductions Project Leader:Michael Wittman - FRC Team #1714 Project Members: From Team #1714: Sarah Wittman, AJ Rehfeldt,

Similar presentations


Presentation on theme: "FRC Team #1714. Team #1714 Introductions Project Leader:Michael Wittman - FRC Team #1714 Project Members: From Team #1714: Sarah Wittman, AJ Rehfeldt,"— Presentation transcript:

1 FRC Team #1714

2 Team #1714 Introductions Project Leader:Michael Wittman - FRC Team #1714 Project Members: From Team #1714: Sarah Wittman, AJ Rehfeldt, Joey Laabs, Collin Matthews, Owen Davies, Ben Knappenberger, Johnny Ensign, Jason Bacon, Brian Cieslak, Dennis Miller, Bill Gierach From Team #537: Matt Kline, John Byrne From Team #269: Jon Stieber

3 Team #1714 Thank you Sponsors Discovery World Museum For hosting this webcast event Rockwell Automation: For their support of FIRST and More Robotics, funding expenses relating to Beta testing.

4 Team #1714 Beta Test Process

5 Team #1714 Beta Test Process Teams were required to test the 2009 FRC Control System as instructed in Section 0 of the Beta test manual. This document is available on the FIRST website under documents and updates-2009 Control system. Or it can be found at this link: http://www.usfirst.org/community/frc/content. aspx?id=10934

6 Team #1714 Beta Test Process

7 Team #1714 Beta Test Process Fear not All FRC teams have an advantage because of what Beta teams went through in this process. I suspect that once you start working with the new control system you will find it to be very robust as well as easy to use.

8 Team #1714 Introducing The 2009 FRC Control System

9 Team #1714 What’s next? What will FIRST suggest you do when you receive your 2009 FIRST Control System? As of the creation of this presentation, we don’t know… But we recommend you perform the benctop test just as the Beta test teams did. Why? Familiarize yourself with the components. Verify function of components. Start writing and testing code while robot is being built. Gain confidence and increase comfort working with new system. Its an easy way to learn what you need to know to get your control system up and running quickly.

10 Team #1714 Understanding the Documentation

11 Team #1714 Task 1 – Benchtop test Divide and conquer The benchtop test is simply setting up the control system on a benchtop and running the default code in the cRIO and Driver Station.

12 Team #1714 Task 1 - What is a WAGO Connector? Before using the WAGO Connectors please read the document titled, Making Wago 745 Connectors Work for You These are located on the Power distribution Board.

13 Team #1714 Task 1 – Wire The Components. 1. Conect Anderson connector to circuit breaker 2. Wire circuit breaker to the power distribution board 3. Wire cRIO to power distribution board 4. Install and wire Analog Bumper 5. Install and wire pneumatic Bumper 6. Wire Digital Sidecar 7. Wire speed controllers 8. Wire motors to speed controllers (remember to secure motors before testing) 9. Connect Wireless Bridge

14 Team #1714 Task 1 – Benchtop test Once it is wired it should look like one of these.

15 Team #1714 Task 1 – Connect Drivers Station Once it is wired it should look like one of these.

16 Team #1714 Task 1 – test it! Once you have the Driver Station connected and ready you can benchtop test your system. It is important that you power up and power down in the proper sequence. Power on 1. Drivers Station (wait until it boots up before turning on the cRIO) 2. Power up the Robot Power down 1. Turn off the robot 2. Turn off the Drivers Station.

17 Team #1714 Task 1 - Wireless set up Set up is similar to setting up a wireless network. Follow the instructions carefully. You will configure the IP address using you team number in place of xx.yy. For example our team would use 10.17.14.1

18 Team #1714 Task 2 2 Programming using Windriver Programs are organized into Projects Projects are built into.out files.out files are sent to the robot and run

19 Programming using Wind River Programs are organized into Projects Projects are built into.out files.out files are sent to the robot and run

20 Building a Project To build a project, Right-Click on it and select 'Build Project' Once built, a.out file will exist. To download it to the robot, the FIRST Downloader must be configured.

21 Team #1714 Sensors installed

22 Configuring the FIRST Downloader Go to Window > Preferences Select 'FIRST Downloader Preferences in the bar on the left Set your Team Number Click Browse to locate the.out file Click 'OK'

23

24 Downloading to the Robot Ensure that the robot is turned on and connected Select FIRST > Download Make sure the transmission is completed Reboot the Robot for the code to take effect

25

26 Team #1714 Things we like wireless programming and debugging Power distribution board

27 Team #1714 Tips & Tricks do not try to weight reduce any of the components other than removing unused modules from the cRIO. document flow is not always linear, remember pointing document concept WAGO connectors will break if not handled correctly Power up Driver Station then robot, power down robot then Driver Station. remember to update the software, driver station, and cRIO with the latest releases from FIRST.

28 Team #1714 Favorite Web Links 2009 Control System Intro Video - http://forums.usfirst.org/showthread.php?t=9802 Favorite one stop shop of web links - http://controlsystem.neofra.com/http://controlsystem.neofra.com/ FIRSTforums 2009 Control System - http://forums.usfirst.org/forumdisplay.php?f=743


Download ppt "FRC Team #1714. Team #1714 Introductions Project Leader:Michael Wittman - FRC Team #1714 Project Members: From Team #1714: Sarah Wittman, AJ Rehfeldt,"

Similar presentations


Ads by Google