Need more help

[scrambled]

Hi everyone-

Time for my daily update. Still no luck!


I took some pictures, so maybe someone might see a problem.

I have added some extra wires to help in the trouble shooting, so that explains some of the wild wires.

If you have any ideas, let me know---PLEASE.


Steve

[radiantheat]

well good luck.


I would try taking a 12 volt battery , small jumper cables , a laptop , the cable and a vom and get the "E" out of there and go outback. you should be able to establish communication in no time, with no errors of any kind. if not then my only other idea is call granite for help and check about reload of firmware.

[scrambled]

OK-


I now have a handfull of 330 UF /100 volt capacitors!!!

I am going to install these tomorrow and see what happens. If this does not work, then i am going to do as Radiantheat suggested and remove the drive and try to get it working on the bench.

These capacitors have a long connector and a shorter connector, does it matter which is positive and which is negative?


Any other suggestions???




Thanks
Steve

[radiantheat]

Very nice Hookup. The labeling is top notch.

FYI I gave up on breakout boards after having trouble with one ,I lost months trying to figure it out. Now I just use a PCI parallel port board.(ebay-$20) They cost less than a breakout board and I hope that if I do something stupid (guaranteed!) I will just lose the board.

[scrambled]

Update-


Still no luck.

Today, I tried moving some wires around and checked to see if that helped or hurt. It really did not change anything.


I unplugged both the power and the encoder db-connectors and at that point I can communicate with the VSD-e. I powered everything down, and then installed just the encoder. When I powered everything back up, everything is working. I can communicate with the drives. I could see the encoder count in the GD Tool and if I turned the motor shaft, the encoder would either count up or down. So I know that is working.

When I plugged in the DB connector to the motors, then all communication starts acting up. I can connect to the VSD-e, but as soon as I import the settings, the communications faults out.


I confirmed that the two db connectors are connected to just the FG.

I aslo tried connecting to the GND, and it did not help.


I am attaching pictures of my wire. Could that be the problem?

I have red for positive, black for negitive, and the white is the other positive (the red and white are tied together at the motor connector)


I am at the point that if I remove the drives, I am going to switch them out with another manufacture. Getting the drives installed should not be this hard!!! I am loosing money every day.


any other suggestions????



Steve

[scrambled]

Update-


I installed the two grounding rods, one at each end of the table. It did not help at all.


If anyone has any more suggestions, I will try that.

My next step is to remove the VSD-E servo drives.



Steve

[Xerxes]

Hi,

I hooked up my KL34 motor and created a sample config file for it. Please see
http://cnczone.com/forums/showthread.php?p=603083

The communication problem is definitely caused by interference. I couldn't spot what could be the problem in this setup but many times it helps moving cables further away from each other and sometimes wrapping cables (USB etc) in a ferrite core. Interference is typically proportional to applied HV voltage, so temporarily lowering voltage may help.

[scrambled]

Update---


Success!!! It looks like the ferrite core did the trick. I only had time to test 1 VSD-E, and it worked.

I was able to communicate with it, import the settings, and run and change the step response.

I will have a better update tomorrow, but for now it looks like I am back on track.


Steve

[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.