TMDXIDDK379D: Problems with TMDXIDDK379D following the EtherCAT-Based Connected Servo Drive.

Hi Victor,

From your description, I think you connected the board to the AC mains, and get all the DC supplies. In this case, BS1 and BS2 must be connected before turning on the AC power to P1. This is specified in the hardware guide under "docs/IDDKv2.2.1_HardwareGuide.pdf".

At the same time, please refer to the schematic of the example and make sure the voltage supplies to the components are configured right, you can have a look at the hardware guide Section 2.8.

Thanks,

Jiaxin

Hi Jaixin,

I've triple checked all the connections mentioned in the DesignDRIVE IDDK Hardware Reference Guide and DesignDRIVE IDDK User's Guide. All the jumpers/resistors/capacitors are set as they came from factory.

I've even tested SW1 and SW2 set to external (without any 15V power supply connected) and without the control card connected. And still the same problem. I'll attach a video with the problem I've been having.

I'll say it again, it was all fine (board powered up well with BS1 and BS2 connected) till I uploaded Incremental Build Level 2. I know something went wrong with that because after pressing run the problem started.

Tell me if you need any other information or if I can help with anything.

Hi Victor,

I have the trouble in opening the video. Could you reupload the .mp4 video file? At the same time, can you take some pictures of how you make the connection? What is the "VdTesting", and "VqTesting" you set while running buildlevel 2?

Thanks,

Jiaxin

Hi Jiaxin,

VdTesting = 0  and VqTesting = 0.1 (I didn't had the chance to change them)

I'm attaching a few key frames from the video (the link seems to work fine; you can download the 4s video by clicking it) and some pictures of the switches/barcodes on the board.

You'll notice that BS1 and BS2 are not connected, as this causes current flow through the ground and shuts down the main switch in the testing room.

I can't delay the development of the drive, so I'm currently focusing on the communication aspect and putting off the motor control for now.

Hi Victor,

Here are two suggestions:

1. The reference code is only verified with the rotary PMSM and needs some modifications to linear motor. You can try to run level 2 (open-loop control) without the connection of the motor and see if this problem comes from board.

2. It is recommended to power the control card with external 15V power supplies (through M3 and M9), instead of the on-board switching power-supply modules (M2 and M8), during code development so the board operates at low voltage.

Thanks,

Jiaxin

Hi Jiaxin,

Everytime I connect BS1 to BS2 and power up the board, it produces some sparks and the differential switch of the room goes off. And that happens with no encoder connected, no ethernet cable connected and no motor connected. It happens every time.

Could you tell me what test points should I probe to find the problem with the board? Or should I send it back to Germany to have it repaired or have it refunded?

Hi Victor,

VictorFS said:

Everytime I connect BS1 to BS2 and power up the board, it produces some sparks and the differential switch of the room goes off. And that happens with no encoder connected, no ethernet cable connected and no motor connected. It happens every time.

I see. So with this observation, it should be the board's problem.

VictorFS said:

Could you tell me what test points should I probe to find the problem with the board?

Do you have external DC power supply at your side? Can you try supplying the DC power through the external power supply, and external 15V to the controller? This could help you determine if other parts on the board still work, and you can continue on the development.

Thanks,

Jiaxin

Hi Jiaxin,

I've measured the component that sparked. It's called RT1 on the PCB's silkscreen (component name: SL32 10015), and it measures 0.1 Ω (in the Datasheets says it should be 10 Ω).

I've also tested M3 and M9 powered by an external 15V power supply, and I had the same problem.

Do you think it could be that component, or could you get me in touch with someone who can help me?

Thanks for the support,

Victor

Hi Victor,

VictorFS said:

It's called RT1 on the PCB's silkscreen (component name: SL32 10015), and it measures 0.1 Ω (in the Datasheets says it should be 10 Ω).

Do you have NTC thermistor to replace the current RT1?

Thanks,

Jiaxin 

Hi Jiaxin,

I don't have any replacement on hand, I purchased TMDXIDDK379D and TMDSCNCD28388D about 3 weeks ago. Is there any chance this is covered under warranty? I am asking that because if I buy the component and replace it myself I think I'll be voiding any kind of warranty.