Prototrak Plus Retrofit with Mesa 7i77 & 5i25 cards

Just my experience, and that of course may vary, but FF2 has to be at least 10 to 100 times smaller than FF1, in most cases 0 is perfectly acceptable.
I am adding some more info to servo tuning thread that might help.

tommylight, thank you!

Attached are several screenshots with your suggestions, (I changed the scale on some) this is the best.



the others are described in the file name, somewhat.

many thanks!!

Can you please do a test with the following:
FF1 set at 1
FF2 set at 0

on the hal scope only, "joint.N.motor-pos-cmd" and "joint.N.f-error"

tommylight, thank you!!

I have your suggestion saved as screenshot.



And then just the reversal.



many thanks!!

tommylight wrote:
on the hal scope only, "joint.N.motor-pos-cmd" and "joint.N.f-error"

Can you put only those 2 parameters on the halscope?
I am following this thread from the begining, and i am alsmost certain something is not right in your setup, as has been mentioned by other members several times, becouse some parameters do not have any infuence on the system or the resulting hal scope. P value of over 3000 is something i have never seen, but it is posible. FF1 can be a lot of values, but as far as i remember 1 should be the maximum for a normal servo system. And there is the FF2...........it has to be in very low values or 0. On a tuned system changing FF2 value by a smal, like realy smal amount will mess up the tuning and triger an joint following error.
It is beyond me how can you still move the motors with an FF2 value of 3.7 ???????

thank you tommylight!!!

Attached are some screenshots as you requested. Could not find "joint.N.motor-pos-cmd", found only 2 with pos-cmd (the end), the one used was the only one to trigger using "normal" setting, hope this is ok.





The file names tell the settings, take note P=2450 (all others P=3450) on last pic.

Many thanks!!