Difference between revisions of "Analyzing torque mode effects"
| [checked revision] | [checked revision] |
(Created page with "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 compari...") |
|||
| Line 14: | Line 14: | ||
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. | 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. | ||
| + | |||
| + | ===Guide=== | ||
| + | To run comparison in real application, connect drive with Granity and configure capture with following settings: | ||
| + | ;Capture signals | ||
| + | :Only Tracking error | ||
| + | ;Capture controls | ||
| + | :TSR of 500 to 2500Hz | ||
| + | :Capture instantly | ||
| + | :Continuously repeating catpure | ||
| + | |||
| + | Then click Start capture and run the application which uses drive in torque control mode and simultaneously observe the graph. You can do this test with 1.4 and 1.5 firmware versions to see if there is any unexpected difference. | ||
==Firmware files== | ==Firmware files== | ||
Revision as of 18:33, 23 April 2016
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
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:
- Maximum peak powerMPP
- Torque bandwidth limitTBW
- 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.
Guide
To run comparison in real application, connect drive with Granity and configure capture with following settings:
- Capture signals
- Only Tracking error
- Capture controls
- TSR of 500 to 2500Hz
- Capture instantly
- Continuously repeating catpure
Then click Start capture and run the application which uses drive in torque control mode and simultaneously observe the graph. You can do this test with 1.4 and 1.5 firmware versions to see if there is any unexpected difference.
Firmware files
Use the firmware files here to do the comparison with Tracking error feature:
- 1.5.0RC1 (1092)
- 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).
