• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 347 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F2800157: Position control of the 48V ABZ+PWM motor using F2800157 launchpad with DRV8353 using encoder feedback

Kirana H P
Prodigy 205 points
Part Number: TMS320F2800157
Other Parts Discussed in Thread: DRV8353

Tool/software:

Hello team,

I am working on the position control of the 48V ABZ+PWM motor using F2800157 launchpad with DRV8353 power board using encoder feedback. I am using the TI Universal motor code (UMC) and I have enabled the macros related to the motor encoder. 

MOTOR1_ENC -> ENABLED

MOTOR1_FAST ->DISABLED

First, I have tested the same encoder motor in MOTOR1_FAST method its working fine up to build level 4 and then I have disabled the MOTOR1_FAST macro and enabled the MOTOR1_ENC.

motor state changing and stuck with fault as module overcurrent. even tried increasing over current value to 300 but still got the error "Module over current'.The same code-only configuration was changed to Hall (enabled MOTOR1_HALL) and checked working fine in 48v HALL motor.

The same code changed the configuration to Encoder (MOTOR1_ENC) not working and getting always like Module over current fault.

Below I have shared the screenshot for motorHandle_M1->motorState and encHandle->encState values after enabling the flagEnableRunandIdentity flag.

I previously asked an E2E question about an encoder motor interface with a DRV8353 using the F2800157 launchpad. I followed their instructions; however, the motor would not run with the encoder motor. I've posted my raised E2E query below; please take a look at it.

(+) TMS320F2800157: Position control of the 48V ABZ+PWM motor using F2800157 launchpad with DRV8353 power board using encoder feedback - C2000 microcontrollers forum - C2000Tm︎ microcontrollers - TI E2E support forums

While MOTOR1_FAST works well up to build level 4, MOTOR1_ENC with feedback does not function. Could you please advise me on all the software-related considerations we need take when connecting the motor with encoder feedback as compared to the MOTOR1_FAST method?

Please advise me on how to run the motor with encoder feedback and fix this module overcurrent error.

Regards,

Kirana H P

  • 0
    Prodigy 205 points

    Hello team,

    Please assist me with this problem and its solution since I have been dealing with it for a very long period.

    Regards,

    Kirana H P

  • 0 in reply to Kirana H P
    TI__Genius 9031 points

    Kirana,

    Apologies for the lack of replies in the currently open threads. Someone was supposed to reach out to organize a call for your company's issues, but I'm going to guess that they haven't contacted you yet? I'll follow-up with them. The intent was to resolve these issues promptly that way, not to delay further- my apologies.

    Regards,
    Jason Osborn

  • 0 in reply to Jason Osborn
    Prodigy 205 points

    Hello Jason,

    Properties -> Pre-defined Symbols I have deactivated everything related to MOTOR1_FAST and MOTOR1_HALL and enabled MOTOR1_ENC, ENC_CALIB, and ENC_UVW.

    I am utilizing the same software that I used to run the 48-volt HALL motor with feedback to run the encoder motor by making changes to encoder-related settings.

    The encoder motor in build level 2 is operating under MOTOR1_ENC with speed_ref = 60 and cannot be run faster than this value; if we set more than 60f value, the motor will only operate in 60f and use less current.

    In build level 4, the motor consumes more current (30A) during operation if I run it with feedback. However, if I remove the feedback, the motor continues to run, indicating that it is not operating with feedback.

    The identical motor runs at speed_ref = 60f and draws less current (1.1A) in build level 2, but it draws more current (30A) and doesn't run on feedback in built level 4.

    In software side we need to change anything for encoder motor compared to hall motor?

    I want to know what the difference between build level 2 is and 4 apart from phase current and voltage which is already mentioned in instaSPIN-FOC.

    We are facing this issue from long time please suggest the proper way to resolve this issue.

    Regards,

    Kirana H P

  • 0 in reply to Kirana H P
    Prodigy 205 points

    Hello Jason,

    ABZ and PWM feedback from the motor side, including 5v and GND, are taken into account when using an actual ABZ+PWM motor in the feedback side.

    Since the encoder in this motor is optical, I'm curious if the number of encoder slots in user_mtr1.h affects the issue mentioned above.Since the encoder in this motor is optical, I'm curious if the number of encoder slots in user_mtr1.h affects the issue mentioned above.

    In build level 4 motor is running irrespective of the feedback and consuming more current across phases with speed_ref = 60f.

    U phase = 110A

    V phase = 130A

    W phase = 115A

    Below I have shared the image for motor state, and it is not entering MOTOR_CTRL_RUN, please go through that once.

    Please suggest me how to resolve this issue. 

    Regards,

    Kirana H P

  • 0 in reply to Kirana H P
    Prodigy 205 points

    Hello Jason,

    As I mentioned in the starting of my query, we are using ABZ+PWM encoder motor so in feedback with ABZ signal we will get PWM feedback also for rotor position sensing.

    But universal motor code is only designed for 3 feedback (A, B and Z) to run the ABZ encoder motor. below I have shared the feedback waveform of the ABZ+PWM motor. please tell me what all the changes are I need to do for running the encoder motor with ABZ and PWM feedback compared to the ABZ feedback in software side.

    If I connect A, B and Z- (PWM) or A, B and Z+ signals to the DRV8353 and launchpad and when I enable the run and identity flag I am getting module over current fault.

    please suggest me what all are the things I need to take care to resolve this issue.

    Regards,

    Kirana H P