CCS/DRV8323: update from DRV8305 to DRV8323

I use CSD88599Q5DC. I use DRV8323RH. I tried IDRIVE = Hi-Z 240
IDRIVE = 75 kΩ to DVDD 520, IDRIVE = 18 kΩ to DVDD 1140, IDRIVE = to DVDD 2000.

U7 DNP

R15,R16 = 0R.

The second transistor is not installed.

Switching in one channel is induced on the gate in another channel?
Does Switching open a high transistor in another channel and then the driver closes it?

I looked three channels in the gates. In one of the channels visible fluctuations. 0-RPM. IDRIVE - 2A.

We have a standard scheme.  :)EVO BLDC 6050C.PDF

Thanks for the advice,

I watched. nFAULT - everything is clean. We want current up to 70A.
I set GAIN to 40V/V and #define USER_ADC_FULL_SCALE_CURRENT_A (82.5)
I set PWM frequency to 60-80KHz. fluctuations gone. :)

How set the dead time between phases in MotorWare?
Is now the dead time depends on the frequency of the PWM?

Where can I find recommendations (formulas) on the PWM frequency for motors with a small inductance.

thank
Andrew.

PS:

I returned to PWM to 15 KHz, reduced two define to 0.5.

The signals have become readable and beautiful.  :)


// # define HAL_PWM_DBFED_CNT 1
#define HAL_PWM_DBFED_CNT (uint16_t) (0.5 * (float_t) USER_SYSTEM_FREQ_MHz) // 2 usec


//! \ brief Defines the PWM deadband rising edge count (system clocks)
//!
// # define HAL_PWM_DBRED_CNT 1
#define HAL_PWM_DBRED_CNT (uint16_t) (0.5 * (float_t) USER_SYSTEM_FREQ_MHz) // 2 usec


Now I repeat all the tests.
Maybe something else forgot and missed.

:)

I did the first tests. A beautiful signal in the GATE and phase does not mean that the motor is working well. :(

I made a speed comparison regarding the delay. And back to delay 2us or 3us.

I did not expect that with "field weakening" a big difference in speed. To change the direction of rotation with the "field weakening" with great acceleration is generally impossible.

Hello Adam,

dead zone - figured out.
For CSD88599Q5DCT I reduced to 0.2uS. The difference between the normal mode and the "field weakening" has become much smaller.
I have a question. According to the parameters of MotorWare.
1. I returned to GAIN 20V /V and set
#define USER_ADC_FULL_SCALE_CURRENT_A (165) // Rsh 1mR

I have a Rsh 1mR, 5W that will allow the controller to load up to 70A RMS. For sine, the peak current will be 100A. The current through the motor phase is not the RMS current. :) Resistances allow 5x overload and I have good cooling. (water)

I have a 50A, 600W motor. Alas, I do not know what the current RMS or peak, and I do not know the maximum through.

I set
#define USER_IQ_FULL_SCALE_CURRENT_A (100.0) // peak Rsh
and limited
#define USER_MOTOR_MAX_CURRENT (70.0) //peak motor

I managed to load the motor up to 600W - 1000W.

In many TI examples, "#define USER_IQ_FULL_SCALE_CURRENT_A" is set to half of #define USER_ADC_FULL_SCALE_CURRENT_A
In my case, this would be dvr8323 - 140A / 2 = 70A.

Can someone from the TI make comments of their choice.
#define USER_IQ_FULL_SCALE_CURRENT_A - RMS <> peak ????
#define USER_MOTOR_MAX_CURRENT RMS <> Peak ???

Thank.
Andrew.

#define USER_ADC_FULL_SCALE_CURRENT_A (165) // Rsh 1mR

suggests your hardware is measuring -82.5A (0V at ADC) to 82.5A (3.0V at ADC)

Is this correct?

If so, you should set

#define USER_IQ_FULL_SCALE_CURRENT_A (82.5)

#define USER_MOTOR_MAX_CURRENT

should be set to the peak IqRef_A  command that you want the speed controller to saturate too. This is not a hardware limit, but a limit on the input to the torque controller (when you are using the PI speed controller).