SPRUHW1A June   2014  – October 2021 TMS320F28052-Q1 , TMS320F28052M , TMS320F28052M-Q1 , TMS320F28054-Q1 , TMS320F28054M , TMS320F28054M-Q1

 

  1. 1Read This First
    1. 1.1 About This Manual
    2. 1.1 Glossary
    3. 1.1 Support Resources
    4.     Trademarks
  2. 1 F2805xM InstaSPIN-MOTION Enabled MCUs
  3. 2InstaSPIN-MOTION Key Capabilities and Benefits
    1. 2.1 Overview
    2. 2.2 FAST Unified Observer
    3. 2.3 SpinTAC Motion Control Suite
      1.      IDENTIFY
      2.      CONTROL
      3.      MOVE
      4.      PLAN
    4. 2.4 Additional InstaSPIN-MOTION Features
  4. 3InstaSPIN-MOTION Block Diagrams
    1.     Scenario 1: InstaSPIN-MOTION Speed Control with FAST Software Encoder
    2.     Scenario 2: InstaSPIN-MOTION Speed Control with a Mechanical Sensor
    3.     Scenario 3: InstaSPIN-MOTION Position Control with Mechanical Sensor and Redundant FAST Software Sensor
  5. 4Application Examples
    1. 4.1 Treadmill Conveyor: Smooth Motion Across Varying Speeds and Loads
    2. 4.2 Video Camera: Smooth Motion and Position Accuracy at Low Speeds
    3. 4.3 Washing Machine: Smooth Motion and Position Accuracy at Low Speeds
      1.      Agitation Cycle
      2.      Spin Cycles
    4. 4.4 InstaSPIN-MOTION Works Over the Entire Operating Range
  6. 5Evaluating InstaSPIN-MOTION Performance
    1. 5.1 Overview
    2. 5.2 Velocity Control Performance: SpinTAC vs PI
      1. 5.2.1 Disturbance Rejection
      2. 5.2.2 Reference Tracking
      3. 5.2.3 Step Response
    3. 5.3 Position Control Performance: SpinTAC vs PI
      1. 5.3.1 Disturbance Rejection
      2. 5.3.2 Reference Tracking
      3. 5.3.3 Step Response
      4. 5.3.4 Inertia Estimation Repeatability
  7. 6Microcontroller Resources
    1. 6.1 CPU Utilization
    2. 6.2 Memory Utilization
    3. 6.3 Security Zones
    4. 6.4 Linker Command File Settings
    5. 6.5 Interfacing FAST ROM Libraries
    6. 6.6 Pin Utilization
    7. 6.7 Consideration of Analog Front-End (AFE) Module
      1. 6.7.1 Routing Current Signals
      2. 6.7.2 Voltage Reference Connection
      3. 6.7.3 Routing Voltage Signals
        1.       A Resources
          1.        B Definition of Terms and Acronyms
            1.         C Revision History

Reference Tracking

Reference tracking tests how well the controller follows a changing target speed. The two metrics to evaluate in this testing are the maximum error and the absolute average error. The maximum speed error shows how much the controller overshoots while changing speeds. This is an indication of how aggressively your controller is tuned. If your controller is not tuned aggressively enough, the speed will overshoot the target, and take a long time to recover. If the controller is tuned too aggressively it will overshoot, and then oscillate as it settles on the goal speed. If the controller is correctly tuned, it will minimally overshoot and then smoothly return to the goal speed.

Absolute average error is an average of the absolute value of the instantaneous speed error over the entire profile. This measure shows the amount of deviation throughout the entire profile. It takes into account all of the little errors as the motor is running. If the controller is tuned too aggressively it will result in larger absolute average error because the controller will be oscillating throughout the profile. If the controller is not tuned aggressively enough, it will result in a larger absolute average error because the motor is continuously lagging the profile.

A tracking profile was created to exercise the motor in a repeatable a pattern. The profile was used to compare the performance of SpinTAC and PI controllers. The profile included quick transitions as well as gentle sweeping transitions. Figure 6-5 is a plot of the speed profile used during the reference tracking tests. The blocked off areas are areas where additional plots will be shown detailing the differences between the SpinTAC and PI controllers.

GUID-C03B3C17-C2E9-466C-83E8-12C1180A0ED4-low.pngFigure 5-5 Speed Profile Used During Reference Tracking Test

 

There are some differences between the SpinTAC and PI controller that should be called out and evaluated in addition to the absolute average error and maximum error of the profile tracking. Figure 6-6 shows how the PI controller greatly overshoots the speed reference when it makes a very drastic change. It then takes quite a bit of time to recover from that initial error, while the SpinTAC controller has no problems with the drastic reference change.

GUID-C37805A4-C2B3-4D02-B850-7080922E379F-low.pngFigure 5-6 Large Overshoot for PI Controller During Reference Tracking

 

Figure 6-7 shows how the PI controller falls behind the reference as the drastic changes in the reference continue. The PI controller cannot keep up, while the SpinTAC controller has no difficultly in accurately tracking the speed reference.

GUID-F10F54B5-CFD4-412A-AA0D-FC612A9AB2AC-low.pngFigure 5-7 Speed Tracking Error for PI Controller During Reference Tracking

 

When starting from zero speed with a slow trajectory change, the PI controller has more difficulty than the SpinTAC controller. This is due to the SpinTAC controller's superior ability to track a changing reference signal. Figure 6-8 shows an example of this from the reference tracking test.

It is important to test multiple speeds and accelerations in your profile as well as multiple different loads. Speed controllers have different performance characteristics when placed into different situations. In order to properly evaluate the effectiveness of your speed controller, tests should be conducted across the entire application range. This includes when you design the profile for testing. Care needs to be taken to ensure that the application speeds and accelerations are built into the profile. The results of these tests will inform you if your controller will meet the application specifications or if your controller needs to be tuned multiple times for different operating points. Notice wide range of speeds and accelerations that are tested in Figure 6-5.

It is also important to be able to create repeatable profiles. Creating a repeatable profile can be done using SpinTAC Move and SpinTAC Plan (the InstaSPIN-FOC and InstaSPIN-MOTION User's Guide provides detailed information on SpinTAC Move and SpinTAC Plan and lab projects are available in the MotorWare repository). Repeatable profiles are required so that all controllers are tested using the same reference in the same order and for the same length of time. This ensures that test conditions are as identical as possible. The profile for this test was made using SpinTAC Move and SpinTAC Plan to ensure that an identical profile was presented to both the SpinTAC and PI controllers.

GUID-66754BA0-6F75-4479-8448-714D173022A0-low.pngFigure 5-8 Startup Error From Zero Start for PI Controller

 

The following parameters were measured:

  • Absolute Average Speed Error: The positive or negative deviation from the goal speed over the entire speed profile.
  • Maximum Speed Error: The maximum deviation from the goal speed during the speed profile.

Table 5-4 SpinTAC vs PI Profile Tracking Test Results
Trapezoidal Curve st-Curve
SpinTAC PI SpinTAC Advantage (percentage improvement over PI) SpinTAC PI SpinTAC Advantage (percentage improvement over PI)
Teknic Motor
Abs Avg Error (rpm) 6.01 19.94 69.86 5.98 19.51 69.35
Max Error (rpm) 266.06 430.00 38.13 263.00 334.71 21.42
Estun Motor
Abs Avg Error (rpm) 5.39 16.11 66.54 5.73 16.124 64.46
Max Error (rpm) 248.29 312.74 20.61 181.64 307.61 40.95