Don't know if you mention this. But for anything more complicated than this, you should declare any motors, servos, sensors, etc... in a hardware class. This means that whenever i want to use a motor, servo or sensor in any of my code i don't need to enter all of this information each time. This comes in handy when you start writing your own classes.
How would you do an ease in ease out movement for your robot so that it doesn't start at full power, but goes from 10 to 20 to 30 to 40, etc.? Your videos are super helpful, thanks!
Good question. I'll have to ask our programmer about that one. I know he made it so the robot drives at 70 percent normally, and if the left trigger is pushed it's like 50 percent, and if the right trigger is pushed it's 100 percent. There are some teams that do some math to the joystick power to make the bottom part of the joystick more "useful". I think it's like cubing the value or cube root or something. There's a lot of info out that process if you google search for it.
Hey PC Man. We're glad you are finding the videos useful. We are working on a video on Java syntax right now. It should be out soon. After that, we want to dive a bit into getting control over servos and then maybe some autonomous programming. Make sure to subscribe so you can get any updates as they come out. Thank you for the encouragement.
Hi Cory. I would appreciate it if you could respond as quickly as possible. Basically, I am assuming we don't need @TeleOp before the gamepad for this class. And you didn't state the value for the double data type (decimal) instead you just left it as leftWheelPower is it because it will automatically assume that both speeds are the same for the left and right wheel?
Sorry for the delay. While using Android Studio, if you type gamepad1. it should give you a list of the different button names. The ones I can remember right now are leftstick, rightstick, dpad up down, left bumper, right bumper, left trigger, right trigger, and the ones that are labeled x, y, etc. I hope this helps.
hi! in the variables why did you decide to add a double, isn't double for decimal powers? In the end you're only left with a -1 and 1 as powers. Would you mind explaining that to me?
Hey Michelle. You are correct. double is for decimals. I guess we forgot to mention that the joysticks on the gamepad return decimal values BETWEEN -1 and 1. This gives you variable speed. For instance, if the joystick is pushed halfway, you get (-.5) or (.5) depending on direction. Then we apply that value to the motors and get variable speed control. That's why we use double instead of int. Does that answer it?
Don't know if you mention this. But for anything more complicated than this, you should declare any motors, servos, sensors, etc... in a hardware class. This means that whenever i want to use a motor, servo or sensor in any of my code i don't need to enter all of this information each time. This comes in handy when you start writing your own classes.
How does the range.clip() function work? I wanted to know that. Would appreciate it if you can reply ASAP. thanks.
How would you do an ease in ease out movement for your robot so that it doesn't start at full power, but goes from 10 to 20 to 30 to 40, etc.?
Your videos are super helpful, thanks!
Good question. I'll have to ask our programmer about that one. I know he made it so the robot drives at 70 percent normally, and if the left trigger is pushed it's like 50 percent, and if the right trigger is pushed it's 100 percent. There are some teams that do some math to the joystick power to make the bottom part of the joystick more "useful". I think it's like cubing the value or cube root or something. There's a lot of info out that process if you google search for it.
FTC Team 9779 PIEaters thank you so much!
Has the next video been released as of 7-9-17?
This information has helped me a lot and has introduced me to the ftc java programming.
Hey PC Man. We're glad you are finding the videos useful. We are working on a video on Java syntax right now. It should be out soon. After that, we want to dive a bit into getting control over servos and then maybe some autonomous programming. Make sure to subscribe so you can get any updates as they come out. Thank you for the encouragement.
Hi Cory. I would appreciate it if you could respond as quickly as possible. Basically, I am assuming we don't need @TeleOp before the gamepad for this class. And you didn't state the value for the double data type (decimal) instead you just left it as leftWheelPower is it because it will automatically assume that both speeds are the same for the left and right wheel?
does anyone know where i could find a complete button mapping of the gamepad so i can use it for programming it in java?
Sorry for the delay. While using Android Studio, if you type gamepad1. it should give you a list of the different button names. The ones I can remember right now are leftstick, rightstick, dpad up down, left bumper, right bumper, left trigger, right trigger, and the ones that are labeled x, y, etc. I hope this helps.
its so helpful
hi! in the variables why did you decide to add a double, isn't double for decimal powers? In the end you're only left with a -1 and 1 as powers. Would you mind explaining that to me?
Hey Michelle. You are correct. double is for decimals. I guess we forgot to mention that the joysticks on the gamepad return decimal values BETWEEN -1 and 1. This gives you variable speed. For instance, if the joystick is pushed halfway, you get (-.5) or (.5) depending on direction. Then we apply that value to the motors and get variable speed control. That's why we use double instead of int. Does that answer it?
Epic
noice
i am team 14941, this is outdated