This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HVKit tuned

Hi to All,

we are using the ti HV-Kit. For some Tests we would like to have 20% more current - since the IGBT-Module can go up to 40A we decided to "tune" the Kit a little bit.
To enlarge it's current capability we changed the resistor dividers between the op-amps and the ad-inputs of the CPU.
R47, 48, 49, 50 = 1K, R25,26,27,28 = 4K7    => this results in a divider of 0.825
As result we extend the measurement range of the current values.
In fact they are 121% comparred to the original placement (R47..50 = 0R, R25..28 = not populated).
To ensure that the Algorithm is calculating with the correct current values we also changed:

Original Values:
#define USER_IQ_FULL_SCALE_CURRENT_A  (10.0)
#define USER_ADC_FULL_SCALE_CURRENT_A  (19.89)

To our new Values:
#define USER_IQ_FULL_SCALE_CURRENT_A  (12.0)
#define USER_ADC_FULL_SCALE_CURRENT_A  (24.27)

We assumed to get the same Motor ID, but the Motor IDs are different.
The Rs is about 1 Ohm greater on the HVKit tuned.
Is there another scale factor that i must correct it?
To get the Parameter i have done the Labs
Lab2a -> Motor ID
Lab3a -> ADC Offsets
Lab5c -> Inertia, Friction
Lab5e -> Bandwidth


HVKit R1.1 original

#define USER_IQ_FULL_SCALE_CURRENT_A (10.0)

#define USER_ADC_FULL_SCALE_CURRENT_A (19.89)

#define USER_SYSTEM_BANDWIDTH_SCALE (2.5)

#define I_A_offset (0.9889517426)

#define I_B_offset (0.9821072817)

#define I_C_offset (0.9883185625)

#define V_A_offset (0.3615697026)

#define V_B_offset (0.360293448)

#define V_C_offset (0.3602167964)

#define USER_MOTOR_TYPE MOTOR_Type_Pm

#define USER_MOTOR_NUM_POLE_PAIRS (4)

#define USER_MOTOR_Rr (NULL)

#define USER_MOTOR_Rs (2.937094)

#define USER_MOTOR_Ls_d (0.003506451)

#define USER_MOTOR_Ls_q (0.003506451)

#define USER_MOTOR_RATED_FLUX (0.6112353)

#define USER_MOTOR_MAGNETIZING_CURRENT (NULL)

#define USER_MOTOR_RES_EST_CURRENT (5.0)

#define USER_MOTOR_IND_EST_CURRENT (-0.5)

#define USER_MOTOR_MAX_CURRENT (10.0)

#define USER_MOTOR_FLUX_EST_FREQ_Hz (20.0)

#define USER_SYSTEM_INERTIA (0.02935403585)

#define USER_SYSTEM_FRICTION (0.08022159338)

 

HVKit R1.1 tuned

#define USER_IQ_FULL_SCALE_CURRENT_A (12.0)

#define USER_ADC_FULL_SCALE_CURRENT_A (24.27)

#define USER_SYSTEM_BANDWIDTH_SCALE (3.0)

#define I_A_offset (0.9546062946)

#define I_B_offset (0.9486871958)

#define I_C_offset (0.95380193)

#define V_A_offset (0.3577740192)

#define V_B_offset (0.3565648198)

#define V_C_offset (0.3565022349)

#define USER_MOTOR_TYPE MOTOR_Type_Pm

#define USER_MOTOR_NUM_POLE_PAIRS (4)

#define USER_MOTOR_Rr (NULL)

#define USER_MOTOR_Rs (4.070159)

#define USER_MOTOR_Ls_d (0.002782427)

#define USER_MOTOR_Ls_q (0.002782427)

#define USER_MOTOR_RATED_FLUX (0.5964383)

#define USER_MOTOR_MAGNETIZING_CURRENT (NULL)

#define USER_MOTOR_RES_EST_CURRENT (3.0)

#define USER_MOTOR_IND_EST_CURRENT (-1.0)

#define USER_MOTOR_MAX_CURRENT (12.0)

#define USER_MOTOR_FLUX_EST_FREQ_Hz (20.0)

#define USER_SYSTEM_INERTIA (0.02122914791)

#define USER_SYSTEM_FRICTION (0.0814639926)


SOFTWARE TOOLS:

CCS :5.5.0.0.0077
COMPILER : 06.02.04
MOTORWARE : 1_01_00_11


  • 1. The IPM is capable of 40A maybe, but not with the PCB and cooling we use. There is also a 10A fuse. 

    2. I'm on mobile so can't check the math, but I think it's wrong. Please check the UG section on the scaling. 

    3. The Ls and flux are also not close, another hint something is wrong. 

    4. Your Rs is too high. 10% of rated is a good target. Use the smallest required to insure the motor can start spinning during RampUp. 5A may be overheating.

  • hi chris, 

    1. we know it. we cooling the board with an extern fan :-). 

    2. What is UG section?

    3. Our Motor was by TI. They made a test- report for us.

        Ls and flux values are the same values what i measured.

        Why do you mean that these value are not correct?

    4. Rs is too high?. TI identified the same value.

        What do you mean "10% of rated is a good target". ?

       

        Alex

       

     

    Mibtec_v0_0_0.pdf
  • 2. Spruhj1. I'm on mobile, but I think it's ch 5

    3. The parameters in your "new" user.h are not the same as the test report. The Rs and Ls are wrong because your current scaling is incorrect. 

    4. Your RES_CURRENT is set too high in the user.h, look at the value used in the test report vs the 4A in user.h. That is just one issue.