• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 271 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDXIDDK379D: HVPMSMMTR does not work properly

Daesik Choi
Prodigy 10 points

Part Number: TMDXIDDK379D
Other Parts Discussed in Thread: HVPMSMMTR

Tool/software:

Dear TI E2E support team,

I'm very new to control a motor and want to control multi-axis motors.

I was following TIDUEV1 document with all kits from TI and 'multi_axis_master' example code.

Before trying to control multi-axis, I've tried to control only a master HVPMSMMTR with TMDXIDDK and F28388d control card. When I set Master_Control build level as Level 1 in cpu1 and Main_Axis_Drive as level 2 in cpu2, the motor just stops as soon as I run the motor.

Also, I am supplying AC 200V, and followed all the steps in Hardware Guide. Variable 'vdcBus' value is around 30 to 50. Should it be around 300V?

Therefore, I tried another example code, 'fcl_f2838x_tmdxiddk'. With this example code, the motor does run and 'vdcBus' is around 300V but it makes high pitch noise from build level 3. However, if I change CURRENT_SENSE from LEM_SENSE to SD_SENSE, it no longer makes noise.

I also have some trouble with FSI communication. If I put F28388D on IDDK board, FSI does not work. But if I run the same code without putting on, FSI does work well. Even though I run with default example code, why do I get this kind of error?

Please guide me what I'm doing wrong. I attached PWM and Current sense on DAC. They seems alright for me.

p.s. Dual-axis example with F280049C and Teknic motors run well.

  • 0
    TI__Mastermind 45606 points

    Hi,

    Daesik Choi said:
    Therefore, I tried another example code, 'fcl_f2838x_tmdxiddk'. With this example code, the motor does run and 'vdcBus' is around 300V but it makes high pitch noise from build level 3. However, if I change CURRENT_SENSE from LEM_SENSE to SD_SENSE, it no longer makes noise.

    For evaluating motor control on IDDK hardware first, this example will be simpler to use since it doesn't have the FSI and eCAT comms integrated. The multi-axis project was originally built upon this 'fcl_f2838x_tmdxiddk' project.

    Daesik Choi said:
    I also have some trouble with FSI communication. If I put F28388D on IDDK board, FSI does not work. But if I run the same code without putting on, FSI does work well. Even though I run with default example code, why do I get this kind of error?

    Is code execution getting stuck somewhere if you pause execution in CCS?

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 10 points

    Dear Kevin,

    Kevin Allen18 said:
    For evaluating motor control on IDDK hardware first, this example will be simpler to use since it doesn't have the FSI and eCAT comms integrated. The multi-axis project was originally built upon this 'fcl_f2838x_tmdxiddk' project.

    That's why I tried 'fcl_f2838x_tmdxiddk' project. But the problem is that it makes high pitch noise from build level 3 with CURRENT_SENSE as LEM_SENSE. Therefore, I checked PWM and Current and they looked alright for me.

    Kevin Allen18 said:
    Is code execution getting stuck somewhere if you pause execution in CCS?

    It stucks in the while loop in FSI_handshakeLead. Even though the master sends a ping, the node cannot receive that.

  • 0 in reply to Daesik Choi
    TI__Mastermind 45606 points

    Hi,

    Daesik Choi said:
    That's why I tried 'fcl_f2838x_tmdxiddk' project. But the problem is that it makes high pitch noise from build level 3 with CURRENT_SENSE as LEM_SENSE. Therefore, I checked PWM and Current and they looked alright for me.

    You could try reducing the bandwidth configured in the project.

    Daesik Choi said:
    It stucks in the while loop in FSI_handshakeLead. Even though the master sends a ping, the node cannot receive that.

    Can you try with a lower FSI clock speed? If that still does not work, I suggest probing the FSI RX lines near the node device.

    Best,

    Kevin