Prototrak Plus Retrofit with Mesa 7i77 & 5i25 cards

Also your FF2 is way to high, set it at 0 and only after you get to move the motors at your desired speed proceed to adding FF2 only and only if you end up getting to much overshoot at the begining and end of a move. Most probably the spikes you are getting are from that.

Many thanks for all the help!!

The screen shots have description in the file name. I believe this is the best, (I will need to look at these side by side myself) compared to others. The pid.n.error gets lower as the pics are arranged in order.




Many, many thanks!

Edit: The scale for pid.n.error was change between the pic, form 1m/div to 2m/div. The best screenshot I think is Sshotyf1.01f23.8Db.00003.png just did not edit well.

Just for shits and giggles try FF1=-0.2

Todd thank you!


this is FF1= .2 and other is .0009



the last 3 look the same to me, when I look at these traces, I am trying to keep pid.n.error low, and trying to keep the light blue (teal) trace (.encoder) from over shooting the dark blue. I can revisit the .ini file, I don't have notes in front of me to include that data now.

many thanks!

Now try a negative ,2 in FF1 (the font used by the forum made the "-" sign in my last post very small so maybe you didn't see it.

Hold on, Also try much larger FF1 valuses, like 1, 2 ...
To see the trend here. Don't change any onther things. Only make one change at a time to get a feel for what is actually doing what.