Announcement

Collapse
No announcement yet.

Youtube videos about using App Inventor for autonomous mode

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

  • #16
    Originally posted by Westside View Post
    In Lesson 6, is it necessary to set the mode to Run_to_Position? It seems the program is not using that capability. Instead it's testing the encoder values directly.
    As I recall, yes, it was necessary. You could try a different mode but that's the one I used to get it to work.
    ...Bruce

    Comment


    • #17
      Hi,

      Our team followed everything we could to do the Color Sensor program lesson. We think we are messing up the Configuration part of it. The robot is not stopping at the blue line, it just keeps going and going and going.

      https://www.dropbox.com/s/tx3fzsa3l3...error.pdf?dl=0 Here is a picture of our configuration app page where we are getting stuck (when I took the picture, the robot was not on, so disregard that note). Our color sensor it plugged in at the 4th one as shown in the picture. I don't think we configured the color sensor correctly.

      Also, if we get that to work, then we were wondering, how do we program the robot to stop at white instead of blue? Is there a different set of number values?

      Thanks for any help.

      Comment


      • #18
        Originally posted by RoboticsFun View Post
        Hi,

        Our team followed everything we could to do the Color Sensor program lesson. We think we are messing up the Configuration part of it. The robot is not stopping at the blue line, it just keeps going and going and going.

        https://www.dropbox.com/s/tx3fzsa3l3...error.pdf?dl=0 Here is a picture of our configuration app page where we are getting stuck (when I took the picture, the robot was not on, so disregard that note). Our color sensor it plugged in at the 4th one as shown in the picture. I don't think we configured the color sensor correctly.

        Also, if we get that to work, then we were wondering, how do we program the robot to stop at white instead of blue? Is there a different set of number values?

        Thanks for any help.
        The Modern robotics is an I2C Device so you'll want to select that menu, Select Color Sensor under the port number matching the port where you have it plugged in and then enter the name that you assigned the sensor in Designer mode. The ports on the Core Device Interface module are number from the bottom up with the bottom one being 0.

        Your team should review the first part of the YouTube video to gain an understanding of how color is handled and think about what makes up the color white.

        ...Bruce

        Comment


        • #19
          Originally posted by schaferbw View Post
          The Modern robotics is an I2C Device so you'll want to select that menu, Select Color Sensor under the port number matching the port where you have it plugged in and then enter the name that you assigned the sensor in Designer mode. The ports on the Core Device Interface module are number from the bottom up with the bottom one being 0.

          Your team should review the first part of the YouTube video to gain an understanding of how color is handled and think about what makes up the color white.

          ...Bruce
          Thank you so much for the help. We'll try all these out at an upcoming meeting. Thanks again!

          Comment


          • #20
            We made the changes, but the color sensor autonomous program isn't working right. Our other autonomous programs are running correctly, but this color sensor one crashes when we try to press Stop (since the robot doesn't stop at blue).

            I am not sure it makes a difference, but we are using both the Core Legacy Module for our Hitechnic motors, and the Core Device Interface now for the color sensors. The Core Device Interface is new for us, but we are following everything we think we are supposed to.

            This program isn't working, what else could it be? Thanks.

            Comment


            • #21
              Thanks for the great tutorial, Bruce. An interesting thing happened to us. We ran the program and it never left the first loop. After some experimenting, we found that removing the "or" condition made everything ok. We just check motor 1 position in each while loop. Not sure why the "or" messed things up.

              Comment

              Working...
              X