[radiantheat]

Congrats. When you get a chance , could you post part numbers and photos of the ferrite cores.

[scrambled]

update-

I am slowly getting the motors tuned. So far, I have 2 finished, and 2 to go.

Radiantheat-

The ferrite core was one I had in the shop. I don't have any part numbers for it. I am sure it came from Mouser or Newark.

I tried to take a picture of it tonight, but I forgot to put the CF card in the camera--(oops)


I will try again tomorrow.



Steve

[scrambled]

Radiantheat--

I have attached a picture of the ferrite core for you to see. This is what did the trick. I can communicate with all the drives, but I am still having issues with 1.


Update:

I am having problems with 1 servo drive. This is acting different than the problems I was having earlier. Before when I was having a communication problem, the HV was the problem. I either had to unplug the incomming power to the servo drives that I was not using, or I had to dissconnect the the DB 25 connector to the servo motor.

Now for this last servo drive, the problem is with the encoder connector. As long as the DB connector is plugged in, I can not communicate with the servo drive.


Any ideas? Is it possible that the servo drive is too close to the terminal stripps to the other wiring?

I have attached two pictures that show the drive next to the terminal strips



Steve

[Xerxes]

Hi Steve,

Have you tried isolating the problem with the one drive? You may transfer all GDtool settings from problematic drive to a known good one and swap all cables to it, too.

If swapped drive works, then you may also swap physical location of drives to see if the problem is caused by some interference source near one drive.