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.

MCT8316Z: Motor Driver stuck until manual movement, unclear mode of operation

Part Number: MCT8316Z

I'm using MCT8316Z, and I have tried to setup different working modes, 

in two modes I see unclear behavior.

All Motor outputs are set to high voltage, ( HS FET is open for All) , the motor is stuck 

To release from a stuck state, I just move the motor a bit to the required direction and then the controller starts working,

I believe most of the time it gets stuck is when the motor can't move to one direction ( mechanical stop), But I DO request it to go to the other direction !!

- in this specific case it gets stuck 100% of the time, but sometimes I see its happening without mechanical limitations on the motor.

At any part of the occasion, we provide high PWM ( up to 90%), and not brake or coast commands !

The modes where it gets stuck - 

Modes of cooperation when Gets stuck -

Control_Registar_2A -  PWM_MODE = 3 (Synchronous with digital hall)

Control_Register_5 - EN_AAR=1, EN_ASR=1 (ASR and AAR enabled)

Yellow - One of the phase current

Blue,red,Green - three-phase output voltage

As can be seen all phases are high voltage , meaning all phases HS FET is open.

OR 

Control_Registar_2A -  PWM_MODE = 1 (Asynchronous with digital hall)

Control_Register_5 - EN_AAR=1, EN_ASR=1 (ASR and AAR enabled)

  • Hi liran,

    I'll get back to you by Wednesday.

    Regards,

    Joshua

  • Hi liran,

    Does this behavior still occur if EN_AAR = 0 and EN_ASR = 0?

    Also could you provide a register dump?

    Regards,

    Joshua

  • This behavior only occurs with ASR and AAR On.

    We have tried four different modes -

    Synchronized PWM + ASR\AAR Off - Did not see stuck issues, But the system is vibrating 

    Asynchronized PWM _ASR\AAR Off -  woking O.K

    Synchronized PWM + ASR\AAR On - system got stuck

    Asynchronized PWM _ASR\AAR On - system got stuck

    Attached bellow is a table of all the registers per mode of operation.

    Also we noticed that is we use high PID values - ones that cause the PWM\DIr to jump without going through stationary mode ( so the PWM may be 10% with one direction ,and within a msec we change it to 10% to the other direction) - Then it tends to get stuck (again - only with ASR\AAR On) - so this might be a good clue.

    #

    PWM mode 

    AAR, ASR

    Reg 

    Scope

    Status

    Notes

    1

    1

    0

    INFO  ~ 7835.937: OK - E_IC_STATUS       0x00: 0x40

     INFO  ~ 7835.951: OK - E_STATUS_REG_1    0x01: 0x00

     INFO  ~ 7835.966: OK - E_STATUS_REG_2    0x02: 0xa0

     INFO  ~ 7835.980: OK - E_CONTROL_REG_1   0x03: 0x03

     INFO  ~ 7835.995: OK - E_CONTROL_REG_2A  0x04: 0x62

     INFO  ~ 7836.010: OK - E_CONTROL_REG_3   0x05: 0x66

     INFO  ~ 7836.024: OK - E_CONTROL_REG_4   0x06: 0x10

     INFO  ~ 7836.038: OK - E_CONTROL_REG_5   0x07: 0x40

     INFO  ~ 7836.053: OK - E_CONTROL_REG_6   0x08: 0x00

     INFO  ~ 7836.067: OK - E_CONTROL_REG_7   0x09: 0x00

     INFO  ~ 7836.081: OK - E_CONTROL_REG_8   0x0a: 0x03

     INFO  ~ 7836.096: OK - E_CONTROL_REG_9   0x0b: 0x00

     INFO  ~ 7836.110: OK - E_CONTROL_REG_10  0x0c: 0x00

    Mode 1

    OK 

    2

    3

    0

    INFO  ~ 7835.931: OK - E_IC_STATUS       0x00: 0x40

     INFO  ~ 7835.946: OK - E_STATUS_REG_1    0x01: 0x00

     INFO  ~ 7835.960: OK - E_STATUS_REG_2    0x02: 0xa0

     INFO  ~ 7835.975: OK - E_CONTROL_REG_1   0x03: 0x03

     INFO  ~ 7835.989: OK - E_CONTROL_REG_2A  0x04: 0x66

     INFO  ~ 7836.004: OK - E_CONTROL_REG_3   0x05: 0x66

     INFO  ~ 7836.018: OK - E_CONTROL_REG_4   0x06: 0x10

     INFO  ~ 7836.032: OK - E_CONTROL_REG_5   0x07: 0x40

     INFO  ~ 7836.046: OK - E_CONTROL_REG_6   0x08: 0x00

     INFO  ~ 7836.061: OK - E_CONTROL_REG_7   0x09: 0x00

     INFO  ~ 7836.075: OK - E_CONTROL_REG_8   0x0a: 0x03

     INFO  ~ 7836.089: OK - E_CONTROL_REG_9   0x0b: 0x00

     INFO  ~ 7836.104: OK - E_CONTROL_REG_10  0x0c: 0x00

    Mode 2

    OK

    Original mode (ILIM RECIR set to COAST for this run)– shaky robot

    3

    1

    1

    INFO  ~ 7835.921: OK - E_IC_STATUS       0x00: 0x40

     INFO  ~ 7835.935: OK - E_STATUS_REG_1    0x01: 0x00

     INFO  ~ 7835.950: OK - E_STATUS_REG_2    0x02: 0xa0

     INFO  ~ 7835.964: OK - E_CONTROL_REG_1   0x03: 0x03

     INFO  ~ 7835.979: OK - E_CONTROL_REG_2A  0x04: 0x62

     INFO  ~ 7835.993: OK - E_CONTROL_REG_3   0x05: 0x66

     INFO  ~ 7836.008: OK - E_CONTROL_REG_4   0x06: 0x10

     INFO  ~ 7836.022: OK - E_CONTROL_REG_5   0x07: 0x4c

     INFO  ~ 7836.036: OK - E_CONTROL_REG_6   0x08: 0x00

     INFO  ~ 7836.050: OK - E_CONTROL_REG_7   0x09: 0x00

     INFO  ~ 7836.065: OK - E_CONTROL_REG_8   0x0a: 0x03

     INFO  ~ 7836.079: OK - E_CONTROL_REG_9   0x0b: 0x00

     INFO  ~ 7836.094: OK - E_CONTROL_REG_10  0x0c: 0x00

    Mode 3

    Stuck

    Updated mode from the last 2 weeks, lesser vibrations (~same as maxon)

    4

    3

    1

    INFO  ~ 7835.917: OK - E_IC_STATUS       0x00: 0x40

     INFO  ~ 7835.935: OK - E_STATUS_REG_1    0x01: 0x00

     INFO  ~ 7835.951: OK - E_STATUS_REG_2    0x02: 0xa0

     INFO  ~ 7835.967: OK - E_CONTROL_REG_1   0x03: 0x03

     INFO  ~ 7835.983: OK - E_CONTROL_REG_2A  0x04: 0x66

     INFO  ~ 7836.000: OK - E_CONTROL_REG_3   0x05: 0x66

     INFO  ~ 7836.016: OK - E_CONTROL_REG_4   0x06: 0x10

     INFO  ~ 7836.032: OK - E_CONTROL_REG_5   0x07: 0x4c

     INFO  ~ 7836.048: OK - E_CONTROL_REG_6   0x08: 0x00

     INFO  ~ 7836.064: OK - E_CONTROL_REG_7   0x09: 0x00

     INFO  ~ 7836.080: OK - E_CONTROL_REG_8   0x0a: 0x03

     INFO  ~ 7836.095: OK - E_CONTROL_REG_9   0x0b: 0x00

     INFO  ~ 7836.110: OK - E_CONTROL_REG_10  0x0c: 0x00

    Mode 4

    Stuck

    8316_config.docx

  • Hi liran,

    I will need sometime to look into this, I will aim to get back to you by next Wednesday.

    Regards,

    Joshua

  • Hi liran,

    I am noticed that the reg dumps that you provided show that the device is experiencing a BUCK_OCP and OCP fault. These faults could be what is causing the device to get stuck.

    Regards,

    Joshua