Announcement

Collapse
No announcement yet.

Video Code Walkthrough of the FIRST® Tech Challenge (FTC) Robot Controller

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Video Code Walkthrough of the FIRST® Tech Challenge (FTC) Robot Controller

    Hello,

    We made a video code walk through to show the new development platform. In the video we go over two different op modes: a tele op mode, and an autonomous op mode where we follow around an IR beacon.

    https://www.youtube.com/watch?v=a-aX...ature=youtu.be

    Thanks!

    - Jonathan
    Last edited by Jonathan Berling; 05-14-2015, 10:16 PM.

  • #2
    wrong link?
    2015 FTC World Champion - Valley X Robotics 2844 - Founding Memeber

    Comment


    • #3
      Originally posted by R2D2 View Post
      wrong link?
      Corrected. Thank you.

      Comment


      • #4
        Thanks for this Jonathan!

        Comment


        • #5
          Thanks Jonathan,

          This was very good info.

          Question: What are the expectations for code development for the phone hosting the game-pads? For example, will it be possible to have automated op-mode changes in that phone?

          Comment


          • #6
            Originally posted by Ollie View Post
            What are the expectations for code development for the phone hosting the game-pads? For example, will it be possible to have automated op-mode changes in that phone?
            The way it is currently set up, op modes reside on the robot controller (the device on the robot). When the driver station (the device with the gamepads attached) connects to the robot controller, the robot controller will send over a list of op modes that it has been programmed with. The user then selects the op mode they want to run from the driver station. Once the user has selected the op mode, the robot controller will begin to execute that op mode.

            Comment


            • #7
              Originally posted by Jonathan Berling View Post
              The way it is currently set up, op modes reside on the robot controller (the device on the robot). When the driver station (the device with the gamepads attached) connects to the robot controller, the robot controller will send over a list of op modes that it has been programmed with. The user then selects the op mode they want to run from the driver station. Once the user has selected the op mode, the robot controller will begin to execute that op mode.
              How does that play out with the period judges need to take between autonomous and tele-op? Will we be able to stop and run no OpMode until the second half of the match starts?
              FTC6460 mentor (software+computer vision+electronics), FPGA enthusiast. In favor of allowing custom electronics on FTC bots.
              Co-founder of ##ftc live chat for FTC programming--currently you may need to join and wait some time for help--volunteer basis only.

              Comment


              • #8
                Originally posted by hexafraction View Post
                How does that play out with the period judges need to take between autonomous and tele-op? Will we be able to stop and run no OpMode until the second half of the match starts?
                Hi hexafraction,

                I believe that when the autonomous period ends, teams will stop their robots and the referees will score the autonomous points. Once the refs have completed the scoring for automous, there will be a second start for the teleop phase of the match.

                Tom

                Comment


                • #9
                  Jonathan,

                  Thank you for posting this video - it's very helpful!

                  Kind regards,

                  Norm

                  Comment


                  • #10
                    Originally posted by Jonathan Berling View Post
                    The way it is currently set up, op modes reside on the robot controller (the device on the robot). When the driver station (the device with the gamepads attached) connects to the robot controller, the robot controller will send over a list of op modes that it has been programmed with. The user then selects the op mode they want to run from the driver station. Once the user has selected the op mode, the robot controller will begin to execute that op mode.
                    Jonathan,

                    Should I interpret this that the only way to change the op mode is manually by user selection? Does this mean that there is no team developed code in the driver station and all code comes from FTC?

                    Comment


                    • #11
                      Hi Jonathan,

                      In the video, I see a DcMotor class and a Servo class. Is there a single Servo class or will there be a separate class for continuous servos that operate differently from the 180 degree servos? For example, at the end of an OpMode, a standard servo may be stopped by simply no longer updating its setting, while a continuous servo that was set to a value will keep running if the value is not reset to a particular value corresponding to a stopped state (and unfortunately that stopped state value may differ from servo to servo). Just curious how this will be handled in the new paradigm.

                      Comment


                      • #12
                        Originally posted by Ollie View Post
                        Jonathan,

                        Should I interpret this that the only way to change the op mode is manually by user selection? Does this mean that there is no team developed code in the driver station and all code comes from FTC?
                        At the beta test all of the sources for the driver station were included in the SDK. We played with some simple modifications to position/resize the telemetry window so that is was visible on our driver station (we had a phone vs. a tablet). I hope they will leave it open to modification as I think it likely people will want to customize the UI to take advantage of the telemetry functions and so on.

                        Comment


                        • #13
                          Originally posted by Robert Van Hoose View Post
                          At the beta test all of the sources for the driver station were included in the SDK. We played with some simple modifications to position/resize the telemetry window so that is was visible on our driver station (we had a phone vs. a tablet). I hope they will leave it open to modification as I think it likely people will want to customize the UI to take advantage of the telemetry functions and so on.
                          Knowing that we have a wifi direct connection, assuming it is still open to modification will we be permitted/able to open other sockets over the wifi direct link for additional telemetry/communication in both directions?
                          FTC6460 mentor (software+computer vision+electronics), FPGA enthusiast. In favor of allowing custom electronics on FTC bots.
                          Co-founder of ##ftc live chat for FTC programming--currently you may need to join and wait some time for help--volunteer basis only.

                          Comment


                          • #14
                            What software was being used for this video?

                            Comment


                            • #15
                              Originally posted by FTC6981 View Post
                              What software was being used for this video?
                              The IDE is Android Studio. http://developer.android.com/sdk/index.html

                              Comment

                              Working...
                              X