Following errors

[scrambled]

Tero-

I have made changes to my flame table to try to get it to run better.

Before the changes, I was using 5 to 1 gearboxes and a 2.5 inch pinion for the rack.

Everything worked, but I was still getting following errors and the acceleration and deceleration was kinda jerky. I could use the table, but I had to keep an eye out for the following error.


So I decided to change the gearboxes out to 30 to 1 and still use the 2.5 pinion. The acceleration and deceleration have improved greatly, but it now fault for a following error with about 15-20 inches of movement.


I am planning on retuning the motors in the next day or so. Is there anything else I can try?

Is there a way to eliminate this fault completely?



Steve

[Xerxes]

Steve,

Can you do the faulting move under GDtool step response test? That would give lots of useful data to find the error source. You can achieve longer moves in that test by:

-Increasing "mutliplier" parameter in trajectory planner page
-Reduce "sample rate" in step test page
-Increase "buffer length" in step test page

[scrambled]

Tero-

The problem is this is on the x axis, and I have two servo motors.

I have not been able monitor both of the axis at the same time. I can only make GDTool connect to one drive at a time.


Any suggestions


Steve

[Xerxes]

Are they brushless or brushed motors? With brushless you will need to use hall-sensors of motors to operate in parallel.

[scrambled]

Tero-

They are brushed DC

Steve

[Xerxes]

Have you tried using DualDC firmware for the parallel axis (one drive controlling both motors)? I believe its easier to set-up for such operation.

[scrambled]

Tero

I have not tried the dual firmware. Right now I have a servo drive for each axis. I don't want to have to rewire everything unless it is absolutely necessary.

I am using the vsd-e 160 volt servo drives and the vsdepi board.

I will try to get a copy of the drive settings before I start making changes.

Is there anything else you need?


Steve

[scrambled]

Tero

I am also using 1125 oz in motors. Would two of these be too much for the dual drive function ?


Steve

[Xerxes]

I guess you have Keling KL34-180-90. I have that motor too and it actually was used during development of DualDC so it will work nicely.

Are your motors & encoders & mechanics & drive parameters identical for both motors?

[scrambled]

Tero

Everything is as identical as I can get. Same motors, gearbox, encoders (1250), and same rack


Steve

[scrambled]

Tero-

I made a mistake when I told you that it was a following error. I was going from memory instead of looking at the error code. Sorry about the wild goose chase.

The error is overcurrent, which according to the error code is probably caused by bad tuning.

Now here is the problem--- i cant get any of the drives to connect to my laptop.

here are some of the items I tried to get it to connect.

1. Made sure to remove the CMD connector
2. Double check that the USB was connected correctly
3. E stopped the machine to disable the HV
4. Last time I had communication problems you also had me install capitors on the + an - HV
5. Installed a ferrite core abound the USB cable- Three wraps
6. removed the motor power connector
7. tried 3 of the 4 drives with no luck


When I connect the USB cable to my laptop- Same laptop I used last year- windows would make a Bing sound when the plug was connected to the laptop


I am leaning towards the possibility that the USB cable is defective. What would be the best way to test it?

Is there a local supplier USA for these cables?


any other ideas?


Steve

[Xerxes]

You can test the cable with this utily:
http://www.granitedevices.fi/assets/files/cabletest.zip

Place the exe file to GDtool install folder and run it when cable is plugged. You'll also need short piece of wire.

FTDI TTL232-R 5V cables are available from Mouser & Digikey.