It looks quite good when the robot has the same moment of inertia and speed, but when batteries get lower and you change attachments these two change and you constantly have to adjust those 80 degrees.
I‘d recommend to use a motor speed proportional to the angle. So robot starts to turn quickly and slows down at the end... this way the oversteering should be less while the speed of your turns improves significantly.
One more thing.... if you turn by absolute values (meaning "turn until total gyro value reaches 'current_value + turn') instead of relative values (meaning "turn until gyro differs from 'current_value" by "turn") you won't have any accumulated errors, because any oversteering is automatically corrected at the next turn. So you turn to 90° on turn one, to 180° on turn 2, and so forth). This way your robot can follow the square precisely until the battery runs out :-)
The speed proportional to angle idea is great, I may try that for myself soon! The downside of programming the target individually each time (90, 180, 270, etc) instead of adding 90 for the next angle is that I would need to individually program each target, which would take forever.. By adding 90 degrees, I can have it go on indefinitely. Thanks for sharing these ideas!
I guess for this use case ( following a square infinitely) just adding 90 degrees every turn is as simple as turning 90 degrees relatively. For more complicated routes it’s indeed a bit cumbersome to keep track of the total gyro values all the time... but as I said... your robot will always turn like you want, hence I believe it’s worth the effort... at least in robot competitions. Feel free to check our UA-cam channel... we posted a video for our WRO 2018 Junior robot. The video shows still the non proportional turns... meanwhile we switched to proportional turns using absolute instead of relative gyro values and our robot is now 20% faster while having become much more stable at the same time.
It indeed is pretty cool and worked quite well for me, however it seemed like the gyro was having drift issues much more often than before using that method. So I stopped using it and the drift almost completly disappeared. I suspect it is because it requires the gyro too much in a short amount of time or something...
Hi, we are a team in Belgium and we want to program the robot to ride 1 rotation forward, then he turns to the left, he ride again 1 rotation forward. Then we want to let the robot turn to his startposition. So for example, when he starts, it's 0 degrees on the gyro. How can we take that variable, put into his memory and then, let motor B of C rotate till he reached again his 0 degrees? Thx for answers!
I m facing the problem that my gyro sensor doesn't take same degree turn every turn. I use calibration before each turn but 3 to 5 degree it turns more or less
When my team tries this approach along it works, but when it’s added within a program it just keeps spinning never stopping the turn. It almost seems like it never reads the gyro to exit. The gyro works fine on a straight line loop just not this one. Any ideas??
We are struggling to find the Gyro button on the EVS Home Edition like you have here. Is there something we can do? I've checked all the updates and we seem to be okay.
The Gyro block needs to be downloaded from lego.com/mindstorms then imported into your EV3 software. I have a tutorial that teaches you how to do this: ua-cam.com/video/Jcb6r4KbHo8/v-deo.html
That has to do with the way the motors on Sirius are positioned; since they have an upside-down orientation, negative power is necessary to make my robot drive forward.
Hi, its me again :D. So, it seems like my lego pieces is getting more and more fragile. My broken TECHNIC® pieces keep increase in number (even my RJ12 cables have it's holder thingy broken, so it couldn't connect securely in the port). Does this ever happen to you? What trick did you use to treat those TECHNIC® pieces carefully?? By the way, thanks for your attention and patience for replying my questions 😁, keep up the good work!
That is strange, I have found LEGO pieces to be quite durable and I don't think I've ever broken a LEGO piece. The only thing I can recommend is that you be careful when building to consider the stress that your design may put on individual pieces. Always design and reinforce the design to minimize the stress in your parts.
Wow, maybe I'm too rude with my Lego Mindstorms connectors (are connectors actually durable? I broke a lot of them, especially the longer blue one.) I'll try to be careful with my TECHNIC pieces. Thanks for replying!
It looks quite good when the robot has the same moment of inertia and speed, but when batteries get lower and you change attachments these two change and you constantly have to adjust those 80 degrees.
That is very true, and a major downside of using the gyro.
@@Builderdude35 do u know y my chromebook does not have all thee tabs on the bottom of our programmer
thanks for this. we have robotix class and we need this for into orbit 2018 whatver thank you for the brains
Thanks so much can't wait until next week!
Thank you! I think you will love next week's video!
I‘d recommend to use a motor speed proportional to the angle. So robot starts to turn quickly and slows down at the end... this way the oversteering should be less while the speed of your turns improves significantly.
Yes. Also start and end of fast rotating - stress for Gyro, this is the reason for accumulating error.
One more thing.... if you turn by absolute values (meaning "turn until total gyro value reaches 'current_value + turn') instead of relative values (meaning "turn until gyro differs from 'current_value" by "turn") you won't have any accumulated errors, because any oversteering is automatically corrected at the next turn. So you turn to 90° on turn one, to 180° on turn 2, and so forth). This way your robot can follow the square precisely until the battery runs out :-)
The speed proportional to angle idea is great, I may try that for myself soon!
The downside of programming the target individually each time (90, 180, 270, etc) instead of adding 90 for the next angle is that I would need to individually program each target, which would take forever.. By adding 90 degrees, I can have it go on indefinitely.
Thanks for sharing these ideas!
I guess for this use case ( following a square infinitely) just adding 90 degrees every turn is as simple as turning 90 degrees relatively. For more complicated routes it’s indeed a bit cumbersome to keep track of the total gyro values all the time... but as I said... your robot will always turn like you want, hence I believe it’s worth the effort... at least in robot competitions. Feel free to check our UA-cam channel... we posted a video for our WRO 2018 Junior robot. The video shows still the non proportional turns... meanwhile we switched to proportional turns using absolute instead of relative gyro values and our robot is now 20% faster while having become much more stable at the same time.
It indeed is pretty cool and worked quite well for me, however it seemed like the gyro was having drift issues much more often than before using that method. So I stopped using it and the drift almost completly disappeared. I suspect it is because it requires the gyro too much in a short amount of time or something...
how do i create a myblock in which i tell how many geus it should turn? because in this programming he keeps walking infinitely
Hi, we are a team in Belgium and we want to program the robot to ride 1 rotation forward, then he turns to the left, he ride again 1 rotation forward. Then we want to let the robot turn to his startposition. So for example, when he starts, it's 0 degrees on the gyro. How can we take that variable, put into his memory and then, let motor B of C rotate till he reached again his 0 degrees? Thx for answers!
thank you so much!
You're welcome!
I m facing the problem that my gyro sensor doesn't take same degree turn every turn. I use calibration before each turn but 3 to 5 degree it turns more or less
When my team tries this approach along it works, but when it’s added within a program it just keeps spinning never stopping the turn. It almost seems like it never reads the gyro to exit.
The gyro works fine on a straight line loop just not this one. Any ideas??
i am literally having the same problem but with mine it doesn't work with stabilizing
Dude you are a Lego Legend!
Thanks, I try :)
We are struggling to find the Gyro button on the EVS Home Edition like you have here. Is there something we can do? I've checked all the updates and we seem to be okay.
The Gyro block needs to be downloaded from lego.com/mindstorms then imported into your EV3 software. I have a tutorial that teaches you how to do this: ua-cam.com/video/Jcb6r4KbHo8/v-deo.html
Which software you use for programming
Sayma Bano he’s using the default ev3 language
I want to ask, "how we gonna exit the loop of this program"?
You can simply put it on a 'loop' instead of 'forever'
Why do you always use negative powers? Thanks
That has to do with the way the motors on Sirius are positioned; since they have an upside-down orientation, negative power is necessary to make my robot drive forward.
thanks!!!
What robot do you use?
Joshua Liu ev3
Please rep ASAP🥺
wow these guys too big brain to me LOL
Hi, its me again :D.
So, it seems like my lego pieces is getting more and more fragile. My broken TECHNIC® pieces keep increase in number (even my RJ12 cables have it's holder thingy broken, so it couldn't connect securely in the port).
Does this ever happen to you? What trick did you use to treat those TECHNIC® pieces carefully??
By the way, thanks for your attention and patience for replying my questions 😁, keep up the good work!
That is strange, I have found LEGO pieces to be quite durable and I don't think I've ever broken a LEGO piece. The only thing I can recommend is that you be careful when building to consider the stress that your design may put on individual pieces. Always design and reinforce the design to minimize the stress in your parts.
Wow, maybe I'm too rude with my Lego Mindstorms connectors (are connectors actually durable? I broke a lot of them, especially the longer blue one.) I'll try to be careful with my TECHNIC pieces. Thanks for replying!
watan hyiny
You just keep getting older. Why?
Doe Python man amateur