I just buy a Dugrad Eagle 1000, 4 axis, YOM:2004. I did install it and every things seem right till I turn the screen on. The error on every exits incurred and the problem is no encoder signal.

If someone know how to troubleshoot this, appreciate very much your helps.

Does it indicate which axis has lost encoder? if so you will have to trace out and confirm the encoder signal from motor to controller, if it is all axis you may have a power supply missing somewhere.
Al.

Does it indicate which axis has lost encoder? if so you will have to trace out and confirm the encoder signal from motor to controller, if it is all axis you may have a power supply missing somewhere.
Al.

It's true, it losts signal at all axis. The seller removed the motor when they shipped this machine to us. We did check manytimes the motor installation and cable. It seems right but the error still exist.

I do appreciate that if someone has the wiring book of this machine and share with me. I believe also that we have problem with cable wiring but we could not find where's the root of trouble.

There are some more infors I have just checked with the machine today. Hope any experts can advice me what to do and send me information if any.

Appreciate your help very much

1. On the assembly of the machine, I think we did all right every things.
2. I did check the cable and all cable connection, using voltage and Ampere devices, all seems OK.
3. The encoder signal errors are existed at all axis but not only Y-axis. I did change the encoder cable of axis on the driver, the errors are no change.
4. I did disconnect all the encoder cable (S,X,Y,Z and A) and found that Axis's drivers notified the start-up errors. It means that there's no problem with encoder.
5. I did check the power supply to machine using test device and it found that the power supply is fully enough but the 24V power supply to SIMODRIVER 611 was automatically lost (power off) after 1 minute power-up of the machine, leading to the power lost on Drivers ( I don't know the cause).
6. In conclusion, I think the errors roots from the source driver named SIMODRIVER 611. I am looking for any information, books related to SIMODRIVER 611 to find the cause.
7. I am sending here with some pics.

http://www.flickr.com/photos/33149115@N04/3628030821/
http://www.flickr.com/photos/33149115@N04/3628030821/