Editing Analyzing torque mode effects

Due to discussion about torque control differences between IONI firmware versions 1.4 and 1.5, we made a special versions of both firmware versions to allow analytical comparison of torque output. If unexpected differences are noticed, please report us at Granite Devices support. 

==How to compare==
[[File:torque_effect_tracking_error.png|thumb|400px|Example of Tracking error on step response test with TBW and notch filter enabled]]
[[File:no_torque_effect_tracking_error.png|thumb|400px|Example of Tracking error on step with TBW set to Unlimited and all other effects disabled]]
Analytical comparison is achieved by the means of ''Tracking error'' capture channel in Granity. This channel displays the difference between the pure unmodified user setpoint and realized actual torque. The difference scale is in millamperes.

Following parameters will modify the setpoint torque and cause the difference between actual and raw setpoint to grow:
*{{param|MPP}}
*{{param|TBW}}
*Torque notch filter 
*Torque mode effects
*Motor torque cogging & ripple compensation

If all effects are disabled and TBW is set Unlimited, then in the ideal case Tracking error would be straight line at zero. However, in practice some error will be there due to current sense noise and physically limited torque control bandwidth.

==Firmware files==
Use the firmware files here to do the comparison with Tracking error feature:
*[[Media:IONIFWpackage1.5.0-RC1.gdf|1.5.0RC1 (1092)]]
*[[Media:IONIFWpackage1.4.1.gdf|1.4.1 (1085)]] - this exactly same as 1.4.0 but with same ''Tracking error'' feature is added to torque control mode.

Older firmware versions don't have Tracking error scope in torque mode (will display only straight line of zero value).