Quote:
Originally posted by EbonySeraphim
About your code for the next quote - I have no clue what that does. You'd need to tell me what all of those variables mean/are set to in this or that case. Looking at the names of certain variables, it seems that code limits how much change in the x or y axis of the joystick can occur per iteration. The intial post was asking for a slowdown to stop - not a limiter. Though a limiter would get rid of code for gradually slowing down the robot.
|
The code I posted will make it so the robot gradually changes speed, as set by softChangeCoeff. Each loop it will calculate the difference between where p1_y is and where it was last loop (p1_y_filt) and decrease that interval by some percentage of it. At the end of each loop, there is a p1_y_filt=p1_y to accomplish this. If you want more detail, check out InnovationFirst's whitepapers as it is taken almost directly from there.
Quote:
|
I understand that axiom...but in this case. I would trust the user not to screw up the robot, and also, I know our robot can handle that kind of controlling. We have ran ours in full foward to reverse, and it works fine. I'm sure its a big strain, but it can take it a few times.
|
That's what we though two years ago. We then proceeded to destroy three gearboxes at a single regional. After adding the above two lines of code, we had no problems whatsoever.
Remember, this thread is not about your robot or mine. EvilDeathCrab asked for help implementing this feature not whether or not it was necessary. If you want to continue this discussion, please PM or email me.