SPRUJF4A October   2024  – December 2024

 

  1.   1
  2.   Description
  3.   Features
  4.   Applications
  5.   5
  6. 1Evaluation Module Overview
    1. 1.1 Introduction
    2. 1.2 Kit Contents
    3. 1.3 Specification
    4. 1.4 Device Information
    5.     General Texas Instruments High Voltage Evaluation (TI HV EVM) User Safety Guidelines
  7. 2Hardware
    1. 2.1 Hardware Description
      1. 2.1.1 Auxiliary Power Supply
      2. 2.1.2 DC Link Voltage Sensing
      3. 2.1.3 Motor Phase Voltage Sensing
      4. 2.1.4 Motor Phase Current Sensing
        1. 2.1.4.1 Three-Shunt Current Sensing
        2. 2.1.4.2 Single-Shunt Current Sensing
      5. 2.1.5 External Overcurrent Protection
      6. 2.1.6 Internal Overcurrent Protection for TMS320F2800F137
    2. 2.2 Getting Started Hardware
      1. 2.2.1 Test Conditions and Equipment
      2. 2.2.2 Test Setup
  8. 3Motor Control Software
    1. 3.1 Three-Phase PMSM Drive System Design Theory
      1. 3.1.1 Field-Oriented Control of PMSM
        1. 3.1.1.1 Space Vector Definition and Projection
          1. 3.1.1.1.1 ( a ,   b ) ⇒ ( α , β ) Clarke Transformation
          2. 3.1.1.1.2 ( α , β ) ⇒ ( d ,   q ) Park Transformation
        2. 3.1.1.2 Basic Scheme of FOC for AC Motor
        3. 3.1.1.3 Rotor Flux Position
      2. 3.1.2 Sensorless Control of PM Synchronous Motor
        1. 3.1.2.1 Enhanced Sliding Mode Observer With Phase-Locked Loop
          1. 3.1.2.1.1 Mathematical Model and FOC Structure of an IPMSM
          2. 3.1.2.1.2 Design of ESMO for the IPMS
            1. 3.1.2.1.2.1 Rotor Position and Speed Estimation With PLL
      3. 3.1.3 Field Weakening (FW) and Maximum Torque Per Ampere (MTPA) Control
    2. 3.2 Getting Started Software
      1. 3.2.1 GUI
      2. 3.2.2 Download and Install C2000 Software
      3. 3.2.3 Using the Software
      4. 3.2.4 Project Structure
  9. 4Test Procedure and Results
    1. 4.1 Build Level 1: CPU and Board Setup
    2. 4.2 Build Level 2: Open-Loop Check With ADC Feedback
    3. 4.3 Build Level 3: Closed Current Loop Check
    4. 4.4 Build Level 4: Full Motor Drive Control
    5. 4.5 Test Procedure
      1. 4.5.1 Startup
      2. 4.5.2 Build and Load Project
      3. 4.5.3 Setup Debug Environment Windows
      4. 4.5.4 Run the Code
        1. 4.5.4.1 Build Level 1 Test Procedure
        2. 4.5.4.2 Build Level 2 Test Procedure
        3. 4.5.4.3 Build Level 3 Test Procedure
        4. 4.5.4.4 Build Level 4 Test Procedure
          1. 4.5.4.4.1 Tuning Motor Drive FOC Parameters
          2. 4.5.4.4.2 Tuning Field Weakening and MTPA Control Parameters
          3. 4.5.4.4.3 Tuning Current Sensing Parameters
    6. 4.6 Performance Data and Results
      1. 4.6.1 Load and Thermal Test
      2. 4.6.2 Overcurrent Protection by External Comparator
      3. 4.6.3 Overcurrent Protection by Internal CMPSS
  10. 5Hardware Design Files
    1. 5.1 Schematics
    2. 5.2 PCB Layouts
    3. 5.3 Bill of Materials (BOM)
  11. 6Additional Information
    1. 6.1 Known Hardware or Software Issues
    2. 6.2 Trademarks
    3. 6.3 Terminology
  12. 7References
  13. 8Revision History

Project Structure

Once the project is imported, the project explore appears inside CCS as shown in Figure 3-25.

The folder src_board includes device peripheral configuration. This configuration is done with driverlib from C2000Ware. MCU configuration is generally located in the Hardware Access Layer (HAL) files, hal.c and hal.h. This folder also contains user_mtr1.c, in which various parameters are calculated or assigned. In most use cases, any parameters fully defined or derived in this file will not need to be adjusted by the user.

The folder src_control includes motor drive files that call motor control core algorithm functions within the interrupt service routines and background tasks. This folder also holds various secondary functionalities, such as SFRA, the GUI interface, and so forth.

The folder src_control/common/include holds various header files useful to the system. Of these, the most notable is user_mtr1.h, which contains the motor and system parameter definitions.

The folder src_device holds driverlib, used by the HAL.

The folder src_sta holds self-test application code.

TIEVM-MTR-HVINV TIEVM-MTR-HVINV Project Explorer ViewFigure 3-25 TIEVM-MTR-HVINV Project Explorer View

Figure 3-26 shows the project software flow diagram of ISR for motor control, a main loop for motor control parameters update in background loop.

TIEVM-MTR-HVINV Firmware Project Flow DiagramFigure 3-26 Firmware Project Flow Diagram

The project consists of a motor control interrupt service routine, which are called every PWM cycle. A few background tasks are called in a loop forever in main() and can be used to run slow tasks for which absolute timing accuracy is not required, motor control parameters update, and so on. A CPU timer is used to trigger slow background tasks.

motor1CtrlISR is reserved for calling the motor drive control algorithms to spin the motor 1 that is periodically triggered at the user-defined rate of USER_M1_ISR_FREQ_Hz.

To simplify the system, the design of the software for this EVM is organized into four labs with incremental builds (DMC_BUILDLEVEL), which makes learning and getting familiar with the board and software easier. This approach is also good for debugging and testing boards. Table 3-1 lists the detailed incremental build options. To select a particular build option, select the corresponding BUILDLEVEL option in sys_settings.h. Once the build option is selected, compile the project by selecting the rebuild all compiler option. Section 4.5 provides more details to run each of the build level options.

Table 3-1 Incremental Build Options
OPERATIONBUILD OPTIONDESCRIPTION
MOTOR DRIVEDMC_LEVEL_150% PWM duty, verify ADC offset calibration, PWM output and phase shift
DMC_LEVEL_2Open-loop v/f control to check current and voltage sensing signals for motor
DMC_LEVEL_3Closed current loop to check the hardware settings
DMC_LEVEL_4Motor parameters identify and run with InstaSPIN-FOC or eSMO