Other Parts Discussed in Thread: MCT8329A
Tool/software:
Hello,
I am currently working with the MCF8329A gate driver. A few days ago, the system was running in closed loop—although not optimally—mainly because I do not yet have the precise BEMF constant. While MPET does determine a BEMF constant, it is not accurate enough for stable closed-loop operation when running on PWM.
However, for the past two days I have encountered a persistent issue: whenever I connect my hardware (not the EVM) to the PC, the OCP_SNS_Fault occurs immediately—even before running MPET or applying PWM. This happens regardless of which register file I load. For example, even with the default MCF8329A register set, running MPET directly triggers the OCP_SNS_Fault. Writing the default registers to EEPROM does not resolve the problem.
I find this unusual, because the same parameter sets that worked on PWM just two days ago now consistently trigger the fault. I have carefully checked my hardware and found no apparent issues. This raises the question: if the hardware and parameter set were working before, why does the same configuration now fail?
For reference, the two register files I have used are:
-
BLDC_fan_40A_1p8KHz_MCF8329A
-
Default Registers MCF8329A
Motor specifications:
-
Resistance: 0.232 Ω
-
Inductance: 0.19 mH
-
BEMF constant: unknown
-
Peak current: unknown
Additionally, even when using the default registers, I always modify the base current to 0x2731
(100 A).
Could you please help me identify the cause of this persistent OCP_SNS_Fault and suggest a resolution?