Awesome step by step. Had spent hours trying to figure this out and after watching your video I had all the needed code in place in 10 minutes! Bravo sir.
This is probably a stupid question, but how do we initiate the code. We have a controller plugged into the phone and the program initiated, but nothing is happening. I also did the edit in the description.
New coach question -- The telemetry game pad setup needs done on the driver station first, right? Getting my rookies together this weekend for a first shot at programming. Thank you!
Before you start the program you do need to do the start+a on the driver station. I wouldn't recommend starting with programming a mecanum drive, but rather as a tank drive (even if it is a mecanum, tank drive will work and be simpler). Our connections, configurations, and coding video (th-cam.com/video/qKZh8l0ZcR4/w-d-xo.html) is one of our in-person training sessions which we recorded and edited down to be around an hour long, though it usually takes 2-3 hours in person. I would recommend following along with it - it goes over setting up the phones, a bit about the control system, launching the block programming interface, and making a tank-drive teleop.
Nevermind. It works perfectly, but if it were a geared drive the code would need work, thanks for the excellent video, you guys are the GO-TO-TEAM for info!!
Excellent content and presentation! But I have a question. Sum of vertical, horizontal, and turn powers will sometimes be >1. I think setpower will clip the power to be between 1 and -1. How do you deal with that?
You can make a function that scales the powers of the motors based on the highest power if any of them are larger than 1. If any of your motors' theoretical speeds would be larger than 1 then, your whole robot will be slowed down, which occurs mainly during complex motions. It is perfectly driveable without this scaling though, as we've found that if it inputs a value larger than 1 or less than -1 the app treats it as if it is 1 or -1 respectively.
If you're using mecanum wheels, follow the tutorial in the video. If you're just using normal tank drive wheels (omni wheels or that type), you can follow our tank drive tutorial
Hello, on the right side of the block programming environment for new versions of the FTC app is a live Java view. Follow this video and then you can copy the Java using the live Java view.
Hey guys! Can I ask how you got the front_right block? I automatically have every other block (like right drive for example), but this is the only one missing for my team. Thanks in advance!
@@losersclub5648 Hi. Shealin is a member of our team, so I will add that we could use some help still. We are still unable to find the front_right, front_left, back_right, and back_left blocks. Any additional help would be greatly appreciated. Thanks!
@@losersclub5648 Thanks for the nudge in the right direction on configuring the Robot Controller! In the year since the team last worked on a robot (thanks COVID), we had completely forgotten that configuring the robot needed to be done first. We are good to go now!
The robot shown in this video is a holonomic drive, where the omni wheels have to be facing different ways. You can take a look at our goBILDA Strafer Kit build video, which covers building a mecanum drive where all 4 wheels face in the same direction, and the robot can move in every direction still. The coding for both types of drivetrains is the same.
This video is very helpful for the team who is using mecanum wheels for the first time and don't have blocks program to begin with. There is a minor issue with this code. Our team was using Gobilda mecanum wheels and after implementing the program in the video, the wheels are not moving. After consulting some experts, team moved the 'read of joysticks' to inside the loop. With this change, wheels started moving.
After writing this program none of the motors would move. We tried other programs to make sure everything on the robot was set up correctly. It was, we added telemetry for the drive motors and none of the motors moved. Each of the motor powers for the telemetry was 0. We also tried rewriting the program again but nothing changed. Any advice? Anything we might be doing wrong?
@@WizardsexeFTC9794 We are having the same problem, we have added the telemetry and tested everything on other programs, but our drive motors still do not turn on. The phone on the robot register the joysticks movement. Any help would be great!
Awesome step by step. Had spent hours trying to figure this out and after watching your video I had all the needed code in place in 10 minutes! Bravo sir.
You guys rock! I am helping a rookie team and this video was exactly what we needed today. Thank you!
Terrific video, such a great help for young and inexperienced FTC teams. Please keep making Block Programming videos. Many thanks.
Thank you so much for this video! Our programming team was way over thinking this. Keep up the good work!
This is a superb walkthrough, thanks for putting this out there!
Please move the 'read of joysticks' to inside the loop. This helped moving the motors
EXACTLY What my team needed! Any chance you could make a video on identifying the Skystones using a webcam in blocks?
Just posted one on exactly that
I suggest pinning the fix in the description in the comment because it took me awhile to find why the program wasn't working
Great video guys, thank you very much!!!!
No problem!
hello there. if to program the mecanum wheels , is it possible to program it to move autonomously ? please answer . thank you
Why do you use the VuforiaNavigation concept instead if VuMarkIdentification concept for skystone?
This is probably a stupid question, but how do we initiate the code. We have a controller plugged into the phone and the program initiated, but nothing is happening. I also did the edit in the description.
Are you using the expantion hub or the control hub?
New coach question -- The telemetry game pad setup needs done on the driver station first, right? Getting my rookies together this weekend for a first shot at programming. Thank you!
Before you start the program you do need to do the start+a on the driver station. I wouldn't recommend starting with programming a mecanum drive, but rather as a tank drive (even if it is a mecanum, tank drive will work and be simpler). Our connections, configurations, and coding video (th-cam.com/video/qKZh8l0ZcR4/w-d-xo.html) is one of our in-person training sessions which we recorded and edited down to be around an hour long, though it usually takes 2-3 hours in person. I would recommend following along with it - it goes over setting up the phones, a bit about the control system, launching the block programming interface, and making a tank-drive teleop.
What changes need to be done if sprockets and chain are being used, I have tried and have gotten all but the straight fwd and reverse to work
Nevermind. It works perfectly, but if it were a geared drive the code would need work, thanks for the excellent video, you guys are the GO-TO-TEAM for info!!
Excellent content and presentation! But I have a question. Sum of vertical, horizontal, and turn powers will sometimes be >1. I think setpower will clip the power to be between 1 and -1. How do you deal with that?
You can make a function that scales the powers of the motors based on the highest power if any of them are larger than 1. If any of your motors' theoretical speeds would be larger than 1 then, your whole robot will be slowed down, which occurs mainly during complex motions. It is perfectly driveable without this scaling though, as we've found that if it inputs a value larger than 1 or less than -1 the app treats it as if it is 1 or -1 respectively.
@@WizardsexeFTC9794 Thank you! That makes sense.
What changes woulf we make if the wheels were all facing the same way?
If you're using mecanum wheels, follow the tutorial in the video. If you're just using normal tank drive wheels (omni wheels or that type), you can follow our tank drive tutorial
can you please show us what the program looks like in java. Thank you.
Hello, on the right side of the block programming environment for new versions of the FTC app is a live Java view. Follow this video and then you can copy the Java using the live Java view.
Hey guys! Can I ask how you got the front_right block? I automatically have every other block (like right drive for example), but this is the only one missing for my team. Thanks in advance!
Hey there did you get it figured out?
I think you need to
Configure it. Reply if you need help (:
@@losersclub5648 Hi. Shealin is a member of our team, so I will add that we could use some help still. We are still unable to find the front_right, front_left, back_right, and back_left blocks. Any additional help would be greatly appreciated. Thanks!
@@losersclub5648 Thanks for the nudge in the right direction on configuring the Robot Controller! In the year since the team last worked on a robot (thanks COVID), we had completely forgotten that configuring the robot needed to be done first. We are good to go now!
@@michaelbrooke448 awesome! That’s great! Let me know if I can help you at all (:
Does the wheels have to be in that specific orientation into order for the code to work? Or can the wheels all be facing in one direction?
The robot shown in this video is a holonomic drive, where the omni wheels have to be facing different ways. You can take a look at our goBILDA Strafer Kit build video, which covers building a mecanum drive where all 4 wheels face in the same direction, and the robot can move in every direction still. The coding for both types of drivetrains is the same.
Hey i was trying to test this program very helpful but my robot wheels didnt move
This video is very helpful for the team who is using mecanum wheels for the first time and don't have blocks program to begin with. There is a minor issue with this code. Our team was using Gobilda mecanum wheels and after implementing the program in the video, the wheels are not moving. After consulting some experts, team moved the 'read of joysticks' to inside the loop. With this change, wheels started moving.
Sorry about that! It was a problem on our end. Please see the updated video description for a quick fix to the problem.
Wizards.exe FTC #9794 thank you and good luck to you in competition
@@WizardsexeFTC9794 wich one is the updated video?
@@borteaclaudiu2082 The video is the same, but we placed a note in the description of this video to provide a quick fix to the problem.
Is there a way to limit the motor power to like 0.5 while doing this?
Yes! Just multiply all the motor powers by .5. This will make them move at half speed.
@@WizardsexeFTC9794 Thanks!
For some reason this doesn't work for my teams mecanum, none of the wheels move.
Send us an email at Wizards.exe@gmail.com and we can try to debug.
Hey, sorry about the problem! It was a problem on our end. Please see the updated video description for a quick fix to the problem.
@@WizardsexeFTC9794 Thanks!
After writing this program none of the motors would move. We tried other programs to make sure everything on the robot was set up correctly. It was, we added telemetry for the drive motors and none of the motors moved. Each of the motor powers for the telemetry was 0. We also tried rewriting the program again but nothing changed. Any advice? Anything we might be doing wrong?
I would check that your gamepads are working and connected to the phone. Try adding telemetry for the applicable joysticks to test them.
@@WizardsexeFTC9794 We know that they are connected because the other programs are working. We will try adding telemetry to the joysticks though.
@@carterstegg Let us know if that works. Otherwise email wizards.exe@gmail.com and we can help you further
@@WizardsexeFTC9794 Sounds good!
@@WizardsexeFTC9794 We are having the same problem, we have added the telemetry and tested everything on other programs, but our drive motors still do not turn on. The phone on the robot register the joysticks movement. Any help would be great!
will this also work with mecanum wheels
Yes it will!
Wizards.exe FTC #9794 thank you it worked
This is a good video!!!.uitui'
uitui
uitui
That was a spelling mistake lol
hi
?
Please move the 'read of joysticks' to inside the loop. This helped moving the motors